Re: Merging RRP and Whois

Patrik,

I'd the impression that the proposal to change the application running on
port 43 was offered, and withdrawn upon strong non-hum, at the IETF49 BoF.
Randy's note seemed like clean-up for the benefit of those not present that
naive demultiplexing on port 43 was a non-starter.

A distinct issue is what an application running on some other port might
look like, which provided whois-like access to registration data in DNS
registries.

Yet another issue is what an application running on some other port might
look like, which provides ICANN-specified access to ICANN-specified data
in ICANN-specified DNS registries.

I distinguish between the 2nd and 3rd possible reasons for this incantation
of an ietf-whois list, because I know that ICANN-specified DNS registries
are contractually obligated to specific conditions, and national DNS registries
operate under distinct specific conditions. These differences may effect 
the level of (data security and data protection) service minimially, or
maximally available to the group working on whois.

A registry operator may seek to meet both the ICANN service requirements
where applicable, and other requirements where applicable.

Cheers,
Eric