[Pce] SR-MPLS-TP: Question on draft-xiong-pce-pcep-extension-sr-tp
Loa Andersson <loa@pi.nu> Tue, 09 April 2019 12:52 UTC
Return-Path: <loa@pi.nu>
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 481EB1207F3; Tue, 9 Apr 2019 05:52:59 -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, 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 HXfsrd67TOzr; Tue, 9 Apr 2019 05:52:58 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C76201207FE; Tue, 9 Apr 2019 05:52:54 -0700 (PDT)
Received: from [172.20.4.169] (unknown [46.218.58.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id CAACB33F5AF; Tue, 9 Apr 2019 14:52:52 +0200 (CEST)
To: "pce@ietf.org" <pce@ietf.org>, draft-xiong-pce-pcep-extension-sr-tp@ietf.org
From: Loa Andersson <loa@pi.nu>
Message-ID: <3e5c5691-856c-4cbe-d0ed-4e83a62569cd@pi.nu>
Date: Tue, 09 Apr 2019 14:52:51 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/1JmS6uiAiJ4rSOnfi6Rhzniw7cI>
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: Tue, 09 Apr 2019 12:53:01 -0000
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
- [Pce] SR-MPLS-TP: Question on draft-xiong-pce-pce… Loa Andersson
- [Pce] 答复: SR-MPLS-TP: Question on draft-xiong-pce… xiong.quan
- Re: [Pce] 答复: SR-MPLS-TP: Question on draft-xiong… Loa Andersson