
From my.mailing.acc@gmail.com  Fri Feb  3 09:32:52 2012
Return-Path: <my.mailing.acc@gmail.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEA5E21F855A for <6lowpan@ietfa.amsl.com>; Fri,  3 Feb 2012 09:32:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[AWL=0.980,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 GkQI47I7Ll3l for <6lowpan@ietfa.amsl.com>; Fri,  3 Feb 2012 09:32:52 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 249DA21F851E for <6lowpan@ietf.org>; Fri,  3 Feb 2012 09:32:51 -0800 (PST)
Received: by lahl5 with SMTP id l5so2272424lah.31 for <6lowpan@ietf.org>; Fri, 03 Feb 2012 09:32:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=Dqj/9E02S2uU5uIbFhJAnyzVwibS6uCPwU0LS935h24=; b=vjEcWvyG8UrRd5uiM9s0VklXKgCMsTLzqNhv4bZm3dmH02f1p9BA8JwFURoccU87s/ kAPLeJtWrDxt+P/0UHj9VxAUb/di9b8QlRDK7ncznfQKZuF0W1xYzO9C61CRptHho8KN xzR0LBm0UDzgNVFsI64fAB9ErkVFJ2erbgnyg=
MIME-Version: 1.0
Received: by 10.152.147.38 with SMTP id th6mr4078389lab.47.1328290371115; Fri, 03 Feb 2012 09:32:51 -0800 (PST)
Received: by 10.112.76.164 with HTTP; Fri, 3 Feb 2012 09:32:51 -0800 (PST)
Date: Fri, 3 Feb 2012 23:02:51 +0530
Message-ID: <CAHoqu_p-LFH6A6j3UG-iDvBzwjRzS+V+Je7uZAXGF+5rd-A_0g@mail.gmail.com>
From: Tom <my.mailing.acc@gmail.com>
To: 6lowpan@ietf.org
Content-Type: multipart/alternative; boundary=e89a8f22bdc5ba9bf304b812b3f8
Subject: [6lowpan] ND-18 Multiple Prefix
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 03 Feb 2012 17:32:53 -0000

--e89a8f22bdc5ba9bf304b812b3f8
Content-Type: text/plain; charset=ISO-8859-1

Hello Everyone,

Kindly clarify does ND-18 support multiple prefix (and multiple
address/node derived from these prefixes).
I raise this doubt because the assumption section,  bullet 4 says -> a
6lowpan is configured with one or more prefixes,
and the final bullet says -> since the 6lowpan shares one single prefix
through out the network.

Further, if 6LBR is advertising multiple prefix and host configures
multiple global addresses based on these prefix how will they be useful.
Will not the 6LR/6LBR reject registration through ARO from different source
address but same EUI-64 (same node auto configuring with different
prefixes).

Regards,
Thomas Chacko

--e89a8f22bdc5ba9bf304b812b3f8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Everyone,<br><br>Kindly clarify does ND-18 support multiple prefix (a=
nd multiple address/node derived from these prefixes). <br>I raise this dou=
bt because the assumption section,=A0 bullet 4 says -&gt; a 6lowpan is conf=
igured with one or more prefixes,<br>

and the final bullet says -&gt; since the 6lowpan shares one single prefix =
through out the network.<br><br>Further, if 6LBR is advertising multiple pr=
efix and host configures multiple global addresses based on these prefix ho=
w will they be useful. Will not the 6LR/6LBR reject registration through AR=
O from different source address but same EUI-64 (same node auto configuring=
 with different prefixes).<br>

<br>Regards,<br>Thomas Chacko<br><div style=3D"line-height:130%;text-align:=
left;font-size:10px;overflow:hidden;margin-left:0px;word-wrap:break-word;ma=
rgin-top:0px;padding:0px"></div>
<div style=3D"padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;wo=
rd-wrap:break-word;color:black;font-size:10px;text-align:left;line-height:1=
30%" id=3D"avg_ls_inline_popup"></div>

--e89a8f22bdc5ba9bf304b812b3f8--

From nordmark@acm.org  Fri Feb  3 09:42:36 2012
Return-Path: <nordmark@acm.org>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06CCF21F8468 for <6lowpan@ietfa.amsl.com>; Fri,  3 Feb 2012 09:42:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, 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 ByzKgTS7AFqy for <6lowpan@ietfa.amsl.com>; Fri,  3 Feb 2012 09:42:35 -0800 (PST)
Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by ietfa.amsl.com (Postfix) with ESMTP id 870F621F8466 for <6lowpan@ietf.org>; Fri,  3 Feb 2012 09:42:35 -0800 (PST)
Received: from Erik-Nordmarks-MacBook-Pro-2.local (128-107-239-233.cisco.com [128.107.239.233]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id q13HgW3d008421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Feb 2012 09:42:32 -0800
Message-ID: <4F2C1C88.2030304@acm.org>
Date: Fri, 03 Feb 2012 09:42:32 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Tom <my.mailing.acc@gmail.com>
References: <CAHoqu_p-LFH6A6j3UG-iDvBzwjRzS+V+Je7uZAXGF+5rd-A_0g@mail.gmail.com>
In-Reply-To: <CAHoqu_p-LFH6A6j3UG-iDvBzwjRzS+V+Je7uZAXGF+5rd-A_0g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] ND-18 Multiple Prefix
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 03 Feb 2012 17:42:36 -0000

On 2/3/12 9:32 AM, Tom wrote:
> Hello Everyone,
>
> Kindly clarify does ND-18 support multiple prefix (and multiple
> address/node derived from these prefixes).

Yes it does.

> I raise this doubt because the assumption section,  bullet 4 says -> a
> 6lowpan is configured with one or more prefixes,
> and the final bullet says -> since the 6lowpan shares one single prefix
> through out the network.

That inconsistency was pointed out in the IESG review. The final bullet 
is supposed to point out that the prefix or prefixes are shared across 
all the links in the 6lowpan network.

> Further, if 6LBR is advertising multiple prefix and host configures
> multiple global addresses based on these prefix how will they be useful.

They will be useful the same way multiple IPv6 prefixes are useful in 
general. For example, a site could have a ULA prefix plus a global 
prefix. Or a site might have multiple prefixes due to multihoming either 
permanently or while moving from one ISP to another. There are issues 
with multi-prefix multihoming for IPv4 and IPv6, but none of those are 
specific to 6lowpan networks.

> Will not the 6LR/6LBR reject registration through ARO from different
> source address but same EUI-64 (same node auto configuring with
> different prefixes).

Shouldn't be. There is nothing in the document that says that the same 
EUI-64 can't be used to register multiple addresses. I don't know if it 
makes sense to state this explicitly in the document.

Regards,
    Erik

From cabo@tzi.org  Fri Feb  3 09:44:14 2012
Return-Path: <cabo@tzi.org>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9ACC21F8592 for <6lowpan@ietfa.amsl.com>; Fri,  3 Feb 2012 09:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 gCrSLnyGakg9 for <6lowpan@ietfa.amsl.com>; Fri,  3 Feb 2012 09:44:14 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 1073621F8591 for <6lowpan@ietf.org>; Fri,  3 Feb 2012 09:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q13Hi6Hp019724; Fri, 3 Feb 2012 18:44:06 +0100 (CET)
Received: from [192.168.217.103] (p5489B96E.dip.t-dialin.net [84.137.185.110]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 9695F60E; Fri,  3 Feb 2012 18:44:01 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHoqu_p-LFH6A6j3UG-iDvBzwjRzS+V+Je7uZAXGF+5rd-A_0g@mail.gmail.com>
Date: Fri, 3 Feb 2012 18:43:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <17A9171E-18C1-489F-8829-94C35D02ACF9@tzi.org>
References: <CAHoqu_p-LFH6A6j3UG-iDvBzwjRzS+V+Je7uZAXGF+5rd-A_0g@mail.gmail.com>
To: Tom <my.mailing.acc@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] ND-18 Multiple Prefix
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 03 Feb 2012 17:44:15 -0000

On Feb 3, 2012, at 18:32, Tom wrote:

> Hello Everyone,
>=20
> Kindly clarify does ND-18 support multiple prefix (and multiple =
address/node derived from these prefixes).=20
> I raise this doubt because the assumption section,  bullet 4 says -> a =
6lowpan is configured with one or more prefixes,
> and the final bullet says -> since the 6lowpan shares one single =
prefix through out the network.

Yes, this editorial problem was noted by Adrian Farrel in the IESG =
review as well.

Fix:
s/shares one single prefix/shares its prefix(es)/

(The point of the sentence was that prefixes are lowpan-wide and thus =
you don't have a separate prefix for each link, not that there is only =
one prefix.  Bad wording.)

The expectation is that the number of these prefixes is going to be low.
Due to renumbering, we can't really rule out a situation where there is =
more than one prefix.

> Further, if 6LBR is advertising multiple prefix and host configures =
multiple global addresses based on these prefix how will they be useful.

Mostly in a renumbering situation, I think.

> Will not the 6LR/6LBR reject registration through ARO from different =
source address but same EUI-64 (same node auto configuring with =
different prefixes).

No, it would reject multiple nodes registering the same address, but =
there is no problem with one node registering multiple addresses.  =
Beside multiple prefixes, you may want to have one address based on a =
EUI-64 and another one based on a 16-bit MAC address (see RFC 4944) or =
you might even want an additional temporary address as a privacy =
address.  The EUI-64 is there in the ARO so the 6LBR can find out wether =
multiple nodes are trying to register the same address -- this is most =
likely to happen for 16-bit-based addresses, of course.

Gr=FC=DFe, Carsten


From my.mailing.acc@gmail.com  Tue Feb  7 03:04:37 2012
Return-Path: <my.mailing.acc@gmail.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7377A21F86D9 for <6lowpan@ietfa.amsl.com>; Tue,  7 Feb 2012 03:04:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.215
X-Spam-Level: 
X-Spam-Status: No, score=-1.215 tagged_above=-999 required=5 tests=[AWL=-1.076, BAYES_20=-0.74, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6]
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 zs2i6xi8Utm5 for <6lowpan@ietfa.amsl.com>; Tue,  7 Feb 2012 03:04:37 -0800 (PST)
Received: from mail-lpp01m020-f172.google.com (mail-lpp01m020-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id AC76621F853E for <6lowpan@ietf.org>; Tue,  7 Feb 2012 03:04:35 -0800 (PST)
Received: by lbbgk8 with SMTP id gk8so1716533lbb.31 for <6lowpan@ietf.org>; Tue, 07 Feb 2012 03:04:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=eGiAMRbHFqGWni8N8eWW6M/+fRbtX8SYklapBKpEZFA=; b=awM3j8qTUP3zNogePduz2izIokdJxkL0xOpQpUAu1u2DLM2FsUlFYhe0h8/3Qfzz/7 LGmQgnOKQeIz+rK0xXvK3GxKlW6v8oRTSoTpqc+UQ7mre4+IhBnT2VxQpUMaZiTwZWNq +omK9WFczFLkNxSX3u8k3dGVRrYhEjWoM53Vc=
MIME-Version: 1.0
Received: by 10.112.39.136 with SMTP id p8mr5974678lbk.79.1328612674642; Tue, 07 Feb 2012 03:04:34 -0800 (PST)
Received: by 10.112.76.164 with HTTP; Tue, 7 Feb 2012 03:04:34 -0800 (PST)
Date: Tue, 7 Feb 2012 16:34:34 +0530
Message-ID: <CAHoqu_qMbL7aicOoZSG8mcKEeo1TzdhX0c02nD99X7KSDGJTYg@mail.gmail.com>
From: Tom <my.mailing.acc@gmail.com>
To: 6lowpan@ietf.org
Content-Type: multipart/alternative; boundary=bcaec539653284234004b85dbe5d
Subject: [6lowpan] nd-18 NCE
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 07 Feb 2012 11:04:37 -0000

--bcaec539653284234004b85dbe5d
Content-Type: text/plain; charset=ISO-8859-1

Hi All,

Is there any state transition diagram available for the NCE maintenance in
ND-18.

Also, kindly clarify what does "A renewed ARO should mark the cache entry
as STALE" .

Is it to say that the first time a ARO is received the NCE becomes
REGISTERED and for all the subsequent received AROs from the same node the
NCE is set to STALE, but not grabage-collected and treated as REGISTERED.

Or is that a NCE now has two state variables (4861 state = probe,stale etc
and ND-18 state - registered or tentative).

Regards,
Thomas Chacko

--bcaec539653284234004b85dbe5d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br clear=3D"all"><div>Hi All,</div><div><br></div><div>Is there any state=
=A0transition=A0diagram available for the NCE=A0maintenance=A0in ND-18.</di=
v><div><br></div><div>Also, kindly clarify what does <font color=3D"#ff0000=
">&quot;A renewed ARO should mark the cache entry as STALE&quot; .</font></=
div>
<div><font color=3D"#ff0000"><br></font></div><div>Is it to say that the fi=
rst time a ARO is received the NCE becomes REGISTERED and for all the subse=
quent received AROs from the same node the NCE is set to STALE, but not gra=
bage-collected and treated as REGISTERED.</div>
<div><br></div><div>Or is that a NCE now has two state variables (4861 stat=
e =3D probe,stale etc and ND-18 state - registered or tentative).</div><div=
><br></div><div>Regards,</div><div>Thomas Chacko</div><br>

--bcaec539653284234004b85dbe5d--

From my.mailing.acc@gmail.com  Wed Feb  8 08:07:29 2012
Return-Path: <my.mailing.acc@gmail.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A953B21F84F3 for <6lowpan@ietfa.amsl.com>; Wed,  8 Feb 2012 08:07:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.876
X-Spam-Level: 
X-Spam-Status: No, score=-1.876 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6]
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 JsVfRIHcQjcX for <6lowpan@ietfa.amsl.com>; Wed,  8 Feb 2012 08:07:29 -0800 (PST)
Received: from mail-lpp01m020-f172.google.com (mail-lpp01m020-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 741F221F8523 for <6lowpan@ietf.org>; Wed,  8 Feb 2012 08:07:28 -0800 (PST)
Received: by lbbgk8 with SMTP id gk8so396249lbb.31 for <6lowpan@ietf.org>; Wed, 08 Feb 2012 08:07:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VrKP68kkXRNcPpdLuEdCHbQma0e+UVvJ12VILdQDimE=; b=Ym59o4HIvOy5r0u0az0tNh4fnUq9DnatfaFIOpZ4OrgiJEI9HR+rPtIuZcpNyW7MfB HU1U98QCVlwbAIYbN5MuE5NF/Cd7CmFTHJ94aEtiWHWpN+6k9/TteTvtV7hoXXbmmYOA n5/tY5EZigoyjsswB4S978xwwfNvXeKe/5jds=
MIME-Version: 1.0
Received: by 10.152.114.74 with SMTP id je10mr15675949lab.40.1328717247191; Wed, 08 Feb 2012 08:07:27 -0800 (PST)
Received: by 10.112.76.164 with HTTP; Wed, 8 Feb 2012 08:07:27 -0800 (PST)
In-Reply-To: <CAHoqu_qMbL7aicOoZSG8mcKEeo1TzdhX0c02nD99X7KSDGJTYg@mail.gmail.com>
References: <CAHoqu_qMbL7aicOoZSG8mcKEeo1TzdhX0c02nD99X7KSDGJTYg@mail.gmail.com>
Date: Wed, 8 Feb 2012 21:37:27 +0530
Message-ID: <CAHoqu_pY3+b_yojkAMWzc5aim8jBOLcpCaVEscQVaQ90Sbacmg@mail.gmail.com>
From: Thomas Chacko <my.mailing.acc@gmail.com>
To: 6lowpan@ietf.org
Content-Type: multipart/alternative; boundary=f46d0408d7ed8699d404b87617a2
Subject: Re: [6lowpan] nd-18 NCE
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 08 Feb 2012 16:07:29 -0000

--f46d0408d7ed8699d404b87617a2
Content-Type: text/plain; charset=ISO-8859-1

Hi All,

Will really appreciate if you could give some pointers.

Regards,
Thomas Chacko

On Tue, Feb 7, 2012 at 4:34 PM, Tom <my.mailing.acc@gmail.com> wrote:

>
> Hi All,
>
> Is there any state transition diagram available for the NCE maintenance in
> ND-18.
>
> Also, kindly clarify what does "A renewed ARO should mark the cache entry
> as STALE" .
>
> Is it to say that the first time a ARO is received the NCE becomes
> REGISTERED and for all the subsequent received AROs from the same node the
> NCE is set to STALE, but not grabage-collected and treated as REGISTERED.
>
> Or is that a NCE now has two state variables (4861 state = probe,stale etc
> and ND-18 state - registered or tentative).
>
> Regards,
> Thomas Chacko
>
>

--f46d0408d7ed8699d404b87617a2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi All,<br><br>Will really appreciate if you could give some pointers. <br>=
<br>Regards,<br>Thomas Chacko<br><br><div class=3D"gmail_quote">On Tue, Feb=
 7, 2012 at 4:34 PM, Tom <span dir=3D"ltr">&lt;<a href=3D"mailto:my.mailing=
.acc@gmail.com">my.mailing.acc@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br clear=3D"all"><div>Hi All,</div><div><br=
></div><div>Is there any state=A0transition=A0diagram available for the NCE=
=A0maintenance=A0in ND-18.</div>
<div><br></div><div>Also, kindly clarify what does <font color=3D"#ff0000">=
&quot;A renewed ARO should mark the cache entry as STALE&quot; .</font></di=
v>
<div><font color=3D"#ff0000"><br></font></div><div>Is it to say that the fi=
rst time a ARO is received the NCE becomes REGISTERED and for all the subse=
quent received AROs from the same node the NCE is set to STALE, but not gra=
bage-collected and treated as REGISTERED.</div>

<div><br></div><div>Or is that a NCE now has two state variables (4861 stat=
e =3D probe,stale etc and ND-18 state - registered or tentative).</div><div=
><br></div><div>Regards,</div><div>Thomas Chacko</div><br>
</blockquote></div><br><br clear=3D"all"><br>
<div style=3D"padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;wo=
rd-wrap:break-word;color:black;font-size:10px;text-align:left;line-height:1=
30%" id=3D"avg_ls_inline_popup"></div>

--f46d0408d7ed8699d404b87617a2--

From cabo@tzi.org  Fri Feb 24 00:26:02 2012
Return-Path: <cabo@tzi.org>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD50221F85E7; Fri, 24 Feb 2012 00:26:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.821
X-Spam-Level: 
X-Spam-Status: No, score=-105.821 tagged_above=-999 required=5 tests=[AWL=-0.172, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_13=0.6, 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 SrlwqWPvFQqq; Fri, 24 Feb 2012 00:26:02 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id ED5E721F85E5; Fri, 24 Feb 2012 00:26:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q1O8PrP2018457; Fri, 24 Feb 2012 09:25:53 +0100 (CET)
Received: from [192.168.217.105] (p5B3E6044.dip.t-dialin.net [91.62.96.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 0B95A872; Fri, 24 Feb 2012 09:25:52 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Fri, 24 Feb 2012 09:25:53 +0100
To: 6lowpan@ietf.org, "core@ietf.org WG" <core@ietf.org>, roll@ietf.org, lwip@ietf.org
Message-Id: <1B2B5C1F-AF12-44CB-BCF1-C5DD2978FBEB@tzi.org>
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Subject: [6lowpan] Constrained Node/Network Cluster @ IETF83
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 24 Feb 2012 08:26:03 -0000

Here is my usual compilation of the draft agenda for IETF83.
Note that this agenda is subject to change, so please don't plan travel =
around it.
This time, we are nicely spread out over the week, so a lot of things =
will happen between the meeting slots.

Gr=FC=DFe, Carsten


***DRAFT*** Agenda for Constrained Node/Network related events during
   IETF 83 in Paris
***Subject to change*** -- don't plan travel around this

* FRIDAY, March 23, 2012

IAB Workshop on Smart Object Security

* SATURDAY, March 24, 2012; SUNDAY, March 25, 2012

ETSI CoAP plugfest

* MONDAY, March 26, 2012

0900-1130
Maillot OPS   v6ops    IPv6 Operations WG

* TUESDAY, March 27, 2012

0900-1130
243     APP   *core*   Constrained RESTful Environments WG
Maillot INT   homenet  Home Networking WG

1300-1500
241     OPS   eman     Energy Management WG

* WEDNESDAY, March 28, 2012

0900-1130
242AB   INT   6man     IPv6 Maintenance WG

1300-1500
241     RTG   *roll*   Routing Over Low power and Lossy networks WG

* THURSDAY, March 29, 2012

1300-1500
Maillot INT   intarea  Internet Area Working Group WG

1520-1720
252B    INT   *lwig*   Light-Weight Implementation Guidance WG
Maillot OPS   v6ops    IPv6 Operations WG

* FRIDAY, March 30, 2012

0900-1100
253     APP   *core*   Constrained RESTful Environments WG


From dat@exegin.com  Wed Feb 29 03:17:15 2012
Return-Path: <dat@exegin.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8991421F883B for <6lowpan@ietfa.amsl.com>; Wed, 29 Feb 2012 03:17:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_LOW=-1]
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 CKTNp8w0WWUH for <6lowpan@ietfa.amsl.com>; Wed, 29 Feb 2012 03:17:15 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id C628F21F8897 for <6lowpan@ietf.org>; Wed, 29 Feb 2012 03:17:14 -0800 (PST)
Received: by wicr5 with SMTP id r5so2593677wic.31 for <6lowpan@ietf.org>; Wed, 29 Feb 2012 03:17:13 -0800 (PST)
Received-SPF: pass (google.com: domain of dat@exegin.com designates 10.180.24.7 as permitted sender) client-ip=10.180.24.7; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of dat@exegin.com designates 10.180.24.7 as permitted sender) smtp.mail=dat@exegin.com
Received: from mr.google.com ([10.180.24.7]) by 10.180.24.7 with SMTP id q7mr47547079wif.14.1330514233405 (num_hops = 1); Wed, 29 Feb 2012 03:17:13 -0800 (PST)
Received: by 10.180.24.7 with SMTP id q7mr37853009wif.14.1330514233356; Wed, 29 Feb 2012 03:17:13 -0800 (PST)
Received: from [192.168.3.26] (196-210-130-71.dynamic.isadsl.co.za. [196.210.130.71]) by mx.google.com with ESMTPS id hb10sm85635632wib.10.2012.02.29.03.17.11 (version=SSLv3 cipher=OTHER); Wed, 29 Feb 2012 03:17:12 -0800 (PST)
Message-ID: <4F4E0934.4060000@exegin.com>
Date: Wed, 29 Feb 2012 13:17:08 +0200
From: Dario Tedeschi <dat@exegin.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: 6lowpan@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnqFwCEHV68LnGi/2Pk8ZPpWBSCI4UUixivQdGTMpOFa8hUkx5iNE7oC/fP94/7x3cGBGik
Subject: [6lowpan] Identifying a host
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 29 Feb 2012 11:17:15 -0000

I was wondering if it would be useful to add an R (Router) flag to the 
ARO, in 6LoWPAN ND, to indicate whether a node is a router or a host. It 
would be very handy for route-over topologies (i.e. RPL).

When a node registers an address through its default router, that router 
needs to know whether the node is operating as a router as well or just 
a host. If it's a host, the router can add a host route to that node, 
indicating that that node is outside of the routing domain and that the 
node expects traffic forwarded on it's behalf.

The reason for choosing the ARO to add the flag is that NS does not have 
the R flag like the NA does, and since it's likely that only an NS+ARO 
will ever be sent from a registering node and the ARO is specific to 
6LoWPAN, adding an R flag to the ARO would seem the logical choice.

Dario
