Logical-Interface Support for IP Hosts with Multi-Access Support
draft-ietf-netext-logical-interface-support-14

[Ballot comment]
As mentioned by Jürgen Schönwälder in this OPS-DIR:

The 'grandfather' model for interfaces in the OPS world is RFC 2863
and RFC 7223 builds on that. I think your definitions are reasonably
compatible (except that the other models do not restrict a logical
interface to an IP interface). Perhaps it makes sense to discuss this
related work or at least provide pointers, e.g., add a paragraph at
the end of section 2 explaining how the terminology introduced here
relates to RFC 2863 and RFC 7223?

I also believe it would be a nice addition to the draft.

[Ballot comment]

I would have thought that noting that different layer 2
interfaces can have different security properties would be
worth noting, even if we might not want to recommend that
logical interfaces only group physical interfaces with
similar security properties (which may be an interesting
idea, but I can see it is also likely impractical today).

I note that the secdir review [1] raises the same issue but
I don't think there was a response to that. (If there was,
apologies, I didn't find it;-)

  [1] https://www.ietf.org/mail-archive/web/secdir/current/msg06352.html

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

IANA has reviewed draft-ietf-netext-logical-interface-support-12.txt, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any IANA actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, IANA does not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
IANA Specialist
ICANN

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: netext@ietf.org, brian@innovationslab.net, bpatil1+ietf@gmail.com, draft-ietf-netext-logical-interface-support@ietf.org, netext-chairs@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Logical-interface Support for Multi-access enabled IP Hosts) to Informational RFC


The IESG has received a request from the Network-Based Mobility
Extensions WG (netext) to consider the following document:
- 'Logical-interface Support for Multi-access enabled IP Hosts'
  as Informational
RFC

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-02-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


  A Logical-interface is a software semantic internal to the host
  operating system.  This semantic is available in all popular
  operating systems and is used in various protocol implementations.
  The Logical-interface support is required on the mobile node attached
  to a Proxy Mobile IPv6 domain, for leveraging various network-based
  mobility management features such as inter-technology handoffs,
  multihoming and flow mobility support.  This document explains the
  operational details of 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.  Furthermore, this document identifies the applicability of
  this approach to various link-layer technologies and analyzes the
  issues around it when used in conjunction with various mobility
  management features.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-netext-logical-interface-support/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-netext-logical-interface-support/ballot/


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