Re: FW: I-D ACTION:draft-ietf-enum-enumservice-sms-smpp-01.txt WGLC ????

Peter Koch <[email protected]> Thu, 2 Oct 2008 10:55:48 +0200
Newsgroups gmane.ietf.enum
Message-ID <[email protected]>
On Wed, Oct 01, 2008 at 01:29:03PM -0400, Richard Shockey wrote:
> In our desire to clean up the document queue... are we ready for WGLC on
> this?

> 	Title		: IANA Registrations of Enumservice 
> "sms:smpp" and "smpp" URI
> 	Author(s)	: J. Yu
> 	Filename	: draft-ietf-enum-enumservice-sms-smpp-01.txt

I understand the draft updates an existing registration, as stated in

      This document updates RFC 4355 [4] by registering a new enumservice 
      subtype "smpp" under the existing type "sms" using the URI scheme 
      "smpp" as per the IANA registration process defined in RFC 3761 [2] 
      and draft-ietf-enum-enumservices-guide-07 [12] and registers a new 
      URI scheme "smpp" according to the URI registration procedure in RFC 
      4395 [5]. 

but how can it refer to both Enumservice registration procedures at the
same time?  Isn't this an update that can wait until after approval of
the Enumservice guidelines or is a standards track document really intended?

My reading of the example in section 6 is that it actually contains the
specification for the "smpp:" URI resolution.  

The extra abbreviations section is uncommon for RFCs and since most of the
abbreviations are pretty well expanded in the text within proper context
(SRV=Service only makes sense if you have the RR type in mind), I'd doubt
its necessity.

-Peter