Re: [OSPF] draft-ietf-ospf-segment-routing-extensions-03
Peter Psenak <ppsenak@cisco.com> Tue, 02 December 2014 17:08 UTC
Return-Path: <ppsenak@cisco.com>
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 2DED01A6EF1 for <ospf@ietfa.amsl.com>; Tue, 2 Dec 2014 09:08:47 -0800 (PST)
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 1K5KXE_wiR6C for <ospf@ietfa.amsl.com>; Tue, 2 Dec 2014 09:08:44 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B3BE1A6EF4 for <ospf@ietf.org>; Tue, 2 Dec 2014 09:08:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2108; q=dns/txt; s=iport; t=1417540124; x=1418749724; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=pznj/m+qbDTm65DcUUwOw0uROdNMTxiPgqXAlvvmVBA=; b=aqCdS2LoRMTrZCCtLOuvcel8Rv5iNsTrppUToPdbJ4AseSuCUBeUG/Ga kKqGHuaGVR3QVQG6Xwct8GyPSZxmHT7aE3PbnsJpoQtDzQlD+ZVq5wtMM jI3pjILMAD4Fo3Pp4JSW/Fir6CsJWD8uxtbz93rLXsCY5on2/lkcEY0rw 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FANDwfVStJV2T/2dsb2JhbABbgwfOWgKBIhYBAQEBAX2EAgEBAQMBMgEFQAEFCwsYCRYPCQMCAQIBRQYBDAEHAQGIMwnWSwEBAQEBAQEBAQEBAQEBAQEBAQEBGJBvB4RIAQScBoEsgziCYo1bg3w+gncBAQE
X-IronPort-AV: E=Sophos;i="5.07,501,1413244800"; d="scan'208";a="101958659"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-2.cisco.com with ESMTP; 02 Dec 2014 17:08:43 +0000
Received: from [10.148.128.133] ([10.148.128.133]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id sB2H8g9b022370; Tue, 2 Dec 2014 17:08:42 GMT
Message-ID: <547DF219.4020500@cisco.com>
Date: Tue, 02 Dec 2014 18:08:41 +0100
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Shraddha Hegde <shraddha@juniper.net>, "draft-ietf-ospf-segment-routing-extensions@tools.ietf.org" <draft-ietf-ospf-segment-routing-extensions@tools.ietf.org>
References: <64c8be7dc5744779b0a119ac0584777c@BY1PR0501MB1381.namprd05.prod.outlook.com>
In-Reply-To: <64c8be7dc5744779b0a119ac0584777c@BY1PR0501MB1381.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/3S2ZTlma092qyBwgiUc5zqOAYY8
Cc: OSPF WG List <ospf@ietf.org>
Subject: Re: [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 17:08:47 -0000
Shraddha, please see inline: On 12/2/14 17:50 , Shraddha Hegde wrote: > 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. sure, we can add that. > 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. no. LAN AdjSID Sub TLV only advertises a adj-SID for a single neighbor. If you have more non-DR neighbors, you need to advertise multiple LAN Adj-SID Sub-TLVs. > “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 SIDand > advertises label to non-DR nodes? no. > Shouldn’t each node in broadcast link originate LAN adj-SID and > advertise label to all other nodes on the link? For the adjacency to DR, Adj-SID Sub-TLV is used. For the adjacency to non-DR LAN Adj-SID Sub-TLV is used. It's done all all nodes on the LAN. > > 3. Adj-Sid sub TLV section 7.1: > > Description of V-flag mentions Prefix-SID, it should be changed to Adj-SID. good catch, will correct. > > 4. Section 4: Extended prefix range TLV is very similar to Extended > prefix TLV just that it has additional range associated with it. yes, that is correct. > > I would think that we should have "route type" as in Extended prefix TLV > instead of just having a bit indicating "inter area" route-type would be misleading for range, as single range can include prefixes of various types (intra, inter, external). We have discussed this between authors and we agreed route-type is not the right way. thanks, Peter > Rgds > Shraddha
- [OSPF] draft-ietf-ospf-segment-routing-extensions… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Peter Psenak
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Peter Psenak
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Peter Psenak
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Peter Psenak
- [OSPF] draft-ietf-ospf-segment-routing-extensions… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Peter Psenak
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Peter Psenak
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Peter Psenak
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Shraddha Hegde
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Peter Psenak
- Re: [OSPF] draft-ietf-ospf-segment-routing-extens… Shraddha Hegde