Re: [provreg] Proposed Charter for EPP Extensions (eppext) Working Group
Michael Young <michael@mwyoung.ca> Wed, 18 September 2013 12:01 UTC
Return-Path: <michael@mwyoung.ca>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BA5311E8243 for <provreg@ietfa.amsl.com>; Wed, 18 Sep 2013 05:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WeRzlQSx6ZYU for <provreg@ietfa.amsl.com>; Wed, 18 Sep 2013 05:01:47 -0700 (PDT)
Received: from mail-la0-f53.google.com (mail-la0-f53.google.com [209.85.215.53]) by ietfa.amsl.com (Postfix) with ESMTP id 2769311E8253 for <provreg@ietf.org>; Wed, 18 Sep 2013 05:01:41 -0700 (PDT)
Received: by mail-la0-f53.google.com with SMTP id el20so5605046lab.12 for <provreg@ietf.org>; Wed, 18 Sep 2013 05:01:40 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ZjhfBGLDh30j0UB1q0pgM8dkfGKVy8NqbWZHiohNxb8=; b=WeMXa7fduRjyheX3RR5Zo3gLkNouPlm+7r1+bxmgJjgqbGBO1fVoIUX0GSSlCYCYIG RdR0nEDOtDLElfCgb/4sysQc/Qe73qEL7ayYI4cXMQfr+Q+XsgkrLyWS+NSd3cRiOsKj r5ZvDo8FqxwOXt77mcdsYOrHnCxvsPNYZ2XdWIi0fyq4V6NdY+bDHf7+5ronamwrIGXj WcsnuZOE5RW1eJbAMNFVdygD6VsZ4/If79gozgqlJlYvYhPmJ4wrbs9vAx8wuCN7OL6C 8ApAiujRCsMowXfEZ0gHH+4WWIbJ6qPufcWkfzoUXpYF39cWB0QbQD136qEm/CpWrsSa 2I2Q==
X-Gm-Message-State: ALoCoQkJQ5t4zx45WqMPET5IhBM39xhCSIr8kJCazB7VBRC8OYU+SQgUeBNnK6e2D/z52WnPQbty
MIME-Version: 1.0
X-Received: by 10.152.10.99 with SMTP id h3mr35003811lab.13.1379505700149; Wed, 18 Sep 2013 05:01:40 -0700 (PDT)
Received: by 10.114.78.196 with HTTP; Wed, 18 Sep 2013 05:01:40 -0700 (PDT)
Received: by 10.114.78.196 with HTTP; Wed, 18 Sep 2013 05:01:40 -0700 (PDT)
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49266AC2@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <831693C2CDA2E849A7D7A712B24E257F49266AC2@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Date: Wed, 18 Sep 2013 08:01:40 -0400
Message-ID: <CACyVkNhGfrjj5OQQEfZVwomJCfoYqA8qNs9bTmymcOGNa6sbiQ@mail.gmail.com>
From: Michael Young <michael@mwyoung.ca>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Content-Type: multipart/alternative; boundary="001a1132f26a392c5f04e6a733ad"
Cc: provreg@ietf.org
Subject: Re: [provreg] Proposed Charter for EPP Extensions (eppext) Working Group
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 18 Sep 2013 12:01:53 -0000
Scott I'm willing to participate and help write, Michael Young On 2013-09-18 7:21 AM, "Hollenbeck, Scott" <shollenbeck@verisign.com> wrote: > I recently closed a conversation with Applications Area Director Pete > Resnick to see what he thought about a narrowly-focused charter for a > working group to develop a registry for EPP extensions. Pete has agreed > with the concept in principal. I'm including the text of the proposed > charter that I shared with Pete and I'd like to ask others to review it and > share feedback as appropriate. > > If we have enough support for a proposed charter Pete is willing to > entertain a chartering request. If there's more to discuss we can ask about > scheduling a BOF during the Vancouver meeting. > > I've got one specific question: are people able and willing to write a > draft (or drafts) that describe(s) the registry and registration > procedures? I don't think this will be a difficult task because cloning an > existing registry is a perfectly reasonable approach, but someone needs to > do the work. I'm willing to co-chair (if you all will have me) if we form a > working group, and thus it would be best if we find other volunteers to > write documents. > > Scott > ---------- > Proposed Charter for EPP Extensions (eppext) Working Group > > 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 internationalized domain name variants. > > ICANN is now well into a 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 is only expected to become worse. > > The goal of the EPP Extensions (eppext) working group is to develop an > IANA registry of EPP extensions and procedures to review specifications for > inclusion in the registry. It will accomplish this goal in two steps: > > 1. Develop a Proposed Standard specification for the registration and > review of EPP extensions. There is no current Internet Draft that describes > this process. > > 2. Test the extension registration process by developing a small number of > standards track extensions that currently exist in Internet Draft form, > including: > > draft-gieben-epp-keyrelay ( > http://datatracker.ietf.org/doc/draft-gieben-epp-keyrelay/) > > draft-obispo-epp-idn ( > http://datatracker.ietf.org/doc/draft-obispo-epp-idn/) > > draft-tan-epp-launchphase ( > http://datatracker.ietf.org/doc/draft-tan-epp-launchphase/) > draft-lozano-tmch-smd ( > https://datatracker.ietf.org/doc/draft-lozano-tmch-smd/) > draft-tan-epp-launchphase has a normative dependency on > draft-lozano-tmch-smd. > > When these milestones have been completed the working group will consider > rechartering to explore the issue of ongoing extension development and > standardization. Modifications to EPP itself are explicitly out of scope > for this working group. > > Milestones: > > TBD Extensions registry document to IESG > > TBD draft-gieben-epp-keyrelay to IESG > > TBD draft-obispo-epp-idn to IESG > > TBD draft-tan-epp-launchphase and draft-lozano-tmch-smd to IESG > > > _______________________________________________ > provreg mailing list > provreg@ietf.org > https://www.ietf.org/mailman/listinfo/provreg >
- [provreg] Proposed Charter for EPP Extensions (ep… Hollenbeck, Scott
- Re: [provreg] Proposed Charter for EPP Extensions… Michael Young
- Re: [provreg] Proposed Charter for EPP Extensions… Gould, James
- Re: [provreg] Proposed Charter for EPP Extensions… Alexander Mayrhofer
- Re: [provreg] Proposed Charter for EPP Extensions… Luis Muñoz
- Re: [provreg] Proposed Charter for EPP Extensions… Francisco Obispo
- Re: [provreg] Proposed Charter for EPP Extensions… Jothan Frakes
- Re: [provreg] Proposed Charter for EPP Extensions… Dan York
- Re: [provreg] Proposed Charter for EPP Extensions… Jay Daley
- Re: [provreg] Proposed Charter for EPP Extensions… Antoin Verschuren
- Re: [provreg] Proposed Charter for EPP Extensions… Gustavo Lozano
- Re: [provreg] Proposed Charter for EPP Extensions… Jian Chen
- Re: [provreg] Proposed Charter for EPP Extensions… Mike O'Connell
- Re: [provreg] Proposed Charter for EPP Extensions… Jan Saell
- Re: [provreg] Proposed Charter for EPP Extensions… Hollenbeck, Scott
- Re: [provreg] Proposed Charter for EPP Extensions… Peter Koch
- Re: [provreg] Proposed Charter for EPP Extensions… Ning Kong
- Re: [provreg] Proposed Charter for EPP Extensions… Linlin Zhou
- Re: [provreg] Proposed Charter for EPP Extensions… Hollenbeck, Scott
- Re: [provreg] Proposed Charter for EPP Extensions… Hollenbeck, Scott
- Re: [provreg] Proposed Charter for EPP Extensions… Ning Kong
- Re: [provreg] Proposed Charter for EPP Extensions… Hollenbeck, Scott