IETF Logo Mail Archive

Re: [urn] Alissa Cooper's Discuss on draft-ietf-urnbis-rfc2141bis-urn-21: (with DISCUSS and COMMENT)

Julian Reschke <julian.reschke@gmx.de> Thu, 02 March 2017 07:07 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29B0A1294A0; Wed, 1 Mar 2017 23:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 FxmsMNVlb73D; Wed, 1 Mar 2017 23:07:39 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 994591294A8; Wed, 1 Mar 2017 23:07:38 -0800 (PST)
Received: from [192.168.178.20] ([93.217.107.91]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M1iGk-1cTBr80uza-00ti6C; Thu, 02 Mar 2017 08:07:20 +0100
To: John C Klensin <john-ietf@jck.com>, Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
References: <148838107824.7093.11755371556465062472.idtracker@ietfa.amsl.com> <E1B86D7B58E7FBAABCAE9FD9@PSB>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <83e9152f-3ed1-6806-1861-45a7ee48f132@gmx.de>
Date: Thu, 02 Mar 2017 08:07:19 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <E1B86D7B58E7FBAABCAE9FD9@PSB>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:qtp9SvdUUDv+YnMFljvlk4h4oMCxQ9dGUw2imVlib/2QFS9hw3h sJ68lrlI6fpcHkhwW2vEcxzrCBStLhFiJTmJ5SlZIwR2syhjx/OJQzC2ZgfHV4/BxPOZFU5 BRaDdTYbaCK2biu+TgUmnwbB1pxaF7ApkkLUFM8s+PjOMCiYrAy3BL7msG78BMIOnKjs1mb DtN+AiO8LC7r7yTyoiK7Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:UGwtyC49Ty0=:CXH3RnAjUz7ax6HIvAqjOq m7n/VizvuVEgEz3eKf5BDSK6KMfmc6Z3dS8itjJbAcN2v0N1EdFUEqAtmp8YtHW2Ej1OGlmtm KlGY5rwY3dvSMgkQL/FcXwBwwAQSHsa8oRwzvelVCA3aphn0w57CIlFAwtvntE0LNqI1Tiu3Q CVw0q+AWMCSKB4cU9hlAC6xgJwHbEI3jOTgKJnCGNJpsMF7SzbnK6O/MolA9cQABzeaJdw3lq HCt0isgk5DsUSDZ/XsLMXCaEVNyF3vUZmQcsEndHjs6Hhuzf4uxgQbNNnXsKduydvA9U6pIdi A4ug5vw/1359HilmlxTA6sq7CHIlG+sj7+xEkzfRNN6Qegrfh1E/nT/7ixH43iL0zbMhmafey eGYf6+bfPBecBIMD1g1cuj+AJm93LP10dvtRNFE/xvu7HSx1LeBAeHjNySvxD2W3lySFU9Erd RBJfF1hr90OD/XEsZhQmwVseCnpd4GX1+Qm4NXT/tO0g1leplkQM2VZOFU4izf4Z9pQopl6NA 1bSQQ0OVBMgEbtn4MNZEYZSvjQq6FFtX9m6YTD2VEg7HAV0kQYAOLUguyADVxzVanwwog/K+6 M9zyRUPLfiCaVQnyJhTu4StMHUp8tVzPKmCJRgNhFTkKzIfnntiDW1uOIhmGp5xxrjKa+hkVE uH2McWgFIQ8KCe6mMvmlo7Sz/mW54fqOYORTCRLOTRvDkWK7PGPZr58iQRTvndjObcwvGRILR sY9z5qGlimEuZI0maEd2uKqlAi67AYYPeLoVgX5g1WSC2hEkRqpOWZbzk65wenCSAtc8c9xjT eszc2CR
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/MADN6HGdrqbgPLJAO1vTXAzg2m0>
Cc: urn@ietf.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org, barryleiba@computer.org
Subject: Re: [urn] Alissa Cooper's Discuss on draft-ietf-urnbis-rfc2141bis-urn-21: (with DISCUSS and COMMENT)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Mar 2017 07:07:40 -0000

On 2017-03-02 03:18, John C Klensin wrote:
> ...
> That problem is that the predecessors of RFC 3986 established a
> generic, and quite prescriptive, syntax for URLs.  RFC 3986
> expanded that to cover all URIs, arguably including URNs without
> fully understanding the implications of that expansion.  The
> result is that almost anything one puts in a URI either means
> something, is part of some specific component, or both.
> ...

Actually, that happened with RFC 2396 in August 1998.

> ...

Best regards, Julian

v2.23.0 | Report a Bug | By Email