A Profile for Resource Certificate Repository Structure
RFC 6481

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

(Ron Bonica) Yes

(Stewart Bryant) Yes

(Jari Arkko) No Objection

(Gonzalo Camarillo) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) (was Discuss) No Objection

Comment (2011-07-28)
No email
send info
All Comments and Discuss resolved

(Stephen Farrell) No Objection

Comment (2011-07-13 for -)
No email
send info
(1) Including examples for all the recommended names would be a real
help for implementers and shouldn't be too hard if someone has code
already. I'd really like to see that added. 

(2) Did the WG consider specifying that repositories MAY or SHOULD
contain a README-like file informally describing the content of the
repository. It might be good to have a well-defined place for that kind
of information.

(David Harrington) No Objection

(Russ Housley) No Objection

(Pete Resnick) (was Discuss) No Objection

(Dan Romascanu) No Objection

(Peter Saint-Andre) (was Discuss) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection

Comment (2011-07-13 for -)
No email
send info
Please make the following changes to Section 3:

OLD:

   The publication repository MUST be available using RSYNC [RFC5781].

NEW:

The publication repository MUST be available using RSYNC [RFC5781][RSYNC].


And the following normative reference:

   [RSYNC]    Tridgell, A., "rsync", March 2008,
              <http://rsync.samba.org/>

This will line it up with the arch document.