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

JORDI PALET MARTINEZ <> Tue, 16 October 2018 11:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AE3BF130DCC for <>; Tue, 16 Oct 2018 04:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
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] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 98cAwu-LFBax for <>; Tue, 16 Oct 2018 04:33:33 -0700 (PDT)
Received: from ( [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C6C62127333 for <>; Tue, 16 Oct 2018 04:33:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple;; s=MDaemon; t=1539689610; x=1540294410;; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=Bv0+zij2de7+OjgfytgG33DLC1391t15pvK1/x22jzM=; b=K3Q6vgn//kyBr mJs3flKpISx0lFC2wAYF03ne5+WDQlvG/aCLLMSQLbzgs9Yl6RkWk8dIDmiuOGqq lV4/Ln3PgVhRxvEKR6m29KGfKyCyWpqgakVtf05mGBEHVQTEDYmo4BCYwgFrtH70 nxWzwFLG50PHmhU2GZW9V1zHYvWcus=
X-MDAV-Result: clean
X-MDAV-Processed:, Tue, 16 Oct 2018 13:33:30 +0200
X-Spam-Processed:, Tue, 16 Oct 2018 13:33:30 +0200
Received: from [] by (MDaemon PRO v16.5.2) with ESMTPA id md50005910892.msg for <>; Tue, 16 Oct 2018 13:33:29 +0200
X-MDRemoteIP: 2001:67c:64:42:e5de:50f3:d3c6:3a59
X-MDHelo: []
X-MDArrival-Date: Tue, 16 Oct 2018 13:33:29 +0200
User-Agent: Microsoft-MacOutlook/
Date: Tue, 16 Oct 2018 13:33:27 +0200
To: Eliot Lear <>, "" <>
CC: Alissa Cooper <>
Message-ID: <>
Thread-Topic: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process
References: <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
Subject: Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 16 Oct 2018 11:33:36 -0000

Hi Eliot, all,

I've reviewed the changes and look good to me.



-----Mensaje original-----
De: Mtgvenue <> en nombre de Eliot Lear <>
Fecha: martes, 16 de octubre de 2018, 13:28
Para: "" <>
CC: Alissa Cooper <>
Asunto: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process

    Dear colleagues,
    The meeting selection document is now with the RFC editor and is in
    AUTH48 state.  Since last call, the IETF LLC has come into existence,
    and the IASA as previously described is no longer relevant.  Therefore,
    some changes are needed to the final draft of the document.  These edits
    largely amount to replacing the IASA with the LLC.  However, I draw your
    attention to  one part of the text that has changed substantially: the
    appeal mechanisms open to  community members have changed.  This is
    primarily due to the nature of the relationship between the
    organizations, and how LLC board members are selected.
    You can find a diff of what was approved by the IESG and what is now
    with  the RFC editor at the following link:
    Barring serious objections, I will give the RFC editor my "Okidoke" for
    this work by the end of the week.
    Mtgvenue mailing list

IPv4 is over
Are you ready for the new Internet ?
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.