Re: New Version Notification for draft-brown-epp-fees-01.txt

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============5222121624491587119==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="pMWe5Lwg8w824cwn9B8qAlWTKTdhrdgXe"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--pMWe5Lwg8w824cwn9B8qAlWTKTdhrdgXe
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 08/05/2014 17:07, Pat Moroney wrote:
> Hi Jens,
>=20
> I like the optional type attribute being added to the <fee:cd> as well
> as required on the <fee:create> if it was set.
> Especially if that optional description attribute is added to the
> <fee:fee> element as well, which was hinted at in Gavin's email about
> the new draft.
>=20
> He had the following example:
> S:         <fee:cd
> S:           xmlns:fee=3D"urn:ietf:params:xml:ns:fee-0.5">
>=20
> S:           <fee:fee description=3D"Application Fee">5.00</fee:fee>
> S:           <fee:fee description=3D"Registration Fee">5.00</fee:fee>
> S:         </fee:cd>
>=20
> That, combined with the type attribute, allows a lot of flexability for=

> registries.
> For example, Donuts, if they used this extension, could then return the=

> following for a premium domain during their Early Access Period day 2:
>=20
> S:         <fee:cd
> S:           xmlns:fee=3D"urn:ietf:params:xml:ns:fee-0.5" type=3D"BBB+"=
>
> S:           <fee:name>example.com</fee:name>
> S:           <fee:currency>USD</fee:currency>
> S:           <fee:command>create</fee:command>
> S:           <fee:period unit=3D"y">1</fee:period>
> S:           <fee:fee description=3D"Early Access Fee">2500.00</fee:fee=
>
> S:           <fee:fee description=3D"Registration Fee">66.00</fee:fee>
> S:         </fee:cd>
>=20
> That allows a registrar to recognize that the domain is a premium as
> well as there being added fees, and differentiating what those fees are=
 for.

The current working draft includes a "description" attribute on the
<fee:fee> elements. If we're going to add additional syntax to describe
the domain itself, then I think that syntax should be added to the
<fee:name> element, like so:

S:  <fee:cd>
S:    <fee:name class=3D"premium">example.com</fee:name>
S:    <fee:currency>USD</fee:currency>
S:    <fee:command>create</fee:command>
S:    <fee:period unit=3D"y">1</fee:period>
S:    <fee:fee description=3D"Early Access Fee">2500.00</fee:fee>
S:    <fee:fee description=3D"Registration Fee">66.00</fee:fee>
S:  </fee:cd>

The above example uses "class" as the attribute name, but it could just
as easily be "category" or "type" or something similar. The value of the
attribute would be a token, which would presumably come from a set of
possible tokens that the server would provide to clients out-of-band.

Thoughts?

--=20
Gavin Brown
Chief Technology Officer
CentralNic Group plc (LSE:CNIC)
Innovative, Reliable and Flexible Registry Services
for ccTLD, gTLD and private domain name registries
https://www.centralnic.com/

CentralNic Group plc is a company registered in England and Wales with
company number 8576358. Registered Offices: 35-39 Moorgate, London,
EC2R 6AR.


--pMWe5Lwg8w824cwn9B8qAlWTKTdhrdgXe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlNrxRgACgkQ6H45IPkjtM4DkgCfagNZl2evUFfmUWIO8iERXgnr
ZHIAoIzaE/FnSxL3X5elFbfOGQuIWEYV
=/9uU
-----END PGP SIGNATURE-----

--pMWe5Lwg8w824cwn9B8qAlWTKTdhrdgXe--


--===============5222121624491587119==
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

--===============5222121624491587119==--