Re: [Roll] Spencer Dawkins' No Objection on draft-ietf-roll-routing-dispatch-03: (with COMMENT)

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 26 October 2016 16:16 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C254412969C; Wed, 26 Oct 2016 09:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.951
X-Spam-Level:
X-Spam-Status: No, score=-14.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XfOeNxu3wZtQ; Wed, 26 Oct 2016 09:16:53 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29D8C12968F; Wed, 26 Oct 2016 09:16:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=54006; q=dns/txt; s=iport; t=1477498613; x=1478708213; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=94ynLX5cThJBRERL4PVMKesM68Bu2l0RpS7zl2Bpdos=; b=K2Fxd6tv8QJKwDGdW8hYMQP3o0xj7+suFA3gy/rReeVw8tnMdP+zEPoe 8Hi7cKV5Ubxb0r1xV3j+8MIV1hVJ9DNeOwPo5HPdij/dJZ6iXeQ0ZsCtf fW4v6EZxh0Ea1XQwZ8aK7/6Arpop+ikxXdfY/CpTeg6dbGmGiMSKd90rI M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B3AQCt1hBY/4wNJK1cGgEBAQECAQEBAQgBAQEBgnM3AQEBAQEdWH0HjS6WfodeilKCD4IJKYV5AhqBbD8UAQIBAQEBAQEBYiiEYgEBAQQjCkwMBAIBCBEEAQEhAQYDAgICHxEUCQgCBA4FCAaILAMXDrNpiHUNg28BAQEBAQEBAQEBAQEBAQEBAQEBAQEODoY9hFWCR4FSEQFSCIJGglsFiEWGBYVuhSk1AYNBgmqGUYMcgXVOhB+JKYhwhBqEAAEeNl6DGRwYgTpyAYY8gSCBCQEBAQ
X-IronPort-AV: E=Sophos;i="5.31,551,1473120000"; d="scan'208,217";a="339057660"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Oct 2016 16:16:52 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u9QGGquW004821 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 26 Oct 2016 16:16:52 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 26 Oct 2016 11:16:51 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1210.000; Wed, 26 Oct 2016 11:16:51 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Thread-Topic: Spencer Dawkins' No Objection on draft-ietf-roll-routing-dispatch-03: (with COMMENT)
Thread-Index: AQHSLzqeOoO/tkqjTU+qTev4BssAsKC6VEtAgADKrwD//7iF8IAAZW2A//+sUWA=
Date: Wed, 26 Oct 2016 16:16:50 +0000
Deferred-Delivery: Wed, 26 Oct 2016 16:16:08 +0000
Message-ID: <3506df9c27844345812dffc24d9a0086@XCH-RCD-001.cisco.com>
References: <147745319246.29259.2342833266178316799.idtracker@ietfa.amsl.com> <8fe34e2a63e448998b90177140876d41@XCH-RCD-001.cisco.com> <CAKKJt-fKrTF9u7V7sOMmw77gy9Oi3vpy-d9oW+4L2EZ5g+APTg@mail.gmail.com> <9ba8442cca594fd6906ab62fea8d4067@XCH-RCD-001.cisco.com> <CAKKJt-fgBd43aCXwQTd=prwG-q11dHgsboSv7Z8r+HRZuA7fUg@mail.gmail.com>
In-Reply-To: <CAKKJt-fgBd43aCXwQTd=prwG-q11dHgsboSv7Z8r+HRZuA7fUg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.22.4]
Content-Type: multipart/mixed; boundary="_004_3506df9c27844345812dffc24d9a0086XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/NqCmKNU-BDnaYGajHRaH2YxtwsA>
Cc: "roll-chairs@ietf.org" <roll-chairs@ietf.org>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>, "roll@ietf.org" <roll@ietf.org>, "draft-ietf-roll-routing-dispatch@ietf.org" <draft-ietf-roll-routing-dispatch@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Roll] Spencer Dawkins' No Objection on draft-ietf-roll-routing-dispatch-03: (with COMMENT)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 26 Oct 2016 16:16:56 -0000

Thanks again Spencer : )

I posted, then!

URL:            https://www.ietf.org/internet-drafts/draft-ietf-roll-routing-dispatch-04.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-roll-routing-dispatch/
Htmlized:       https://tools.ietf.org/html/draft-ietf-roll-routing-dispatch-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-routing-dispatch-04
Take care,

Pascal

From: Spencer Dawkins at IETF [mailto:spencerdawkins.ietf@gmail.com]
Sent: mercredi 26 octobre 2016 18:13
To: Pascal Thubert (pthubert) <pthubert@cisco.com>
Cc: The IESG <iesg@ietf.org>; roll-chairs@ietf.org; Alvaro Retana (aretana) <aretana@cisco.com>; roll@ietf.org; draft-ietf-roll-routing-dispatch@ietf.org; mcr+ietf@sandelman.ca
Subject: Re: Spencer Dawkins' No Objection on draft-ietf-roll-routing-dispatch-03: (with COMMENT)

Hi, Pascal,

On Wed, Oct 26, 2016 at 10:24 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Nice! I love it Spencer : )

