Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc7084-bis-01.txt

Hi Jordi, 

Thank you for this update. 

Putting aside the update/obsolete issue, below some comments:

* 464XLAT is followed by mobile operators. I suggest to remove it from the document because there are plenty IPv6-specific features that need to be supported by a wireless CPE. There is no reason to focus on CLAT while ignoring other specific IPv6 requirements for cellular devices (see for example RFC7849).  

* If you would like to maintain 6rd/6in4, then you may need to structure the various mechanisms, e.g.,

OLD: 

     5.4.  Transition Technologies Support . . . . . . . . . . . . .  15
       5.4.1.  464XLAT . . . . . . . . . . . . . . . . . . . . . . .  15
       5.4.2.  6in4  . . . . . . . . . . . . . . . . . . . . . . . .  15
       5.4.3.  6rd . . . . . . . . . . . . . . . . . . . . . . . . .  17
       5.4.4.  Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . .  18
       5.4.5.  Lightweight 4over6 (lw4o6)  . . . . . . . . . . . . .  19
       5.4.6.  MAP-E . . . . . . . . . . . . . . . . . . . . . . . .  19
       5.4.7.  MAP-T . . . . . . . . . . . . . . . . . . . . . . . .  20

NEW:

     5.4.  IPv4 Service Continuity over IPv6 Networks . . . . . . . .  15
       5.4.1.  xxxx . . . . . . . . . . . . . . . . . . . . . . .      15
       5.4.x.  xxxx . . . . . . . . . . . . . .  . . . . . . . . .     18
       5.4.x.  xxxxxxxxxx  . . . . . . . . . . . . . . . . . . .       19
       5.4.x.  xxxxx . . . . . . . . . . . . . . . . . . . . . . . .   19
       5.4.x.  xxxxx . . . . . . . . . . . . . . . . . . . . . . . .   20 
     5.5.  IPv6 over IPv4 Networks  . . . . . . . . . . . . . . . . . xxx
       5.x.x.  xxxx  . . . . . . . . . . . . . . . . . . . . . . . .  xxx
       5.x.x.  xxxx . . . . . . . . . . . . . . . . . . . . . . . . .  xx

Cheers,
Med

> -----Message d'origine-----
> De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de JORDI PALET
> MARTINEZ
> Envoyé : mercredi 12 avril 2017 18:00
> À : v6ops@ietf.org
> Objet : Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc7084-bis-01.txt
> 
> Hi all,
> 
> As indicated a couple of days ago, I’ve posted a new version.
> 
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-rfc7084-bis
> 
> It contains a new Annex at the end of the document, reflecting the changes
> from -00, which basically are what has been discussed in the list the last
> few days:
> 
> 1. LW4O6-5 changed to port-restricted to conform with [RFC7596].
> 2. MAPE-3 changed to port-restricted to conform with [RFC7597].
> 3. MAPT-3 changed to port-restricted to conform with [RFC7599].
> 4. [RFC7341] removed from 464XLAT, DS-LITE, MAP-E and MAP-T requirements.
> 5. [RFC5625] removed from 464XLAT, and included as general LAN
> requirement.
> 6. [RFC7618] included as MAY for lw4o6.
> 
> Hopefully now that we have some “heat” in the discussion, this version
> will facilitate interested folks to read over.
> 
> Regards,
> Jordi
> 
> 
> -----Mensaje original-----
> De: v6ops <v6ops-bounces@ietf.org> en nombre de <internet-drafts@ietf.org>
> Responder a: <internet-drafts@ietf.org>
> Fecha: miércoles, 12 de abril de 2017, 17:51
> Para: <i-d-announce@ietf.org>
> CC: <v6ops@ietf.org>
> Asunto: [v6ops] I-D Action: draft-ietf-v6ops-rfc7084-bis-01.txt
> 
> 
>     A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>     This draft is a work item of the IPv6 Operations of the IETF.
> 
>             Title           : Basic Requirements for IPv6 Customer Edge
> Routers
>             Author          : Jordi Palet Martinez
>     	Filename        : draft-ietf-v6ops-rfc7084-bis-01.txt
>     	Pages           : 29
>     	Date            : 2017-04-12
> 
>     Abstract:
>        This document specifies requirements for an IPv6 Customer Edge (CE)
>        router.  Specifically, the current version of this document focuses
>        on the basic provisioning of an IPv6 CE router and the provisioning
>        of IPv6 hosts attached to it.  The document also covers several
>        transition technologies, 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 able to do so.  The
> document
>        obsoletes RFC 7084.
> 
> 
>     The IETF datatracker status page for this draft is:
>     https://datatracker.ietf.org/doc/draft-ietf-v6ops-rfc7084-bis/
> 
>     There are also htmlized versions available at:
>     https://tools.ietf.org/html/draft-ietf-v6ops-rfc7084-bis-01
>     https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-rfc7084-bis-01
> 
>     A diff from the previous version is available at:
>     https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-rfc7084-bis-01
> 
> 
>     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 use of the
> individual(s) named above. If you are not the intended recipient be aware
> that any disclosure, copying, distribution or use of the contents of this
> information, including attached files, is prohibited.
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops