Re: Registry lock - two-factor or intervention

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 19-09-13 11:22, Michele Neylon - Blacknight schreef:

> This is not the general case, so your statement is biased.
> 
>> So is your reaction :)

Touche. :-).
Just wanted to state that ICANN gTLD's are not the only norm. This is
an IETF mailinglist. The IETF create standards, not ICANN contracts.

> The role of the registrar is to offload administrative burden of
> the registry, the registrar acts as an administrative agent for
> the registrant.
> 
>> Wow! That's actually incredibly offensive to registrars.

Perhaps I'm just not a native speaker, and did not find a better term
than burden, where I meant distribute administrative tasks to market
players that are far better in communicating with end-customers.

>> So any time there are *any* issues with *any* domains of any kind
>> I can just send all the registrants, users and $random 3rd
>> parties directly to the registry?

I think it's the misunderstanding of the term "registrar" that has led
and still leads to these strong statements.
There are indeed a lot of entities that act as registrar in one of
their roles that do a lot more than just that. They also act as
dns-operator as a service to their customer, offer legal services, do
website hosting, are a CA, or offer much more service to their
customer, and do that well.
But these extra services are not part of the pure registrar role in
the model, as there are entities that act as registrar that do not
offer these services, and it's important to clearly separate these
roles when we need to come up with a clear model to base assumptions on.
These entities are service providers, and one of their roles is acting
as a registrar for those of their customers that are registrants.
(They may have other customers that are not registrants). Registrar
refers to the role, not to the entity.
By administrative agent, I mean a registrar is responsible for all
administrative, legal and financial communication and transactions
between registrant and registry regarding the registration of a
domain. The registrar represents the registry towards the registrant,
and represents the registrant towards the registry.


- -- 
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: [email protected]
XMPP: [email protected]
HTTP://www.sidn.nl/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJSOu9vAAoJEDqHrM883AgneqcH/3L3prtNQxfn1YwPb4pCCUs0
2v57k6bOlhvZKEPk0wDN6YzG/DkyAH8y6E5yqGuUp6esi2r3PH/hitdJ1HnxdDo7
0CKCUci9QFnGu3cwn/tBivm9e2VJ9ExOD0TwNGuVLEhNKmjX+IyN4viE17m6obzw
rz0c/1fIYZYmoKfCSrVd1FchG0aWb9c49lY3VKQMItdkRBjogjz5U9SAezpVyCsU
BcD0HXwGlwqrnlGi6JGUHzz3PH3LXXSXVxf7gLWHOL7yF5ocK6p5XRH0gCS01ipB
+8z3ombUQ7qoF4ymjAQDLSITrSHlRtXObxMkFE9xbsue/tzBzPidA9bhjvIq+Rw=
=X4fI
-----END PGP SIGNATURE-----
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg