Re: [v6ops] I-D Action: draft-ietf-v6ops-transition-ipv4aas-03.txt

[JORDI PALET MARTINEZ <[e-mail]>]

Hi all,



As indicated a couple of day ago, we have updated this document, so instead of an update of RFC8026 and a new option code, we only need to ask IANA to use a NAT64 existing one for the RFC8026 priority table.



https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/?include_text=1



Let's know any comments you have.



Thanks!



Regards,

Jordi

 

 



-----Mensaje original-----

De: v6ops <[e-mail]> en nombre de <[e-mail]>

Fecha: sábado, 16 de junio de 2018, 8:43

Para: <[e-mail]>

CC: <[e-mail]>

Asunto: [v6ops] I-D Action: draft-ietf-v6ops-transition-ipv4aas-03.txt



    

    A New Internet-Draft is available from the on-line Internet-Drafts directories.

    This draft is a work item of the IPv6 Operations WG of the IETF.

    

            Title           : Requirements for IPv6 Customer Edge Routers to Support IPv4 Connectivity as-a-Service

            Authors         : Jordi Palet Martinez

                              Hans M.-H. Liu

                              Masanobu Kawashima

    	Filename        : draft-ietf-v6ops-transition-ipv4aas-03.txt

    	Pages           : 20

    	Date            : 2018-06-15

    

    Abstract:

       This document specifies the IPv4 service continuity requirements for

       an IPv6 Customer Edge (CE) router, either provided by the service

       provider or thru the retail market.

    

       Specifically, this document extends the "Basic Requirements for IPv6

       Customer Edge Routers" in order to allow the provisioning of IPv6

       transition services for the support of "IPv4 as-a-Service" (IPv4aaS)

       by means of new transition mechanisms.  The document only covers

       transition technologies for delivering IPv4 in IPv6-only access

       networks, commonly called "IPv4 as-a-Service" (IPv4aaS), as required

       in a world where IPv4 addresses are no longer available, so hosts in

       the customer LANs with IPv4-only or IPv6-only applications or

       devices, requiring to communicate with IPv4-only services at the

       Internet, are still able to do so.

    

    

    The IETF datatracker status page for this draft is:

    https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/

    

    There are also htmlized versions available at:

    https://tools.ietf.org/html/draft-ietf-v6ops-transition-ipv4aas-03

    https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-transition-ipv4aas-03

    

    A diff from the previous version is available at:

    https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-transition-ipv4aas-03

    

    

    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/

    

    _______________________________________________

    v6ops mailing list

    [e-mail]

    https://www.ietf.org/mailman/listinfo/v6ops

    




**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.