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

Bob Hinden <bob.hinden@gmail.com> Wed, 17 October 2018 16:26 UTC

Return-Path: <bob.hinden@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 D6F3C130E16 for <mtgvenue@ietfa.amsl.com>; Wed, 17 Oct 2018 09:26:06 -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 FNxHAs3Survl for <mtgvenue@ietfa.amsl.com>; Wed, 17 Oct 2018 09:26:05 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 AF175130DEC for <mtgvenue@ietf.org>; Wed, 17 Oct 2018 09:26:04 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id g15-v6so30394852wru.9 for <mtgvenue@ietf.org>; Wed, 17 Oct 2018 09:26:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=pghnWXbeuwqA0fPInktzKc2kKvrQrJLIWbWnYj4Eiyk=; b=V44XaxQb4BCKvjhdHxjjsIj8pIySWOxIWSDN5SGlVAiNe2rXjbgyu3VDZanYzUDL7K 2kCoNVowJBi01fR73b/exHCDrSaTwUzhaa5OhrMHaqXS4XMj0FoF8EnUDeDAjCtYuUiu vKzOrNyRE0lUAWO8hCWVRWHbCCZ0x7rpgW67fqwlPd7kuF/84QmPjB75U0LeqHgtyihN gD0Kk29JtBl90cTKjDDK1cw26f0o36tYFpQhIqYYFuqwnGrqMzgTc8Jq9xw12tFEJgV2 vXvyX06S6VBF/nVNj26vvxBrUoDNGtKhgmCHtvlhITgUKt7E+HLgwbZiUH3Mud+CsSag PoHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=pghnWXbeuwqA0fPInktzKc2kKvrQrJLIWbWnYj4Eiyk=; b=Bgd2AuUIMM8MjwQEDX9DnxWevjNAkN8ClJRylJTGVp1dt7KsqFUsSmWYKPF4Ms6Hmt y/yIao3BzlqxQopOdIP4guQwN2/CrQmkky4CnCV+JvDlIAoQClqrgJm6Ca7B8d+U5oWl aI9nxE1cwaShdaBMESMdNPtc11HUO1P0QW/u5F1QgBFV6ZDENxYf6hoMADrcNJW+C0zT F41kzGuoqPksVHYJsl/RldlxqXooRB/o8rKCzG6zorpcXYcXKy2WxuB52a7iLzfyPsZa xw3tlY3FbLHXFBPApI1fpWsgnunEIR437VQtZ0czTHT9dLOY/MOCR/brWFx5yNBQewEV I8ag==
X-Gm-Message-State: ABuFfogfE/wtVLGTFsYLimGb5TFHDynNZtIaCTjInN+UM/HuGpDgUaJq A+OslKNGdUxfBg+XS1Utd4U=
X-Google-Smtp-Source: ACcGV614Bw37ATmAKWjbcVjMfUipclNh9LndlJEV0EL4W5RM5IHO4L8AizVRgmpQoVSntf+iiUE93A==
X-Received: by 2002:adf:f4c3:: with SMTP id h3-v6mr23219994wrp.259.1539793563050; Wed, 17 Oct 2018 09:26:03 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:f3a:f837:25cf:f8b9:8bb0? ([2601:647:4d01:f3a:f837:25cf:f8b9:8bb0]) by smtp.gmail.com with ESMTPSA id 91-v6sm3678688wrb.95.2018.10.17.09.26.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Oct 2018 09:26:01 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <DCC5361B-7D11-4FC7-B877-32B3DC9EB09D@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_699315DB-5AAF-4538-A16D-3697469CA75B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 17 Oct 2018 09:25:59 -0700
In-Reply-To: <9711dba7-e13c-832d-12e7-622c73377aa2@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Alissa Cooper <alissa@cooperw.in>, mtgvenue <mtgvenue@ietf.org>, Lou Berger <lberger@labn.net>, Eliot Lear <lear@cisco.com>
To: Brian Carpenter <brian.e.carpenter@gmail.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> <9711dba7-e13c-832d-12e7-622c73377aa2@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/P_bow-q1ZhRfbMx7lx4-6t75TCE>
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 16:26:07 -0000

Brian,

> On Oct 16, 2018, at 8:27 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> 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.

While I am fine either way, seems like the meeting venue draft has been going on for a long time and it would be nice to see it published.

Bob