Re: [apps-discuss] Retroactive application of draft-ietf-appsawg-uri-scheme-reg - comprehensive review

Barry Leiba <barryleiba@computer.org> Fri, 10 April 2015 15:38 UTC

Return-Path: <barryleiba@gmail.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 089DC1A1B0B; Fri, 10 Apr 2015 08:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 fGAXi8DtqISm; Fri, 10 Apr 2015 08:38:12 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E9CF1A1A79; Fri, 10 Apr 2015 08:38:12 -0700 (PDT)
Received: by iejt8 with SMTP id t8so20364255iej.2; Fri, 10 Apr 2015 08:38:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=6PBQOZbK4GYsAyND5wNjjMIKFSTMlUxwk3b9gTdGeTc=; b=CG8BLXTHzAw860LKXZoBow1Y0V2ZGBG4DnUB/hed+tucnsqVb6olGIwHeK3AgLD/D7 lXH/czsFGXnRA1kJhn9ZRaBSHoU7zOW6yh3q5Sh8ZD/Uy+IAPwSuP2OWPCV4MQ147Z2u 7/8vvO0chq+0vF4XGR+e9QFxUsfI3u0I+svg8aiINrnGeFdUDOYaItD3t+Dfj47V03vV 96oCYDcLlSp5XNZk7Kr4dZ89iRMObC0y6z0xo+GAw7KTF08sqDqnFiHgX/f+IIkM79Pq gwMewaQE71HmGqrnmcYOm0nOO4yh2lrqCrxaIqAeukHmq0+G7gF1LFmjiFjIJo8AO5wk UKFA==
MIME-Version: 1.0
X-Received: by 10.50.35.195 with SMTP id k3mr29699341igj.11.1428680291518; Fri, 10 Apr 2015 08:38:11 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.107.7.130 with HTTP; Fri, 10 Apr 2015 08:38:11 -0700 (PDT)
In-Reply-To: <CA288E99-DE72-4DCF-9BD5-822A9C8F41F9@gbiv.com>
References: <2E49FA112B054FFAED69D8A1@JcK-HP8200.jck.com> <CALaySJ+JdE5YrBuXv343_CfNP4mYxOR94JV4q_Uso4VoWfD=Ng@mail.gmail.com> <723FBC93979E1019101319C5@JcK-HP8200.jck.com> <4EA0B2F8-5109-49EA-8BAF-0199D1640407@gbiv.com> <55274198.5030309@andyet.net> <CA288E99-DE72-4DCF-9BD5-822A9C8F41F9@gbiv.com>
Date: Fri, 10 Apr 2015 11:38:11 -0400
X-Google-Sender-Auth: 2HHJV-Tc3vxlZei49HezJJXCLbQ
Message-ID: <CALaySJJZsCuQHUSMFULfH33ke63_Xrka8OMft2Dp0NPJNKLF5w@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Roy T. Fielding" <fielding@gbiv.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/CbZZAEfEaFzF3fEf3-vhZ9jlSKE>
Cc: Apps Discuss <apps-discuss@ietf.org>, "draft-ietf-appsawg-uri-scheme-reg.all@ietf.org" <draft-ietf-appsawg-uri-scheme-reg.all@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [apps-discuss] Retroactive application of draft-ietf-appsawg-uri-scheme-reg - comprehensive review
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: Fri, 10 Apr 2015 15:38:13 -0000

> No scheme can prohibit fragments. They are not part of the scheme's syntax.

We continue to have a confusion between syntax and semantics here.

I absolutely agree that no scheme can say that fragments are
syntactically invalid, because the schemes do not control the syntax
of a URI.

But a scheme can certainly say that fragments make no semantic sense
within that scheme, and that if a URIs uses that scheme and contains a
fragment, it is not a well formed URI within that scheme.

It's rather like saying that English words are composed of characters
from the set "abcdefghijklmnopqrstuvwxyz", and, therefore, the string
"qwx" is a valid piece of an English word (syntax)... but that, in
fact, no valid English words contain "qwx" (semantics).

That's not a layering violation at all -- it has to be up to the
scheme to say what the semantic meaning of a fragment is within that
scheme, or whether fragments have any meaning at all.

Barry