ietf-mxcomp
[Top] [All Lists]

Re: Designing and Allocating a new RR type

2004-06-24 11:18:12


I think that the idea of using ASN.1 is fine as an architectural point
(DNS certainly suffers from a lack of strict data-typing), but it's
overkill for what we need, while the implementation and potential exploit
problems are on par with XML. So I don't think we should use it for this
specific RR. Too much work for too little gain.

Remember that every ~100 bytes of RR data is roughly the same as whatever
was cached from PTR/A/NS lookups, and saving ~30% or so on that is a good
enough target, so getting to ~70 bytes per RR is really what we should be
looking to reasonably achieve.

If the scope of data is limited, it will probably be good enough to have
coded types and textual field data within the limited subset of types.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/