IETF Logo Mail Archive

Re: [Gen-art] Gen-ART review of draft-pal-eidr-urn-2016-01

"Vijay K. Gurbani" <vkg@bell-labs.com> Tue, 05 July 2016 17:21 UTC

Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80D3612D1B8; Tue, 5 Jul 2016 10:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 iHKEmwbzAN3o; Tue, 5 Jul 2016 10:21:52 -0700 (PDT)
Received: from smtp-us.alcatel-lucent.com (us-hpatc-esg-01.alcatel-lucent.com [135.245.18.27]) (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 A3D7012D128; Tue, 5 Jul 2016 10:21:52 -0700 (PDT)
Received: from us70tumx1.dmz.alcatel-lucent.com (unknown [135.245.18.13]) by Websense Email Security Gateway with ESMTPS id 4F44D3834FEAE; Tue, 5 Jul 2016 17:21:48 +0000 (GMT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (us70tusmtp1.zam.alcatel-lucent.com [135.5.2.63]) by us70tumx1.dmz.alcatel-lucent.com (GMO) with ESMTP id u65HLpOq030910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 5 Jul 2016 17:21:51 GMT
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id u65HLodr015962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jul 2016 17:21:51 GMT
Received: from [135.185.238.141] (shoonya.ih.lucent.com [135.185.238.141]) by umail.lucent.com (8.13.8/TPES) with ESMTP id u65HLoHt020582; Tue, 5 Jul 2016 12:21:50 -0500 (CDT)
To: Pierre-Anthony Lemieux <pal@sandflow.com>
References: <5cfe1036-0ce0-8c52-6dc9-77cec5b3f1c0@bell-labs.com> <CAF_7JxCLzzcDxL_Bu0o0azDAOirUshBvD-Y_wfi8V2c1LgsTcw@mail.gmail.com>
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Message-ID: <b5a08bf7-74be-5cbb-6f31-a3c748350fa1@bell-labs.com>
Date: Tue, 05 Jul 2016 12:21:50 -0500
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CAF_7JxCLzzcDxL_Bu0o0azDAOirUshBvD-Y_wfi8V2c1LgsTcw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/hLMAqRhDzQJkWvMpRtx_fWA_ySI>
Cc: draft-pal-eidr-urn-2016.authors@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-pal-eidr-urn-2016.ad@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-pal-eidr-urn-2016-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2016 17:21:54 -0000

Pierre: Thank you for attending to my comment.  More inline.

On 07/02/2016 03:30 PM, Pierre-Anthony Lemieux wrote:
> Hi Vijay,
>
> I appreciate the review and comment.
>
>> That is, are the schemes (urn, eidr) part of the case-insensitive string match?
>
> Yes, it looks like
>
> "Lexical equivalence of EIDR-URN is defined by case-insensitive string match."
>
> should say
>
> "Lexical equivalence of URN-EIDR is defined by case-insensitive string match."
>
> This would confirm that the entire URN-EIDR string defined in
> "Declaration of syntactic structure" is considered for matching,
> including "urn:eidr:".

I will appreciate if the "including 'urn:eidr:'" part made it into the
draft.  Implementers have varying level understanding as they attempt
to divine RFC text.  So to the extent that we can make our intent
explicit with a few additional strokes of the pen (or the keyboard), we
are all the more better off for it.

Cheers,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Nokia Networks
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@bell-labs.com / vijay.gurbani@nokia-bell-labs.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

v2.23.0 | Report a Bug | By Email