Subject: Re: [DNSOP] DNSOP Digest, Vol 142, Issue 6

From: Tariq Saraj <[email-masked]>
Date: Thu, 6 Sep 2018 10:56:22 +0500

>most email providers will not accept incoming connections on port 25
unless forward and reverse DNS entries match. A couple of years back I have
been working in the design and development of Hybrid IPv4-IPv6 network
different scenarios. One fact about an IPv6 communicating host is that
mostly it uses a pseudo random suffix along with the network prefix.

On Thu, Sep 6, 2018 at 12:04 AM <[email-masked]> wrote:

> Send DNSOP mailing list submissions to
>         [email-masked]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/dnsop
> or, via email, send a message with subject or body 'help' to
>         [email-masked]
>
> You can reach the person managing the list at
>         [email-masked]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of DNSOP digest..."
>
>
> Today's Topics:
>
>    1.  I-D Action: draft-ietf-dnsop-isp-ip6rdns-06.txt
>       ([email-masked])
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 05 Sep 2018 11:45:34 -0700
> From: [email-masked]
> To: <[email-masked]>
> Cc: [email-masked]
> Subject: [DNSOP] I-D Action: draft-ietf-dnsop-isp-ip6rdns-06.txt
> Message-ID: <[email-masked]>
> Content-Type: text/plain; charset="utf-8"
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Domain Name System Operations WG of the
> IETF.
>
>         Title           : Reverse DNS in IPv6 for Internet Service
> Providers
>         Author          : Lee Howard
>         Filename        : draft-ietf-dnsop-isp-ip6rdns-06.txt
>         Pages           : 14
>         Date            : 2018-09-05
>
> Abstract:
>    In IPv4, Internet Service Providers (ISPs) commonly provide IN-
>    ADDR.ARPA information for their customers by prepopulating the zone
>    with one PTR record for every available address.  This practice does
>    not scale in IPv6.  This document analyzes different approaches and
>    considerations for ISPs in managing the IP6.ARPA zone.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-isp-ip6rdns/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dnsop-isp-ip6rdns-06
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-isp-ip6rdns-06
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-isp-ip6rdns-06
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> DNSOP mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/dnsop
>
>
> ------------------------------
>
> End of DNSOP Digest, Vol 142, Issue 6
> *************************************
>

-- 
Regards
Tariq Saraj
Riphah Institute of Systems Engineering, Islamabad