Re: [Idr] WG Adoption - draft-li-idr-sr-policy-path-mtu-03.txt - 2 Week WG adoption call (3/30 - 4/13)

"gongxia@chinatelecom.cn" <gongxia@chinatelecom.cn> Sun, 05 April 2020 09:51 UTC

Return-Path: <gongxia@chinatelecom.cn>
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 842083A0900 for <idr@ietfa.amsl.com>; Sun, 5 Apr 2020 02:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 JrBPbji3vyd0 for <idr@ietfa.amsl.com>; Sun, 5 Apr 2020 02:51:04 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.223]) by ietfa.amsl.com (Postfix) with ESMTP id EBA413A08FB for <idr@ietf.org>; Sun, 5 Apr 2020 02:51:03 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.218:35686.561968910
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-113.111.9.218?logid-98BE0828866247B9B7FAE56043BBF61A (unknown [172.18.0.218]) by chinatelecom.cn (HERMES) with SMTP id 8478E280079; Sun, 5 Apr 2020 17:50:53 +0800 (CST)
X-189-SAVE-TO-SEND: 71041897@chinatelecom.cn
Received: from ([172.18.0.218]) by App0025 with ESMTP id 98BE0828866247B9B7FAE56043BBF61A for shares@ndzh.com; Sun Apr 5 17:50:55 2020
X-Transaction-ID: 98BE0828866247B9B7FAE56043BBF61A
X-filter-score: filter<0>
X-Real-From: gongxia@chinatelecom.cn
X-Receive-IP: 172.18.0.218
X-MEDUSA-Status: 0
Date: Sun, 5 Apr 2020 17:50:33 +0800
From: "gongxia@chinatelecom.cn" <gongxia@chinatelecom.cn>
To: "Susan Hares" <shares@ndzh.com>, "'IDR List'" <idr@ietf.org>
References: <01a201d6068f$c1f3aaf0$45db00d0$@ndzh.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.10.151[cn]
Mime-Version: 1.0
Message-ID: <2020040517495963614112@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart018681472161_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ClxA_uN4zU-XdlnzsCW3qu3iXAg>
Subject: Re: [Idr] WG Adoption - draft-li-idr-sr-policy-path-mtu-03.txt - 2 Week WG adoption call (3/30 - 4/13)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2020 00:46:36 -0000

 Suport the adoption.

Since the length of the packet header of SR/SRv6 is not fixed, path mtu carried for the SR policy via BGP can deal with some network deployment problems. 



gongxia
 
From: Susan Hares
Date: 2020-03-30 20:35
To: 'IDR List'
Subject: [Idr] WG Adoption - draft-li-idr-sr-policy-path-mtu-03.txt - 2 Week WG adoption call (3/30 - 4/13)
This begins a 2 week WG adoption call for draft-li-idr-sr-policy-path-mtu-03.txt 
 
You can view this draft at: 
https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-mtu/
 
This draft distributes path maximum transmission unit for the 
SR policy via BGP.  
 
Any discussion regarding on whether one desires 
SR Policy should be clearly distinguished from the 
Technical discussions on the mechanisms to pass SR policy MTU. 
 
The questions for the people to discuss on this draft are: 
 
1) Is there a need for this mechanism in networks using 
        MPLS-SR or SR-V6 and SR policy? 
 
2) Are there any error handling issues besides what is being 
     Taken care of in RFC7752bis-03.txt
 
3) Do you think this draft is ready to be adopted? 
     In this category, please list any concerns you have
     regarding adoption.  This category can include 
     general concerns about BGP-LS, MPLS-SR, 
    SR-V6, and SR-Policy.   
 
Cheers, Sue Hares