Re: [Mtgvenue] document status, the role of the iaoc, and enforceability

S Moonesamy <sm+ietf@elandsys.com> Sun, 08 January 2017 17:47 UTC

Return-Path: <sm@elandsys.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 129AC1204D9 for <mtgvenue@ietfa.amsl.com>; Sun, 8 Jan 2017 09:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.09
X-Spam-Level:
X-Spam-Status: No, score=-3.09 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=rzrIs8+G; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=Eb2Dge4s
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 BrBSLolkWODF for <mtgvenue@ietfa.amsl.com>; Sun, 8 Jan 2017 09:47:09 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 88C96129553 for <mtgvenue@ietf.org>; Sun, 8 Jan 2017 09:47:09 -0800 (PST)
Received: from SUBMAN.elandsys.com (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v08Hkt1c007106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 Jan 2017 09:47:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1483897622; x=1483984022; bh=LplMnBLjZ/K+JY5cqk97ZdJDqhUKOoGrhm8CKfKGSSc=; h=Date:To:From:Subject:In-Reply-To:References; b=rzrIs8+GeZhXKTqnZf0p2wEQ14/fTVLdazTG2vmPlEx74JL4vreUTK/gss9z85ykp P8ASjG8smxp5iXh/CMUoamQFpDCz6Gil4oYiZQD6sc4eHbhHuPYc/E33I7FP++woc/ lN5sO+GjduPcZn0CI4vJCADIH9ClzGkfN4EIUatU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1483897622; x=1483984022; i=@elandsys.com; bh=LplMnBLjZ/K+JY5cqk97ZdJDqhUKOoGrhm8CKfKGSSc=; h=Date:To:From:Subject:In-Reply-To:References; b=Eb2Dge4sHOeSg90pAbrBfB2VsvvFumm/1O7yqfh8pPL8jlc8B11K5Y11+ZAgGkrNr 7fd7JLWdxyfaeOaezkLHfD/5gCRMOX1Cr1FKHfSA8vtRn7dupbVnA8rLrrvJxRHzBa Osgc3VuJETeUsHUcuv12BmJC0k+llscZLMdLG63Q=
Message-Id: <6.2.5.6.2.20170108090723.0badd8d0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 08 Jan 2017 09:38:33 -0800
To: Eliot Lear <lear@cisco.com>, mtgvenue@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <ac68caa4-a6da-9eb0-d7cb-41ccab444e81@cisco.com>
References: <148302624729.30218.3797301462532090032.idtracker@ietfa.amsl.com> <e2da432a-1ed8-fd51-be59-70213cd932f6@dcrocker.net> <be74a492-a414-1947-91cc-f8eafabd57f8@cisco.com> <31e61662-a92e-dbdc-f918-d91c5694420b@labn.net> <ac68caa4-a6da-9eb0-d7cb-41ccab444e81@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/TJZNjDvS4nvStnKR3uszUQ-Ytak>
Subject: Re: [Mtgvenue] document status, the role of the iaoc, and enforceability
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 08 Jan 2017 17:47:11 -0000

Hi Eliot,
At 10:13 06-01-2017, Eliot Lear wrote:
>Yes, there is this indirection with NOMCOM.  Having a voice is
>important.  I don't really know the composition of the meetings
>committee, but it seems to me that perhaps that is a place for a certain
>amount of diversity so that concerns can be identified early.  Maybe
>it's just me, but when I consider a question like, "should the IETF meet
>in a certain location?" my first question is, would I be comfortable
>with my wife or daughter present?  In other words, I personalize it.  I
>would expect others do something similar, if only subconsciously.  Had

The meeting committee is not responsible to the 
IETF.  The line of responsibility goes to the 
IAOC.  For what it worth, 20% of the IAOC members are appointed by Nomcom.

It is not unusual for a person to think about 
whether he or she would like to go to 
venue.  However, the selection of venue should 
not be a matter of personal preference.  the 
question to ask is whether there be any concerns 
from IETF attendees if that venue is 
selected.  It is not possible for a select group 
of persons to be aware of all the 
concerns.  However, they should have read the 
IETF discussion list and the triannual attendees 
mailing lists to get a sense of which concerns might be raised.

Regards,
S. Moonesamy