BFD Group, chairs, Álvaro, Since BFD will not be meeting in IETF95 [1], I’m sending this message to the list attempting to understand the state, potential dependencies, and timing for advancing the S-BFD documents.
Note that [1] says: “- S-BFD is done, AD comments being addressed.” Currently, draft-ietf-bfd-seamless-base-08, submitted on 2016-02-23, addressed all of the AD Evaluation comments. Bfd-seamless-base is a hard (Normative) dependency on 5 other documents [2], which are stuck waiting for -base to move (bfd-seamless-ip, isis-sbfd, ospf-sbfd, l2tpext-sbfd, and pals-seamless-vccv). Not progressing bfd-seamless-base is blocking 6 docs (including itself) One of the changes made as part of the AD Evaluation of draft-ietf-bfd-seamless-base is to make the rational for S-BFD in the Introduction independent (i.e., not Normatively dependent) from the use cases in bfs-seamless-use-case. Basically, bfd-seamless-base includes self-defined self-contained rational for the protocol, and informatively points to use-cases. The bfd-seamless-use-case document was last submitted in July 2015. I can appreciate the fact that publishing use-cases after the protocol is potentially of little value — there is a value in that those use-cases can guide extensions to the protocol. But it also concerns me that there seems to be very little value for the base document to wait on publishing the use-cases first, since the -base protocol is done and the base document was updated to be independent from use cases. The use case document is only referenced by the -base document, and that pointer is Informative [3]. What’s the plan on pushing forward bfd-seamless-base (and untangling the other 5)? Is there something for the WG or editors to do (I assume not since -base has no dependencies and all AD Evaluation comments have been addressed)? Net-net: I’d recommend moving -base (and dependents) forward. Thanks, — Carlos. [1] https://www.ietf.org/mail-archive/web/rtg-bfd/current/msg03108.html [2] https://datatracker.ietf.org/doc/draft-ietf-bfd-seamless-base/referencedby/ [3] https://datatracker.ietf.org/doc/draft-ietf-bfd-seamless-use-case/referencedby/
signature.asc
Description: Message signed with OpenPGP using GPGMail
