[Pce] 答复: SR-MPLS-TP: Question on draft-xiong-pce-pcep-extension-sr-tp

<xiong.quan@zte.com.cn> Wed, 10 April 2019 07:47 UTC

Return-Path: <xiong.quan@zte.com.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39BFE12013C; Wed, 10 Apr 2019 00:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 WLDEWOwXBS3z; Wed, 10 Apr 2019 00:47:27 -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 0884A12012A; Wed, 10 Apr 2019 00:47:26 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 0948CFA1ED6F93DAE370; Wed, 10 Apr 2019 15:47:25 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Forcepoint Email with ESMTPS id E620E8E4891A938B259A; Wed, 10 Apr 2019 15:47:24 +0800 (CST)
Received: from njxapp03.zte.com.cn ([10.41.132.202]) by mse01.zte.com.cn with SMTP id x3A7lKnV034845; Wed, 10 Apr 2019 15:47:20 +0800 (GMT-8) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Wed, 10 Apr 2019 15:47:21 +0800 (CST)
Date: Wed, 10 Apr 2019 15:47:21 +0800
X-Zmail-TransId: 2afd5cad9f8978527182
X-Mailer: Zmail v1.0
Message-ID: <201904101547214513821@zte.com.cn>
In-Reply-To: <3e5c5691-856c-4cbe-d0ed-4e83a62569cd@pi.nu>
References: 3e5c5691-856c-4cbe-d0ed-4e83a62569cd@pi.nu
Mime-Version: 1.0
From: xiong.quan@zte.com.cn
To: loa@pi.nu
Cc: pce@ietf.org, draft-xiong-pce-pcep-extension-sr-tp@ietf.org, gregory.mirsky@ztetx.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse01.zte.com.cn x3A7lKnV034845
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/8og84BwJtNG05RA5UmGQ6uNgmXE>
Subject: [Pce] 答复: SR-MPLS-TP: Question on draft-xiong-pce-pcep-extension-sr-tp
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 07:47:31 -0000

Hi Loa,






Thanks for your review and inspired comment! It is very important and much appreciated.





Refer to your question, we proposed the terminology of the "SR-MPLS-TP" in the following use case draft.

https://datatracker.ietf.org/doc/draft-hu-mpls-sr-inter-domain-use-cases/ 




We plan to work on the definition and scope of SR-MPLS-TP and start discussion in MPLS and SPRING working group next week.


Welcome to review and discuss about that draft and provide suggestions for SR-MPLS-TP!




Best Regards,

Quan









原始邮件



发件人:LoaAndersson <loa@pi.nu>
收件人:pce@ietf.org <pce@ietf.org>;draft-xiong-pce-pcep-extension-sr-tp@ietf.org <draft-xiong-pce-pcep-extension-sr-tp@ietf.org>;
日 期 :2019年04月10日 03:55
主 题 :SR-MPLS-TP: Question on draft-xiong-pce-pcep-extension-sr-tp


Authors, Working Group,

MPLS-TP is defined as a network that:

   "It MUST be possible to operate and configure the MPLS-TP data
    plane without any IP forwarding capability in the MPLS-TP data
    plane. (RFC 5654, section 2.3, requirement 36.)"

    ...

  "It MUST be possible to provide protection for the MPLS-TP data
   plane without any IP forwarding capability in the MPLS-TP data
   plane. (RFC 5654, section 2.5.1.1, requirement 63.)"

In fact most MPLS-TP networks are deployed without IP in the data
plane.

SR-MPLS on the other hand is a technology that is defined to USE
IGPs to distribute MPLS-labels, and thus requires IP in the data
plane.

PCEP also runs over TCP/IP.

The draft does not discuss this. I think this is needed, do you
have plans to do so?

/Loa
-- 


Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64