Re: [lisp] [Technical Errata Reported] RFC7052 (4256)

"Isidoros Kouvelas (kouvelas)" <kouvelas@cisco.com> Mon, 09 March 2015 19:05 UTC

Return-Path: <kouvelas@cisco.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB9181A92E2 for <lisp@ietfa.amsl.com>; Mon, 9 Mar 2015 12:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 4nNSuHY-82Lq for <lisp@ietfa.amsl.com>; Mon, 9 Mar 2015 12:05:23 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98F4E1A90D7 for <lisp@ietf.org>; Mon, 9 Mar 2015 12:04:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2305; q=dns/txt; s=iport; t=1425927895; x=1427137495; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=QDffjDQHBiHsSfV+ARBbAs8SGwiUJfdsuASfkvySb1I=; b=d/90pJcU6gM+56dk8EkBc72PACzFvmTAkFMaBU6GTXmmJEymAjS8jXcd ufP2AKi0IXJoM8bqd4G9QqTzLY1xFt4Ykwt6BE4U25XogSUblk1ZPlMLn K9G2RYCWmZBGoBbN5s6BZUNPkzSHdEw/1F26XkJQBb5kth1LH7or/uj9Z Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AADQDI7f1U/4QNJK1SCoMGgSwEwDOIJgKBKk0BAQEBAQF8hA8BAQEDAXkFCwIBCBguMiUCBA4FiCcIwWkBAQEBAQEBAQEBAQEBAQEBAQEBAQEXixeBPYJVBSQzB4MXgRYBBJAPiVOBGoV8jF4jgg+BX2+BA0F/AQEB
X-IronPort-AV: E=Sophos;i="5.11,369,1422921600"; d="scan'208";a="130325251"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-4.cisco.com with ESMTP; 09 Mar 2015 19:04:54 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t29J4scb019542 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 9 Mar 2015 19:04:54 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.142]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Mon, 9 Mar 2015 14:04:54 -0500
From: "Isidoros Kouvelas (kouvelas)" <kouvelas@cisco.com>
To: Brian Haberman <brian@innovationslab.net>
Thread-Topic: [Technical Errata Reported] RFC7052 (4256)
Thread-Index: AQHQQFxlnTg8pe7qO0ib4DaVqyuxIpzkBIuAgAAYCoCAAARKAIAAA3qAgAAG+QCAACV6AIAwZx+AgAAy1ICAAAKhgIAAHZUA
Date: Mon, 09 Mar 2015 19:04:54 +0000
Message-ID: <44F338B7-4A00-4B8B-A398-788110DE90CA@cisco.com>
References: <20150204092419.B7DE3180092@rfc-editor.org> <54D4C0BB.3030906@innovationslab.net> <EDF4C663-E6D0-4D93-8117-203538C20C83@cisco.com> <54D4D87E.7060807@innovationslab.net> <F412925B-8EA0-414E-AC9B-263F51715059@cisco.com> <54D4E142.6020409@innovationslab.net> <8A99A6AF-5E6D-458B-B7F8-8B4DE2FEA182@cisco.com> <54FDA92F.9060902@innovationslab.net> <2F6DE777-4655-4F71-87CC-84ABA2EF3B5C@cisco.com> <54FDD607.1090701@innovationslab.net>
In-Reply-To: <54FDD607.1090701@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.197.103]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <D1198AA0FA23944CA86BB2DE8FDBC7A7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/efNhaVXeiKlWfsp12I3bRdjxmIA>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>
Subject: Re: [lisp] [Technical Errata Reported] RFC7052 (4256)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2015 19:05:24 -0000

On Mar 9, 2015, at 19:19, Brian Haberman <brian@innovationslab.net> wrote:

> Hi Gregg,
> 
> On 3/9/15 1:09 PM, Gregg Schudel (gschudel) wrote:
>> 
>> On Mar 9, 2015, at 7:07 AM, Brian Haberman <brian@innovationslab.net>
>> wrote:
>> 
>>> 
>>> On 2/6/15 12:58 PM, Gregg Schudel (gschudel) wrote:
>>>> 
>>>> On Feb 6, 2015, at 7:44 AM, Brian Haberman
>>>> <brian@innovationslab.net> wrote:
>>>> 
>>>>> It turns out that the discussion during review was with the
>>>>> upper limit. I can't find any reference to discussions on the
>>>>> lower limit.  Authors?
>>>> 
>>>> going back to check Brian - it was a while ago.
>>> 
>>> Have we gotten anywhere with this check?  The erratum is sitting in
>>> a less-than-useful state at this point.
>>> 
>>> Regards, Brian
>> 
>> Hi Brian I’m really sorry about droppng this.
>> 
>> I’ve checked internal notes, authors, etc. I cannot find any record
>> of (nor do we recall) us discussing “minimum length.” Looking at it
>> now, the value of “5” in RFC7052 does not match any “real minimum
>> length” that we can see.
>> 
>> Further, (in discussing with Isidor), the ability to return
>> unspecified as an empty address, hence “0” length, makes sense.
>> 
>> So, again - the errate makes sense. No evidence is available to
>> indicate otherwise.
>> 
> 
> Isidor and I discussed whether changing all the lower bounds of 5 to 0
> made sense or if there was a smaller subset of variables that should be
> changed.
> 
> Isidor insisted on lispEidRegistrationLastRegisterSenderLength being
> changed, but there are potentially others.
> 
> I do not want to see a slew of errata roll in over the years changing
> one variable's lower limit at a time.  Keeping in mind, a change for one
> variable actually requires a change to two variables (the affected
> variable and its corresponding Length variable).
> 
> Can the WG identify all the MIB variables that it wants changed with
> this erratum?

The reason for which I think lispEidRegistrationLastRegisterSender is the only use of LispAddressType that needs to be changed is that its access is "read-only". All other uses are "not-accessible” and part of the index of tables.

thanks
Isidor