Dear RIPE: Please don't encourage phishing
Robert E. Seastrom
rs at seastrom.com
Wed Feb 15 05:46:40 CST 2012
Valdis.Kletnieks at vt.edu writes:
> 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. ;)
Valdis, re-read the original assertion and challenge.
Your attempt at RFC lawyering appears to be "Experimental" <grin>
More information about the NANOG