[lacnog] Cuestiones operacionales del direccionamiento IPv6 (Fwd: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard)

Fernando Gont fgont en si6networks.com
Mie Feb 22 17:45:59 BRT 2017


El mismo "bloodshed" al que se refiere Randy ha sido necesario para casi
todas las cosas que yo he hecho en IETF.

Cuando uno relaciona lo de abajo, con el manejo que logran hacer los
grandes vendors de los procesos de IETF, la cosa se vuelve aun mas penosa.

-------- Forwarded Message --------
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version
6 Addressing Architecture) to Internet Standard
Date: Thu, 23 Feb 2017 03:25:43 +0700
From: Randy Bush <randy en psg.com>
To: Job Snijders <job en ntt.net>
CC: 6man WG <ipv6 en ietf.org>, IETF-Discussion Discussion <ietf en ietf.org>,
draft-ietf-6man-rfc4291bis en ietf.org, 6man-chairs en ietf.org

>> "Conflicts with the NTT backbone" != "conficts with almost every
>> deployed backbone".
> You gross over the fact that NTT connects with many other backbones, and
> that the data I shared is a reflection on both NTT's own addressing
> structure as well as peering partner's or customer's addressing.

face it job.  what we have here is non-ops telling us what we should do
and denying what we actually do and intend to keep doing.  welcome to
the ietf; we want ops here but that does not mean we want to listen to

this is not new.  this is the last classful sickness needing expunging
from ipv6.  it has been a long trail.  you would have loved the insanity
of NLA/TLA; and it took some years of bloodshed to get rid of them.


IETF IPv6 working group mailing list
ipv6 en ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6

Más información sobre la lista de distribución LACNOG