Re: [6lowpan] Fwd: New Version Notification fordraft-chakrabarti-6lowpan-ipv6-nd-simple-00
Jonathan Hui <jhui@archrock.com> Tue, 23 March 2010 21:44 UTC
Return-Path: <jhui@archrock.com>
X-Original-To: 6lowpan@core3.amsl.com
Delivered-To: 6lowpan@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51C7D3A6816 for <6lowpan@core3.amsl.com>; Tue, 23 Mar 2010 14:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level:
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 Zv2ssIbLOCfk for <6lowpan@core3.amsl.com>; Tue, 23 Mar 2010 14:44:01 -0700 (PDT)
Received: from mail.sf.archrock.com (mail.sf.archrock.com [216.121.16.71]) by core3.amsl.com (Postfix) with ESMTP id 86AC33A67F2 for <6lowpan@ietf.org>; Tue, 23 Mar 2010 14:44:01 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sf.archrock.com (Postfix) with ESMTP id 4184DAF835; Tue, 23 Mar 2010 14:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
Received: from mail.sf.archrock.com ([127.0.0.1]) by localhost (mail.sf.archrock.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wlX7D+0iXO0; Tue, 23 Mar 2010 14:44:16 -0700 (PDT)
Received: from dhcp-wireless-open-abg-24-97.meeting.ietf.org (dhcp-wireless-open-abg-24-97.meeting.ietf.org [130.129.24.97]) by mail.sf.archrock.com (Postfix) with ESMTP id 8BCC0AF81F; Tue, 23 Mar 2010 14:44:16 -0700 (PDT)
Message-Id: <BDE6C079-BC9E-4734-B5A5-4648A4FCE3B5@archrock.com>
From: Jonathan Hui <jhui@archrock.com>
To: Erik Nordmark <erik.nordmark@sun.com>
In-Reply-To: <4BA92EC6.30200@sun.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 23 Mar 2010 14:44:14 -0700
References: <4B8BBE45.4080402@sun.com> <8A977BDC5A7B0E429B0F521E8D6F91EE01A589F8@XMB-AMS-103.cisco.com> <4BA92EC6.30200@sun.com>
X-Mailer: Apple Mail (2.936)
Cc: 6lowpan <6lowpan@ietf.org>
Subject: Re: [6lowpan] Fwd: New Version Notification fordraft-chakrabarti-6lowpan-ipv6-nd-simple-00
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 21:44:02 -0000
Hi Erik, On Mar 23, 2010, at 2:12 PM, Erik Nordmark wrote: > On 03/22/10 10:45 AM, Mathilde Durvy (mdurvy) wrote: >> Hi Erik, Samita, >> >> Thanks for your draft. This proposal is much closer to what I had >> in mind >> myself and I feel this is a great step forward! >> >> I have a few questions / comments: >> - Assumptions: why do you assume that 6LR use RA to configure their >> global >> addresses while host are allowed to use DHCPv6? In IPv6, routers are >> typically ignoring received RAs... It is not very clear whether your >> proposal allows the case where all addresses (host and 6LR) are >> assigned >> using DHCPv6. It might also be that in a route-over situation the >> routing >> protocol itself would take care of distributing well chosen >> prefixes/addresses to allow prefix aggregation in routing tables or >> routing >> messages. > > We just borrowed this from draft-ietf-6lowpan-nd-08. > > As I said during the presentation yesterday, I think the key thing > to standardize around ND is the host-router interaction. This router- > border interaction is, as you point out, something that can be done > in different ways. > > I think it makes sense to provide an optional way to perform the > router-border interaction as part of the ND work, while making it > clear that there are other ways to do those pieces such as the > routing protocol. > > But I don't think DHCPv6 can be used to assign the same prefix to > all the routers in the 6lowpan (DHCP prefix delegation would give > them all different prefixes which is not what we want.) I think Mathilde was referring to using DHCPv6 to assign only IPv6 addresses (not prefixes) and that the only router-border interaction is through the use of DHCPv6 relay agents. I agree that DHCPv6 prefix delegation in 6LoWPAN networks doesn't make much sense in most situations. -- Jonathan Hui
- [6lowpan] Fwd: New Version Notification for draft… Erik Nordmark
- Re: [6lowpan] Fwd: New Version Notification for d… Zach Shelby
- Re: [6lowpan] Fwd: New Version Notification for d… Erik Nordmark
- Re: [6lowpan] Fwd: New Version Notification for d… Zach Shelby
- Re: [6lowpan] Fwd: New Version Notification for d… Erik Nordmark
- Re: [6lowpan] Fwd: New Version Notification fordr… Mathilde Durvy (mdurvy)
- Re: [6lowpan] Fwd: New Version Notificationfordra… Pascal Thubert (pthubert)
- Re: [6lowpan] Fwd: New Version Notificationfordra… Mathilde Durvy (mdurvy)
- Re: [6lowpan] Fwd: New Version Notification fordr… Erik Nordmark
- Re: [6lowpan] Fwd: New Version Notificationfordra… Pascal Thubert (pthubert)
- Re: [6lowpan] Fwd: New Version Notification fordr… Jonathan Hui
- Re: [6lowpan] Fwd: New Version Notification fordr… Samita Chakrabarti
- Re: [6lowpan] Fwd: New Version Notification fordr… Mathilde Durvy (mdurvy)
- Re: [6lowpan] Fwd: New Version Notification fordr… Erik Nordmark