IETF Logo Mail Archive

Re: [v6ops] Bar BoF on a 6to4 replacement?

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 13 November 2014 22:53 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E103C1AE148 for <v6ops@ietfa.amsl.com>; Thu, 13 Nov 2014 14:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.795
X-Spam-Level:
X-Spam-Status: No, score=-4.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
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 d5ef9kU9a7RX for <v6ops@ietfa.amsl.com>; Thu, 13 Nov 2014 14:53:09 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13A701AE141 for <v6ops@ietf.org>; Thu, 13 Nov 2014 14:53:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sADMr8OU030316; Thu, 13 Nov 2014 14:53:08 -0800
Received: from XCH-BLV-101.nw.nos.boeing.com (xch-blv-101.nw.nos.boeing.com [130.247.25.116]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sADMqx5Q029777 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 13 Nov 2014 14:53:00 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.66]) by XCH-BLV-101.nw.nos.boeing.com ([169.254.1.11]) with mapi id 14.03.0210.002; Thu, 13 Nov 2014 14:52:59 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, Jeroen Massar <jeroen@massar.ch>, Gert Doering <gert@space.net>, Iljitsch van Beijnum <iljitsch@muada.com>
Thread-Topic: [v6ops] Bar BoF on a 6to4 replacement?
Thread-Index: AQHP/5SRBJqwQ4D6aUGjUUXr5CsnMA==
Date: Thu, 13 Nov 2014 22:52:58 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D8619C@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832D76378@XCH-BLV-504.nw.nos.boeing.com> <AD4F3B9C-18D2-4B6F-867C-423368D6F489@muada.com> <4C77BAB8-38FD-4830-B779-E24586EB9275@delong.com> <5458294D.9000502@massar.ch> <64F92F49-4A31-4268-99D3-8A482E95735F@delong.com> <EB80E1B1-335F-45CA-BAFA-C2DB1BA58F1A@muada.com> <54643D0B.4070208@gmail.com> <88329C76-8C09-42D1-A0F7-9A65B98E1D44@muada.com> <alpine.DEB.2.02.1411132029560.25356@uplift.swm.pp.se> <D202E444-D659-447E-919A-10C6DB48A0BE@muada.com> <20141113195636.GY31092@Space.Net> <54652728.9040901@massar.ch> <54652F3F.2090006@gmail.com>
In-Reply-To: <54652F3F.2090006@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/cjQ3XJT2wtR_wZerHc1wJPiqg08
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Bar BoF on a 6to4 replacement?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 13 Nov 2014 22:53:11 -0000

Hi,

> Goal - any new replacement of 6to4 must be future proof: avoid
> renumbering when 6to4-replacement dies out.  (this is what current
> tunnel brokers dont offer, they force one into a lockin going away from
> tunnel broker to native IPv6 one has renumber).

To amplify this point, tunnels are for more than just IPv6 transition. They are
useful also for:

  - mobility management
  - routing control
  - security (e.g., VPN)
  - multihoming
  - traffic engineering
  - renumbering avoidance
  - etc.

You get all of this (plus v6/v4 transition, of course) with AERO. Indeed,
AERO can be a one-stop-shopping solution for any tunnel application.

Thanks - Fred
fred.l.templin@boeing.com

v2.46.0 | Report a Bug | By Email | System Status