Re: [C310] "6TiSCH" in titles (9030-9033)

Jean Mahoney <jmahoney@amsl.com> Fri, 14 May 2021 14:30 UTC

Return-Path: <jmahoney@amsl.com>
X-Original-To: c310@rfc-editor.org
Delivered-To: c310@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 1BF76F407E4; Fri, 14 May 2021 07:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -97.71
X-Spam-Level:
X-Spam-Status: No, score=-97.71 tagged_above=-999 required=5 tests=[MIME_8BIT_HEADER=0.3, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=2, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WELCOMELIST=-0.01, USER_IN_WHITELIST=-100] autolearn=no autolearn_force=no
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2B4YkY5hV_x; Fri, 14 May 2021 07:30:25 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 43C71F407E3; Fri, 14 May 2021 07:30:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6353238A089; Fri, 14 May 2021 07:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aOGkJqa-vf0b; Fri, 14 May 2021 07:30:30 -0700 (PDT)
Received: from AMSs-MBP.localdomain (unknown [47.186.1.92]) by c8a.amsl.com (Postfix) with ESMTPSA id 0066A38A087; Fri, 14 May 2021 07:30:29 -0700 (PDT)
To: Mališa Vučinić <malisa.vucinic@inria.fr>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: "6tisch-ads@ietf.org" <6tisch-ads@ietf.org>, "c310@rfc-editor.org" <c310@rfc-editor.org>, "6tisch-chairs@ietf.org" <6tisch-chairs@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
References: <D855FC99-A501-49EE-92F4-50DE15EC1FCC@amsl.com> <FAD83BD7-97C8-4462-AA73-19C5BEC2094B@cisco.com> <57DC8BFB-2512-4DF2-85C5-02803573A403@cisco.com> <5405827a-5c27-204b-e83f-361b2cc3053e@amsl.com> <01314ED8-00B1-45B6-BD30-35E9E9FBF2A7@cisco.com> <DD4651A3-8E65-4821-8C6C-B56EFDE5972B@inria.fr> <9112fe72-13f4-3328-9767-ed389e6fa94a@amsl.com> <0BDCB578-0100-447A-A8BF-5076687B5BEB@inria.fr>
From: Jean Mahoney <jmahoney@amsl.com>
Message-ID: <6980f065-6fdb-4522-184b-9c4d4f515acb@amsl.com>
Date: Fri, 14 May 2021 09:30:29 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <0BDCB578-0100-447A-A8BF-5076687B5BEB@inria.fr>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: [C310] "6TiSCH" in titles (9030-9033)
X-BeenThere: c310@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <c310.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/c310>, <mailto:c310-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/c310/>
List-Post: <mailto:c310@rfc-editor.org>
List-Help: <mailto:c310-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/c310>, <mailto:c310-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2021 14:30:29 -0000

Mališa,

We have noted your approval on the AUTH48 status page:

https://www.rfc-editor.org/auth48/rfc9031

As approvals are now complete, we will move this document forward in the 
publication process (along with the other documents in its cluster when 
they have completed AUTH48):

https://www.rfc-editor.org/auth48/C310

Thank you!

RFC Editor/jm

