Re: [netext] #4: Logical interface support: Point to point links

Sri Gundavelli <sgundave@cisco.com> Mon, 14 March 2011 22:22 UTC

Return-Path: <sgundave@cisco.com>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76FA53A6D74 for <netext@core3.amsl.com>; Mon, 14 Mar 2011 15:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.149
X-Spam-Level:
X-Spam-Status: No, score=-10.149 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aXIoleZrC0cl for <netext@core3.amsl.com>; Mon, 14 Mar 2011 15:22:01 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id A23A63A6978 for <netext@ietf.org>; Mon, 14 Mar 2011 15:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=2950; q=dns/txt; s=iport; t=1300141394; x=1301350994; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=ejz/uQh6lWqrlq0ag2WzRyFKxRyiPczX5W8fdW+Zr58=; b=UOmz3oQFSCyQe4tvnfLZZLCd7KalheWpAraQ80kYQyL8ge/qiJhvfhj1 2qKT3EF8tSNJW4wYg68zcohn/ckBDx7QdvImAIlf3u+okZM4kdOnX2IIB GZWE/hPas+uZE5SdrlLXlxBBgZ0lSutBx1NlbP8zzB5jKm5A9JksZ/jb9 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcGAF8yfk2tJV2a/2dsb2JhbACZBo0Hd6RtnDiFYgSFK4cng1Q
X-IronPort-AV: E=Sophos;i="4.62,319,1297036800"; d="scan'208";a="225576672"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-2.cisco.com with ESMTP; 14 Mar 2011 22:23:13 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2EMN7kJ002589 for <netext@ietf.org>; Mon, 14 Mar 2011 22:23:13 GMT
Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Mar 2011 15:22:41 -0700
Received: from 10.32.246.213 ([10.32.246.213]) by xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) with Microsoft Exchange Server HTTP-DAV ; Mon, 14 Mar 2011 22:22:40 +0000
User-Agent: Microsoft-Entourage/12.28.0.101117
Date: Mon, 14 Mar 2011 15:24:29 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: netext@ietf.org
Message-ID: <C9A3E3AD.135AF%sgundave@cisco.com>
Thread-Topic: [netext] #4: Logical interface support: Point to point links
Thread-Index: AcvilpVrmDU4NCZvYkyaf3ogiAFeBA==
In-Reply-To: <066.44c02c04592a11d868774e78f7db352d@trac.tools.ietf.org>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 14 Mar 2011 22:22:41.0243 (UTC) FILETIME=[5530E2B0:01CBE296]
Subject: Re: [netext] #4: Logical interface support: Point to point links
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Mon, 14 Mar 2011 22:22:03 -0000

> #4: Logical interface support: Point to point links

 Clarify the use and
> behavior of the logical interface on PtP links.


Folks: Again, reflecting the team's contributions on this topic, the authors
of this document have discussed this and resolve it with the following text.
The key points we tried to reflect are around that the logical interface
appears to the application as a shared link. There were thoughts around
making it appear like a p2p link, given that there are multiple neighbors on
each sub interface, this choice appears reasonable. With respect to how a
packet is transmitted, is still based on the chosen link model at each sub
interface level. Let us know, if you see any issues with it. This is proven
based on the multiple implementations from some of the co-authors of this
doc.




---
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 3/3/11 9:17 AM, "netext issue tracker" <trac+netext@trac.tools.ietf.org>
wrote:

> #4: Logical interface support: Point to point links

 Clarify the use and
> behavior of the logical interface on PtP links.

--
> 
---------------------------------------+------------------------------------

> Reporter:  basavaraj.patil@Š          |       Owner:  telemaco.melia@Š
> 
     Type:  defect                     |      Status:  new
> 
 Priority:  major                      |   Milestone:
> 
Component:  logical-interface-support  |     Version:
> 
 Severity:  -                          |    Keywords:
> 
---------------------------------------+------------------------------------

> 
Ticket URL: <http://trac.tools.ietf.org/wg/netext/trac/ticket/4>
netext
> <http://tools.ietf.org/netext/>

_____________________________________________
> __
netext mailing
> list
netext@ietf.org
https://www.ietf.org/mailman/listinfo/netext