IETF Logo Mail Archive

Re: [6lowpan] "Advertize on Behalf" flag in ARO

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 30 March 2011 08:28 UTC

Return-Path: <pthubert@cisco.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 A1ACB28C0E2 for <6lowpan@core3.amsl.com>; Wed, 30 Mar 2011 01:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.382
X-Spam-Level:
X-Spam-Status: No, score=-10.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 SAKMj-f+No-e for <6lowpan@core3.amsl.com>; Wed, 30 Mar 2011 01:28:36 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 3B2F03A6A2B for <6lowpan@ietf.org>; Wed, 30 Mar 2011 01:28:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pthubert@cisco.com; l=1527; q=dns/txt; s=iport; t=1301473815; x=1302683415; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=RM4THJLcN8LPQlQsSYbWuPhEYIWSLRNEt3vbrDRTESo=; b=ZoFxz5pJhg3V3JndiBy9wbesBsB80GEyQsQQRtepi5taCtgbB5Om6Jg9 BDhUu/fN4Ig7jMZCXUmM6bwtXdc6WNgaBN3cxqm/lSO6OAuwVNE3tig9E UWvcue60gX50FKQfAKi5mmKmONLX0R/bqvv9g0KgI8O6LAn8VcoottUbB E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As4AAADpkk2Q/khLgWdsb2JhbACYEY07FAEBFiYloGucTYVqBJBh
X-IronPort-AV: E=Sophos;i="4.63,267,1299456000"; d="scan'208";a="23754179"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 30 Mar 2011 08:30:14 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2U8UEYQ025111; Wed, 30 Mar 2011 08:30:14 GMT
Received: from xmb-ams-107.cisco.com ([144.254.74.82]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 30 Mar 2011 10:30:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 30 Mar 2011 10:30:09 +0200
Message-ID: <6A2A459175DABE4BB11DE2026AA50A5D04395561@XMB-AMS-107.cisco.com>
In-Reply-To: <AD337F0D-E0AF-42A6-A9F6-05D07DF900F3@tzi.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [6lowpan] "Advertize on Behalf" flag in ARO
Thread-Index: AcvuNaWMKrhu0N22TXmXezhX6pZOlgAfUafw
References: <22230823.477101.1299157661084.JavaMail.root@mail02.pantherlink.uwm.edu> <4D91BEDA.7080907@acm.org> <6A2A459175DABE4BB11DE2026AA50A5D0439536D@XMB-AMS-107.cisco.com> <AD337F0D-E0AF-42A6-A9F6-05D07DF900F3@tzi.org>
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Carsten Bormann <cabo@tzi.org>
X-OriginalArrivalTime: 30 Mar 2011 08:30:14.0319 (UTC) FILETIME=[B11D1BF0:01CBEEB4]
Cc: 6lowpan <6lowpan@ietf.org>
Subject: Re: [6lowpan] "Advertize on Behalf" flag in ARO
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: Wed, 30 Mar 2011 08:28:37 -0000

Hi Carsten:

RPL recognizes a movement when a DAO information has a stale
DAOSequence. The DAOSequence is an information that the owner of the
advertised target increments.
If we define an interaction whereby we redistribute ND-15 into RPL, then
(probably) the RPL router will inject a host route on behalf of the
host.
When the RPL router injects such a route and then maintains that route,
it still has has to provide an idea of the freshness of the information
that it is injecting in a DAOSequence.
When the host moves to an alternate router, it would have to provide
something so that the new router sets an updated DAOSequence that the
routing update percolates up the DODAG.
IOW, without a TID, a host cannot efficiently move from a router to the
next.

People can find more on TID interactions with RPL and ND in
http://tools.ietf.org/html/draft-thubert-6lowpan-backbone-router-02 .
I'll see what I do with that draft; probably propose it to ROLL.

Pascal
http://www.xtranormal.com/watch/7011357/


> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org]
> Sent: Tuesday, March 29, 2011 7:20 PM
> To: Pascal Thubert (pthubert)
> Cc: Erik Nordmark; Mukul Goyal; 6lowpan
> Subject: Re: [6lowpan] "Advertize on Behalf" flag in ARO
> 
> On Mar 29, 2011, at 18:25, Pascal Thubert (pthubert) wrote:
> 
> > But then, RPL, like the backbone router draft operation, needs the
TID
> 
> Can you explain why RPL needs a sequence number here?
> 
> Gruesse, Carsten

v2.23.0 | Report a Bug | By Email