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

"Ing-Wher (Helen) Chen" <ichen@kuatrotech.com> Wed, 09 March 2016 16:28 UTC

Return-Path: <ichen@kuatrotech.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89AE412D715 for <urn-nid@ietfa.amsl.com>; Wed, 9 Mar 2016 08:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kuatrotechnology.onmicrosoft.com
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mxU2d-EDpvb2 for <urn-nid@ietfa.amsl.com>; Wed, 9 Mar 2016 08:28:58 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0619.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::619]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36E2012D717 for <urn-nid@apps.ietf.org>; Wed, 9 Mar 2016 08:28:57 -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=IsO8HoyzR26gyOKpswfPLjYfyhnY8L+OuP6PLXO01ns=; b=IHecCkcWLR5p+yK1zmaelEO5wACxXSes41+2BvxzJwuTX8rOKvFPnVteJ9n0TgvYaM88KajEal938/mtvl9u7+UVkM1Lw4XOa0ps79C1mBllzl/FoQiDKi7DOjXDB0oScs+XZ+ygaJBo5WFEuT9GsQG1rX8LBp67UxQAYtDnGME=
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.427.16; Wed, 9 Mar 2016 16:28:37 +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.0427.019; Wed, 9 Mar 2016 16:28:37 +0000
From: "Ing-Wher (Helen) Chen" <ichen@kuatrotech.com>
To: "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+Z80UhKAgARZzSCAGLIwgA==
Date: Wed, 9 Mar 2016 16:28:36 +0000
Message-ID: <DB5PR06MB0950D42A59AA62292470E12DD0B30@DB5PR06MB0950.eurprd06.prod.outlook.com>
References: <87povsmo0e.fsf@hobgoblin.ariadne.com> <56C7E6C5.3030306@it.aoyama.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ariadne.com; dkim=none (message not signed) header.d=none; ariadne.com; dmarc=none action=none header.from=kuatrotech.com;
x-originating-ip: [98.191.72.170]
x-ms-office365-filtering-correlation-id: b367d1e1-b082-45c5-6651-08d34837ddd8
x-microsoft-exchange-diagnostics: 1; DB5PR06MB0952; 5:uN5RpdIemtDrImH5Qb9gkw2zYWC+Zj2Gqn9LWIrZNNcXO1TkoAJm4lkoTMAbCme1QiTjCH2ZYRYDqRuCvgw+VclCWHLHfTYHlUmOtD02b+iRZsTkGbgbnoeXHePvM/aZOhH5qc/v8aKWNWbVTLpHUQ==; 24:G6At0O5ij7tHrakmdVMySC/6RZ2tV9hvK8mXnAq+vEv8qeVrQInAyu0lEgRU7QTyI9ngRjV6sbyOR9vF/5Gw3MxS1dgoXQJFwu7KcvKJP5I=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR06MB0952;
x-microsoft-antispam-prvs: <DB5PR06MB0952B913EFEDDF9F55CB6D87D0B30@DB5PR06MB0952.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DB5PR06MB0952; BCL:0; PCL:0; RULEID:; SRVR:DB5PR06MB0952;
x-forefront-prvs: 0876988AF0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(377454003)(13464003)(479174004)(24454002)(164054003)(52604005)(10400500002)(4326007)(74316001)(1096002)(110136002)(86362001)(2906002)(1220700001)(3846002)(6116002)(87936001)(586003)(102836003)(122556002)(3900700001)(54356999)(3660700001)(3280700002)(50986999)(76176999)(5002640100001)(19580405001)(5003600100002)(5008740100001)(2900100001)(33656002)(189998001)(15975445007)(5004730100002)(92566002)(66066001)(81166005)(77096005)(19580395003)(106116001)(76576001)(11100500001); 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: 09 Mar 2016 16:28:36.9532 (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/fFjwJMup43-P4mGQ4GMnG5DsrdM>
Cc: "urn-nid@apps.ietf.org" <urn-nid@apps.ietf.org>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 09 Mar 2016 16:28:59 -0000

Hello again,

I've taken Dale's advice to restrict the rdns URNs to be entirely lowercase
letters (by eliminating uppercase letters in <URN chars>), to bypass the need for
case-insensitive and case-sensitive comparison for lexical equivalence.
The latest version is -05.

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

The diff between the latest version -05 and the previous version I posted 
on this list, -03 (not -04), is here:

<https://www.ietf.org/rfcdiff?url1=https://www.ietf.org/archive/id/draft-chen-rdns-urn-03.txt&url2=https://www.ietf.org/id/draft-chen-rdns-urn-05.txt>

Thanks,
Helen

> -----Original Message-----
> From: Ing-Wher (Helen) Chen
> Sent: Monday, February 22, 2016 5:38 PM
> To: 'Martin J. Dürst' <duerst@it.aoyama.ac.jp>jp>; Dale R. Worley
> <worley@ariadne.com>
> Cc: urn-nid@apps.ietf.org
> Subject: RE: two-week review: registering formal "rdns" NID
> 
> 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
> > >
> > > .
> > >