Re: [Isis-wg] CCAMP LC: draft-ietf-ccamp-isis-interas-te-extension-02.txt

Mach Chen <mach@huawei.com> Tue, 22 July 2008 08:38 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 733A83A6949; Tue, 22 Jul 2008 01:38:41 -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 6477D3A6972 for <isis-wg@core3.amsl.com>; Tue, 22 Jul 2008 01:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level:
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[AWL=-0.623, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 F+5ZjpAopXQX for <isis-wg@core3.amsl.com>; Tue, 22 Jul 2008 01:38:39 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 5C54C3A6949 for <isis-wg@ietf.org>; Tue, 22 Jul 2008 01:38:39 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K4E00DFGG19XL@szxga02-in.huawei.com> for isis-wg@ietf.org; Tue, 22 Jul 2008 16:39:09 +0800 (CST)
Received: from M55527 ([10.111.12.55]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K4E00GJLG18FG@szxga02-in.huawei.com> for isis-wg@ietf.org; Tue, 22 Jul 2008 16:39:09 +0800 (CST)
Date: Tue, 22 Jul 2008 16:39:07 +0800
From: Mach Chen <mach@huawei.com>
To: Hannes Gredler <hannes@juniper.net>
Message-id: <6F94653915024061AB64A668EC2A8912@M55527>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V12.0.1606
X-Mailer: Microsoft Windows Live Mail 12.0.1606
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
X-RFC2646: Format=Flowed; Original
References: <2655E353-3E2F-4459-91DF-9598201CD1E3@cisco.com> <20080718130626.GA12470@juniper.net> <20C0CD73B835481AA6848980AF34E0B9@M55527> <20080721080115.GB5890@juniper.net> <C9754D8B91734C3CAD7E455C5B4BD0D2@M55527> <20080722074154.GE5953@juniper.net>
Cc: Christian Hopps <chopps@rawdofmt.org>, isis mailing list <isis-wg@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>, Ross Callon <rcallon@juniper.net>, jgs@juniper.net, ALABS Brungard Deborah A <dbrungard@att.com>
Subject: Re: [Isis-wg] CCAMP LC: draft-ietf-ccamp-isis-interas-te-extension-02.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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 Hannes,

> | >
> | > i am asking specifically about the inter-AS reachability TLV.
> | > what should get inserted in the first seven octects ?
> | > what should get inserted if the neighboring AS runs OSPF ?
> |
> | No matter what the neighboring AS runs ISIS or OSPF, we consider that 
> local
> | System-ID+0 or local Router ID+0 could get inserted into the first seven
> | octects, and there will not be any extra configuration required. The
> | System-ID or Router-ID can be used for indicating the source of the 
> inter-AS
> | reach TLV.
>
> well that does not feel right. just consider the intra-level case.
> a node with system-ID XXX is advertising some reachability to node XXX.
>
> all the existing IS-Reach TLVs are carrying edges to
> *neighboring* routers, i.e. not to yourself.

I guess you misunderstand what I mean.

There is a little bit different between inter-AS reach TLV and IS-Reach TLV, 
the inter-AS Reach TLV does not need to advertise the reachability by 
carrying System-ID. The System-ID field( may be called Originator ID or 
something else, just like the Router ID of "IS-IS Router CAPABILITY TLV" 
which defined in RFC 4971) in the inter-AS Reach TLV is just used as the 
identifier of the source who generates the inter-AS Reach TLV.

So:
 The Inter-AS Reachability TLV has type 141 (which needs to be
 confirmed by IANA see Section 6.1), it contains a data structure
 consisting of:

      6 octets of System ID( indicate the source of the inter-AS reach TLVs)
      3 octets of default metric
      1 octet of control information, consisting of:
         1 bit of flooding-scope information
         1 bit of up/down information
         6 bits reserved
      1 octet of length of sub-TLVs
      0-244 octets of sub-TLVs
         where each sub-TLV consists of a sequence of:
           1 octet of sub-type
           1 octet of length of the value field of the sub-TLV
           0-242 octets of value

Best regards,
Mach

 


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www.ietf.org/mailman/listinfo/isis-wg