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

Sri Gundavelli <sgundave@cisco.com> Sun, 11 September 2011 18:15 UTC

Return-Path: <sgundave@cisco.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 55BFE21F889A for <netext@ietfa.amsl.com>; Sun, 11 Sep 2011 11:15:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.081
X-Spam-Level:
X-Spam-Status: No, score=-2.081 tagged_above=-999 required=5 tests=[AWL=-0.878, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
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 TX-2uEk5Xar3 for <netext@ietfa.amsl.com>; Sun, 11 Sep 2011 11:15:03 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 9751521F888A for <netext@ietf.org>; Sun, 11 Sep 2011 11:15:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=5097; q=dns/txt; s=iport; t=1315765025; x=1316974625; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=HLMZrhtSdgYmMjv4AmwMMv1nHAMC/+08BOKWELPWHf8=; b=IyxeX0nOOecx4b6g5Nq2YM1O25ApS1a3NfGcPqN/TO2gcjqpI4nouWsJ 4WgwAVeNpGtLjyACRDGb42I0u71ZtS9LYNLYan6Zk6Vp6lGLiqmrzT3mL oJIseGLeL4f7i8A66VG6BghEhC8NsKfVjdEBtw7iW4NLwJY58czAn9jJ0 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgGADz6bE6rRDoG/2dsb2JhbABBoV+FPH94gVIBAQQBAQEBDwEpATELBQ0BCBhPBjABAQQOBQkZh1UElzgBnGCGbgSHPi+LToUghGiHNg
X-IronPort-AV: E=Sophos;i="4.68,364,1312156800"; d="scan'208";a="1436090"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 11 Sep 2011 18:17:04 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p8BIH4GB006635; Sun, 11 Sep 2011 18:17:04 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 11 Sep 2011 11:17:04 -0700
Received: from 10.32.246.213 ([10.32.246.213]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ; Sun, 11 Sep 2011 18:17:03 +0000
User-Agent: Microsoft-Entourage/12.30.0.110427
Date: Sun, 11 Sep 2011 11:16:59 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Julien Laganier <julien.ietf@gmail.com>
Message-ID: <CA92492B.280FF%sgundave@cisco.com>
Thread-Topic: [netext] I-D Action: draft-ietf-netext-logical-interface-support-03.txt
Thread-Index: Acxwrv7lEKIN0cvaq0WQEsFjAeMooA==
In-Reply-To: <CAE_dhjsPkif2AzdUdOEUw1=DjWrZ0vHw58EFvjtdoVjRmHLpwg@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 11 Sep 2011 18:17:04.0378 (UTC) FILETIME=[021A7DA0:01CC70AF]
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: Sun, 11 Sep 2011 18:15:04 -0000

Yes. There is the proposed text from you. Thanks !

There was also a comment on ND layer considerations when presenting multiple
peers on the other side of the p2p link as a single peer. Else, it should be
fine. 


Regards
Sri



On 9/9/11 9:35 AM, "Julien Laganier" <julien.ietf@gmail.com> wrote:

> 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-sup
>>>> po
>>>> 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-supp
>>>> or
>>>> 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
>> 
>>