Telechat Review of draft-ietf-bfd-vxlan-09
review-ietf-bfd-vxlan-09-opsdir-telechat-schoenwaelder-2019-12-17-00

Request Review of draft-ietf-bfd-vxlan
Requested revision No specific revision (document currently at 16)
Type Telechat Review
Team Ops Directorate (opsdir)
Deadline 2019-12-17
Requested 2019-12-03
Authors Santosh Pallagatti , Greg Mirsky , Sudarsan Paragiri , Vengada Prasad Govindan , Mallik Mudigonda
I-D last updated 2019-12-17
Completed reviews Rtgdir Last Call review of -07 by Joel M. Halpern (diff)
Opsdir Last Call review of -07 by Jürgen Schönwälder (diff)
Genart Last Call review of -07 by Erik Kline (diff)
Tsvart Last Call review of -07 by Olivier Bonaventure (diff)
Secdir Last Call review of -07 by Shawn M Emery (diff)
Opsdir Telechat review of -09 by Jürgen Schönwälder (diff)
Secdir Telechat review of -09 by Shawn M Emery (diff)
Genart Telechat review of -09 by Erik Kline (diff)
Assignment Reviewer Jürgen Schönwälder
State Completed
Request Telechat review on draft-ietf-bfd-vxlan by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/848TzV0H331ui5cbdZaiK_dsY1A
Reviewed revision 09 (document currently at 16)
Result Has nits
Completed 2019-12-17
review-ietf-bfd-vxlan-09-opsdir-telechat-schoenwaelder-2019-12-17-00
I have only a limited understanding of VXLAN and BFD technology.
Hence, some of my question may look odd to the insiders.

- Never	heard of this IPv6 loopback address space before. Is it	OK to
  allocate and use it this way?

- Why is echo BFD outside the scope of this document? Can I just turn
  on echo mode or will extra specifications be needed?

- Nits:

  OLD

    Ability to monitor path continuity

  NEW

    The ability to monitor path continuity

  OLD

    BFD packet MUST be encapsulated

  NEW

    BFD packets MUST be encapsulated