A URN Namespace for ucode
RFC 6588

Note: This ballot was opened for revision 03 and is now closed.

(Peter Saint-Andre) Yes

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

Comment (2012-02-14 for -)
No email
send info
I agree with Stephen's DISCUSS that the language on IoT could be tightened up.  IoT is more of a concept than something concrete, and there are different approaches to IoT, not all of which necessarily involve ucode.

(Adrian Farrel) No Objection

Comment (2012-02-14 for -)
No email
send info
I agree with the concern about the term "Internet of Things". I don't
think the use of that term is needed to justify this work, and I believe
the I-D would be easier to read and more compelling if the term was left
out. It is good enough to say "ucode exists and is use din many 
applications. This document provides a URN namespace for ucode to 
enable its use in Internet-related devices and software."

(Stephen Farrell) (was Discuss) No Objection

Comment (2012-02-14)
No email
send info
- Can someone tell me if uidcenter.org is ok as an SDO for a
normative reference or not? I've never heard of 'em but this
may be outside my normal sphere of operation. 

- Even if uidcenter.org is ok, their normaive July 28 2009 document
(with a 2010 copyright?) or white paper or working draft doesn't
seem like a very stable document as a normative reference for an

- Even if it were, then it appears that this I-D a) repeats the
text from the [UCODE] ref - if uidcenter.org are a bona-fide SDO
why is an RFC needed that says the same thing?) and b) has no
new substantive technical content, so I'm puzzled by that.

- If "Applications that use ucode take advantage of the Internet
extensively" is true, then what applications are those and why
are there no references to them?

- What is a "small user"?

(Russ Housley) No Objection

(Pete Resnick) No Objection

Comment (2012-02-13 for -)
No email
send info
Instead of creating a new hex-decimal, please use HEXDIG from RFC 5234.

(Robert Sparks) No Objection

(Sean Turner) No Objection