[eppext] WG Meeting at IETF-95?
"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 02 February 2016 12:33 UTC
Return-Path: <shollenbeck@verisign.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19D1E1A8AAE for <eppext@ietfa.amsl.com>; Tue, 2 Feb 2016 04:33:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 pe4qZxiENuT0 for <eppext@ietfa.amsl.com>; Tue, 2 Feb 2016 04:33:57 -0800 (PST)
Received: from mail-qg0-x261.google.com (mail-qg0-x261.google.com [IPv6:2607:f8b0:400d:c04::261]) (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 C8E9C1A8AAF for <eppext@ietf.org>; Tue, 2 Feb 2016 04:33:56 -0800 (PST)
Received: by mail-qg0-x261.google.com with SMTP id 2so807690qgf.1 for <eppext@ietf.org>; Tue, 02 Feb 2016 04:33:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:importance:date :message-id:accept-language:content-language:content-type :content-transfer-encoding:mime-version; bh=POaDlkYrEzLRoLHJ7+3z9loa+gS10gJByFDXt5XwXhk=; b=AIuMVV3TNWxbPgQj2sgOccV4lISxytdL7wVlQLjU/zVjV2rHhU5esknBkjK5fiWjM2 M5BqoXBrtKC/x9PaC0bbCA2Fr3SAEPLElnludKvUlPBK1AsfW8mPmKJihVYvy/ZtQE0a rc/3FGX79kVI0VHSpPYo0IE8fkkedf9c2ysm0fmat+H00IiswKFt4P3sMR22wenQybG/ 4nFEoocy3t6QrEoW9ilrJkDSjuGXDU6zwM/xEUh1XcDQ/numi3rE2JLXGbjA1CwMCm3X K+2JPdJ9W/HYx8eAoVwilpL3eWJE0BHgc2RojLb7Ogy6Q2I28tbz9TNNzJX6akOzo3/h IUug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index :importance:date:message-id:accept-language:content-language :content-type:content-transfer-encoding:mime-version; bh=POaDlkYrEzLRoLHJ7+3z9loa+gS10gJByFDXt5XwXhk=; b=fuGqQzY29qgOWkliItO7sUJXsEVvvaaXAU7TYI0MRAcu0akbxTtpTVQTK6ePHEex5y uk3mpC05OWBLG8ETtkrLFYguo140x2Ur80k/9PLYbVp0vT/PW2SMv71ADsTdeMZDAGRy vS5fvQsAgnO5WdDvjzEpk6B7UOHHT8i8ng6Y8xSk1eaF3BnWpf7yamnGLsFjBYpxtc5p 8gkHBZJkVn9vlXN+JDxG9t/6jp3JbRbdHe6/YRH8f57kPbLW+7iP7FUEF+k3VNnPzgd0 wsGiFB2jrvrWCIOwoFB/GRIXIWiubAfS0m+ffI1itJXhDNRxf9wYl44s77sPJmW13NUF 2eYQ==
X-Gm-Message-State: AG10YOQFDzeaSuhPk7wZwvBZmO6nL8+BFGD10/PKalJy3ysUO+5vWsje0PYzyVjKfgnwwqmWT9u39dhOsd/1B90ZV52DqxPG
X-Received: by 10.140.251.11 with SMTP id w11mr34919610qhc.7.1454416435558; Tue, 02 Feb 2016 04:33:55 -0800 (PST)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id x75sm141301qkx.7.2016.02.02.04.33.55 for <eppext@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 02 Feb 2016 04:33:55 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id u12CXt8a016835 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <eppext@ietf.org>; Tue, 2 Feb 2016 07:33:55 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 2 Feb 2016 07:33:54 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: WG Meeting at IETF-95?
Thread-Index: AdFdtfnPyF1fw9YKR+WH8rMqAVdV6g==
Importance: high
X-Priority: 1
Date: Tue, 02 Feb 2016 12:33:53 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A14F898@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/JgVqkl5DBbxDE4QAxxa_9NJZh-o>
Subject: [eppext] WG Meeting at IETF-95?
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 12:33:59 -0000
The cut-off for submitting WG meeting requests for IETF-95 is 19 February. The question has been asked more than once with no response - have our chairs submitted a meeting request? Do they intend to? Scott
- [eppext] WG Meeting at IETF-95? Hollenbeck, Scott
- Re: [eppext] WG Meeting at IETF-95? Antoin Verschuren
- Re: [eppext] WG Meeting at IETF-95? Linlin Zhou
- Re: [eppext] WG Meeting at IETF-95? Gould, James
- Re: [eppext] WG Meeting at IETF-95? Gustavo Lozano