Steve Atkins wrote:
I think that deploying a new RR isn't as trivial as has been claimed,
but having TXT and something else just won't work well.
Steve,
I see your point and concern.
If the WG is wanting a new RR, then my vote for a RR/TXT lookup order
was just the most logical strategy, IMO.
On the other hand, the TXT record can contain an NEWRR=1 attribute that
tells the client that the same info is available via an RR lookup, if
its reliable for the client to use. In this case, it would a TXT lookup
first time concept.
I don't see that as a problem.
But again, my vote was only if the WG was moving towards a new RR idea.
Which I think it should as a long term stategy.
--
Sincerely
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html