IETF Logo Mail Archive

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

"Anders Brandt" <abr@sdesigns.dk> Wed, 17 November 2010 13:50 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 60ECD3A6903 for <roll@core3.amsl.com>; Wed, 17 Nov 2010 05:50:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.563
X-Spam-Level:
X-Spam-Status: No, score=-1.563 tagged_above=-999 required=5 tests=[AWL=1.036, 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 Kt7JjG6cFrsC for <roll@core3.amsl.com>; Wed, 17 Nov 2010 05:50:00 -0800 (PST)
Received: from mail.zen-sys.com (mail.zen-sys.com [195.215.56.170]) by core3.amsl.com (Postfix) with ESMTP id 55F373A6912 for <roll@ietf.org>; Wed, 17 Nov 2010 05:50:00 -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: Wed, 17 Nov 2010 14:50:45 +0100
Message-ID: <6D9687E95918C04A8B30A7D6DA805A3E01CCD53D@zensys17.zensys.local>
In-Reply-To: <AANLkTi=whP0wayUk7v_j-iL0a1pX26=uFfRb6JvZnoWD@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RPL P2P - Clarify that hop-by-hop is identical to RPL Storing mode
Thread-Index: AcuEsHGhY/NbgJ7vRrSU0AvUM2mCPQBq6Ahw
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>
From: Anders Brandt <abr@sdesigns.dk>
To: ROLL WG <roll@ietf.org>
Subject: [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 13:50:01 -0000

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

v2.23.0 | Report a Bug | By Email