Dear RIPE: Please don't encourage phishing

Valdis.Kletnieks at vt.edu Valdis.Kletnieks at vt.edu
Wed Feb 15 04:13:54 CST 2012


On Wed, 15 Feb 2012 10:44:38 +0100, Stephane Bortzmeyer said:

> Challenge taken.
>
> RFC 2277, "IETF Policy on Character Sets and Languages", section 3.1,
> "Protocols MUST be able to use the UTF-8 charset [...] Protocols MAY
> specify, in addition, how to use other charsets [something DNS does
> not do, so it must be UTF-8]"

(ooh.. an RFC lawyering fight. Goody goody, haven't had one in a while..  :)

That requires overlooking the minor detail that the DNS RFC predates that by quite
some time, and there's no combination of RFCs 2119 and 2277 that mandates
retrofitting grandfathered protocols by fiat.

It also requires overlooking the fact that 2277 is a BCP, not an Internet Standard, and
as such isn't itself binding, merely A Good Idea.

Nice try though. ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20120215/7af051c3/attachment.bin>


More information about the NANOG mailing list