IETF Logo Mail Archive

Re: [Roll] useofrplinfo version 5

Michael Richardson <mcr@sandelman.ca> Mon, 18 July 2016 14:29 UTC

Return-Path: <mcr@sandelman.ca>
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 D67BC12DFC8 for <roll@ietfa.amsl.com>; Mon, 18 Jul 2016 07:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level:
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 tKpa58KAgSLG for <roll@ietfa.amsl.com>; Mon, 18 Jul 2016 07:29:10 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74E7712DF49 for <roll@ietf.org>; Mon, 18 Jul 2016 06:54:53 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 90286200A7 for <roll@ietf.org>; Mon, 18 Jul 2016 10:04:16 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1DE41638D1 for <roll@ietf.org>; Mon, 18 Jul 2016 09:54:52 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <e4d82623-86e1-efd7-b813-de4dedb2eaf8@gmail.com>
References: <b9e569f12a008245ef824e340f510dff@xs4all.nl> <e4d82623-86e1-efd7-b813-de4dedb2eaf8@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20717.1468850092.1@obiwan.sandelman.ca>
Date: Mon, 18 Jul 2016 09:54:52 -0400
Message-ID: <20718.1468850092@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/owHCu4Qk5qHH6zPI-4pJ9U0_lAM>
Subject: Re: [Roll] useofrplinfo version 5
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: Mon, 18 Jul 2016 14:29:13 -0000

In trying to update useofrplinfo and to answer Cenk, I find myself
trying to explain inserting per-hop IPIP headers.  I am dissatisfied with
this text, and I see a clearer explanation:

             <section title="hop-by-hop IPv6-in-IPv6 headers">
                <t>
                The term "hop-by-hop IPv6-in-IPv6" header refers
                to: adding a header
                that originates from a node to an adjacent node,
                using the addresses (usually the GUA or ULA, but could use
                the link-local addresses)
                of each node.  If the packet must traverse multiple
                hops, then it must be decapsulated at each hop, and then
                re-encapsulated again in a similar fashion.

Can anyone write this clearer?


--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email