The rsync URI Scheme
draft-weiler-rsync-uri-01
Yes
No Objection
Recuse
Note: This ballot was opened for revision 01 and is now closed.
Lars Eggert No Objection
(Jari Arkko; former steering group member) Yes
(Ross Callon; former steering group member) Yes
(Adrian Farrel; former steering group member) No Objection
I commend the brevity of this I-D. The Abstract is, however, very terse. http://www.ietf.org/id-info/guidelines.html says... An Abstract will typically be 5-10 lines, but an Abstract of more than 20 lines or less than 3 lines is generally not acceptable. How about adding... An rsync URI describes a source or destination for the rsync application including a hostname, path, and optional user and port. --- There are several mentions of "the rsync application." While "we all know what resync is", it would be nice to include a couple of lines to say what it is.
(Alexey Melnikov; former steering group member) (was Discuss) No Objection
Nit: This is missing a normative reference to RFC 5234 (ABNF). Otherwise this looks good to me.
(Cullen Jennings; former steering group member) No Objection
(Dan Romascanu; former steering group member) No Objection
(Lisa Dusseault; former steering group member) No Objection
I agree with Pasi about specifying transports.
(Magnus Westerlund; former steering group member) No Objection
(Pasi Eronen; former steering group member) (was Discuss) No Objection
(Ralph Droms; former steering group member) No Objection
In section 2, should "rsyncurl" be "rsyncuri" ?
(Robert Sparks; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Tim Polk; former steering group member) (was No Record, Discuss) No Objection
(Russ Housley; former steering group member) Recuse