I suggest a slight adaptation to show that with the current specs, the device is the endpoint for the tunnel and the destination of inner packet as well.


       ------+---------                           ^
             |          Internet                  |
             |                                    | Native IPv6
          +-----+                                 |
          |     | Border Router (RPL Root)      + | +
          |     |                               | | |
          +-----+                               | | | tunneled
             |                                  | | | using
       o    o   o    o                          | | | IPv6-in-
   o o   o  o   o  o  o o   o                   | | | IPv6 and
  o  o o  o o    o   o   o  o  o                | | | RPL SRH
  o   o    o  o     o  o    o  o  o             | | |
o  o   o  o   o         o   o o                | | |
o          o             o     o               + v +
                   LLN


Works ?

I knew you could fix the stuff I got wrong :D ...

Works for me!

Pascal

From: Spencer Dawkins at IETF [mailto:spencerdawkins.ietf@gmail.com<mailto:spencerdawkins.ietf@gmail.com>]
Sent: mercredi 26 octobre 2016 16:26
To: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Cc: The IESG <iesg@ietf.org<mailto:iesg@ietf.org>>; roll-chairs@ietf.org<mailto:roll-chairs@ietf.org>; Alvaro Retana (aretana) <aretana@cisco.com<mailto:aretana@cisco.com>>; roll@ietf.org<mailto:roll@ietf.org>; draft-ietf-roll-routing-dispatch@ietf.org<mailto:draft-ietf-roll-routing-dispatch@ietf.org>; mcr+ietf@sandelman.ca<mailto:mcr%2Bietf@sandelman.ca>
Subject: Re: Spencer Dawkins' No Objection on draft-ietf-roll-routing-dispatch-03: (with COMMENT)

Hi, Pascal,

Thanks for the quick response. Inline.

On Wed, Oct 26, 2016 at 4:37 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Hello Spencer,

The 2 shorter arrows, left and right, represent the encapsulation tunnel.

Now that you've said that, I totally get it, but I didn't get that from the picture at all.

Would you have a suggestion to improve the readability?

Maybe :-)

I lengthened the native IPv6 arrow and used different endpoints for the tunnel, hyphenated "IPv6-in-IPv6, and included "tunneled using" in the label (I probably didn't use the right words, but you'd know what is correct).

       ------+---------                           ^
             |          Internet                  |
             |                                    | Native IPv6
          +-----+                                 |
          |     | Border Router (RPL Root)      + | +
          |     |                               | | |
          +-----+                               | | | tunneled
             |                                  | | | using
       o    o   o    o                          | | | IPv6-in-
   o o   o  o   o  o  o o   o                   | | | IPv6 and
  o  o o  o o    o   o   o  o  o                | | | RPL SRH
  o   o    o  o     o  o    o  o  o             | | |
 o  o   o  o   o         o   o o                + | +
 o          o             o     o                 |
                   LLN                            v

If this helps you folks, please use it (and if it doesn't, please don't!)

Thanks,

Spencer the AD, where "A" may or may not stand for "ASCII-artist" ...

Take care,

Pascal

-----Original Message-----
From: Spencer Dawkins [mailto:spencerdawkins.ietf@gmail.com<mailto:spencerdawkins.ietf@gmail.com>]
Sent: mercredi 26 octobre 2016 05:40
To: The IESG <iesg@ietf.org<mailto:iesg@ietf.org>>
Cc: draft-ietf-roll-routing-dispatch@ietf.org<mailto:draft-ietf-roll-routing-dispatch@ietf.org>; Alvaro Retana (aretana) <aretana@cisco.com<mailto:aretana@cisco.com>>; Michael Richardson <mcr+ietf@sandelman.ca<mailto:mcr%2Bietf@sandelman.ca>>; roll-chairs@ietf.org<mailto:roll-chairs@ietf.org>; mcr+ietf@sandelman.ca<mailto:mcr%2Bietf@sandelman.ca>; roll@ietf.org<mailto:roll@ietf.org>
Subject: Spencer Dawkins' No Objection on draft-ietf-roll-routing-dispatch-03: (with COMMENT)

Spencer Dawkins has entered the following ballot position for
draft-ietf-roll-routing-dispatch-03: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-roll-routing-dispatch/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In figure 2, I'm a bit confused on what the third-from-the-left vertical line represents - is it also IPv6 in IPv6 plus RPL SRH, or something else?


--- Begin Message ---
A new version of I-D, draft-ietf-roll-routing-dispatch-04.txt
has been successfully submitted by Pascal Thubert and posted to the
IETF repository.

Name:           draft-ietf-roll-routing-dispatch
Revision:       04
Title:          6LoWPAN Routing Header
Document date:  2016-10-26
Group:          roll
Pages:          36
URL:            https://www.ietf.org/internet-drafts/draft-ietf-roll-routing-dispatch-04.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-roll-routing-dispatch/
Htmlized:       https://tools.ietf.org/html/draft-ietf-roll-routing-dispatch-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-routing-dispatch-04

Abstract:
   This specification introduces a new 6LoWPAN dispatch type for use in
   6LoWPAN Route-Over topologies, that initially covers the needs of RPL
   (RFC6550) data packets compression.  Using this dispatch type, this
   specification defines a method to compress RPL Option (RFC6553)
   information and Routing Header type 3 (RFC6554), an efficient IP-in-
   IP technique and is extensible for more applications.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--- End Message ---