On Thu, 2008-04-03, Michael Storz wrote:
At the moment I see two positions:
- use AAAA RRs in synthesizing MX RRs
- do not use AAAA RRs in synthesizing MX RRs
Reasoning about first position:
- it carries over the semantics of IPv4
- it will maximize email connectivity
Reasoning about second position:
- it will reduce server load and ressources, because emails with
* "recipient-AAAA-domains" without an MX RR will be immediately
rejected
* "originator-AAAA-domains" without an MX RR will not be accepted
In the end this means: has the majority of email servers to pay for
the connectivity of a minority of email servers?
Is there any other reason I forgot? Otherwise we could just try to find
consensus which position we prefer.
Looking at this from a slightly different angle.
We choose one of these alternatives and publish 2821bis. Then it is
concluded that the wrong choice has been made. Which of the following
corrections will be the easier RFC to write?
1 - "Now *stop* using AAAA RRs to synthesize MX RRs."
2 - "Now *start* using AAAA RRs to synthesize MX RRs."
--
Bill McQuillan <McQuilWP(_at_)pobox(_dot_)com>