IETF Logo Mail Archive

Re: Another look at 6to4 (and other IPv6 transition issues)

Keith Moore <moore@network-heretics.com> Tue, 19 July 2011 12:30 UTC

Return-Path: <moore@network-heretics.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 B6DDD21F8786 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 05:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.206
X-Spam-Level:
X-Spam-Status: No, score=-3.206 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
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 3epI+opzwzNG for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 05:30:55 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 1DAD921F84F7 for <ietf@ietf.org>; Tue, 19 Jul 2011 05:30:55 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5F88A20C05; Tue, 19 Jul 2011 08:30:54 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 19 Jul 2011 08:30:54 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=YJiH3MX6xQfBwXT8vrDV7i6Wv7w=; b=dsH7ayMTSbqYY/3JZxjzIeH9KjCHeFY4KQyFfMaomQw6gSJKRacM5pqVCh84myQBaKymxIaFyqPmQEMQyrwDc2hpV8+ebCsquO5LwHzxN9CgeYQTbrZx/41uLtDCJZOyzzh/A+b2ARrwVqpIPX5k96kq7qAn1Hm+qgtOyUdLfNo=
X-Sasl-enc: FYm3a/qrV/osk/9h3OYQ9Cf5gvXW04uHMEvBSMbOWh/u 1311078653
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 65AAA44E9C1; Tue, 19 Jul 2011 08:30:52 -0400 (EDT)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <004b01cc45e4$8be36f60$4001a8c0@gateway.2wire.net>
Date: Tue, 19 Jul 2011 08:29:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E4FFDA4-8752-4037-BC4C-D12D072F3C0F@network-heretics.com>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu> <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net> <004b01cc45e4$8be36f60$4001a8c0@gateway.2wire.net>
To: "t.petch" <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1084)
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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: Tue, 19 Jul 2011 12:30:55 -0000

On Jul 19, 2011, at 3:21 AM, t.petch wrote:

> What is needed is some lateral thinking, such as the proposal that instead of
> trying to shoehorn an RFC into an inappropriate, closed set of maturity levels,
> we use a completely different option, namely an Appplicability Statement that
> spells out that this magnificent standards track, non-historic piece of
> technology now has an extremely limited applicability, and unless you really
> know what you are doing, forget it.

An Applicability Statement was my first suggestion for how to address the problem, and it's still acceptable to me.

Keith

v2.23.0 | Report a Bug | By Email