![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
\>> Should webarter away good current functionality because there's not an RFC for rsync?
Nope. I would hope that the RFC Editor would have an rsync server available. But that's different than mandating one when we can't really say what an rsync server is at any particular point in time (the protocol has changed over time).
I think that in a contractual situation, 'hope' isn't enough to keep us out of trouble.
Good point.
And I'd be reasonably happy if we specified 'any version of rsync greater than X.Y.Z', or some such. The current debian stable version (2.6.4-6) would work for me.
--Paul Hoffman, Director --VPN Consortium
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.