Re: [Uri-review] Request for review

Timothy Mcsweeney <tim@dropnumber.com> Wed, 11 November 2020 16:03 UTC

Return-Path: <tim@dropnumber.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2CB3A0DAB for <uri-review@ietfa.amsl.com>; Wed, 11 Nov 2020 08:03:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 yLB43mnFj-i4 for <uri-review@ietfa.amsl.com>; Wed, 11 Nov 2020 08:03:24 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 294503A0C8E for <uri-review@ietf.org>; Wed, 11 Nov 2020 08:03:24 -0800 (PST)
Received: from oxuslxaltgw03.schlund.de ([10.72.76.59]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0MWD5b-1koGRu16l7-00XGzA for <uri-review@ietf.org>; Wed, 11 Nov 2020 17:03:23 +0100
Date: Wed, 11 Nov 2020 11:03:22 -0500
From: Timothy Mcsweeney <tim@dropnumber.com>
To: uri-review@ietf.org
Message-ID: <1724424081.10216.1605110602967@email.ionos.com>
In-Reply-To: <1516971670.87548.1589903220738@email.ionos.com>
References: <491516506.246380.1589851279474@email.ionos.com> <f5by2poi7p2.fsf@ecclerig.inf.ed.ac.uk> <1516971670.87548.1589903220738@email.ionos.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.3-Rev26
X-Originating-Client: open-xchange-appsuite
X-Provags-ID: V03:K1:Tsv+vqdQu0CNsP9EfcfiGAGED8b+soznidbS5hBnlhh4FVJaqO1 sNdNeWTPumttds/iFGaioRpOOOFNNS9/2rpSJBPfTNeMLx06d8sdcSLmnmNnwOn1xMJepKo kVtoSG9ovtajacjwFFCbCjA2h05P9028Uigmz1dYw32k2DsIL37pQO1Uvf6z3r2HLSFS/01 Q2OKvIUVbTlRI/m7rZxfA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:4Hf4bnkN5Ws=:uel1oWAXnlLNLLXEhaYDQS 8PwEzZinaE+oYBdUa60WuQ9iUOgh+In6UBX3G2Ql23a4x0U0GczesmRskpNnCOW4sOMo4wTH6 BJe5a+W2Vt3jtfQxVU5cKXymIXyApU9Kpj8iq+NR2/Gi6bhgcqfCWevd7YO2xuIlWixpVtQSt 1NkqtuwKOx2B91w/MU7i+eD4S4THgjXCXWejdQIxOl99roZQoGpzR7B50c0+Q21pa14dEMorJ x+OEjAy3kWBbmrkhxZMMwRNRrqFjQ/Cm7jZ2Gvhz0CSdAM1sxhCvHJsl/UivEdoW7DFj+3uiP kXPzSfKA21Hd6CBrz/PmhHggwKpU3DhWrYUcbyTjNRJtMElydjYW2TC84SpsL0Aak+IRQrk1h tYAZtQ2IVcIvL4hw163MddZNbXfAXYeKbPqgtYXdDJ81lxDpe3aBzkm15GI4qCy8uvHrgNULi CVDiGEMfKA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/OohwpNhJbXRs1URFSyaNYbHWy0Y>
Subject: Re: [Uri-review] Request for review
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2020 16:03:26 -0000

text version:

Hi Henry,
I apologize for anything that was misleading as that was certainly not my intent. I will separate those two statements. The only similarity I wanted to point out was that 'tel' and 'leaptofrogans' use less than all five scheme components. Perhaps 'geo:' would have been a better example?

For the syntax, I wasn't sure exactly how much info was needed. I thought that only the scheme and path were required. Maybe I could change the reference to [RFC3986] section 2.2? If you think it would be better, should I write it out more like this?

path = / path-noscheme ; begins with a non-colon segment
          / path-rootless ; begins with a segment
          / path-empty ; zero characters

path-noscheme = segment-nz-nc *( "/" segment )
path-rootless = segment-nz *( "/" segment )
path-empty = 0<pchar>

segment = *pchar
segment-nz = 1*pchar
segment-nz-nc = 1*( unreserved / pct-encoded / sub-delims / "@" )
                       ; non-zero-length segment without any colon ":"

pchar =      unreserved / pct-encoded / sub-delims / ":" / "@"


Hi Martin,
I know at first glance it might look out of place but the #fg34htx part isn't a fragment. I think the "drop" part will be recognized as the scheme name because of its dereferencing.


> On 05/19/2020 11:47 AM Timothy Mcsweeney <tim@dropnumber.com> wrote:
> 
> 
> Hi Henry,
> I apologize for anything that was misleading as that was certainly not my intent. I will separate those two statements. The only similarity I wanted to point out was that 'tel' and 'leaptofrogans' use less than all five scheme components. Perhaps 'geo:' would have been a better example?
> 
> For the syntax, I wasn't sure exactly how much info was needed. I thought that only the scheme and path were required. Maybe I could change the reference to [RFC3986] section 2.2? If you think it would be better, should I write it out more like this?
> 
> path = / path-noscheme ; begins with a non-colon segment
> / path-rootless ; begins with a segment
> / path-empty ; zero characters
> 
> path-noscheme = segment-nz-nc *( "/" segment )
> path-rootless = segment-nz *( "/" segment )
> path-empty = 0<pchar>
> 
> segment = *pchar
> segment-nz = 1*pchar
> segment-nz-nc = 1*( unreserved / pct-encoded / sub-delims / "@" )
> ; non-zero-length segment without any colon ":"
> 
> pchar = unreserved / pct-encoded / sub-delims / ":" / "@"
> 
> 
> Hi Martin,
> I know at first glance it might look out of place but the #fg34htx part isn't a fragment. I think the "drop" part will be recognized as the scheme name because of its dereferencing.
> 
> 
> > On May 19, 2020 at 5:40 AM "Henry S. Thompson" < ht@inf.ed.ac.uk> wrote:
> > 
> > 
> > Timothy Mcsweeney writes:
> > 
> > > This is a request for a review of the 'drop' URI scheme. The
> > > draft can be found here
> > > https://datatracker.ietf.org/doc/draft-mcsweeney-drop-scheme/
> > Without commenting on any other aspect of the proposed scheme, and
> > mostly just to save people time, I found the following aspect of the
> > proposal somewhat misleading:
> > 
> > "Similar to the previously registered 'tel' [RFC3966] and
> > 'leaptofrogans' [RFC8589] URIs, the 'drop' URI scheme is
> > syntactically correct but does not need to use all 5 of the
> > parse-able components available to it. The 'drop' scheme uses the
> > number sign '#' as a general delimiter as seen in Appendix
> > A. Collected ABNF [RFC3986]. The scheme syntax is as follows:
> > 
> > " drop-uri = 'drop#' character string
> > 
> > drop # fg34htx
> > \__/ \_/ \_____/
> > | | |
> > <scheme> | <scheme-specific-part>
> > <gen-delim>
> > "
> > 
> > I read this as implying that
> > 
> > 1) 'tel' and 'leaptofrogans' URIs did not begin "tel:" and
> > "leaptofrogans:";
> > 2) The 3986 ABNF for URIs recognises "drop#fg34htx" as a URI.
> > 
> > Neither of these is in fact that case. The two referenced schemes
> > require ':' after the 'scheme' component, and the 'URI' production does
> > _not_ recognise the above example. (The 'URI-reference' production does,
> > but not using the 'scheme' production to cover the "drop" part.)
> > 
> > ht
> > --
> > Henry S. Thompson, School of Informatics, University of Edinburgh
> > 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
> > Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
> > URL: http://www.ltg.ed.ac.uk/~ht/
> > [mail from me _always_ has a .sig like this -- mail without it is forged spam]
> > 
> > The University of Edinburgh is a charitable body, registered in
> > Scotland, with registration number SC005336.
> > 
> > _______________________________________________
> > Uri-review mailing list
> > Uri-review@ietf.org
> > https://www.ietf.org/mailman/listinfo/uri-review