Re: [Isis-wg] [Technical Errata Reported] RFC4920 (4480)

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Fri, 25 September 2015 14:15 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 781511A1AAE; Fri, 25 Sep 2015 07:15:26 -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 1L3EA6U9Izkd; Fri, 25 Sep 2015 07:15:18 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DD8B1A1AA7; Fri, 25 Sep 2015 07:15:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6175; q=dns/txt; s=iport; t=1443190518; x=1444400118; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=rpMGAOtLrQcPwIZeLcMZ3QxXBRJau/8wHvW0u2CYhgg=; b=YaZHCe3620lQ92HGnZUteuahgSbdJf3Eu82m/Ds8FP87+JNz5TH4N0fx g5GY0PAbXLyYL7mP5+XDJoTRDD67DezAkGplS4P8Ge0yITC3BW3Pb4UQ9 dp2HxH+TtLnZwoXeNbVcnmXr/A5zy9UGtFNgHFh1adf4RwO56eIpM5ARh k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DzAQD3VQVW/4ENJK1DGoMkVGkGrCyQfQENgXAMhXcCgSs4FAEBAQEBAQGBCoQkAQEBBAEBATc0CwwEAgEIEQQBAR8JByEGCxMBCQgCBAENBQiIEQMSDTvGRg2EfQEBAQEBAQEBAQEBAQEBAQEBAQEBAReGc4R9gT2BE4FaEQFRBwaEJgWFfAyBLAaGc4c6AYURhgoGgWWBU0aDcIMhiisXh0EBHwEBQoIOAxyBVHEBE4gZOoEFAQEB
X-IronPort-AV: E=Sophos;i="5.17,587,1437436800"; d="scan'208";a="32034708"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-5.cisco.com with ESMTP; 25 Sep 2015 14:15:17 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t8PEFHeW004363 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 25 Sep 2015 14:15:17 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 25 Sep 2015 09:15:16 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1104.000; Fri, 25 Sep 2015 09:15:16 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [Isis-wg] [Technical Errata Reported] RFC4920 (4480)
Thread-Index: AQGroSSfQVAc2ph/Eee004rhkpvedp6X01sQgAAhUNA=
Date: Fri, 25 Sep 2015 14:15:16 +0000
Message-ID: <d9703fdb465240698a8d3fa2cfc2ea71@XCH-ALN-001.cisco.com>
References: <20150921055453.C79F2180204@rfc-editor.org> <09bb01d0f78b$ead496e0$c07dc4a0$@olddog.co.uk>
In-Reply-To: <09bb01d0f78b$ead496e0$c07dc4a0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.75.252]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/jKDZ-axlmGNW1wIt0FcMLljBtVg>
Cc: "isis-wg@ietf.org" <isis-wg@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Isis-wg] [Technical Errata Reported] RFC4920 (4480)
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2015 14:15:26 -0000

Adrian -

The definitive document on OSI addressing is ISO 8348 (Annex A and B). Freely available here: http://standards.iso.org/ittf/PubliclyAvailableStandards/c035872_ISO_IEC_8348_2002(E).zip

Some text in ISO 10589 Section 7.1 is also helpful.

But if you don't want to wade through the documents (for which I would not blame you :-) ) here's the short version: An area address is 1 - 13 octets in length - so at a quick read the proposed text in the errata seems to be correct.

   Les



