Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-isp-ip6rdns-03.txt

From: "Woodworth, John R" <[email-masked]>
Date: Mon, 5 Jun 2017 20:58:59 +0000

> -----Original Message-----
> From: DNSOP [mailto:[email-masked]] On Behalf Of John R Levine
> Sent: Thursday, May 11, 2017 1:41 PM
> To: Paul Vixie
> Cc: [email-masked]
> Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-isp-ip6rdns-03.txt
>
> >> You might want to talk to large providers that do v6 now.
> >> With only one exception I can think of, they have no plans
> >> to do synthesized v6 rDNS, and they routinely block port 25
> >> from all their consumer networks.
> >
> > i'd like to meet your friends. but i'd also like them write an
> > rfc about it.
>
> You've met a lot of them at M3AAWG.  Also see draft-ietf-dnsop-isp-ip6rdns
>
> I hope we are not so foolish as to repeat the NAT fiasco and stick our
> fingers in our ears becuse the rest of the world doesn't work in a way
> some of us might prefer.
>
> The reality is that if you want people to accept your v6 mail, your mail
> hosts need rDNS, and not rDNS that looks like it was autogenerated by
> kludges like BULK.
>

Looks like the radioactive spider that bit me was from the control group
because there was no tingling of my spidey sense :)

I echo the point of email servers being assigned a real rDNS to cut down
on heartburn.  Thankfully one of BULK's features ensures real RRs can
easily coexist within a synthesized range.

BTW: kludge seems harsh for a carefully thought-out solution

/John

>
> Regards,
> John Levine, [email-masked], Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>
> _______________________________________________
> DNSOP mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/dnsop
>
>
-- THESE ARE THE DROIDS TO WHOM I REFER:
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.