Re: Proposed Charter for EPP Extensions (eppext) Working Group
"Hollenbeck, Scott" <[email protected]> Tue, 24 Sep 2013 11:01:41 +0000
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <831693C2CDA2E849A7D7A712B24E257F492815E8@BRN1WNEXMBX01.vcorp.ad.vrsn.com> |
> -----Original Message----- > From: Ning Kong [mailto:[email protected]] > Sent: Tuesday, September 24, 2013 2:08 AM > To: Hollenbeck, Scott > Cc: [email protected] > Subject: Re: [provreg] Proposed Charter for EPP Extensions (eppext) > Working Group > > > > Ning, I was trying to limit the initial list to a small number of > active drafts that have already been the subject of discussion and have > been revised at least once to reflect that discussion. Your document is > a -00 draft that expired in September 2012. Given the lack of recent > progress I didn't think your document was far enough along to be > included in the first batch. > The main reason of the lack of progress is that there is not a suitable > WG to improve it. I had thought to form a new WG for this work. I'm > very glad to see your work for the new eppext WG. > > I'm not sure we should limit the number of active drafts or limit the > number of topics for the first batch. If we choose topics, I think my > draft is within the scope. As I mentioned in my last email, > "registering internationalized domain name variants" is listed in the > proposed charter, but there is no draft within the current first batch > discussing the variants issue. I'm going with Pete's original guidance on the drafts to be selected. This is how John Levine explained that guidance to me: > I talked to Pete Resnick, one of the IETF apps area ADs yesterday, and > he > says he's willing to set up a short lived working group to turn EPP > extension drafts into RFCs. There are two conditions: that we identify > the drafts in advance, all of which have to be in current use, and that > we > round up enough people with implementation experience to read them and > confirm that what we plan to publish is what they implemented. So I have to disagree when it comes to imposing limits - and I can easily change the proposed charter text if there is any confusion about IDN variants. Pushing out an update now to create the illusion of activity won't help us. Scott _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg