Re: [eppext] Re-Charter Progress?

"Hollenbeck, Scott" <shollenbeck@verisign.com> Fri, 15 January 2016 11:58 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 853501B2BB0 for <eppext@ietfa.amsl.com>; Fri, 15 Jan 2016 03:58:11 -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 zdwMnqC-Khrj for <eppext@ietfa.amsl.com>; Fri, 15 Jan 2016 03:58:10 -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 281DA1B2BAF for <eppext@ietf.org>; Fri, 15 Jan 2016 03:58:09 -0800 (PST)
Received: by mail-oi0-x261.google.com with SMTP id w75so10554169oie.0 for <eppext@ietf.org>; Fri, 15 Jan 2016 03:58:09 -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:date:message-id :references:in-reply-to:accept-language:content-language :content-type:content-transfer-encoding:mime-version; bh=Gyge9kjEVDS++MI8p82vz3+M6PnV7Cpdd+sGVIKmqf4=; b=mURSYfVCw/oAzCchyvuhvPSAXAFfy9fR+3B2V6/sfAkFMkAB2K3TiFo+l9bXlEX2ri 4qBZOO9Z0CZR/EniTxptIpmrd47UXYeA2YrCGFu7MMfbYZrBknoLRKVB0aMGrl3W1/3i F2q2qQ97QhP+T7VlcYT9Jx3LpAP/LK4xtBgTLrh3sfZDudUAe2rTyR4kNgi1SNS5veNF 1MwP5WIl01wZKnzl4k6zKp5TWZlc2LbGCFAIudnSTI2884FYjxjSxNWyhgc15BqI017+ 2kF9zVDs46RYKw9sKjT3I4o32FzVMsZwbX+q40lSNBu+eGWAd3oAUahY6/9oMT3kMoRV 3Fgw==
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:date :message-id:references:in-reply-to:accept-language:content-language :content-type:content-transfer-encoding:mime-version; bh=Gyge9kjEVDS++MI8p82vz3+M6PnV7Cpdd+sGVIKmqf4=; b=VbIxdhyIR7bm9EDZvfbe6ZBj1gtvWkLOIMlTwyx23EtWT12JOrf/CSZkKtbY/6NY8L c3EHFiqw0T6vTvnHjEkCWE8p9crkZz20gW2o5o/zWn7LAdLxJzmcsSfrYm44+siyac9q ZP6SYRW16BAMGHp83N62BA2CTXsZPGZaipQ9Ot64t8lfQ62CeWIziLUdf6Z2MGDW7GHS NSBMJPNjGmrPNQ8OXWB15E7lZXtfzDM1H1MdRGxTBpYyGv1zLDPULoDfH9DDkPEP9KT+ 0DRLJa9EfOBDPMIau6rBrpCSA86CqE4WWGsFKHGKv/nMbbxVEXQP6QXMaFU0/4gQgttM mAMQ==
X-Gm-Message-State: ALoCoQnq3nRLhgV+H5BnuwkkOn/smCOgOb09qIuPM2FC37G5nUQeXs+bvSjwo1VXQwKkwaWrOzncEuBG/YQUDSqpcGgFzjh4lV3GNjkB0n3UGL8EEYW+yTU=
X-Received: by 10.55.72.146 with SMTP id v140mr12300518qka.63.1452859089288; Fri, 15 Jan 2016 03:58:09 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id y16sm1527795qka.6.2016.01.15.03.58.09 for <eppext@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 15 Jan 2016 03:58:09 -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 u0FBw8L9025992 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <eppext@ietf.org>; Fri, 15 Jan 2016 06:58:08 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 15 Jan 2016 06:58:08 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: Re-Charter Progress?
Thread-Index: AdFIt+ptGRNgP0ARQpO6wDat4wMc+gG057FA
Date: Fri, 15 Jan 2016 11:58:07 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A12DDA2@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <831693C2CDA2E849A7D7A712B24E257F4A126B50@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <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/RGNjucuSUmpTs4LQzKtSdpcqg80>
Subject: Re: [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: Fri, 15 Jan 2016 11:58:11 -0000

> -----Original Message-----
> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Hollenbeck,
> Scott
> Sent: Wednesday, January 06, 2016 2:25 PM
> To: eppext@ietf.org
> Subject: [eppext] Re-Charter Progress?
> Importance: High
> 
> 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.

Could someone in a leadership position please respond? This lack of communication is not acceptable.

Scott