Re: [netext] I-D Action: draft-ietf-netext-logical-interface-support-03.txt

Julien Laganier <> Thu, 08 September 2011 16:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4908821F87FA for <>; Thu, 8 Sep 2011 09:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.518
X-Spam-Status: No, score=-3.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9lou9hoSUQls for <>; Thu, 8 Sep 2011 09:02:32 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5D5FA21F85EC for <>; Thu, 8 Sep 2011 09:02:32 -0700 (PDT)
Received: by ewy19 with SMTP id 19so447771ewy.31 for <>; Thu, 08 Sep 2011 09:04:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=/LbOaQERDClaA8X+hV8uB7jAgx+5FWGelzfWVq/qCR8=; b=qx1wqTo4HizhuPjIgyxpLVKs3tGqFF1A0Xu50mZl5LcDk08vgI2E3DPGqf4+WGmJrF 9spfazgItrp7zixksdgOBSU2t2Q/NRjamgWCKWWBek6SnueCF8Amz3aPA29OadGVbCGl jOZmhfQQ+YeRHxKw7NV+8PZIosaTTOf6cXNcY=
MIME-Version: 1.0
Received: by with SMTP id z9mr920387vdv.93.1315497863831; Thu, 08 Sep 2011 09:04:23 -0700 (PDT)
Received: by with HTTP; Thu, 8 Sep 2011 09:04:23 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Thu, 08 Sep 2011 09:04:23 -0700
Message-ID: <>
From: Julien Laganier <>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [netext] I-D Action: draft-ietf-netext-logical-interface-support-03.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 08 Sep 2011 16:02:33 -0000

I thought that we already discussed this and concluded it wasn't appropriate?

6.3.  Supported Link models for a logical interface

   The sub-interfaces of a logical interface can be bound to a point-to-
   point or a shared link (Example: LTE and WLAN).  The logical
   interface appears as a shared-link to the applications, and adapts to
   the link model of the sub-interface for packet communication.  For
   example, when transmitting a packet on a sub-interface which is
   attached to a p2p link, the transmission conforms to the p2p link
   model and when transmitting on a sub-interface attached to a shared
   link, the transmission conforms to the shared link model.

   Based on the link to which the sub-interface is attached to, the
   layer-2 resolutions may or may not be needed.  If the interface is
   bound to a P2P link with PPP running, there will not be any link-
   layer resolutions in the form of ARP/ND messages.  However, if the
   interface is bound to a shared link such as Ethernet, there will be
   ND resolutions.  The logical interface implementation has to maintain
   the required link model and the associated state for each sub-

On Mon, Sep 5, 2011 at 9:15 AM,  <> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network-Based Mobility Extensions Working Group of the IETF.
>        Title           : Logical Interface Support for multi-mode IP Hosts
>        Author(s)       : Telemaco Melia
>                          Sri Gundavelli
>        Filename        : draft-ietf-netext-logical-interface-support-03.txt
>        Pages           : 26
>        Date            : 2011-09-05
>   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
>   operating in 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 context with various
>   mobility management features.
> A URL for this Internet-Draft is:
> Internet-Drafts are also available by anonymous FTP at:
> This Internet-Draft can be retrieved at:
> _______________________________________________
> netext mailing list