Re: [IPsec] Barry Leiba's No Objection on draft-ietf-ipsecme-qr-ikev2-10: (with COMMENT)

Barry Leiba <barryleiba@computer.org> Wed, 08 January 2020 13:20 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 559931200F4; Wed, 8 Jan 2020 05:20:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Log9DcIA7Q8L; Wed, 8 Jan 2020 05:20:00 -0800 (PST)
Received: from mail-io1-f68.google.com (mail-io1-f68.google.com [209.85.166.68]) (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 3D7481200B7; Wed, 8 Jan 2020 05:20:00 -0800 (PST)
Received: by mail-io1-f68.google.com with SMTP id h8so3178291iob.2; Wed, 08 Jan 2020 05:20:00 -0800 (PST)
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:content-transfer-encoding; bh=blEFC0/XTpdNM0GeYeZe23NlHex2oxO+S53QBmZiEGQ=; b=bhenqxUh7WQPnfbPu0RLA2mY0K0rq6vymY+/jM+Kax1kI6YJty8pDSYShFD2jyxhol EqAXnp27ozHWpGg743tPhzXAQszJmCYAxC207bTps3Xc+Xpcub7VQddCFtqzjaBve1xK 7griVayyNMyah4ApDZRXff+UYkT/5WTTDuCBQRI3vDaYUD7+UU91rJnscrjyXNCG1b74 qyl0gxTTh/CYkxuNpns0Bl8kzRJqCXWLUXPP/iqZM3r2w8OmQ4ZgJ+n4A/pM0Eg1jM24 Lv+mmRFxhuNF2r/EqlE2zz+lTOoiXAf2sF5AQ2v150inRm3sNHHQMy/ZsiDfvV/bwr8h YFlg==
X-Gm-Message-State: APjAAAU66puwdQ04FL9BRq9rUZQmLVWAhDcUExzVG2PWIKx718jFV8Yx 3aKkorJECMUhVx5iaIH0IUokORpj6DcqtD+PVrR4bw==
X-Google-Smtp-Source: APXvYqzxTS2mJEpBTmS7AcgfPu42bH8W+jh3ViPtQGjulmCHRvGfAWUhs7iSDznEConJV95mH+SyHuTSjRPf/JaiPYI=
X-Received: by 2002:a02:4e46:: with SMTP id r67mr4074577jaa.118.1578489599291; Wed, 08 Jan 2020 05:19:59 -0800 (PST)
MIME-Version: 1.0
References: <157846240313.20876.14052335668083715754.idtracker@ietfa.amsl.com> <00bd01d5c607$dfe2ef80$9fa8ce80$@elvis.ru>
In-Reply-To: <00bd01d5c607$dfe2ef80$9fa8ce80$@elvis.ru>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 08 Jan 2020 08:20:01 -0500
Message-ID: <CALaySJ+rzx2CkZSGsS6hwfaJFjV05_pbgKNHtWKjxR7PhCJjAw@mail.gmail.com>
To: Valery Smyslov <svan@elvis.ru>
Cc: The IESG <iesg@ietf.org>, draft-ietf-ipsecme-qr-ikev2@ietf.org, David Waltermire <david.waltermire@nist.gov>, ipsecme-chairs@ietf.org, ipsec@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/klLTCtdetx1HBemew4TfdhaYdgo>
Subject: Re: [IPsec] Barry Leiba's No Objection on draft-ietf-ipsecme-qr-ikev2-10: (with COMMENT)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 13:20:01 -0000

All good, Valery, and thanks for the quick response.

Barry

On Wed, Jan 8, 2020 at 4:42 AM Valery Smyslov <svan@elvis.ru> wrote:
>
> Hi Barry,
>
> > Barry Leiba has entered the following ballot position for
> > draft-ietf-ipsecme-qr-ikev2-10: No Objection
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-ipsecme-qr-ikev2/
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Yes, an interesting document, and thanks for that.  A few editorial
> > comments:
> >
> > — Section 1 —
> >
> >    to be quantum resistant, that is, invulnerable to an attacker with a
> >    quantum computer.
> >
> > “Invulnerable” isn’t the same as “not vulnerable”: it has a stronger
> > connotation.  You should probably use “not vulnerable” or “resistant”
> > instead.
>
> OK, thanks.
>
> >    By bringing post-
> >    quantum security to IKEv2, this note removes the need to use
> >
> > Make it “this document”, please.
>
> OK.
>
> >    This document does not replace the
> >    authentication checks that the protocol does; instead, it is done as
> >    a parallel check.
> >
> > What’s the antecedent to “it”?  Should “it is” instead be “they are”?
>
> I think it was meant that using PPK doesn't directly influence peer authentication
> in IKEv2, but I agree that the wording is not clear enough.
> It's probably better to rephrase it:
>
>     This document does not replace the
>     authentication checks that the protocol does; instead, they are
>     strengthened by using an additional secret key.
>
> Is it better?
>
> > — Section 3 —
> >
> >    when the initiator believes it has a mandatory to use PPK
> >
> > You need hyphens in “mandatory-to-use”.
>
> OK.
>
> THank you,
> Valery.
>
> >
> > —
> >
> > I also find it interesting that Alexey thought you needed to add a normative
> > reference for “ASCII”, bit not for “base64”.  Personally, I think both are
> > sufficiently well known that you need neither.
> >
>
>