Re: INFO Framework: IANA Registry

"Elwell, John" <[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <0D5F89FAC29E2C41B98A6A762007F5D0014831AA@GBNTHT12009MSX.gb002.siemens.net>
 

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Eric Burger
> Sent: 20 November 2008 00:47
> To: SIP List
> Subject: [Sip] INFO Framework: IANA Registry
> 
> There was some discussion as to whether the registry for Info 
> Packages  
> should be Specification Required, Expert Review, or First Come First  
> Served.
> 
> Specification Required today means that the specification requires  
> expert review.
> 
> Expert Review means someone needs to give a cursory review of the  
> registration application.
> 
> First Come First Served means what it says: send a note to IANA, and  
> get a registration (with some basic review).
> 
> We can also have two trees, one Specification Required and one  
> Private. This has been proven to be an interoperability and 
> marketing  
> nightmare, but I will put it out there for completeness.
> 
> 
> I would offer we go with First Come First Served.  We can 
> have a field  
> for a reference, giving us the best of the specification 
> required (you  
> can look up what a published specification is) and Private 
> (if you are  
> creating a private Info Package, you do not have to specify anything  
> other than the package name).
> 
> Please Vote:
> [X] First Come First Served with pointer to optional specification
> [ ] First Come First Served
> [ ] Specification Required
> [ ] Expert Review
> [ ] Two trees: Specification Required and Private

John
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.