Re: [6lowpan] Fundamental concerns about 6lowpan ND
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [6lowpan] Fundamental concerns about 6lowpan ND
- To: "Pascal Thubert (pthubert)" <pthubert at cisco.com>, "Carsten Bormann" <cabo at tzi.org>, "Brian Haberman" <brian at innovationslab.net>, <bob.hinden at gmail.com>
- Subject: Re: [6lowpan] Fundamental concerns about 6lowpan ND
- From: "Mathilde Durvy (mdurvy)" <mdurvy at cisco.com>
- Date: Wed, 14 Oct 2009 19:15:55 +0200
- Authentication-results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
- Cc: 6lowpan <6lowpan at ietf.org>, Samita Chakrabarti <samitac at ipinfusion.com>
- Delivered-to: 6lowpan at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mdurvy at cisco.com; l=2250; q=dns/txt; s=sjiport06001; t=1255540559; x=1256750159; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Mathilde=20Durvy=20(mdurvy)"=20<mdurvy at cisco.co m>|Subject:=20RE:=20[6lowpan]=20Fundamental=20concerns=20 about=206lowpan=20ND|Date:=20Wed,=2014=20Oct=202009=2019: 15:55=20+0200|Message-ID:=20<8A977BDC5A7B0E429B0F521E8D6F 91EE7AA8EA at XMB-AMS-103.cisco.com>|To:=20"Pascal=20Thubert =20(pthubert)"=20<pthubert at cisco.com>,=0D=0A=20=20=20=20 =20=20=20=20"Carsten=20Bormann"=20<cabo at tzi.org>,=0D=0A =20=20=20=20=20=20=20=20"Brian=20Haberman"=20<brian at innov ationslab.net>,=20<bob.hinden at gmail.com>|Cc:=20"6lowpan" =20<6lowpan at ietf.org>,=0D=0A=20=20=20=20=20=20=20=20"Sami ta=20Chakrabarti"=20<samitac at ipinfusion.com> |MIME-Version:=201.0|Content-Transfer-Encoding:=20quoted- printable|In-Reply-To:=20<6A2A459175DABE4BB11DE2026AA50A5 D6DD112 at XMB-AMS-107.cisco.com>|References:=20<B6DBCBF27DE B1047AD57F03F217B106155FB0E at XMB-AMS-113.cisco.com><B1F71F 71-E743-4D01-89F7-60F00A82CCE8 at cisco.com><4AD4E311.809000 4 at innovationslab.net><B6DBCBF27DEB1047AD57F03F217B10615AF FB1 at XMB-AMS-113.cisco.com><B1FAB468-695C-475D-940D-5B73EF 852B70 at tzi.org>=20<6A2A459175DABE4BB11DE2026AA50A5D6DD112 @XMB-AMS-107.cisco.com>; bh=D/rZzsagA7pl0a0A2XlRPXUUVIWU8IVo1dlWOXaKd4E=; b=StykYhOv1XUnQof/REquksYay7Uvx5fuOxmUjliV12awfG4mV3Y1CPbw DNkLFaT6/Y/xjBeUAGFPYelNm2HQlfZ9ENXzyT49DW0VNw9C/r7OD8+E0 HVQ5wPRU2vLXq/7CrRW4LLwBRZACHQBTtv0gnWlEHfeno43wD+tVCSrD3 Q=;
- In-reply-to: <6A2A459175DABE4BB11DE2026AA50A5D6DD112 at XMB-AMS-107.cisco.com>
- List-archive: <http://www.ietf.org/mail-archive/web/6lowpan>
- List-help: <mailto:6lowpan-request@ietf.org?subject=help>
- List-id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
- List-post: <mailto:6lowpan@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
- References: <B6DBCBF27DEB1047AD57F03F217B106155FB0E at XMB-AMS-113.cisco.com><B1F71F71-E743-4D01-89F7-60F00A82CCE8 at cisco.com><4AD4E311.8090004 at innovationslab.net><B6DBCBF27DEB1047AD57F03F217B10615AFFB1 at XMB-AMS-113.cisco.com><B1FAB468-695C-475D-940D-5B73EF852B70 at tzi.org> <6A2A459175DABE4BB11DE2026AA50A5D6DD112 at XMB-AMS-107.cisco.com>
- Thread-index: AcpM2t65fq4caIjbRtaO4hJxquJKSwAApOiwAAQwgoA=
- Thread-topic: [6lowpan] Fundamental concerns about 6lowpan ND
Hi Pascal, Brian,
A few comments below:
> ... RFC 2491 was written to capture those interfacing functions needed
> to allow NDP and such to operate correctly.
[Pascal] RFC 2491 expects a MARS based service to enable a multicast
emulation for ND and present a common face to ND.
So we do something similar with a registrar of sorts, but a lot simpler
and more economical as it is integrated in ND.
[Mathilde] This does not sound similar to me. In one case you emulate
multicast below ND; ND remains unchanged. In the other you redefine ND.
> Is it possible that standard IPv6 nodes could operate on a
> 6lowpan network as well as a more traditional (e.g., ethernet) one?
[Pascal] Another question is whether that is desirable. There are
assumptions behind classical NDP as described in RFC 4861. The farther
you go from those assumption, the least NDP as its stands applies, and
the more costly the adaptation layer becomes. Classical NDP being
optimized for potentially large transitive networks with a high degree
of trust and few specific destination. It is based on assumptions
like...
[Mathilde] What about a router with two interfaces, one Ethernet and one
802.15.4. With the current proposal this router will need two
implementation of ND, 4861 on the Ethernet interface and 6lowpan-ND on
the other.
An important implication is that we need to modify the OS (where ND is
implemented) of exiting computers / routers / etc to allow them to use a
802.15.4 interface.
>> ... Yet, IPv6 over 802.11 works relatively well.
[Pascal] Certainly not on flat 802.11 (aka adhoc mode)...
[Mathilde] So is there a strong push from 802.11 vendors to redefine ND?
I didn't hear anything on this list.
[Pascal] My conclusion:
Yes, we are definitely interested in bringing our NDP extension to a
larger audience because:
- a whole industry is waiting for us; that industry can hardly accept a
solution that would be constrained to a single type of interface
[Mathilde] If a 'larger audience' is needed, I definitely think that
this work should not be done in 6lowpan as it is clearly focusing on
802.15.4 and I'm not sure the whole industry is aware of the effort.
Best,
Mathilde
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.