Re: [v6ops] Sunset4 gap analysis: rfc6555bis, ipv6rtr-reqs, rfc7084-bis

Hi Lee,

I’m happy to review draft-ietf-v6ops-rfc7084-bis-04 with possible solutions, but we first, as a WG, need to clarify if still want to update RFC7084 or instead, want to go in the direction of separating the transition requirements as per draft-palet-v6ops-rfc7084-bis-transition-00.

Updating draft-ietf-v6ops-rfc7084-bis-04 could allow what you are asking for.

However, if we don’t want to touch RFC7084, seems to me difficult that we can do it in a “transition” only document.

So, do we want to re-consider this decision again?

My plan, if time permits, is to update either one or the other document next week.

Regarding 6&7, I actually provided text on that to the authors, and one of my comments was in the direction of RFC6555-bis can somehow sort out those, but the actual text is still based in RFC6555 until RFC6555-bis become an RFC, in order to avoid “holding” draft-ietf-sunset4-gapanalysis-09, so all depends on how fast we move with one or the other …

Regards,
Jordi

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Lee Howard <lee@asgard.org>
Responder a: <lee@asgard.org>
Fecha: miércoles, 16 de agosto de 2017, 18:28
Para: <v6ops@ietf.org>
Asunto: [v6ops] Sunset4 gap analysis: rfc6555bis, ipv6rtr-reqs, rfc7084-bis

    Reading through draft-ietf-sunset4-gapanalysis-09 it seemed to me that several problems might be resolvable in documents we currently have open:

    Can problems 1-5 (indicating that IPv4 is unavailable, disabling IPv4 in the LAN) be addressed with recommendations in any, some, or all of:
    draft-ietf-v6ops-ipv6rtr-reqs-00 "Requirements for IPv6 Routers"
    draft-ietf-v6ops-rfc7084-bis-04  “Basic Requirements for IPv6 Customer Edge Routers"
    Or other drafts under discussion in v6ops now?
    Or do we need new IPv6 signalling (RA?) that IPv4 is unavailable? That would have to go to 6man. Or did we do this, and I’ve forgotten in my old age?

    Are problems 6 & 7 (Happy Eyeballs and getaddrinfo()) addressed with draft-ietf-v6ops-rfc6555bis-03,  "Happy Eyeballs Version 2: Better Connectivity Using Concurrency”?
    Can problem 10 be addressed in rfc6555-bis?

    Thanks,

    Lee

    _______________________________________________
    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.