Re: EPP Domain Contacts

--===============1607473375695486743==
Content-Type: multipart/signed; boundary="Apple-Mail=_A5347BB8-6B46-4D9B-ADC8-C7C6E83B3500"; protocol="application/pgp-signature"; micalg=pgp-sha1


--Apple-Mail=_A5347BB8-6B46-4D9B-ADC8-C7C6E83B3500
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Without saying it being good or bad, as Frobbit that I work with is not =
a registrar to .AT, in general as a registrar I would like to be able to =
register billing contact as well (or rather, I would like to be able to =
fetch billing info). The downside with your policy is that if the domain =
is transferred from one registrar to another, the information on billing =
info must be moved out of band of the actual transfer (that is via the =
registry).

   Patrik

On 4 dec 2013, at 08:55, Alexander Mayrhofer =
<[email protected]> wrote:

> In the gTLD configuration of our Registry, we do require the contact =
type to be either  =84tech=93 or =84admin=93. We don=92t allow for =
=93billing=94 type contacts, since any billing goes via the registrar.
> =20
> Alex
> =20
> =20
> Von: provreg [mailto:[email protected]] Im Auftrag von Mike =
O'Connell
> Gesendet: Mittwoch, 04. Dezember 2013 06:13
> An: [email protected]
> Betreff: [provreg] EPP Domain Contacts
> =20
> All,
> =20
> I came across an issue the other day around Domain Contacts, =
specifically, the domain contact element contains an optional attribute =
'type' which can be one of [tech, billing, admin]. The problem here is =
that the attribute is optional with no assumed default.=20
> =20
> 	=95 Does anybody use the domain contact element without the =
'type' attribute?=20
> 	=95 Does anybody use a default value for the 'type' attribute =
when it is not provided?
> =20
> Apologies if this is a old/duplicate topic.
> =20
> Regards,
> =20
> Mike
> =20
> --
> =20
> If you don't know where you are going, any road will get you there.
> =20
> _______________________________________________
> provreg mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/provreg


--Apple-Mail=_A5347BB8-6B46-4D9B-ADC8-C7C6E83B3500
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSnuherMabGguI180RAvYSAJ0USaFJTNbC91JLHsz8ZPXjuK/uIQCcCjdk
qT2kkGS+GF0CYsSNHbvaIoI=
=e7zc
-----END PGP SIGNATURE-----

--Apple-Mail=_A5347BB8-6B46-4D9B-ADC8-C7C6E83B3500--

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

--===============1607473375695486743==--