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

"Chengli (Cheng Li)" <chengli13@huawei.com> Thu, 17 January 2019 02:07 UTC

Return-Path: <chengli13@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CE9B0126CB6; Wed, 16 Jan 2019 18:07:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.093
X-Spam-Status: No, score=-3.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7JzGST_V31kE; Wed, 16 Jan 2019 18:07:33 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com []) (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 1143E130F37; Wed, 16 Jan 2019 18:07:33 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 25883D0AED5181C3D957; Thu, 17 Jan 2019 02:07:31 +0000 (GMT)
Received: from DGGEML421-HUB.china.huawei.com ( by lhreml704-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 17 Jan 2019 02:07:30 +0000
Received: from DGGEML529-MBX.china.huawei.com ([]) by dggeml421-hub.china.huawei.com ([]) with mapi id 14.03.0415.000; Thu, 17 Jan 2019 10:07:24 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: "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/+Wip3EBNTvKyippM5tgAxg==
Date: Thu, 17 Jan 2019 02:07:23 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB01AAF161@dggeml529-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB01AAF161dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/g55lV_6StJ-fX9YI1jmQ2xaECas>
Subject: [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: Thu, 17 Jan 2019 02:07:35 -0000

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: Does the Locator can be imported another protocol? Like OSPF?
2: Will SRv6 End SID sub-TLV be carried when the locator TLV is leaked from level-2 to Level-1?