Re: [core] [Last-Call] Iotdir telechat review of draft-ietf-core-dev-urn-09
Russ Housley <housley@vigilsec.com> Thu, 07 January 2021 13:39 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60ADF3A1168 for <core@ietfa.amsl.com>; Thu, 7 Jan 2021 05:39:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable 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 1xf9U0EczZfd for <core@ietfa.amsl.com>; Thu, 7 Jan 2021 05:39:24 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EC9D3A1108 for <core@ietf.org>; Thu, 7 Jan 2021 05:39:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A6EF5300BD1 for <core@ietf.org>; Thu, 7 Jan 2021 08:33:14 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YvaPkB7iWYBl for <core@ietf.org>; Thu, 7 Jan 2021 08:33:12 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 505C8300AE5; Thu, 7 Jan 2021 08:33:12 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CALaySJLQwa-yAR74qUGwFPo7JidGvCThsJHwuWSnx8gNr9n=9A@mail.gmail.com>
Date: Thu, 07 Jan 2021 08:33:13 -0500
Cc: "iot-directorate@ietf.org" <iot-directorate@ietf.org>, draft-ietf-core-dev-urn.all@ietf.org, core WG <core@ietf.org>, last-call@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6E40C4E-B763-4B52-B97E-DF02D46520E7@vigilsec.com>
References: <160996930502.21827.5533521556349871834@ietfa.amsl.com> <CALaySJKKEgPRzkG18QAyOutGHO93zP=Hm2bBaF0qvE5j7r_dYw@mail.gmail.com> <A1152BE4-410F-4E2B-884D-DD5E62129122@vigilsec.com> <CALaySJLQwa-yAR74qUGwFPo7JidGvCThsJHwuWSnx8gNr9n=9A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/nH_Su6D31RYki-JUU17SxRWPL7o>
Subject: Re: [core] [Last-Call] Iotdir telechat review of draft-ietf-core-dev-urn-09
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 13:39:29 -0000
Barry: >> You are, of course, correct. RFC 5234 says: >> >> ABNF strings are case insensitive and the character set for these >> strings is US-ASCII. >> >> However, that raises a different issue: >> >> The DEV URN syntax allows both upper and lower case characters. The >> URN-equivalence of the DEV URNs is defined per [RFC8141] Section 3.1, >> i.e,. two URNs are URN-equivalent if their assigned-name portions are >> octet-by-octet equal after applying case normalization to the URI >> scheme ("urn") and namespace identifier ("dev"). >> >> So, the ABNF should be changed so that the "mac:", "ow:", "org:", "os:", and "ops:" are required to >> be lowercase. I guess that means replacing each letter with the appropriate value in the %x61-7A >> range. That will not be as easy to read... > > Not if it's done that way, indeed. But RFC 7405 helps us here. Indeed, I forgot about RFC 7405. Much better solution. Russ
- [core] Iotdir telechat review of draft-ietf-core-… Russ Housley via Datatracker
- Re: [core] Iotdir telechat review of draft-ietf-c… Barry Leiba
- Re: [core] [Last-Call] Iotdir telechat review of … John C Klensin
- Re: [core] [Last-Call] Iotdir telechat review of … Martin J. Dürst
- Re: [core] [Last-Call] Iotdir telechat review of … Russ Housley
- Re: [core] [Last-Call] Iotdir telechat review of … Barry Leiba
- Re: [core] [Last-Call] Iotdir telechat review of … Russ Housley
- Re: [core] Iotdir telechat review of draft-ietf-c… Jari Arkko
- Re: [core] [Last-Call] Iotdir telechat review of … Russ Housley
- Re: [core] [Last-Call] Iotdir telechat review of … Jari Arkko
- Re: [core] [Last-Call] Iotdir telechat review of … Jari Arkko
- Re: [core] [Last-Call] Iotdir telechat review of … Russ Housley
- Re: [core] [Last-Call] Iotdir telechat review of … John C Klensin
- Re: [core] [Last-Call] Iotdir telechat review of … Jari Arkko
- Re: [core] [Last-Call] Iotdir telechat review of … Carsten Bormann
- Re: [core] [Last-Call] Iotdir telechat review of … Jari Arkko
- Re: [core] [Last-Call] Iotdir telechat review of … Russ Housley