Re: [Isis-wg] I-DAction:draft-ietf-ccamp-isis-interas-te-extension-03.txt
"Adrian Farrel" <adrian@olddog.co.uk> Wed, 27 August 2008 11:03 UTC
Return-Path: <isis-wg-bounces@ietf.org>
X-Original-To: isis-archive@megatron.ietf.org
Delivered-To: ietfarch-isis-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id D273528C1E6;
Wed, 27 Aug 2008 04:03:06 -0700 (PDT)
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 80DB028C1E6
for <isis-wg@core3.amsl.com>; Wed, 27 Aug 2008 04:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.662
X-Spam-Level:
X-Spam-Status: No, score=-0.662 tagged_above=-999 required=5 tests=[AWL=1.936,
BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id yKha3Ns1IFu3 for <isis-wg@core3.amsl.com>;
Wed, 27 Aug 2008 04:03:04 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
by core3.amsl.com (Postfix) with ESMTP id 1F5C728C23D
for <isis-wg@ietf.org>; Wed, 27 Aug 2008 04:02:04 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1])
by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
m7RB24dT027789
for <isis-wg@ietf.org>; Wed, 27 Aug 2008 12:02:05 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
[81.140.15.32]) (authenticated bits=0)
by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
m7RB24YF027778
for <isis-wg@ietf.org>; Wed, 27 Aug 2008 12:02:04 +0100
Message-ID: <052e01c90834$56157c20$0300a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "isis mailing list" <isis-wg@ietf.org>
References: <6DEB3C8154434B10BE83D8D8B66053AE@M55527>
<AE36820147909644AD2A7CA014B1FB52064AC7C1@xmb-sjc-222.amer.cisco.com>
Date: Wed, 27 Aug 2008 12:01:51 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Subject: Re: [Isis-wg]
I-DAction:draft-ietf-ccamp-isis-interas-te-extension-03.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>,
<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: isis-wg-bounces@ietf.org
Errors-To: isis-wg-bounces@ietf.org
Hi, Yes, I think Les is right. In RSVP we have got in a fine mess by having several objects with a set of identical TLVs. The IANA registry is a mess because people forget to request that all of the objects are updated with a new TLV (or a place-holder if the TLV isn't carried on the object). So, creating a single tidy registry that both 141 and 22 can point to would be nice. This looks pretty simple to me. The registry is currently called: "Registry Name: Sub-TLVs for TLV 22" We would change this to "Registry Name: Sub-TLVs for TLVs 22, 141, and 222" We would add columns to the registry to show: "May be present on TLV 22" "May be present on TLV 141" "May be present on TLV 222" Does this work for everyone? Cheers, Adrian ----- Original Message ----- From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com> To: "Mach Chen" <mach@huawei.com>om>; "isis mailing list" <isis-wg@ietf.org> Cc: "Hannes Gredler" <hannes@juniper.net> Sent: Wednesday, August 27, 2008 9:38 AM Subject: Re: [Isis-wg] I-DAction:draft-ietf-ccamp-isis-interas-te-extension-03.txt > Mach - > > One editorial nit: > > In Section 3.1 2nd paragraph page 8: > > s/GNINFO/GENINFO > > On a more substantive note, the discussion of sub-TLV allocation that > you added into Section 6.2 is clearly an improvement, but it still gives > me cause for concern. You say: > > " the sub-TLVs which are defined in > [ISIS-TE], [ISIS-TE-V3] and other documents for describing the TE > properties of an TE link are applicable to describe an inter-AS TE > link and MAY be included in the Inter-AS Reachability TLV when > adverting inter-AS TE links. So, these sub-TLVs need to be > registered in the ISIS sub-TLV registry for TLV 141. And in order to > simplify the registration, we suggest using the same registry value > as they are registered in the ISIS sub-TLV registry for TLV 22." > > This suggests that: > > 1)Every subTLV in the TLV22 registry needs to be added to the TLV141 > subTLV registry - and any future definitions have to be added in both > places regardless of whether they are for TLV22 or TLV141 (or both). > > 2)It may be acceptable for a subTLV which is used in both TLV22 and > TLV141 to have different number assignments in the two TLV registries > (though you recommend against this). > > I would prefer that we insist upon a single shared registry so that the > issues of duplicate registrations and/or different numerical assignments > never arises. > > This would then eliminate the need to repeat the existing TLV22 subTLV > assignments in this document (as you do immediately below the quoted > text) - and it would eliminate confusion between the statement above and > the statement later in the same section: > > "...the new sub-TLVs MUST be defined from a sub- > TLV registry which is shared by these two TLVs." > > Les > >> -----Original Message----- >> From: Mach Chen [mailto:mach@huawei.com] >> Sent: Monday, August 25, 2008 7:19 PM >> To: isis mailing list >> Cc: Hannes Gredler; Les Ginsberg (ginsberg) >> Subject: Fw: I-D > Action:draft-ietf-ccamp-isis-interas-te-extension-03.txt >> >> Hi, >> >> We have already updated the draft according to the comments received >> during >> the ISIS WG Last Call from Hannes Gredler and Les Ginsberg. >> >> Hannes and Les, could you please confirm whether this revision > addresses >> your comments? >> >> >> Best regards, >> Mach >> >> -------------------------------------------------- >> From: <Internet-Drafts@ietf.org> >> Sent: Monday, August 25, 2008 11:30 AM >> To: <i-d-announce@ietf.org> >> Cc: <ccamp@ops.ietf.org> >> Subject: I-D Action:draft-ietf-ccamp-isis-interas-te-extension-03.txt >> >> > A New Internet-Draft is available from the on-line Internet-Drafts >> > directories. >> > This draft is a work item of the Common Control and Measurement > Plane >> > Working Group of the IETF. >> > >> > >> > Title : ISIS Extensions in Support of Inter-AS > Multiprotocol >> > Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic > Engineering >> > Author(s) : M. Chen, R. Zhang >> > Filename : draft-ietf-ccamp-isis-interas-te-extension-03.txt >> > Pages : 20 >> > Date : 2008-08-24 >> > >> > This document describes extensions to the ISIS (ISIS) protocol to >> > support Multiprotocol Label Switching (MPLS) and Generalized MPLS >> > (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems >> > (ASes). It defines ISIS-TE extensions for the flooding of TE >> > information about inter-AS links which can be used to perform inter- >> > AS TE path computation. >> > >> > >> > >> > No support for flooding information from within one AS to another AS >> > is proposed or defined in this document. >> > >> > Conventions used in this document >> > >> > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", >> > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this >> > document are to be interpreted as described in RFC-2119 [RFC2119]. >> > >> > A URL for this Internet-Draft is: >> > > http://www.ietf.org/internet-drafts/draft-ietf-ccamp-isis-interas-te- >> extension-03.txt >> > >> > Internet-Drafts are also available by anonymous FTP at: >> > ftp://ftp.ietf.org/internet-drafts/ >> > >> > Below is the data which will enable a MIME compliant mail reader >> > implementation to automatically retrieve the ASCII version of the >> > Internet-Draft. >> > >> >> >> >> > _______________________________________________ >> > I-D-Announce mailing list >> > I-D-Announce@ietf.org >> > https://www.ietf.org/mailman/listinfo/i-d-announce >> > Internet-Draft directories: http://www.ietf.org/shadow.html >> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >> > >> >> begin 666 draft-ietf-ccamp-isis-interas-te-extension-03.txt >> M0V]N=&5N="U4>7!E.B!T97AT+W!L86EN#0I#;VYT96YT+4E$.B \,C P."TP >> <."TR-#(P,C,T.2Y)+41 :65T9BYO<F<^#0H-"@`` >> ` >> end > > _______________________________________________ > 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
- [Isis-wg] Fw: I-D Action:draft-ietf-ccamp-isis-in… Mach Chen
- Re: [Isis-wg] Fw: I-D Action:draft-ietf-ccamp-isi… Hannes Gredler
- Re: [Isis-wg] Fw: I-D Action:draft-ietf-ccamp-isi… Christian Hopps
- Re: [Isis-wg] Fw: I-D Action:draft-ietf-ccamp-isi… Mach Chen
- Re: [Isis-wg] I-D Action:draft-ietf-ccamp-isis-in… Les Ginsberg (ginsberg)
- Re: [Isis-wg] I-DAction:draft-ietf-ccamp-isis-int… Adrian Farrel
- Re: [Isis-wg] I-D Action:draft-ietf-ccamp-isis-in… Mach Chen
- Re: [Isis-wg] I-DAction:draft-ietf-ccamp-isis-int… Les Ginsberg (ginsberg)