Re: [6lo] Genart last call review of draft-ietf-6lo-backbone-router-14

elwynd <> Fri, 07 February 2020 19:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6CE0C120926; Fri, 7 Feb 2020 11:47:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qaRojArycgq7; Fri, 7 Feb 2020 11:47:21 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 369FF120903; Fri, 7 Feb 2020 11:47:21 -0800 (PST)
Received: by with SMTP id t14so4055673wmi.5; Fri, 07 Feb 2020 11:47:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=message-id:from:savedfromemail:date:subject:in-reply-to:importance :to:cc:mime-version; bh=Kf0u6/fGONi2HXfzoKrdNYHRDbtSLpQzFED/xZrxXa4=; b=EGOVUjlzNruphtUycr98Xqh6gFx3k5kSc5ORV56w4E3UoUh0mDBoHy5KjzeS/6KlNm ROMZDCBtTSqpw36+vIW5KFCpuP17woTeZV3cnMJu3r7C+tqCO3QlIR4/xhlYzjsWHFhp n/JIhjjvSMNPmQNEUtyeYp/tIPC8KnNZ/EElTFjjZJCILqlA6QozhYfVAx4Wn/YZze22 6qE4xl9OokfhMYsELyKz6IsuKf7lEHLToOZnh73aNoOKNC0scmJ3yArif79FDcIl4lK5 sDETCV2BYrQ/MavZrubn/EppwLP9/v4w7vwwPqMH7/v9yOK/DP2I5kThlZREWh8yuJOF dzHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:message-id:from:savedfromemail:date:subject :in-reply-to:importance:to:cc:mime-version; bh=Kf0u6/fGONi2HXfzoKrdNYHRDbtSLpQzFED/xZrxXa4=; b=fnj50StFwDWhBUfBJI3E+fYohZfoaH6ck5FxaMKp6l2RBWIC2nT80jIpb3kXxwWJDs HJqe+vZ+GVzslIh871R45IuUjeKiQCjk8B/w/uwGN7SIAFJR5w/Kz7KP0M5HlKUYTADC 19gipOvSUTMftGS+miTChhtEMcIbFU7QPDXIBT4+CCM/jxuEZ2DSRFIhmlVr+gYmMJZu PHVoi3bO13VS/cq5RE/Cit/PNlg37FWchhQN+rLpBvk8ngBkwQwpBo97dLQ46k9enU/J Rgh+HMwbTMWVGxkKitL7dvkYn6YMasZ85+XYfDC5xm7u6fw6lRBE0ta5Hgiw8qm4lIXh ebjA==
X-Gm-Message-State: APjAAAWCe3D8V+6uN0HDPYKA1eBy9ZW04P+8RWxVMWIUUBnmL2kqUbyx m3heRVu5zJfkY+msrorw4zA=
X-Google-Smtp-Source: APXvYqwxipwxlqy9oBLbvclGC3DqVS10Vo3/C3uVJXMh4qTZNMKumvb4c64VfyWP3MwYgV75/kJ0rA==
X-Received: by 2002:a1c:a9c3:: with SMTP id s186mr5616514wme.64.1581104839634; Fri, 07 Feb 2020 11:47:19 -0800 (PST)
Received: from ?IPv6:2001:8b0:bf:1:cb6a:ea1c:d1ea:1910? ( [2001:8b0:bf:1:cb6a:ea1c:d1ea:1910]) by with ESMTPSA id d16sm5048024wrg.27.2020. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Feb 2020 11:47:18 -0800 (PST)
Message-ID: <>
From: elwynd <>
X-Google-Original-From: elwynd <>
Date: Fri, 07 Feb 2020 19:47:18 +0000
In-Reply-To: <>
Importance: normal
To: "Pascal Thubert (pthubert)" <>, "" <>
Cc: "" <>, "" <>, "" <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=""
Archived-At: <>
Subject: Re: [6lo] Genart last call review of draft-ietf-6lo-backbone-router-14
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 07 Feb 2020 19:47:26 -0000

