IETF Logo Mail Archive

Re: [C310] AUTH48 [JM]: RFC 9031 <draft-ietf-6tisch-minimal-security-15.txt> NOW AVAILABLE

Mališa Vučinić <malisa.vucinic@inria.fr> Wed, 12 May 2021 17:21 UTC

Return-Path: <malisa.vucinic@inria.fr>
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 3E800F407DC; Wed, 12 May 2021 10:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -96.37
X-Spam-Level:
X-Spam-Status: No, score=-96.37 tagged_above=-999 required=5 tests=[HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=2, SPF_PASS=-0.001, SUBJECT_IN_WHITELIST=-100, URIBL_BLOCKED=0.001] 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 h_fy9_2EMTYH; Wed, 12 May 2021 10:21:31 -0700 (PDT)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by rfc-editor.org (Postfix) with ESMTPS id BE3DAF407D9; Wed, 12 May 2021 10:21:30 -0700 (PDT)
IronPort-HdrOrdr: A9a23:xwr1VK0IcsxL6V9ovCcjsAqjBIokLtp133Aq2lEZdPRUGvb3qyl0poV+6faaslwssR0b9exofZPwI080l6QV3aA0PbOvGBbro3GpKoYK1/qG/9SIIUSXygce79YCT0EUMrDN5C9B7foSjjPWLz9t+rK6zJw=
X-IronPort-AV: E=Sophos;i="5.82,293,1613430000"; d="p7s'?scan'208";a="381296074"
Received: from adsl-46-161-103156.crnagora.net (HELO [192.168.100.4]) ([46.161.103.156]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES256-GCM-SHA384; 12 May 2021 19:21:29 +0200
User-Agent: Microsoft-MacOutlook/10.11.0.180909
Date: Wed, 12 May 2021 19:21:27 +0200
From: Mališa Vučinić <malisa.vucinic@inria.fr>
To: Jean Mahoney <jmahoney@amsl.com>, Michael Richardson <mcr+ietf@sandelman.ca>
CC: rfc-editor@rfc-editor.org, jonathan.simon@analog.com, pister@eecs.berkeley.edu, ek.ietf@gmail.com, 6tisch-ads@ietf.org, 6tisch-chairs@ietf.org, c310@rfc-editor.org
Message-ID: <38780CBC-1554-4026-B612-CFA119D85B0A@inria.fr>
Thread-Topic: [C310] AUTH48 [JM]: RFC 9031 <draft-ietf-6tisch-minimal-security-15.txt> NOW AVAILABLE
References: <20210511062119.002BEF407AA@rfc-editor.org> <A94F0C78-2E71-45CB-9217-7E9F9B1F37B2@inria.fr> <c01e7b24-43f8-7bbe-acce-2a3ab36dab1f@amsl.com> <16711.1620836053@localhost> <2484e7a2-b4b7-b568-2758-f65269b6521f@amsl.com>
In-Reply-To: <2484e7a2-b4b7-b568-2758-f65269b6521f@amsl.com>
Mime-version: 1.0
Content-type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha256"; boundary="B_3703692087_1870641635"
Subject: Re: [C310] AUTH48 [JM]: RFC 9031 <draft-ietf-6tisch-minimal-security-15.txt> NOW AVAILABLE
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: Wed, 12 May 2021 17:21:36 -0000

Jean,

Could you do the following small changes before my final approval. Right now, the table of contents shows:
- Link-layer Configuration (note the lowercase "l" in "layer")
- Network-Layer Configuration (note the uppercase "L" in "Layer")
- Application-Level Configuration (note the use of "Level")

I propose that we use the "*-Layer" form for all three cases.

On a similar note, I propose to replace the following two occurrences of "level" with "layer" in the text:
Section 8.3.1: "relates to the application-level handling"
Section 8.4.2, Table 5: "Identifies the array carrying one or more link-level cryptographic keys"

Thanks!

Mališa

On 12/05/2021 18:55, "Jean Mahoney" <jmahoney@amsl.com> wrote:

    Michael,
    
    Thank you for your response. We have noted your approval on the AUTH48 
    status page:
    
        https://www.rfc-editor.org/auth48/rfc9031
    
    We'll await further word from Mališa regarding other AUTH48 changes 
    and/or approval.
    
    Best regards,
    
    RFC Editor/jm
    
    On 5/12/21 11:14 AM, Michael Richardson wrote:
    > Jean Mahoney <jmahoney@amsl.com> wrote:
    >      > Thank you for your quick response. We have updated the document with
    >      > your feedback:
    >
    >      >    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
    >      > https://www.rfc-editor.org/authors/rfc9031-diff.html (all changes)
    >      > https://www.rfc-editor.org/authors/rfc9031-auth48diff.html (AUTH48
    >      > changes)
    >
    >      > We have also updated the terms "layer-2" and "layer-3" to "Layer 2" and
    >      > "Layer 3" to match changes in RFC 9030.
    >
    > I have been through the changes, and I approve of them all.
    > Thank you.
    >
    >
    >
    > --
    > Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
    >             Sandelman Software Works Inc, Ottawa and Worldwide
    >
    >
    >
    >

v2.23.0 | Report a Bug | By Email