Re: [Roll] Part 2: comment resolutions for AD Review of draft-ietf-roll-aodv-rpl-07

Alvaro Retana <aretana.ietf@gmail.com> Tue, 16 June 2020 21:35 UTC

Return-Path: <aretana.ietf@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 1E64B3A07BE; Tue, 16 Jun 2020 14:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 mNyW_HfUjsJm; Tue, 16 Jun 2020 14:35:25 -0700 (PDT)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 BD2DC3A07BD; Tue, 16 Jun 2020 14:35:24 -0700 (PDT)
Received: by mail-wr1-x431.google.com with SMTP id x6so138195wrm.13; Tue, 16 Jun 2020 14:35:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=59QgoxKzL9mqz5TFwhWpOHMYSNe9Tq1G0LSWD+dd+2k=; b=IIrjOAwH5vivkeQQhkd4H9WuN8B5RkjiVO11S5nUqPGZEipiB2cwDjGfABTt7dsh/R jMiZzOtZEHfj3U7HE52MeyIXujOgNjEo/rjrMMfPlLdDFVIq2186AENg0bP7KkwOfejk SEaQiuziMTTra6cAlj1hxtZwJgo5HErPHwa7nXv4BrIxG3FxzGQfYckIZGrhMbu6yHvN CIO3cYYHXQaiAgBbcEBMV3wct/Fp6Z+jxxNM2OnZFVgEseRWEm7zbMKI76DAxNxsawY0 InF/74zqk0WAgCBHyO68P2nQC68KXRo46u+2OWQaQ7ClTCzdOVV91WVcoaYgfI9TOOhE z0Ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=59QgoxKzL9mqz5TFwhWpOHMYSNe9Tq1G0LSWD+dd+2k=; b=Dw7QQh4uT2xnrPpSn9BYtl9KZzEl23NsScsECV3Cq6lAc4uK69UBfYwrbZ5HOM+EUA IzJYw6n0XlRU5LzQe/ssOxE+NrdmI4xc2GOAE+Q/AtCwhAnfJxT7J4MIU7fI4rW73Lpd Z8pQ/eZVLc1FffkZQPzek/GX5ZIQdFkVtkKq5yMpKwJfDt6LMsqcCdWoHCxgxOpeBun3 GJKtS5rdA5j48o2MVt48lesm62LH9xlrnlZ1epVLsE42yo+kZKeGI948xgQA4avwZReC o1hNaOzDXMvjymyvxefP7ODmFHVQ0ii9x65ax8OKEUKTykbjrQDIijixu/9Zphq245d3 j6qg==
X-Gm-Message-State: AOAM5338FEiYqyFDuKXZWmhHBuyX6aqyjbCLlQv4VWjqCZLEygsOQ5zS fZU4LWFspxqmqru/AcmzPtDeZuV90a/XCTZ0UKkp/DCb
X-Google-Smtp-Source: ABdhPJzJ8/3p4jscvZ2BbZR3KeLcJCAShO3Sh5hgFu6ZMfHjKiiaJIQ+waIAFPa5FvdlFqTakudoYlloLCtWfZeKIXg=
X-Received: by 2002:adf:ef83:: with SMTP id d3mr4778537wro.145.1592343323036; Tue, 16 Jun 2020 14:35:23 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 16 Jun 2020 14:35:22 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <81fbfde3-df64-311e-392d-7c091a06fd80@earthlink.net>
References: <81fbfde3-df64-311e-392d-7c091a06fd80@earthlink.net>
MIME-Version: 1.0
Date: Tue, 16 Jun 2020 14:35:22 -0700
Message-ID: <CAMMESsxVKaQcCqaRic8HB7LMcUamDrwOzcO-Yk+kGeN1Cd4BmQ@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, Charlie Perkins <charles.perkins@earthlink.net>
Cc: "draft-ietf-roll-aodv-rpl@ietf.org" <draft-ietf-roll-aodv-rpl@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/NEPy0L9l_c_uu_P-C_8EtzGBQSc>
Subject: Re: [Roll] Part 2: comment resolutions for AD Review of draft-ietf-roll-aodv-rpl-07
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: Tue, 16 Jun 2020 21:35:26 -0000

On May 7, 2020 at 3:52:33 PM, Charlie Perkins wrote:


Charlie:

Hi!

Just a couple of answers to Part 2.

Thanks!

Alvaro.



...
> > 920 10. Security Considerations
> >
> > 922 The security mechanisms defined in section 10 of [RFC6550] and
> > 923 section 11 of [RFC6997] can also be applied to the control messages
> > 924 defined in this specification. The RREQ-DIO and RREP-DIO both have a
> > 925 secure variant, which provide integrity and replay protection as well
> > 926 as optional confidentiality and delay protection.
...
> > [minor] §3 talks about the fact that an RREQ-DIO is a DIO message
> > with the rREQ Option (and there's similar text for the RREP-DIO).
> > However, I think it's confusing to the reader to mention that there are
> > secure variants. I think that expanding the description (at the end of
> > §3) of what exactly the *-DIO messages are (and that the definition
> > includes the secure variants) would go a long way.
>
> Is it O.K. if we note that RREQ and RREP have secure variants, without
> having to reproduce the entire section?

I think so — pointing to rfc6550.



...
> > 1060 Appendix A. Example: ETX/RSSI Values to select S bit
...
> > [minor] It would be really nice to provide a reference for these tests.
> TODO: provide a citation.
> >
> > [minor] Add references for ETX/RSSI.
> TODO: provide a citation.

Pending...