Re: [provreg] FW: WG Review: Extensible Provisioning Protocol Extensions (eppext)
Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Sat, 23 November 2013 10:59 UTC
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56CC91AE2B6 for <provreg@ietfa.amsl.com>; Sat, 23 Nov 2013 02:59:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level:
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525] 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 bxWm34gp9aZY for <provreg@ietfa.amsl.com>; Sat, 23 Nov 2013 02:59:37 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by ietfa.amsl.com (Postfix) with ESMTP id 19DA11AC862 for <provreg@ietf.org>; Sat, 23 Nov 2013 02:59:36 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.71) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1VkAw0-00079C-Bd; Sat, 23 Nov 2013 11:59:33 +0100
Date: Sat, 23 Nov 2013 11:59:32 +0100
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F492EAD28@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Message-ID: <alpine.DEB.2.00.1311231142380.27081@softronics.hoeneisen.ch>
References: <20131122171808.16557.95825.idtracker@ietfa.amsl.com> <831693C2CDA2E849A7D7A712B24E257F492EAD28@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Cc: "provreg@ietf.org" <provreg@ietf.org>
Subject: Re: [provreg] FW: WG Review: Extensible Provisioning Protocol Extensions (eppext)
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>, <mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg/>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>, <mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Nov 2013 10:59:40 -0000
+1 Looks like a great plan! Glad to see this moving forward! [ Something I was proposing already 7:ish years ago, though with far less traction than now...the proposal appears to have matured a lot over time... ] Thanks Scott et al. for taking care of this! All the best, Bernie -- http://ucom.ch/ Tech Consulting for Internet Technology On Fri, 22 Nov 2013, Hollenbeck, Scott wrote: > Yay! > > Scott > > -----Original Message----- > From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG > Sent: Friday, November 22, 2013 12:18 PM > To: IETF-Announce > Cc: eppext WG > Subject: WG Review: Extensible Provisioning Protocol Extensions (eppext) > > A new IETF working group has been proposed in the Applications Area. The > IESG has not made any determination yet. The following draft charter was > submitted, and is provided for informational purposes only. Please send > your comments to the IESG mailing list (iesg at ietf.org) by 2013-12-02. > > Extensible Provisioning Protocol Extensions (eppext) > ------------------------------------------------ > Current Status: Proposed WG > > Assigned Area Director: > Pete Resnick <presnick@qti.qualcomm.com> > > Charter: > > The Extensible Provisioning Protocol (EPP) was a work product of the IETF > Provisioning Registry Protocol (provreg) working group. EPP was published > as a Proposed Standard (RFCs 3730, 3731, 3732, 3733, and 3734) in March > 2004. It became a Draft Standard (RFCs 4930, 4931, 4932, 4933, and 4934) > in May 2007, and a Standard (Standard 69; RFCs 5730, 5731, 5732, 5733, > and 5734) in August 2009. It is the standard domain name provisioning > protocol for generic top-level domain name registries that operate under > the auspices of the Internet Corporation for Assigned Names and Numbers > (ICANN). It is also used by a number of country code top-level domain > registries. > > Domain name registries implement a variety of business models. The > difference in these models made it very difficult to come up with a "one > size fits all" provisioning protocol, so the provreg working group made a > conscious decision to focus on a minimal set of common functionality. EPP > was designed to be extensible to allow additional features to be > specified on an "as needed" basis. Guidelines for extending EPP were > published as Informational RFC 3735 in March 2004. > > The provreg working group was chartered to develop EPP, but not these > additional extensions. The working group was closed in 2004 after > producing a number of Proposed Standard specifications. As registries > began to implement and deploy EPP the need for extensions became real, > and the user community found itself facing a situation in which multiple > extensions were being developed by different registries to solve the same > basic problems, such as registering additional contact information. > > EPP is widely implemented by generic top-level domain name registry > operators. It is also used by multiple country-code top-level domain name > registry operators. The Internet Corporation for Assigned Names and > Numbers (ICANN) has an active program to delegate a large number of new > generic top-level domains. EPP will be used to provision those domains, > and new registry operators are expected to develop additional protocol > extensions. With no way to coordinate the development of these > extensions, the problem of non-standard extension duplication by multiple > operators is only expected to become worse. > > The goal of the EPP Extensions (eppext) working group is to create an > IANA registry of EPP extensions and to review specifications of > extensions for inclusion in the registry. It will accomplish this goal in > two steps: > > 1. Develop a specification for a registry of and corresponding > registration procedures for EPP extensions. One proposal is documented in > https://datatracker.ietf.org/doc/draft-hollenbeck-epp-ext-reg/. > > 2. Produce a small number of extensions based on existing Internet Draft > documents and use the IANA registration process as developed in 1 to > register those extensions, as follows: > > DNSSEC key relay: draft-gieben-epp-keyrelay > (http://datatracker.ietf.org/doc/draft-gieben-epp-keyrelay/) > > Internationalized domain names: draft-obispo-epp-idn > (http://datatracker.ietf.org/doc/draft-obispo-epp-idn/) > > New TLD launch phases: draft-tan-epp-launchphase > (http://datatracker.ietf.org/doc/draft-tan-epp-launchphase/) > > Trademark Clearinghouse: draft-lozano-tmch-smd > (https://datatracker.ietf.org/doc/draft-lozano-tmch-smd/) > > Note: draft-tan-epp-launchphase has a normative dependency on > draft-lozano-tmch-smd. > > Only the development of the registration process and the > publication/registration of the four extensions noted above are in scope > for the working group. The working group can choose not to publish or > register one or more of the extensions noted above, but it is out of > scope to work on other extensions. > > > Milestones: > May 2014 - Extensions registry document to IESG > Jul 2014 - DNSSEC key relay extension to IESG > Jul 2014 - New TLD launch phases extension to IESG > Sep 2014 - Internationalized domain names extension to IESG > > > _______________________________________________ > provreg mailing list > provreg@ietf.org > https://www.ietf.org/mailman/listinfo/provreg >
- [provreg] FW: WG Review: Extensible Provisioning … Hollenbeck, Scott
- Re: [provreg] WG Review: Extensible Provisioning … Patrik Fältström
- Re: [provreg] FW: WG Review: Extensible Provision… Bernie Hoeneisen
- Re: [provreg] FW: WG Review: Extensible Provision… Jiankang Yao
- Re: [provreg] FW: WG Review: Extensible Provision… Hollenbeck, Scott