IETF Logo Mail Archive

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

Brian Haley <brian.haley@hp.com> Tue, 06 September 2011 13:34 UTC

Return-Path: <brian.haley@hp.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 5BE5321F886A for <netext@ietfa.amsl.com>; Tue, 6 Sep 2011 06:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.307
X-Spam-Level:
X-Spam-Status: No, score=-105.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 hJvqLgtoMROA for <netext@ietfa.amsl.com>; Tue, 6 Sep 2011 06:34:35 -0700 (PDT)
Received: from g6t0186.atlanta.hp.com (g6t0186.atlanta.hp.com [15.193.32.63]) by ietfa.amsl.com (Postfix) with ESMTP id BD81521F87D3 for <netext@ietf.org>; Tue, 6 Sep 2011 06:34:35 -0700 (PDT)
Received: from g5t0030.atlanta.hp.com (g5t0030.atlanta.hp.com [16.228.8.142]) by g6t0186.atlanta.hp.com (Postfix) with ESMTP id 1E6D72C031; Tue, 6 Sep 2011 13:36:22 +0000 (UTC)
Received: from [16.1.1.40] (squirrel.fc.hp.com [15.11.146.57]) by g5t0030.atlanta.hp.com (Postfix) with ESMTP id 9CC6B14154; Tue, 6 Sep 2011 13:36:21 +0000 (UTC)
Message-ID: <4E6621D4.4020407@hp.com>
Date: Tue, 06 Sep 2011 09:36:20 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: HP Cloud Services
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Lightning/1.0b2 Thunderbird/3.1.12
MIME-Version: 1.0
References: <20110905161510.5234.57634.idtracker@ietfa.amsl.com>
In-Reply-To: <20110905161510.5234.57634.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 06 Sep 2011 06:39:11 -0700
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: Tue, 06 Sep 2011 13:34:36 -0000

Hi Sri,

On 09/05/2011 12:15 PM, 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

I read this draft and had a comment on Section 6.5:

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.

I'm not sure about other OSes, but since you mentioned the Linux bonding driver
as an example of a Logical interface I can respond regarding that.  There are
configurations where you do NOT want to replicate a packet and forward it on all
the underlying physical interfaces.  Doing so can cause DAD failures if any of
the other interfaces see those packets sent to the all-nodes multicast address.
 We noticed and fixed that back in 2008.

BTW, I'm not subscribed to net-next, so haven't seen any previous discussion on
the draft.

-Brian

v2.23.0 | Report a Bug | By Email