[eppext] Re-Charter Progress?
"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 06 January 2016 19:24 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 34C821A0146 for <eppext@ietfa.amsl.com>; Wed, 6 Jan 2016 11:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.332
X-Spam-Level:
X-Spam-Status: No, score=-0.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, XPRIO=1.568] autolearn=no
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 h5Lo8kD5K5xI for <eppext@ietfa.amsl.com>; Wed, 6 Jan 2016 11:24:55 -0800 (PST)
Received: from mail-oi0-x261.google.com (mail-oi0-x261.google.com [IPv6:2607:f8b0:4003:c06::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 E2B451A0120 for <eppext@ietf.org>; Wed, 6 Jan 2016 11:24:54 -0800 (PST)
Received: by mail-oi0-x261.google.com with SMTP id o124so40550710oia.3 for <eppext@ietf.org>; Wed, 06 Jan 2016 11:24:54 -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=e6hQHi7zQ1zlrlzrAJB4W0Osxeg90ryqBJFx7MAGvOU=; b=YXVVoJYGa5aERTLdiSr7YjfUlBUss26R8EqqLrxuroHWX6hmoiM+U1Be10LK1ceA1p +7iukLYWQeAwPMw/8HBAGI34dkquUuNfz0zqfdE+7hpL3CLpWJIwLTTh26Fc0W8Aq9DI 76szsoNopEj4FGra/JpNbrp0hn4tJei9wKHkIZGM7s1iTOCkclfBRrQemC0/ztgRpDoO 7PXsI+vrI6yFImBegrtKsXu5Dx1Cr177Vx+dfIHeUd8nYxS6aYgUnuTgtZz6X0BCCOZn haKibyjRzC0ewLHEv0OI04CPtY9ZCuVDmeIdqV2k7vmJVLyNK9CwcPomOJ3zFiI1NKjw f2YQ==
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=e6hQHi7zQ1zlrlzrAJB4W0Osxeg90ryqBJFx7MAGvOU=; b=WcW8s6Dm0yGXxR2pk+jvq86g3ytBkBLTSoakS3xuo4VXetQD3UPadcBmeNnF9/QEJe xzN8iynDGFx00Zy1TWETN8SG8OzSSrYW8v2QVTrc7tcJTCENfjNuqPF797q3tILCWaXr K6txJjy5OGbtF3RYz0CEtynd6zEf8+OFEZzCjm21KX1GXFPAq7QYpftI1aebmIIGpxVY HQvrz5LnKF7Nqy66UEkUmvyXL3mAWw5KWrGr867ZjXwlsGKK4mfRg/XfU5z0HZCEXbEn 2l1LD09JlMMfrSxs+AZ1kiJtWgMYH/xIdbmdNlBBtcEX7YbJ2RgGeDTlJktvy6qoSN3f /YUQ==
X-Gm-Message-State: ALoCoQkRUOA4dNhncVedf0H76gP7WFcAHQEtljc2QbVTQgYGgk6QSDQ0bvUjlij5JD4Y/H3PG+Be+WKA1a5jmZQjjSa8xbR73HU3yaNLFaCKMaavWm5ceH0=
X-Received: by 10.140.27.139 with SMTP id 11mr127802942qgx.62.1452108294228; Wed, 06 Jan 2016 11:24:54 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id v20sm4009580qka.8.2016.01.06.11.24.53 for <eppext@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 06 Jan 2016 11:24:54 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id u06JOrPm002024 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <eppext@ietf.org>; Wed, 6 Jan 2016 14:24:53 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 6 Jan 2016 14:24:53 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: Re-Charter Progress?
Thread-Index: AdFIt+ptGRNgP0ARQpO6wDat4wMc+g==
Importance: high
X-Priority: 1
Date: Wed, 06 Jan 2016 19:24:51 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A126B50@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/toMtvr_rIhwAHEt_Abb3MM7lLME>
Subject: [eppext] Re-Charter Progress?
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: Wed, 06 Jan 2016 19:24:56 -0000
Could our chairs and/or AD please give us an update as to where things stand with our re-chartering effort? Some insight would be helpful as we consider things that we need to talk about at IETF-95 now that the window of opportunity to request meeting slots is open. Scott
- [eppext] Re-Charter Progress? Hollenbeck, Scott
- Re: [eppext] Re-Charter Progress? Ning Kong
- Re: [eppext] Re-Charter Progress? Rik Ribbers
- Re: [eppext] Re-Charter Progress? Hollenbeck, Scott