- From: Graham Klyne <gk@ninebynine.org>
- Date: Mon, 22 Dec 2014 13:28:38 +0000
- To: Sam Ruby <rubys@intertwingly.net>, Mark Nottingham <mnot@mnot.net>, Larry Masinter <masinter@adobe.com>
- CC: "public-ietf-w3c@w3.org" <public-ietf-w3c@w3.org>, Wendy Seltzer <wseltzer@w3.org>, Philippe Le Hégaret <plh@w3.org>, Barry Leiba <barryleiba@computer.org>, Pete Resnick <presnick@qualcomm.com>, Daniel Appelquist <appelquist@gmail.com>
On 21/12/2014 21:10, Sam Ruby wrote: > Building a specification that obsoletes RFC 3986 as well as RFC 3987 is > lower risk and less work than updating RFC 3986 and/or RFC 3987 and then > updating the URL Living standard based on this work; all in the hopes that parts > of the results might be picked up at some later point by the IETF. I'll repeat pretty much what I've said before. I haven't seen any indication of anything that's actually wrong or unworkable in RFC3986. As such, I'm unconvinced that it needs updating *or* obsoleting. #g --
Received on Monday, 22 December 2014 13:29:17 UTC