<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.zuniga-mif-lif-implementation-guidelines" target="https://datatracker.ietf.org/doc/html/draft-zuniga-mif-lif-implementation-guidelines-00">
   <front>
      <title>Logical Interface (LIF) Implementation Guidelines</title>
      <author initials="J. C." surname="Zúñiga" fullname="Juan-Carlos Zúñiga">
         <organization>InterDigital Communications</organization>
      </author>
      <author initials="T." surname="Melia" fullname="Telemaco Melia">
         <organization>Alcatel-Lucent</organization>
      </author>
      <date month="October" day="18" year="2010" />
      <abstract>
	 <t>A Logical Interface is a software module internal to the host that is
available in all popular operating systems. The use of this Logical
Interface allows supporting different network-based mobility
management solutions. In the NETEXT WG, work has been carried out to
define ways in which a Logical Interface can help IP flow mobility
(IFOM) for Proxy Mobile IPv6 [I-D.draft-ietf-netext-logical-
interface-support]. The same Logical Interface construct can help
other mobility management solutions like 3GPP GPRS Tunnelling
Protocol (GTP), and it can add benefits to multi-access scenarios
such as 3GPP Multi Access PDN Connectivity (MAPCON). This document
provides guidelines for the implementation and configuration of a
generic Logical Interface.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-zuniga-mif-lif-implementation-guidelines-00" />
   
</reference>
