Re: [apps-discuss] Scope of RFC3986 and successor - what is a URI?

mike amundsen <mamund@yahoo.com> Sat, 17 January 2015 19:58 UTC

Return-Path: <mamund@yahoo.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21E751ACECB for <apps-discuss@ietfa.amsl.com>; Sat, 17 Jan 2015 11:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.787
X-Spam-Level:
X-Spam-Status: No, score=-0.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMmK9FiV1dfE for <apps-discuss@ietfa.amsl.com>; Sat, 17 Jan 2015 11:58:45 -0800 (PST)
Received: from nm17-vm6.bullet.mail.ne1.yahoo.com (nm17-vm6.bullet.mail.ne1.yahoo.com [98.138.91.110]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A0FD1ACD82 for <apps-discuss@ietf.org>; Sat, 17 Jan 2015 11:58:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1421524724; bh=XoDtVWzN6s4n9nI2zD+iErMxmbaTL20+0/UpgBI/jP0=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From:Subject; b=rUBRrVEXayYScIon5vaQXy7Z7X2w7NE74s6qcnRExcMVhBwVlt8vxaicLdRER3YmoDw4myquUUSwPWFpKI3ltyeDAZqi7Rw+GToeQd0YKfAEpgK6Q7LirLFXuXZRCq0GwjgAdwjlTi+fEp5DhgUSdD0X0KZhj6pN1d71MMoIIeK94uVTvVCsC+c8ziC0+/vf8gR/VGyUdirR4UoxEhHymk952sixNodWF8vLioVC8GPWaUvYUt94k4v1vMopnxvhDTGeGDpW09vi1Dq8zKTlgzyS5Nva0gIowOqCiwTeQYGz2bkP5OwXJCm9q0JuTMzjp4efNpU/CZEgAZ11uGgC5g==
Received: from [98.138.100.102] by nm17.bullet.mail.ne1.yahoo.com with NNFMP; 17 Jan 2015 19:58:44 -0000
Received: from [98.138.104.116] by tm101.bullet.mail.ne1.yahoo.com with NNFMP; 17 Jan 2015 19:58:44 -0000
Received: from [127.0.0.1] by smtp225.mail.ne1.yahoo.com with NNFMP; 17 Jan 2015 19:58:44 -0000
X-Yahoo-Newman-Id: 724084.1038.bm@smtp225.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: S7P8FmcVM1m2r97S8wYMib39y7PcyEUyjaxVMZhnBCwBRjp 30kykaCUUdcbMSkpuAxsrQgxrLrLw2M2LR_b_MLB1iPkENLa_e24.CBaiRvz _Ngls7aaqZMwBnJchtjq50od9dY9yBkYCQgIVP2a20E72MfXb9kD23_c5cg1 NMh8fEb7Xpr_V72KEGP526kvxnkv6O9owlJTdMWWVp42rnilL11WniJxJTsl 0LbMj25wJ4SVkc4ObTexz1lXgwhWNuLk02Xfg5KdvtBuia.N7tra2lp3m8nS i6Lt0VuAdyJcEeNUBgFCA2SHSz1.0Tnht8JMPCoOyOBms2V8OBwOMcXNDujw kYkYzOcxJcJ6v2OIzWRYcj1k0JWGMoQIxE_67HhVphwfXOEk6hX86E0lLfkg cbjWETLr6_ETJdCp389Neuy3sRDpnWGg6p7WZJEZAkUtaBN34Up.ZBjekX0T mW2GVkpm_VXzLBBNFQIkUtbn9WivnlWBvXNLOcUDHb29nSI_BFW8yrn0wEi2 hv0oqP6SUFHAau4fQAR2sLEUT.6Tl.J3B9VsjEaoGOT2uXLXIfDd1yAKbYFG AuQkjoHL89SfavE5Ww3EX2SAslCBetHwrSggX8kUtdsYd9yXZf5s4kgc8ouL OSL2p9Rh0NO.RXHuyoSZ9HWGE4dQC2mWHtVBKHYp73FVxKkKk5QGNp4Q0jhM Uf2FZM.0cIgP6OJg2n7NbIjvd3FjWNt1z6WBJGcMHEnWJK6145HV2OQwhmOT OYtOxdWiWyA--
X-Yahoo-SMTP: i12ABOmswBAkPG1PnjmsmmFRWA--
Received: by mail-lb0-f169.google.com with SMTP id f15so2501966lbj.0 for <apps-discuss@ietf.org>; Sat, 17 Jan 2015 11:58:42 -0800 (PST)
X-Gm-Message-State: ALoCoQmUryMVvWhFVFoXvXQ/+oV8TnEaH04lq4PLsKUrVJZX740yjPIKUcsOzY5Y1yJqpW+qLbTV
X-Received: by 10.112.156.169 with SMTP id wf9mr21810163lbb.85.1421524722458; Sat, 17 Jan 2015 11:58:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.166.203 with HTTP; Sat, 17 Jan 2015 11:58:21 -0800 (PST)
In-Reply-To: <54BAB143.1080006@intertwingly.net>
References: <20140926010029.26660.82167.idtracker@ietfa.amsl.com> <54B18B61.8010308@seantek.com> <54B19435.8070401@intertwingly.net> <54B1B211.3050807@seantek.com> <54B1B682.3070609@intertwingly.net> <012001d02d91$6ec42300$4001a8c0@gateway.2wire.net> <54B2781C.4040505@intertwingly.net> <018e01d02dc6$1d03b0a0$4001a8c0@gateway.2wire.net> <54B2CC75.5080900@intertwingly.net> <54B79930.3070009@ninebynine.org> <54B7AEC2.9010109@intertwingly.net> <CAKHUCzz=jZAF-i2_pwGpkER5vNhv95CMwdBCMwigPJ0FA_t4_A@mail.gmail.com> <54B7BD4A.1090803@intertwingly.net> <54B7CF28.7060408@gmx.de> <54B7D605.2060307@intertwingly.net> <f5boaq0gdw5.fsf@troutbeck.inf.ed.ac.uk> <54B806A2.8020803@intertwingly.net> <CAKHUCzzN4Eu6R_f2Sf8EtiAp-8w3ds5Yp3-PBHK+B0wGRxEtmw@mail.gmail.com> <54b9381b.8ca1e00a.243f.ffffcae4@mx.google.com> <98A81DE7-1845-46EC-A3EB-F00438863ECB@seantek.com> <54B93F2A.5070900@intertwingly.net> <54BA7EE2.1040102@ninebynine.org> <54BAB143.1080006@intertwingly.net>
From: mike amundsen <mamund@yahoo.com>
Date: Sat, 17 Jan 2015 14:58:21 -0500
Message-ID: <CAPW_8m6ju6QFmp_pvby72KXYAyOCOVOvhbf9VfP384=5QKFwUA@mail.gmail.com>
To: Sam Ruby <rubys@intertwingly.net>
Content-Type: multipart/alternative; boundary="001a11c240b01f3e6e050cde84af"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/TRqwRAGmdNeHrwGsLuNxoT3tQWo>
Cc: Graham Klyne <gk@ninebynine.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Scope of RFC3986 and successor - what is a URI?
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Jan 2015 19:58:47 -0000

Sam:

i might be missing some key points but..

<snip>
What is effectively being said is that documenting how things actually work
will break things, which is clearly untrue.
</snip>

let's not confuse "changing the specification" with "documenting."
 documenting NEVER breaks things. changing a specification MAY break things.

if all this is about is writing *documentation*, have at it. if you want to
write some BCPs, no worries.

but if the work involves changing specifications, as long as those changes
are made in ways that do not break existing *spec-compliant*
implementations, i have no problem with the work.

changing shared specs to match one or more existing non-compliant
implementations is rarely the right approach.



mamund
+1.859.757.1449
skype: mca.amundsen
http://amundsen.com/blog/
http://twitter.com/mamund
https://github.com/mamund
http://linkedin.com/in/mamund

On Sat, Jan 17, 2015 at 2:00 PM, Sam Ruby <rubys@intertwingly.net> wrote:

> On 01/17/2015 10:25 AM, Graham Klyne wrote:
>
>> On 16/01/2015 16:41, Sam Ruby wrote:
>>
>>> As to what the breakage it, that is less clear to me.  There are existing
>>> parsers that don't percent encode square brackets when they occur at
>>> some point
>>> after a question mark is encountered in the input. Perhaps those
>>> parsers lose
>>> the ability to claim that they are "RFC 3986 compliant".
>>>
>>
>> Surely, it's not the role of a *parser* to %-encode, but a *generator*
>> of URIs?
>>
>> The primary role of a URI parser is to simply decide if a given string
>> is or is not a valid URI.  A parser can only be RFC3986-compliant in the
>> extent to which it correctly makes this determination in accordance with
>> RFC3986.  Of course, parsers may do more than this, but the detail of
>> such behaviour is not specified by RFC3986.
>>
>> (I would say that a *generator* of URIs that does not %-encode square
>> brackets in fragments is not RFC3986 compliant.)
>>
>
> As many people have pointed out, nomenclature seems to be a big problem
> here.  I started to write a reply that spells this out, but I realized that
> I was repeating things that I've said before, and figured it made sense to
> pull it out into a separate blog post that I can point to:
>
> http://intertwingly.net/blog/2015/01/17/RFC-3986bis
>
> TL;DR: URL parsers consume URLs and generate URIs.  Such URIs are not RFC
> 3986 complaint.  I’d like to fix that.
>
>  #g
>> --
>>
>
> - Sam Ruby
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>