Re: [IPsec] Spencer Dawkins' No Objection on charter-ietf-ipsecme-11-01: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 01 June 2018 20:01 UTC

Return-Path: <spencerdawkins.ietf@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 BFBD012D94D; Fri, 1 Jun 2018 13:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 Qhkz8PDnFBGO; Fri, 1 Jun 2018 13:01:33 -0700 (PDT)
Received: from mail-yw0-x244.google.com (mail-yw0-x244.google.com [IPv6:2607:f8b0:4002:c05::244]) (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 CBB0612D7F3; Fri, 1 Jun 2018 13:01:32 -0700 (PDT)
Received: by mail-yw0-x244.google.com with SMTP id w13-v6so2306828ywa.5; Fri, 01 Jun 2018 13:01:32 -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=ywr2Apy8qVr+W76P4eyGVnPDGb+ygE6g2WMqlVxe0yg=; b=bJpmZVmMICZHe9ElL3QFJOhAQJ9EEIL0JEjumpCc7OHGHqG+M8u2V1zCJKN+ZVp+sP tXmiwWhgXtKrYlWiNOakmKN6ir7nB6b1iq9y4Hxk/f7XUSw6EbfFxX9Et35iSlcRuNJV usw/S1DlA+op5RlJgB4fi7lvfeUzw+p05LDnsy8DWT8Z9nqSxP5iVLpIhvxXegAl1KUv r3Zp2yUctb/DvephTx1YBVd5+ffQx58bpea8TpCr2M/ab8Z/uyVWjNIg6ig+UvuMP106 2q4ph8eXmSt4iGYsB2RtXQs7W/FqOfLExTKDDf/uJUHbkU/jlqT/rjVy621BmLDBRWbT 8m1g==
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=ywr2Apy8qVr+W76P4eyGVnPDGb+ygE6g2WMqlVxe0yg=; b=M7lJ4VXKaEOiGVDB4DW4WganGhCOprJm5WQ4iJzJrlq540Px+sLL/3GKiie8OpBJe1 sCCalLCictIZlIPWgJpFCKhoeDpiakRzq6Qe0OUlwZSdxWoRYvAT3jvN0dVkCcKMZ1V1 PBhg55m9y9RAaQrJEvR4HIDqK3tvqsPv+I4rDPVSehZjRFQ9gtyLVw8E4xJM8n5WTxeO 0Fx5QHvc8uFYCcLXChxItBOvdWnZyPjYKB5IHgV6tov8oBPUt4sakb9Hv8bYJI3zcmpd CS1YTkGbO5u+vToKT+tkrFjGKNyMtfbULdL3FzjLTr4OaZEOmVYL89YAiJ9fb4O8l1UF Necg==
X-Gm-Message-State: ALKqPwd9QfYXHO8/CY/l81YGizRhBr6Vu723Y7apKTE6dGBkC9M/g1U+ 3Kph02NXtFPYtNCs++qPzIXxN2Bwl3TID3FiNxk=
X-Google-Smtp-Source: ADUXVKJfbQYhtXjaovWc+HN8GEplrXwUHC/AZTFt8YfwC3OrmFnj830IW60/ExWKC1/mCcmCDSYDfI9lVQpW8RnixSY=
X-Received: by 2002:a81:5f84:: with SMTP id t126-v6mr6744694ywb.19.1527883291760; Fri, 01 Jun 2018 13:01:31 -0700 (PDT)
MIME-Version: 1.0
References: <152785983554.14699.4435544739023643415.idtracker@ietfa.amsl.com>
In-Reply-To: <152785983554.14699.4435544739023643415.idtracker@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 01 Jun 2018 15:01:19 -0500
Message-ID: <CAKKJt-fS4ijLTLr8MpywLn0tW1b72NcVNDs-tf_-BH6XEc1Wsg@mail.gmail.com>
To: IESG <iesg@ietf.org>
Cc: IPsecME WG <ipsec@ietf.org>, ipsecme-chairs@tools.ietf.org, ipsecme-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dd1bd6056d9a0c2e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/vFGz9yXI3sVzGiZlGTcAnWNygBc>
Subject: Re: [IPsec] Spencer Dawkins' No Objection on charter-ietf-ipsecme-11-01: (with COMMENT)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 01 Jun 2018 20:01:36 -0000

Thanks, Benjamin, for catching this ...

On Fri, Jun 1, 2018 at 8:30 AM Spencer Dawkins <
spencerdawkins.ietf@gmail.com> wrote:

> Spencer Dawkins has entered the following ballot position for
> charter-ietf-ipsecme-11-01: 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.)
>
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-ipsecme/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I don't object to this proposed charter going for internal review, but do
> have
> one question.
>

I don't object to this proposed charter going for EXTERNAL review, either,
and that's actually what Eric is asking the IESG to ballot on ...

Sorry!

Spencer

When looking at some of the work items, I see
>
> "A possible starting point is draft-yeung-g-ikev2" (nit, missing closing
> period)
>
> "draft-mglt-ipsecme-diet-esp and
> draft-mglt-ipsecme-ikev2-diet-esp-extension
> are expected to be good starting points for ESP compression."
>
> "draft-smyslov-ipsecme-ikev2-compression and
> raft-smyslov-ipsecme-ikev2-compact
> are good starting point for IKEv2 compression." (nit, should be "starting
> points")
>
> "draft-boucadair-ipsecme-ipv6-ipv4-codes could be used as a starting point
> for
> this item."
>
> If you're using different language to convey a nuance, that would be fine
> (I'm
> missing it, but I miss things).
>
> If you're saying the same thing in all four cases, I'd suggest using the
> same
> phrasing in each case. so working group chairs and participants aren't
> trying
> to figure out whether "possible starting point" and "could be used as a
> starting point" are the same as "expected to be good starting points" and
> "are
> good starting points".
>
> I think I see "A possible starting point is" in most charters that point to
> individual drafts, which lets the working group decide whether to adopt
> that
> proposal or work on a different approach, but do the right thing, of
> course.
>
>
>