Re: Fwd: New Version Notification for draft-brown-epp-fees-01.txt
Seth Goldman <[email protected]> Thu, 24 Apr 2014 19:48:27 -0400
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <CAAHh_-LxVJnu2fMS9mdsiztNdksu0PM83hrteb+VSk52X5V3qQ@mail.gmail.com> |
--===============1148091111184512415==
Content-Type: multipart/alternative; boundary=001a11c3a9204ec05204f7d27c51
--001a11c3a9204ec05204f7d27c51
Content-Type: text/plain; charset=ISO-8859-1
Hi Gavin,
I know this is very late in coming, but I do have a small piece of feedback
on the proposed extension. The <check> command in your draft can have
multiple <check> elements underneath the <extension> element, e.g.:
<?xml version="1.0" encoding="utf-8" standalone="no"?>
> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
> <command>
> <check>
> <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
> ...
> </domain:check>
> </check>
> <extension>
> <fee:check xmlns:fee="urn:ietf:params:xml:ns:fee-0.4">
> ...
> </fee:check>
> <fee:check xmlns:fee="urn:ietf:params:xml:ns:fee-0.4">
> ...
> </fee:check>
> <fee:check xmlns:fee="urn:ietf:params:xml:ns:fee-0.4">
> ...
> </fee:check>
> </extension>
> <clTRID>ABC-12345</clTRID>
> </command>
> </epp>
As far as I can tell, no other EPP extensions puts repeated types inside
the <extension> element (for either commands or responses). Instead, they
use a top-level container type, with repeated elements nested underneath
that, e.g.:
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<check>
<domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
...
</domain:check>
</check>
<extension>
<fee:check xmlns:fee="urn:ietf:params:xml:ns:fee-0.4">
<fee:domain>
<fee:name>example.tld</fee:name>
...
</fee:domain>
<fee:domain>
<fee:name>example.com</fee:name>
...
</fee:domain>
<fee:domain>
<fee:name>example.org</fee:name>
...
</fee:domain>
</fee:check>
</extension>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
I think if you modified your draft to follow this pattern, it would be more
in line with the convention used by other EPP extensions.
Cheers,
Seth
On Mon, Dec 9, 2013 at 1:18 PM, Gavin Brown <[email protected]>wrote:
> Changes since the last version:
>
> 1. Restore the <check> command extension; either <check> or <info>
> can be used.
>
> 2. added extension elements for <create>, <renew>, <transfer> and
> <update> so that the server can reject the command if the fee is
> incorrect.
>
> G.
>
> -------- Original Message --------
> Subject: New Version Notification for draft-brown-epp-fees-01.txt
> Date: Mon, 09 Dec 2013 09:58:47 -0800
> From: [email protected]
> To: Gavin Brown <[email protected]>
>
>
> A new version of I-D, draft-brown-epp-fees-01.txt
> has been successfully submitted by Gavin Brown and posted to the
> IETF repository.
>
> Filename: draft-brown-epp-fees
> Revision: 01
> Title: Registry Fee Extension for the Extensible Provisioning
> Protocol
> (EPP)
> Creation date: 2013-12-09
> Group: Individual Submission
> Number of pages: 27
> URL:
> http://www.ietf.org/internet-drafts/draft-brown-epp-fees-01.txt
> Status: http://datatracker.ietf.org/doc/draft-brown-epp-fees
> Htmlized: http://tools.ietf.org/html/draft-brown-epp-fees-01
> Diff: http://www.ietf.org/rfcdiff?url2=draft-brown-epp-fees-01
>
> Abstract:
> This document describes an Extensible Provisioning Protocol (EPP)
> extension mapping for registry fees.
>
>
>
>
>
> 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.
>
> The IETF Secretariat
>
>
> --
> 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.
>
>
> _______________________________________________
> provreg mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/provreg
>
--001a11c3a9204ec05204f7d27c51
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Gavin,<div><br></div><div>I know this is very late in c=
oming, but I do have a small piece of feedback on the proposed extension. T=
he <check> command in your draft can have multiple <font face=3D"cour=
ier new, monospace"><check></font>=A0elements underneath the <font fa=
ce=3D"courier new, monospace"><extension></font>=A0element, e.g.:</di=
v>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex"><font face=3D"courier new, monospace"><?=
xml version=3D"1.0" encoding=3D"utf-8" standalone=3D&qu=
ot;no"?><br>
</font><font face=3D"courier new, monospace">=A0 <epp xmlns=3D"urn:=
ietf:params:xml:ns:epp-1.0"><br></font><font face=3D"courier new, m=
onospace">=A0 <command><br></font><font face=3D"courier new, monospac=
e">=A0 =A0 <check><br>
</font><font face=3D"courier new, monospace">=A0 =A0 =A0 <domain:check x=
mlns:domain=3D"urn:ietf:params:xml:ns:domain-1.0"><br></font><=
font face=3D"courier new, monospace">=A0 =A0 =A0 ...<br></font><font face=
=3D"courier new, monospace">=A0 =A0 =A0 </domain:check><br>
</font><font face=3D"courier new, monospace">=A0 =A0 </check><br></fo=
nt><font face=3D"courier new, monospace">=A0 =A0 <extension><br></fon=
t><font face=3D"courier new, monospace">=A0 =A0 =A0 <fee:check=A0xmlns:f=
ee=3D"urn:ietf:params:xml:ns:fee-0.4"><br>
</font><font face=3D"courier new, monospace">=A0 =A0 =A0 ...<br></font><spa=
n style=3D"font-family:'courier new',monospace">=A0 =A0 =A0 </fe=
e:check><br></span><font face=3D"courier new, monospace">=A0 =A0 =A0 <=
;fee:check=A0xmlns:fee=3D"urn:ietf:params:xml:ns:fee-0.4"><br>
</font><font face=3D"courier new, monospace">=A0 =A0 =A0 ...<br></font><spa=
n style=3D"font-family:'courier new',monospace">=A0 =A0 =A0 </fe=
e:check><br></span><font face=3D"courier new, monospace">=A0 =A0 =A0 <=
;fee:check=A0xmlns:fee=3D"urn:ietf:params:xml:ns:fee-0.4"><br>
</font><font face=3D"courier new, monospace">=A0 =A0 =A0 ...<br></font><spa=
n style=3D"font-family:'courier new',monospace">=A0 =A0 =A0 </fe=
e:check><br></span><span style=3D"font-family:'courier new',mono=
space">=A0 =A0 </extension><br>
</span><font face=3D"courier new, monospace">=A0 =A0 <clTRID>ABC-1234=
5</clTRID><br></font><font face=3D"courier new, monospace">=A0 </c=
ommand><br></font><font face=3D"courier new, monospace"></epp></fo=
nt></blockquote>
<div><div><div><br></div></div></div><div>As far as I can tell, no other EP=
P extensions puts repeated types inside the <font face=3D"courier new, mono=
space"><extension></font>=A0element (for either commands or responses=
). Instead, they use a top-level container=A0type, with repeated elements n=
ested underneath that, e.g.:</div>
<div><br></div><div><font face=3D"courier new, monospace"><?xml version=
=3D"1.0" encoding=3D"utf-8" standalone=3D"no"=
?><br></font><font face=3D"courier new, monospace">=A0 <epp xmlns=3D&=
quot;urn:ietf:params:xml:ns:epp-1.0"><br>
</font><font face=3D"courier new, monospace">=A0 <command><br></font>=
<font face=3D"courier new, monospace">=A0 =A0 <check><br></font><font=
face=3D"courier new, monospace">=A0 =A0 =A0 <domain:check xmlns:domain=
=3D"urn:ietf:params:xml:ns:domain-1.0"><br>
</font><font face=3D"courier new, monospace">=A0 =A0 =A0 ...<br></font><fon=
t face=3D"courier new, monospace">=A0 =A0 =A0 </domain:check><br></fo=
nt><font face=3D"courier new, monospace">=A0 =A0 </check><br></font><=
font face=3D"courier new, monospace">=A0 =A0 <extension><br>
</font><font face=3D"courier new, monospace">=A0 =A0 =A0 <fee:check=A0xm=
lns:fee=3D"urn:ietf:params:xml:ns:fee-0.4"><br></font><font fa=
ce=3D"courier new, monospace">=A0 =A0 =A0 =A0 <fee:domain></font></di=
v><div><div><font face=3D"courier new, monospace">=A0 =A0 =A0 =A0 =A0 <f=
ee:name>example.tld</fee:name></font></div>
<div><font face=3D"courier new, monospace">=A0 =A0 =A0 =A0 =A0 ...</font></=
div><span style=3D"font-family:'courier new',monospace">=A0 =A0 =A0=
=A0 </fee:domain></span></div><div><div><font face=3D"courier new, m=
onospace">=A0 =A0 =A0 =A0 <fee:domain></font></div>
<div><div><font face=3D"courier new, monospace">=A0 =A0 =A0 =A0 =A0 <fee=
:name><a href=3D"http://example.com">example.com</a></fee:name></f=
ont></div><div><font face=3D"courier new, monospace">=A0 =A0 =A0 =A0 =A0 ..=
.</font></div><span style=3D"font-family:'courier new',monospace">=
=A0 =A0 =A0 =A0 </fee:domain></span><br style=3D"font-family:'cou=
rier new',monospace">
</div><div><div><font face=3D"courier new, monospace">=A0 =A0 =A0 =A0 <f=
ee:domain></font></div><div><div><font face=3D"courier new, monospace">=
=A0 =A0 =A0 =A0 =A0 <fee:name><a href=3D"http://example.org">example.=
org</a></fee:name></font></div>
<div><font face=3D"courier new, monospace">=A0 =A0 =A0 =A0 =A0 ...</font></=
div><span style=3D"font-family:'courier new',monospace">=A0 =A0 =A0=
=A0 </fee:domain></span></div><span style=3D"font-family:'courie=
r new',monospace"></span></div>
<span style=3D"font-family:'courier new',monospace">=A0 =A0 =A0 <=
;/fee:check><br></span><span style=3D"font-family:'courier new',=
monospace">=A0 =A0 </extension><br></span><font face=3D"courier new, =
monospace">=A0 =A0 <clTRID>ABC-12345</clTRID><br>
</font><font face=3D"courier new, monospace">=A0 </command><br></font=
><font face=3D"courier new, monospace"></epp></font><br></div><div><b=
r></div><div>I think if you modified your draft to follow this pattern, it =
would be more in line with the convention used by other EPP extensions.</di=
v>
<div><br></div><div>Cheers,</div><div>Seth</div></div><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Mon, Dec 9, 2013 at 1:18 PM, Ga=
vin Brown <span dir=3D"ltr"><<a href=3D"mailto:[email protected]=
m" target=3D"_blank">[email protected]</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Changes since the last version:<br>
<br>
=A0 =A01. =A0Restore the <check> command extension; either <check&=
gt; or <info><br>
=A0 =A0 =A0 =A0can be used.<br>
<br>
=A0 =A02. =A0added extension elements for <create>, <renew>, &l=
t;transfer> and<br>
=A0 =A0 =A0 =A0<update> so that the server can reject the command if =
the fee is<br>
=A0 =A0 =A0 =A0incorrect.<br>
<br>
G.<br>
<br>
-------- Original Message --------<br>
Subject: New Version Notification for draft-brown-epp-fees-01.txt<br>
Date: Mon, 09 Dec 2013 09:58:47 -0800<br>
From: <a href=3D"mailto:[email protected]">[email protected]<=
/a><br>
To: Gavin Brown <<a href=3D"mailto:[email protected]">gavin.bro=
[email protected]</a>><br>
<br>
<br>
A new version of I-D, draft-brown-epp-fees-01.txt<br>
has been successfully submitted by Gavin Brown and posted to the<br>
IETF repository.<br>
<br>
Filename: =A0 =A0 =A0 =A0draft-brown-epp-fees<br>
Revision: =A0 =A0 =A0 =A001<br>
Title: =A0 =A0 =A0 =A0 =A0 Registry Fee Extension for the Extensible Provis=
ioning Protocol<br>
(EPP)<br>
Creation date: =A0 2013-12-09<br>
Group: =A0 =A0 =A0 =A0 =A0 Individual Submission<br>
Number of pages: 27<br>
URL:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-brown-epp-fees-01.txt"=
target=3D"_blank">http://www.ietf.org/internet-drafts/draft-brown-epp-fees=
-01.txt</a><br>
Status: =A0 =A0 =A0 =A0 =A0<a href=3D"http://datatracker.ietf.org/doc/draft=
-brown-epp-fees" target=3D"_blank">http://datatracker.ietf.org/doc/draft-br=
own-epp-fees</a><br>
Htmlized: =A0 =A0 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-brown-=
epp-fees-01" target=3D"_blank">http://tools.ietf.org/html/draft-brown-epp-f=
ees-01</a><br>
Diff: =A0 =A0 =A0 =A0 =A0 =A0<a href=3D"http://www.ietf.org/rfcdiff?url2=3D=
draft-brown-epp-fees-01" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=
=3Ddraft-brown-epp-fees-01</a><br>
<br>
Abstract:<br>
=A0 =A0This document describes an Extensible Provisioning Protocol (EPP)<br=
>
=A0 =A0extension mapping for registry fees.<br>
<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
<br>
--<br>
Gavin Brown<br>
Chief Technology Officer<br>
CentralNic Group plc (LSE:CNIC)<br>
Innovative, Reliable and Flexible Registry Services<br>
for ccTLD, gTLD and private domain name registries<br>
<a href=3D"https://www.centralnic.com/" target=3D"_blank">https://www.centr=
alnic.com/</a><br>
<br>
CentralNic Group plc is a company registered in England and Wales with<br>
company number 8576358. Registered Offices: 35-39 Moorgate, London,<br>
EC2R 6AR.<br>
<br>
<br>
_______________________________________________<br>
provreg mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/provreg" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/provreg</a><br>
</blockquote></div><br></div>
--001a11c3a9204ec05204f7d27c51--
--===============1148091111184512415==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg
--===============1148091111184512415==--