Re: [Pce] I-D Action: draft-ietf-pce-stateful-interdomain-02.txt Tue, 13 July 2021 11:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1EC973A14F0; Tue, 13 Jul 2021 04:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.488
X-Spam-Status: No, score=-0.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FORGED_MUA_MOZILLA=2.309, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JeVolBC-m5pe; Tue, 13 Jul 2021 04:32:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 178973A14EE; Tue, 13 Jul 2021 04:32:03 -0700 (PDT)
Received: from (unknown [xx.xx.xx.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by (ESMTP service) with ESMTPS id 4GPJPs674Jz1yMB; Tue, 13 Jul 2021 13:32:01 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1626175921; bh=w1Ko5sBHotFyDRSJIlX0YrRqrLANBTavTvUdUK5sCHY=; h=Subject:To:From:Message-ID:Date:MIME-Version:Content-Type: Content-Transfer-Encoding; b=S4sWKjgcYLBT2NNv13bWXdpVZuYg1h1ptY/MysAFy0VrNC919kDW7UKBpI9sxrl6D Vd4ecXBNTMkOAMF24uWB6Jkz4AwpIBwK5P/Hu4a7TuZBIWsMnAerUrCex3HHLIlma7 QMMqlPkq6Cr/OX4Pfjf33PKr8j5S2eA6fuR1QIz31X12doIIGWKTYRATHU0RwxTVyr 90k8RMQCvsni7REqJ9d7PPFLASujInWzxw1uzHQnuA/tu1/MbdgDzdBZ/kGssiEpKt Xf/B7Z3msYptMMeqI9onkyw7hwiOBKSPRs8mftHU4Mx6kspJdsAmyAIRz3DiHp7Eys dXtR1yKI793Dw==
Received: from Exchangemail-eme3.itn.ftgroup (unknown [xx.xx.50.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (ESMTP service) with ESMTPS id 4GPJPs5RdVzDq7r; Tue, 13 Jul 2021 13:32:01 +0200 (CEST)
Received: from [] ( by exchange-eme3.itn.ftgroup ( with Microsoft SMTP Server (TLS) id 14.3.498.0; Tue, 13 Jul 2021 13:32:01 +0200
To: <>, <>, <>
References: <>
From: <>
Organization: Orange Labs
Message-ID: <>
Date: Tue, 13 Jul 2021 13:32:00 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-GB
X-Originating-IP: []
Archived-At: <>
Subject: Re: [Pce] I-D Action: draft-ietf-pce-stateful-interdomain-02.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 13 Jul 2021 11:32:09 -0000

Dear all, We just published a new version of draft-ietf-pce-stateful-interdomain. This revision 2 takes into account the recommendations about how to convey the Stitching Label. As decided following the discussion on the mailing list, the draft has been updated to use the TE-PATH-BINDING TLV to request and convey the Stiching Label as a Binding Value. Main modification concerns: - Section 2 to explainhow to use the TE-PATH-BINDING TLV and to define 2 new flagsfor Binding Value. Some texts have been also move from section 6 to section 2to explain how to steer traffic at inter-domain. This includes  both RSVP-TE and Segment Routing use case. - Section 3 and 4 to adapt the distributed and centralised use case accordingly  to section 2. Both use case have been generalized to RSVP-TE and Segment Routing for local path enforcement. - Section 6 to explain in which condition a domain could Nested inter-domain traffic. - Section 7 to adapt IANA requests according to section 2. As usual, comments are welcome.


Olivier, on behalf of authors

Le 12/07/2021 à 19:30, a écrit :
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Path Computation Element WG of the IETF.
>         Title           : PCEP Extension for Stateful Inter-Domain Tunnels
>         Authors         : Olivier Dugeon
>                           Julien Meuric
>                           Young Lee
>                           Daniele Ceccarelli
> 	Filename        : draft-ietf-pce-stateful-interdomain-02.txt
> 	Pages           : 37
> 	Date            : 2021-07-12
> Abstract:
>    This document specifies how to use a Backward Recursive or
>    Hierarchical method to derive inter-domain paths in the context of
>    stateful Path Computation Element (PCE).  The mechanism relies on the
>    PCInitiate message to set up independent paths per domain.  Combining
>    these different paths together enables them to be operated as end-to-
>    end inter-domain paths, without the need for a signaling session
>    between inter-domain border routers.  For this purpose, this document
>    defines a new Stitching Label, new Association Type, and a new PCEP
>    communication Protocol (PCEP) Capability.
> The IETF datatracker status page for this draft is:
> There is also an htmlized version available at:
> A diff from the previous version is available at:
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> Pce mailing list


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.