Hi, Pascal.Thanks for the rapid turnround!I did check the abbreviations list for the well-knownness of MAC.  There are a multitude of possible expansions so it is not marked as well-known.But otherwise... that looks good and we are all done.It is pretty complex system and I can't say that my brain was capable of running a proper simulation ;-) but it seemed to cover most of the bases that I could think of.  Are there existing implementations (I'd guess so!) - if so it might be worth mentioning somethng about them but that is a nice-to-have.Cheers,ElwynSent from Samsung tablet.
-------- Original message --------From: "Pascal Thubert (pthubert)" <> Date: 07/02/2020  13:36  (GMT+00:00) To: Elwyn Davies <>om>, Cc:,, Subject: RE: Genart last call review of draft-ietf-6lo-backbone-router-14 Hello Elwyn:Many thanks for your review!Let's see below:> General: s/i.e. /i.e., / (4 places), s/e.g. /e.g.,/ (2 places)Done> > Abbreviations: The definition of abbreviations in this document is inconistent.> There is a list of abbreviations but it is not complete; many abbreviations are> introduced in the text in the usual way and there are some that are not> expanded. Please be consistent - a complete list would be helpful, especially> as some are used before the abbreviations section.Made a pass> References to Neighbor Solicitation/Advertisement messages: The formats> NS(xxxx) and NA(xxxx) are used to refer to various NS/NA messages. Please> add an explanation of this convention and a definition of the various> messages referred to.Added the abbreviations> Use of Layer-2 and Layer-3:  These terms are not normally  hyphenated.Removed the hyphen.> s1: Term STA used for a 'node': Please expand this abbreviation and possibly> explain why it is used (I am unclear how it is derived).STA and AP are 802.11 terminology,  STA means station I believe. Changed to "connectivity to the end node (the Wi-Fi STA)"> > s1, para 5: s/Like/In the same way as/Done> > s1, para 5: ID is not a well-known abbreviation - please expand on first use.Added in the "Abbreviation" section which is where it is first used> > s1, para 9: Need to expand MAC.I think we got directives from RFC editor not to expand very well-known terms. If my memory serves me that was one.> > s2.2, "Sleeping Proxy": It might be useful to add in " which might be in a sleep> state in a low power network"."   Sleeping Proxy         A 6BBR acts as a Sleeping Proxy if it answers ND Neighbor         Solicitations over the Backbone on behalf of the Registering         Node which might be in a sleep state in a low power network.         The Sleeping Proxy that is also a Bridging Proxy will         preferably forward the relevant messages to the Registering         Node as unicast frames in accord to the duty cycle of the         Registering Node and let it respond."> > s2.2, "Routing Proxy": Need to expand TLLA.Done> > s3, para 1: s/The next/The following/ Done> > s3, 2nd set of bullets, bullet #2: s/This includes participating to the>       solicited-node multicast address/This includes responding to messages>       addressed tothe solicited-node multicast address/The point is really the MLD thingy. What about:"     This includes joining the multicast group associated to      the SNMA derived from the Registered Address as specified in      section 7.2.1. of [RFC4861] over the Backbone."> > s3, 2nd set of bullets, bullet #3: Expand NUD on first use (currently expanded> twice in sss6 and 8).Done and looked up /updated the other cases > s3.1: Expand SLLAO on first use.done> s3.3, para at bottom of page 13 just before Figure 5: s/is a transmitted as a> multicast/is transmitted as a multicast /done> s3.3, last para: s/suggests using RPL/suggests using the RPL routing protocol/Done > s3.4, last para: s/details/detail/Done > s3.5, para 1: s/as silently ignored./are silently ignored./Done> s4, last para: s/the MTU MUST have a same value/the MTU MUST have the> same value/Done, found several places> s5, para 2: s/It results that a 6LBR MUST be capable of maintaining a> state/Consequently a 6LBR MUST be capable of maintaining state/ Done> s5, para 3: s/ which may be avoided of/ which may be avoided if/Done> s5, para 5: Expand TLLAO on first use.Done> s9: It would be useful to add a forward ref to s12 where the value of> TENTATIVE_DURATION is defined.Done, same for STALE_DURATION> > s9.1: Remove empty second bullet.Was gone already> > Titles of ss9.1, 9.2 and 9.3: I Think these should be "Operations on...."Changed> > s9.2, 1st bullet: s/small timer/timer with a short setting/.  Is it possible to> recommend any values here or indicate how to assign a suitable value?Added " e.g., a few seconds to a minute;"> > ss9.2, 9.3: It would be useful to add a forward ref to s12 where the value of> STALE_DURATION is defined.Done per the above commentMany thanks again Elwyn!I'm publishing right away as version 15 so people do not suffer from those nits again.All the bestPascal