NOTES |
ccNSO PGA WG | Tuesday, 27 August 2024 at 20:00 UTC
Welcome by Jordan Carter
2.
Administrative matters
a.
SOI updates
The ccNSO Statement of Interest form:
https://forms.gle/79Jw4wSnNhn5W4Z46
Check your SOI here:
https://community.icann.org/x/doAFEg
Pengyu Zhu: CNNIC. 4 am here now.
Peter Van Roste: GM CENTR. one of the most important pieces of work for the ccNSO
Laxmi: .np
Abdalmonem: director numbering and planning telecom operator Egypt. Egypt idn ccTLD
Atsushi: JPRS (.jp). deputy vice president planning division
Chris D: Council member. additional notes missing
Diego Ernesto: .co - additional notes missing
Eduardo: .hn link between ccTLD and community. doing social work. joint efforts
Federica: lactld
Irina: .ru on council when work started. member of the ad hoc group at the time
Kim Davies: heads up the IANA team. responsible for implementing the global policies. overseeing staff doing the transfers
Laura: uruguay. I am alac liaison to ccnso. I am observing.
Maria: .co
Mirjana: .rs Serbian registry. i am a member of the GRC for at least 10 years.
Pablo: .pr been with registry for at least 20 years. council member.
Rocio: GM LACTLD
Selina: manager iana operations. iana resource for this group
Svetlana: .ru
ccNSO Council nominated Jordan as interim chair.
Council will formally appoint the chair of the PGA at its next Council meeting
3.
PGA deliverables as per its Charter
Agenda item 3: charter
https://ccnso.icann.org/sites/default/files/field-attached/charter-pga-wg-13jun24-en.pdf
Jordan: situation with a ccTLD led to a response by council. a small group of council members convened. the ad hoc group.
see introductory paragraph of the charter
Ad-Hoc Group) began to explore a range of issues, including:
● Potential for consolidation of core policy - currently there are a variety of policy
documents, which only partly describe the actual policy. For example, RFC 1591
includes a lot of language around gTLDs and language that has become obsolete
with respect to ccTLDs.
● Unaddressed identified issues – Over time situation have emerged and been
identified that are not addressed in policies or agreed upon practices
● Emerging issues that have never been contemplated.
Foundational responsibility of the ccNSO. Ad hoc did not feel like the right way to move forward. hence the more formal creation of the PGA WG.
The objective of the PGA WG is to:
A. Complete preparation of an overview of ccNSO policies and guidance related to
ccTLDs and present the overview at ICANN81.
B. Provide details to Council and ccTLD community on any gaps in the current
policies, guidance or practices pertaining to the delegation, transfer, revocation
and retirement of ccTLDs, and other related IANA Naming Functions for ccTLDs
(hereafter: Gaps, or Gap), and
C. Advise the ccNSO Council if, the order and how these Gaps need to be addressed
by the ccNSO. tools? report, study group, full pdp as some examples.
Abdalmonem: how could we go for the gaps? do we need community input? will we review the policies and list the gaps and present our findings to the community?
Jordan: combination.
Bart: not only gaps in the policy. See also discussion in Kigali. depends on how you qualify the gap, which tool you use to address. a gap could also mean in the interpretation or implementation
of the policy.
Jordan: any questions about the objectives? none
Jordan: working with PTI and IANA, and propose an order of the gaps. not wise to fix everything at once. see agenda item 5
Diego: how do we know there is a mistake in the policy? gap in the interpretation?
Bart: different interpretations. example. include as background. if you would have a look at the Framework of Interpretation, it provides interpretation for RFC1591. source doc for revocation
etc of ccTLDs. ultimately it is the call of this group, whether this is interpretation or implementation. this group to propose to community
Abdalmonem: question
Jordan: if we identify a gap, we will suggest the tool as well. this group does not decide on a new policy. that will require follow-up work. it will involve consultations with the ccNSO community,
and beyond.
Bart: hypotehticals driven by experiences from iana.
Jordan: iana deals with most cctlds as anyone in icann org. they experience most vividly what the gaps mean. work openly and cooperatively with the iana team. as clear and complete as possible.
Jordan: Framework of Internpretation (FOI)
https://ccnso.icann.org/en/workinggroups/foi-final-07oct14-en.pdf
4.
What has been done to date?
https://community.icann.org/display/ccnsowkspc/Background+Material
Bart: starting doc.
11 areas to further discuss and work on.
4 of them were discussed in San Juan and in Kigali. Results from these discussions can be used by the PGA WG. You will see a series of questions by iana that drive the discussion.
Bart: 2nd one.
clearly one of the objectives. overview applicable polcies and advisories. needs to be updated. contains an overview in table format of all relevant policies. starting with policy mandate of
the ccnso.
interprtation of the section of the FOI inserted. assumption of the policy
Jordan: start with the 2nd doc on the list. that is the best way to start. then start looking at doc 5 on this list. it will give you the context. number 2 doc is the kind of output we are asked
to prepare for the istanbul meeting.
5.
Setting priorities for next steps
6.
AOB
7.
Next meeting
Suggestion is to meet every 2 weeks.
10 September
24 September
a.
Rotation
timing, seen the geographical diversity of the group.
Bart: we will share an overview of the geo distribution of the group members, and come up wth 2 or 3 times. rotate between those times. if you miss the meeting, there will be a recording. decisions
will be made only after a second reading/meeting.
8.
Closure
Bart: nominate a chair and vice chair online.
Jordan: if you want to nominate someone, send email to group. also accept or reject when you have been nominated.
Decision at the next meeting.
Peter: How will we organise and provide input? Mainly meetings? Collaborative docs?
Jordan: ad hoc. written input, and discussions. that is how we approeached it in the past. more info at the next meeting.
Bart: pdf, to ensure accessible to all. baseline. cannot be edited. we could turn them into google doc for collaboration.
Jordan: homework