RE: two-week review: registering formal "rdns" NID

"Ing-Wher (Helen) Chen" <ichen@kuatrotech.com> Mon, 22 February 2016 22:37 UTC

Return-Path: <ichen@kuatrotech.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8904D1A90C1 for <urn-nid@ietfa.amsl.com>; Mon, 22 Feb 2016 14:37:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 AuI5ows_FnnV for <urn-nid@ietfa.amsl.com>; Mon, 22 Feb 2016 14:37:45 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0073.outbound.protection.outlook.com [104.47.2.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D1431A90A5 for <urn-nid@apps.ietf.org>; Mon, 22 Feb 2016 14:37:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kuatrotechnology.onmicrosoft.com; s=selector1-kuatrotech-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=9I7CJhzQ8qCLkdTLUoz44hZlGOUwQ4B7Lnw/G7fpCvE=; b=IChEAmzl7m6xmLobMXCePzY7fCRgtPUCY5JMTLs8fzv/XChPekoguRaDl/vHL8yMwWa2gXv6H9Sn8byjoOPd3efs2mqQzOq+oF+hmK75jiibPgN07GOWNsxQ3ecVxI9x/vfqDqyU890gAa+/ei4ElSS967astw4VkSOof0+hD+8=
Received: from DB5PR06MB0950.eurprd06.prod.outlook.com (10.162.158.140) by DB5PR06MB0952.eurprd06.prod.outlook.com (10.162.158.142) with Microsoft SMTP Server (TLS) id 15.1.409.15; Mon, 22 Feb 2016 22:37:41 +0000
Received: from DB5PR06MB0950.eurprd06.prod.outlook.com ([10.162.158.140]) by DB5PR06MB0950.eurprd06.prod.outlook.com ([10.162.158.140]) with mapi id 15.01.0409.024; Mon, 22 Feb 2016 22:37:41 +0000
From: "Ing-Wher (Helen) Chen" <ichen@kuatrotech.com>
To: =?utf-8?B?TWFydGluIEouIETDvHJzdA==?= <duerst@it.aoyama.ac.jp>, "Dale R. Worley" <worley@ariadne.com>
Subject: RE: two-week review: registering formal "rdns" NID
Thread-Topic: two-week review: registering formal "rdns" NID
Thread-Index: AQHRa1XjvFkAZYJ8RqaIjpDWt7hu+Z80UhKAgARZzSA=
Date: Mon, 22 Feb 2016 22:37:40 +0000
Message-ID: <DB5PR06MB0950DFEA65B217BD9F04849FD0A30@DB5PR06MB0950.eurprd06.prod.outlook.com>
References: <87povsmo0e.fsf@hobgoblin.ariadne.com> <56C7E6C5.3030306@it.aoyama.ac.jp>
In-Reply-To: <56C7E6C5.3030306@it.aoyama.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: it.aoyama.ac.jp; dkim=none (message not signed) header.d=none;it.aoyama.ac.jp; dmarc=none action=none header.from=kuatrotech.com;
x-originating-ip: [98.191.72.170]
x-microsoft-exchange-diagnostics: 1; DB5PR06MB0952; 5:0LHE+0iTLVyasTeJuE3H/B5fuxKZipNdRKGT7UlRp6IJtby/HyxBc47dDEa5vU4tXz2o+qDpCTzvbW7A0vmo9xGvuS6JivqMk9eePG0m1AouHwM2ZbnZC7ukrSZLt7biiTGyuZ7jmIVdbLMdZceJfg==; 24:vzMkryBMCYJYOKfs2k4MH8/FbDx6DQAoG+Z1EqqZ1cOgbOGofwkdflh/ozQloVndhcBSpz8UBMb0R4wuM+COpUl5Tv4uuuxMFrwjPxhD410=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR06MB0952;
x-ms-office365-filtering-correlation-id: 8cd1acce-5dae-49e2-a3d3-08d33bd8c617
x-microsoft-antispam-prvs: <DB5PR06MB09524778E8BE6486CDB083FED0A30@DB5PR06MB0952.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:DB5PR06MB0952; BCL:0; PCL:0; RULEID:; SRVR:DB5PR06MB0952;
x-forefront-prvs: 0860FE717F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(43544003)(479174004)(164054003)(52604005)(13464003)(377454003)(87936001)(102836003)(50986999)(3846002)(54356999)(76176999)(11100500001)(189998001)(5001960100002)(106116001)(76576001)(5004730100002)(5002640100001)(5003600100002)(5008740100001)(2906002)(586003)(1096002)(4326007)(1220700001)(66066001)(74316001)(15975445007)(6116002)(3660700001)(3280700002)(92566002)(2900100001)(86362001)(2950100001)(10400500002)(40100003)(122556002)(33656002)(19580405001)(77096005)(19580395003)(5001770100001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB5PR06MB0952; H:DB5PR06MB0950.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: kuatrotech.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Feb 2016 22:37:40.8815 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 99314f4e-50ab-4d4e-a9c6-b21b0c887384
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR06MB0952
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/UgfKVlPS87x-1j2juHI8jLHdmAY>
Cc: "urn-nid@apps.ietf.org" <urn-nid@apps.ietf.org>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 22:37:47 -0000

Hi Martin and Dale,

Thanks for pointing out that "urn:rdns" should be case insensitive.
I've updated the section on "Rules for Lexical Equivalent".

URL:            https://www.ietf.org/internet-drafts/draft-chen-rdns-urn-03.txt
Status:         https://datatracker.ietf.org/doc/draft-chen-rdns-urn/
Htmlized:       https://tools.ietf.org/html/draft-chen-rdns-urn-03
Diff:           https://www.ietf.org/rfcdiff?url2=draft-chen-rdns-urn-03

Thanks,
Helen

> -----Original Message-----
> From: Martin J. Dürst [mailto:duerst@it.aoyama.ac.jp]
> Sent: Friday, February 19, 2016 11:09 PM
> To: Dale R. Worley <worley@ariadne.com>om>; Ing-Wher (Helen) Chen
> <ichen@kuatrotech.com>
> Cc: urn-nid@apps.ietf.org
> Subject: Re: two-week review: registering formal "rdns" NID
> 
> Hello Dale, Helen, others,
> 
> Indeed as Dale says, the "urn" and "rdns" components are case-insensitive,
> and a namespace registration cannot change that.
> 
> Regards,   Martin.
> 
> On 2016/02/20 05:41, Dale R. Worley wrote:
> > Comments on draft-chen-rdns-urn-02:
> >
> > "Ing-Wher (Helen) Chen" <ichen@kuatrotech.com> writes:
> >>> Comments on draft-chen-rdns-urn-00:
> >>
> >> [Helen]  Just a note that at the time that I submitted to
> >>                 urn-nid@apps.ietf.org for review, the latest version was -01.
> >
> > I should have noticed that!
> >
> > I think your changes take care of the problems that I've noticed.
> >
> >>> The rule for lexical equivalence can't be implemented because there
> >>> is no algorithm for parsing an "rdns" URN into <reverse-dns> and
> >>> <dss>, and the lexical equivalence rule specifies that <reverse-dns>
> >>> is case-insensitive and <dss> is case-sensitive (as far as I can tell; you
> should update the wording).
> >>
> >> [Helen]  I updated the section on "Rules for Lexical Equivalence".  On
> second
> >>                 thought, because "rdns" URNs are meant to be XML
> >>                 namespaces of enterprise YANG modules, I think the
> >>                 rules for lexical equivalence for "rdns" URNs should be
> >>                 as defined for those of XML namespaces.
> >
> > There might be a problem, as RFC 2141 prescribes that "urn" and the
> > NID
> > ("rdns") are case-insensitive, whereas the draft prescribes that all
> > of the URN is to be compared case-sensitively.  Looking at RFC 3406,
> > the definition of the NID registration template, Appendix B.1 gives an
> > example:
> >
> >     Rules for Lexical Equivalence:
> >
> >        FQDNs are case-insensitive.  Thus, the portion of the URN
> >
> >                    urn:<assigned number>:<FQDN>:
> >
> >        is case-insensitive for matches.  The remainder of the identifier
> >        must be considered case-sensitive.
> >
> > The syntax for rdns URNs is
> >
> >         "rdns" URN    ::= urn:rdns:<reverse-dns>:<dss>
> >         <reverse-dns> ::= registered domain name in reverse, each label
> >                           separated by a colon (":")
> >         <dss>         ::= 1*<URN chars>
> >
> > I think we are constrained to require (for URN comparison) that "urn"
> > and "rdns" be case-insensitive, whereas you can specify whatever rule
> > you want for the reverse-dns and dss parts.
> >
> > But perhaps other people on this list have more knowledge of how this
> > issue has been handled for other URN namespaces.
> >
> > Dale
> >
> > .
> >