[IANA #171390] FW: Revision of IANA Enumservice registry

Hello Bernie,

Will there be a version 13 to look at?  I just checked and didn't see one.
I didn't see any response to how IANA will categorize the request's stages as
far as our tracking goes so hopefully what I outlined below as ok (as far as
waiting on requester).

For the time limit, it is a bit hard...
So if the documentation is going to be in the form of an RFC, maybe the ticket
should just be closed after the registration is approved by the expert, as the
addition of the service name would follow the normal RFC publication process and
be part of the approval.  The only thing is that the expert would need to review
it as part of the approval.

For the other types of documentation, it really depends on how long other types
of documents take to get published.

We could just resolve the request after the expert approves the template. Then
open a new request when the documentation has been published and then have the
expert do the second review then.

What are your thoughts?

Thanks,

Michelle


On Sun Oct 19 23:38:55 2008, [email protected] wrote:
> Michelle,
> 
> Thanks for your fast feedback.
> 
> I have changed the document to make it more clear, i.e. I made a
> difference between RFC specs and other specs. RFC specs follow the
> normal
> IETF procedures, non-RFC specs are handled slightly different (as
> outlined
> below).
> 
> The XML2RFC template is no longer part of the document, so no worries
> here.
> 
> The only comment I have not addressed (yet) is the time limit. Does
> this really have to be specified? If yes, what would be good figure?
> 
> cheers,
>   Bernie
> 
> 
> 
> > Bernie, I have reviewed the IANA Considerations section in version
> 12 of the
> > document once more.  Most everything does seem ok.
> > I do have a couple comments.
> >
> > I still feel the review described here does not exactly follow what
> is described
> > in RFC5226, so it might be worth stating that it follows RFC 5226
> with some
> > additional procedures.
> >
> > When a registration is first reviewed by an expert and then is
> approved.  IANA
> > will notify the author (requester).  At that time, it seems that the
> > registration is then put "on hold" waiting for the publication of
> the
> > specification. When IANA has these requests in our ticketing system,
> is it
> > sufficient to put this request as "waiting on the requester" as IANA
> waits to be
> > informed the spec has been published? Is there a time limit of how
> long IANA
> > waits?  This means IANA will have a ticket open for a long time in
> our queue.
> >
> > Also.  For section 11.2, does IANA really need to make the xml2rfc
> template
> > public or is having it in this document enough?  Also, will you be
> adding the
> > "chunk" for the registry when it is finalized for future
> registrations?
> >
> > Hope this review helps.
> >
> > Michelle Cotton
> > IANA
>