Re: [Lsr] draft-bashandy-isis-srv6-extensions: Locator Leaking

"Chengli (Cheng Li)" <chengli13@huawei.com> Fri, 18 January 2019 09:58 UTC

Return-Path: <chengli13@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5AD128766; Fri, 18 Jan 2019 01:58:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mbwAdJKTpEM7; Fri, 18 Jan 2019 01:58:01 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0ED1131186; Fri, 18 Jan 2019 01:58:00 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 86647F52FA92B7955B09; Fri, 18 Jan 2019 09:57:58 +0000 (GMT)
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 18 Jan 2019 09:57:58 +0000
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.240]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0415.000; Fri, 18 Jan 2019 17:57:55 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: Peter Psenak <ppsenak@cisco.com>, "draft-bashandy-isis-srv6-extensions@ietf.org" <draft-bashandy-isis-srv6-extensions@ietf.org>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: draft-bashandy-isis-srv6-extensions: Locator Leaking
Thread-Index: AdSuCUi/+Wip3EBNTvKyippM5tgAxv//0yUA//9giPCAAkh6gP//ZuNQ
Date: Fri, 18 Jan 2019 09:57:55 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB01AAF603@dggeml529-mbx.china.huawei.com>
References: <C7C2E1C43D652C4E9E49FE7517C236CB01AAF161@dggeml529-mbx.china.huawei.com> <738fda50-f9a2-1b71-0c38-ac9a8724a707@cisco.com> <C7C2E1C43D652C4E9E49FE7517C236CB01AAF533@dggeml529-mbx.china.huawei.com> <400f7b1c-1d82-08bb-50fa-b53cb9a3a122@cisco.com>
In-Reply-To: <400f7b1c-1d82-08bb-50fa-b53cb9a3a122@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.185.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/QsntHswZBlyiH1fmMmoDpm8NOow>
Subject: Re: [Lsr] draft-bashandy-isis-srv6-extensions: Locator Leaking
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2019 09:58:03 -0000

Hi Peter,

Please see inline.


-----Original Message-----
From: Peter Psenak [mailto:ppsenak@cisco.com] 
Sent: Friday, January 18, 2019 4:47 PM
To: Chengli (Cheng Li) <chengli13@huawei.com>;; draft-bashandy-isis-srv6-extensions@ietf.org
Cc: lsr@ietf.org
Subject: Re: draft-bashandy-isis-srv6-extensions: Locator Leaking

Hi Cheng,

please see inline:


On 18/01/2019 04:53 , Chengli (Cheng Li) wrote:
> Hi Peter,
>
> Thanks to your reply. Please see my reply inline [Cheng].
>
> Thanks,
> Cheng
>
>
> -----Original Message-----
> From: Peter Psenak [mailto:ppsenak@cisco.com]
> Sent: Thursday, January 17, 2019 3:26 PM
> To: Chengli (Cheng Li) <chengli13@huawei.com>;; 
> draft-bashandy-isis-srv6-extensions@ietf.org
> Cc: lsr@ietf.org
> Subject: Re: draft-bashandy-isis-srv6-extensions: Locator Leaking
>
> Hi Cheng,
>
> On 17/01/2019 03:07 , Chengli (Cheng Li) wrote:
>> Hi Authors,
>>
>>
>>
>> In chapter 6.1 of draft-bashandy-isis-srv6-extensions-04,  it 
>> mentions that Locator TLV can be leaked from level-2 to level-1.(See 
>> D bit)
>>
>>
>>
>> I am wondering that
>>
>> 1: Can the Locator be imported from another protocol? Like OSPF?
>
> what do you mean by "imported"?
>
> [Cheng] For example, a locator A::/64 is learned via OSPF, can it be imported to IS-IS? Maybe it  is called "copy"? or "leak"? Not sure about the term.

it's called "redistribution". Sure, nobody stops you to redistribute locators between protocols. Please note that it is not something that is specified by the IETF, because it's an internal implementation detail. 
 From protocol perspective, there is nothing specific needed to support that.

[Cheng] Cool. Get it.


>
>
>>
>> 2: Will SRv6 End SID sub-TLV be carried when the locator TLV is 
>> leaked from level-2 to Level-1?
>
> yes.
>
> [Cheng]If SRv6 End SID sub-TLVs are carried when the locator TLV is leaked  from level-2 to Level-1, does it mean  the locator TLV can not be summary? (Route aggregation)?

When you leak the locator TLV, you leak it as it is, including END SIDs.

When you summarize multiple locators, you would advertise only the summary prefix - in IP reachability TLV I would think.

This is the same as with SR MPLS. If you leak a prefix, you include SIDs. If you summarize at the area border, no SIDs are advertised with the summary itself.


[Cheng] Agree. That is what I thought. When we summarize at the are border, no SIDs are advertised with the summary itself. Thank you!


thanks,
Peter



>
> thanks,
> Peter
>
>>
>>
>>
>> Thanks,
>>
>> Cheng
>>
>>
>>
>>
>>
>
> .
>