From nobody Mon Jul 7 13:08: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 B1A0A1A0515 for ; Mon, 7 Jul 2014 13:08:39 -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 vyVqvFON-DFn for ; Mon, 7 Jul 2014 13:08:34 -0700 (PDT) Received: from exprod6og110.obsmtp.com (exprod6og110.obsmtp.com [64.18.1.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D4851A0A81 for ; Mon, 7 Jul 2014 13:08:31 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob110.postini.com ([64.18.5.12]) with SMTP ID DSNKU7r+PmsGJ1DeVuctr1kckIbA5XwR2AW6@postini.com; Mon, 07 Jul 2014 13:08:33 PDT Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s67K8THx014250 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 7 Jul 2014 16:08:30 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 7 Jul 2014 16:08:29 -0400 From: "Gould, James" To: "Hollenbeck, Scott" , Marc Groeneweg , "eppext@ietf.org" Thread-Topic: [eppext] draft-ietf-eppext-keyrelay-00 Feedback Thread-Index: AQHPPTZwhTqnVBiC0UudESqSbZQK05rcFYQAgALzWICAAEbDgIBDSP2AgATA0QCAAAQzAIBRhb6AgABE/oCAHJurgA== Date: Mon, 7 Jul 2014 20:08:29 +0000 Message-ID: In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F494246E5@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.6.130613 x-originating-ip: [10.173.152.4] Content-Type: multipart/related; boundary="_004_CFE074EA62861jgouldverisigncom_"; type="multipart/alternative" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/crAcLfz6d4g87M1kq3qdsm7B9KE Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback 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, 07 Jul 2014 20:08:40 -0000 --_004_CFE074EA62861jgouldverisigncom_ Content-Type: multipart/alternative; boundary="_000_CFE074EA62861jgouldverisigncom_" --_000_CFE074EA62861jgouldverisigncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I concur. I believe that we=92re going to see many custom extensions that = will be registered as is, but that will be of general interest for collabor= ative rework as Standards Track drafts. The Key Relay draft would be a goo= d representative use case. -- JG [cid:40DFFFC3-8230-4E3C-98CA-5C4B9DCDAFD0] James Gould Principal Software Engineer jgould@verisign.com 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com From: , Scott > Date: Thursday, June 19, 2014 at 7:16 AM To: Marc Groeneweg >,= "eppext@ietf.org" > Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Marc Groeneweg Sent: Thursday, June 19, 2014 3:09 AM To: eppext@ietf.org Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback All, Thank you all for the given feedback. The authors have considered your feedback, and they make sense EPP protocol wise. When we started the EPPEXT WG, we promised we would document what is currently implemented, and that is the draft as is. The changes are significant to the current implementation at SIDN, our registrars and what's implemented in EPP clients already, so changing the draft would mean there would be no implementation. So we would like to stick to the Draft, and register this version as a SIDN version of the Key Relay. How about registering EPP-keyrelay as is for now with the draft as documentation, as it is an implemented extension, and progress with a new version of the draft aimed to be accepted as EPP RFC for a generic relay command? All your feedback is being considered as input for this new version, which we are discussing internally at this moment. [SAH] I see value in this. Documents that describe existing implementations= are often published as Informational RFCs, and the approach we=92re taking= should be able to accommodate the registration of non-standard extensions= . I=92m OK with the idea of using this document to explore that kind of reg= istration use case. Scott --_000_CFE074EA62861jgouldverisigncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <6930760EECE3FE4A94E0BD9073FC392D@verisign.com> Content-Transfer-Encoding: quoted-printable

I concur. I believe that we=92re going to see many custom extens= ions that will be registered as is, but that will be of general interest fo= r collaborative rework as Standards Track drafts. The Key Relay draft= would be a good representative use case.

James Gould

Principal Software E= ngineer

jgould@verisign.com

703-948-3271 (Office= )

12061 Bluemont Way

Reston, VA 20190

VerisignInc.com

From: <Hollenbeck>, Scott <= ;shollenbeck@verisign.com&g= t;
Date: Thursday, June 19, 2014 at 7:= 16 AM
To: Marc Groeneweg <Marc.Groeneweg@sidn.nl>, "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] draft-ietf-ep= pext-keyrelay-00 Feedback

From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Marc Groeneweg
Sent: Thursday, June 19, 2014 3:09 AM
To: eppext@ietf.org
Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback

All,

Thank you all for the given feedback. The authors have con= sidered your

feedback, and they make sense EPP protocol wise.<= span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: b= lack;">

When we started the EPPEXT WG, we promised we would document = what is

currently implemented, and that is the draft as is. The chang= es are

significant to the current implementation at SIDN, our regist= rars and

what's implemented in EPP clients already, so changing the dr= aft would

mean there would be no implementation. So we would like to st= ick to the

Draft, and register this version as a SIDN version of the Key= Relay.

How about registering EPP-keyrelay as is for now with the dra= ft as

documentation, as it is an implemented extension, and progres= s with a

new version of the draft aimed to be accepted as EPP RFC for = a

generic relay command? All your feedback is being considered = as input for

this new version, which we are discussing internally at this = moment.

[SAH] I see value in this. Documents that describe e= xisting implementations are often published as Informational RFCs, and the = approach we=92re taking should be able to accommodate the registration of non-standard extensions. I=92m OK with = the idea of using this document to explore that kind of registration use ca= se.

Scott

--_000_CFE074EA62861jgouldverisigncom_-- --_004_CFE074EA62861jgouldverisigncom_ Content-Type: image/png; name="3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[108].png" Content-Description: 3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[108].png Content-Disposition: inline; filename="3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[108].png"; size=4109; creation-date="Mon, 07 Jul 2014 20:08:29 GMT"; modification-date="Mon, 07 Jul 2014 20:08:29 GMT" Content-ID: <40DFFFC3-8230-4E3C-98CA-5C4B9DCDAFD0> 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_CFE074EA62861jgouldverisigncom_-- From nobody Tue Jul 8 06:13: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 95BD71B283E for ; Tue, 8 Jul 2014 06:13:31 -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 hrR9EzE7fjA6 for ; Tue, 8 Jul 2014 06:13:29 -0700 (PDT) Received: from exprod6og119.obsmtp.com (exprod6og119.obsmtp.com [64.18.1.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA1DD1B2837 for ; Tue, 8 Jul 2014 06:13:28 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob119.postini.com ([64.18.5.12]) with SMTP ID DSNKU7vueNcdrRwi3aGdxZAOlXYmiDJYLIQT@postini.com; Tue, 08 Jul 2014 06:13:28 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 s68DDR63031427 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 8 Jul 2014 09:13:27 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 8 Jul 2014 09:13:26 -0400 From: "Gould, James" To: "eppext@ietf.org" Thread-Topic: EPPEXT IETF Meeting Thread-Index: AQHPmq5buyFvc1uvMUKJG1fImSrhyQ== Date: Tue, 8 Jul 2014 13:13:25 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.6.130613 x-originating-ip: [10.173.152.4] Content-Type: multipart/mixed; boundary="_004_CFE16307628C6jgouldverisigncom_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/_rkAoXxAFo8iCNJx9UNN_wbKFb0 Subject: [eppext] EPPEXT IETF Meeting 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, 08 Jul 2014 13:13:31 -0000 --_004_CFE16307628C6jgouldverisigncom_ Content-Type: multipart/alternative; boundary="_000_CFE16307628C6jgouldverisigncom_" --_000_CFE16307628C6jgouldverisigncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Since we=92re not going to be meeting in Toronto I=92d like to try to bring= a couple of topics up for discussion again. I=92ve shared feedback on dra= ft-ietf-eppext-idnmap, draft-ietf-eppext-keyrelay, and draft-ietf-eppext-re= g. The authors of draft-ietf-eppext-reg and draft-ietf-eppext-launchphase = have incorporated mine and others feedback, but I think there are still som= e unresolved issues with draft-ietf-eppext-keyrelay and draft-ietf-eppext-i= dnmap as highlighted below: 1. draft-ietf-eppext-keyrelay =96 Marc Groeneweg responded that draft-ie= tf-eppext-keyrelay as drafted could be registered as a custom extension for= SIDN and the desire to progress draft-ietf-eppext-keyrelay with changes ba= sed on the list feedback. The authors are considering the feedback for a n= ew version of the draft that I=92m assuming would be worked on by the EPPEX= T WG. Discussion at an IETF meeting would have been useful to further disc= uss the options and the preferences of the authors. 2. draft-ietf-eppext-idnmap =96 Francisco and I have been going back and= forth on support for both a language and the existing table model. We hav= e a custom IDN Language Tag extension that takes language as input, so it= =92s important to me that language is explicitly supported. Discussion at = an IETF meeting would have been useful to discuss the various models and ap= proaches to use draft-ietf-eppext-idnmap for the registration of IDN domain= names across the registries. I noticed that there was no on-list call for meeting agenda items. It might= be helpful to meet if we don=92t make on-list progress in the near future. -- JG [cid:E1D0E96A-9490-4C17-9B94-4B4B5A58C14C] James Gould Principal Software Engineer jgould@verisign.com 703-948-3271 (Office) 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_CFE16307628C6jgouldverisigncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable

Since we=92re no= t going to be meeting in Toronto I=92d like to try to bring a couple of top= ics up for discussion again. I=92ve shared feedback on draf= t-ietf-eppext-idnmap, draft-ietf-eppext-keyrelay, and draft-ietf-eppex= t-reg. The authors of draft-ietf-eppext-reg and draft-ietf-eppext-laun= chphase have incorporated mine and others feedback, but I th= ink there are still some unresolved issues with draft-ietf-eppext-keyr= elay and draft-ietf-eppext-idnmap as highlighted below:

draft-ietf-eppe= xt-keyrelay =96 Marc Groeneweg responded that draft-ietf-eppext-keyrel= ay as drafted could be registered as a custom extension for SIDN and the de= sire to progress draft-ietf-eppext-keyrelay with changes based on the list feedback. The authors are considering= the feedback for a new version of the draft that I=92m assuming would be w= orked on by the EPPEXT WG. Discussion at an IETF meeting would have b= een useful to further discuss the options and the preferences of the authors.
draft-ietf-eppext-idnmap =96= Francisco and I have been going back and forth on support for both a langu= age and the existing table model. We have a custom IDN Language Tag e= xtension that takes language as input, so it=92s important to me that language is explicitly supported. &n= bsp;Discussion at an IETF meeting would have been useful to discuss the var= ious models and approaches to use draft-ietf-eppext-idnmap for the registra= tion of IDN domain names across the registries.

I noticed that t= here was no on-list call for meeting agenda items. It might be helpful to m= eet if we don=92t make on-list progress in the near future.

= James Gould

= Principal Software Engineer

<= a href=3D"mailto:jgould@verisign.com">jgould@verisign.com

= 703-948-3271 (Office)

= 12061 Bluemont Way

= Reston, VA 20190

= VerisignInc.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_CFE16307628C6jgouldverisigncom_-- --_004_CFE16307628C6jgouldverisigncom_ Content-Type: image/png; name="3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[109].png" Content-Description: 3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[109].png Content-Disposition: attachment; filename="3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[109].png"; size=4109; creation-date="Tue, 08 Jul 2014 13:13:25 GMT"; modification-date="Tue, 08 Jul 2014 13:13:25 GMT" Content-ID: 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_CFE16307628C6jgouldverisigncom_-- From nobody Wed Jul 9 03:54: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 D013C1A03FD for ; Wed, 9 Jul 2014 03:54:40 -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 HsKw5cfxhs98 for ; Wed, 9 Jul 2014 03:54:36 -0700 (PDT) Received: from exprod6og111.obsmtp.com (exprod6og111.obsmtp.com [64.18.1.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9E341A03FB for ; Wed, 9 Jul 2014 03:54:32 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob111.postini.com ([64.18.5.12]) with SMTP ID DSNKU70fZ4ztCwfN3hyT8PThoqcO6+ChysEF@postini.com; Wed, 09 Jul 2014 03:54:36 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 s69AsUbK024006 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Jul 2014 06:54:31 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 9 Jul 2014 06:54:30 -0400 From: "Hollenbeck, Scott" To: "Gould, James" , Marc Groeneweg , "eppext@ietf.org" Thread-Topic: [eppext] draft-ietf-eppext-keyrelay-00 Feedback Thread-Index: AQHPPTZwhTqnVBiC0UudESqSbZQK05rcFYQAgALzWICAAEbDgIBDSP2AgATA0QCAAAQzAIBRhb6AgABE/oCAHJurgIACiLuQ Date: Wed, 9 Jul 2014 10:54:29 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F49448CE9@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F494246E5@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: 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_831693C2CDA2E849A7D7A712B24E257F49448CE9BRN1WNEXMBX01vc_"; type="multipart/alternative" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/E2KtnOqQGs2GkWVP9P6Kkfwbxzc Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback 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, 09 Jul 2014 10:54:41 -0000 --_004_831693C2CDA2E849A7D7A712B24E257F49448CE9BRN1WNEXMBX01vc_ Content-Type: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F49448CE9BRN1WNEXMBX01vc_" --_000_831693C2CDA2E849A7D7A712B24E257F49448CE9BRN1WNEXMBX01vc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable WG chairs: can we do this? Our charter doesn't specifically identify the in= tended status of the in-charter extensions. Scott From: Gould, James Sent: Monday, July 07, 2014 4:08 PM To: Hollenbeck, Scott; Marc Groeneweg; eppext@ietf.org Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback I concur. I believe that we're going to see many custom extensions that wi= ll be registered as is, but that will be of general interest for collaborat= ive rework as Standards Track drafts. The Key Relay draft would be a good = representative use case. -- JG [cid:image001.png@01CF9B42.A50F3DA0] James Gould Principal Software Engineer jgould@verisign.com 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com From: , Scott > Date: Thursday, June 19, 2014 at 7:16 AM To: Marc Groeneweg >,= "eppext@ietf.org" > Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Marc Groeneweg Sent: Thursday, June 19, 2014 3:09 AM To: eppext@ietf.org Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback All, Thank you all for the given feedback. The authors have considered your feedback, and they make sense EPP protocol wise. When we started the EPPEXT WG, we promised we would document what is currently implemented, and that is the draft as is. The changes are significant to the current implementation at SIDN, our registrars and what's implemented in EPP clients already, so changing the draft would mean there would be no implementation. So we would like to stick to the Draft, and register this version as a SIDN version of the Key Relay. How about registering EPP-keyrelay as is for now with the draft as documentation, as it is an implemented extension, and progress with a new version of the draft aimed to be accepted as EPP RFC for a generic relay command? All your feedback is being considered as input for this new version, which we are discussing internally at this moment. [SAH] I see value in this. Documents that describe existing implementations= are often published as Informational RFCs, and the approach we're taking = should be able to accommodate the registration of non-standard extensions. = I'm OK with the idea of using this document to explore that kind of registr= ation use case. Scott --_000_831693C2CDA2E849A7D7A712B24E257F49448CE9BRN1WNEXMBX01vc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

WG chairs: can we do this? Our charter doe= sn’t specifically identify the intended status of the in-charter exte= nsions.

Scott<= o:p>

From: Gould, J= ames
Sent: Monday, July 07, 2014 4:08 PM
To: Hollenbeck, Scott; Marc Groeneweg; eppext@ietf.org
Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback

I concur. I believe t= hat we’re going to see many custom extensions that will be registered= as is, but that will be of general interest for collaborative rework as Standards Track drafts. The Key Relay draft would be a good repre= sentative use case.

James Gould

Principal Software Engineer<= /p>

jgould@verisign.c= om

703-948-3271 (Office)

12061 Bluemont Way

Reston, VA 20190

VerisignInc.com

From: <Hollenbeck>, Scott <shollenbeck@verisign.com>
Date: Thursday, June 19, 2014 at 7:16 AM
To: Marc Groeneweg <Mar= c.Groeneweg@sidn.nl>, "eppex= t@ietf.org" <eppext@ietf.org= >
Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback

From: EppExt [mailto:e= ppext-bounces@ietf.org] On Behalf Of Marc Groeneweg
Sent: Thursday, June 19, 2014 3:09 AM
To: eppext@ietf.org
Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback<= span style=3D"color:black">

=

All,

Thank you all for the given feedback. The authors have con= sidered your

feedback, and they make sense EPP protocol wise.<= span style=3D"color:black">

When we started the EPPEXT WG, we promised we would document = what is

currently implemented, and that is the draft as is. The chang= es are

significant to the current implementation at SIDN, our regist= rars and

what's implemented in EPP clients already, so changing the dr= aft would

mean there would be no implementation. So we would like to st= ick to the

Draft, and register this version as a SIDN version of the Key= Relay.

How about registering EPP-keyrelay as is for now with the dra= ft as

documentation, as it is an implemented extension, and progres= s with a

new version of the draft aimed to be accepted as EPP RFC for = a

generic relay command? All your feedback is being considered = as input for

this new version, which we are discussing internally at this = moment.

=

[SAH] I see value in this. Documents that = describe existing implementations are often published as Informational RFCs= , and the approach we’re taking should be able to accommodate the registration of non-standard extensions. I’m OK with the idea of= using this document to explore that kind of registration use case.<= span style=3D"color:black">

<= o:p>

Scott

--_000_831693C2CDA2E849A7D7A712B24E257F49448CE9BRN1WNEXMBX01vc_-- --_004_831693C2CDA2E849A7D7A712B24E257F49448CE9BRN1WNEXMBX01vc_ Content-Type: image/png; name="image001.png" Content-Description: image001.png Content-Disposition: inline; filename="image001.png"; size=4109; creation-date="Wed, 09 Jul 2014 10:54:29 GMT"; modification-date="Wed, 09 Jul 2014 10:54:29 GMT" Content-ID: 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_831693C2CDA2E849A7D7A712B24E257F49448CE9BRN1WNEXMBX01vc_-- From nobody Wed Jul 9 06:14:25 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 BFBFD1A050E for ; Wed, 9 Jul 2014 06:14:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.557 X-Spam-Level: X-Spam-Status: No, score=-0.557 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, RP_MATCHES_RCVD=-0.651, 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 pjZDFgzJWqTF for ; Wed, 9 Jul 2014 06:14:22 -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 B4EBC1A03E4 for ; Wed, 9 Jul 2014 06:14:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=SacbV180YFveNgKwCJek4DnoJJzG0I3o7AUvs1kV42I=; b=XQkV9bFDD/35OfDjDiOjVtOMG4jAKNgO91VZOFByMRL6Xb+1X6rWS+fBNCTB4Yt5mi9zHHZDB44fcYGQ0aV9uKvNef2IWFQER/DryWscRNnFzggubIrJFWnmHYCHYGTNbOjgonD0Qehek1dWTkK6Ht3EnNgxhl0Zkvg5se8bYMM= Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by arn2-kamx.sidn.nl with ESMTP id s69DEKVM014603-s69DEKVO014603 (version=TLSv1.0 cipher=AES128-SHA bits=128 verify=CAFAIL) for ; Wed, 9 Jul 2014 15:14:20 +0200 Received: from [94.198.152.216] (94.198.152.216) by kahubcasn02.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 9 Jul 2014 15:14:15 +0200 Message-ID: <53BD4026.1070809@sidn.nl> Date: Wed, 9 Jul 2014 15:14:14 +0200 From: Antoin Verschuren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: References: <831693C2CDA2E849A7D7A712B24E257F494246E5@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F49448CE9@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49448CE9@BRN1WNEXMBX01.vcorp.ad.vrsn.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-Originating-IP: [94.198.152.216] Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/8MIeK99ApZIDz4m_mFRrjduhzl8 Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback 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, 09 Jul 2014 13:14:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 op 09-07-14 12:54, Hollenbeck, Scott schreef: > WG chairs: can we do this? Our charter doesn�t specifically > identify the intended status of the in-charter extensions. [hat on] Our charter does not specify that documentation for an extension needs to have a status, as that was left as the topic for discussion for the process in the registry document. The charter talks about registration of extensions, not standards. The milestones seem to suggest that the 3 example extensions need to be documented by the IETF though, be it that the status of the IETF document is not defined in the milestones, they can also be experimental. That seems to suggest that "documentation required" in the registry document is not sufficient to meet our charter, and that "RFC required" is the minimum for at least the 3 example extensions. The charter also says that "the problem of non-standard extension duplication by multiple operators" is the problem we're trying to solve with the registry. I would say keep it simple. It's a standard, or it's not, it's implemented, or it's not. I would advise the WG to review the registry document in WGLC with these specific requirements in mind. There is a possibility to not register the extensions mentioned in our charter due to a lack of standardization, but standardizing the extensions or at least documenting them in the IETF is in our charter. [/hat on] [no hat] The wish to harmonize extensions is a specific wish from the registrar community, that I don't see well represented in the EPPEXT WG. The specific wish to be able to register a proprietary extension came from some in the registry community as an argument against "RFC required". I may have a suggestion around this: What if we allow proprietary extensions to be registered, but with the specific notion that it is a proprietary extension and not a standard? One way to do this is to say that when the "TLDs" field in the registry identifies specific TLD's, "documentation required" is sufficient, but when "ANY" or "Any" is used, it must be a standard and therefor "RFC required". Perhaps the words "ANY" or "Any" should be replaced by "STANDARD" or "Standard"? This way we accommodate inclusion in the registry for proprietary extensions, but we do meet our charter in trying to solve the non-standard extension duplication. Many registries will only implement the "standard" extensions, and will be aware that a proprietary extension may not be supported by all registrars so they loose market share. Mind though that it is not compulsory to register a proprietary extension. I personally feel registering a proprietary extension is a failure to meet market demand. [/no hat] - -- 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) iQEcBAEBAgAGBQJTvUAmAAoJEDqHrM883AgnzmUH/Aqe1DDfs5t0s0Zqk70DfG/M Sp9jhYQJkSz+ignqKXU/A+q3G4QZ39p34TV551eqBMBuqdVSq3nlMHTVrQj4xLdW rS2ZRiW0cRXQhf/Ei6DLj572yN4QusBIuPIdw//vuflC2xgKzslAyaBLrL577RHD Av7r/Lq9wtyvdYmBjJQ+x6y20TnnLuKDpGzYKXWaIWhReHQH6ODXmsSOu4Qjs+dL YdteEDj5DBtCrjZjsMPIi1nPEaXEwGhf/GnmH3Ye17HzHqqs7TAQ5dqw8r9+2bI8 lRuzBKgUy8BLheCHetcUvxEOmwA+zx1lVDQheBjcN7hEc+qWYD6n6saQuz1CG2E= =V1ur -----END PGP SIGNATURE----- From nobody Wed Jul 9 07:23:33 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 0F5521A03CE for ; Wed, 9 Jul 2014 07:23:30 -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 qcVayUSFuiSG for ; Wed, 9 Jul 2014 07:23:27 -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 14D521A064C for ; Wed, 9 Jul 2014 07:23:24 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob114.postini.com ([64.18.5.12]) with SMTP ID DSNKU71QXIVQKjlbxnxnWAQ0X1hpjDnNiZI/@postini.com; Wed, 09 Jul 2014 07:23:27 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 s69ENNiR030650 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Jul 2014 10:23:23 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 9 Jul 2014 10:23:02 -0400 From: "Gould, James" To: Antoin Verschuren , "eppext@ietf.org" Thread-Topic: [eppext] draft-ietf-eppext-keyrelay-00 Feedback Thread-Index: AQHPPTZwhTqnVBiC0UudESqSbZQK05rcFYQAgALzWICAAEbDgIBDSP2AgATA0QCAAAQzAIBRhb6AgABE/oCAHJurgIACiLuQgABrOwD//9BRAA== Date: Wed, 9 Jul 2014 14:23:21 +0000 Message-ID: In-Reply-To: <53BD4026.1070809@sidn.nl> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.6.130613 x-originating-ip: [10.173.152.4] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <5C4A2D4761F2664CB731AABD91D47227@verisign.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/YNHxfFxA_EpyZksFJIt3xbsZEHU Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback 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, 09 Jul 2014 14:23:30 -0000 Antoin, There may be extensions that are proprietary (not standard) and not specific to any one or a small set of TLD=B9s. Registries most likely have built platforms that support a pluggable set of TLD=B9s, where the extensions are applicable to the platform (or set of platforms), and may be used for most or all of the TLD=B9s on the platform. I believe most of the extensions will be classified as =B3Any=B2 even if they are proprietary= by not going through the IETF process. Actually, only a few have fully followed the RFC process, some have been posted as IETF drafts, and many more have been defined outside of the IETF. EPP makes it easy to create extensions to meet specific business needs that may not be applicable to a large set of TLD=B9s. I don=B9t view registering a proprietary extension a= s a failure to meet market demand, but as a reality of meeting different business models. As a co-author of an EPP extension RFC, as a co-author of an inflight EPP extension IETF draft, and as an author of many proprietary EPP extensions, I understand the tradeoffs of meeting specific business needs and collaborating with the community on a standard. I believe it is important for the proprietary extensions to get registered into the extension registry, with an adequate amount of documentation, to help identify overlap and open up the opportunity for consolidation. The Registry Operations Industry Alliance being discussed on the regops mailing list may be a good place to help with the consolidation. --=20 =20 JG =20 =20 James Gould Principal Software Engineer jgould@verisign.com =20 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com On 7/9/14, 9:14 AM, "Antoin Verschuren" wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >op 09-07-14 12:54, Hollenbeck, Scott schreef: >> WG chairs: can we do this? Our charter doesn=B9t specifically >> identify the intended status of the in-charter extensions. > >[hat on] >Our charter does not specify that documentation for an extension needs >to have a status, as that was left as the topic for discussion for the >process in the registry document. >The charter talks about registration of extensions, not standards. > >The milestones seem to suggest that the 3 example extensions need to be >documented by the IETF though, be it that the status of the IETF >document is not defined in the milestones, they can also be >experimental. That seems to suggest that "documentation required" in the >registry document is not sufficient to meet our charter, and that "RFC >required" is the minimum for at least the 3 example extensions. > >The charter also says that "the problem of non-standard extension >duplication by multiple operators" is the problem we're trying to solve >with the registry. I would say keep it simple. It's a standard, or it's >not, it's implemented, or it's not. > >I would advise the WG to review the registry document in WGLC with these >specific requirements in mind. >There is a possibility to not register the extensions mentioned in our >charter due to a lack of standardization, but standardizing the >extensions or at least documenting them in the IETF is in our charter. >[/hat on] > >[no hat] >The wish to harmonize extensions is a specific wish from the registrar >community, that I don't see well represented in the EPPEXT WG. > >The specific wish to be able to register a proprietary extension came >from some in the registry community as an argument against "RFC required". > >I may have a suggestion around this: >What if we allow proprietary extensions to be registered, but with the >specific notion that it is a proprietary extension and not a standard? > >One way to do this is to say that when the "TLDs" field in the registry >identifies specific TLD's, "documentation required" is sufficient, but >when "ANY" or "Any" is used, it must be a standard and therefor "RFC >required". Perhaps the words "ANY" or "Any" should be replaced by >"STANDARD" or "Standard"? > >This way we accommodate inclusion in the registry for proprietary >extensions, but we do meet our charter in trying to solve the >non-standard extension duplication. Many registries will only implement >the "standard" extensions, and will be aware that a proprietary >extension may not be supported by all registrars so they loose market >share. > >Mind though that it is not compulsory to register a proprietary >extension. I personally feel registering a proprietary extension is a >failure to meet market demand. >[/no hat] > > > > >- --=20 >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) > >iQEcBAEBAgAGBQJTvUAmAAoJEDqHrM883AgnzmUH/Aqe1DDfs5t0s0Zqk70DfG/M >Sp9jhYQJkSz+ignqKXU/A+q3G4QZ39p34TV551eqBMBuqdVSq3nlMHTVrQj4xLdW >rS2ZRiW0cRXQhf/Ei6DLj572yN4QusBIuPIdw//vuflC2xgKzslAyaBLrL577RHD >Av7r/Lq9wtyvdYmBjJQ+x6y20TnnLuKDpGzYKXWaIWhReHQH6ODXmsSOu4Qjs+dL >YdteEDj5DBtCrjZjsMPIi1nPEaXEwGhf/GnmH3Ye17HzHqqs7TAQ5dqw8r9+2bI8 >lRuzBKgUy8BLheCHetcUvxEOmwA+zx1lVDQheBjcN7hEc+qWYD6n6saQuz1CG2E=3D >=3DV1ur >-----END PGP SIGNATURE----- > >_______________________________________________ >EppExt mailing list >EppExt@ietf.org >https://www.ietf.org/mailman/listinfo/eppext From nobody Thu Jul 10 05:22: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 12DC81B28A6 for ; Thu, 10 Jul 2014 05:22:05 -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 da60f-e66BWg for ; Thu, 10 Jul 2014 05:22:02 -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 B2B561B28BC for ; Thu, 10 Jul 2014 05:21:48 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob115.postini.com ([64.18.5.12]) with SMTP ID DSNKU76FXBP81r8Pjd+wHR8X6SJQFpk5wJiL@postini.com; Thu, 10 Jul 2014 05:21:51 PDT Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s6ACLk7p010151 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 10 Jul 2014 08:21:46 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 10 Jul 2014 08:21:46 -0400 From: "Hollenbeck, Scott" To: Antoin Verschuren , "eppext@ietf.org" Thread-Topic: [eppext] draft-ietf-eppext-keyrelay-00 Feedback Thread-Index: AQHPPTZwhTqnVBiC0UudESqSbZQK05rcFYQAgALzWICAAEbDgIBDSP2AgATA0QCAAAQzAIBRhb6AgABE/oCAHJurgIACiLuQgABrOwCAAT2l0A== Date: Thu, 10 Jul 2014 12:21:45 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4944B43D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F494246E5@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F49448CE9@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <53BD4026.1070809@sidn.nl> In-Reply-To: <53BD4026.1070809@sidn.nl> 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/cPv2qSB_ftodUomIkHgT_NoGLBY Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback 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, 10 Jul 2014 12:22:05 -0000 > -----Original Message----- > From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Antoin > Verschuren > Sent: Wednesday, July 09, 2014 9:14 AM > To: eppext@ietf.org > Subject: Re: [eppext] draft-ietf-eppext-keyrelay-00 Feedback >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > op 09-07-14 12:54, Hollenbeck, Scott schreef: > > WG chairs: can we do this? Our charter doesn't specifically > > identify the intended status of the in-charter extensions. >=20 > [hat on] > Our charter does not specify that documentation for an extension needs > to have a status, as that was left as the topic for discussion for the > process in the registry document. > The charter talks about registration of extensions, not standards. >=20 > The milestones seem to suggest that the 3 example extensions need to be > documented by the IETF though, be it that the status of the IETF > document is not defined in the milestones, they can also be > experimental. That seems to suggest that "documentation required" in > the > registry document is not sufficient to meet our charter, and that "RFC > required" is the minimum for at least the 3 example extensions. I'd say just the opposite. The fact that our charter doesn't explicitly def= ine the intended status means that we have some flexibility. It may be that= the three we're considering are intended to be RFCs because we started wit= h documents that happened to be I-Ds, but I don't think that implies that e= very extension should have an RFC requirement - or that all RFCs need to be= on the Standards Track. Back to the document that's the subject of this message: We all need to tak= e another look at it if the idea is to document it as an as-is, information= al document that describes an existing implementation. It currently says "I= ntended status: Standards Track". This note from one of the authors: http://www.ietf.org/mail-archive/web/eppext/current/msg00117.html suggests that the intended status should be "Informational". We need to mak= e a decision and proceed accordingly. I would be OK with an Informational d= ocument as long as appropriate changes are made to reflect that status and = doing so would be consistent with our charter. Scott From nobody Fri Jul 18 15: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 E624D1A028A for ; Fri, 18 Jul 2014 15:16:42 -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 EI2Xuc_Omnp2 for ; Fri, 18 Jul 2014 15:16:39 -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 2C5BC1A02BA for ; Fri, 18 Jul 2014 15:16:26 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob115.postini.com ([64.18.5.12]) with SMTP ID DSNKU8mcus+g69MntKrtFffHYfL4OP3z5zoG@postini.com; Fri, 18 Jul 2014 15:16:27 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 s6IMGNw4021086 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 18 Jul 2014 18:16:23 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 18 Jul 2014 18:16:23 -0400 From: "Hollenbeck, Scott" To: "eppext@ietf.org" Thread-Topic: Working Group Last call for draft-ietf-eppext-reg Concluded Thread-Index: Ac+i1eg1Op3RptjHR6yzKbpCsBFj6w== Date: Fri, 18 Jul 2014 22:16:22 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F494606DB@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/JgotKYHaiwEME3X2kyrdXMk8l4A Subject: [eppext] Working Group Last call for draft-ietf-eppext-reg Concluded 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, 18 Jul 2014 22:16:43 -0000 The WG last call for eppext-reg-06 concluded last Friday, 11 July. I've got= -07 (with edits to address last call feedback) ready to go. What next? Scott From nobody Mon Jul 21 05:25:20 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 8C81B1B296F; Mon, 21 Jul 2014 05:25:18 -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 nEFY-JfAPMJ7; Mon, 21 Jul 2014 05:25:17 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 819B41B2C89; Mon, 21 Jul 2014 05:25:17 -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.1.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140721122517.2355.93294.idtracker@ietfa.amsl.com> Date: Mon, 21 Jul 2014 05:25:17 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/l1Gv7lGYggqRaWraEzYOpGDvYn8 Cc: eppext@ietf.org Subject: [eppext] I-D Action: draft-ietf-eppext-reg-07.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: Mon, 21 Jul 2014 12:25:18 -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-07.txt Pages : 11 Date : 2014-07-21 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-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-eppext-reg-07 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 Mon Jul 21 05:28: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 E2D5B1B2D93 for ; Mon, 21 Jul 2014 05:28: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 LqnRFNcWJq5C for ; Mon, 21 Jul 2014 05:28:39 -0700 (PDT) Received: from exprod6og111.obsmtp.com (exprod6og111.obsmtp.com [64.18.1.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BE681B2DC4 for ; Mon, 21 Jul 2014 05:28:39 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob111.postini.com ([64.18.5.12]) with SMTP ID DSNKU80HdrMvDWbSwBmEUWcRo3RflxzDo3D3@postini.com; Mon, 21 Jul 2014 05:28:39 PDT Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s6LCSc2u013718 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 21 Jul 2014 08:28:38 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 21 Jul 2014 08:28:37 -0400 From: "Hollenbeck, Scott" To: "eppext@ietf.org" Thread-Topic: [eppext] I-D Action: draft-ietf-eppext-reg-07.txt Thread-Index: AQHPpN7XrCkejboXekO2pi/v0dGqUpuqdJ5g Date: Mon, 21 Jul 2014 12:28:36 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F494630B1@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20140721122517.2355.93294.idtracker@ietfa.amsl.com> In-Reply-To: <20140721122517.2355.93294.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/d70zLqUM-vjlgzW5wo_PirAdYOU Subject: Re: [eppext] I-D Action: draft-ietf-eppext-reg-07.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, 21 Jul 2014 12:28:41 -0000 > -----Original Message----- > From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of internet- > drafts@ietf.org > Sent: Monday, July 21, 2014 8:25 AM > To: i-d-announce@ietf.org > Cc: eppext@ietf.org > Subject: [eppext] I-D Action: draft-ietf-eppext-reg-07.txt >=20 >=20 > 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. >=20 > Title : Extension Registry for the Extensible > Provisioning Protocol > Author : Scott Hollenbeck > Filename : draft-ietf-eppext-reg-07.txt > Pages : 11 > Date : 2014-07-21 This version includes changes made to address the comments received during = the last call period that ended on 11 July. Scott From nobody Mon Jul 21 14:32: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 38F3A1A030D; Mon, 21 Jul 2014 09:28:03 -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 LZAmHshE_Def; Mon, 21 Jul 2014 09:28:01 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D7F2A1A02DD; Mon, 21 Jul 2014 09:28:01 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: miek@google.com, marc.groeneweg@sidn.nl, rik.ribbers@sidn.nl, antoin.verschuren@sidn.nl X-Test-IDTracker: no X-IETF-IDTracker: 5.6.1.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140721162801.12461.33415.idtracker@ietfa.amsl.com> Date: Mon, 21 Jul 2014 09:28:01 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/-Y3IS4LRaOurmIFC0jUgEJqsTzU X-Mailman-Approved-At: Mon, 21 Jul 2014 14:32:21 -0700 Cc: antoin.verschuren@sidn.nl, presnick@qti.qualcomm.com, ipr-announce@ietf.org, eppext@ietf.org, barryleiba@computer.org, galvin@elistx.com Subject: [eppext] IPR Disclosure: Verisign Inc.'s Statement about IPR related to draft-ietf-eppext-keyrelay-00 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: Mon, 21 Jul 2014 16:28:03 -0000 Dear R. (Miek) Gieben, M. Groeneweg, Rik Ribbers, Antoin Verschuren: An IPR disclosure that pertains to your Internet-Draft entitled "Key Relay Mapping for the Extensible Provisioning Protocol" (draft-ietf-eppext-keyrelay) was submitted to the IETF Secretariat on 2014-07-21 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/2393/). The title of the IPR disclosure is "Verisign Inc.'s Statement about IPR related to draft-ietf-eppext- keyrelay-00.""); The IETF Secretariat From nobody Mon Jul 21 14:47:57 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 6AE091A001C for ; Mon, 21 Jul 2014 14:47: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 CFGu_hIGiLXf for ; Mon, 21 Jul 2014 14:47:53 -0700 (PDT) Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CDD71A007C for ; Mon, 21 Jul 2014 14:47:45 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob112.postini.com ([64.18.5.12]) with SMTP ID DSNKU82Kf9Y7Vyt8uDz3LthO/hux/SPj8bnH@postini.com; Mon, 21 Jul 2014 14:47:49 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 s6LLleMj009463 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 21 Jul 2014 17:47:40 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 21 Jul 2014 17:47:39 -0400 From: "Hollenbeck, Scott" To: "miek@google.com" , "marc.groeneweg@sidn.nl" , "rik.ribbers@sidn.nl" , "antoin.verschuren@sidn.nl" Thread-Topic: [eppext] IPR Disclosure: Verisign Inc.'s Statement about IPR related to draft-ietf-eppext-keyrelay-00 Thread-Index: AQHPpStDIBfNA+6cn0++ywLNFd9fuJurDdvg Date: Mon, 21 Jul 2014 21:47:39 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F49464369@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20140721162801.12461.33415.idtracker@ietfa.amsl.com> In-Reply-To: <20140721162801.12461.33415.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/Yt5Cevd4xe7Ms_vrXtcm8tqzBk0 Cc: "presnick@qti.qualcomm.com" , "antoin.verschuren@sidn.nl" , "eppext@ietf.org" , "barryleiba@computer.org" , "galvin@elistx.com" Subject: Re: [eppext] IPR Disclosure: Verisign Inc.'s Statement about IPR related to draft-ietf-eppext-keyrelay-00 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, 21 Jul 2014 21:47:55 -0000 (trimming recipients...) > -----Original Message----- > From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of IETF > Secretariat > Sent: Monday, July 21, 2014 12:28 PM > To: miek@google.com; marc.groeneweg@sidn.nl; rik.ribbers@sidn.nl; > antoin.verschuren@sidn.nl > Cc: antoin.verschuren@sidn.nl; presnick@qti.qualcomm.com; ipr- > announce@ietf.org; eppext@ietf.org; barryleiba@computer.org; > galvin@elistx.com > Subject: [eppext] IPR Disclosure: Verisign Inc.'s Statement about IPR > related to draft-ietf-eppext-keyrelay-00 >=20 >=20 > Dear R. (Miek) Gieben, M. Groeneweg, Rik Ribbers, Antoin Verschuren: >=20 > An IPR disclosure that pertains to your Internet-Draft entitled "Key > Relay > Mapping for the Extensible Provisioning Protocol" (draft-ietf-eppext- > keyrelay) > was submitted to the IETF Secretariat on 2014-07-21 and has been posted > on the > "IETF Page of Intellectual Property Rights Disclosures" > (https://datatracker.ietf.org/ipr/2393/). The title of the IPR > disclosure is > "Verisign Inc.'s Statement about IPR related to draft-ietf-eppext- > keyrelay-00.""); I recently became aware of the patent application described in the referenc= ed disclosure. I asked my employer to have this disclosure made in accordan= ce with RFC 3979. Scott From nobody Wed Jul 23 15:28: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 8239B1B2976 for ; Wed, 23 Jul 2014 15:28:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.093 X-Spam-Level: X-Spam-Status: No, score=0.093 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, RP_MATCHES_RCVD=-0.001, 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 wl9Axj2tXPkh for ; Wed, 23 Jul 2014 15:28:42 -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 856911B298E for ; Wed, 23 Jul 2014 15:28:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed; h=message-id:date:from:user-agent:mime-version:to:subject:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=DgM7IYQt3v9sro2rXpHlKzVE82uIZJAiy0O7JXTgKF0=; b=nGYfuI+efuTQh4TWCeh0kDHjI9Jsloh1cG/XkKwMRMI1LNnmFg97OFs5XocY4mYDTYPGDXROD+M34YpUGiUy4BbIA0MgUzFCkKilKuefYp434QG5vnwi3HMFSPmtD4X0zJzf5swYefTscUe4xkMjoIDaH0jngHAoSUuWe2YFl4k= Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by arn2-kamx.sidn.nl with ESMTP id s6NMSdMV016179-s6NMSdMX016179 (version=TLSv1.0 cipher=AES128-SHA bits=128 verify=CAFAIL) for ; Thu, 24 Jul 2014 00:28:39 +0200 Received: from [94.198.152.222] (94.198.152.222) by kahubcasn02.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.3.174.1; Thu, 24 Jul 2014 00:28:38 +0200 Message-ID: <53D03712.80809@sidn.nl> Date: Thu, 24 Jul 2014 00:28:34 +0200 From: Antoin Verschuren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: "eppext@ietf.org" X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [94.198.152.222] Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/jwoRIlO1AdSYEDmJdIygH35H-8Y Subject: [eppext] Conclusion for WGLC for draft-ietf-eppext-reg 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, 23 Jul 2014 22:28:43 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear WG, Working group last call for the registry document ended on 11 July. A new version of the document is available since 21 July with no comments on the mailing list. The chairs have reviewed version 07 of the document and believe all the remarks during WGLC have been properly incorporated in the document. The latest version of the document can be found here: https://datatracker.ietf.org/doc/draft-ietf-eppext-reg/ http://www.ietf.org/id/draft-ietf-eppext-reg-07.txt The chairs intend to send this version to the IESG this Friday 25 July. If you don't agree, please respond before Friday. - -- 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) iQEcBAEBAgAGBQJT0DcSAAoJEDqHrM883AgnTJMH/1ts6ph39tMs7zxqKAn6M/9e JidftQhKO842aGup5rLRThzZODsf9dkkU1fRmAdHNtZ/iQ/n8t7eZFb1raOr2CnP FWuvQ4UBEJpC6zCHfAchucTzNIuPZQOR62IC3zZoJivQQ5xGWzDh2DBCq9TpoQw9 FyYWh4Nglc3fAso0qo1xk5SfQYmVeaK4SwWTSKcuMdddZbiSyd6i/A+Ac+xuomLe ClurapUU3mGh+DtJhuCfzcAIelqOpUMQ6Ymvbs0ZQG/N1yEuvQ07+AcNuT8ffrBX niKCrgSWPhyDVPpaK4oUVfLGYJG8PnxxBmmBAvdg/YYWCQdE/HtUWNRRUN8BC/w= =4pw4 -----END PGP SIGNATURE-----