Skip to main content

Last Call Review of draft-ietf-netext-logical-interface-support-12
review-ietf-netext-logical-interface-support-12-secdir-lc-kelly-2016-02-04-00

Request Review of draft-ietf-netext-logical-interface-support
Requested revision No specific revision (document currently at 14)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2016-02-05
Requested 2016-02-02
Authors Telemaco Melia , Sri Gundavelli
I-D last updated 2016-02-04
Completed reviews Genart Last Call review of -12 by Ron Bonica (diff)
Secdir Last Call review of -12 by Scott G. Kelly (diff)
Opsdir Last Call review of -12 by Jürgen Schönwälder (diff)
Assignment Reviewer Scott G. Kelly
State Completed
Request Last Call review on draft-ietf-netext-logical-interface-support by Security Area Directorate Assigned
Reviewed revision 12 (document currently at 14)
Result Has issues
Completed 2016-02-04
review-ietf-netext-logical-interface-support-12-secdir-lc-kelly-2016-02-04-00
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.

From the abstract, this Informational document explains the operational details
of [sic] Logical-interface construct and the specifics on how the link-layer
implementations hide the physical interfaces from the IP stack and from the
network nodes on the attached access networks.

The brief security considerations section says the implementation on the host
is not visible to the network and does not require any special security
considerations. One thing that occurred to me when I read this is that if
someone is depending on link layer security (e.g. 802.11i) for any reason, then
there may be security implications to switching the exit interface. Not sure if
this is important - I'll leave it to the ADs to decide.