Re: [netext] #3: Logical Interface: Use of the Virtual LLID

Sri Gundavelli <sgundave@cisco.com> Mon, 14 March 2011 22:32 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 6CDE73A6D75 for <netext@core3.amsl.com>; Mon, 14 Mar 2011 15:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.183
X-Spam-Level:
X-Spam-Status: No, score=-10.183 tagged_above=-999 required=5 tests=[AWL=0.416, 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 1oGxHWiu2wJd for <netext@core3.amsl.com>; Mon, 14 Mar 2011 15:32:27 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 5F2943A6FD3 for <netext@ietf.org>; Mon, 14 Mar 2011 15:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=2012; q=dns/txt; s=iport; t=1300142017; x=1301351617; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=xClPEXKYQ49pF6H4eFX9lIfVxUsCadvf27BZyvk5pec=; b=YbqpSACczjfRmw+zn7G9NoNfokG7UYv9K3CDhoE0co9UaiklH3LDfzSq 66/TIu3BkSw4lhuAum22taod2GPjxjs73952HvxYaA/DpoIL0CfWMfxfg 6mEl/1XIG7cdFzr2Yg7Z1Xacswnkw+PaP1loHYe+qmPFgkqbcydpGlu/h c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcGAAI0fk2tJV2Z/2dsb2JhbACZBo0Hd6RpnDiFYgSFK4cng1Q
X-IronPort-AV: E=Sophos;i="4.62,319,1297036800"; d="scan'208";a="320225087"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by sj-iport-2.cisco.com with ESMTP; 14 Mar 2011 22:33:37 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2EMXbrs028354; Mon, 14 Mar 2011 22:33:37 GMT
Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Mar 2011 15:33:36 -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:33:35 +0000
User-Agent: Microsoft-Entourage/12.28.0.101117
Date: Mon, 14 Mar 2011 15:35:23 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: netext@ietf.org
Message-ID: <C9A3E63B.135B7%sgundave@cisco.com>
Thread-Topic: [netext] #3: Logical Interface: Use of the Virtual LLID
Thread-Index: AcvimBs7blf7gtIPJ0uMTj78sxo6Uw==
In-Reply-To: <066.d2b1a47b864e8340579c7215fdc00464@trac.tools.ietf.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 14 Mar 2011 22:33:36.0805 (UTC) FILETIME=[DBEFB550:01CBE297]
Cc: draft-ietf-netext-logical-interface-support@tools.ietf.org
Subject: Re: [netext] #3: Logical Interface: Use of the Virtual LLID
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:32:28 -0000

> #3: Logical Interface: Use of the Virtual LLID


There were quite a few discussion on this among the authors. Looking things
are done WiMAX, CDMA and LTE. It appeared logical to allow both the use of a
neutral link-layer identifier, or adopt one of the link-layer identifier
from its sub-interfaces.  We may have to add some text around SEND
considerations. This section can go through some updates. Few need to
reflect few comments from Yokota-san and others ... Its not complete. It
shows where we are heading.



--
6.4.  Link-layer Identifier of a Logical Interface

   The logical Interface may or may not use the link-layer identifier
   from one of its sub-interfaces.  Following are the considerations.

   o  In access architectures where it is possible to adopt a virtual
      link-layer identfier and use it for layer-2 communications in any
      of the access networks, a virtual identifier (VLL-Id) may be used.
      The specifics on how that identifier is chosen is out side the
      scope of this document.  This identifier may be used for all link-
      layer communications.  This identifier may also be used for
      generating IPv6 global or link-local addresses on that interface.

   o  In access architectures, where the link-layer identifier is
      associated with a specific access technology, it will not be
      possible for the logical interface to adopt a virtual identifier
      and it use it across different access networks.  In such networks,
      the logical interface must adopt the identifier of the respective
      sub-interface through which a packet is being transmitted.
--
 




On 3/3/11 9:16 AM, "netext issue tracker" <trac+netext@trac.tools.ietf.org>
wrote:

> #3: Logical Interface: Use of the Virtual LLID
> 
>  Clarify the use of virtual LLID and how this is used in the scope of
>  PMIP6.
>  Discuss the solution and propose text and ensure there is clear consensus
>  before you can close this issue.