Logical Interface (LIF) Implementation Guidelines
draft-zuniga-mif-lif-implementation-guidelines-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Juan-Carlos Zúñiga , Telemaco Melia | ||
| Last updated | 2010-10-18 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Juan-Carlos Zúñiga
Telemaco Melia
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)