Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC

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

Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC

From: Paul Hoffman <paul.hoffman at vpnc.org>
To: Ted Hardie <ted.ietf at gmail.com>, Russ Housley <housley at vigilsec.com>
Cc: ietf at ietf.org
Date: Wed, 30 Sep 2009 18:33:14 -0700
In-reply-to: <6e04e83a0909301641w4f89a22ft8bb61eb58b650476 at mail.gmail.com>
References: <20090930143140.4502D3A6977 at core3.amsl.com> <6e04e83a0909301218y4be199fu3848861829984ab at mail.gmail.com> <20090930195139.D6193F2404F at odin.smetech.net> <6e04e83a0909301641w4f89a22ft8bb61eb58b650476 at mail.gmail.com>

At 4:41 PM -0700 9/30/09, Ted Hardie wrote:
>Fair enough; thanks for the explanation.  I think adding something to
>the IANA considerations documenting that logic couldn't hurt, e.g:
>
>"A provisional registration is being sought as there is no citable
>rsync protocol specification at this time, despite its widespread
>deployment".

+1

--Paul Hoffman, Director
--VPN Consortium

References:
- Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC
  - From: Ted Hardie
- Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC
  - From: Russ Housley
- Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC
  - From: Ted Hardie

Prev by Date: Re: Request for community guidance on issue concerning a future meeting of the IETF
Next by Date: Re: Last Call: draft-ietf-idnabis-bidi (Right-to-left scripts for IDNA) to Draft Standard
Previous by thread: Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC
Next by thread: Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.