IETF Logo Mail Archive

Re: [eppext] revised draft charter - v2

Roger D Carney <rcarney@godaddy.com> Mon, 31 August 2015 11:55 UTC

Return-Path: <rcarney@godaddy.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 B11591B3880 for <eppext@ietfa.amsl.com>; Mon, 31 Aug 2015 04:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 WJv2UPouThOt for <eppext@ietfa.amsl.com>; Mon, 31 Aug 2015 04:55:53 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0108.outbound.protection.outlook.com [65.55.169.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E85B01B3836 for <eppext@ietf.org>; Mon, 31 Aug 2015 04:55:52 -0700 (PDT)
Received: from BN1PR02MB119.namprd02.prod.outlook.com (10.255.204.21) by BN1PR02MB117.namprd02.prod.outlook.com (10.255.204.11) with Microsoft SMTP Server (TLS) id 15.1.256.15; Mon, 31 Aug 2015 11:55:51 +0000
Received: from BN1PR02MB119.namprd02.prod.outlook.com ([169.254.8.83]) by BN1PR02MB119.namprd02.prod.outlook.com ([169.254.8.83]) with mapi id 15.01.0256.013; Mon, 31 Aug 2015 11:55:51 +0000
From: Roger D Carney <rcarney@godaddy.com>
To: eppext <eppext@ietf.org>
Thread-Topic: [eppext] revised draft charter - v2
Thread-Index: AQHQ4dgdv4YVb4+B6U21md3tnVgWKJ4iB1WAgAP5/+A=
Date: Mon, 31 Aug 2015 11:55:50 +0000
Message-ID: <BN1PR02MB11962AE54CE598219AE50CDB16B0@BN1PR02MB119.namprd02.prod.outlook.com>
References: <55E0D247.2020408@elistx.com> <CALaySJL+FjdFgiEF7-+05hwkh22oe6eZhZOKe1P1EirGg=3Rmw@mail.gmail.com>
In-Reply-To: <CALaySJL+FjdFgiEF7-+05hwkh22oe6eZhZOKe1P1EirGg=3Rmw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rcarney@godaddy.com;
x-originating-ip: [71.217.219.133]
x-microsoft-exchange-diagnostics: 1; BN1PR02MB117; 5:tUOww8ErwSILY9ClWPlksW7ZcGoSRL8VpHgwPP7tfQl1zDNuL4izRevj/BUizATeu+H0ETtsfFpHK8gM4c6VPzCKambJbkdJCYWXZZByP13XmAxa5nsVs8fPDgqnrR8ARHOO0D21L9HMZIBr/ngU8g==; 24:3msSQ58EHPcAu1wahWUrM7TcG2mqZKWfLqwIndq8ut6FIoR0Pe5YNkw6Ut+vXjmZsPimWUMLvfVWDWCYk+V8CpdjaEaCZoeeS38KodmFJTQ=; 20:nfxRo5u+6Z2HRBEzyQbjtjAj40FeQM939iWwbQeEliHyLh8/IoFQxtWehov62RhxM4jqnENVqwHPwHKXAnS2+Q==
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(42139001); SRVR:BN1PR02MB117;
x-microsoft-antispam-prvs: <BN1PR02MB1172AC63C1C90270D2D5E9DB16B0@BN1PR02MB117.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(8121501046)(5005006)(3002001); SRVR:BN1PR02MB117; BCL:0; PCL:0; RULEID:; SRVR:BN1PR02MB117;
x-forefront-prvs: 0685122203
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(377454003)(13464003)(199003)(122556002)(2900100001)(99286002)(66066001)(10400500002)(2656002)(106116001)(19580395003)(102836002)(15975445007)(5003600100002)(19580405001)(106356001)(33656002)(40100003)(5007970100001)(68736005)(105586002)(5004730100002)(76576001)(86362001)(189998001)(450100001)(107886002)(62966003)(77156002)(5001860100001)(46102003)(2950100001)(76176999)(74316001)(81156007)(5001960100002)(5001830100001)(4001540100001)(5001920100001)(5002640100001)(50986999)(97736004)(54356999)(64706001)(92566002)(101416001)(87936001)(110136002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR02MB117; H:BN1PR02MB119.namprd02.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: godaddy.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: godaddy.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Aug 2015 11:55:50.7575 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d5f1622b-14a3-45a6-b069-003f8dc4851f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR02MB117
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/Ja8eCegrdMAFd-DwZHkHWl0t6AI>
Subject: Re: [eppext] revised draft charter - v2
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: Mon, 31 Aug 2015 11:55:55 -0000

Thanks Berry, makes sense and sounds great, I like Andy's suggest to include WEIRDS as well as Rik's to include provreg (I think many of us are on multiples of these but it would catch all those that are not).

Jim, I would like to suggest including Reseller, Bundling, and Fees to the milestones, in that order sounds good too.  I assume the Key Relay will be finished under the "old/current" WG/Charter.


Thanks
Roger


 
-----Original Message-----
From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Barry Leiba
Sent: Friday, August 28, 2015 6:02 PM
To: James Galvin
Cc: eppext
Subject: Re: [eppext] revised draft charter - v2

> Marc Blanchet proposed a new name of REGistration protocols EXTensions 
> (REGEXT).  There were no objections so I adopted it in this revised draft.

I think changing the name is a fine thing, but just to alert y'all so it doesn't seem weird when I do it:

Because of the change to the short name (eppext to regext), and the way things are keyed in the datatracker, I will handle this by chartering a new working group with the same chairs, and then close the eppext working group once the regext charter is approved and active.

We can also change the mailing list name at the same time, and leave "eppext" as an alias for it.  That way, everyone will still be subscribed and no one will have to change anything.

Barry

_______________________________________________
EppExt mailing list
EppExt@ietf.org
https://www.ietf.org/mailman/listinfo/eppext

v2.23.0 | Report a Bug | By Email