<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.6049" name=GENERATOR>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.0pt; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
LI.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-compose
}
.MsoChpDefault {
mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
OL {
MARGIN-BOTTOM: 0cm
}
UL {
MARGIN-BOTTOM: 0cm
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2>Guys,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2>I'm very sorry having missed the call yesterday. It was my
fault in organizing myself.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2>Thanks, Tony, for the summary as well for the draft
charter. I've only a small edit (see attached) with regards to the council
member terms. In line with the rules of procedure it should be pointed out that
one follow-up term should be allowed.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2>Thanks also for assigning the travel support that
way.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2>WIth respect to the ISPCP meeting in SF I'd suggest to
invite the new SSAC chairman for a short presentation and discussion on their
activities.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2>In addition, I'd like to draw your attention to the "Joint
DNS security and stability analysis WG (DSSA-WG)" which has been established
last year and is still open for volunteers; GNSO approved draft charter at <A
title=http://ccnso.icann.org/workinggroups/dssa-draft-charter-12nov10-en.pdf
style="COLOR: blue; TEXT-DECORATION: underline"
href="http://ccnso.icann.org/workinggroups/dssa-draft-charter-12nov10-en.pdf"><FONT
face="Times New Roman"
size=3>http://ccnso.icann.org/workinggroups/dssa-draft-charter-12nov10-en.pdf</FONT></A>.
If you're interested in participating pls. let me know or forward the name of
the participant directly to the GNSO secretariat.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=108213409-27012011><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=de><FONT face="Courier New" size=2>Best regards</FONT></SPAN>
<BR><SPAN lang=de><FONT face="Courier New" size=2>Wolf-Ulrich
</FONT></SPAN></P><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=de dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>Von:</B> owner-ispcp@gnso.icann.org
[mailto:owner-ispcp@gnso.icann.org] <B>Im Auftrag von
</B>Tonyarholmes@btinternet.com<BR><B>Gesendet:</B> Mittwoch, 26. Januar 2011
20:25<BR><B>An:</B> ispcp@icann.org<BR><B>Betreff:</B> [ispcp] Main points
from ISPCP conference call Wenesday 26th Jan<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN lang=EN-GB>The following note record the main issues
discussed during the call.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB><o:p> </o:p></SPAN></P>
<P class=MsoNormal><U><SPAN lang=EN-GB>Changes to ISPCP
Charter<o:p></o:p></SPAN></U></P>
<P class=MsoNormal><SPAN lang=EN-GB>An updated copy of the ISPCP Charter had
been circulated which attempted to align the document with relevant
requirements set out within the CSG Charter. <I>Comments should be submitted
to the Secretariat within the next 7 days</I>. If no comments are received
this version (v4) will be considered the final approved version of the ISPCP
Constituency Charter.<o:p></o:p></SPAN></P>
<P class=MsoNormal><U><SPAN lang=EN-GB><o:p><SPAN
style="TEXT-DECORATION: none"> </SPAN></o:p></SPAN></U></P>
<P class=MsoNormal><U><SPAN lang=EN-GB>Arrangements for the March San
Francisco meeting<o:p></o:p></SPAN></U></P>
<P class=MsoNormal><U><SPAN lang=EN-GB><o:p><SPAN
style="TEXT-DECORATION: none"> </SPAN></o:p></SPAN></U></P>
<P class=MsoNormal style="TEXT-INDENT: 36pt"><SPAN
lang=EN-GB>-
Proposed meeting between SO reps and ICANN <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>ICANN have proposed an additional meeting
between the chairs of the SOs and ACs and ICANNs CEO. Originally the proposal
was for a 2-day meeting but has since been reduced to a half-day session
followed by dinner. No agenda for the meeting has been posted. ISPCP
councillors will offer support for attendance by the GNSO Chair and in
addition will call for an agenda to be posted in good time, and for the
outcome to be publicly posted to ensure full
transparency.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB><o:p> </o:p></SPAN></P>
<P class=MsoNormal style="TEXT-INDENT: 36pt"><SPAN lang=EN-GB>-
GNSO
arrangements<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>No information is currently available on
the agenda for the GNSO sessions that will be held on the Saturday and Sunday
prior to the meeting. This issue will be discussed once that
happens.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB><o:p> </o:p></SPAN></P>
<P class=MsoNormal style="TEXT-INDENT: 36pt"><SPAN
lang=EN-GB>-
Constituency and SG arrangements<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>It has yet to be confirmed whether the CSG
breakfast with the Board will take place in San Francisco. Concern exist
within the ISPCP that the ability to have adequate dialogue with ICANN Board
members will be reduced. If this meeting does not go ahead the ISPCP will
discuss with other CSG representatives how best to increase the level dialogue
with Board members, the GAC and other key stakeholders<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB><o:p> </o:p></SPAN></P>
<P class=MsoNormal style="TEXT-INDENT: 36pt"><SPAN
lang=EN-GB>-
Early agenda items for the ISPCP Constituency meetings<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>No final decisions were taken with regard
to the ISPCP Constituency meeting, but <I>members were asked to flag important
issues for the agenda</I>, particularly after the GAC, Board meeting in
Brussels.<o:p></o:p></SPAN></P>
<P class=MsoNormal style="TEXT-INDENT: 36pt"><SPAN
lang=EN-GB><o:p> </o:p></SPAN></P>
<P class=MsoNormal style="TEXT-INDENT: 36pt"><SPAN
lang=EN-GB>-
Travel support<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>ICANN travel support, allocated via the
ISPCP Constituency for the San Francisco meeting will be assigned to
Wolf-Ulrich Knoben (GNSO Councillor) and Tony Harris (ISPCP CSG executive).
The Secretariat will advise the GNSO secretary.<o:p></o:p></SPAN></P>
<P class=MsoNormal style="TEXT-INDENT: 36pt"><SPAN
lang=EN-GB><o:p> </o:p></SPAN></P>
<P class=MsoNormal><U><SPAN lang=EN-GB>GNSO Council
issues<o:p></o:p></SPAN></U></P>
<P class=MsoNormal><SPAN lang=EN-GB>Attention was drawn to the status of the
report on CWG Rec 6. The GNSO council have been requested to endorse the
report which was sent to the Board via ALAC. Concern exist that the CWG did
not refer back to the SO’s prior to submitting their report to the Board.
<I>ISPCP members are invited to send comments on the report to the list within
the next 7-days</I> in order to ensure ISPCP council members can represent
their views when this is discussed at the next GNSO Council
meeting.<o:p></o:p></SPAN></P>
<P class=MsoNormal><U><SPAN lang=EN-GB><o:p><SPAN
style="TEXT-DECORATION: none"> </SPAN></o:p></SPAN></U></P>
<P class=MsoNormal><U><SPAN lang=EN-GB>ATRT report<o:p></o:p></SPAN></U></P>
<P class=MsoNormal><SPAN lang=EN-GB>Olivier Muron gave a short overview of the
status of the ATRT report which is now open for public comment. It was noted
that the ISPCP have already raised issues over the ASO, which whilst raised
within the report, were not covered by the recommendations. This remains a
major issue for the ISPCP but no further action was proposed.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><U><SPAN lang=EN-GB><o:p><SPAN
style="TEXT-DECORATION: none"> </SPAN></o:p></SPAN></U></P>
<P class=MsoNormal><U><SPAN lang=EN-GB>GNSO Working Group
Guidelines<o:p></o:p></SPAN></U></P>
<P class=MsoNormal><SPAN lang=EN-GB>Public comments on the WG Guidelines are
now invited. <I>ISPCP members who wish to express any views were invited to
contact Wolf-Ulrich Knoben</I> who has led on this issue for the
Constituency.<o:p></o:p></SPAN></P>
<P class=MsoNormal><U><SPAN lang=EN-GB><o:p><SPAN
style="TEXT-DECORATION: none"> </SPAN></o:p></SPAN></U></P>
<P class=MsoNormal><U><SPAN lang=EN-GB>ISPCP website<o:p></o:p></SPAN></U></P>
<P class=MsoNormal><SPAN lang=EN-GB>Noting the ISPCP website urgently requires
updating and that currently this cannot be achieved through the GNSO toolkit,
it was agreed that minimum changes must be made to reflect the current
organisation of the ISPCP, its charter and position statement. Once this can
be handled as part of the GNSO toolkit the Constituency will appoint a contact
person for the website. The Secretariat was requested to pursue this in
conjunction with the GNSO Secretariat.<o:p></o:p></SPAN></P>
<P class=MsoNormal><U><SPAN lang=EN-GB><o:p><SPAN
style="TEXT-DECORATION: none"> </SPAN></o:p></SPAN></U></P>
<P class=MsoNormal><U><SPAN lang=EN-GB>Date of next conference
call<o:p></o:p></SPAN></U></P>
<P class=MsoNormal><SPAN lang=EN-GB>To be advised.<o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BLOCKQUOTE></BODY></HTML>