The "about" URI Scheme
RFC 6694

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

Barry Leiba Yes

(Pete Resnick) (was Discuss) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Benoît Claise) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

Comment (2012-06-03 for -05)
No email
send info
I have no objection to the publication of this document as an
Informaitonal RFC.

Following on from the transition to Informational (for which, thanks),
you might consider s/specifies/describes/  (But this is a *very*
unimportant comment!)

(Stephen Farrell) No Objection

Comment (2012-06-04 for -06)
No email
send info
The FCFS registration scheme could lead to anyone
registering an about-token that's in current use in a 
browser. Why isn't expert review more suitable here to
protect against such abuse? For example, nothing 
here prevents me from registering about:config, which
is used by >1 browser. I don't get why that is not
a problem. (This is almost a discuss btw, I'd really like 
to see a response if possible before the telechat.)

Why does about-token "correspond" to hier-part from 3986?
What would "about://example.com/foo/bar" mean? I'd have
thought that omitting the authority would be correct for
this scheme - why am I wrong?

(Brian Haberman) No Objection

Comment (2012-05-16 for -04)
No email
send info
Just a non-blocking comment that can be resolved easily...

The Acknowledgments section appears to be incomplete.  The first sentence looks fragmented, maybe an editing mistake?

(Russ Housley) No Objection

(Robert Sparks) No Objection

(Martin Stiemerling) No Objection

Comment (2012-06-04 for -06)
No email
send info
no objection if this draft is really going for informational (as listed in the draft) and not as Standards Track as listed in the datatracker.

(Sean Turner) (was Discuss) No Objection

Comment (2012-06-05 for -06)
No email
send info
I have no objection to the publication of this document as an Informational RFC.