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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Sun, 22 April 2018 09:22 UTC

Return-Path: <eckelcu@cisco.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 6489B1243F3; Sun, 22 Apr 2018 02:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 7Z_kKA04jSny; Sun, 22 Apr 2018 02:22:42 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F6D1120721; Sun, 22 Apr 2018 02:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1856; q=dns/txt; s=iport; t=1524388962; x=1525598562; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=tkrnfDBn1Xg7Ijxrhmh3hT9+LSxWFu6BbjGYECNO7vw=; b=i3zs0X14Kf6Groji3bqYERRiAko9Oy9UqZCoyS2RKvIo5HHEZXZpj2al 2qkncg9pvkapfnwrAEPLaxAuNLkhON5NGrjXVuIIJl0I7Cx1cNcaQvBkk O6IYhW/+SJK/+TGAzqS1PMzEcLrRquMkHcEEgwN6YKgOFwR4XUsjN5h2K w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ATAQCzU9xa/4UNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYNDgVsoCoNgiAKMdoFTIYEPkwCBeAuEawIagishNBgBAgEBAQEBAQJsKIUiAQEBAQMjEUUMBAIBCBEDAQIBAgIfBwICAjAVCAgCBAENBYUPpnOCHIg9gi6BCYZ0D4ITgQ8jDIIuLoRzgwAwgiQCl3MIAo4+jE6QBgIREwGBJAEcOIFScBVlAYIYgkiOBm+PNYEYAQE
X-IronPort-AV: E=Sophos;i="5.49,311,1520899200"; d="scan'208";a="382944466"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Apr 2018 09:22:41 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w3M9MfiA026233 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 22 Apr 2018 09:22:41 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sun, 22 Apr 2018 04:22:41 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1320.000; Sun, 22 Apr 2018 04:22:41 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Adam Roach <adam@nostrum.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
CC: IETF Crazy <ietf@ietf.org>
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
Thread-Topic: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice
Thread-Index: AQHTzRp2yefpiP932UOYj1bLN+GgV6QHttyAgAGB9YCAApOJgIAAFWYAgAAYDgCAAAzBgIAAdJ+A
Date: Sun, 22 Apr 2018 09:22:41 +0000
Message-ID: <115F383E-49E6-4237-849D-E36B26DA977B@cisco.com>
References: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com> <20180419013457.fq4ruqj7p4lfwxb4@mx4.yitter.info> <CABcZeBPXUqe6ixF+Yx7P6E3Jt3fGjAMUrP368DTedGq-O-T61Q@mail.gmail.com> <ED191002-261F-4E3C-A359-CBFEF1812AF8@iii.ca> <531F8285-71D0-4EFD-AC2D-C96DD98E4F44@fugue.com> <23d1e398-887d-4c7c-2c9d-da9fad200415@cs.tcd.ie> <b4a8b4a7-7919-df3f-f301-1cd634f4900c@nostrum.com>
In-Reply-To: <b4a8b4a7-7919-df3f-f301-1cd634f4900c@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.9.0.180116
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.83.239]
Content-Type: text/plain; charset="utf-8"
Content-ID: <61678E2B6D44A04EB6ED6C8C62C69092@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RGqoa6kSOciUHgTm3nx4av-oMz0>
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: Sun, 22 Apr 2018 09:22:44 -0000

-----Original Message-----
From: Mtgvenue <mtgvenue-bounces@ietf.org> on behalf of Adam Roach <adam@nostrum.com>
Date: Saturday, April 21, 2018 at 9:25 PM
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
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

    On 4/21/18 1:39 PM, Stephen Farrell wrote:
    >I don't see evidence sufficient to warrant a change to
    >something else right now. In saying that I regard the
    >1-1-1 scheme as being somewhat aspirational in practice,
    >and that's ok.
    
    
    Agreed, and I think the crux of the conversation underway is whether 
    these guidelines are aspirational or mandatory. The introduction of 
    meeting-policy makes it pretty clear that the document is an attempt to 
    write down the currently-in-use informal policy rather than change it, 
    and I believe that any citation of meeting-policy from venue-selection 
    needs to make the aspirational nature of the 1-1-1-* policy clear 
    (rather than, for example, using normative language, especially at a 
    MUST level).
    
    /a

[cue] I agree with Adam on all points here.

Cheers,
Charles