Subject: Re: [Pce] New Version Notification for draft-koldychev-pce-multipath-02.txt

From: "Mike Koldychev (mkoldych)" <[email-masked]>
Date: Tue, 23 Jun 2020 16:29:12 +0000

Hi PCE,

We added another example, error handling and clarifications.

Thanks,
Mike.

-----Original Message-----
From: [email-masked] <[email-masked]> 
Sent: Tuesday, June 23, 2020 11:40 AM
To: Vishnu Pavan Beeram <[email-masked]>; Tarek Saad <[email-masked]>; Bhupendra Yadav <[email-masked]>; Vishnu Beeram <[email-masked]>; Mike Koldychev (mkoldych) <[email-masked]>; Siva Sivabalan <[email-masked]>; Hooman Bidgoli <[email-masked]>
Subject: New Version Notification for draft-koldychev-pce-multipath-02.txt

A new version of I-D, draft-koldychev-pce-multipath-02.txt
has been successfully submitted by Mike Koldychev and posted to the IETF repository.

Name:		draft-koldychev-pce-multipath
Revision:	02
Title:		PCEP Extensions for Signaling Multipath Information
Document date:	2020-06-23
Group:		Individual Submission
Pages:		15
URL:            https://www.ietf.org/internet-drafts/draft-koldychev-pce-multipath-02.txt
Status:         https://datatracker.ietf.org/doc/draft-koldychev-pce-multipath/
Htmlized:       https://tools.ietf.org/html/draft-koldychev-pce-multipath-02
Htmlized:       https://datatracker.ietf.org/doc/html/draft-koldychev-pce-multipath
Diff:           https://www.ietf.org/rfcdiff?url2=draft-koldychev-pce-multipath-02

Abstract:
   Current PCEP standards allow only one intended and/or actual path to
   be present in a PCEP report or update.  Applications that require
   multipath support such as SR Policy require an extension to allow
   signaling multiple intended and/or actual paths within a single PCEP
   message.  This document introduces such an extension.  Encoding of
   multiple intended and/or actual paths is done by encoding multiple
   Explicit Route Objects (EROs) and/or multiple Record Route Objects
   (RROs).  A special separator object is defined in this document, to
   facilitate this.  This mechanism is applicable to SR-TE and RSVP-TE
   and is dataplane agnostic.

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