Last Call Review of draft-ietf-pwe3-vccv-bfd-
review-ietf-pwe3-vccv-bfd-secdir-lc-harkins-2009-07-03-00

Request Review of draft-ietf-pwe3-vccv-bfd
Requested rev. no specific revision (document currently at 07)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2009-06-30
Requested 2009-06-16
Other Reviews
Review State Completed
Reviewer Dan Harkins
Review review-ietf-pwe3-vccv-bfd-secdir-lc-harkins-2009-07-03
Posted at http://www.ietf.org/mail-archive/web/secdir/current/msg00762.html
Draft last updated 2009-07-03
Review closed: 2009-07-03

Review
review-ietf-pwe3-vccv-bfd-secdir-lc-harkins-2009-07-03

  I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

  This draft adds some new types verify connectivity and signal fault
detection or fault status over a Pseudowire. It states that it introduces
no new security issues beyond those defined in RFC 5085 and a couple of
I-Ds on Bidirectional Forwarding Detection (BFD) and that seems to be
correct. I see no security issues with this draft.

  On a non-security issue though, it appears that when doing IP
encapsulation of BFD it sends to a randomly selected IP address from the
loopback. I always thought that a loopback address MUST NOT appear outside
a router or host. Has that changed or am I misunderstanding something
about this draft?

  regards,

  Dan.