Re: [Roll] Martin Duke's No Objection on draft-ietf-roll-turnon-rfc8138-12: (with COMMENT)

Martin Duke <martin.h.duke@gmail.com> Wed, 02 September 2020 17:23 UTC

Return-Path: <martin.h.duke@gmail.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 006923A0BE9; Wed, 2 Sep 2020 10:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 EVjByiT2xzlt; Wed, 2 Sep 2020 10:23:29 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 805E13A0BE6; Wed, 2 Sep 2020 10:23:29 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id m23so6633443iol.8; Wed, 02 Sep 2020 10:23:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JrJA4nWJiK6l7WCs56keg9glqq8fnpb4Puz3kdP31s0=; b=jnYpF/2Qyz3Jw7YeqbiIqsXagreiHRtl+SEeapeVqVQTz7T36xyiAjvaPMOyGI0VFp jerse1x5je995jLqJaVK4C41Jy8h+qHStH8uKXgvwsPtQZvDrWqMbybbrk17JOJnEHIw LyQQw+x2hlhchjm+PJzfgurufu/DfYTvtnukFTMDxuo7SOPXOCtzdgzwIBzZRH3qhKFr KGWQOG6/k51Au8fFzojwEzdnwZLURkxZADG7w5pnXE7pOsSnBSoLsPfoDSNsm+sq8WcZ ksa49eAqNdQFtKgr2LyeSWBF66xIHtV8hVtguf5MUgrNjhJwn4pMrJ3uxHX5pBIblFWm 0EwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JrJA4nWJiK6l7WCs56keg9glqq8fnpb4Puz3kdP31s0=; b=lnJTnRqHx/HYeNXYQtWZnWBI0iSLDNw35U7OqmqoA/7LdS7EAUCpRvOeXVipKaEspQ H47Dmdk+jiC0s/AzPvgdDhHARgu3p7L0vi0S+gawCoWoBD27zuKNBJoYvskcsPwuVES/ IolY+bwhug60i5wy0t8hd8W9hNFlaHE7MeprYu7ojNyBRIv1lpviCoCh+XzgG5aD31iq sYlTi2o0H3k0XM/ugyauJp2EOSjXbmgL/hZyERdNQxD7GCpiEOWmR7Ygw7t54g4gI00c T29IE+kMIe23ss3y+2ALQoKN+KzlHZcmESWgbW1Pe7FfBpirI/foV+alNAYmstXxoA23 XbSA==
X-Gm-Message-State: AOAM532nvIqlwAUBpdWiINOuc/FmGATQ03bj+b0vp30dP6bZWVyZPB6X eqD9lr4hCyB0FI9AZKDSLOXcV5UDbm9Px0XLAW8=
X-Google-Smtp-Source: ABdhPJxfKExqmwj/PgToQqlGjv8II/NCPxF/SK/qkVQaAqTH9SPKgIX+F0BUplncu1z+1o2lVQOyLPxxwlSNn1r9/j4=
X-Received: by 2002:a02:a047:: with SMTP id f7mr4184977jah.31.1599067408722; Wed, 02 Sep 2020 10:23:28 -0700 (PDT)
MIME-Version: 1.0
References: <159906391966.364.6288639877267418145@ietfa.amsl.com> <55B5F8AC-7965-4A56-A541-AD64CC2D103B@cisco.com>
In-Reply-To: <55B5F8AC-7965-4A56-A541-AD64CC2D103B@cisco.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 02 Sep 2020 10:23:19 -0700
Message-ID: <CAM4esxRb+2MD8rDpNhYAGeK-+X7jgKC+6r1Fu0N3W28PmjazLg@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-roll-turnon-rfc8138@ietf.org" <draft-ietf-roll-turnon-rfc8138@ietf.org>, "roll-chairs@ietf.org" <roll-chairs@ietf.org>, "roll@ietf.org" <roll@ietf.org>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, "mariainesrobles@googlemail.com" <mariainesrobles@googlemail.com>
Content-Type: multipart/alternative; boundary="000000000000de6d1105ae57e4fb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/LbUyvB7m465cKCuJTZQJ3QWELvE>
Subject: Re: [Roll] Martin Duke's No Objection on draft-ietf-roll-turnon-rfc8138-12: (with COMMENT)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 02 Sep 2020 17:23:31 -0000

Ah, OK, I understand what is happening now though I would not have gotten
that from the text.

1. It is critical that IANA considerations then add instructions to add MOP
codepoint 7 to the registry.

2. May I suggest new text for this paragraph:
OLD

“Section 6.3.1 of [RFC6550] defines a 3-bit Mode of Operation (MOP) in
the DIO Base Object. This specification applies to MOP values 0 to 6. For a
MOP
value of 7, the compression MUST be used by default regardless of the
setting
of the "T" flag.“

NEW
"Section 6.3.1 of [RFC6550] defines a 3-bit Mode of Operation (MOP) in
the DIO Base Object. This specification adds codepoint 7 to the registry
for this field.   For a MOP
value of 7, the compression MUST be used by default regardless of the
setting
of the "T" flag.“

Martin

On Wed, Sep 2, 2020 at 9:35 AM Pascal Thubert (pthubert) <pthubert@cisco.com>
wrote:

> Hello Martin
>
> Many thanks for your time and review!
>
> Let’s see below :
>
> ----------------------------------------------------------------------
>
> COMMENT:
> ----------------------------------------------------------------------
>
> Sec 3. “Section 6.3.1 of [RFC6550] defines a 3-bit Mode of Operation (MOP)
> in
> the DIO Base Object. This specification applies to MOP values 0 to 6. For
> a MOP
> value of 7, the compression MUST be used by default regardless of the
> setting
> of the "T" flag.“
>
> Is “This specification” referring to 6550 or roll-turn on-rfc8138? I have a
> feeling you mean RFC6550. But that document only defines MOPs 0-3!
>
>
> This specification means this draft not RPL.
> Not sure how to improve this text. Curiously it went through a lot of
> massaging already.
>
> On a similar note, it might be useful to establish an IANA registry for MOP
> code points so that change control for these bits is clearer.
>
> Good point, and we actually did it.
>
> Please see https://www.iana.org/assignments/rpl/rpl.xhtml#mop
>
> Did you find anything else we could clarify ?
>
> Take care,
>
> Pascal
>