Re: ENUM WG Request for Publication - draft-ietf-enum-iax-04.txt
<[email protected]> Thu, 18 Sep 2008 10:46:59 +0200
| Newsgroups | gmane.ietf.enum |
|---|---|
| Message-ID | <[email protected]> |
Hi Cullen Peter has suggested to test-run the new Enumservice registration process. The document defining this process (draft-ietf-enum-enumservices-guide-12) is currently in WG LC. Is the IESG interested in such a test-run of the new Enum Registration process as it has been done with 2929bis? The IAX Enumservice registration (draft-ietf-enum-iax-04) is a perfect sample for this. cheers, Bernie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Cullen Jennings Sent: Wednesday, September 17, 2008 8:16 PM To: Peter Koch Cc: [email protected]; 'Peterson, Jon' Subject: Re: [Enum] ENUM WG Request for Publication - draft-ietf-enum-iax-04.txt My suggestion of the easiest way to solve this would be to IETF Last Call draft-ietf-enum-iax calling out a 3967 downref to draft-guy-iax-04. On Sep 7, 2008, at 2:23 PM, Peter Koch wrote: > On Fri, Sep 05, 2008 at 02:41:06PM -0400, Richard Shockey wrote: > >> Title : IANA Registration for IAX Enumservice >> Filename : draft-ietf-enum-iax-04.txt > >> A two week WG last call on this document concluded on July 7, 2008. >> >> The document listed above is being considered for Proposed Standard. > > so, for the process addicts amongst us - what is the solution to the > downref problem? > There is a normative reference to <draft-guy-iax-04.txt> and > rightfully so. > This drafts sits in the RFC Editor queue for publication as > Informational. > RFC 3967, section 2, first bullet item, could be read as a way out of > this, but I doubt it could be appropriately invoked: the only reason > that draft-ietf-enum-iax-04.txt is aiming at Standards Track is that > that has been the only way to get an enum service registered since > RRFC 3761. > Now, the IANA registration document update for ENUM services is in > WGLC now and hopefully can be shipped to the IESG soon. This > eliminates the need for draft-ietf-enum-iax-04.txt going to proposed. > Instead, I've had hoped - apologies if you heard this a couple of > times already - we could have processed draft-ietf-enum-iax-04.txt > under the upcoming ENUM services guidelines with an exception granted > from the IESG as it was done with RFC2929bis. > > What's the plan? > > -Peter > _______________________________________________ > enum mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list [email protected] https://www.ietf.org/mailman/listinfo/enum