I-D Action: draft-ietf-bfd-multipoint-active-tail-07.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bidirectional Forwarding Detection WG of the 
IETF.

Title   : BFD Multipoint Active Tails.
Authors : Dave Katz
  Dave Ward
  Santosh Pallagatti
  Greg Mirsky
Filename: draft-ietf-bfd-multipoint-active-tail-07.txt
Pages   : 18
Date: 2018-02-21

Abstract:
   This document describes active tail extensions to the Bidirectional
   Forwarding Detection (BFD) protocol for multipoint and multicast
   networks.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfd-multipoint-active-tail/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bfd-multipoint-active-tail-07
https://datatracker.ietf.org/doc/html/draft-ietf-bfd-multipoint-active-tail-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-multipoint-active-tail-07


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

I-D Action: draft-ietf-bfd-multipoint-14.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bidirectional Forwarding Detection WG of the 
IETF.

Title   : BFD for Multipoint Networks
Authors : Dave Katz
  Dave Ward
  Santosh Pallagatti
  Greg Mirsky
Filename: draft-ietf-bfd-multipoint-14.txt
Pages   : 18
Date: 2018-02-21

Abstract:
   This document describes extensions to the Bidirectional Forwarding
   Detection (BFD) protocol for its use in multipoint and multicast
   networks.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfd-multipoint/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bfd-multipoint-14
https://datatracker.ietf.org/doc/html/draft-ietf-bfd-multipoint-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-multipoint-14


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Re: IPR call for draft-mirsky-bfd-p2mp-vrrp-use-case

[Jeff Tantsura]

Chris,

I'm not aware of any IPR that applies to draft-mirsky-bfd-p2mp-vrrp-use-case, 
other, than already disclosed.

Thanks!
Jeff
On 2/20/18, 11:37, "Rtg-bfd on behalf of Chris Bowers" 
 wrote:

RTGWG,

draft-mirsky-bfd-p2mp-vrrp-use-case is currently an individual draft.
Before conducting
a poll regarding working group adoption by RTGWG, I would like to get
responses from
the authors and contributors regarding any IPR related to this draft.

There are currently two IPR statements related to this draft:

https://datatracker.ietf.org/ipr/3133/
https://datatracker.ietf.org/ipr/3135/

If you are listed as an author or contributor to
draft-mirsky-bfd-p2mp-vrrp-use-case,
please respond to this email stating whether or not you are aware of
any IPR that
applies to draft-mirsky-bfd-p2mp-vrrp-use-case. The response needs to be
sent to the RTGWG mailing list.

Thanks,
Chris

Re: Call for topics - IETF 101, London

[Jeffrey Haas]

Just a reminder, a call for topics is open for the upcoming session.

I've posted the agenda to date:
https://datatracker.ietf.org/doc/agenda-101-bfd/

-- Jeff

On Thu, Feb 15, 2018 at 04:22:31PM -0500, Jeffrey Haas wrote:
> Working Group,
> 
> BFD has requested a meeting slot for IETF 101 in London.  IETF is little
> over a month away.
> 
> This is a call for topics for our session.  Even if you think you've
> requested a slot, please respond in thread so all can see the request for
> discussion on the topic.
> 
> As is our tradition, please try to reserve requests for timeslots for 
> DISCUSSION, rather than simply a powerpoint update on a diff between two
> versions of the draft.
> 
> -- Jeff & Reshad

Re: [yang-doctors] Yangdoctors last call review of draft-ietf-bfd-yang-09

[Jeffrey Haas]

On Sun, Feb 18, 2018 at 03:28:13AM +, Reshad Rahman (rrahman) wrote:
> Hi Acee,
> 
> What I meant is that BFD always augments the control palne protocols in 
> ietf-routing model. And the BFD augmentation can be used as-is or mounted in 
> LNE or in NI.

Basically:
Whereever ietf-routing is, BFD may also be.

BFD may not be everywhere that ietf-routing is (e.g. it may or may not be in
an instance, depending on device capabilities).

-- Jeff