IETF Logo Mail Archive

Re: [Roll] Benjamin Kaduk's Discuss on draft-ietf-roll-turnon-rfc8138-14: (with DISCUSS and COMMENT)

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 12 September 2020 17:51 UTC

Return-Path: <mcr+ietf@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 2D4ED3A0C76; Sat, 12 Sep 2020 10:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 yGwzgE_NCsp5; Sat, 12 Sep 2020 10:51:49 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0DB23A0870; Sat, 12 Sep 2020 10:51:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id F2778389D6; Sat, 12 Sep 2020 13:21:41 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kCeZv5zKPvwc; Sat, 12 Sep 2020 13:21:31 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5BA02389CE; Sat, 12 Sep 2020 13:21:31 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B2929215; Sat, 12 Sep 2020 13:42:44 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
cc: Benjamin Kaduk <kaduk@mit.edu>, "roll-chairs@ietf.org" <roll-chairs@ietf.org>, Ines Robles <mariainesrobles@googlemail.com>, "draft-ietf-roll-turnon-rfc8138@ietf.org" <draft-ietf-roll-turnon-rfc8138@ietf.org>, The IESG <iesg@ietf.org>, Alvaro Retana <aretana.ietf@yahoo.com>
In-Reply-To: <8F19C753-DCA0-4A32-BA3B-A124B2F7F745@cisco.com>
References: <159968972884.1065.3876077471852624744@ietfa.amsl.com> <MN2PR11MB35659A0710E687A7C9995E6ED8270@MN2PR11MB3565.namprd11.prod.outlook.com> <20200910200744.GE89563@kduck.mit.edu> <17053.1599841430@localhost>, <20200911162617.GQ89563@kduck.mit.edu> <8F19C753-DCA0-4A32-BA3B-A124B2F7F745@cisco.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 12 Sep 2020 13:42:44 -0400
Message-ID: <13242.1599932564@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/OorL6Yu-muuen6N81NB8fLUu-uY>
Subject: Re: [Roll] Benjamin Kaduk's Discuss on draft-ietf-roll-turnon-rfc8138-14: (with DISCUSS and 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: Sat, 12 Sep 2020 17:51:53 -0000

Pascal Thubert \(pthubert\) <pthubert=40cisco.com@dmarc.ietf.org> wrote:
    > Now I’m unsure Michael and I agree anymore.
    > What will today’s developer code?

    > We ask him to test if mop is < 7
    > What value will the developer place in his code if the test returns
    > false?

That's a good question.
Pascal, it your intention that 8138 be turned on in this case?

I'm not opposed to that conclusion, but I thought that the goal was to move
the signaling to mopex/capabilities/TBD?

Would there be cases in the future where ONLY 8138 compression would be coded?

We have set the situation where if a node does not understand the MOP, it can
be a leaf, but 8138 incompatibility makes that not work.


    > Leaving it to the implementation will have some people choose true and
    > others false. This is not what we want.

    > We want to control what the code does so we can expect it in the future
    > and build our backward compatibility based on that sure knowledge.

    > Before the draft the default was no compression. Quite naturally since
    > initially it did not exist.

    > Also we discussed on the ML that for RPLv2 all implementations MUST support the compression.

Just consider that for some link layers, 8138 compression might not make sense.

    > In which case it is a better default for a coder today to decide to use
    > the compression for mop 7, isn’t it?
    > I hope I make the case right. Just think you’re coding it!

We're assuming someone coding today.
Someone who is not writing MOP=7 code, has no mopex or capabilities code,
because we haven't defined that.
We agree that the "T" flag does not exist, and should be checked.
Such a node would be a leaf.

I can live with defaulting 8138 to be on for MOP=7 for link layers for which
8138 is appropriate. (Someone coding today will know what link layers they
have)

--
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