Last Modified: 2004-11-02
|
IDN BOF, Washington DC Notes
Nov 9, 2004 Chairs: Howard Eland Patrick Falstrom Edmon Chung presentation: IDN over EPP (IDNPROV) IDN/EPP Basics IDN Submission (Punycode?, UTF-8?, ...) Language Tags Variants/Provisioning IDN Registration/Background Extend EPP ? New IDN Object mapping ? .pl example no extensions to EPP .info extension to domain mapping .tw idn object and variants Proposal Extend EPP to make "idn" work Prob Statement and Discussion Does this work require a new WG within the IETF ? Moving Forward John Kleinson Issues need work drivin by ICANN Unable to get IANA to engage Should we figure it out here and present to them or you come with a better idea Risk to go ahead without IANA/ICANN input Charge ahead ? and present solution ? ICANN has not offered input into this problem as of yet Edmon Start with a protocol extention and requirements Berney IDN is just one of the problems Contact is another problem EPP is not usable for IDN as it stands, needs changes to core EPP ccTLD is not able to use EPP, esp Contact object and field separatino Host and subordinate object, and relationship to domain is not always the case Transfer of domain, .... Scott Redsign EPP not for here Too late should have discussed when EPP was in WG Get back to EPP IDN not redesign EPP Ted Diversity of solutions, may be diverse problems Legal requirements, drive problems Non interroperable extensions to EPP Standardize epp extensions ? and does this help and issues around that Scott Refer to examples, where is case to unify 1 solution in IDN extension what benefit is there with a common solution Who is the customer for this standardization ? Edmon EPP tried to find a common domain registration and so why not IDN follow suit ? Can we standardize IDN EXT ? .jp Multiple registration world will need common IDN, but not used as of yet Howard examples just a sample not a basis for common IDN Ed Luis Basic framework for EPP - Yes Should that apply to extensions ? and is IDN one of them More than one way may be better Is this even possible Janusz examples given are subsets and very close in relation, perhaps could find a common solution Focus on mechanism for IDN that are outside of policy, but focus on facts like mapping Edmon There are common elements to make up a basic extension, common feature set to standardize Andy Newton Problem policy not data model Policy will get in the way of the extension, push work into the XML What are all the policies and can we enumerate them all and is very complex Edmon Server policy are enforced in the software but the XML will provision the common elements Are there enough common elements Mech of IDN is a meaning full addition Policy is in the server not the protocol, common elements drives the need lang tag Mike Young IDN Ext may not suceed you can choose to opt in or out of this common idea Time is now to implement John Too many different IDN EXT may do more harm than good But, .. there must be a uniform aggreement and improve competitive env. not IETF problem Pete URL schemes, etc, list of these types, http/ftp/... IANA registry of here is how we do lang tag ... Scott ICANN problem guidelines describe the Reg/Reg Refer to RGP ext Open to common IDN ext and post as proposal using ICANN guidance in ICANN context for ext Jansuz Complexity of IDN is more than RGP and needs WG More input would help in the WG forum Edmon Variants would make this more aware Chinese example would be a perfect example as its a req. There is a good working scope already Beine Collect problems issues on IDN EPP and EPP ? req for other epp problems in IDN world Patrick You need to know what the problem is, what do we want to do Scott EPP already has req and they are avail area directory, can not charter WG on just EPP as this is closed need to be based on new work not standard EPP Ed Luis This work should go to RFC eventually whatever it is, but are there harmonious req for this We need to get all the common req, it should be a WG if we have a common question Many sources of req ICANN, .... Edmon What are the common elements and this would be the first thing done in the WG Ted Hardie Wonder will this solve any of our problems The common tools do they solve the problems Worse off if we have a bunch of tools in a non common ext We may get it wrong if we try to solve the entire problem set John ICANN, will not help and would not really be a help ICANN should be deployed by users of IDN and get them to force IDN common items When they make those standards we come back here and make a WG Need real proof that we can really come up with a common toolkit and protocol Patrick Whether we have something here are new requirements here not already discussed, to change the EPP protocol Scott and Patrick think to do work on this we need to know what we need before we make a WG New ideas not old ones already discussed and is there a problem to solve John Concerned with appearance of author EPP enforceing rules in this forum and consider it a joint decision not just Scott. Ted Area director you are not ready for a HMM, do more work before you come here and have a written document set to give an example of the short comming ICANN might help you but you need to consult them first before this and a HMM 2nd BOF and come back again with more proof this is even needed Find those common elements and bring them here not just we need "common idn framework" Scott ICANN will be talking about this in cape town, in a month and now would be a time to talk to them Get the req and bring them to ICANN ICANN looking at IDN committee and EPP Edmon How ? ICANN John Needs beer to talk about this in more than one hand and first beer would be a good start. |