Re: letting IETF build on top of Open Source technology

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/30/17 2:03 PM, Russ Housley wrote:
> There was not a document that describes the rsync protocol.  The code
> has lots of comments, and it supports many versions.  The code is the
> real protocol definition.

I'd like to think that ultimately we'll be able to include
code or other non-IETF-standard material in normative
references, but I think there are some key issues not
addressed in the draft, particularly around the stability
of the reference.  I think that revision control systems
probably can be used to address some of that ("branch
<whatever> on date <whenever>") but stuff gets moved in and
out of repos all the time and it's difficult to guarantee
the stability of material under someone else's control.  So,
I expect the question of the quality of the reference itself
probably needs to be addressed in Section 2 of the draft.
It also might be worth distinguishing between the quality of
the reference and the quality of the material being referenced
(basically the same point).

Melinda

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]