Seamless Bidirectional Forwarding Detection (S-BFD) for Virtual Circuit Connectivity Verification (VCCV)
draft-ietf-pals-seamless-vccv-03

[Ballot comment]
seems like this is package with two drafts on the 5/5 telechat. they could be put together and that would be fine, gi ven this one is largely the values which need to be understood in the context of the other two drafts.

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-pals-seamless-vccv-02.txt. If any part of this review is inaccurate, please let us know.

IANA understands that, upon approval of this document, there are three actions which IANA must complete.

First, in the MPLS VCCV Connectivity Verification (CV) Types subregistry of the Pseudowire Name Spaces (PWE3) registry located at:

https://www.iana.org/assignments/pwe3-parameters/

Bit(Value): [ TBD-at-Registration ]
Description: S-BFD IP/UDP-encapsulated, for PW Fault Detection only
Reference: [ RFC-to-be ]

Bit(Value): [ TBD-at-Registration ]
Description: S-BFD PW-ACH-encapsulated, for PW Fault Detection only
Reference: [ RFC-to-be ]

Second, in the VCCV Capability AVP (Attribute Type 96) Values subregistry of the Layer Two Tunneling Protocol "L2TP" registry located atL

https://www.iana.org/assignments/l2tp-parameters/

the following types will be added to the L2TPv3 Connectivity Verification (CV) Types subregistry:

Bit(Value): [ TBD-at-registration ]
Description: S-BFD IP/UDP-encapsulated, for PW Fault Detection only
Reference: [ RFC-to-be ]

Bit(Value): [ TBD-at-registration ]
Description: S-BFD L2SS-encapsulated, for PW Fault Detection only
Reference: [ RFC-to-be ]

Third, in the MPLS Generalized Associated Channel (G-ACh) Types (including Pseudowire Associated Channel Types) subregistry of the Generic Associated Channel (G-ACh) Parameters registry located at:

https://www.iana.org/assignments/g-ach-parameters/

a single type will be added as follows:

Value: [ TBD-at-registration ]
Description: S-BFD Control, PW-ACH/L2SS encapsulation (without IP/UDP Headers)
Reference: [ RFC-to-be ]

IANA understands that these are the only actions required to be completed upon approval of this document.


Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. 


Thank you,

Sabrina Tanamal
IANA Specialist
ICANN

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: db3546@att.com, agmalis@gmail.com, pals-chairs@ietf.org, pals@ietf.org, "Andrew G. Malis" , draft-ietf-pals-seamless-vccv@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Seamless BFD for VCCV) to Proposed Standard


The IESG has received a request from the Pseudowire And LDP-enabled
Services WG (pals) to consider the following document:
- 'Seamless BFD for VCCV'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-04-05. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document extends the procedures and Connectivity Verification
  (CV) types already defined for Bidirectional Forwarding Detection
  (BFD) for Virtual Circuit Connectivity Verification (VCCV) to define
  Seamless BFD (S-BFD) for VCCV.  This document updates RFC 5885,
  extending the CV Values and the Capability Selection.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-pals-seamless-vccv/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-pals-seamless-vccv/ballot/


No IPR declarations have been submitted directly on this I-D.

1. Summary

The document shepherd is Andy Malis. The responsible Area Director is Deborah Brungard.

This document extends the procedures and Connectivity Verification (CV) types already defined for Bidirectional Forwarding Detection (BFD) for Virtual Circuit Connectivity Verification (VCCV) to define Seamless BFD (S-BFD) for VCCV.  It updates RFC 5885, extending the CV Values and the Capability Selection, and is thus being submitted to be a Proposed Standard.

This draft is part of a group of drafts for Seamless BFD (see the references for the related drafts). As some of these drafts are normative references, this draft will need to be published as a part of an RFC Editor cluster.

2. Review and Consensus

As IETF work items go, this draft progressed relatively quickly, as the initial individual draft came out only about a year ago. One of the reasons that it has progressed so rapidly is that the draft has received good discussion and review, first as an individual draft and then as a working group draft. It also received attention as being a part of the larger Seamless BFD effort. The acknowledgements section in the draft reflects the people that submitted substantive reviews and comments. Two WG LC reviews in particular resulted in some good improvements in the draft.

The draft has been non-controversial and there were no objections to consensus at any point.

The draft is externally cited by a CableLabs document, Data-Over-Cable Service Interface Specifications DCA - MHAv2 ( http://www.cablelabs.com/wp-content/uploads/specdocs/CM-SP-R-DEPI-I03-161021.pdf ) as a MUST for portions of its functionality. To my knowledge it has not yet been implemented, as it has not received IANA early allocations, but it is in at least one vendor's roadmap once the allocations have been made.

3. Intellectual Property

Each author has confirmed conformance with BCP 78/79. There are no IPR disclosures on the document.

4. Other Points

This draft does not create any new IANA registries. It requests allocations in existing registries that require IETF consensus/review, but not expert review. The allocation requests are clear and straightforward for IANA to execute.