Subject: Re: [Tsv-art] New Version Notification for draft-ietf-v6ops-transition-ipv4aas-12.txt

From: JORDI PALET MARTINEZ <[email-masked]>
Date: Thu, 27 Dec 2018 18:25:42 +0100

Hi all,

Considering the review comments from ops, sec, rtg and tsv, we just completed a new version:

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

Thanks!

Regards,
Jordi

-----Mensaje original-----
De: <[email-masked]>
Fecha: jueves, 27 de diciembre de 2018, 18:20
Para: Masanobu Kawashima <[email-masked]>, "Hans M.-H. Liu" <[email-masked]>, Jordi Palet Martinez <[email-masked]>, Jordi Palet <[email-masked]>, Hans Liu <[email-masked]>
Asunto: New Version Notification for draft-ietf-v6ops-transition-ipv4aas-12.txt

    A new version of I-D, draft-ietf-v6ops-transition-ipv4aas-12.txt
    has been successfully submitted by Jordi Palet Martinez and posted to the
    IETF repository.
    
    Name:		draft-ietf-v6ops-transition-ipv4aas
    Revision:	12
    Title:		Requirements for IPv6 Customer Edge Routers to Support IPv4 Connectivity as-a-Service
    Document date:	2018-12-27
    Group:		v6ops
    Pages:		24
    URL:            https://www.ietf.org/internet-drafts/draft-ietf-v6ops-transition-ipv4aas-12.txt
    Status:         https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/
    Htmlized:       https://tools.ietf.org/html/draft-ietf-v6ops-transition-ipv4aas-12
    Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-transition-ipv4aas
    Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-transition-ipv4aas-12
    
    Abstract:
       This document specifies the IPv4 service continuity requirements for
       an IPv6 Customer Edge (CE) router, either provided by the service
       provider or by vendors who sell through the retail market.
    
       Specifically, this document extends the "Basic Requirements for IPv6
       Customer Edge Routers" (RFC7084) 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).  This
       is necessary because there aren't sufficient IPv4 addresses available
       for every possible customer/device.  However, devices or applications
       in the customer LANs (Local Area Networks) may be IPv4-only or
       IPv6-only and still need to communicate with IPv4-only services at
       the Internet.

    
    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

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
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.