IETF Logo Mail Archive

Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice

Suresh Krishnan <suresh.krishnan@gmail.com> Wed, 25 April 2018 22:41 UTC

Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9F2812D7F4; Wed, 25 Apr 2018 15:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 PIYJUGAMHldn; Wed, 25 Apr 2018 15:41:31 -0700 (PDT)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (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 00254124207; Wed, 25 Apr 2018 15:41:30 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id o15-v6so54804619wro.11; Wed, 25 Apr 2018 15:41:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=L4fe7zCZg0FE0LgVbG0f8Jg9QD+J3t/WA8WRrC5iU9Y=; b=A2KG6w4pmhz8oYDi4dX8p4kT6vqYSYedKPyrqHAkgjOe4uD8vphNXhQn95vltK8k6s hRR7PGY0p5HQqmzPG8G/eKy79egiCWGVTovBRP9Z8/jS7eBhObujB31au4Bt0cEvJ14f R/6GVp0VNJazNP8wvpPpnwBOZ81EBHs/P/gd1Dx0WzUx7MMxEBi8eLbr62hLoIjod2XD okNlYMmWRLR8Gw0Vn9PYpeZHJJ0NpbUFiH8pYzy4qjP0Urqo/6FDofVgM4jQOWgTXpEC mhJTFp+dOPqfcSPRkiP2UJOT2fj22NCdCIKBplsMl+Wsw1LoE+ddY9fWWGpPcxt1giet hOlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=L4fe7zCZg0FE0LgVbG0f8Jg9QD+J3t/WA8WRrC5iU9Y=; b=QXQ0Rcd6dWfUTLclepyx5djKXvxOA/pCS2pqUg7/Y8X3ukHuqCLOIH7TfHbIvvNlrI fBWUWo/7/peLOwSedM9YNO9c1ry3CkcRCYFKmmmytdfyagW06sY2iLTkJEu1RKmYw8oG Y+t3akUMrXg9biLQKlp9fzFqW9X+QrqAnomSPCy8pod5N+aX59RZH+bPyBH2PhVr70gv WzXYO8xc7mbu67bhPygYfvrWEWbuxEzT9M92b9BeoMUokRrNBSfQp5QUyaVDqYF3UPRG +Ujwx4yrbtG3AuZs15K6MLJf3zI/0LggRtT2tcK+UHQ9LI3TJnPZsmyRITcmuACmjpzF uHGw==
X-Gm-Message-State: ALQs6tDRiPg9AU+x1orHbXuXgy+ieKloXb4vP+7uELtYvPF0rT+WOvSq R4m7a6L+GGZThbcHbxXdeVPKFlgV
X-Google-Smtp-Source: AIpwx48ldSwBO5Gh6PQjLIC4Am+JdaB6Ihab1QaK+LHVA1rRbwL0yGa8kxoT1LG3wb6AE6IoirGdXA==
X-Received: by 2002:adf:b8b0:: with SMTP id i45-v6mr24838339wrf.105.1524696089478; Wed, 25 Apr 2018 15:41:29 -0700 (PDT)
Received: from [10.192.0.149] (132.16.158.77.rev.sfr.net. [77.158.16.132]) by smtp.gmail.com with ESMTPSA id r3sm5244288wmg.5.2018.04.25.15.41.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Apr 2018 15:41:28 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice
From: Suresh Krishnan <suresh.krishnan@gmail.com>
In-Reply-To: <B86A9648-9C63-481D-B4B8-9E981AB0FE73@vigilsec.com>
Date: Thu, 26 Apr 2018 00:41:26 +0200
Cc: IETF <ietf@ietf.org>, mtgvenue@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB05B47C-4B05-4ABD-9C29-0AB2212DECE3@gmail.com>
References: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com> <B86A9648-9C63-481D-B4B8-9E981AB0FE73@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jbtZJNWDPSmueae0EyVD15fLAsQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2018 22:41:33 -0000

Hi Russ,
  Thanks for your comments. Please find responses inline.

> On Apr 17, 2018, at 7:47 PM, Russ Housley <housley@vigilsec.com> wrote:
> 
> Thanks for putting this document together.  I have two minor comments.
> 
> First, in Section 2 the document says:
> 
>   Please note that the boundaries between those regions has been
>   purposefully left undefined per WG consensus.
> 
> As a BCP, I think it would be more valuable to simply say:
> 
>   The boundaries between regions is purposefully left ambiguous.

Sounds good. Will make this change.

> 
> 
> Second, at the end of Section 2, the document says:
> 
>   How often we intend to do such meetings in the future should also be
>   an open topic for discussion within the community.
> 
> I think the document should nail down who makes this decision.  I suggest:
> 
>   The timing and frequency of such exploratory meetings in the future
>   is left to the IETF Chair, after discussion with the IESG and the
>   community.

Sounds good. Does this text work?

"The timing and frequency of such exploratory meetings in the future will be based on IETF consensus as determined by the IETF chair”

Thanks
Suresh

v2.23.0 | Report a Bug | By Email