IETF Logo Mail Archive

Re: 6to4v2 (as in ripv2)?

Fred Baker <fred@cisco.com> Wed, 27 July 2011 11:10 UTC

Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E46921F8548; Wed, 27 Jul 2011 04:10:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.109
X-Spam-Level:
X-Spam-Status: No, score=-103.109 tagged_above=-999 required=5 tests=[AWL=-0.510, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AnhJ1MC4Bq1T; Wed, 27 Jul 2011 04:10:25 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id B6E7521F854C; Wed, 27 Jul 2011 04:10:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=304; q=dns/txt; s=iport; t=1311765025; x=1312974625; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=1hin4uOQkS5g+jSDNnAebBaB/3C6zDOjcxMIYRhoq7E=; b=bpTs4M1fD7dKBfE7do6X9B2GF6H0lU3r3y5Mhjuz7gUdRnJ33KxlWkWf ykQcEQe9iI9ewz2OcAZoTP0EwOdjBtjQsNZnL0jlLY+YNPQRWDaLTAgFi e1kZHW5uHGOwIyr5w5tlk7XgrvEZwYG6Zmly0PSwj08wLfeZSTP96W5rh Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EADzxL06rRDoI/2dsb2JhbAA1AQEBAQIBFAErRQUMDFIUUQc+pxp3iHyieJ5mhWFfBJJ1hQeLdw
X-IronPort-AV: E=Sophos;i="4.67,276,1309737600"; d="scan'208";a="6905634"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-4.cisco.com with ESMTP; 27 Jul 2011 11:09:49 +0000
Received: from dhcp-4466.meeting.ietf.org (sjc-vpn6-314.cisco.com [10.21.121.58]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p6RB8MU5020644; Wed, 27 Jul 2011 11:09:47 GMT
Received: from [127.0.0.1] by dhcp-4466.meeting.ietf.org (PGP Universal service); Wed, 27 Jul 2011 07:09:48 -0400
X-PGP-Universal: processed; by dhcp-4466.meeting.ietf.org on Wed, 27 Jul 2011 07:09:48 -0400
Subject: Re: 6to4v2 (as in ripv2)?
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4E2F4491.30102@gmail.com>
Date: Wed, 27 Jul 2011 07:09:47 -0400
Message-Id: <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 11:10:26 -0000

On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:

> Since 6to4 is a transition mechanism it has no long term future *by definition*. Even if someone chooses to design a v2, who is going to implement it?

Actually, I think one could argue pretty effectively that 6rd is 6to4-bis.

v2.23.0 | Report a Bug | By Email