Re: [Sframe] Éric Vyncke's Block on charter-ietf-sframe-00-00

Emad Omara <emadomara@google.com> Tue, 15 September 2020 05:20 UTC

Return-Path: <emadomara@google.com>
X-Original-To: sframe@ietfa.amsl.com
Delivered-To: sframe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E62383A0DE6 for <sframe@ietfa.amsl.com>; Mon, 14 Sep 2020 22:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 ILly1MA97bHy for <sframe@ietfa.amsl.com>; Mon, 14 Sep 2020 22:20:44 -0700 (PDT)
Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (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 521E33A0DDE for <sframe@ietf.org>; Mon, 14 Sep 2020 22:20:44 -0700 (PDT)
Received: by mail-ua1-x929.google.com with SMTP id j12so623278ual.7 for <sframe@ietf.org>; Mon, 14 Sep 2020 22:20:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=edeum7ImTvQe/ikyEGqTL3MzEyMobbgtQHRnuXVCFlM=; b=Q2BRHCwVIbfFSe74XNzM08vk2PZA8mjrHiDizIvsX7Q8Mb5UdYbMKWF0QoJG+BWO+x XH5w2o/LcC176uZ2T8YBihkBt8fQAz3N7+BwugaUn16Kxa5lZEqT4lwImSLuUkYZEOXQ 3kbCerGtYeXkqREVsGaKPXe/XPX91gBSbAcQ0uxbphDCCbAww5MED2kI06329dW7Tgz6 ypn2+/6qGBRS1kgASqql6LbXTRxRHHGwQH/pNmushT5N+dwSosnHXCpMt5rwAyeytAbm DCHAKi6Ddgpo+wE/rNYgsgvG30UPisABlo4lpbYxCz+hZxuq/VfFshNvJLQOTdBKVeUn ghvA==
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=edeum7ImTvQe/ikyEGqTL3MzEyMobbgtQHRnuXVCFlM=; b=opY3TVse2uZUWb60vxyUxvNQxcwvrJktCNxyHkDfLbhz4qnPTSU2F9Zf5qWW5ALIXW iHj8jmQkx8FprmWZvzqTLEnXSfxm35iPw/2BG94bDJiYDYKckesj+b1pocBFStEoq2+Y tCPxn7WYtTQ6ov3kQra8B7OGlZwXyjohYXnF/VgKPwfZJRM0z7KFK67KSFpzvfr4xoHf uVFl0g3l5gDSrOeeblBpi/KGnQR/XYXIVeT9Nm45ok8mHIYCnu9jljc6IBhvil87VLAo /c5R49lY6Y0C4y/iEnErsadn4W0ui9tJ+WtiT79YXuZRZn0EKwBxmE99gghvmbyfIZ5m Q4hg==
X-Gm-Message-State: AOAM531TXjI1aNlK7u1aMQy4ysCubR4veNjKQ2IwbjnmirtHOFzg0rjE wiJzssm5kpOI+a/ViszLfa1pPbhoiJM+xeYwYoTV
X-Google-Smtp-Source: ABdhPJzAcfYQeQh4gOZMZTIJM+EQrpwz/Sje/GYZ1wm+klt5bbvF5FEsB2XmqnuElfnvjB8Y3jYGgosUY/qIs0zyIy4=
X-Received: by 2002:ab0:20b6:: with SMTP id y22mr8739939ual.30.1600147243122; Mon, 14 Sep 2020 22:20:43 -0700 (PDT)
MIME-Version: 1.0
References: <CAL02cgRE8LjzNX-PF=iz+FEH0JkCpzaLyCO=zbKAgUTvV2hwYA@mail.gmail.com>
In-Reply-To: <CAL02cgRE8LjzNX-PF=iz+FEH0JkCpzaLyCO=zbKAgUTvV2hwYA@mail.gmail.com>
From: Emad Omara <emadomara@google.com>
Date: Mon, 14 Sep 2020 22:20:30 -0700
Message-ID: <CAHo7dC-sOOu92e=YFUXJNZ2nJ590LuyKRJjK+JmJjxLKFf7qOQ@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Cc: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, DISPATCH <dispatch@ietf.org>, sframe@ietf.org, The IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000004413305af535040"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sframe/0ENmuDd4ov81S8wu9XLR0A27sSM>
Subject: Re: [Sframe] =?utf-8?q?=C3=89ric_Vyncke=27s_Block_on_charter-ietf-sf?= =?utf-8?q?rame-00-00?=
X-BeenThere: sframe@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <sframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sframe>, <mailto:sframe-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sframe/>
List-Post: <mailto:sframe@ietf.org>
List-Help: <mailto:sframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sframe>, <mailto:sframe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2020 05:20:46 -0000

Hi Eric,

Did Richard's responses address your concerns? Please let us know if you
have more questions or concerns.

Emad

On Thu, Sep 10, 2020 at 7:28 AM Richard Barnes <rlb@ipv.sx> wrote:

> Hi Éric,
>
> For some reason, your Block didn't get sent to the relevant mailing lists,
> so I'm crafting my own reply :)
>
> - 'Selection among multiple encryption keys' should there be a way to use
>> different encryption algorithm as well with the encapsulation (I noted that
>> this bullet is explicitly for inside a session)?
>>
>
> No.  The assumption is that the algorithm is fixed for a given flow, but
> there may be multiple keys (e.g., for different senders), and of course,
> each encrypted unit needs a different nonce.  We could add some text to
> clarify this if you think it's really necessary, but this seems like a
> finer level of granularity than is needed in a charter.
>
>
>> - like Magnus, I find "Information to form a unique nonce" pretty vague
>> and is it 'nonce' or more 'initialization vector' ?
>>
>
> I've revised to be clear that the encapsulation has a standard nonce
> formation algorithm, and the wire format provides the input to it.  The
> word "nonce" is standard here (see
> https://tools.ietf.org/html/rfc5116#section-2.1)
>
>
>> - 'This working group will not specify the signaling required to
>> configure SFrame encryption", it is unclear to me whether the WG will
>> specify a control channel to negotiate keys and crypto algorithms as the
>> current sentence appears more generic configuration (e.g., supported crypto
>> algorithms)
>>
>
> No, the WG will not specify a control channel.  That is something the
> application will have to provide.
>
>
>> - only one milestone ? There is nothing about the RTP mapping document
>> that is mentioned in the charter text
>>
>
> Yep.  Just one thing, the encapsulation.  The MLS mapping and RTP
> considerations should both be small enough to be sections in that document.
>
> --Richard
>
>
> --
> Sframe mailing list
> Sframe@ietf.org
> https://www.ietf.org/mailman/listinfo/sframe
>