Subject: [spring] draft-ietf-spring-segment-routing-mpls-12

From: <[email-masked]>
Date: Fri, 9 Mar 2018 09:54:13 +0000

Ahmed, authors,
Thanks for the work updating this document, answering Alvaro’s comment and presenting at London.

WG,
This draft has been returned to the WG by the AD.
Please have a look at the document and comment, especially as the changes are non-trivial.

In particular, as indicated by Ahmed, this draft now covers the handling of incoming and outcoming label collision and as a result my understanding is that the WG draft draft-ietf-spring-conflict-resolution will not be pursued.
If you have reviewed or commented on draft-ietf-spring-conflict-resolution during its working group last call, you are likely interested in reviewing draft-ietf-spring-segment-routing-mpls and checking whether your comments are addressed.

Finally, the document shepherd was Martin who is now serving as routing AD. Rob and I both co-authors this draft so it’s not appropriate for us to be shepherd.
Shraddha has agreed to shepherd this document; Thank you Shraddha.

--Bruno

From: spring [mailto:[email-masked]] On Behalf Of Ahmed Bashandy (bashandy)
Sent: Thursday, March 08, 2018 6:18 PM
To: [email-masked]
Subject: [spring] Fwd: New Version Notification for draft-ietf-spring-segment-routing-mpls-12.txt

Hi,

Here is a new version of the draft. This version has non-trivial changes from the previous one. Here is a summary of the changes
- Specifications of the rules governing SRGB and SRLB
- Specification of how to translate a SID index into a label
- Specification of what a router do when receiving an SRGB advertisement that does not conform to the rules
- Handling incoming label collision
- Handling outgoing label collision
- Rules governing redistribution of routes that have SR-MPLS SIDs

Thanks

Ahmed

-------- Original Message --------
Subject:

New Version Notification for draft-ietf-spring-segment-routing-mpls-12.txt

Date:

Fri, 23 Feb 2018 05:06:46 -0800

From:

<[email-masked]><mailto:[email-masked]>

To:

Ahmed Bashandy <[email-masked]><mailto:[email-masked]>, Bruno Decraene <[email-masked]><mailto:[email-masked]>, Clarence Filsfils <[email-masked]><mailto:[email-masked]>, "Stefano Previdi" <[email-masked]><mailto:[email-masked]>, Rob Shakir <[email-masked]><mailto:[email-masked]>, "Stephane Litkowski" <[email-masked]><mailto:[email-masked]>

A new version of I-D, draft-ietf-spring-segment-routing-mpls-12.txt

has been successfully submitted by Ahmed Bashandy and posted to the

IETF repository.

Name:         draft-ietf-spring-segment-routing-mpls

Revision:     12

Title:        Segment Routing with MPLS data plane

Document date: 2018-02-23

Group:        spring

Pages:        24

URL:            https://www.ietf.org/internet-drafts/draft-ietf-spring-segment-routing-mpls-12.txt

Status:         https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-mpls/

Htmlized:       https://tools.ietf.org/html/draft-ietf-spring-segment-routing-mpls-12

Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-mpls-12

Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-mpls-12

Abstract:

   Segment Routing (SR) leverages the source routing paradigm.  A node

   steers a packet through a controlled set of instructions, called

   segments, by prepending the packet with an SR header.  In the MPLS

   dataplane, the SR header is instantiated through a label stack. This

   document specifies the forwarding behavior to allow instantiating SR

   over the MPLS dataplane.

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

_________________________________________________________________________________________________________________________

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.