This page is for you to publish your meeting reports for Monday. Please log in with your email address and password ad use the "edit" button to add your report.

Reports from other days:

Tuesday, 27 October 2009 Wednesday, 28 October 2009 Thursday, 29 October 2009*

IRTP Part B WG Open Meeting

Time: 0700 - 0830
Location: Sapphire 1-3 (L3)
Author: Wolf, Cheryl

Cheryl, Silvia and I were at the Internet Registry Transfer Policy B WG openMeeting this morning. There were not too many people present at that early hour
of the day, and I must admit, I had some difficulties to catch-up with the
discussion. But I think we have to follow-up this debate more closely to
formulate our position. It was interesting to observe the “dynamic” of this
group. Need to discuss how to get involved.

SSAC Open Meeting

Time: 0730 - 0900
Location: Sapphire 4 (L3)
Author: Patrick, James, Dev, Gareth

SSAC - Monday
The SSAC was organised after 9/11 There are on going reviews. SSAC gives guidance to the Board and the community.

Questions remain as to the nature of the threats and there is an outcomes report to be produced.

One of the major topics at the session was the problem of redirects. If they are not done properly at the browser level they can affect many basic Internet operations.

For example, Mail won't work properly anymore - error messages don't get generated and ping and traceroute don't work.

IDNs would break as well.

As many inexperienced users equate the Web with the Internet, improper redirects are often not seen as the problem they really are.

Gareth

SSAC presentation : http://sel.icann.org/meetings/seoul2009/presentation-ssac-26oct09-en.pdf

Steve Crocker, chair of SSAC gave an background overview of the SSAC.
Ram Mohan discussed the 1st ever SSAC retreat which took place on 29 sept to 1 oct 2009.
where several topics were discussed and recommendations made. The were many positive comments about the retreat from the attendees.

Rom Mohan introduced the next topic "Redirection & Synthesized DNS - Responses in TLDs" aka
DNS wildcarding at the TLD level. The SSAC perspective : DNS wildcarding at the TLD level is significant danger to security & stability of the DNS ; DNS wildcarding at the TLD level impacts all internet applications ; breaks basic troubleshooting tools (e.g ping).

SSAC advice is for the prohibition of wildcarding for all TLDs. Question was asked re: DNS wildcarding at the ISP level. The response was that the SSAC did not consider DNS wildcarding at such a level ; another pointed out that an end user can choose a different DNS resolver as a workaround but no workarounds exist for DNS wildcarding at the TLD level.

Rom Moham introduced the next topic "Scaling the root"
Bruce Tonkin pointed out in a comment that ICANN has gone though this before. When ICANN went from three letter TLDs to longer length ones, there were problems with software vendors/internet services that made incorrect assumptions (e.g mail software that assumed TLDs were only 3 characters in length, but they adapted. Similarly root servers will also adapt.

Orphaned Name Services from Dave Piscitello was the next topic. The Step2 slide (page 25 in the PDF) was challenged by someone in the audience that such a scenario could not happen under the .NET TLD as Dave had mentioned. Didn't understand this topic fully.

After a discussion of the SSAC Outreach activities (there was mention of a one page information piece on SSAC at the registration desk - perhaps ALAC should have one also?), in response to a question, SSAC said that there was no formal SSAC involvement re: High Security Zones in the DAG v3.

Dev Anand Teelucksingh |

New gTLD Program Overview

Time: 1030 - 1200
Location: Crystal (L2)
Author: Pavan, Didier, Dave, Evan, Sebastien, Carlton, Dev

A slightly refreshed version of the same old roadshow we've heard multiple times before. Some of the new stuff in DAGv3 introduced. Invitation to attend other sessions. Yawn.
The "Q&A" was generally a parade of registrars and would-be registries complaining about the delays, and especially the lack of hard deadlines.

  • Evan

Clearly many were very disappointed at the further delays announced, not just delays but no new timeline given. Cost of delays running to millions of dollars in back-end services. paraphrasing on comment "its cost us collectively this morning a few hundred thousdands dollars to hear Kurt say there will be further delay."

Important point is there is no regulatory certainty.

  • Adam |

Orientation Session for New & Returning ccTLDs

Time: 1100 - 1130
Location: Astor (L36)
Author: Rudi

Please add your report here

IDN ccTLD Fast Track WorkshopTime: 1330 - 1500

Location: Crystal A (L2)
Author: James, Cheryl, Sylvia

Quick Summary from James:
1. If all thing goes well, ICANN will start accepting application from
16th Nov 2009 onwards. They expect about 50 or so applications.

2. The issues of variants seem resolved. ccTLD will get their variants
one way or another.

(Altho not said in the public forum, I understand that China is still not quite happy with the handling of the variant, as a matter of "principles")

So unless for some odd reasons the Board decided not to approve it on
Friday, IDN ccTLD Fast Track should be starting soon. |

Registry/Registrar Seperation Discussion

Time: 1500 - 1630
Location: Crystal B (L2)
Author: Adam, Dave, Pavan, Andrés

Sorry, missed this meeting, was talking about discussions going on at the ITU Council meeting where there's a push for allocation of IPv6 by national registries from a block controlled by the ITU. Will send more information about this as an when I get it.***

I attended the registry-registrar separation discussion. Was kind of intrigued by the lineup for and against. At the minute, separation means the status quo; registries are not permitted to own registrars of their own TLD. The new proposal is to allow such ownerships up and down, full or partial, leading to vertical integration.

Those opposed say the access to transaction and traffic data is presumptively advantageous and will lead to bad anti-competitive behaviour; for example, warehousing of preferred domain names to be disposed later to the highest bidder on the auction block. They suggest that this will give an unfair advantage to the vertically integrated couplings, leading to market dominance and de facto restraint of trade.

Those in favour point out that the data issue is a red herring since both classes can be collected elsewhere via commercial contract; that the behaviour is common in other industries, including regulated ones. And given the RAA and other safeguards, this is a rank demonizing of what amounts to operationalizing an ordinary business model.

Apparently Afilias, Nuestar and PIR are for separation; the status quo. Network Solutions is the biggest name against. Sometimes you feel the hand of Esau even as you hear the voice of Jacob. Makes one wonder what the real issue is.

  • Carlton Samuels

Malicious Conduct and new gTLDs

Time: 1630 - 1800
Location: Crystal A (L2)
Author: Rudi

Standard presentation, focusing on large users (ie, financial)

Malicious Conduct and Consumer Protection

Time: 1730 - 1800
Location: Crystal A (L2)
Author:

Please add your report here


Vanda - some points I would like to raise:
a) related to registry X registrar separation - i believe ALAc should demqnd a more detailled study related to economic impact from the alternatives if implanted.
b) another concern I have mention during the GAC/ALAC meeting is realted qith the consumer confusing relate to new IDN ccTLD. some implementation with diferent lenght TLD may no work in some softwares, so user shall be alerted/awarned about it before sign.

contributed by guest@socialtext.net on 2009-10-27 14:36:22 GMT



SSAC - Monday

The SSAC was organised after 9/11 There are on going reviews. SSAC gives guidance to the Board and the community.

Questions remain as to the nature of the threats and there is an outcomes report to be produced.

One of the major topics at the session was the problem of redirects. If they are not done properly at the browser level they can affect many basic Internet operations.

For example, Mail won't work properly anymore - error messages don't get generated and ping and traceroute don't work.

IDNs would break as well.

As many inexperienced users equate the Web with the Internet, improper redirects are often not seen as the problem they really are.

Gareth

contributed by guest@socialtext.net on 2009-10-29 06:26:29 GMT

  • No labels