Re: [Roll] Source Routing Header Format
"Popa, Daniel" <Daniel.Popa@itron.com> Tue, 18 May 2010 06:59 UTC
Return-Path: <Daniel.Popa@itron.com>
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 0CDAF3A6C2C for <roll@core3.amsl.com>; Mon, 17 May 2010 23:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 ug5nTs4EMPiK for <roll@core3.amsl.com>; Mon, 17 May 2010 23:59:17 -0700 (PDT)
Received: from itron.com (itron9-144.itron.com [198.182.9.144]) by core3.amsl.com (Postfix) with ESMTP id AABB13A6C28 for <roll@ietf.org>; Mon, 17 May 2010 23:59:17 -0700 (PDT)
Received: from ITR-EXMBXVS-1.itron.com ([192.168.9.112]) by spo-exchcn-2.itron.com ([192.168.9.116]) with mapi; Mon, 17 May 2010 23:59:09 -0700
From: "Popa, Daniel" <Daniel.Popa@itron.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, JP Vasseur <jpv@cisco.com>, "JeongGil Ko (John)" <jgko@cs.jhu.edu>
Date: Mon, 17 May 2010 23:59:06 -0700
Thread-Topic: [Roll] Source Routing Header Format
Thread-Index: Acr1vzKL+77aa0CVSayUfL+M/7aMGwAlAVNAAAD4qXA=
Message-ID: <83027ECE5ECDC04E9BA5350B756A88E158D096CBE1@ITR-EXMBXVS-1.itron.com>
References: <6AAA6AEF-11B3-4342-BEA3-6D6D39E8154C@cs.jhu.edu> <7ED5239F-691E-448D-A174-D6B51128584D@cisco.com> <6A2A459175DABE4BB11DE2026AA50A5D01E85DBE@XMB-AMS-107.cisco.com>
In-Reply-To: <6A2A459175DABE4BB11DE2026AA50A5D01E85DBE@XMB-AMS-107.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ROLL WG <roll@ietf.org>
Subject: Re: [Roll] Source Routing Header Format
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: Tue, 18 May 2010 06:59:19 -0000
Pascal, +1. It seems a good starting point. Daniel > -----Original Message----- > From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf Of > Pascal Thubert (pthubert) > Sent: Tuesday, May 18, 2010 8:36 AM > To: JP Vasseur; JeongGil Ko (John) > Cc: ROLL WG > Subject: Re: [Roll] Source Routing Header Format > > Hi JP: > > For the P2P, it appears that we'll need the record route piece as well. > But the record route does not preexist in IPv6 standards. > > It is present in my early work on tree discovery, so in a somewhat > similar context of mobile routers forming networks: > http://tools.ietf.org/html/draft-thubert-nemo-reverse-routing-header > > One option to move forward could be to start from that draft and make > it > a separate spec. > > We'd cleanup the mobility/tunnel pieces and make it fully agnostic to > routing protocols. > > What does the group think? > > Pascal > > > -----Original Message----- > > From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf > Of JP > > Vasseur > > Sent: Monday, May 17, 2010 2:44 PM > > To: JeongGil Ko (John) > > Cc: ROLL WG > > Subject: Re: [Roll] Source Routing Header Format > > > > Hi, > > > > On May 7, 2010, at 8:24 AM, JeongGil Ko (John) wrote: > > > > > Hi all, > > > > > > Have we decided on what the routing header format will be for > point- > > > to-point routing? > > > The last discussion that I remember concluded with "Let's do > something > > > like RH0 and do tag/labels for addressing". > > > > Right, Jonathan agreed to take the ownership of the ticket: indeed > the > > conclusion was RH0-like, staying within RPL domain to avoid security > issues. > > Labels may come next (separate ID). > > > > Thanks. > > > > JP. > > > > > Do we have anything else after that? > > > > > > -John > > > > > > ------ > > > JeongGil Ko (John) > > > Ph.D. Student > > > Department of Computer Science > > > Johns Hopkins University > > > http://www.cs.jhu.edu/~jgko > > > > > > _______________________________________________ > > > Roll mailing list > > > Roll@ietf.org > > > https://www.ietf.org/mailman/listinfo/roll > > > > _______________________________________________ > > Roll mailing list > > Roll@ietf.org > > https://www.ietf.org/mailman/listinfo/roll > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll
- [Roll] Source Routing Header Format JeongGil Ko (John)
- Re: [Roll] Source Routing Header Format in RPL Anders Brandt
- Re: [Roll] Source Routing Header Format in RPL JP Vasseur
- Re: [Roll] Source Routing Header Format JP Vasseur
- Re: [Roll] Source Routing Header Format Pascal Thubert (pthubert)
- Re: [Roll] Source Routing Header Format Popa, Daniel
- Re: [Roll] Source Routing Header Format Daniel Gavelle
- Re: [Roll] Source Routing Header Format Pascal Thubert (pthubert)
- Re: [Roll] Source Routing Header Format Carsten Bormann
- Re: [Roll] Source Routing Header Format Robert Cragie
- Re: [Roll] Source Routing Header Format JP Vasseur