Return-Path: X-Original-To: idr@ietfa.amsl.com Delivered-To: idr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 046131200D8 for ; Tue, 24 Sep 2019 20:34:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 b2mU8m1ZyRqg for ; Tue, 24 Sep 2019 20:34:54 -0700 (PDT) Received: from m176115.mail.qiye.163.com (m176115.mail.qiye.163.com [59.111.176.115]) by ietfa.amsl.com (Postfix) with ESMTP id 24D001200BA for ; Tue, 24 Sep 2019 20:34:54 -0700 (PDT) Received: from WangajPC (unknown [219.142.69.77]) by m176115.mail.qiye.163.com (Hmail) with ESMTPA id 2730B661ED9; Wed, 25 Sep 2019 11:34:47 +0800 (CST) From: "Aijun Wang" To: "'Susan Hares'" , "'idr wg'" References: <016601d56d75$e3756320$aa602960$@ndzh.com> In-Reply-To: <016601d56d75$e3756320$aa602960$@ndzh.com> Date: Wed, 25 Sep 2019 11:34:46 +0800 Message-ID: <003f01d57352$2e3315b0$8a994110$@org.cn> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0040_01D57395.3C5655B0" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdVtdHc29FIBUpzKSseFCqrVBuGyHAF2RCVQ Content-Language: zh-cn X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZVktVT01NQkJCQk9DS0lPTE5ZV1koWU FKTEtLSjdXWS1ZQUlXWQkOFx4IWUFZNTQpNjo3JCkuNz5ZBg++ X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Ojo6Iww5MDlJAQ1WDVEVAxc4 MS0aCSNVSlVKTk1CSENJT0JJTkJPVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxMWVdZCAFZQUpDS0xINwY+ X-HM-Tid: 0a6d667c54c49373kuws2730b661ed9 Archived-At: Subject: [Idr] =?gb2312?b?tPC4tDogIEFkb3B0aW9uOiBkcmFmdC1saS1pZHItYmdw?= =?gb2312?b?LWxzLXNyLXBvbGljeS1wYXRoLXNlZ21lbnQtMDMudHh0IGFuZCBkcmFmdC1s?= =?gb2312?b?aS1zci1wb2xpY3ktcGF0aC1zZWdtZW50LTAxLnR4dCBbOS8xNyB0byAxMC8x?= =?gb2312?b?LzIwMTld?= X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Sep 2019 03:34:57 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0040_01D57395.3C5655B0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Hi, All: =20 Support the adoption. =20 One comments: Can these two drafts be merged into one?=20 =20 Most of the their contents are overlapped. Add simply the corresponding part for =A1=B0BGP-LS protocol extension=A1=B1 in =A1=B0draft-li-sr-policy-path-segment-01.txt=A1=B1may be more easily for = future advancing and the user reading. =20 Best Regards. =20 Aijun Wang China Telecom =20 =B7=A2=BC=FE=C8=CB: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] = =B4=FA=B1=ED Susan Hares =B7=A2=CB=CD=CA=B1=BC=E4: 2019=C4=EA9=D4=C218=C8=D5 0:35 =CA=D5=BC=FE=C8=CB: 'idr wg' =D6=F7=CC=E2: [Idr] Adoption: = draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019] =20 This begins a 2 week WG Adoption call two related drafts [9/17 to = 10/1/2019] =A1=A4 draft-li-bgp-ls-sr-policy-path-segment-03.txt and=20 =A1=A4 draft-li-idr-sr-policy-path-segment-01.txt.=20 =20 You can access these two drafts at the following location:=20 =20 https://datatracker.ietf.org/doc/draft-li-idr-bgp-ls-sr-policy-path-segme= nt/ =20 https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment/ =20 The authors have pointed out that the adoption of this=20 draft since the following SR-MPLS Path Segment draft has been adopted:=20 =20 https://tools.ietf.org/html/draft-ietf-spring-mpls-path-segment-00 =20 Please consider the following questions in your responses?=20 =20 1) Should this SR Policy technology be included in BGP for SR-MPLS=20 =20 Spring has adopted the draft, but IDR can provide feedback=20 to spring about putting this technology in BGP. =20 2) Is this technology a good way to implement the required=20 Features in BGP?=20 =20 3) Is this technology ready for adoption?=20 =20 4) Do you have any concerns about adopting this technology?=20 =20 =20 Cheers, Susan Hares=20 ------=_NextPart_000_0040_01D57395.3C5655B0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hi, = All:

 

Support the adoption.  =

One comments: Can these two = drafts be merged into one?

 

Most of the their contents are = overlapped.  Add simply the corresponding part for =A1=B0BGP-LS =  protocol extension=A1=B1 in = =A1=B0draft-li-sr-policy-path-segment-01.txt=A1=B1may be more easily for = future advancing and the user reading.

 

Best = Regards.

 

Aijun = Wang

China = Telecom

 

=B7=A2=BC=FE=C8=CB: = idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] =B4=FA=B1=ED = Susan = Hares
=B7=A2=CB=CD=CA=B1=BC= =E4: 2019=C4=EA9=D4=C218=C8=D5 0:35
=CA=D5=BC=FE=C8=CB: 'idr = wg'
=D6=F7=CC=E2: [Idr] Adoption: = draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and = draft-li-sr-policy-path-segment-01.txt [9/17 to = 10/1/2019]

 

This begins a 2 week WG Adoption = call two related drafts [9/17 to 10/1/2019]

=A1=A4         = draft-li-bgp-ls-sr-policy-path-segment-03.txt and =

=A1=A4         = draft-li-idr-sr-policy-path-segment-01.txt. =

 

You can access these two drafts at the following location: =

 

https://datatracker.ietf.org/doc/draft-li-idr-bgp-ls-sr-poli= cy-path-segment/

 

https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segmen= t/

 

The authors have pointed out that the adoption of this =

draft = since the following  SR-MPLS Path Segment draft has been adopted: =

 

https://tools.ietf.org/html/draft-ietf-spring-mpls-path-segment-00=

 

Please consider the following questions in your responses? =

 

1)      = Should this SR Policy = technology be included in BGP for SR-MPLS

 

Spring has adopted the = draft, but IDR can provide feedback

to spring about putting this = technology in BGP.

 

2)      = Is this technology a = good way to implement the required

Features in BGP? =

 

3)      = Is this technology = ready for adoption?

 

4)      = Do you have any = concerns about adopting this technology?

 

 

Cheers, Susan Hares =

------=_NextPart_000_0040_01D57395.3C5655B0--