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

Hi all,

Just a quick comment about this version.

The version -09 incorporated editorial changes according to inputs from the AD review.

In that version, to address one of those comments, I used in the abstract and intro "IPv4 public addresses", and Mohamed Boucadair reported that this is not just about the lack "public" ones, but also private, because in some networks private ranges are also a trouble, and thus a reason to move to IPv6.

So just removing "public" is the only correction in this document.

Thanks!

Regards,
Jordi

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de <internet-drafts@ietf.org>
Responder a: <v6ops@ietf.org>
Fecha: miércoles, 17 de octubre de 2018, 8:49
Para: <i-d-announce@ietf.org>
CC: <v6ops@ietf.org>
Asunto: [v6ops] I-D Action: draft-ietf-v6ops-transition-ipv4aas-10.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-10.txt
    	Pages           : 22
    	Date            : 2018-10-16

    Abstract:
       This document specifies the IPv4 service continuity requirements for
       an IPv6 Customer Edge (CE) router, either provided by the service
       provider or through 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).  This is
       required in a world where sufficient IPv4 addresses are no longer
       available for every possible customer/device.  However, devices or
       applications in the customer LANs may be IPv4-only or IPv6-only and
       still need to communicate with IPv4-only services at the Internet.

    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-10
    https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-transition-ipv4aas-10

    A diff from the previous version is available at:
    https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-transition-ipv4aas-10

    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
    v6ops@ietf.org
    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.