From shollenbeck@verisign.com Thu Dec 12 08:28:47 2013 Return-Path: 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 1FB761AE028 for ; Thu, 12 Dec 2013 08:28:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 mIUf1jhwBDs9 for ; Thu, 12 Dec 2013 08:28:42 -0800 (PST) Received: from exprod6og103.obsmtp.com (exprod6og103.obsmtp.com [64.18.1.185]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8931ADDA0 for ; Thu, 12 Dec 2013 08:28:42 -0800 (PST) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob103.postini.com ([64.18.5.12]) with SMTP ID DSNKUqnkNIqKjSAAsHoVl2VWIaQ9lXZRreHh@postini.com; Thu, 12 Dec 2013 08:28:36 PST Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id rBCGSa5I031410 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 12 Dec 2013 11:28:36 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Thu, 12 Dec 2013 11:28:35 -0500 From: "Hollenbeck, Scott" To: "eppext@ietf.org" Thread-Topic: New Working Group! Thread-Index: Ac73VzQoZK07ajh5QV+PZ/t1miB+Xg== Date: Thu, 12 Dec 2013 16:28:35 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493006B5@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 Subject: [Eppext] New Working Group! X-BeenThere: eppext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: EPPEXT List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2013 16:28:47 -0000 It hasn't yet been announced, but it looks like the mailing list has been c= reated for the new eppext working group. I'm looking forward to working wit= h everyone. Scott From iesg-secretary@ietf.org Thu Dec 12 15:24:56 2013 Return-Path: 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 619051AE07D; Thu, 12 Dec 2013 15:24:56 -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] 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 peFLPNbWUgb4; Thu, 12 Dec 2013 15:24:53 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DDE91AE533; Thu, 12 Dec 2013 15:24:52 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131212232452.12561.36027.idtracker@ietfa.amsl.com> Date: Thu, 12 Dec 2013 15:24:52 -0800 X-Mailman-Approved-At: Mon, 16 Dec 2013 10:28:06 -0800 Cc: eppext WG Subject: [Eppext] WG Action: Formed Extensible Provisioning Protocol Extensions (eppext) X-BeenThere: eppext@ietf.org X-Mailman-Version: 2.1.15 List-Id: EPPEXT List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2013 23:24:56 -0000 A new IETF working group has been formed in the Applications Area. For additional information please contact the Area Directors or the WG Chairs. Extensible Provisioning Protocol Extensions (eppext) ------------------------------------------------ Current Status: Proposed WG Chairs: James Galvin Antoin Verschuren Assigned Area Director: Pete Resnick Mailing list Address: eppext@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/eppext Archive: http://www.ietf.org/mail-archive/web/eppext/ 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 From shollenbeck@verisign.com Tue Dec 17 05:55:43 2013 Return-Path: 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 AF4FF1AE1B0 for ; Tue, 17 Dec 2013 05:55:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 xZBV8gOTIQ_g for ; Tue, 17 Dec 2013 05:55:42 -0800 (PST) Received: from exprod6og105.obsmtp.com (exprod6og105.obsmtp.com [64.18.1.189]) by ietfa.amsl.com (Postfix) with ESMTP id F21001AC441 for ; Tue, 17 Dec 2013 05:55:41 -0800 (PST) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob105.postini.com ([64.18.5.12]) with SMTP ID DSNKUrBX3ITUJlOG/6gwws1XfyLeyY+wwVuq@postini.com; Tue, 17 Dec 2013 05:55:41 PST Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id rBHDteTU009893 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 17 Dec 2013 08:55:40 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Tue, 17 Dec 2013 08:55:39 -0500 From: "Hollenbeck, Scott" To: "eppext@ietf.org" Thread-Topic: Document Adoption and Starting Work Thread-Index: Ac77L6qoA2HlczV/ToqTSouukFDEcg== Date: Tue, 17 Dec 2013 13:55:38 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493056ED@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 Subject: [Eppext] Document Adoption and Starting Work X-BeenThere: eppext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: EPPEXT List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 13:55:43 -0000 I'd like to propose that we formally adopt all of the documents described i= n our charter. They are: https://datatracker.ietf.org/doc/draft-hollenbeck-epp-ext-reg/ http://datatracker.ietf.org/doc/draft-gieben-epp-keyrelay/ http://datatracker.ietf.org/doc/draft-obispo-epp-idn/ http://datatracker.ietf.org/doc/draft-tan-epp-launchphase/ https://datatracker.ietf.org/doc/draft-lozano-tmch-smd/ Scott From galvin@elistx.com Wed Dec 18 11:30:33 2013 Return-Path: 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 51DDE1AE146 for ; Wed, 18 Dec 2013 11:30:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.977 X-Spam-Level: X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, USER_IN_WHITELIST=-100] 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 AgkYiMrxoNJ8 for ; Wed, 18 Dec 2013 11:30:31 -0800 (PST) Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com [209.85.213.180]) by ietfa.amsl.com (Postfix) with ESMTP id 8466B1AE078 for ; Wed, 18 Dec 2013 11:30:31 -0800 (PST) Received: by mail-ig0-f180.google.com with SMTP id uq1so1942503igb.1 for ; Wed, 18 Dec 2013 11:30:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=yY7sI2XBgh+omx3vQpGyjCPshUKz8jAv8gePNPv8ab0=; b=O8ojZucS0EMUhfEeZFRSgRrKZWOUhCeyxy69oXeNCgqkpeIx9XICU/mS5BbrMy+RuJ 5T5TwC6vn0QCrbdst2aM2RMuWhjZAwRw9u25+8/+QrViq0OhADgRKEgeHmFuBYT3Hwls Xvw9ooG3pYaGWh3TfNY6B4DHt76iTQ5jvj2HF/AWGdMosniJztILlHMPAJgBW+hzRlvo q49AZk9pZeN1Q70b5FiNUe6A9iDcwgJ0/eNqkrwXyMI1IihxnBU0Hobas7Zfad+X5JzD qG/e4UCJdtv4PKgsz7sP0dpVJT/IRjrJW5fzT2eaEXwp5m20biXpgge73nvsydYRmp22 01JQ== X-Gm-Message-State: ALoCoQlO2M5cTfc250wmYUT305A+ozymDhkUNWc68fOgtQ93kMLNmdWu64C7iMVhGn5ywIA1sRv2 MIME-Version: 1.0 X-Received: by 10.50.40.102 with SMTP id w6mr9828743igk.20.1387395029894; Wed, 18 Dec 2013 11:30:29 -0800 (PST) Received: by 10.64.78.103 with HTTP; Wed, 18 Dec 2013 11:30:29 -0800 (PST) X-Originating-IP: [68.49.97.93] Date: Wed, 18 Dec 2013 14:30:29 -0500 Message-ID: From: James Galvin To: eppext@ietf.org Content-Type: multipart/alternative; boundary=089e0112c7feeba17904edd413e0 Subject: [eppext] almost time to get started X-BeenThere: eppext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: EPPEXT List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 19:30:33 -0000 --089e0112c7feeba17904edd413e0 Content-Type: text/plain; charset=UTF-8 Hello and welcome from your co-Chairs, Antoin and myself. There are now over 40 people subscribed to this mailing list, which hopefully means we have a lot of interest. Given the fast approaching holiday season Antoin and I would like to suggest that this working group not formally get started until after the new year. All that really means is not we are not going to start pressing on moving forward with specific documents. It seems that both Antoin and myself already have vacation time scheduled in our immediate future and our families would like us to honor that. Nonetheless, as Scott has already suggested, our first action will be to accept documents as working group documents. So, if folks want to get started reviewing the documents Scott has listed and commenting both on the whether the documents should be working group documents and the content of the documents, please do! Antoin and I will pickup the discussions and move things along during the first full week of January 2014. Thanks! What a great way to start off our new year! Jim and Antoin --089e0112c7feeba17904edd413e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello and welcome from your co-Chairs,= Antoin and myself.

There are now over 40 people subscribed to this = mailing list, which hopefully means we have a lot of interest.

Given the fast approaching holiday season Antoin and I would like= to suggest that this working group not formally get started until after th= e new year.=C2=A0 All that really means is not we are not going to start pr= essing on moving forward with specific documents.=C2=A0 It seems that both = Antoin and myself already have vacation time scheduled in our immediate fut= ure and our families would like us to honor that.

Nonetheless, as Scott has already suggested, our first action wil= l be to accept documents as working group documents.=C2=A0 So, if folks wan= t to get started reviewing the documents Scott has listed and commenting bo= th on the whether the documents should be working group documents and the c= ontent of the documents, please do!

Antoin and I will pickup the discussions and move things along du= ring the first full week of January 2014.

Thanks!=C2=A0 What a= great way to start off our new year!

Jim and Antoin

--089e0112c7feeba17904edd413e0--