Re: [6lowpan] 6lowpan-nd version 2

"JinHyeock Choi" <jinchoe11@gmail.com> Mon, 10 July 2006 14:21 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fzwdn-0000KD-Ny; Mon, 10 Jul 2006 10:21:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fzwdm-0000K8-W0 for 6lowpan@ietf.org; Mon, 10 Jul 2006 10:21:38 -0400
Received: from wx-out-0102.google.com ([66.249.82.194]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fzwdk-0001ev-LG for 6lowpan@ietf.org; Mon, 10 Jul 2006 10:21:38 -0400
Received: by wx-out-0102.google.com with SMTP id i26so1694752wxd for <6lowpan@ietf.org>; Mon, 10 Jul 2006 07:21:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qoZ2lRRx5FadvSNGnMzoOML34kW85v6HfNN0j59jgGx9pJq69U6SC9JOdGiVAIx35DVLrtYQmK6StAtbJFmay0IuL2MhnmnbK6kvk23Wpp4fZ3nvL9M3GP9MbL4BrSq2O5bhcqKwQdFHVZ0Bt4OxG57bKZiY21qkJ0xbS0DTwFE=
Received: by 10.70.32.7 with SMTP id f7mr5478510wxf; Mon, 10 Jul 2006 07:21:35 -0700 (PDT)
Received: by 10.70.28.18 with HTTP; Mon, 10 Jul 2006 07:21:35 -0700 (PDT)
Message-ID: <e8c51d9b0607100721y3175bb38x8d52388354987652@mail.gmail.com>
Date: Mon, 10 Jul 2006 15:21:35 +0100
From: JinHyeock Choi <jinchoe11@gmail.com>
To: Samita Chakrabarti <samitac2@gmail.com>
Subject: Re: [6lowpan] 6lowpan-nd version 2
In-Reply-To: <43b91d370607071659n1fada033xfb521ca5a2132c46@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <43b91d370606261905k4409d643u27fdc0fc5a4d0d39@mail.gmail.com> <20060627025420.49130.qmail@web60317.mail.yahoo.com> <e8c51d9b0607050106i19aa94b9p8bad437537fd92cc@mail.gmail.com> <43b91d370607071659n1fada033xfb521ca5a2132c46@mail.gmail.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: 6lowpan@ietf.org
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
Errors-To: 6lowpan-bounces@ietf.org

Dear Samita

Thanks for your clarification.

>> The above is possible only after DAD is completed, which results in
>> delay. How about including 'Tentative Option' instead?
>>
> Are you talking about Optimized DAD?

yes.

> How much time should we be saving?

1 sec by default.

> Will it be worth the extra code ?

It depends. :-)

> This document is only concerned with the base ND changes.

I see.

>> >   Since every host sends a RS when it attaches to the PAN and there is
>> >   a single router for the PAN (the PAN co-ordinator), this router will
>> >   observe the arrival of all the IPv6 link local addresses
>>
>> This may not be so. Allow me an example. When a host attaches to a
>> network, while performing DAD, it may receive an unsolicited
>> (periodic) RA. Then the host would not send an RS. Also the host may
>> generate a new (link-local) address while staying at the same link for
>> the privacy reason. Then it would simply configure a new address
>> without sending an RS.
>
> In case of LowPan-ND, we are requiring to send unicast RS to the IPv6-router.
> We have not decided whether DAD should be mandatory for these devices or not.
> Since this draft assumes each node has EUI-64 addresses, DAD may not be
> required in theory. But in practice, it may choose to do DAD through
> the Ipv6-router.
> However, it will not receive unsolicited RA while waiting on DAD, because in
> this ND-extension RA will happen (most likely) through unicast L2 messages.
> Since both the DAD and RA will be sent by the same Ipv6 router, I'd assume
> they will happen in sequence. But due to radio link issues, we cannot guarantee
> that one will reach the destination always in sequence. Perhaps, we
> need to re-word the above mentioned text to clarify "observe the
> arrival..." part of the sentence.

ok.

>> How about monitoring the incoming DAD NS to generate the list instead?
>> That's the approach WiMAX takes right now.
>
> Will discuss that. As mentioned above that DAD may not be mandatory.

ok.

>> >   Firstly, it might very well be possible to increase the default time
>> >   significantly as long as the hosts can use some other mechanism to
>> >   detect when the router (the PAN co-ordinator) disappears.
>>
>> We also try to increase the maximum of MaxRtrAdvInterval.
>
> What was the value?  Which draft is it in?


> Sorry, that sentence is problematic. We are missing a punctuation.
>
> It means that DAD means broadcast in 802.15.4 network and should we
> skip DAD for 802.15.4 network?

ok.

>> >                             This RS message MUST carry sender's
>> >   link-layer address (SLLA) option.
>>
>> If the RS is sent before completing DAD, it can't carry SLAA. In that
>> case it may carry Tentative Option.
>
> Can you please point me to the Tentative Option document?

http://www.ietf.org/internet-drafts/draft-ietf-dna-tentative-00.txt

Take notice that the draft is planned to be merged into a single DNA draft.

>> In WiMAX, the router would not send a Redirect message. Usually L2
>> address is not used for data forwarding inside a link. In WiMAX, an MS
>> has only an AR, a default router, as its on-link neighbor.
>
> Please see section 10 of this draft for application on other technologies.
> RFC2461 actually recommends using off-link RA advertisements for
> the non-broadcast/non-multicast networks neighbor soliciation. This is
> not new in this draft.

I see.

>> As I wrote the above, an MS has only its AR as its on-link neighbor in
>> its Neighbor Cache. So I don't think it's necessary for AR to relay an
>> address resolution query.
>
> So, according to your description,  each MS is off-link to the other.
> So any packet has to be forwarded to the AR first. It sounds like
> the AR needs to have a different IPv6 link and L2 link (for each MS),
> such that an IPv6-link consists of multiple MSes.
> So, if AR follows IPv6 neighbor discovery it should advertise RA with L=0
> and all data packets are forwarded through it like a star topology in 6lowpan.

yes.

> Thanks for pointing out the differences in Wimax technology. As I mentioned
> before, this draft only provides guidelines for other technolgies so that
> mimimal change is required to adopt IPv6 ND on other non-broadcast/multicast
> networks.

I see.

Thanks for your kind consideration.

Best Regards

JinHyeock

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan