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

Philip Levis <pal@cs.stanford.edu> Wed, 17 November 2010 17:13 UTC

Return-Path: <pal@cs.stanford.edu>
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 A0F2B3A6940 for <roll@core3.amsl.com>; Wed, 17 Nov 2010 09:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 KC4ZXTu955mD for <roll@core3.amsl.com>; Wed, 17 Nov 2010 09:13:40 -0800 (PST)
Received: from cs-smtp-3.Stanford.EDU (cs-smtp-3.Stanford.EDU [171.64.64.27]) by core3.amsl.com (Postfix) with ESMTP id 8517C3A6912 for <roll@ietf.org>; Wed, 17 Nov 2010 09:13:40 -0800 (PST)
Received: from [76.14.65.187] (helo=[192.168.1.106]) by cs-smtp-3.Stanford.EDU with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.60) (envelope-from <pal@cs.stanford.edu>) id 1PIlaU-0006Xb-3y; Wed, 17 Nov 2010 09:14:26 -0800
In-Reply-To: <6D9687E95918C04A8B30A7D6DA805A3E01CCD53D@zensys17.zensys.local>
References: <AANLkTinvXyAUG6yzTzLn5Vq8MUDjQx-K8R_1HQ4rjMeR@mail.gmail.com><FD2837AD-A44B-4043-9610-54525B042A2A@cisco.com><484090EF-9061-4739-B222-A9130CF9E79A@cs.berkeley.edu><AANLkTikSrRQE5TaXEfVVfTOCTU2jy0-P6=ZaK5XFz116@mail.gmail.com><79B005E5-3DA0-4556-9B9F-48A9C658C115@tzi.org> <AANLkTi=whP0wayUk7v_j-iL0a1pX26=uFfRb6JvZnoWD@mail.gmail.com> <6D9687E95918C04A8B30A7D6DA805A3E01CCD53D@zensys17.zensys.local>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <7EBEEA03-7A81-49E8-9BE3-39A523DAF080@cs.stanford.edu>
Content-Transfer-Encoding: 7bit
From: Philip Levis <pal@cs.stanford.edu>
Date: Wed, 17 Nov 2010 09:14:24 -0800
To: Anders Brandt <abr@sdesigns.dk>
X-Mailer: Apple Mail (2.753.1)
X-Scan-Signature: f9929892efd47015c544d6ca2fb551e9
Cc: ROLL WG <roll@ietf.org>
Subject: Re: [Roll] RPL P2P - Clarify that hop-by-hop is identical to RPL Storing 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: Wed, 17 Nov 2010 17:13:41 -0000

On Nov 17, 2010, at 5:50 AM, Anders Brandt wrote:

> Dear P2P'ers
>
>
> 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.
>
> 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.
>
> Obviously, the frame format descriptions should
> be common.
>
> Just my $.05

I think it make sense to keep them as separate sections of the same  
document. They should definitely be separate, concrete sections,  
though. I think there's always a push to break things up into many  
tiny documents because of short attention spans. But it's easier to  
keep them consistent in a single document, and the aggregate length  
is shorter.

Phil