> -----Original Message-----
> From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Adrian Farrel
> Sent: Friday, September 25, 2015 5:16 AM
> To: ccamp@ietf.org
> Cc: isis-wg@ietf.org; teas@ietf.org
> Subject: Re: [Isis-wg] [Technical Errata Reported] RFC4920 (4480)
> 
> All,
> 
> This email is copied to TEAS and ISIS, but it would be really helpful if any
> discussion was held to one list. CCAMP is probably best because they "own"
> RFC 4920.
> 
> The CCAMP chairs asked me to look into this as one of the original authors,
> and I have to say it has been so long that I can't recall the answer.
> 
> However, I looked at RFC 1195 and found section 3.3 gave me that the full
> description of an Area ID as:
> 
> >         AFI       1 octet       value "47" (specifies ICD format)
> >
> >         ICD       2 octet       value "00 05" (specifies Internet/Gosip)
> >
> >         DFI       1 octet       value "xx"
> >
> >         AA        3 octets      value "xx xx xx" (specifies special
> >                                 IP-only use of NSAPs)
> >
> >         Reserved  2 octets      must be "00 00"
> >
> >         RD        2 octets      contains autonomous system number
> >
> >         Area      2 octets      must be assigned as described below
> 
> This implies (to me) that an Area ID must be at least the trailing two octets,
> but may be given more context reading up this table up to a maximum of 13
> octets.
> 
> All I deduce from this is that I am consistent in my ability to reproduce my
> processing, not that I am right.
> 
> Can someone with IS-IS clue please comment:
> What are the max and min string lengths of an "area ID" in IS-IS?
> 
> Thanks,
> Adrian
> 
> > -----Original Message-----
> > From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> > Sent: 21 September 2015 06:55
> > To: adrian@olddog.co.uk; asatyana@cisco.com; a-iwata@ah.jp.nec.com; n-
> > fujita@bk.jp.nec.com; gash5107@yahoo.com; akatlas@gmail.com;
> > db3546@att.com; aretana@cisco.com; daniele.ceccarelli@ericsson.com;
> > zhangfatai@huawei.com
> > Cc: dhruv.ietf@gmail.com; ccamp@ietf.org; rfc-editor@rfc-editor.org
> > Subject: [Technical Errata Reported] RFC4920 (4480)
> >
> > The following errata report has been submitted for RFC4920, "Crankback
> > Signaling Extensions for MPLS and GMPLS RSVP-TE".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=4920&eid=4480
> >
> > --------------------------------------
> > Type: Technical
> > Reported by: Dhruv Dhody <dhruv.ietf@gmail.com>
> >
> > Section: 6.2
> >
> > Original Text
> > -------------
> > For types 10 and 23, the Value field has the format:
> >
> >        0                   1                   2                   3
> >        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >       |   Length      |     IS-IS Area Identifier                     |
> >       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >       ~                     IS-IS Area Identifier (continued)         ~
> >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >        Length
> >
> >           Length of the actual (non-padded) IS-IS Area Identifier in
> >           octets.  Valid values are from 2 to 11 inclusive.
> >
> > Corrected Text
> > --------------
> > For types 10 and 23, the Value field has the format:
> >
> >        0                   1                   2                   3
> >        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >       |   Length      |     IS-IS Area Identifier                     |
> >       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >       ~                     IS-IS Area Identifier (continued)         ~
> >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >        Length
> >
> >           Length of the actual (non-padded) IS-IS Area Identifier in
> >           octets.  Valid values are from 1 to 13 inclusive.
> >
> > Notes
> > -----
> > IS-IS area IDs can vary from 1 to 13 bytes in length (max NSAP length
> > is 20,
> minus
> > 1 byte for NSEL, minus 6 bytes for SysID).
> >
> > *Noted by Jonathan Hardwick in another document that was using the
> > same data.
> >
> > Instructions:
> > -------------
> > This erratum is currently posted as "Reported". If necessary, please
> > use "Reply All" to discuss whether it should be verified or rejected.
> > When a decision is reached, the verifying party (IESG) can log in to
> > change the status and edit the report, if necessary.
> >
> > --------------------------------------
> > RFC4920 (draft-ietf-ccamp-crankback-06)
> > --------------------------------------
> > Title               : Crankback Signaling Extensions for MPLS and GMPLS
> RSVP-TE
> > Publication Date    : July 2007
> > Author(s)           : A. Farrel, Ed., A. Satyanarayana, A. Iwata, N. Fujita,
> G. Ash
> > Category            : PROPOSED STANDARD
> > Source              : Common Control and Measurement Plane
> > Area                : Routing
> > Stream              : IETF
> > Verifying Party     : IESG
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg