ietf-mxcomp
[Top] [All Lists]

[RFC 1464?] RE: Alternative to TXT or new RR was: Comments ondraft-ietf-marid-core-01 xml use

2004-06-11 12:39:46

There is an alternative to a hostile take-over of the TXT record as I
mentioned.

Use a token such as "MARID-1" and follow this with a CRC-32c checksum
(good Hamming distance and code used in SCTP) of the entire 
record where
the checksum field is treated as zero.  Such as "MARID-1[FD034A45]..."
or perhaps "FD034A45_MARID-1...". See RFC3309 for an example 
of language and code.

No one's brought up RFC 1464 yet, which describes how to store unique and
arbitrary information in TXT records in DNS.  SPF does this, DMP does this.
It avoids the TXT record collision problem by describing a unique attribute
name along with a value for the attribute.

How does ISC dhcpd store its host information in the TXT records?  And how
does it tell the difference between its own records and something else's?
Doesn't it use a token like RFC 3309 or an attribute format like RFC 1464?

-- 
PGP key (0x0AFA039E): 
<http://www.pan-am.ca/consulting(_at_)pan-am(_dot_)ca(_dot_)asc>
Sometimes it's hard to tell where the game ends and where reality bites,
er, begins. <http://vmyths.com/resource.cfm?id=50&page=1>