Re: [DNSOP] New Version Notification for draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt

["Brzozowski, John" <[e-mail]>]

Cross posting with dnsop and sunsets per email exchanges/conversations
with both sets of chairs.

John

-----Original Message-----
From: John Jason Brzozowski <[e-mail]>
Date: Monday, November 2, 2015 at 17:21
To: "[e-mail]" <[e-mail]>
Cc: Fred Baker <[e-mail]>, "[e-mail]"
<[e-mail]>, "[e-mail]" <[e-mail]>, Joel
Jaeggli <[e-mail]>, Paul Ebersman
<[e-mail]>, Brian Haberman
<[e-mail]>, "[e-mail]"
<[e-mail]>, Wesley George <[e-mail]>,
Marc Blanchet <[e-mail]>
Subject: New Version Notification for
draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt

>sunset4,
>
>Please see the following I-D that was submitted earlier today.  We would
>appreciate your feedback and comments.  I had some offline email with the
>dnsop and v6ops chairs and ADs (they are copied instead of cross posting
>for now).  The guidance I received was to post this here to sunset4.
>
>Thanks,
>
>John
>[phone]
>
>
>
>
>-----Original Message-----
>From: "[e-mail]" <[e-mail]>
>Date: Monday, November 2, 2015 at 16:48
>To: Paul Ebersman <[e-mail]>, John Jason Brzozowski
><[e-mail]>
>Subject: New Version Notification for
>draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt
>
>>
>>A new version of I-D, draft-jjmb-sunset4-dns-forwarding-ipv4aas-00.txt
>>has been successfully submitted by John Jason Brzozowski and posted to
>>the
>>IETF repository.
>>
>>Name:		draft-jjmb-sunset4-dns-forwarding-ipv4aas
>>Revision:	00
>>Title:		DNS Forwarding and IPv4aaS
>>Document date:	2015-11-02
>>Group:		Individual Submission
>>Pages:		7
>>URL:            
>>https://www.ietf.org/internet-drafts/draft-jjmb-sunset4-dns-forwarding-ip
>>v
>>4aas-00.txt
>>Status:         
>>https://datatracker.ietf.org/doc/draft-jjmb-sunset4-dns-forwarding-ipv4aa
>>s
>>/
>>Htmlized:       
>>https://tools.ietf.org/html/draft-jjmb-sunset4-dns-forwarding-ipv4aas-00
>>
>>
>>Abstract:
>>   The depletion of IPv4 coupled with the wide spread deployment of IPv6
>>   for broadband globally is creating an environment where service
>>   providers can seriously begin to consider alternate uses and
>>   applications for native IPv6 connectivity.  Pervasive, reliable
>>   support for IPv6 across many access technologies suggests that one
>>   critical use for native IPv6 is the carry legacy IPv4 communications.
>>   Today this is referred to as IPv4 as a Service (IPv4aaS).  IPv4aaS
>>   can leverage a variety of transports ranging from Mapping of Address
>>   and Ports (MAP) to Generic Route Encapsulation (GRE) along with other
>>   viable protocols.  Most every use case for IPv4aaS includes the use
>>   of CG-NAT, however, this is not strictly required.  The purpose of
>>   this document is to hone in on DNS specific behavior that must be
>>   taken into consideration as the deployment of IPv4aaS advances
>>   globally.
>>
>>                 
>>        
>>
>>
>>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.
>>
>>The IETF Secretariat
>>
>>
>