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

Daniele Ceccarelli <daniele.ceccarelli@ericsson.com> Sat, 26 September 2015 14:42 UTC

Return-Path: <daniele.ceccarelli@ericsson.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 73F2E1B2E9B; Sat, 26 Sep 2015 07:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 yt9EJruWX3xq; Sat, 26 Sep 2015 07:42:50 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7FF31B2E9A; Sat, 26 Sep 2015 07:42:49 -0700 (PDT)
X-AuditID: c1b4fb2d-f79626d000004282-30-5606aee7b369
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 6F.D2.17026.7EEA6065; Sat, 26 Sep 2015 16:42:47 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.93]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0248.002; Sat, 26 Sep 2015 16:42:46 +0200
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Les Ginsberg (ginsberg)'" <ginsberg@cisco.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [Teas] [Isis-wg] [Technical Errata Reported] RFC4920 (4480)
Thread-Index: AQHQ983Q+nljVvvbfUeW/EFmhrS55J5Nm/UAgAFHcVA=
Date: Sat, 26 Sep 2015 14:42:46 +0000
Message-ID: <4A1562797D64E44993C5CBF38CF1BE4812A37FC1@ESESSMB301.ericsson.se>
References: <20150921055453.C79F2180204@rfc-editor.org> <09bb01d0f78b$ead496e0$c07dc4a0$@olddog.co.uk> <d9703fdb465240698a8d3fa2cfc2ea71@XCH-ALN-001.cisco.com> <0ab901d0f7ca$74c3d530$5e4b7f90$@olddog.co.uk> <79ce681fb7f949febcb73956959af4f9@XCH-ALN-001.cisco.com> <0adb01d0f7d6$8e794a80$ab6bdf80$@olddog.co.uk>
In-Reply-To: <0adb01d0f7d6$8e794a80$ab6bdf80$@olddog.co.uk>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGfG3Rvf5OrYwg3lLDSx+9Nxgtngy5waL xYY/G9ktjh56z2rR+mMHiwOrx5TfG1k9liz5yeSxYvNKxgDmKC6blNSczLLUIn27BK6MNzvO sxVMiaxYe+wLawNjo10XIyeHhICJxMFFdxkhbDGJC/fWs3UxcnEICRxllOhafYkZwlnMKLHl 8jsgh4ODTcBK4skhH5C4iEAbo0TDnwVMIN3MAl4SXw4dB7OFBTwkHl+/xA5iiwh4SiyasJcN wraS+P1pEjOIzSKgKtF1ZCpYPa+Ar8SdE58ZIZYdYJK4uuMXK0iCU8BaYs3t/WCDGAVkJSbs XsQIsUxc4taT+UwQZwtILNlznhnCFpV4+fgfK4StJLFi+yWoej2JG1OnsEHY2hLLFr5mhlgs KHFy5hOWCYxis5CMnYWkZRaSlllIWhYwsqxiFC1OLS7OTTcy1kstykwuLs7P08tLLdnECIy1 g1t+6+5gXP3a8RCjAAejEg+vwh/WMCHWxLLiytxDjNIcLErivC1MD0KFBNITS1KzU1MLUovi i0pzUosPMTJxcEo1MBpMWfI/OHbWtd4QyYTlObyCJUGsKXOrZ1TfzVqrx9qcuZLpY6mQ70Sd VLFbasddI254ql4JFul9e3bKjB9LNv113vGiVvOuomBHvUycTGIhV8GqriZPe26pF6ynz3sv 8PhZ8WRDAGuhzA6xkqpnhjkHl3zYNTEz9+BDr7efJx1/+urUvNB995VYijMSDbWYi4oTAccX FmGWAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/rL8fAr9xT1H26fjs1eX1M40k1k8>
X-Mailman-Approved-At: Mon, 28 Sep 2015 07:56:27 -0700
Cc: "isis-wg@ietf.org" <isis-wg@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Isis-wg] [Teas] [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: Sat, 26 Sep 2015 14:42:53 -0000

Thanks a lot Les and Adrian.

BR
Daniele

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Adrian Farrel
> Sent: venerdì 25 settembre 2015 23:10
> To: 'Les Ginsberg (ginsberg)'; ccamp@ietf.org
> Cc: isis-wg@ietf.org; teas@ietf.org
> Subject: Re: [Teas] [Isis-wg] [Technical Errata Reported] RFC4920 (4480)
> 
> Got it. Thanks!
> 
> CCAMP chairs - looks like the Errata Report is correct.
> 
> Adrian
> 
> > -----Original Message-----
> > From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
> > Sent: 25 September 2015 21:07
> > To: adrian@olddog.co.uk; ccamp@ietf.org
> > Cc: isis-wg@ietf.org; teas@ietf.org
> > Subject: RE: [Isis-wg] [Technical Errata Reported] RFC4920 (4480)
> >
> > Adrian -
> >
> > I assume you are quoting Section 3.3?
> >
> > NSAPs come in a variety of flavors/formats depending upon the
> > addressing authority. The example in RFC Section 3.3 is talking about
> > using USA GOSIP version 2.0 format as specified in Reference #9. The
> > NSAP field is then broken into a set of subfields which include:
> >
> >         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
> >
> >         ID        6 octets      must be assigned as desribed below
> >
> >         SEL       1 octet       used as described below
> >
> > Everything up to "ID" is part of the "area address". So the
> > AFI/ICD/AA/Reserved/RD/Area comprise a 13 octet "area address" - part
> > of which are specific values mandated by the GOSIP format. The "area"
> > is simply one field in this GOSIP format.
> >
> > ISO 8348 has more info - but frankly I always found this somewhat
> > nauseating
> to
> > read. The simplest way of thinking about things is:
> >
> > Area Address: 1 -13 octets (length and values depend on the NSAP
> > format
> > chosen)
> > System ID: 1-6 octets - but always 6 octets in practice
> > NSEL: 1 octet - always 0
> >
> >    Les
> >
> > > -----Original Message-----
> > > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Adrian
> > > Farrel
> > > Sent: Friday, September 25, 2015 12:43 PM
> > > To: Les Ginsberg (ginsberg); ccamp@ietf.org
> > > Cc: isis-wg@ietf.org; teas@ietf.org
> > > Subject: Re: [Isis-wg] [Technical Errata Reported] RFC4920 (4480)
> > >
> > > OK, Thanks Les, a great help.
> > >
> > > One last point of clarification...
> > >
> > > When RFC 1195 says...
> > > >         Area      2 octets      must be assigned as described below
> > > ... why am I confused that that is allowed to be just one octet?
> > >
> > > Cheers,
> > > Adrian
> > >
> > > > -----Original Message-----
> > > > From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
> > > > Sent: 25 September 2015 15:15
> > > > To: adrian@olddog.co.uk; ccamp@ietf.org
> > > > Cc: isis-wg@ietf.org; teas@ietf.org
> > > > Subject: RE: [Isis-wg] [Technical Errata Reported] RFC4920 (4480)
> > > >
> > > > Adrian -
> > > >
> > > > The definitive document on OSI addressing is ISO 8348 (Annex A and B).
> > > > Freely available here:
> > > > http://standards.iso.org/ittf/PubliclyAvailableStandards/c035872_I
> > > > SO_I
> > > > EC_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
> > >
> > > _______________________________________________
> > > Isis-wg mailing list
> > > Isis-wg@ietf.org
> > > https://www.ietf.org/mailman/listinfo/isis-wg
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas