Re: [netext] #1: Behavior of ND
Sri Gundavelli <sgundave@cisco.com> Mon, 14 March 2011 22:14 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 9C8B73A6B24 for <netext@core3.amsl.com>; Mon, 14 Mar 2011 15:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.129
X-Spam-Level:
X-Spam-Status: No, score=-10.129 tagged_above=-999 required=5 tests=[AWL=0.470, 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 XwOwl+yr5USH for <netext@core3.amsl.com>; Mon, 14 Mar 2011 15:14:34 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 93E0A3A6978 for <netext@ietf.org>; Mon, 14 Mar 2011 15:14:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=2746; q=dns/txt; s=iport; t=1300140959; x=1301350559; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=cNIJpQnhHT5rEOhaUlWxWTg0ztfaW4CfpuYLwog+MiY=; b=eUPQ8Q0WUfGl2M3D4IHGz0rBQMG9A9QzI6m2UBHjG6GN65FPS9VGqZ9T 5amOqZJlr6aDhzQqpwVX7ZP5Ylmehg6BVhjYykasdSwg6KlUK1h7UCt5S AFZ+wla4HKa1Q3MNpNenL5Z4P0WWJQfz12akeId0NowW99M7Bc2J3XzA7 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkINAAcwfk2tJXG8/2dsb2JhbACZBoYxhlZ3pHacOYViBIUrhyeDVA
X-IronPort-AV: E=Sophos;i="4.62,319,1297036800"; d="scan'208";a="277900279"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by sj-iport-3.cisco.com with ESMTP; 14 Mar 2011 22:15:58 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2EMFwum025022; Mon, 14 Mar 2011 22:15:58 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:15:57 -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:15:56 +0000
User-Agent: Microsoft-Entourage/12.28.0.101117
Date: Mon, 14 Mar 2011 15:17:42 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: netext@ietf.org
Message-ID: <C9A3E216.135A6%sgundave@cisco.com>
Thread-Topic: [netext] #1: Behavior of ND
Thread-Index: AcvilaLUZBtBd0KjkkiHnmqKMBVjiw==
In-Reply-To: <066.e9f936f62456f0a0d9c6a916f3c93be2@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:15:57.0808 (UTC) FILETIME=[64B99700:01CBE295]
Cc: draft-ietf-netext-logical-interface-support@tools.ietf.org
Subject: Re: [netext] #1: Behavior of ND
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:14:35 -0000
> #1: Behavior of ND > Folks: The authors of this document have discussed this and resolve it with the following text. Please comment, if you see any open issues. This captures the ND interactions around logical interface, for various message types. Might be missing one or two other details, we can capture them. 6.5. ND Considerations for Logical Interface The following are the Neighbor Discovery related considerations for the logical interface. o Any Neighbor Discovery messages, such as Router Solicitation, Neighbor Solicitation messages that the host sends to a multicast destination address of link-local scope such as, all-nodes, all- routers, solicited-node multicast group addresses, using either an unspecified (::) source address, or a link-local address configured on the logical interface will be replicated and forwarded on each of the sub-interfaces under that logical interface. However, if the destination address is a unicast address and if that target is known to exist on a specific sub- interface, the message will be forwarded only on that specific sub-interface. o Any Neighbor Discovery messages, such as Router Advertisement, that the host receives from any of its sub-interfaces, will be associated with the logical interface, i.e., in some implementations the message will appear on the input interface of the logical interface. o When using Stateless Address Autoconfiguraion [RFC4862] for generating IPv6 address configuration on the logical interface, the host may use any of the IPv6 prefixes receieved from the Router Advertisement messages that it received from any of its sub-interfaces. Melia & Gundavelli Expires September 15, 2011 [Page 15] Internet-Draft Logical Interface Support March 2011 o The response to a Neighbor Discovery message received for a unicast, link-specific multicast group address, will be sent on the same sub-interface path where the packet was received. o When using DHCPv4 for obtaining address configuration for the logical interface, the value in the chaddr field in the DHCP messages will be based on the link-layer identfier scheme chosen by the logical interface. . On 3/2/11 2:05 PM, "netext issue tracker" <trac+netext@trac.tools.ietf.org> wrote: > #1: Behavior of ND > > At IETF79 there was a concern identified that the I-D did not clearly > explain the behavior of ND in the case of the logical interface on a host. > Please propose text that addresses this concern.
- [netext] #1: Behavior of ND netext issue tracker
- Re: [netext] #1: Behavior of ND Sri Gundavelli