Re: [OSPF] 答复: 答复: Inconsistency between OSPF extention and IS-IS extension for segment routing

Peter Psenak <ppsenak@cisco.com> Fri, 08 November 2013 19:56 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A7BF21E819E; Fri, 8 Nov 2013 11:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.128
X-Spam-Level:
X-Spam-Status: No, score=-5.128 tagged_above=-999 required=5 tests=[AWL=-1.824, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gv6StuzbunP1; Fri, 8 Nov 2013 11:56:22 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id F031121E8179; Fri, 8 Nov 2013 11:56:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1750; q=dns/txt; s=iport; t=1383940582; x=1385150182; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=YJqwxZ4JnklB3RHRAEVkGb+KUzJoSg3SsVLx5HtNuyY=; b=L5x+aMqzpT24gxRhiXpKP8DskhNqxdvXyr5jHPUFxl43QA/sZToEECXU uRdhuNsJvZJXRccQaE03u5mm8HxMerIw9+XJEdDZjL6Pw0zCKupqidpaN 0D6VLwUdn+DZuOJe5CBGLFBMGM3LM9u3ME13WRR9vmW9AoiTB+LDyvoYZ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAJpBfVKrRDoJ/2dsb2JhbABZgwc4g0e8IoExFnSCJQEBAQQyAUUBEAkCGAQFFg0CCQMCAQIBOgsGDQEFAgEBh3wOjxGbWAiSSIEljkIHgmeBSQOJDzOOTYEvhQ6LToFogV8b
X-IronPort-AV: E=Sophos;i="4.93,661,1378857600"; d="scan'208";a="94404526"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 08 Nov 2013 19:56:21 +0000
Received: from [10.21.86.118] ([10.21.86.118]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA8JuKSq013843; Fri, 8 Nov 2013 19:56:20 GMT
Message-ID: <527D41E3.1050008@cisco.com>
Date: Fri, 08 Nov 2013 11:56:19 -0800
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Xuxiaohu <xuxiaohu@huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0822770A@NKGEML512-MBS.china.huawei.com>, <527C2606.5060906@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082277AB@NKGEML512-MBS.china.huawei.com>, <527C32B0.5070101@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082277D4@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082277D4@NKGEML512-MBS.china.huawei.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
Cc: "ospf@ietf.org" <ospf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [OSPF] 答复: 答复: Inconsistency between OSPF extention and IS-IS extension for segment routing
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 08 Nov 2013 19:56:26 -0000

Xiaohu,

there is no LDP in the SR network, so RFC5283 is not applicable.

thanks,
Peter

On 11/7/13 17:28 , Xuxiaohu wrote:
> Hi Peter,
> 
> The 'longest-match algorithm' for LIB installation has been proposed by RFC5283.
> 
> Best regards,
> Xiaohu
> 
> ________________________________________
> 发件人: Peter Psenak [ppsenak@cisco.com]
> 发送时间: 2013年11月8日 8:39
> 收件人: Xuxiaohu
> 抄送: ospf@ietf.org; isis-wg@ietf.org
> 主题: Re: 答复: [OSPF] Inconsistency between OSPF extention and IS-IS extension for segment routing
> 
> Xiaohu,
> 
> On 11/7/13 16:23 , Xuxiaohu wrote:
>>
>> Hi Peter,
> ]
>> if you aggregate on area/L1L2 boundary, SIDs/labels for individual
>> prefixes that are covered by the aggregate are useless in the area to
>> which you aggregate - there will be no FIB entries for these individual
>> prefixes in such area. So if you aggregate, there is no need to
>> propagate SIDs/labels for aggregated prefixes.
>>
>> [Xiaohu] "In the multi-area/level
>>      scenario where route summary between areas/levels is required, the IP
>>      longest-match algorithm SHOULD be used by SR-capable routers when
>>      processing label bindings advertised by the mapping server" For more details, please read the Introduction section of http://tools.ietf.org/html/draft-xu-rtgwg-global-label-adv-00
> 
> I don't understand. If you summarize, then only the summary prefix will
> be visible in the backbone (and remote areas) and installed in the FIB
> on all routers in these areas.
> 
> Where would you apply 'longest-match algorithm' when you only see the
> single summary? How would you use the SID/label for prefixes that are
> covered by the summary?
> 
> thanks,
> Peter
>