Re: [Roll] RPL P2P - Clarify that hop-by-hop is identical to RPLStoring mode

"Anders Brandt" <abr@sdesigns.dk> Thu, 18 November 2010 10:41 UTC

Return-Path: <abr@sdesigns.dk>
X-Original-To: roll@core3.amsl.com
Delivered-To: roll@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76DD43A681D for <roll@core3.amsl.com>; Thu, 18 Nov 2010 02:41:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=0.622, BAYES_00=-2.599]
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 epT7ESAT1TYp for <roll@core3.amsl.com>; Thu, 18 Nov 2010 02:41:15 -0800 (PST)
Received: from mail.zen-sys.com (mail.zen-sys.com [195.215.56.170]) by core3.amsl.com (Postfix) with ESMTP id 0914C28C0D0 for <roll@ietf.org>; Thu, 18 Nov 2010 02:41:14 -0800 (PST)
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: Thu, 18 Nov 2010 11:42:01 +0100
Message-ID: <6D9687E95918C04A8B30A7D6DA805A3E01CCD546@zensys17.zensys.local>
In-Reply-To: <1010799673.1728842.1290023295331.JavaMail.root@mail02.pantherlink.uwm.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Roll] RPL P2P - Clarify that hop-by-hop is identical to RPLStoring mode
Thread-Index: AcuGkGFAjcnASc/xQLSZx7Pi/ZAcPQAfBSGw
References: <6D9687E95918C04A8B30A7D6DA805A3E01CCD53D@zensys17.zensys.local> <1010799673.1728842.1290023295331.JavaMail.root@mail02.pantherlink.uwm.edu>
From: Anders Brandt <abr@sdesigns.dk>
To: Mukul Goyal <mukul@uwm.edu>
Cc: ROLL WG <roll@ietf.org>
Subject: Re: [Roll] RPL P2P - Clarify that hop-by-hop is identical to RPLStoring mode
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Nov 2010 10:41:17 -0000

Hi Mukul

(see inline)

Cheers,
  Anders 

> -----Original Message-----
> From: Mukul Goyal [mailto:mukul@uwm.edu] 
> Sent: Wednesday, November 17, 2010 20:48
> To: Anders Brandt
> Cc: ROLL WG
> Subject: Re: [Roll] RPL P2P - Clarify that hop-by-hop is 
> identical to RPLStoring mode
> 
> Hi Anders,
> 
> [Anders]
> 
> The current RPL P2P draft
> http://tools.ietf.org/html/draft-dt-roll-p2p-rpl-02
> 
> appears to be a little unclear on the terms
> 
> * hop-by-hop route
> * source route
> * RPL Storing mode
> * RPL Non-storing mode
> 
> The introduction does a nice job of explaining the difference 
> of the two uncompatible modes but forgets to point out the 
> detail that the RPL Non-storing mode is using source routes 
> while RPL Storing mode implements hop-by-hop routes.
> 
> [Mukul]
> 
> The introduction section does say that
> 
> "In non-storing mode operation, only the DAG root maintains 
> downward routing
>    information and hence a packet travels all the way to the DAG root,
>    which then sends it towards its destination using a source route."
> 
> Then it describes the storing mode operation
> 
> "In storing mode operation, if the destination is a DAG descendant and
>    the source maintains "downwards" routing state about this 
> descendant,
>    it can forward the packet along this route.  Otherwise, the source
>    sends the packet to a DAG parent, which then applies the 
> same set of
>    rules to forward the packet further."
> 
> I guess I could modify the first sentence as follows
> 
> "In storing mode operation, if the destination is a DAG descendant and
>    the source maintains "downwards" HOP-BY-HOP routing state 
> about this descendant,
>    it can forward the packet along this route."
> 
> Would this change be sufficient?

[Anders]

Yes, this definitely helps. But the last part
" ...forward the packet along this route."
seems to mix things up.

May I suggest:
" ...forward the packet to a descendant router closer to the
destination..."

> [Anders]
> Since a given implementation is going to be either 
> non-storing or storing one may consider having dedicated 
> sections (or documents?) explaining what is required for 
> making a system work for non-storing or storing mode, respectively.
> 
> [Mukul]
> 
> Are you suggesting that hop-by-hop P2P routes can not be used 
> in an LLN using non-storing mode RPL operation? It seems to 
> me that both types of P2P routes (hop-by-hop; source) can be 
> used irrespective of whether core RPL operation is storing 
> mode or non-storing mode.
> 
> Thanks
> Mukul
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>