Antoin, On Mon, May 28, 2018, at 22:40, Patrick Mevzek wrote: > > > On Mon, May 28, 2018, at 21:29, Antoin Verschuren wrote: > > Op 27 mei 2018, om 21:23 heeft Patrick Mevzek <p...@dotandco.com> het > > volgende geschreven: > > > > > This is covered I think in ICANN world by section 1.4.2 of the whois > > > specification: > > > > > > "Additional data elements can be added at the end of the text format > > > outlined below.” > > > > Ah yes, let’s take the solution of "we can put everything in one non- > > parseble TXT record like DNS can do too if we fail proper design and > > really want to” ;-) > > Sorry for the sarcasm Patrick, but that one was a too open goal ;-) > > I am not sure to see where in the text it says that formatted content is > forbidden, can you pinpoint it to me? > > Also, I fail to see how any EPP extension would have any impact here > (in the sense that: you can change what is displayed in whois > irrespective to what happens on the EPP channel).
In your quote you missed the other part which is basically: all domain names are not under ICANN policies. So for all other TLDs currently can you let me know which protocol limitations currently forbid registry to add formatted content in their whois or, let us say just decide to implement RDAP to start with? Do you really think there are almost none because of protocol limitations, especially in the EPP channel, or maybe for other reasons? -- Patrick Mevzek _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
