[rpp] Session / registrar mapping

[Ruth Trevor-Allen <[e-mail]>]

Hi all,

I've been working on a prototype RPP implementation for use with web
apps, and something I'd like us to be able to support is use cases
where a user is not necessarily exactly equivalent to a registrar. For
example, they might be a superuser with access to carry out operations
but no specific registrar ID, or an admin contact at multiple
registrars with a single login to a web app which maps to multiple EPP
logins. In order to offer a seamless experience to these users, it
would be nice to be able to specify a registrar ID when carrying out
operations where one is needed (for example domain: create), but it
would also be nice not to have to identify the registrar for
operations where it doesn't matter or can be inferred.

In particular, using EPP as a backend for apps like these, domain:
check is an example of an operation where the actual registrar ID
doesn't normally matter as long as the user has access to the TLD in
general, and having to identify the appropriate user in order to
submit the request can be undesirable overhead.

I don't know if this has implications for RPP design but wanted to
flag it - is anyone else having these issues?

Thanks,
Ruth