From nobody Wed Oct 1 05:30:44 2014 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 0ED441A0296; Wed, 1 Oct 2014 05:30:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9WFwK8xRRAxS; Wed, 1 Oct 2014 05:30:41 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2D61A0340; Wed, 1 Oct 2014 05:30:41 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Adrian Farrel" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141001123041.4367.19913.idtracker@ietfa.amsl.com> Date: Wed, 01 Oct 2014 05:30:41 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/PO1UonEqrg_TMtkIM7zzzM2LsZs Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Adrian Farrel's Discuss on draft-ietf-eppext-reg-08: (with DISCUSS and COMMENT) 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: Wed, 01 Oct 2014 12:30:43 -0000 Adrian Farrel has entered the following ballot position for draft-ietf-eppext-reg-08: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Holding a Discuss for IANA's request of 9/30 > NOTE: Please update the next version to include the revisions > raised in ticket 782732 during Last Call. Please resolve the issues to IANA's satisfaction and update the document as necessary. --- Last time we went through a similar document, the IESG asked me why I was running it as Standards track when Informational seemed to be good enough and there was no description of protocol behavior in the document. Additionally, the IESG seemed to think that this sort of document might usefully be tagged as updating the RFC(s) that define the registries it discusses. Personally, I find it hard to care about this point and I am not asking the author to make any changes. But I would like to take advantage of the IESG telechat to ask the IESG to try to be a little consistent! I will remove this part of the Discuss during the telechat. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The document shows a warning in idnits. == Unused Reference: 'RFC3986' is defined on line 441, but no explicit reference was found in the text From nobody Wed Oct 1 06:53:44 2014 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 AA6D11ACDAB; Wed, 1 Oct 2014 06:53:41 -0700 (PDT) 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 FoSFcD6zX3zx; Wed, 1 Oct 2014 06:53:40 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 402D31A19E6; Wed, 1 Oct 2014 06:53:40 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Barry Leiba" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141001135340.17060.42314.idtracker@ietfa.amsl.com> Date: Wed, 01 Oct 2014 06:53:40 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/c6PmD63llWgSTksoT8qae8BfFFs Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Barry Leiba's No Objection on draft-ietf-eppext-reg-08: (with COMMENT) 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: Wed, 01 Oct 2014 13:53:42 -0000 Barry Leiba has entered the following ballot position for draft-ietf-eppext-reg-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I agree with Adrian that this should be Informational. From nobody Wed Oct 1 07:22:13 2014 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 39F8B1ACDDC; Wed, 1 Oct 2014 07:22:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.787 X-Spam-Level: X-Spam-Status: No, score=-7.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, 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 cXrr2X_OyAiV; Wed, 1 Oct 2014 07:22:05 -0700 (PDT) Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAF8B1ACDD5; Wed, 1 Oct 2014 07:22:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1412173323; x=1443709323; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=XTkIH0aCxruQM0x4g6bmxt2rdCjmC0fG0wtM9HiwLe0=; b=HFOYqdoqLVaP2nTc4W3lVhtQs5tyjzMT4XLM6XGzQ1Rh/MtqmpL5fTY0 tfYLYH714606mMjF7vhCea7zNhuPaHkJmBV/G7r3lbOJ5RXxIe4mPOtSO 6EIsEk7FDEzqOrN7SKJepXfNmEY1mHoyT9Cpm07/c6Gr4XwrRFpLxFpun o=; X-IronPort-AV: E=McAfee;i="5600,1067,7577"; a="75252759" Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 01 Oct 2014 07:22:03 -0700 X-IronPort-AV: E=Sophos;i="5.04,632,1406617200"; d="scan'208";a="31431332" Received: from nasanexhc11.na.qualcomm.com ([172.30.39.6]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 Oct 2014 07:22:02 -0700 Received: from NASANEXM01F.na.qualcomm.com (10.46.201.192) by nasanexhc11.na.qualcomm.com (172.30.39.6) with Microsoft SMTP Server (TLS) id 14.3.181.6; Wed, 1 Oct 2014 07:22:00 -0700 Received: from resnick2.qualcomm.com (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.46.201.192) with Microsoft SMTP Server (TLS) id 15.0.913.22; Wed, 1 Oct 2014 07:22:01 -0700 Message-ID: <542C0E06.7040804@qti.qualcomm.com> Date: Wed, 1 Oct 2014 09:21:58 -0500 From: Pete Resnick User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4 MIME-Version: 1.0 To: Adrian Farrel References: <20141001123041.4367.19913.idtracker@ietfa.amsl.com> In-Reply-To: <20141001123041.4367.19913.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanexm01a.na.qualcomm.com (129.46.53.228) To NASANEXM01F.na.qualcomm.com (10.46.201.192) Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/FBvxbidimT9oX2EvBfb8djqbLPM Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, The IESG , eppext@ietf.org Subject: Re: [eppext] Adrian Farrel's Discuss on draft-ietf-eppext-reg-08: (with DISCUSS and COMMENT) 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, 01 Oct 2014 14:22:07 -0000 On 10/1/14 7:30 AM, Adrian Farrel wrote: > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > Holding a Discuss for IANA's request of 9/30 > > >> NOTE: Please update the next version to include the revisions >> raised in ticket 782732 during Last Call. >> > Please resolve the issues to IANA's satisfaction and update the document > as necessary. > I'm happy to hold that DISCUSS if you like, or make it Revised-ID Needed on that issue. I was simply going to wait until after IESG Evaluation to ask them to produce a new rev of the document. > Last time we went through a similar document, the IESG asked me why I > was running it as Standards track when Informational seemed to be good > enough and there was no description of protocol behavior in the > document. Additionally, the IESG seemed to think that this sort of > document might usefully be tagged as updating the RFC(s) that define > the registries it discusses. > > Personally, I find it hard to care about this point and I am not asking > the author to make any changes. But I would like to take advantage of > the IESG telechat to ask the IESG to try to be a little consistent! I > will remove this part of the Discuss during the telechat. > You will note in the Ballot that I said: The WG put forward this document as Standards Track. However, there is no strong feeling in the WG that this is required, so it is left to the discretion of the IESG to decide whether Informational is more appropriate. It was a complete "Pete-fail" for me not not catch this before Last Call, but I figured I would deal with it when it got to the IESG, which we're allowed to do. But a fine thing to DISCUSS. > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > The document shows a warning in idnits. > > == Unused Reference: 'RFC3986' is defined on line 441, but no explicit > reference was found in the text > Ack. Change in -08 that didn't clean the refs. (*mumble*) pr -- Pete Resnick Qualcomm Technologies, Inc. - +1 (858)651-4478 From nobody Wed Oct 1 07:35:50 2014 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 EFB131ACDE6; Wed, 1 Oct 2014 07:35:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.787 X-Spam-Level: X-Spam-Status: No, score=-7.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, 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 US-zF_AVwugU; Wed, 1 Oct 2014 07:35:46 -0700 (PDT) Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C178F1ACDE5; Wed, 1 Oct 2014 07:35:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1412174146; x=1443710146; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=XCsWI5ohevbxXswJO+8PRrEPACvKETKv5Jv7BKDwt/E=; b=cDMFJDUEbf7Tf2j51j5bunwj1/y1hCZ3bCd3LIEVr9xfu3ei5aoMdJD9 vOEkCNI1sQB12pIIbx8utV6Li30mQ9H0CTa134YWaMyYe+oYnCGMFivx+ Dh9rk2vvw+RAN1T9vxpbfEEjEPna4djf0EecYjOLOzNQyU3bkmDlGCld7 g=; X-IronPort-AV: E=McAfee;i="5600,1067,7577"; a="75880249" Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth02.qualcomm.com with ESMTP; 01 Oct 2014 07:35:46 -0700 X-IronPort-AV: E=Sophos;i="5.04,632,1406617200"; d="scan'208";a="31431416" Received: from nasanexhc15.na.qualcomm.com ([129.46.52.215]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 Oct 2014 07:35:46 -0700 Received: from NASANEXM01F.na.qualcomm.com (10.46.201.192) by nasanexhc15.na.qualcomm.com (129.46.52.215) with Microsoft SMTP Server (TLS) id 14.3.181.6; Wed, 1 Oct 2014 07:35:46 -0700 Received: from resnick2.qualcomm.com (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.46.201.192) with Microsoft SMTP Server (TLS) id 15.0.913.22; Wed, 1 Oct 2014 07:35:45 -0700 Message-ID: <542C112D.2050008@qti.qualcomm.com> Date: Wed, 1 Oct 2014 09:35:25 -0500 From: Pete Resnick User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4 MIME-Version: 1.0 To: Kathleen Moriarty References: <20141001142835.21061.50467.idtracker@ietfa.amsl.com> In-Reply-To: <20141001142835.21061.50467.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanexm01a.na.qualcomm.com (129.46.53.228) To NASANEXM01F.na.qualcomm.com (10.46.201.192) Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/C3AJ_m7cK3HDbU5c4Y2RRNP8ncA Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, The IESG , eppext@ietf.org Subject: Re: [eppext] Kathleen Moriarty's No Objection on draft-ietf-eppext-reg-08: (with COMMENT) 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, 01 Oct 2014 14:35:48 -0000 On 10/1/14 9:28 AM, Kathleen Moriarty wrote: > This is just a comment as I don't have any issues with the security > considerations, just a question. Aren't the security considerations > addressed by the expert review required? The registry won't just get > amended as a result of an email request. The rest of the process should > help. > Agreed. The SecDir pointed this out too. I'll ask the WG to update the document to use the SecDir suggested text. pr -- Pete Resnick Qualcomm Technologies, Inc. - +1 (858)651-4478 From nobody Wed Oct 1 07:57:22 2014 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 ABA271ACE2A; Wed, 1 Oct 2014 07:57:12 -0700 (PDT) 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 IOLC93zLngLQ; Wed, 1 Oct 2014 07:57:11 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E39F1A1A05; Wed, 1 Oct 2014 07:57:11 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Pete Resnick" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141001145711.11931.49820.idtracker@ietfa.amsl.com> Date: Wed, 01 Oct 2014 07:57:11 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/lhlWxTuAeywOAIpU7KIY-o682G8 Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Pete Resnick's Discuss on draft-ietf-eppext-reg-08: (with DISCUSS) 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: Wed, 01 Oct 2014 14:57:12 -0000 Pete Resnick has entered the following ballot position for draft-ietf-eppext-reg-08: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Holding a Discuss for IANA's request of 9/30 > NOTE: Please update the next version to include the revisions > raised in ticket 782732 during Last Call. From nobody Wed Oct 1 08:03:05 2014 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 0D0D61ACE44; Wed, 1 Oct 2014 08:03:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Xk1e72PqUyMV; Wed, 1 Oct 2014 08:02:59 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA0D1ACE48; Wed, 1 Oct 2014 08:02:47 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Adrian Farrel" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141001150247.9614.50990.idtracker@ietfa.amsl.com> Date: Wed, 01 Oct 2014 08:02:47 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/8CF9tuifGlZAGAlH2OdtbsdlFLc Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Adrian Farrel's Discuss on draft-ietf-eppext-reg-08: (with DISCUSS and COMMENT) 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: Wed, 01 Oct 2014 15:03:01 -0000 Adrian Farrel has entered the following ballot position for draft-ietf-eppext-reg-08: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- [Cleared the bit about IANA as Pete now has it in his Discuss] Last time we went through a similar document, the IESG asked me why I was running it as Standards track when Informational seemed to be good enough and there was no description of protocol behavior in the document. Additionally, the IESG seemed to think that this sort of document might usefully be tagged as updating the RFC(s) that define the registries it discusses. Personally, I find it hard to care about this point and I am not asking the author to make any changes. But I would like to take advantage of the IESG telechat to ask the IESG to try to be a little consistent! I will remove this part of the Discuss during the telechat. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The document shows a warning in idnits. == Unused Reference: 'RFC3986' is defined on line 441, but no explicit reference was found in the text From nobody Wed Oct 1 14:04:07 2014 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 3FC711ACE01; Wed, 1 Oct 2014 07:42:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=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 scgViUsZcULP; Wed, 1 Oct 2014 07:41:58 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DCFD11ACE14; Wed, 1 Oct 2014 07:41:58 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Kathleen Moriarty" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141001144158.17791.58903.idtracker@ietfa.amsl.com> Date: Wed, 01 Oct 2014 07:41:58 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/fsgYoj2FYSHw-EZ2a8T2vDbiCSY X-Mailman-Approved-At: Wed, 01 Oct 2014 14:04:05 -0700 Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Kathleen Moriarty's No Objection on draft-ietf-eppext-reg-08: (with COMMENT) 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: Wed, 01 Oct 2014 14:42:00 -0000 Kathleen Moriarty has entered the following ballot position for draft-ietf-eppext-reg-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This is just a comment as I don't have any issues with the security considerations, just a question. Aren't the security considerations addressed by the expert review required? The registry won't just get amended as a result of an email request. The rest of the process should help. Please respond to the SecDir review and suggestions as well, thanks: https://www.ietf.org/mail-archive/web/secdir/current/msg05091.html Yoav had a similar comment, so how about the following text for the Security Considerations section: "Security Considerations This document introduces no new security considerations to EPP. However, extensions should be evaluated according to the Security Considerations of RFC 3735." Thanks. From nobody Wed Oct 1 14:04:09 2014 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 2E0A01ACE17; Wed, 1 Oct 2014 07:56:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 8ojR2klOVHc8; Wed, 1 Oct 2014 07:56:39 -0700 (PDT) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94A4D1ACE1C; Wed, 1 Oct 2014 07:56:38 -0700 (PDT) Received: by mail-la0-f42.google.com with SMTP id mk6so519747lab.29 for ; Wed, 01 Oct 2014 07:56:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yjSE4P3j7pe4FVcJXk0yS89yIGEsPH2jtVzew1sj8Jc=; b=Cu4ElQKirjn58MR35Hu4C+LgB2J1CIY21Xf/siNU9lI7Rr0npsSqJIFqaxn0k+HKXM rYoE/ZCx/y1IzPIcKeoV42fPeJZ0EoChriVQIy5cT94lEokcsk4FWV9ET5FlYrBZWBJQ 5eDxRURJLKS9aaYqpbiF3+x15A7s8xhfLKYp1E6onGmiTXqWU3VCRiF4ZA+EPiGrYRsz yp8Si02T51PQOYY+orn4JQ2//nNq5Pp4/rPhRek1oM90Yeak04EWV4aL/ppM4IO361Vj +n/fp88WGWN6JimcTUxV1MdSN/b3vPv2iBE98Vc0RyLClRv/bRqKqCdHjx6qZD2FyRru gvNQ== MIME-Version: 1.0 X-Received: by 10.112.130.129 with SMTP id oe1mr52165877lbb.4.1412175396821; Wed, 01 Oct 2014 07:56:36 -0700 (PDT) Received: by 10.112.95.36 with HTTP; Wed, 1 Oct 2014 07:56:36 -0700 (PDT) In-Reply-To: <542C112D.2050008@qti.qualcomm.com> References: <20141001142835.21061.50467.idtracker@ietfa.amsl.com> <542C112D.2050008@qti.qualcomm.com> Date: Wed, 1 Oct 2014 10:56:36 -0400 Message-ID: From: Kathleen Moriarty To: Pete Resnick Content-Type: multipart/alternative; boundary=e89a8f64732fe3604e05045db479 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/1LgLU5fgCf3m4f7gt7VwO1t2Yd8 X-Mailman-Approved-At: Wed, 01 Oct 2014 14:04:06 -0700 Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, The IESG , eppext@ietf.org Subject: Re: [eppext] Kathleen Moriarty's No Objection on draft-ietf-eppext-reg-08: (with COMMENT) 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, 01 Oct 2014 14:56:41 -0000 --e89a8f64732fe3604e05045db479 Content-Type: text/plain; charset=UTF-8 Thanks, Pete! On Wed, Oct 1, 2014 at 10:35 AM, Pete Resnick wrote: > On 10/1/14 9:28 AM, Kathleen Moriarty wrote: > >> This is just a comment as I don't have any issues with the security >> considerations, just a question. Aren't the security considerations >> addressed by the expert review required? The registry won't just get >> amended as a result of an email request. The rest of the process should >> help. >> >> > > Agreed. The SecDir pointed this out too. I'll ask the WG to update the > document to use the SecDir suggested text. > > pr > > -- > Pete Resnick > Qualcomm Technologies, Inc. - +1 (858)651-4478 > > -- Best regards, Kathleen --e89a8f64732fe3604e05045db479 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks, Pete!

