Dear All,
the major part of the update is around new Non-FEC Path TLV registry to
host Segment Routing MPLS Tunnel sub-TLV proposed in this document.
We appreciate your questions, comments and consideration by BFD WG to adopt
the draft.

Regards,
Greg

---------- Forwarded message ----------
From: <internet-dra...@ietf.org>
Date: Mon, Dec 4, 2017 at 2:02 PM
Subject: New Version Notification for draft-mirsky-spring-bfd-03.txt
To: Ilya Varlashkin <i...@nobulus.com>, Gregory Mirsky <
gregimir...@gmail.com>, Ilya Varlashkin <i...@nobulus.com>, Jeff Tantsura <
jefftant.i...@gmail.com>, "Mach Chen (Guoyi)" <mach.c...@huawei.com>



A new version of I-D, draft-mirsky-spring-bfd-03.txt
has been successfully submitted by Greg Mirsky and posted to the
IETF repository.

Name:           draft-mirsky-spring-bfd
Revision:       03
Title:          Bidirectional Forwarding Detection (BFD) in Segment Routing
Networks Using MPLS Dataplane
Document date:  2017-12-04
Group:          Individual Submission
Pages:          10
URL:            https://www.ietf.org/internet-drafts/draft-mirsky-spring-
bfd-03.txt
Status:         https://datatracker.ietf.org/doc/draft-mirsky-spring-bfd/
Htmlized:       https://tools.ietf.org/html/draft-mirsky-spring-bfd-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-mirsky-spring-
bfd-03
Diff:           https://www.ietf.org/rfcdiff?url2=draft-mirsky-spring-bfd-03

Abstract:
   Segment Routing architecture leverages the paradigm of source
   routing.  It can be realized in the Multiprotocol Label Switching
   (MPLS) network without any change to the data plane.  A segment is
   encoded as an MPLS label and an ordered list of segments is encoded
   as a stack of labels.  Bidirectional Forwarding Detection (BFD) is
   expected to monitor any kind of paths between systems.  This document
   defines how to use Label Switched Path Ping to bootstrap and control
   path in reverse direction of a BFD session on the Segment Routing
   static MPLS tunnel.




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

Reply via email to