ietf
[Top] [All Lists]

Re: DNS RRTYPEs, the difficulty with

2012-02-27 14:20:03
Thanks Patrick.

Is there an element, or include, the "Simplicity" argument that has been presented to you?

Thats the feeling I am getting - Fast entry, don' sweat the DNS impact and today, its high OS/software, DB speeds and overall robustness is good enough. Once upon a time, the idea of redundancy (calls) was a concern, at least that seem to be the general mindset, but over time, I have seen statements that we shouldn't worry about it - just do it! Better caching resolves much of the redundancy related overhead concerns.

PS: I agree with your position.

I would like to poise this general question to the IETF/DNS community:

   Given higher modern DNS server support for unnamed types, should
   new protocols continues to pursue new RR types or does the
   DNS Community believe this original infrastructure ideal is no longer
   necessary and new protocols can use TXT records with a high
   degree of DNS support confidence for robustness.

Many new protocols use the TXT records simply as a fast entry, high support 
mechanism to store data on DNS. Is the mindset today such that this is still 
desirable, is there an DNS impact with this on going direction?

I have not heard anything else than arguments in RFC5507 against reusing same 
RRType for many different kind of use.

5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed., R.
     Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=44045 bytes)
     (Status: INFORMATIONAL)

So, still, no, you should not reuse TXT. You should have your own RRType. Other 
choices makes your design very complex.

Yes, many people will still disagree with me, using arguments I do not agree 
with...

  Patrik

_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf