Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC)
RFC 6338

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

(Peter Saint-Andre) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

(Stephen Farrell) No Objection

Comment (2011-05-21 for -)
No email
send info
(1) Some examples would be nice.

(2) https://urnreg.terena.org/ doesn't seem to currently have anything very human readable.
Be good to fix that before the RFC issues.

(Russ Housley) (was Discuss) No Objection

(Pete Resnick) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection

Comment (2011-05-20 for -)
No email
send info
#1) I followed the MACE link and got a 404 error.  Maybe this one instead:
http://middleware.internet2.edu/urn-mace/
or you could point to RFC 3613?

#2) Sec 2:  I compared the SCHAC-NSS and MACE-NSS.  The only difference is as follows:

MACE-NSS        =   1*(subStChar) 0*(":" 1*(subStChar))

SCHAC-NSS    =   1*subStChar *( ":" 1*subStChar )

I assume they evaluate to the same thing?

#3) A couple of nits on the last paragraph of Section 3:

   ... sites offering credentials signed by a community recognised
                                             ^ SCHAC-community
   Certificate Authority (CA) and that WILL require the latest secure
             ^ion                      ^^^^will
   methods for accessing a web site, that currently being HTTP [11] over
   the latest version of TLS [12].

Normally, I'd say point to RFC 2818 for HTTP over TLS (i.e., HTTPS), but I guess you might be trying to make people use TLS 1.2?  What about the following:

   In order to guarantee the validity and origin of SCHAC-NSS URN
   values, they MUST be published over https links [11].  The https links
   MUST be secured by sites offering credentials signed by a SHAC-community
   recognised Certification Authority (CA) using the latest secure
   methods for accessing a web site, that currently being the latest
   version of TLS [12].

Replace [11] with 2818 instead of 2616 because 2818 points to 2616.

#4) Because of the MUST(s) in the last paragraph references [11] and [12] are now normative.