On 5/14/21 1:55 AM, Mališa Vučinić wrote:
> Jean, all,
>
> I approve the document to be published in its current state. Thanks.
>
> Mališa
>
> On 14/05/2021 01:02, "Jean Mahoney" <jmahoney@amsl.com> wrote:
>
>      Mališa,
>      
>      We have updated RFC 9031 based on your feedback:
>      
>          https://www.rfc-editor.org/authors/rfc9031-lastrfcdiff.html
>      
>          https://www.rfc-editor.org/authors/rfc9031.txt
>          https://www.rfc-editor.org/authors/rfc9031.pdf
>          https://www.rfc-editor.org/authors/rfc9031.html
>          https://www.rfc-editor.org/authors/rfc9031.xml
>      
>      May we mark your approval on the AUTH48 status page?
>      
>          https://www.rfc-editor.org/auth48/rfc9031
>      
>      Best regards,
>      
>      RFC Editor/jm
>      
>      
>      On 5/12/21 3:51 PM, Mališa Vučinić wrote:
>      > Jean, Pascal,
>      >
>      > Among the co-authors of RFC-to-be 9031, we discussed yesterday exactly the same topic and we would like to drop the "e" in 9031 as well, wherever possible.
>      >
>      > The occurrences of "15.4e" in 9031 are due to:
>      > (1) Expansion of the 6TiSCH acronym in the abstract (x1)
>      > (2) Top-level IANA registry references (x3)
>      > (3) Titles of RFC 7554 and RFC 8180 that are normative references (x2)
>      >
>      >  From Jean's mail, my understanding is that we can get rid of (1) and (2).
>      >
>      > If this could be incorporated in 9031 before we proceed with the next stage, that would be absolutely great!
>      >
>      > Mališa
>      >
>      > On 12/05/2021 22:29, "c310 on behalf of Pascal Thubert (pthubert) via c310" <c310-bounces@rfc-editor.org on behalf of c310@rfc-editor.org> wrote:
>      >
>      >      Hello Jean
>      >
>      >      Great catch! Please remove the e.
>      >
>      >      The change reflects the historical fact that the 802.15.4e amendment was retrofitted in the ieee 802.15.4 standard in 2015.
>      >
>      >      I do not see that we need an approval to recognize this.
>      >
>      >      Take care,
>      >
>      >      Pascal
>      >
>      >      > Le 12 mai 2021 à 22:12, Jean Mahoney <jmahoney@amsl.com> a écrit :
>      >      >
>      >      > Pascal,
>      >      >
>      >      > While assessing the document updates to change the 6TiSCH acronym expansion to "IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4" (dropping the "e" from "15.4e"), we noticed that the name of the top-level 6TiSCH IANA registry contains "e":
>      >      >
>      >      >    IPv6 Over the TSCH Mode of IEEE 802.15.4e (6TiSCH)
>      >      >    https://www.iana.org/assignments/_6tisch/_6tisch.xhtml
>      >      >
>      >      > If we change the acronym expansion in the C310 documents, should this registry name also be updated?  If so, who needs to approve the change?
>      >      >
>      >      > Best regards,
>      >      >
>      >      > RFC Editor/jm
>      >      >
>      >      >> On 5/11/21 12:56 PM, Pascal Thubert (pthubert) wrote:
>      >      >> Happy to remove the ´e ´ in 15.4e
>      >      >>
>      >      >>
>      >      >> Regards,
>      >      >>
>      >      >> Pascal
>      >      >>
>      >      >>>> Le 11 mai 2021 à 19:55, Pascal Thubert (pthubert) <pthubert@cisco.com> a écrit :
>      >      >>>
>      >      >>> Dear all,
>      >      >>>
>      >      >>> Honestly I’d rather keep everything as is.
>      >      >>> If we change something I’d suggest adding (6TiSCH) at the end of the title of 9030.
>      >      >>>
>      >      >>>
>      >      >>> Regards,
>      >      >>>
>      >      >>> Pascal
>      >      >>>
>      >      >>>> Le 11 mai 2021 à 19:28, Alice Russo <arusso@amsl.com> a écrit :
>      >      >>>>
>      >      >>>> Authors of RFCs-to-be 9030, 9031, 9032, and 9033,
>      >      >>>>
>      >      >>>> We'd like to more closely align the titles of these documents; may "6TiSCH" be expanded?  Please reply if you have a preference. Essentially:
>      >      >>>>
>      >      >>>> May the titles be updated as shown in Option A (expanding "6TiSCH")? If so, is it accurate to change "802.15.4" to "802.15.4e" in the cases where it did not appear (9030 and 9032)?
>      >      >>>>
>      >      >>>> -- Original titles (various handling):
>      >      >>>> 9030 - An Architecture for IPv6 over the TSCH mode of IEEE 802.15.4
>      >      >>>> 9031 - Constrained Join Protocol (CoJP) for 6TiSCH
>      >      >>>> 9032 - IEEE 802.15.4 Information Element encapsulation of 6TiSCH Join and Enrollment Information
>      >      >>>> 9033 - 6TiSCH Minimal Scheduling Function (MSF)
>      >      >>>>
>      >      >>>> -- Option A (expanding "6TiSCH"):
>      >      >>>> 9030 - An Architecture for IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4e (6TiSCH)
>      >      >>>> 9031 - The Constrained Join Protocol (CoJP) for IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4e (6TiSCH)
>      >      >>>> 9032 - IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4e (6TiSCH) Information
>      >      >>>> Element Encapsulation of Join and Enrollment Information
>      >      >>>> 9033 - Minimal Scheduling Function for IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4e (6TiSCH)
>      >      >>>>
>      >      >>>> -- Option B (if not expanding "6TiSCH"):
>      >      >>>> 9030 - An Architecture for 6TiSCH
>      >      >>>> 9031 - Constrained Join Protocol (CoJP) for 6TiSCH
>      >      >>>> 9032 - IEEE 802.15.4 Information Element Encapsulation of 6TiSCH Join and Enrollment Information
>      >      >>>>    -> [or perhaps it could be simplified as follows or otherwise.]
>      >      >>>>       Encapsulation of 6TiSCH Join and Enrollment Information Elements
>      >      >>>> 9033 - 6TiSCH Minimal Scheduling Function (MSF)
>      >      >>>>
>      >      >>>> Thank you.
>      >      >>>> RFC Editor/ar
>      >      >>>> --
>      >      >>>>
>      >      >>>> Relevant files:
>      >      >>>> https://www.rfc-editor.org/authors/rfc9030.html
>      >      >>>> https://www.rfc-editor.org/authors/rfc9031.html
>      >      >>>> https://www.rfc-editor.org/authors/rfc9032.html (draft-ietf-6tisch-enrollment-enhanced-beacon-14; not yet available)
>      >      >>>> https://www.rfc-editor.org/authors/rfc9033.html
>      >      >>>> --
>      >      >>>> c310 mailing list
>      >      >>>> c310@rfc-editor.org
>      >      >>>> https://www.rfc-editor.org/mailman/listinfo/c310
>      >      --
>      >      c310 mailing list
>      >      c310@rfc-editor.org
>      >      https://www.rfc-editor.org/mailman/listinfo/c310
>      >
>