On Wed, Oct 1, 2014 at 10:35 AM, Pete Resnick <presnick@qti.qualcomm.com> wrote:
On 10/1/14 9:28 AM, Kathleen Moriarty wrote:
This is just a comment as I don't have any issues with the security
considerations, just a question.=C2=A0 Aren't the security consideratio= ns
addressed by the expert review required?=C2=A0 The registry won't just = get
amended as a result of an email request.=C2=A0 The rest of the process shou= ld
help.
=C2=A0 =C2=A0

 Agreed. The SecDir pointed this out too. I'll ask the WG to update the = document to use the SecDir suggested text.

pr

--
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478




--

Best regards,
Kathleen
--e89a8f64732fe3604e05045db479-- From nobody Wed Oct 1 22:55:53 2014 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 8F97D1A00C5; Wed, 1 Oct 2014 22:55:51 -0700 (PDT) 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 7_MfZStsF211; Wed, 1 Oct 2014 22:55:50 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 60E981A008D; Wed, 1 Oct 2014 22:55:50 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Joel Jaeggli" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141002055550.24383.47984.idtracker@ietfa.amsl.com> Date: Wed, 01 Oct 2014 22:55:50 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/4KBzoLPhER9Y7L1YfHEn3YcPLjk Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Joel Jaeggli's No Objection on draft-ietf-eppext-reg-08: (with COMMENT) 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, 02 Oct 2014 05:55:51 -0000 Joel Jaeggli has entered the following ballot position for draft-ietf-eppext-reg-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- the security considerations section doesn't have anything to do with the protocol or the registry, nor is it instruction to iana, if it was it would be in the iana considerations section. From nobody Thu Oct 2 02:14:02 2014 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 5E3521A0235; Thu, 2 Oct 2014 02:14:00 -0700 (PDT) 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 UQgCe8bjpfF9; Thu, 2 Oct 2014 02:13:58 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A31751A01F7; Thu, 2 Oct 2014 02:13:58 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "Benoit Claise" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141002091358.1421.8098.idtracker@ietfa.amsl.com> Date: Thu, 02 Oct 2014 02:13:58 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/1SM5D3Uk6OnawM-65sko-aD_a-Y Cc: draft-ietf-eppext-reg@tools.ietf.org, suzworldwide@gmail.com, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Benoit Claise's No Objection on draft-ietf-eppext-reg-08: (with COMMENT) 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, 02 Oct 2014 09:14:00 -0000 Benoit Claise has entered the following ballot position for draft-ietf-eppext-reg-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Please see Suzanne's OPS-DIR review below: Per the usual warning, “I have reviewed this document as part of the Operational directorate’s ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the operational area directors. Document editors and WG chairs should treat these comments just like any other last call comments.” Summary: ready with a couple of minor concerns This document doesn’t document new protocol, instead it attempts to close a gap in the existing EPP protocol, specifically its provisions for extensions, to improve interoperability. The mechanism discussed is an IANA registry for documenting EPP extensions, with expert review (“Specification Required”) as the gate. The support for interoperability provided seems good. The process does not provide directly for review of extensions that may be similar in their effects or for any attempt to harmonize similar or conflicting extensions, but (per the Shepherd’s writeup) it was judged preferable to keep the process relatively lightweight so people would choose to document their extensions rather than simply choosing not to bother. This is a reasonable accommodation to the real world, in which EPP was written to be easily extensible in support of a range of operational and business models, often by entities who are not primarily software or networking players and wouldn’t necessarily be willing to execute a painful or costly process for registering EPP extensions that may not even be intended for wide use. The Shepherd’s writeup covered the questions I would have regarding guidelines to the Expert. As an editorial nit, Sec. 2.2.3 and 2.2.4 both move between second person (instructions to the submitter of a proposed registry entry) and third person description of the process. I also have some confusion about one of the fields in the proposed registry. It’s not clear to me exactly what purpose is served by the “Active”/“Inactive” flag: The definition of “active”/“inactive” in 2.2.1: Status: Either "Active" or "Inactive". The "Active" status is used for extensions that are currently implemented and available for use. The "Inactive" status is used for extensions that are not implemented or are otherwise not available for use. doesn’t seem fully consistent with the text in 2.2.4: Entries can change state from "Active" to "Inactive" and back again as long as state change requests conform to the processing requirements identified in this document. Entries for which a specification becomes consistently unavailable over time should be marked "Inactive" by the designated expert until such time as the specification again becomes reliably available. This seems to assume that “availability of the specification” is closely related to whether the extension is “available for use,” but I’m not sure either term is sufficiently clear as an instruction to IANA, the Expert, or potential registrants for entries in the registry. However, there may be an understanding in place between IANA and the IESG on how to manage “availability of the specification” as a factor in “Specification Required” registries. If this is clear to IANA and to the WG (which I know includes potential experts) as sufficient guidance, I suggest clarifying it if possible in the document. If not, I would wonder if the field needs to be more clearly defined, or is simply not necessary. The question above is, however, a very minor point in the big picture, which is that we’re trying to get people to document their EPP extensions and this document gives them a relatively lightweight but useful way to do so. The Shepherd’s writeup raises the question of whether this document should be Standards Track or Informational. I tend to think that a document establishing an IANA registry, with a registration policy that isn’t simply FCFS, be Standards Track, but as this one doesn’t involve assignment of unique codepoints out of a number space— just text strings—that detail doesn’t seem critical. From nobody Thu Oct 2 06:26:01 2014 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 C56901A86FA; Thu, 2 Oct 2014 06:25:57 -0700 (PDT) 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 vzAePh3gRo29; Thu, 2 Oct 2014 06:25:56 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9F11A870B; Thu, 2 Oct 2014 06:25:56 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Stephen Farrell" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141002132556.9818.26252.idtracker@ietfa.amsl.com> Date: Thu, 02 Oct 2014 06:25:56 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/RtJOLf3oD2iAAagkJbAhHeCC0is Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Stephen Farrell's Discuss on draft-ietf-eppext-reg-08: (with DISCUSS) 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, 02 Oct 2014 13:25:57 -0000 Stephen Farrell has entered the following ballot position for draft-ietf-eppext-reg-08: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I believe that there are some uses of EPP that have been mooted or even put in place that are considerd by quite a few folks as being quite privacy unfriendly. If so (and please correct me if I'm wrong) that indicates that the DEs need to explicitly include consideration of the privacy consequences of proposed extensions and that DEs ought at minimum require that any privacy considerations are fully documented in the relevant specification(s). If it were up to me, I'd probably go further on that and ask that the DEs try to ensure that the world is more privacy friendly, but I suspect that'd be beyond IETF consensus. From nobody Thu Oct 2 07:06:37 2014 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 4F8E21A033D; Thu, 2 Oct 2014 07:06:34 -0700 (PDT) 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 bB5xMyRzCJZX; Thu, 2 Oct 2014 07:06:27 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 91A281A03A0; Thu, 2 Oct 2014 07:06:27 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Ted Lemon" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141002140627.8415.84519.idtracker@ietfa.amsl.com> Date: Thu, 02 Oct 2014 07:06:27 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/ialjz4LCXXd8gG1DSuxfrKcpYJw Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Ted Lemon's No Objection on draft-ietf-eppext-reg-08: (with COMMENT) 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, 02 Oct 2014 14:06:34 -0000 Ted Lemon has entered the following ballot position for draft-ietf-eppext-reg-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This seems wrong: Using email to deliver forms to IANA carries a risk of registry entries being created or updated by an attacker who is able to spoof the email address of a legitimate extension registrant. This risk can be mitigated by replying to received messages with a request to confirm the requested action. The reply will be delivered to the specified registrant, who can validate or refute the request. If you have a man-in-the-middle, they can presumably modify messages in both directions. But as Kathleen said, the normal process of review should catch problems of this sort. If that fails, and an erroneous registration occurs, the registrant will see the incorrect IANA registry entry. So this will serve as an out-of-band mechanism for detecting attacks of this type, since the MITM presumably won't be able to spoof the SSL cert from the IANA web site. From nobody Thu Oct 2 09:28:31 2014 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 543871A882A; Thu, 2 Oct 2014 09:28:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 BNDRWGZgSSZn; Thu, 2 Oct 2014 09:28:26 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 266771A1A43; Thu, 2 Oct 2014 09:28:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Adrian Farrel" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141002162826.6766.71925.idtracker@ietfa.amsl.com> Date: Thu, 02 Oct 2014 09:28:26 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/ArpSS3ZU97eC8DPTrkNp5FLfvnA Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Adrian Farrel's No Objection on draft-ietf-eppext-reg-08: (with COMMENT) 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, 02 Oct 2014 16:28:27 -0000 Adrian Farrel has entered the following ballot position for draft-ietf-eppext-reg-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The document shows a warning in idnits. == Unused Reference: 'RFC3986' is defined on line 441, but no explicit reference was found in the text --- I cleared my Discuss. Pete indicated that this will be progressed as Informational From nobody Thu Oct 2 10:45:10 2014 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 803B21A8F4E for ; Thu, 2 Oct 2014 10:45:07 -0700 (PDT) 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 qqNWewPpMprw; Thu, 2 Oct 2014 10:45:06 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7AF1A8A16; Thu, 2 Oct 2014 10:45:06 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: eppext-chairs@tools.ietf.org, draft-ietf-eppext-reg@tools.ietf.org, eppext@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141002174506.15103.47572.idtracker@ietfa.amsl.com> Date: Thu, 02 Oct 2014 10:45:06 -0700 From: IETF Secretariat Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/oIdUaTlI50zof6khUBkDZ8yKCOo Subject: [eppext] ID Tracker State Update Notice: 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, 02 Oct 2014 17:45:07 -0000 IESG state changed to IESG Evaluation::Revised I-D Needed from IESG Evaluation ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ From nobody Thu Oct 2 11:16:56 2014 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 0A2E31A9135 for ; Thu, 2 Oct 2014 11:16:55 -0700 (PDT) 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 K9F_cwVwdLTM for ; Thu, 2 Oct 2014 11:16:53 -0700 (PDT) Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2CAD1A9124 for ; Thu, 2 Oct 2014 11:16:51 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKVC2Wk3TnfCue6A7MsyZIGlJ+OLhiWBqt@postini.com; Thu, 02 Oct 2014 11:16:53 PDT Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s92IGoKx002166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Oct 2014 14:16:50 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 2 Oct 2014 14:16:50 -0400 From: "Hollenbeck, Scott" To: Pete Resnick Thread-Topic: [eppext] ID Tracker State Update Notice: Thread-Index: AQHP3mieqwKRIYGVIEmPu8wndVKhpZwdGtxA Date: Thu, 2 Oct 2014 18:16:49 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F494D6A5D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20141002174506.15103.47572.idtracker@ietfa.amsl.com> In-Reply-To: <20141002174506.15103.47572.idtracker@ietfa.amsl.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/9gfe3mPEWKCz65Ghj1bA-YybYGc Cc: "eppext-chairs@tools.ietf.org" , "eppext@ietf.org" Subject: Re: [eppext] ID Tracker State Update Notice: 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, 02 Oct 2014 18:16:55 -0000 Thanks for moving the document along, Pete. I'll dig through the comments a= nd see about an approach for each one. What, if anything, do you suggest for the comments about the security consi= derations section? I've got the comment about including the considerations = from 3735, but what about this comments from Joel Jaeggli and Ted Lemon? Jo= el's: "the security considerations section doesn't have anything to do with the protocol or the registry, nor is it instruction to iana, if it was it would be in the iana considerations section." Ted's: " This seems wrong: Using email to deliver forms to IANA carries a risk of registry entries being created or updated by an attacker who is able to spoof the email address of a legitimate extension registrant. This risk can be mitigated by replying to received messages with a request to confirm the requested action. The reply will be delivered to the specified registrant, who can validate or refute the request. If you have a man-in-the-middle, they can presumably modify messages in both directions. But as Kathleen said, the normal process of review should catch problems of this sort. If that fails, and an erroneous registration occurs, the registrant will see the incorrect IANA registry entry. So this will serve as an out-of-band mechanism for detecting attacks of this type, since the MITM presumably won't be able to spoof the SSL cert from the IANA web site." ...or Stephen Farrel's discuss: "I believe that there are some uses of EPP that have been mooted or even put in place that are considerd by quite a few folks as being quite privacy unfriendly. If so (and please correct me if I'm wrong) that indicates that the DEs need to explicitly include consideration of the privacy consequences of proposed extensions and that DEs ought at minimum require that any privacy considerations are fully documented in the relevant specification(s). If it were up to me, I'd probably go further on that and ask that the DEs try to ensure that the world is more privacy friendly, but I suspect that'd be beyond IETF consensus." Scott=20 From nobody Fri Oct 3 05:17:42 2014 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 45DBA1A0350 for ; Fri, 3 Oct 2014 05:17:40 -0700 (PDT) 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 kIXod_sIRxKJ for ; Fri, 3 Oct 2014 05:17:37 -0700 (PDT) Received: from exprod6og115.obsmtp.com (exprod6og115.obsmtp.com [64.18.1.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19D041A034D for ; Fri, 3 Oct 2014 05:17:33 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob115.postini.com ([64.18.5.12]) with SMTP ID DSNKVC6T3ZwP+Wm8p3fMqkA22TH1YN8eWF/n@postini.com; Fri, 03 Oct 2014 05:17:36 PDT 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 s93CHWCB001150 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Oct 2014 08:17:32 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 3 Oct 2014 08:17:31 -0400 From: "Hollenbeck, Scott" To: Pete Resnick Thread-Topic: [eppext] ID Tracker State Update Notice: Thread-Index: AQHP3m0OmZ1afrMNtUKDJuoaBUvydJweSjUQ Date: Fri, 3 Oct 2014 12:17:31 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F494D73E8@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20141002174506.15103.47572.idtracker@ietfa.amsl.com> <831693C2CDA2E849A7D7A712B24E257F494D6A5D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F494D6A5D@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/3GSNbCHO_6q5AbYNu43U_StF0Kc Cc: "eppext-chairs@tools.ietf.org" , "eppext@ietf.org" Subject: Re: [eppext] ID Tracker State Update Notice: 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: Fri, 03 Oct 2014 12:17:40 -0000 I just finished an update that addresses (I think) all of the last call and= IESG review comments. I added Stephen Farrel's text to the DE evaluation c= riteria section to make it clear that privacy considerations should be incl= uded in the evaluation. I modified the Security Considerations section as f= ollows: "4. Security Considerations Using email to deliver forms to IANA carries a risk of registry entries being created or updated by an attacker who is able to spoof the email address of a legitimate extension registrant. This risk can be mitigated by replying to received messages with a request to confirm the requested action. The reply will be delivered to the specified registrant, who can validate or refute the request. This document introduces no new security considerations to EPP. However, extensions should be evaluated according to the Security Considerations of RFC 3735 [RFC3735]." I'm going to publish the update in a minute so you can see the rest of the = changes using a diff. Scott > -----Original Message----- > From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Hollenbeck, > Scott > Sent: Thursday, October 02, 2014 2:17 PM > To: Pete Resnick > Cc: eppext-chairs@tools.ietf.org; eppext@ietf.org > Subject: Re: [eppext] ID Tracker State Update Notice: eppext-reg-08.txt> >=20 > Thanks for moving the document along, Pete. I'll dig through the > comments and see about an approach for each one. >=20 > What, if anything, do you suggest for the comments about the security > considerations section? I've got the comment about including the > considerations from 3735, but what about this comments from Joel > Jaeggli and Ted Lemon? Joel's: >=20 > "the security considerations section doesn't have anything to do with > the > protocol or the registry, nor is it instruction to iana, if it was it > would be in the iana considerations section." >=20 > Ted's: >=20 > " This seems wrong: >=20 > Using email to deliver forms to IANA carries a risk of registry > entries being created or updated by an attacker who is able to spoof > the email address of a legitimate extension registrant. This risk > can be mitigated by replying to received messages with a request to > confirm the requested action. The reply will be delivered to the > specified registrant, who can validate or refute the request. >=20 > If you have a man-in-the-middle, they can presumably modify messages in > both directions. But as Kathleen said, the normal process of review > should catch problems of this sort. If that fails, and an erroneous > registration occurs, the registrant will see the incorrect IANA > registry > entry. So this will serve as an out-of-band mechanism for detecting > attacks of this type, since the MITM presumably won't be able to spoof > the SSL cert from the IANA web site." >=20 > ...or Stephen Farrel's discuss: >=20 > "I believe that there are some uses of EPP that have been > mooted or even put in place that are considerd by quite a few > folks as being quite privacy unfriendly. If so (and please > correct me if I'm wrong) that indicates that the DEs need to > explicitly include consideration of the privacy consequences > of proposed extensions and that DEs ought at minimum require > that any privacy considerations are fully documented in the > relevant specification(s). If it were up to me, I'd probably > go further on that and ask that the DEs try to ensure that > the world is more privacy friendly, but I suspect that'd be > beyond IETF consensus." >=20 > Scott >=20 > _______________________________________________ > EppExt mailing list > EppExt@ietf.org > https://www.ietf.org/mailman/listinfo/eppext From nobody Fri Oct 3 05:19:06 2014 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 F1F431A0380; Fri, 3 Oct 2014 05:19:00 -0700 (PDT) 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 amtT01bvW7Cq; Fri, 3 Oct 2014 05:18:55 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D4441A034D; Fri, 3 Oct 2014 05:18:55 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141003121855.9211.57352.idtracker@ietfa.amsl.com> Date: Fri, 03 Oct 2014 05:18:55 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/ZNbbswG8gFAQbOs8JEZjSFknZfc Cc: eppext@ietf.org Subject: [eppext] I-D Action: draft-ietf-eppext-reg-09.txt 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: Fri, 03 Oct 2014 12:19:01 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Extensible Provisioning Protocol Extensions Working Group of the IETF. Title : Extension Registry for the Extensible Provisioning Protocol Author : Scott Hollenbeck Filename : draft-ietf-eppext-reg-09.txt Pages : 12 Date : 2014-10-03 Abstract: The Extensible Provisioning Protocol (EPP) includes features to add functionality by extending the protocol. It does not, however, describe how those extensions are managed. This document describes a procedure for the registration and management of extensions to EPP and it specifies a format for an IANA registry to record those extensions. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eppext-reg-09 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-eppext-reg-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Oct 3 05:19:18 2014 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 047071A0380 for ; Fri, 3 Oct 2014 05:19:06 -0700 (PDT) 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 8Oc3BUKPiJGG; Fri, 3 Oct 2014 05:19:01 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 82A5D1A036D; Fri, 3 Oct 2014 05:18:56 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: eppext-chairs@tools.ietf.org, draft-ietf-eppext-reg@tools.ietf.org, eppext@ietf.org, presnick@qti.qualcomm.com, presnick@qti.qualcomm.com, stephen.farrell@cs.tcd.ie X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141003121856.9211.39557.idtracker@ietfa.amsl.com> Date: Fri, 03 Oct 2014 05:18:56 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/BQ7IMNojLmtQfpxhe_t5_LbjRt4 Subject: [eppext] New Version Notification - draft-ietf-eppext-reg-09.txt 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: Fri, 03 Oct 2014 12:19:06 -0000 A new version (-09) has been submitted for draft-ietf-eppext-reg: http://www.ietf.org/internet-drafts/draft-ietf-eppext-reg-09.txt Sub state has been changed to AD Followup from Revised ID Needed The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ Diff from previous version: http://www.ietf.org/rfcdiff?url2=draft-ietf-eppext-reg-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. IETF Secretariat. From nobody Fri Oct 3 05:20:56 2014 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 2F67A1A0352; Fri, 3 Oct 2014 05:20:52 -0700 (PDT) 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 q4qLl1uGrq5u; Fri, 3 Oct 2014 05:20:50 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 051E61A0301; Fri, 3 Oct 2014 05:20:50 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Stephen Farrell" To: The IESG X-Test-IDTracker: no X-IETF-IDTracker: 5.6.3.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141003122050.14744.72539.idtracker@ietfa.amsl.com> Date: Fri, 03 Oct 2014 05:20:50 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/XT_j7gp-HoohIFj_9Sgfj9zkRo8 Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org Subject: [eppext] Stephen Farrell's No Objection on draft-ietf-eppext-reg-09: (with COMMENT) 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: Fri, 03 Oct 2014 12:20:52 -0000 Stephen Farrell has entered the following ballot position for draft-ietf-eppext-reg-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for speedily addressing my discuss. From nobody Wed Oct 8 05:01:34 2014 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 2AD341A0307 for ; Wed, 8 Oct 2014 05:01:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.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] 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 EqIG3dYVF09D for ; Wed, 8 Oct 2014 05:01:31 -0700 (PDT) Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com [209.85.213.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBC931A02FF for ; Wed, 8 Oct 2014 05:01:30 -0700 (PDT) Received: by mail-ig0-f181.google.com with SMTP id r10so8120492igi.14 for ; Wed, 08 Oct 2014 05:01:30 -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:content-type; bh=oPuiVBFX5+TRdmh7ej5BxORQJRxNoDqwFw0FimTTYxU=; b=ipdXKb1MdvnMaX4C1mahiI1sHyqYJibjmFednTvdffvf9RXr7jlurIhn2zT+RptR7b nozHplrvn6EK5CgwUJiWaprhTppPu2obBeiYwd0IU6+YnpqwurxUPYeFWrvxauY5FITE 4O21rB6H8xX9KduyWxTiHhpM8xNr4RMEoqmb5znL0j6KMljT1/L0ms5E9EVRaV1sf7Zb WVxwePUCWKkbppVpNjIbTrEXezH95yceEhVnIy0yFCIdkt57fwtlazCo1if7F1eJDLAj i9H6IeZd2JK/74XBOCJLMkKhaEkgv31gHEHHL9JOv0lkX1A7eLgnFPmOUIox0YeAO1lx gSeQ== X-Gm-Message-State: ALoCoQnuTcs92fkPqXaiDfR14BGUKm+bTZRlvv+1MA6k2Pvuna8EP0RZEGmRdUroEOHLDyqbu6E5 MIME-Version: 1.0 X-Received: by 10.42.27.20 with SMTP id h20mr12541834icc.82.1412769689977; Wed, 08 Oct 2014 05:01:29 -0700 (PDT) Received: by 10.107.45.131 with HTTP; Wed, 8 Oct 2014 05:01:29 -0700 (PDT) In-Reply-To: <54242DFA.5080000@sidn.nl> References: <542141B3.9020606@sidn.nl> <54242DFA.5080000@sidn.nl> Date: Wed, 8 Oct 2014 14:01:29 +0200 Message-ID: From: Ulrich Wisser To: eppext@ietf.org Content-Type: multipart/alternative; boundary=20cf30434856857ee10504e8132e Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/lOEWjfAR-f2HTH8Rqjad6cZI4mU Subject: Re: [eppext] EPPEXT @ Honolulu 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, 08 Oct 2014 12:01:32 -0000 --20cf30434856857ee10504e8132e Content-Type: text/plain; charset=UTF-8 +1 in person 2014-09-25 17:00 GMT+02:00 Marco Davids (SIDN) : > > > On 23/09/14 11:47, Antoin Verschuren wrote: > > > so could the silent members of the WG +1 if > > they plan to attend EPPEXT in Honolulu so we can request a proper > > meeting room? Or let us know if you plan to attend remotely. > > +1 in person. > > -- > Marco > > > > _______________________________________________ > EppExt mailing list > EppExt@ietf.org > https://www.ietf.org/mailman/listinfo/eppext > > --20cf30434856857ee10504e8132e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
+1 in person

2014-09-25 17:00 GMT+02:00 Marco Davids (SIDN) <marc= o.davids@sidn.nl>:


On 23/09/14 11:47, Antoin Verschuren wrote:

> so could the silent members of the WG +1 if
> they plan to attend EPPEXT in Honolulu so we can request a proper
> meeting room? Or let us know if you plan to attend remotely.

+1 in person.

--
Marco



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


--20cf30434856857ee10504e8132e-- From nobody Thu Oct 9 06:48:34 2014 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 96F3B1ACEB5; Thu, 9 Oct 2014 06:48:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 cvWrLAef7IFn; Thu, 9 Oct 2014 06:48:10 -0700 (PDT) Received: from exprod6og124.obsmtp.com (exprod6og124.obsmtp.com [64.18.1.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96D491A1A00; Thu, 9 Oct 2014 06:48:05 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob124.postini.com ([64.18.5.12]) with SMTP ID DSNKVDaSABbjK8BjXPNBKDv8yb1jAlgDbJcH@postini.com; Thu, 09 Oct 2014 06:48:05 PDT Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s99DliL2031587 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 9 Oct 2014 09:47:44 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 9 Oct 2014 09:47:43 -0400 From: "Gould, James" To: "eppext@ietf.org" , EPP Provreg , "gtld-tech@icann.org" Thread-Topic: Publishing of the Allocation Token EPP Extension IETF Draft Thread-Index: AQHP48eZxld+P85vBkGvRYYC0cCTpQ== Date: Thu, 9 Oct 2014 13:47:43 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: multipart/related; boundary="_004_FCFCE6CA9AB84676A1B9C9504E2854FCverisigncom_"; type="multipart/alternative" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/W4Hw-qVHMa4fu3JBDkMDuT3741I Subject: [eppext] Publishing of the Allocation Token EPP Extension IETF Draft 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, 09 Oct 2014 13:48:17 -0000 --_004_FCFCE6CA9AB84676A1B9C9504E2854FCverisigncom_ Content-Type: multipart/alternative; boundary="_000_FCFCE6CA9AB84676A1B9C9504E2854FCverisigncom_" --_000_FCFCE6CA9AB84676A1B9C9504E2854FCverisigncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable The first draft of the Allocation Token EPP Extension ( http://tools.ietf.o= rg/html/draft-gould-allocation-token-00 ) has been submitted to the IETF. = I co-authored this draft with Sharon Wodjenski and Trung Tran from Neustar = to support the definition of an allocation token for allocating an object l= ike a domain name. In one use case, the token can be used to support the r= eleasing of reserved names via an external auction provider, where the doma= in names and tokens are provided to the auction provider, and the winning r= egistrant of the auction will receive the token to pass through the registr= ar to the registry to allocate a domain name using a transform command like= create, update, or transfer. Another use case is to use the token to auth= orize the allocation of domain names in a founder=92s program. Other alter= natives like leveraging the authinfo or leveraging one of the key, value pa= ir extensions were considered, but we felt that having an explicit allocati= on token to authorize the allocation of an object was the cleanest approach= . Please review the draft and provide any feedback. Thanks, =97 JG [cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com] James Gould Distinguished Engineer jgould@Verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 VerisignInc.com =93This message (including any attachments) is intended only for the use of= the individual or entity to which it is addressed, and may contain informa= tion that is non-public, proprietary, privileged, confidential and exempt f= rom disclosure under applicable law or may be constituted as attorney work = product. If you are not the intended recipient, you are hereby notified tha= t any use, dissemination, distribution, or copying of this communication is= strictly prohibited. If you have received this message in error, notify se= nder immediately and delete this message immediately.=94 --_000_FCFCE6CA9AB84676A1B9C9504E2854FCverisigncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <114E62C78DE88D49882271424C94DF9C@verisign.com> Content-Transfer-Encoding: quoted-printable The first draft of the Allocation Token EPP Extension ( http://tools.ietf.= org/html/draft-gould-allocation-token-00 ) has been submitted to t= he IETF.  I co-authored this draft with Sharon Wodjenski and Trung Tran from Neustar to support the definition of an allo= cation token for allocating an object like a domain name.  In one use = case, the token can be used to support the releasing of reserved names via = an external auction provider, where the domain names and tokens are provided to the auction provider, and the winn= ing registrant of the auction will receive the token to pass through the re= gistrar to the registry to allocate a domain name using a transform command= like create, update, or transfer.  Another use case is to use the token to authorize the allocation of = domain names in a founder=92s program.  Other alternatives like levera= ging the authinfo or leveraging one of the key, value pair extensions were = considered, but we felt that having an explicit allocation token to authorize the allocation of an object was the cleanest= approach.  

Please review the draft and provide any feedback.

Thanks,

=97

<= span style=3D"font-size: 11pt;">

<= span style=3D"font-size: 11pt;">JG




James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignI= nc.com

=93This message (including any attachments) is int= ended only for the use of the individual or entity to which it is addressed= , and may contain information that is non-public, proprietary, privileged, = confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If yo= u are not the intended recipient, you are hereby notified that any use, dis= semination, distribution, or copying of this communication is strictly proh= ibited. If you have received this message in error, notify sender immediately and delete this message immedi= ately.=94
--_000_FCFCE6CA9AB84676A1B9C9504E2854FCverisigncom_-- --_004_FCFCE6CA9AB84676A1B9C9504E2854FCverisigncom_ Content-Type: image/png; name="BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png" Content-Description: BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png Content-Disposition: inline; filename="BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png"; size=4109; creation-date="Thu, 09 Oct 2014 13:47:43 GMT"; modification-date="Thu, 09 Oct 2014 13:47:43 GMT" Content-ID: <77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com> Content-Transfer-Encoding: base64 iVBORw0KGgoAAAANSUhEUgAAAEkAAABACAIAAADZHs1DAAAP1ElEQVRoBe2aa3CU1RnHN3vLJtmQ hEtiwlUBtZUUCiU6tU7wVhinjOB0xmJnFIdpO1Y6DY586Iwdo36gLc4Iip3pVAL9IKjTDnhDEEWC 1GoICHLRctEkXHIPuZHr7qa/c553T152N9lsNvnWM5nDec97Ls//+T+X854lZWBgwDFuRRaXOiUl hX2kHrcNr1vYfd1T0g/ACIVCQV0CgQD/8miwOZ1Ol8vldrupKTyOK9QU2ThpUA4w9Pf39/X19fT0 UCsYYHA6QcLiYKCwF2MEMNh8Pp/X6/V4PAxOXoDoFcYAG7ICplsXNvClpSFvipAimGy1wQmrMgV4 aUzxekEbLV8yPUlhE66u6YJkqT6fMjKDyjRs2GgaeNKA587OTqZnZGSMLYejx4biEautrQ3eUlNT LUiCx6AyjWHhAbKrqwuEwMNQxYyTYUzmjhIbboMo7e3tyIwoMYA5nZ+duXiyur6ju88u5ZL5s+ff mJ+TmUan4JUGNVbQ2tqKNvx+PwTaZ42uPRpseBeoYMygUvRoijp7AnuPXdhz9PyeyvPI7khxqtoU yTcDofk35j1674LH7luY7U8zVsoo2qgMc5gwYQIeaOaNrpEwNoCBqraujgBALDeoOnr6X9t/4rX9 x9t7gg6Xx+F0K1QEQOBRFKoBVYdCjoGgI6T+MtO9j9+74Nlf3gNChhiQHR0dwMvKykoSXmLYMEUY u3T5MoyxMZEDbJTK81fWlR242NrrcHsdToBpSBZpsKeps0gDocYWDDhC6i8zzbO9ZOWKH38/Ah5K hL1kjDMBbMQMDKa6pgaE6enpggp4r+z5cvOeLx0en6bLpRkTbIKKWjGnijoCgQ3qdB3sdwR6FcJg 8NF7Crc99XNeG/ZQIvkQ3xt1bhgpNrYhlMFYY0NDVna2Bczp/MPrh3dVVjncAHOrvxSwuSw3U3SF SVPIxDKpBVuYQOABMtg3f+aUA39aY/fApqYmLB89CmBZY+T1SA8EcIWb1dfXk8QIaFIUsKM1Dk+a w+1xuLQ1Ag9s1p9uC9rBTk2sUoRLq8Ojp6cy/UR100MvvK41oPkdGMjJySF3svXI8dhHjggbSDhD ED8wSxgTYLsqLihgbsRCULBp3gghBobyN5AY33NalKoeuA2rgInYs1rHU37m4rq/vW/gsReZk63Z 0S70CNsjwiakNTU2etxuAXax5dpf3juuuBJgFiQtPdgUKv3n1DZpPdrawFPDwvBoW/C8L79bceD4 eQOPcELMHB118bHhab29vYq0UIhjvGB77p+VHeRk7MpCIn5lgobRrHY5noCnQgrD5JX5sJJOPZ0Y q/h3rdn0NpsaePgbAkiPWXckjfjfOJytMHrcmngltnGsqqmyqllZUYozK82z4MY8tZNYmtnT6T5+ saWtV1DpXuARRYLB4ltyVWw0hZRA4VDS1Xfiu3pe1TR3vLDz4B9XLSGEAIlw0tzcTJ1oPoiPDXto uXoVzfkzM/kyQ4y/f3JW0QVpig3H7vXLJfkqEW3l4OlLd/95n7JbU0KB4rkTDz6z3HTYGyVlH5+o alTjQ6FtHx575hfFvAUeXodaESNRbHFsErWRQxsaGpRBpqRQX2ru/LKmRScxZZBtnd0lr31oF9G0 l9w2rfjmXJWppdDo79n+xL1mgL1RVd+6+f1jWmUq9dc0tb/z+TfsTmEYB2jEkLZ91vDtONgwQhgj ZavPaf1N/enZegUM3uTP7f3Hga8OnqyKuc323xQ7OH9ICQaefWjRrCkTYo5c/fK7yshlTXVkc739 +RlGanQDREvEEI+IOT1mZxxsBH0WlfO+uioIhQ6dbdSuhffrUI5Aqf7SNz6NuTpInl2xQHlXKJDl CZU8sCDmsN1fnC0/16wCiVqTU6jS3cGvqoUoakk87B9z+lCdcbChKoAJY7SBV9PUobMTE3VwQ9Me X/nXtds/Ph5zj5JlhVk+J2erTY/+JDvDF3tM2ceaNI41kjzw5BTMsrWzx8DD8caBt76+YEDZlaYt 1N4bUqo1fyBE39700rf+09rZHS16dkbqplWL5xf4Vy9Rp+HoUvrG4eo2/emgzmgUWVzBO/Fdrdgk vZjlGPPG0nClCVP1uXpIE6qtPKVBOtF6dUv3pt2faeEiK1Bt/+39kb36ufVaz6YPz6jEDf+WvvQL Mor+WhVsSozwfVnMdWJ2DpcDZF0MElj9+kKuvZuERdEJ16p1B/nAk/bcv46svn/RrLxs3XVdBaUp KzYoR7UX1IS7qg+I62+BLALVUGSQGQbkyM/N129m31jnFukQ3kBoey9bWhuTudWXmze9ZOsQ+aBw 1oN3znOkZTsyJg3+pecQh3QCDFvB4AaqR1NlgZI3IwfG+OGwqdda0xg6qRPjnJGdqveIAKb7OBx6 fG8frR4qH2xaXZzl12diuDJ/KjbiYNevqriytGboMsLooSOq4mBDT1wbWLwFgz5sx3xZyh1B2GaU fDqolJR9FHNn8kHJT2+77rRlH6ew8EUnqHRjYGD65Ex1Ka0Lyk2INJaLg43DzqRJk8BG4WQAgd/L y9ASKFfQsoWl4UH7z4lL7cPkg5k5sdKAAFPLWahYnNuU6ZMnWDFkYEBpOcIt9fbDVHGwyRcUVyNg 6+ntxeVmT0pVx6jBb2cjjd6FtOtJKyk7MFQ+KF35Qz6xBwViHWV++m9wzRD03nXrVIs09tZxUhxk cG68VhxsqIrEkpOdDWPwxi43TUzVt1TcC+g/uyHRxnncqW39rtK3hsgHxbfOn04g1WFJARNcRkE0 9LKh4AOL5hjSerq7EWOMecMSIC0/Px9UwOMzceE0/+QMtyUBcqg7Of5EOK1Jwo/Ht/m9So6/0Zol oVXVNmueBJidNFmKNdVF2LKFsxVvmjTUihhj7G8GG1KyC2dLEN4xw69ub7QEgyAlDIgT6qCijr9R pfTNf7f1Ch4YE1O0kabW5Nqr/+E7b8HfLN50Khh7bMjGVSQ2mX/DDRBHsEKFS+dOSHMNqAO+OgSL 74VVrkxUZUYss/ybuoh8UNXYvnnfaXUNQRkExly9iFpKX10G+p56sMgAQ6EYJGJEKSpORxx/YzZW zlf9DwoL+aUQeHyDp7oGfnW7/nYWNataY6OWBtN0UFm95QP7/qu37FUpnnAKfqWFsEbURI0KfQFs +aJpE/3GIFEoAiTqbEoE+95DtbGHvLy8adOmCTwunublehfc4NWWGWZPtG6FUO1Lbm91c9emdypk WT7DYVJhpoijGkiWjrilDMzLz/j9zxYpLwt7mvwEOZRsw/SPCBs649ejosWLyePA69W/jD6+aNL0 TKe+NhV42j5F/cKeTnelbx6WfKDcT04h8lZpQXOlv+5knUxP8K+/vl9QCTyiCVuPgjQwu0pLS4eB Lq+IKOQWNiDF1dXVYVB89fi8njtmZp6u62rvjfpk5IwiQcXh6O3rr2u6WtXQ/mZFtcKmStjBFHth eMFApjuwY+19N+XlMEIdwrjCCAYzMzPBlmhmU5uwAIqRVtyaKNLS0rJv//5Lly6xGT/iZPj9AYfr xU8bLnaElNzqRkDukuUTUx8TddxT0UUNIHnoqIizKfYEWBBVwdi2J+6bN30SK8tPKMjD3dbEiRPx iLiyxRyQADa0QH6rra19b88efkayw3v3m7aPLnQp0YmB6kssjA1IFKU+/cVptXUUUf7JlZ6y5x/N yN782J1ZGT4FTBcuDjP9fo57OFuiac3gTAAbc/ABAsmV2toP9u418Pgxghh9rrlv29Hmpi5NINjI 4NQUqa0NNWkqPMIbpAVmZPseL5774KJZYVBwlkLQz87Kys3NhTf6ramJ/5MYNtYHHj/ocM1sh+f2 eOTHpM8vdh3+ruPrhm7NXvhT2vqGYbZgA1VozpSMh4tmLl84w6CiweJYfu4UVYj7yQBjs4SxCTzY u3r16ifl5TU1NUigfkB1uVAzJkTIaekOfl3f9d/G3sbOvsZr/U3X1HVLps81c2J6flba3Dz/XTfn FWSnMYW5jBcM5DHaBfn5+FiSjLEdZTTYmCYK5grs9JkzlZWVJAaBh5QKIeda/R9nlNxadgEgtYUG VBqZOqeyXCgEpKkFBfJLt6DVEo6+GiU2NiS04PHYZ0Nj4+lTp85duECXoYIjEgg9/LcfQBqcNpaY TgEXMPhpG1Rgww6ZOOrgEaGG0WOThYRAEDa3tJw/f/7Ct98SCTQfihXT4AGcBApmCXtkTMATCfNy c/kNEVTEesZHyJfMY7LYZG/Uj7eQIQBZ39DAz6tkQvXY3W2HRxuLJeqo+D55MkdwIOGi/IgB4GRg xJw7NthkaTgUkPK5QI3R0kM/AwQkJgcSKKKmCIcxJUu+cyyxGWnEl4BEkTav8CIKCCnSNuPHqTEu 2MZJ1kSXHUvfTXTv8R7/f2zjreHxWT/hS4hkxLhy5QqHNVaYOnUqoX/4pS5wGNCFnE4CHH5wzLfu jS++eOXyZd5t2LBB9tu9e3d5eTk9a9as2bp1a/S0tWvXzp49+9VXXyVZ298iRFFR0dKlS+k0b196 6SUeQcVSJD0znpErV65kRzBs2bKF/mXLlsncYQYzbN26ddQFU6euf/ppGma6SLVz586TJ0/Sj/DO 24uKaFGki8Y5LTFJdt68efrNSCtE37t376lTp6InRABjQEVFxfPPP09+jxgMMKCKFpCBIoNf0fjN YPg4dOiQeTQNVIZRiHW4CwsLd+3axTtIWLx4Mad7oZF+M2HOnDlPPvmkeYxoGGY2btzIK4SOUAqq FVmLi4tXrFgBHlTAMFQbbZm8EskeeeQR5GFBoYKLtoh9GQmSiE4MyojqxpThFzzwtmrVKmNmdmxI tm/fPrOKWI55lAYGKQ2RLOKtPLIFPKBXZALkUGPoRyQBRhupMNdol2MjWImGZ5ZVsQSzZBBDsQex TCSw616MzcyJwIZr8UqYoQHJZqQ00KWoz74OW+BvBkDEFGEJecSm5C3jCwoKpM10BIZ8NBUx1zwq bMYsASa82UljgCjbzIloGKrpR4sYXsQAHn+3di0mhCeLwdODZDt27IjYyEzkrYyxLy6dMoaNkNau LDPXNBQ2Y5Zsb2aaETTQjTFie7+0MZivTp4UoQEW7UIyTJyNNmywkRjIZR2i7WsKIbzFaNmX6McY O3syWGgnRNkB29ehbZ1LltiUjedgRfZxfKoQD0xBOPtbTPShlSulJ1oI+omchEQizZEjR4hV9PCx J+ONl8ojtTAJIWVlZYL8iwrrZtqMkQZeE23/9jGKN4rdNuxteQsnkoLkMTpsogtmiUmDxO6rTEG1 ol2MUFaQGrvCZIyjSidWwDqMp6bYx0e3iaVoLbpfeixsGBI2I3qyR56YihH3jXBiHF0AIBDY7G8J GPDDecDIyiO7SEzCumQX4RC069evh38ZzFsEE6+jjdARg9GF/a0d5/8ActOtScHpPCkAAAAASUVO RK5CYII= --_004_FCFCE6CA9AB84676A1B9C9504E2854FCverisigncom_-- From nobody Mon Oct 13 17:33:22 2014 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 91F4E1A1A6C; Mon, 13 Oct 2014 17:33:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.787 X-Spam-Level: X-Spam-Status: No, score=-7.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, 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 w5cz1QVs3E7M; Mon, 13 Oct 2014 17:33:19 -0700 (PDT) Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E33C11A1A64; Mon, 13 Oct 2014 17:33:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1413246798; x=1444782798; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cJxWvboRgCrqegvlV5x5xQbB6pd8sKvkeyvfcV6Cw8o=; b=lUleS/LxkU5BBcWwz2xhu80WfsocG6ASA7uvDKaYDIH9lIwU6eVxGTFY uQ7MURFHOKS6A//x8A4gV897LsooaSPy0hElof4vRJVx1oFPBfh8mleXX 4+jtLiH+H4y241WxO3Di484DgqmgJR3Ryhhqxxi+ADD/CIBbYcycrp44D g=; X-IronPort-AV: E=McAfee;i="5600,1067,7590"; a="74463229" Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by wolverine01.qualcomm.com with ESMTP; 13 Oct 2014 17:33:17 -0700 X-IronPort-AV: E=Sophos;i="5.04,714,1406617200"; d="scan'208";a="31517975" Received: from nasanexhc06.na.qualcomm.com ([172.30.48.21]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 13 Oct 2014 17:33:17 -0700 Received: from NASANEXM01F.na.qualcomm.com (172.30.48.1) by nasanexhc06.na.qualcomm.com (172.30.48.21) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 13 Oct 2014 17:33:16 -0700 Received: from resnick2.qualcomm.com (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.46.201.192) with Microsoft SMTP Server (TLS) id 15.0.913.22; Mon, 13 Oct 2014 17:33:16 -0700 Message-ID: <543C6F48.50106@qti.qualcomm.com> Date: Mon, 13 Oct 2014 19:33:12 -0500 From: Pete Resnick User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4 MIME-Version: 1.0 To: References: <20141003121856.9211.39557.idtracker@ietfa.amsl.com> In-Reply-To: <20141003121856.9211.39557.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: NASANEXM01G.na.qualcomm.com (10.46.200.111) To NASANEXM01F.na.qualcomm.com (10.46.201.192) Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/YF0ir6XsY84llo8B8FmN4kzLnO0 Cc: draft-ietf-eppext-reg@tools.ietf.org, eppext-chairs@tools.ietf.org, eppext@ietf.org, stephen.farrell@cs.tcd.ie Subject: Re: [eppext] New Version Notification - draft-ietf-eppext-reg-09.txt 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, 14 Oct 2014 00:33:20 -0000 I finally got a chance to read through the changes in -09. Two things that I think still need fixing: 3. IANA Considerations: I see what the addition you made was trying to do, as it was taken directly from IANA's note, but I don't think it's terribly clear and contains some redundant information. I suggest simply adding the appropriate info to the first paragraph: OLD IANA is requested to create a new protocol registry to manage EPP extensions. NEW IANA is requested to create a new protocol registry to manage EPP extensions. This registry should appear under its own heading on IANA's protocol listings, using the same title as the name of the registry. END and then delete the new stuff that you copied from the IANA note. The other stuff that IANA required is already stated in the entry. 4. Security Considerations: The paragraph you put in was meant to *replace* what's currently in Security Considerations, not add to it. The IESG felt that the business about email didn't need to be said. Everything else looks fine. Jim (as shepherd): Please review the rest of the comments at https://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ballot/ to double check that we didn't miss anything. (Scott, wait for Jim to do that check and give his OK before publishing a -10 with the above.) Once Jim does the second-set-of-eyes check, I'll push the Approve button. pr -- Pete Resnick Qualcomm Technologies, Inc. - +1 (858)651-4478 From nobody Mon Oct 13 17:52:17 2014 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 643A51A1A76 for ; Mon, 13 Oct 2014 17:52:15 -0700 (PDT) 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 ma83IklvQs0H; Mon, 13 Oct 2014 17:52:10 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A7A971A1A73; Mon, 13 Oct 2014 17:52:10 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: eppext-chairs@tools.ietf.org, draft-ietf-eppext-reg@tools.ietf.org, eppext@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.4 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141014005210.7935.54098.idtracker@ietfa.amsl.com> Date: Mon, 13 Oct 2014 17:52:10 -0700 From: IETF Secretariat Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/uIUozRdnSf-cHqOSg_GWBgXL_Dg Subject: [eppext] ID Tracker State Update Notice: 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: Tue, 14 Oct 2014 00:52:15 -0000 IESG state changed to Approved-announcement to be sent::Revised I-D Needed from IESG Evaluation::AD Followup Addressing a couple of issues before final approval. ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ From nobody Tue Oct 14 05:23:10 2014 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 759701A8764; Tue, 14 Oct 2014 05:23:00 -0700 (PDT) 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 ZxzAAmtWpLTJ; Tue, 14 Oct 2014 05:22:56 -0700 (PDT) Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 704DF1A8761; Tue, 14 Oct 2014 05:22:52 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKVD0VmECDR+mJCeQRbQOwxuJO/kidczsZ@postini.com; Tue, 14 Oct 2014 05:22:56 PDT Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s9ECMiXJ019513 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Oct 2014 08:22:45 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 14 Oct 2014 08:22:44 -0400 From: "Hollenbeck, Scott" To: Pete Resnick , "internet-drafts@ietf.org" Thread-Topic: [eppext] New Version Notification - draft-ietf-eppext-reg-09.txt Thread-Index: AQHP3wRG8gf9Ie6K3EGw9MymyfBCRZwvEeQAgACBiiA= Date: Tue, 14 Oct 2014 12:22:43 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F494E67B0@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20141003121856.9211.39557.idtracker@ietfa.amsl.com> <543C6F48.50106@qti.qualcomm.com> In-Reply-To: <543C6F48.50106@qti.qualcomm.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/3k49Y3KvFSek7HlfrrVIBncIbPw Cc: "draft-ietf-eppext-reg@tools.ietf.org" , "eppext-chairs@tools.ietf.org" , "eppext@ietf.org" , "stephen.farrell@cs.tcd.ie" Subject: Re: [eppext] New Version Notification - draft-ietf-eppext-reg-09.txt 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, 14 Oct 2014 12:23:00 -0000 > -----Original Message----- > From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Pete Resnick > Sent: Monday, October 13, 2014 8:33 PM > To: internet-drafts@ietf.org > Cc: draft-ietf-eppext-reg@tools.ietf.org; eppext-chairs@tools.ietf.org; > eppext@ietf.org; stephen.farrell@cs.tcd.ie > Subject: Re: [eppext] New Version Notification - draft-ietf-eppext-reg- > 09.txt >=20 > I finally got a chance to read through the changes in -09. Two things > that I think still need fixing: >=20 > 3. IANA Considerations: >=20 > I see what the addition you made was trying to do, as it was taken > directly from IANA's note, but I don't think it's terribly clear and > contains some redundant information. I suggest simply adding the > appropriate info to the first paragraph: >=20 > OLD > IANA is requested to create a new protocol registry to manage EPP > extensions. > NEW > IANA is requested to create a new protocol registry to manage EPP > extensions. This registry should appear under its own heading on > IANA's protocol listings, using the same title as the name of the > registry. > END >=20 > and then delete the new stuff that you copied from the IANA note. The > other stuff that IANA required is already stated in the entry. In the interest of making sure I get this right the second time, are you sa= ying that you want to change this: OLD IANA is requested to create a new protocol registry to manage EPP extensions. The information to be registered and the procedures to be followed in populating the registry are described in Section 2. Name of registry: Extensions for the Extensible Provisioning Protocol Section at http://www.iana.org/protocols: Registry Title: Extensions for the Extensible Provisioning Protocol Registry Name: Extensions for the Extensible Provisioning Protocol Registration Procedure: Specification Required Reference: this draft to this (removing the new text provided by IANA)? NEW IANA is requested to create a new protocol registry to manage EPP extensions. This registry should appear under its own heading on IANA's protocol listings, using the same title as the name of the registry. The information to be registered and the procedures to be followed in populating the registry are described in Section 2. Name of registry: Extensions for the Extensible Provisioning Protocol > 4. Security Considerations: >=20 > The paragraph you put in was meant to *replace* what's currently in > Security Considerations, not add to it. The IESG felt that the business > about email didn't need to be said. >=20 > Everything else looks fine. OK, got this. > Jim (as shepherd): Please review the rest of the comments at > https://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ballot/ to > double > check that we didn't miss anything. (Scott, wait for Jim to do that > check and give his OK before publishing a -10 with the above.) Once Jim > does the second-set-of-eyes check, I'll push the Approve button. I'll publish -10 with the changes described above when I get the OK from Ji= m. Scott From nobody Tue Oct 14 15:23:46 2014 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 00E8C1A0049; Tue, 14 Oct 2014 15:23:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.787 X-Spam-Level: X-Spam-Status: No, score=-7.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, 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 9sF0LY6SU989; Tue, 14 Oct 2014 15:23:27 -0700 (PDT) Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 618B01A0016; Tue, 14 Oct 2014 15:23:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1413325407; x=1444861407; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=xib+ToS1lJabbtyRzJMQIegWBuqsjg1VUHORDCVwIkE=; b=gnGN6e0JBHvbqTJNnz706NnOuUpWZoFyTNviRyXk4TXUp2punCr4sLQa JXrMpHOP6XRQeF0Xf+/UBT8+T5wrV3MFAxNFrJUKZyGMbVlxHgmJtAGbM PI7AznPfR5kyF+tQtuvexHJGBqjwyebyV8eJiu/KbcDnY4qtfLMLnAy69 0=; X-IronPort-AV: E=McAfee;i="5600,1067,7591"; a="74778666" Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Oct 2014 15:23:26 -0700 X-IronPort-AV: E=Sophos;i="5.04,719,1406617200"; d="scan'208";a="824435298" Received: from nasanexhc02.na.qualcomm.com ([10.46.56.110]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 14 Oct 2014 15:23:27 -0700 Received: from NASANEXM01F.na.qualcomm.com (10.46.201.192) by NASANEXHC02.na.qualcomm.com (10.46.56.110) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 14 Oct 2014 15:23:25 -0700 Received: from resnick2.qualcomm.com (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.46.201.192) with Microsoft SMTP Server (TLS) id 15.0.913.22; Tue, 14 Oct 2014 15:23:25 -0700 Message-ID: <543DA247.8000305@qti.qualcomm.com> Date: Tue, 14 Oct 2014 17:23:03 -0500 From: Pete Resnick User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4 MIME-Version: 1.0 To: "Hollenbeck, Scott" References: <20141003121856.9211.39557.idtracker@ietfa.amsl.com> <543C6F48.50106@qti.qualcomm.com> <831693C2CDA2E849A7D7A712B24E257F494E67B0@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F494E67B0@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanexm01a.na.qualcomm.com (129.46.53.228) To NASANEXM01F.na.qualcomm.com (10.46.201.192) Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/iKQvmoY_KgfazHCNBlweQOQoyUg Cc: "draft-ietf-eppext-reg@tools.ietf.org" , "eppext-chairs@tools.ietf.org" , "internet-drafts@ietf.org" , "eppext@ietf.org" , "stephen.farrell@cs.tcd.ie" Subject: Re: [eppext] New Version Notification - draft-ietf-eppext-reg-09.txt 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, 14 Oct 2014 22:23:36 -0000 On 10/14/14 7:22 AM, Hollenbeck, Scott wrote: > In the interest of making sure I get this right the second time, are you saying that you want to change this: > > OLD > IANA is requested to create a new protocol registry to manage EPP > extensions. The information to be registered and the procedures to > be followed in populating the registry are described in Section 2. > > Name of registry: Extensions for the Extensible Provisioning Protocol > > Section athttp://www.iana.org/protocols: > Registry Title: Extensions for the Extensible Provisioning Protocol > Registry Name: Extensions for the Extensible Provisioning Protocol > Registration Procedure: Specification Required > Reference: this draft > > to this (removing the new text provided by IANA)? > > NEW > IANA is requested to create a new protocol registry to manage EPP > extensions. This registry should appear under its own heading on > IANA's protocol listings, using the same title as the name of the > registry. The information to be registered and the procedures to > be followed in populating the registry are described in Section 2. > > Name of registry: Extensions for the Extensible Provisioning Protocol > Correct. Everything that IANA needed is now in that text. > I'll publish -10 with the changes described above when I get the OK from Jim. > Excellent. Just chatted with Jim (who is at the ICANN meeting) and he said he'll try to carve out a bit of time this week to take a look. My finger is on the Approve trigger waiting for the go-ahead. ;-) pr -- Pete Resnick Qualcomm Technologies, Inc. - +1 (858)651-4478 From nobody Thu Oct 23 09:15:09 2014 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 B5E2C1ACD5E for ; Thu, 23 Oct 2014 09:15:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.741 X-Spam-Level: X-Spam-Status: No, score=-5.741 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 lyjqOQoHko_w for ; Thu, 23 Oct 2014 09:15:04 -0700 (PDT) Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A03741ACD1D for ; Thu, 23 Oct 2014 09:15:03 -0700 (PDT) Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at over TLS secured channel (TLSv1:AES128-SHA:128) with XWall v3.50 ; Thu, 23 Oct 2014 18:14:57 +0200 Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id 14.03.0210.002; Thu, 23 Oct 2014 18:14:54 +0200 From: Alexander Mayrhofer To: "eppext@ietf.org" Thread-Topic: EPP service message extension Thread-Index: Ac/u23JUB+vr2J8fTAGLipNUCIMtBA== Date: Thu, 23 Oct 2014 16:14:53 +0000 Message-ID: <19F54F2956911544A32543B8A9BDE0753E0F7D0D@NICS-EXCH2.sbg.nic.at> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.10.0.163] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-XWALL-BCKS: auto Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/PUbr2e-F0neGQ5On3o1JCWnN4V8 Subject: [eppext] EPP service message extension 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, 23 Oct 2014 16:15:07 -0000 All, i've just posted a first version of the description of our EPP service mess= age extension. I'm aiming at registering that extension with the hopefully-= soon-to-be EPP Extensions Registry, and therefore i do believe it is of int= erest to the group. The document defines the state of the extension as it i= s currently deployed (including the shady legacy corners), rather than defi= ning a "nice to have" structure. The extension is also contained in the Net= ::DRI Perl EPP client toolkit. I'm happy to present that draft during the upcoming meeting, if the chairs = can spare a time slot. WG adoption is *not* my goal, since this document wo= uldn't be covered by the current charter anyways. Feedback is, however, of = course appreciated :) Here's the announcement: A new version of I-D, draft-mayrhofer-eppext-servicemessage-00.txt has been successfully submitted by A. Mayrhofer and posted to the IETF repo= sitory. Name: draft-mayrhofer-eppext-servicemessage Revision: 00 Title: EPP Service Messages Extension Document date: 2014-10-23 Group: Individual Submission Pages: 12 URL: http://www.ietf.org/internet-drafts/draft-mayrhofer-eppext-= servicemessage-00.txt Status: https://datatracker.ietf.org/doc/draft-mayrhofer-eppext-ser= vicemessage/ Htmlized: http://tools.ietf.org/html/draft-mayrhofer-eppext-serviceme= ssage-00 thanks, Alex From nobody Mon Oct 27 03:57:42 2014 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 1CFA21A90BE for ; Mon, 27 Oct 2014 03:57:38 -0700 (PDT) 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 EjrFudE0JhUM for ; Mon, 27 Oct 2014 03:57:32 -0700 (PDT) Received: from exprod6og114.obsmtp.com (exprod6og114.obsmtp.com [64.18.1.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B1E61A90B4 for ; Mon, 27 Oct 2014 03:57:29 -0700 (PDT) Received: from brn1lxmailout02.vcorp.ad.vrsn.com ([72.13.63.42]) (using TLSv1) by exprod6ob114.postini.com ([64.18.5.12]) with SMTP ID DSNKVE4lGYIxIPFOWL0Dahiu0yB6REcIuNR4@postini.com; Mon, 27 Oct 2014 03:57:32 PDT Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by brn1lxmailout02.vcorp.ad.vrsn.com (8.13.8/8.13.8) with ESMTP id s9RAvSU7022321 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Oct 2014 06:57:28 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 27 Oct 2014 06:57:27 -0400 From: "Hollenbeck, Scott" To: Pete Resnick Thread-Topic: [eppext] New Version Notification - draft-ietf-eppext-reg-09.txt Thread-Index: AQHP3wRG8gf9Ie6K3EGw9MymyfBCRZwvEeQAgAErEseAE65BgA== Date: Mon, 27 Oct 2014 10:57:26 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F49503ED7@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20141003121856.9211.39557.idtracker@ietfa.amsl.com> <543C6F48.50106@qti.qualcomm.com> <831693C2CDA2E849A7D7A712B24E257F494E67B0@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <543DA247.8000305@qti.qualcomm.com> In-Reply-To: <543DA247.8000305@qti.qualcomm.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/nlXeP5rswmOmWT9eLn1GPopg_QM Cc: "draft-ietf-eppext-reg@tools.ietf.org" , "eppext-chairs@tools.ietf.org" , "eppext@ietf.org" Subject: Re: [eppext] New Version Notification - draft-ietf-eppext-reg-09.txt 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: Mon, 27 Oct 2014 10:57:39 -0000 > -----Original Message----- > From: Pete Resnick [mailto:presnick@qti.qualcomm.com] > Sent: Tuesday, October 14, 2014 6:23 PM > To: Hollenbeck, Scott > Cc: internet-drafts@ietf.org; draft-ietf-eppext-reg@tools.ietf.org; > eppext-chairs@tools.ietf.org; eppext@ietf.org; > stephen.farrell@cs.tcd.ie > Subject: Re: [eppext] New Version Notification - draft-ietf-eppext-reg- > 09.txt [snip] > Excellent. Just chatted with Jim (who is at the ICANN meeting) and he > said he'll try to carve out a bit of time this week to take a look. My > finger is on the Approve trigger waiting for the go-ahead. ;-) >=20 > pr How's that review coming along, Jim? Scott From nobody Mon Oct 27 11:04:21 2014 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 7D6961A88C9 for ; Mon, 27 Oct 2014 11:03:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.963 X-Spam-Level: X-Spam-Status: No, score=0.963 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_47=0.6, SPF_PASS=-0.001] autolearn=no 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 ww03DiDHY8ud for ; Mon, 27 Oct 2014 11:03:32 -0700 (PDT) Received: from smtp.centralnic.com (mail-7.fnb.uk.centralnic.net [5.44.25.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6F411A88DE for ; Mon, 27 Oct 2014 11:03:31 -0700 (PDT) Received: from Gavins-MacBook-Pro.local (unknown [213.205.251.66]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.centralnic.com (Postfix) with ESMTPSA id C9B5BA204; Mon, 27 Oct 2014 18:03:22 +0000 (UTC) Message-ID: <544E88B1.2060800@centralnic.com> Date: Mon, 27 Oct 2014 18:02:25 +0000 From: Gavin Brown Organization: CentralNic Ltd User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Alexander Mayrhofer , "eppext@ietf.org" References: <19F54F2956911544A32543B8A9BDE0753E0F7D0D@NICS-EXCH2.sbg.nic.at> In-Reply-To: <19F54F2956911544A32543B8A9BDE0753E0F7D0D@NICS-EXCH2.sbg.nic.at> OpenPGP: id=F923B4CE Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vd2Wcf3gH8N98q25O42wjxmIjGC5fJsw9" Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/Z9WLZQrMRCcFbqIntMv912uyq9k Subject: Re: [eppext] EPP service message extension 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: Mon, 27 Oct 2014 18:03:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vd2Wcf3gH8N98q25O42wjxmIjGC5fJsw9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Alexander, I've reviewed this draft. It addresses a pressing issue which a lot of registrars want to see resolved. My initial concern is that your draft is too flexible. There is a fine balance to be struck between being flexible enough to allow for a variety of different business rules, and being so flexible that you end up with wildly different (and non-interoperable) implementations. There are a few things that I think you could do to tighten up the specificatio= n: * the list of events which would trigger a message should be enumerated, and a unique token for each be included in the schema. I am sure that this mailing list could produce an almost comprehensive list of such even= ts. So the synax would look like this: transferApproved Events that are not covered by this list could be handled using a "custom" value with an optional attribute, like so: custom * require that all messages have a timestamp, like so: transferApproved 2014-10-27T17:48:21.0Z * require that all messages be associated with a single object in the repository. The object should be specified by its namespace, and its unique identifier (and optionally ROID), for example: transferApproved 2014-10-27T17:48:21.0Z Inbound transfer of test.example was APPROVED. Subordinate hosts ns1.test.example, ns2.test.example were also transferred. urn:ietf:params:xml:ns:host-1.0 ns1.text.example hostroid-1 If an event affects multiple objects, queue multiple messages. * Where an event has resulted in a change to the attributes of an object, it should be possible to include a partial response in the message, containing the changed object attributes (plus the minimum necessary elements to allow the element to validate against the schema), like so: transferApproved 2014-10-27T17:48:21.0Z Inbound transfer of test.example was APPROVED. Subordinate hosts ns1.test.example, ns2.test.example were also transferred. urn:ietf:params:xml:ns:host-1.0 ns1.test.example ns1.test.example hostroid-1 G. On 23/10/2014 17:14, Alexander Mayrhofer wrote: > All, >=20 > i've just posted a first version of the description of our EPP service = message extension. I'm aiming at registering that extension with the hope= fully-soon-to-be EPP Extensions Registry, and therefore i do believe it i= s of interest to the group. The document defines the state of the extensi= on as it is currently deployed (including the shady legacy corners), rath= er than defining a "nice to have" structure. The extension is also contai= ned in the Net::DRI Perl EPP client toolkit. >=20 > I'm happy to present that draft during the upcoming meeting, if the cha= irs can spare a time slot. WG adoption is *not* my goal, since this docum= ent wouldn't be covered by the current charter anyways. Feedback is, howe= ver, of course appreciated :) >=20 > Here's the announcement: >=20 > A new version of I-D, draft-mayrhofer-eppext-servicemessage-00.txt > has been successfully submitted by A. Mayrhofer and posted to the IETF = repository. >=20 > Name: draft-mayrhofer-eppext-servicemessage > Revision: 00 > Title: EPP Service Messages Extension > Document date: 2014-10-23 > Group: Individual Submission > Pages: 12 > URL: http://www.ietf.org/internet-drafts/draft-mayrhofer-epp= ext-servicemessage-00.txt > Status: https://datatracker.ietf.org/doc/draft-mayrhofer-eppext= -servicemessage/ > Htmlized: http://tools.ietf.org/html/draft-mayrhofer-eppext-servi= cemessage-00 >=20 >=20 > thanks, > Alex >=20 > _______________________________________________ > EppExt mailing list > EppExt@ietf.org > https://www.ietf.org/mailman/listinfo/eppext >=20 --=20 Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR. --vd2Wcf3gH8N98q25O42wjxmIjGC5fJsw9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlROiLEACgkQ6H45IPkjtM4bPgCfeAP/1AGov4VsiR0OuD92mBAn wv0An32l25jNacwhcifSRzPh1iK2EQe/ =rW41 -----END PGP SIGNATURE----- --vd2Wcf3gH8N98q25O42wjxmIjGC5fJsw9-- From nobody Tue Oct 28 05:30:09 2014 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 1E55E1A6FDB for ; Tue, 28 Oct 2014 05:29:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.084 X-Spam-Level: X-Spam-Status: No, score=0.084 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 0ljc9PEFK82T for ; Tue, 28 Oct 2014 05:29:23 -0700 (PDT) Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A9FE1A87D1 for ; Tue, 28 Oct 2014 05:24:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed; h=from:to:subject:thread-topic:thread-index:date:message-id:references:in-reply-to:accept-language:content-language:x-ms-has-attach:x-ms-tnef-correlator:x-originating-ip:content-type:content-transfer-encoding:mime-version; bh=ycbDeaxXk8bSjpzC01mCvgZebwDBwWB1fB8OfW6iXvg=; b=lvygKpPx8OSCdY6lpfXPCEPkYiEYTFh4mPGWyLwjLt7K2a+sotudZQb7lbBgcLbKAEu7Gmsshw2gDKM+HgrtjIU7bPmzph73Yq2X/1YTSJ2lz7sLId/0ecV9cAcm6MOG61I2sqCx6GCeoN0OH4ToxZmmgkICEFyo0Q6BLx/q9Yw= Received: from kahubcasn01.SIDN.local ([192.168.2.73]) by arn2-kamx.sidn.nl with ESMTP id s9SCO9MQ012006-s9SCO9MS012006 (version=TLSv1.0 cipher=AES128-SHA bits=128 verify=CAFAIL) for ; Tue, 28 Oct 2014 13:24:09 +0100 Received: from KAMBX2.SIDN.local ([fe80::b1fd:88d9:e136:9655]) by kahubcasn01 ([192.168.2.73]) with mapi id 14.03.0174.001; Tue, 28 Oct 2014 13:24:04 +0100 From: Rik Ribbers To: Antoin Verschuren , "eppext@ietf.org" Thread-Topic: [eppext] EPPEXT @ Honolulu Thread-Index: AQHP1xNuX35LalSxoUSWfqvnCIcnX5xFpeJQ Date: Tue, 28 Oct 2014 12:24:04 +0000 Message-ID: References: <542141B3.9020606@sidn.nl> In-Reply-To: <542141B3.9020606@sidn.nl> Accept-Language: nl-NL, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.129.108] 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/xZDBOQ21CIXYH9ZiXjsVr6WCfGQ Subject: Re: [eppext] EPPEXT @ Honolulu 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, 28 Oct 2014 12:29:25 -0000 +1 I will be attending in person -----Original Message----- From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Antoin Verschure= n Sent: dinsdag 23 september 2014 11:48 To: eppext@ietf.org Subject: [eppext] EPPEXT @ Honolulu -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, So far the chairs received 3 requests to have an EPPEXT meeting @IETF91 in Honolulu, so we think it's wise to meet. We hope to have more th= an 5 participants, so could the silent members of the WG +1 if they plan to= attend EPPEXT in Honolulu so we can request a proper meeting room? Or let us know if you plan to attend remotely. As for agenda items, please send them to the chairs if they don't show up i= n the proposed agenda below. We have identified a few issues on the list that were more or less fundamen= tal and not for any particular WG document for f2f discussion. We intend to request for a 1,5 hour slot to have enough time to discuss, bu= t I would like to ask for volunteers to present/summarize and lead these di= scussions: Agenda: 0. Welcome (Antoin 1 min.) 1. draft-ietf-eppext-reg (?? 5 min.) 2. Discussion: Is there sufficient consensus on current EPPEXT drafts for s= tandards track, or should they be informational? (?? 10 min.) 3. draft-ietf-eppext-launchphase/draft-ietf-eppext-tmch-smd (?? 5 min.) 4. Discussion on protocol extension, object extension, or a command-respons= e extension to progress draft-ietf-eppext-keyrelay (?? 20 min.) 5. draft-ietf-eppext-idnmap (?? 10 min.) 6. Discuss if we take on new work items/documents/extensions, recharter or = close down (?? 10 min.) 7. AOB - -- Antoin Verschuren Technical Policy Advisor SIDN Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands P: +31 26 3525500 M: +31 6 23368970 Mailto: antoin.verschuren@sidn.nl XMPP: antoin.verschuren@jabber.sidn.nl HTTP://www.sidn.nl/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJUIUGzAAoJEDqHrM883Agnz7IH/3mtaHw8G6/RpXJ/AeNiF6OA 6xS3W1YsZcba4dep6BZpPKU8EcYvl1Twke6GQ/TMRCIPFDd/ty8Z+DmDFweXs5H4 SEcQ7n3RPKJ5NPcIKdmlbUIcovqV9Fgzn7bwHLNvAkidN/3HCv9EenwTuYwvSjSS GaauATqTKgpwwO7xRQ61ae7EV5jeyMZ6B1++MuIoYaYxvCuK6PTEjqN5kxHn2tmE aTjgrQxuvsySoQwYkKERCRUayJ0vQCFwZzevHKc4rzKaphj0ItOp1lHg/PTDb4dD PUANEa1Bgb77nbYKJqW9QMKxWLtyKXY51+QxL/rp7Uuo0dZow1eS5V21t3q++y8=3D =3DJT5T -----END PGP SIGNATURE----- _______________________________________________ EppExt mailing list EppExt@ietf.org https://www.ietf.org/mailman/listinfo/eppext From nobody Tue Oct 28 07:58:30 2014 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 638DF1A898F for ; Tue, 28 Oct 2014 07:58:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.012 X-Spam-Level: X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 l_LpjBKZeaNr for ; Tue, 28 Oct 2014 07:58:27 -0700 (PDT) Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id B412A1A8A12 for ; Tue, 28 Oct 2014 07:58:26 -0700 (PDT) Received: from [192.168.2.103] (unknown [114.252.212.90]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0ApMJALr09Up4vHAA--.32021S2; Tue, 28 Oct 2014 22:58:20 +0800 (CST) From: Ning Kong Content-Type: multipart/alternative; boundary="Apple-Mail=_D5950032-FF94-4F74-8C20-D3759F693072" Message-Id: Date: Tue, 28 Oct 2014 22:58:14 +0800 To: eppext@ietf.org Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) X-Mailer: Apple Mail (2.1990.1) X-CM-TRANSID: AQAAf0ApMJALr09Up4vHAA--.32021S2 X-Coremail-Antispam: 1UD129KBjvdXoW7Gr15Xw4fZw45Jr13GrW3Wrg_yoWDAFb_ZF n5trW5KwsFya17Wa1IyrWSvrWxZayUKa12k34FqF12k340yws8XFs0vr18Cr47XF4Igwn5 CFy3CryxKryxujkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUb58YjsxI4VWxJwAYFVCjjxCrM7AC8VAFwI0_Jr0_Gr1l1xkIjI8I 6I8E6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM2 8CjxkF64kEwVA0rcxSw2x7M28EF7xvwVC0I7IYx2IY67AKxVWUCVW8JwA2z4x0Y4vE2Ix0 cI8IcVCY1x0267AKxVWUJVW8JwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z2 80aVCY1x0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487McIj6xIIjxv20xvE 14v26r106r15McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2 IYc2Ij64vIr41l42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAq x4xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1j6r 15MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF 7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14 v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Gr0_Gr1UYxBIdaVFxhVjvjDU0xZFpf9x 07UK_M-UUUUU= X-CM-SenderInfo: xqnr0ww6fq0xffof0/ Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/-RBi555qkOBlVZ6_y_Xv1r0TyLo Subject: [eppext] EPP Domain Name Mapping Extension for Bundling Registration 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, 28 Oct 2014 14:58:29 -0000 --Apple-Mail=_D5950032-FF94-4F74-8C20-D3759F693072 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=gb2312 Hi all, I=A1=AFve posted an individual draft which proposes an EPP extension of = EPP domain name mapping for the provisioning of bundling registration. = We hope the extension proposed by this document can meet the needs of = registration and management for the bundled domain names as one single = package. So, the bundled domain names (either IDN variants or domain = names having identical second level label with different TLDs) may have = the same properties, such as expiration date and sponsoring registrar, = by sharing one domain object. Whenever users update any properties = within a bundle package, all of the domains' properties within the = bundle package may be synchronously updated. The draft can be found as the following link, = http://www.ietf.org/internet-drafts/draft-kong-eppext-bundling-registratio= n-00.txt Any comments are appreciated! To Chairs, if I can get 5-10 minutes slot of EPPEXT WG meeting in = honolulu, I=A1=AFd like to present the major idea of this extension. = Thanks! Cheers, Ning --Apple-Mail=_D5950032-FF94-4F74-8C20-D3759F693072 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=gb2312
Hi = all,

I=A1=AFve posted an = individual draft which proposes an EPP extension of EPP = domain name mapping for the provisioning of bundling registration. = We hope the extension proposed by this document can meet the needs = of registration and management for the bundled domain names as one = single package. So, the bundled domain names (either IDN variants or domain = names having identical second level label with different TLDs) = may have = the same properties, such as expiration date and sponsoring registrar, by = sharing one domain object. Whenever users update any properties within a = bundle package, all of the domains' properties within the bundle = package may be synchronously updated.

The draft can be found as the following = link, http://www.ietf.org/internet-drafts/draft-kong-eppext-bundling-= registration-00.txt

Any comments are appreciated!

To Chairs, if I can get 5-10 minutes slot of = EPPEXT WG meeting in honolulu, I=A1=AFd like to present the major = idea of this extension. Thanks!

Cheers,
Ning





= --Apple-Mail=_D5950032-FF94-4F74-8C20-D3759F693072-- From nobody Thu Oct 30 03:56:41 2014 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 B35B51AD0B8 for ; Thu, 30 Oct 2014 03:56:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.441 X-Spam-Level: X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, J_CHICKENPOX_47=0.6, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 puJ4OV4Gl7_O for ; Thu, 30 Oct 2014 03:56:36 -0700 (PDT) Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB1051AD0B6 for ; Thu, 30 Oct 2014 03:56:35 -0700 (PDT) Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at over TLS secured channel (TLSv1:AES128-SHA:128) with XWall v3.50 ; Thu, 30 Oct 2014 11:56:33 +0100 Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id 14.03.0210.002; Thu, 30 Oct 2014 11:56:28 +0100 From: Alexander Mayrhofer To: Gavin Brown , "eppext@ietf.org" Thread-Topic: [eppext] EPP service message extension Thread-Index: Ac/u23JUB+vr2J8fTAGLipNUCIMtBADLFWaAAINUhAA= Date: Thu, 30 Oct 2014 10:56:28 +0000 Message-ID: <19F54F2956911544A32543B8A9BDE075465D73D3@NICS-EXCH2.sbg.nic.at> References: <19F54F2956911544A32543B8A9BDE0753E0F7D0D@NICS-EXCH2.sbg.nic.at> <544E88B1.2060800@centralnic.com> In-Reply-To: <544E88B1.2060800@centralnic.com> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.10.0.163] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-XWALL-BCKS: auto Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/gW64SmG-js5YWw-sETwAfJhDQGk Subject: Re: [eppext] EPP service message extension 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, 30 Oct 2014 10:56:39 -0000 R2F2aW4sDQoNCnRoYW5rcyBmb3IgdGhlIHJldmlldy4uLiBUaGlzIGlzIGRlZmluaXRlbHkgbXVj aCBhcHByZWNpYXRlZCAtIG1vcmUgaW5saW5lOg0KDQo+IEkndmUgcmV2aWV3ZWQgdGhpcyBkcmFm dC4gSXQgYWRkcmVzc2VzIGEgcHJlc3NpbmcgaXNzdWUgd2hpY2ggYSBsb3Qgb2YgcmVnaXN0cmFy cw0KPiB3YW50IHRvIHNlZSByZXNvbHZlZC4NCj4NCj4gTXkgaW5pdGlhbCBjb25jZXJuIGlzIHRo YXQgeW91ciBkcmFmdCBpcyB0b28gZmxleGlibGUuIFRoZXJlIGlzIGEgZmluZSBiYWxhbmNlIHRv DQo+IGJlIHN0cnVjayBiZXR3ZWVuIGJlaW5nIGZsZXhpYmxlIGVub3VnaCB0byBhbGxvdyBmb3Ig YSB2YXJpZXR5IG9mIGRpZmZlcmVudA0KPiBidXNpbmVzcyBydWxlcywgYW5kIGJlaW5nIHNvIGZs ZXhpYmxlIHRoYXQgeW91IGVuZCB1cCB3aXRoIHdpbGRseSBkaWZmZXJlbnQNCj4gKGFuZCBub24t aW50ZXJvcGVyYWJsZSkgaW1wbGVtZW50YXRpb25zLiBUaGVyZSBhcmUgYSBmZXcgdGhpbmdzIHRo YXQgSSB0aGluaw0KPiB5b3UgY291bGQgZG8gdG8gdGlnaHRlbiB1cCB0aGUgc3BlY2lmaWNhdGlv bjoNCg0KSSBkbyBjZXJ0YWlubHkgYWdyZWUuIFdoZW4gaSB3cm90ZSB0aGUgZHJhZnQsIGkgaGFk IHRoZSBjaG9pY2UgYmV0d2VlbiAiZG9jdW1lbnQgd2hhdCdzIHRoZXJlLCBhbmQgdGFrZSB0aGUg YmxhbWUiLCBvciAic3BlY2lmeSB3aGF0IHlvdSB3aXNoIHdvdWxkIGJlIHRoZXJlIi4gSSBjaG9z ZSBkb2N1bWVudGluZyB0aGUgZXhpc3RpbmcgZXh0ZW5zaW9uLCBzaW5jZSBpdCdzIGRlcGxveWVk IGluIHByb2R1Y3Rpb24sIGFuZCAtIGFzIHlvdSBrbm93IC0gc2hpZnRpbmcgdGhhdCB0b3dhcmRz IGEgIm5pY2UgdG8gaGF2ZSIgdmVyc2lvbiBvZiBpdCBpcyBzaWduaWZpY2FudCBlZmZvcnQgb24g Ym90aCBzaWRlcyBvZiB0aGUgRVBQIGNvbm5lY3Rpb24uLg0KDQpXZSdyZSBhbGwgdGVtcHRlZCB0 byBpbXByb3ZlIHRoaW5ncyBhcyBzb29uIGFzIHdlIHNlZSB0aGVtLCBidXQgaXQncyBhIGdvb2Qg cXVlc3Rpb24gd2hldGhlciB0aGUgRVBQIEV4dGVuc2lvbnMgUmVnaXN0cnkgc2hvdWxkIHRha2Ug ImRvY3VtZW50YXRpb24gb2YgZXhpc3RpbmcgdGhpbmdzIiBvciAiY2xlYW4gc2xhdGUiIHNwZWNp ZmljYXRpb25zLiBCb3RoIGhhdmUgdmFsaWQgcmVhc29ucy4NCg0KQnV0LCB5ZXMsIG9mIGNvdXJz ZSBpIGRvIGFwcHJlY2lhdGUgeW91ciBmZWVkYmFjayBvbiB0aGUgc3RydWN0dXJlIG9mIHRoZSBl eHRlbnNpb24gLSBqdXN0IG5vdCBzdXJlIHdoYXQgZGlyZWN0aW9uIHRvIHRha2Ugd2l0aCB0aGUg ZHJhZnQgLSB1bHRpbWF0ZWx5LCBpIHdvdWxkIHByb2JhYmx5IG5lZWQgdG8gY3JlYXRlIHR3byBk cmFmdHMsIG9uZSBmb3IgdGhlIGN1cnJlbnRseSBleGlzdGluZyBleHRlbnNpb24sIGFuZCBvbmUg Zm9yIHRoZSAibmljZSB0byBoYXZlIiBzY2hlbWEgIDopDQoNCj4gKiB0aGUgbGlzdCBvZiBldmVu dHMgd2hpY2ggd291bGQgdHJpZ2dlciBhIG1lc3NhZ2Ugc2hvdWxkIGJlIGVudW1lcmF0ZWQsDQo+ IGFuZCBhIHVuaXF1ZSB0b2tlbiBmb3IgZWFjaCBiZSBpbmNsdWRlZCBpbiB0aGUgc2NoZW1hLiBJ IGFtIHN1cmUgdGhhdCB0aGlzDQo+IG1haWxpbmcgbGlzdCBjb3VsZCBwcm9kdWNlIGFuIGFsbW9z dCBjb21wcmVoZW5zaXZlIGxpc3Qgb2Ygc3VjaCBldmVudHMuDQoNClRoZXJlJ3MgYSBsaXN0IG9m IGV2ZW50cyB0aGF0IHdlIHVzZSwgc29tZSBhcmUgY29udGFpbmVkIGluIHRoZSBleGFtcGxlcy4g U29tZSBhcmUgcHJldHR5IGdlbmVyaWMsIHdoaWxlIHNvbWUgYXJlIHZlcnkgc3BlY2lmaWMgdG8g c29tZSBvZiBvdXIgcG9saWNpZXMuLi4gRm9yIGV4YW1wbGU6DQoNCkNvbnRhY3RTdGF0dXNTZXQg ICAgICAgICAgICAgIA0KQ29udGFjdFN0YXR1c1Vuc2V0ICAgICAgICAgICAgDQpEZWxlZ2F0aW9u RGVsZXRlICAgICAgICAgICAgICANCkhhc0V4cGlyZWQgICAgICAgICAgICAgICAgICAgIA0KTG93 Q3JlZGl0ICAgICAgICAgICAgICAgICAgICAgDQpVUlNMb2NrZWQgICAgICAgICAgICAgICAgICAg ICANCk5vQ3JlZGl0ICAgICAgICAgICAgICAgICAgICAgIA0KLi4uDQoNCg0KPiBTbyB0aGUgc3lu YXggd291bGQgbG9vayBsaWtlIHRoaXM6DQo+IA0KPiA8bWVzc2FnZSB4bWxucz0iaHR0cDovL3Rs ZC1ib3guYXQveG1sbnMvcmVzZGF0YS0xLjAiPg0KPiAgIDx0eXBlPnRyYW5zZmVyQXBwcm92ZWQ8 L3R5cGU+DQo+ICAgPCEtLSAuLi4gLS0+DQo+IDwvbWVzc2FnZT4NCj4NCj4gRXZlbnRzIHRoYXQg YXJlIG5vdCBjb3ZlcmVkIGJ5IHRoaXMgbGlzdCBjb3VsZCBiZSBoYW5kbGVkIHVzaW5nIGEgImN1 c3RvbSINCj4gdmFsdWUgd2l0aCBhbiBvcHRpb25hbCBhdHRyaWJ1dGUsIGxpa2Ugc286DQo+IA0K PiA8bWVzc2FnZSB4bWxucz0iaHR0cDovL3RsZC1ib3guYXQveG1sbnMvcmVzZGF0YS0xLjAiPg0K PiAgIDx0eXBlIG5hbWU9InNvbWV0aGluZ0N1c3RvbSI+Y3VzdG9tPC90eXBlPg0KPiAgIDwhLS0g Li4uIC0tPg0KPiA8L21lc3NhZ2U+DQoNClVuZGVyc3Rvb2QuLi4gV2VsbCwgYW4gYWx0ZXJuYXRp dmUgdG8gdGhhdCB3b3VsZCBiZSB0byBjcmVhdGUgYW4gSUFOQSByZWdpc3RyeSBmb3IgdGhlIGV2 ZW50IHR5cGUgKC4uLiBub3Qgc3VyZSB0aGF0J3Mgd29ydGggdGhlIGVmZm9ydCksIGFuZCB1c2Ug Zmlyc3QgY29tZSBmaXJzdCBzZXJ2ZWQgYXMgcG9saWN5Li4uIEJ1dCB1c2luZyBhICJjdXN0b20i IHR5cGUgd291bGQgYWxzbyB3b3JrLi4uIEknbSBhIGJpdCByZWx1Y3RhbnQgYWJvdXQgc3dpdGNo aW5nIGZyb20gYXR0cmlidXRlIHRvIGVsZW1lbnQgZm9yIHRoZSAidHlwZSIgaW5mb3JtYXRpb24s IGJ1dCBvZiBjb3Vyc2UgaXQgbWFrZXMgc2Vuc2UgZm9yICJtb3JlIHNwZWNpZmljIiBpbmZvcm1h dGlvbi4uLiBhIHBhaXIgb2YgYXR0cmlidXRlcyBjb3VsZCBhbHNvIHdvcmsuLg0KDQogPiAqIHJl cXVpcmUgdGhhdCBhbGwgbWVzc2FnZXMgaGF2ZSBhIHRpbWVzdGFtcCwgbGlrZSBzbzoNCj4gDQo+ IDxtZXNzYWdlIHhtbG5zPSJodHRwOi8vdGxkLWJveC5hdC94bWxucy9yZXNkYXRhLTEuMCI+DQo+ ICAgPHR5cGU+dHJhbnNmZXJBcHByb3ZlZDwvdHlwZT4NCj4gICA8ZXZlbnREYXRlPjIwMTQtMTAt MjdUMTc6NDg6MjEuMFo8L2V2ZW50RGF0ZT4NCj4gICA8IS0tIC4uLiAtLT4NCj4gPC9tZXNzYWdl Pg0KDQpHb29kIHBvaW50LiBJIG5lZWQgdG8gZG91YmxlY2hlY2sgd2hldGhlciBvdXIgYXNzdW1w dGlvbiB3YXMgdGhhdCB0aGVyZSdzIGVub3VnaCB0aW1lc3RhbXBpbmcgaW5mb3JtYXRpb24gaW4g dGhlIHJlc3Qgb2YgdGhlIEVQUCBmcmFtZSBhbHJlYWR5Lg0KDQo+ICogcmVxdWlyZSB0aGF0IGFs bCBtZXNzYWdlcyBiZSBhc3NvY2lhdGVkIHdpdGggYSBzaW5nbGUgb2JqZWN0IGluIHRoZQ0KPiBy ZXBvc2l0b3J5LiBUaGUgb2JqZWN0IHNob3VsZCBiZSBzcGVjaWZpZWQgYnkgaXRzIG5hbWVzcGFj ZSwgYW5kIGl0cyB1bmlxdWUNCj4gaWRlbnRpZmllciAoYW5kIG9wdGlvbmFsbHkgUk9JRCksIGZv ciBleGFtcGxlOg0KIA0KPiA8bWVzc2FnZSB4bWxucz0iaHR0cDovL3RsZC1ib3guYXQveG1sbnMv cmVzZGF0YS0xLjAiPg0KPiAgIDx0eXBlPnRyYW5zZmVyQXBwcm92ZWQ8L3R5cGU+DQo+ICAgPGV2 ZW50RGF0ZT4yMDE0LTEwLTI3VDE3OjQ4OjIxLjBaPC9ldmVudERhdGU+DQo+ICAgPGRlc2M+SW5i b3VuZCB0cmFuc2ZlciBvZiB0ZXN0LmV4YW1wbGUgd2FzIEFQUFJPVkVELg0KPiAgICAgU3Vib3Jk aW5hdGUgaG9zdHMgbnMxLnRlc3QuZXhhbXBsZSwgbnMyLnRlc3QuZXhhbXBsZSB3ZXJlDQo+ICAg ICBhbHNvIHRyYW5zZmVycmVkLjwvZGVzYz4NCj4gICA8b2JqZWN0Pg0KPiAgICAgPG9ialVSST51 cm46aWV0ZjpwYXJhbXM6eG1sOm5zOmhvc3QtMS4wPC9vYmpVUkk+DQo+ICAgICA8b2JqSUQ+bnMx LnRleHQuZXhhbXBsZTwvb2JqSUQ+DQo+ICAgICA8b2JqUk9JRD5ob3N0cm9pZC0xPC9vYmpST0lE Pg0KPiAgIDwvb2JqZWN0Pg0KPiA8L21lc3NhZ2U+DQoNClRoZXJlJ3MgKnNvbWUqIGtpbmQgb2Yg cmVsYXRpb24gbWVjaGFuaXNtIGluIHVzZSBieSBpbmNsdWRpbmcgIjxkYXRhPiA8ZW50cnkgdHlw ZT0nZG9tYWluJz4uLi4iIGVsZW1lbnRzIGludG8gdGhlIG1lc3NhZ2UsIGJ1dCBvZiBjb3Vyc2Ug aXQncyB2ZXJ5IG11Y2ggImZyZWUgZm9ybSIgaW5mb3JtYXRpb24gLSB5ZXMsIHRoZSBwcm9wb3Nh bCBhYm92ZSBpcyByZWFsbHkgbmljZSwgd2lsbCBoYXZlIHRvIHRoaW5rIGFib3V0IGltcGxpY2F0 aW9ucyBvbiBjdXJyZW50IGltcGxlbWVudGF0aW9ucyBhbmQgDQoNCj4gSWYgYW4gZXZlbnQgYWZm ZWN0cyBtdWx0aXBsZSBvYmplY3RzLCBxdWV1ZSBtdWx0aXBsZSBtZXNzYWdlcy4NCg0KSG1tLi4u IFNvbWUgb2YgdGhlIGV2ZW50cyAocGFydGljdWxhcmx5IHRoZSAiV2lsbEV4cGlyZSIgdHlwZSkg Y29udGFpbnMgbGlzdHMgd2l0aCBodW5kcmVkcyBvZiBkb21haW5zLCBhbmQgaW4gc3VjaCBjYXNl cyBpIHdvdWxkIHJhdGhlciBub3Qgd2FudCB0byBxdWV1ZSB0aGF0IG1hbnkgbWVzc2FnZXMgZm9y IHRoZSByZWdpc3RyYXIuIEhvd2V2ZXIsIGkgZG9uJ3Qgc2VlIHdoeSB0aGUgIm9iamVjdCIgZWxl bWVudCB5b3UgcHJvcG9zZWQgYWJvdmUgY291bGRuJ3QgYmUgMC4ubiwgdGhpcyB3b3VsZHdvcmsg cGVyZmVjdGx5IHdlbGwgaW4gdGhhdCB1c2UgY2FzZS4NCiANCj4gKiBXaGVyZSBhbiBldmVudCBo YXMgcmVzdWx0ZWQgaW4gYSBjaGFuZ2UgdG8gdGhlIGF0dHJpYnV0ZXMgb2YgYW4gb2JqZWN0LCBp dA0KPiBzaG91bGQgYmUgcG9zc2libGUgdG8gaW5jbHVkZSBhIHBhcnRpYWwgPGluZm8+IHJlc3Bv bnNlIGluIHRoZSBtZXNzYWdlLA0KPiBjb250YWluaW5nIHRoZSBjaGFuZ2VkIG9iamVjdCBhdHRy aWJ1dGVzIChwbHVzIHRoZSBtaW5pbXVtIG5lY2Vzc2FyeQ0KPiBlbGVtZW50cyB0byBhbGxvdyB0 aGUgZWxlbWVudCB0byB2YWxpZGF0ZSBhZ2FpbnN0IHRoZSBzY2hlbWEpLCBsaWtlIHNvOg0KPiAN Cj4gPG1lc3NhZ2UgeG1sbnM9Imh0dHA6Ly90bGQtYm94LmF0L3htbG5zL3Jlc2RhdGEtMS4wIj4N Cj4gICA8dHlwZT50cmFuc2ZlckFwcHJvdmVkPC90eXBlPg0KPiAgIDxldmVudERhdGU+MjAxNC0x MC0yN1QxNzo0ODoyMS4wWjwvZXZlbnREYXRlPg0KPiAgIDxkZXNjPkluYm91bmQgdHJhbnNmZXIg b2YgdGVzdC5leGFtcGxlIHdhcyBBUFBST1ZFRC4NCj4gICAgIFN1Ym9yZGluYXRlIGhvc3RzIG5z MS50ZXN0LmV4YW1wbGUsIG5zMi50ZXN0LmV4YW1wbGUgd2VyZQ0KPiAgICAgYWxzbyB0cmFuc2Zl cnJlZC48L2Rlc2M+DQo+ICAgPG9iamVjdD4NCj4gICAgIDxvYmpVUkk+dXJuOmlldGY6cGFyYW1z OnhtbDpuczpob3N0LTEuMDwvb2JqVVJJPg0KPiAgICAgPG9iaklEPm5zMS50ZXN0LmV4YW1wbGU8 L29iaklEPg0KPiAgICAgPG9iakluZm8geG1sbnM6aG9zdD0idXJuOmlldGY6cGFyYW1zOnhtbDpu czpob3N0LTEuMCI+DQo+ICAgICAgIDxob3N0Om5hbWU+bnMxLnRlc3QuZXhhbXBsZTwvaG9zdDpu YW1lPg0KPiAgICAgICA8aG9zdDpyb2lkPmhvc3Ryb2lkLTE8L2hvc3Q6cm9pZD4NCj4gICAgICAg PCEtLSAuLi4gLS0+DQo+ICAgICA8L29iakluZm8+DQo+ICAgPC9vYmplY3Q+DQo+IDwvbWVzc2Fn ZT4NCg0KR29vZCBpZGVhLCB0b28uLi4gWWVzLCBpbiBtYW55IGNhc2VzIHRoZSAicmVzb25wb25z ZSBmcmFtZSIgaXMgcHJldHR5IHVzZWxlc3MgaW4gc3VjaCBzaXR1YXRpb25zLCBzbyBpbmNsdXNp b24gb2YgYW4gImluZm8iIGZyYW1lIChvciBzcGVjaWZpY2FsbHksIHRoZSAiaW5mRGF0YSIgZWxl bWVudCwgcHJvYmFibHkpIHdvdWxkIHdvcmsgcXVpdGUgd2VsbCBoZXJlLi4NCg0KRXhjaXRpbmcg aWRlYXMgLSBJIG5lZWQgdG8gdGhpbmsgYW5kIGRpc2N1c3MgdGhvc2UgaW50ZXJuYWxseS4uLiEN Cg0KQWxleA0KDQoNCg==