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

Julien Laganier <julien.ietf@gmail.com> Fri, 09 September 2011 16:33 UTC

Return-Path: <julien.ietf@gmail.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CF9621F8715 for <netext@ietfa.amsl.com>; Fri, 9 Sep 2011 09:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.517
X-Spam-Level:
X-Spam-Status: No, score=-3.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AIVjeaA91f7e for <netext@ietfa.amsl.com>; Fri, 9 Sep 2011 09:33:50 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id D183521F850B for <netext@ietf.org>; Fri, 9 Sep 2011 09:33:42 -0700 (PDT)
Received: by wwf5 with SMTP id 5so888918wwf.13 for <netext@ietf.org>; Fri, 09 Sep 2011 09:35:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=I0Yhc49zDoW0txHai/ni4PaQn6xexrf99ajbuEBPHCA=; b=SG2jlVpuhoRtoDNTk7O38QymrwM19ME+dNrbxXuFTjsE1ExI9aiT6Vb0PY/C5saM0d EO/hmU4IEsXRfOrqW04CMeO1LLhcaBUxTxs8wyu58HIG9C+STPLaIgIo7ZEM/vqCgBY2 iaGfCrFzseedJgY7nrvAqMJyTp99jg8kaHTcM=
MIME-Version: 1.0
Received: by 10.227.151.66 with SMTP id b2mr2224904wbw.44.1315586134429; Fri, 09 Sep 2011 09:35:34 -0700 (PDT)
Received: by 10.227.27.141 with HTTP; Fri, 9 Sep 2011 09:35:34 -0700 (PDT)
In-Reply-To: <CA8EE559.27E7F%sgundave@cisco.com>
References: <CAE_dhjvw1iS=+Yd=p8mdh3Lnhv1dubQBjg+9uuHGJNJSk+hJQw@mail.gmail.com> <CA8EE559.27E7F%sgundave@cisco.com>
Date: Fri, 9 Sep 2011 09:35:34 -0700
Message-ID: <CAE_dhjsPkif2AzdUdOEUw1=DjWrZ0vHw58EFvjtdoVjRmHLpwg@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: Sri Gundavelli <sgundave@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: netext@ietf.org
Subject: Re: [netext] I-D Action: draft-ietf-netext-logical-interface-support-03.txt
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Sep 2011 16:33:50 -0000

We have discussed this extensively during meetings and on list and
this was the proposal on the table:

http://www.ietf.org/mail-archive/web/netext/current/msg01944.html

--julien

On Thu, Sep 8, 2011 at 9:34 PM, Sri Gundavelli <sgundave@cisco.com> wrote:
> Hi Julien,
>
> I know we discussed about this during the meeting, on wow the logical
> interface should appear to the applications. You preferred to not to state
> any thing. I was ok with that, I just wanted to check the socket API, and if
> there is any API which provides the type (p2p or non-p2p), based on that we
> can resolve this. Let me work on this.
>
>
>
> Regards
> Sri
>
>
>
>
>
>
>
> On 9/8/11 9:04 AM, "Julien Laganier" <julien.ietf@gmail.com> wrote:
>
>> 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-
>>    interface.
>>
>> On Mon, Sep 5, 2011 at 9:15 AM,  <internet-drafts@ietf.org> 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:
>>> http://www.ietf.org/internet-drafts/draft-ietf-netext-logical-interface-suppo
>>> rt-03.txt
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> This Internet-Draft can be retrieved at:
>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-netext-logical-interface-suppor
>>> t-03.txt
>>> _______________________________________________
>>> netext mailing list
>>> netext@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netext
>>>
>> _______________________________________________
>> netext mailing list
>> netext@ietf.org
>> https://www.ietf.org/mailman/listinfo/netext
>
>