IETF Logo Mail Archive

[OSPF] draft-ietf-ospf-segment-routing-extensions-03

Shraddha Hegde <shraddha@juniper.net> Tue, 02 December 2014 16:51 UTC

Return-Path: <shraddha@juniper.net>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E031A1EEE for <ospf@ietfa.amsl.com>; Tue, 2 Dec 2014 08:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, 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 K6tu4nHdxeST for <ospf@ietfa.amsl.com>; Tue, 2 Dec 2014 08:51:05 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0734.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::734]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 037F51A1EF5 for <ospf@ietf.org>; Tue, 2 Dec 2014 08:50:35 -0800 (PST)
Received: from BY1PR0501MB1381.namprd05.prod.outlook.com (25.160.107.139) by BY1PR0501MB1448.namprd05.prod.outlook.com (25.160.108.12) with Microsoft SMTP Server (TLS) id 15.1.26.15; Tue, 2 Dec 2014 16:50:13 +0000
Received: from BY1PR0501MB1381.namprd05.prod.outlook.com (25.160.107.139) by BY1PR0501MB1381.namprd05.prod.outlook.com (25.160.107.139) with Microsoft SMTP Server (TLS) id 15.1.26.15; Tue, 2 Dec 2014 16:50:11 +0000
Received: from BY1PR0501MB1381.namprd05.prod.outlook.com ([25.160.107.139]) by BY1PR0501MB1381.namprd05.prod.outlook.com ([25.160.107.139]) with mapi id 15.01.0026.003; Tue, 2 Dec 2014 16:50:11 +0000
From: Shraddha Hegde <shraddha@juniper.net>
To: "draft-ietf-ospf-segment-routing-extensions@tools.ietf.org" <draft-ietf-ospf-segment-routing-extensions@tools.ietf.org>
Thread-Topic: draft-ietf-ospf-segment-routing-extensions-03
Thread-Index: AdAOT6Fi+HUt3MSBSRa5ydDMnUARfw==
Date: Tue, 02 Dec 2014 16:50:11 +0000
Message-ID: <64c8be7dc5744779b0a119ac0584777c@BY1PR0501MB1381.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.14]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1381;UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1381;
x-forefront-prvs: 0413C9F1ED
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(31966008)(4396001)(229853001)(54356999)(110136001)(66066001)(21056001)(50986999)(74316001)(64706001)(230783001)(20776003)(77156002)(108616004)(76576001)(62966003)(120916001)(105586002)(87936001)(40100003)(122556002)(33646002)(99396003)(86362001)(92566001)(2351001)(107046002)(101416001)(46102003)(106356001)(15975445006)(2656002)(15202345003)(77096004)(99286002)(68736005)(95666004)(19580395003)(97736003)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1381; H:BY1PR0501MB1381.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=shraddha@juniper.net;
Content-Type: multipart/alternative; boundary="_000_64c8be7dc5744779b0a119ac0584777cBY1PR0501MB1381namprd05_"
MIME-Version: 1.0
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1448;
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/ofsEJokOEIg-cc87g24ug6pxGdc
Cc: OSPF WG List <ospf@ietf.org>
Subject: [OSPF] draft-ietf-ospf-segment-routing-extensions-03
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 16:51:07 -0000

Authors,

Some  comments on the draft.

1.      The draft refers to the various use cases in the use case document in I-D.filsfils-rtgwg-segment-routing. It's useful to mention the section of the use case draft which is applicable for each reference instead of giving generic reference.
2.      Section 7.2 LAN Adj-sid sub TLV:
    Based on the description of the text it appears that the LAN AdjSID Sub TLV can contain multiple neighbor-ID /SID pairs based on the nodes attached to a broadcast network. The TLV diagram should depict carrying multiple such pairs.

       "It is used to advertise a SID/Label for an
   adjacency to a non-DR node on a broadcast or NBMA network."

   Does the above statement mean only DR originates the LAN-Adj SID and advertises label to non-DR nodes?
      Shouldn't each node in broadcast link  originate LAN adj-SID and advertise label to all other nodes on the link?

3.      Adj-Sid sub TLV section 7.1:
    Description of V-flag mentions Prefix-SID,  it should be changed to Adj-SID.
4.      Section 4: Extended prefix range TLV is very similar to Extended prefix TLV just that it has additional range associated with it.
    I would think that we should have "route type" as in Extended prefix TLV instead of just having a bit indicating "inter area"


    Rgds
    Shraddha

v2.23.0 | Report a Bug | By Email