Re: [mpls] New Version Notification for draft-mirsky-mpls-bfd-directed-00.txt

[Gregory Mirsky <[e-mail]>]

Hi Mach,
thank you for your feedback.
Indeed, both drafts have commonalities.
I'm looking forward to the discussion in Toronto and how we can bring this idea further.

	Regards,
		Greg

-----Original Message-----
From: Mach Chen [mailto:[e-mail]] 
Sent: Tuesday, July 01, 2014 6:57 PM
To: Gregory Mirsky
Cc: [e-mail]
Subject: RE: New Version Notification for draft-mirsky-mpls-bfd-directed-00.txt

Hi Greg,

I have a quick review on the draft, well written and useful draft!

Couple years ago, we submitted a draft (http://tools.ietf.org/html/draft-chen-mpls-bfd-enhancement-01) that intend to solve the similar issue, glad we have the similar thought:-).

It also defines extensions to LSP Ping to direct the choose of the return path of BFD control packets. Please take a look.

Best regards,
Mach

> -----Original Message-----
> From: Rtg-bfd [mailto:[e-mail]] On Behalf Of Gregory 
> Mirsky
> Sent: Wednesday, July 02, 2014 2:19 AM
> To: [e-mail]; [e-mail]
> Subject: FW: New Version Notification for 
> draft-mirsky-mpls-bfd-directed-00.txt
> 
> Dear All,
> we've posted a new draft. LSP Ping already is used to bootstrap a BFD 
> session with BFD Discriminator TLV. A new BFD Reverse Path TLV is 
> introduced in order to instruct a far-end BFD peer to use particular 
> path for reverse direction of the BFD session.
> 
> Greatly appreciate your questions, comments.
> 
> 	Regards,
> 		Greg
> 
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]
> Sent: Monday, June 30, 2014 4:15 PM
> To: Gregory Mirsky; Ilya Varlashkin; Jeff Tantsura; Gregory Mirsky; 
> Jeff Tantsura; Ilya Varlashkin
> Subject: New Version Notification for 
> draft-mirsky-mpls-bfd-directed-00.txt
> 
> 
> A new version of I-D, draft-mirsky-mpls-bfd-directed-00.txt
> has been successfully submitted by Greg Mirsky and posted to the IETF 
> repository.
> 
> Name:		draft-mirsky-mpls-bfd-directed
> Revision:	00
> Title:		Bidirectional Forwarding Detection (BFD) Directed Return Path
> Document date:	2014-06-30
> Group:		Individual Submission
> Pages:		8
> URL:
> http://www.ietf.org/internet-drafts/draft-mirsky-mpls-bfd-directed-00.
> txt
> Status:
> https://datatracker.ietf.org/doc/draft-mirsky-mpls-bfd-directed/
> Htmlized:       http://tools.ietf.org/html/draft-mirsky-mpls-bfd-directed-00
> 
> 
> Abstract:
>    Bidirectional Forwarding Detection (BFD) is expected to monitor bi-
>    directional paths.  When forward direction of a BFD session is to
>    monitor explicitly routed path there is\ a need to be able to direct
>    far-end BFD peer to use specific path as reverse direction of the BFD
>    session.
> 
> 
> 
> 
> 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