Re: [v6ops] Google Alert - IPv6

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Thu, 19 October 2017 01:34 UTC

Return-Path: <rajiva@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F1D513421A for <v6ops@ietfa.amsl.com>; Wed, 18 Oct 2017 18:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id akbftdaVDWU1 for <v6ops@ietfa.amsl.com>; Wed, 18 Oct 2017 18:34:00 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 919E4132EA7 for <v6ops@ietf.org>; Wed, 18 Oct 2017 18:34:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19083; q=dns/txt; s=iport; t=1508376840; x=1509586440; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=E5iF1vrvAXtEThQI3Mgo+w1LcjRWUAyzQybfqFEb+gY=; b=I7poz3nXDuFu9+D6mx55HXEGbRGV8V8vuTNGQFwXkG2Yq6Kdhl9MoJnS oZjwT/GVjBbXoAqTzl+cqn9Mgg5z86lvQHAeLmroE/FhGHtNTk/EpxnKy LY5pn3LsMlCrkPjZQcwKkZT6xSnK6Ss4af5GjZ5SFK4uMwxYObkP2rs6I I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CyAAAmAOhZ/5FdJa1dGQEBAQEBAQEBAQEBBwEBAQEBg19kbieDeoofjziBeYhJiCuFPxCBJQNcChgBCoUYAhqEXz8YAQIBAQEBAQEBayiFHgIEAQEhSwsQAgEIPwMCAgIfBgsUDAUCBA4FiBsBgSBMAxUQqy2CJ4c9DYNZAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYMvgTVSgVFueyyDBIJegWtMBxUSglUvgjIFoQ88AodegReGfYR5ghSRBI0FiEECERkBgTgBHzhPgQx6FUktAYI2CYRWdgGKXwoBAQE
X-IronPort-AV: E=Sophos; i="5.43,399,1503360000"; d="scan'208,217"; a="18964548"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Oct 2017 01:33:59 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v9J1Xxk2020530 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Oct 2017 01:33:59 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 18 Oct 2017 20:33:58 -0500
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1320.000; Wed, 18 Oct 2017 20:33:58 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Google Alert - IPv6
Thread-Index: AQHTSFc+u5JAHism50KeDxfBcuQ1G6LqfCAAgAAIY4CAACiEAP//tvb7
Date: Thu, 19 Oct 2017 01:33:58 +0000
Message-ID: <DF5AFD8B-57A6-41B4-914D-C9164198B37A@cisco.com>
References: <f403045ef57ac52962055bd88b84@google.com> <20395E98-DA55-447F-BEFE-CB581A88BB78@gmail.com> <CAHaKRvJPeJDBZx+aZqPqd0_LOm2PUNBvLJfqBOJq3SyeNaPv_A@mail.gmail.com> <862D044C-72E1-49D5-A259-81C6C6B90943@consulintel.es>, <7d8fcc0c-5082-8b8b-61a8-4b42f3241204@gmail.com>
In-Reply-To: <7d8fcc0c-5082-8b8b-61a8-4b42f3241204@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_DF5AFD8B57A641B4914DC9164198B37Aciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/s9Oj_yC4NddDHBBFHiDY2WDnrDU>
Subject: Re: [v6ops] Google Alert - IPv6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Oct 2017 01:34:02 -0000

Ditto, though I wish 6264 pointed out stateless techniques as well (under the broader umbrella).

Also, a bit of hair splitting below  -

CGNAT is unavoidable, until IPv4 is turned off completely.  There are

IPv4 address sharing is unavoidable, but CGNAT is avoidable (thanks to MAP-T/E etc. employing Stateless Means) in many scenarios.

Charter communications is marching ahead with MAP-T deployments (no CGN), as per the recent NANOG presentation.


Cheers,
Rajiv Asati
Distinguished Engineer, Cisco Services


On Oct 18, 2017, at 8:55 PM, Brian E Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>> wrote:

I would like to remind people that this WG already addressed the issue
a while back: https://tools.ietf.org/html/rfc6264

Of course the ecosystem has evolved since then. In particular, 464XLAT
was not an option, but I hope the basic idea is still valid.

Regards
  Brian

On 19/10/2017 11:30, JORDI PALET MARTINEZ wrote:
Fully agree and in fact this was the basis of my discussion with Europol last week.

We had a complete day workshop on this topic, plus many documents exchange in preparation for that.

After my presentation and all day long discussions, it was clear that the path is deploying IPv6 + voluntary code of conduct among ISPs + legislation.

I also showed that there are ways and ways to deploy IPv6, in terms of different transition mechanism.

Then as promoting (again) IPv6 deployment was decided as the first step from the EC and member states, I indicated that we need to provide example in our own institutions, so I asked (I knew the answer in advance) to raise the hand to all the member states that have already their institutions (police in this case), already IPv6 enabled … surprise surprise … none was ready.

So, I asked if we can agree in a short-term plan for all them to “at least” have public plan announced in the next 6 months. So that’s what I will be working now with them.

Regards,
Jordi


-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org>> en nombre de Paul Marks <pmarks@google.com<mailto:pmarks@google.com>>
Responder a: <pmarks@google.com<mailto:pmarks@google.com>>
Fecha: jueves, 19 de octubre de 2017, 0:01
Para: Fred Baker <fredbaker.ietf@gmail.com<mailto:fredbaker.ietf@gmail.com>>
CC: <v6ops@ietf.org<mailto:v6ops@ietf.org>>
Asunto: Re: [v6ops] Google Alert - IPv6

   On Wed, Oct 18, 2017 at 2:22 PM, Fred Baker <fredbaker.ietf@gmail.com<mailto:fredbaker.ietf@gmail.com>> wrote:
So, this may be a dumb question. IPv6 advocates will reflexively agree with
comments on “CGNAT is a bad idea”. But as operators who very likely have
some combination of IPv6 and CGNAT, do we have thoughtful experience-based
comments on this topic?

   CGNAT is unavoidable, until IPv4 is turned off completely.  There are
   more humans than IPv4 addresses, so somebody needs to share.

   Deploying CGNAT without deploying IPv6 first is a bad idea.

   _______________________________________________
   v6ops mailing list
   v6ops@ietf.org<mailto: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.



_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops


_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops