Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 17 October 2018 03:27 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26889127598 for <mtgvenue@ietfa.amsl.com>; Tue, 16 Oct 2018 20:27:31 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 KEEMxrlFsdUe for <mtgvenue@ietfa.amsl.com>; Tue, 16 Oct 2018 20:27:28 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 4C45B126F72 for <mtgvenue@ietf.org>; Tue, 16 Oct 2018 20:27:28 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id n31-v6so11819852pgm.7 for <mtgvenue@ietf.org>; Tue, 16 Oct 2018 20:27:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=nd/nE6xk5NnnGaQREud000zWP7YjE7AEKLYgjuQguiI=; b=PDw25aXB2aMAo/mZ2avzWTEkOv8n89hdBER8jE8idlDlYcBv2KNFIiWoDwZ2cXUI/v Bnnnh3i52nKw9nY1iMA/wXk6dvA4kyVR3y8P7ovh4A/f4IK0ShLJ9RzdhfKWwhX+jmHu WoLBfsdQOI1e7SlpGBbi91ureGKzc0R8UrdItAf/XiReX2GzZdpMB/wvA+c51Rcip21L ImvMcAD5QLDme/8z2BecEuWiQCjnufWSw8NtUzmKruoyjec448geCPxB/+GrHWGgjr1/ SD5UXigyvDOaZI26gCDoCnuy6Kx34sIh22jHJuHkLRVnV8UCeOueMcJb2+T5PHP/zLQW av7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=nd/nE6xk5NnnGaQREud000zWP7YjE7AEKLYgjuQguiI=; b=bhl9RyYtscDBmFIelDLmJ1MvPh5UMIDGhWPGMrmampR/sfaIE1lzj5gpggxBTqrYDV A66N6a5WO17AxqBXngdelxZ5wi30+CveWASrgF7a9t0oWwGtOPDRydq701pXRjhUh3Sa dxROmcl4kpBKQDHWDGPL0DDx9wjJLVEHmRA5MT3DtxbLFx3/PXFwKfc0QveQnVbr+7vc BtXFm7y9ywScWMAUarL963UOn3bBRCnIxVgwlaAgxTpDaG/sximnckz+pXa5PZpLsozH wkvmBmlcFD98RHFDxYXmOZg5GuKC1JMMraS2nb33ncE52EBlqMlRxXt+G5lIH2ea1/el 6tTg==
X-Gm-Message-State: ABuFfoj6ov3knJ9dgPMKVbtAFe3entUKAQX3fjhZXOHs+P8y9jIHeo7i D+D4Kj8ogbwH7+usHp1ofWM=
X-Google-Smtp-Source: ACcGV61xu6h5P+ZCtrmawrWxaWEBhqB7IB25c/GRJsOX++oPG2E8ipGOIL9zvTonHz7m9tsRYafgYQ==
X-Received: by 2002:a62:d286:: with SMTP id c128-v6mr24798757pfg.14.1539746847783; Tue, 16 Oct 2018 20:27:27 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id a79-v6sm23643292pfa.124.2018.10.16.20.27.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Oct 2018 20:27:26 -0700 (PDT)
To: Bob Hinden <bob.hinden@gmail.com>, Alissa Cooper <alissa@cooperw.in>
Cc: mtgvenue@ietf.org, Lou Berger <lberger@labn.net>, Eliot Lear <lear@cisco.com>
References: <328e9dfe-8e30-6388-68be-95b55af0a5b0@cisco.com> <1667ccb8a70.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <471f7ba9-0b9e-256c-513d-78559ff200a1@cisco.com> <58f9ebdd-355e-129f-a987-dab72bc5da6f@labn.net> <9472f4e7-86bc-121c-ae43-13fcdde451d4@cisco.com> <58B40A28-A847-42A7-99E2-2264FB372189@cooperw.in> <294b058a-8a7f-d3d2-6bb0-563a4b688d7e@labn.net> <A87B2F7F-67D3-416E-B726-A7F4DB41ABCA@cooperw.in> <61264FD0-1AE1-4FDC-B6CF-314BD048B38C@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <9711dba7-e13c-832d-12e7-622c73377aa2@gmail.com>
Date: Wed, 17 Oct 2018 16:27:19 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <61264FD0-1AE1-4FDC-B6CF-314BD048B38C@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/r5lLDm-uU3rdGNhIzs9ACF6ychU>
Subject: Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2018 03:27:31 -0000

Bob,
On 2018-10-17 12:05, Bob Hinden wrote:
> 
>> On Oct 16, 2018, at 3:58 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>>
>>
>>
>>> On Oct 16, 2018, at 9:28 PM, Lou Berger <lberger@labn.net> wrote:
>>>
>>>
>>> Hi Alissa,
>>>
>>> On 10/16/2018 2:38 PM, Alissa Cooper wrote:
>>>> ... I think it’s worth taking the time to sort this out before publication — no rush.
>>>
>>> I have no objection to getting the language right here, but then the document should be returned to the WG to do so.  This change seems well beyond the scope of AUTH48 as evidenced by the discussion - and need to get the language right.
>>
>> That’s why Eliot sent his mail, to have the discussion here now.
>>
> 
> How about if we let this get published soon (it is in AUTH48 now and is correct it today’s world), and then start a BIS that aligns it with IASA 2.0?  Otherwise, it will get held up until the IASA 2.0 work is completed (because I assume it will need a normative reference to the IASA 2 structure document).

Currently the IASA2 structure is tagged as Informational. But I think that's OK, since there doesn't seem to be a good argument for the reference to be normative.

Publishing now with a reference to RFC4071 seems bizarre, since 95% (realistic estimate) of that RFC is obsolete already. I don't see that we lose anything by prolonging AUTH48 until the best way to handle that reference is entirely clear.

   Brian