[mpls] New Version Notification fordraft-xiong-mpls-path-segment-sr-mpls-interworking-01.txt
<xiong.quan@zte.com.cn> Fri, 18 October 2019 06:41 UTC
Return-Path: <xiong.quan@zte.com.cn>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF531200CC for <mpls@ietfa.amsl.com>; Thu, 17 Oct 2019 23:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 WxavjAyJT3eG for <mpls@ietfa.amsl.com>; Thu, 17 Oct 2019 23:40:59 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 528D1120098 for <mpls@ietf.org>; Thu, 17 Oct 2019 23:40:59 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 50DEB833A98386C5BB90 for <mpls@ietf.org>; Fri, 18 Oct 2019 14:40:57 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 3DBC04A1D1A40B004ADE for <mpls@ietf.org>; Fri, 18 Oct 2019 14:40:57 +0800 (CST)
Received: from njxapp03.zte.com.cn ([10.41.132.202]) by mse-fl2.zte.com.cn with SMTP id x9I6eipW001339 for <mpls@ietf.org>; Fri, 18 Oct 2019 14:40:44 +0800 (GMT-8) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid201; Fri, 18 Oct 2019 14:40:44 +0800 (CST)
Date: Fri, 18 Oct 2019 14:40:44 +0800
X-Zmail-TransId: 2afb5da95e6ce5ed1c52
X-Mailer: Zmail v1.0
Message-ID: <201910181440440921514@zte.com.cn>
References: 157129842999.9287.8764743418551324379.idtracker@ietfa.amsl.com
Mime-Version: 1.0
From: xiong.quan@zte.com.cn
To: mpls@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn x9I6eipW001339
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/8i6B9GdbKFEW_1P4YHqBe_9S8P8>
Subject: [mpls] New Version Notification fordraft-xiong-mpls-path-segment-sr-mpls-interworking-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2019 06:41:01 -0000
Dear all, I have updated the following draft. Comments and suggestions are very welcome! A new version of I-D, draft-xiong-mpls-path-segment-sr-mpls-interworking-01.txt has been successfully submitted by Quan Xiong and posted to the IETF repository. Name: draft-xiong-mpls-path-segment-sr-mpls-interworking Revision: 01 Title: The Use of Path Segment in SR-MPLS and MPLS Interworking Document date: 2019-10-17 Group: Individual Submission Pages: 8 URL: https://www.ietf.org/internet-drafts/draft-xiong-mpls-path-segment-sr-mpls-interworking-01.txt Status: https://datatracker.ietf.org/doc/draft-xiong-mpls-path-segment-sr-mpls-interworking/ Htmlized: https://tools.ietf.org/html/draft-xiong-mpls-path-segment-sr-mpls-interworking-01 Htmlized: https://datatracker.ietf.org/doc/html/draft-xiong-mpls-path-segment-sr-mpls-interworking Diff: https://www.ietf.org/rfcdiff?url2=draft-xiong-mpls-path-segment-sr-mpls-interworking-01 Abstract: This document discusses the SR-MPLS and MPLS interworking scenarios and proposes the solution with the use of path segments. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat