[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: draft-ietf-dnsext-apl-rr-01.txt
- To: <namedroppers@ops.ietf.org>
- Subject: RE: draft-ietf-dnsext-apl-rr-01.txt
- From: "Jesper G. Hoy" <jhoy@jhsoft.com>
- Date: Sun, 3 Dec 2000 21:16:57 -0500
- Delivery-date: Sun, 03 Dec 2000 19:01:12 -0800
- Envelope-to: namedroppers-data@psg.com
>> Maybe we should have a "GC" class (garbage can) for these things in
>> DNS?
> We do, it's called TXT.
How about setting aside a range of record type IDs for "exotic" record
types?
The DNS message format allows for 65536 (2 byte identifier) different record
types.
What if we said that all record type IDs with high bit set are "exotic". In
master files, they could be listed as "X1", "X2", etc. and RDATA could be
hex format for all of them.
This way implementers could treat all X... records the same, and thus no
future changes to BIND etc. are necessary when someone wants to add another
"exotic" record type.
Comments please...
Jesper
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.