Re: [v6ops] draft-ietf-v6ops-6to4-to-historic WGLC

james woodyatt <jhw@apple.com> Thu, 21 April 2011 18:18 UTC

Return-Path: <jhw@apple.com>
X-Original-To: v6ops@ietfc.amsl.com
Delivered-To: v6ops@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1A228E06C9 for <v6ops@ietfc.amsl.com>; Thu, 21 Apr 2011 11:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAkmYMWt8u2k for <v6ops@ietfc.amsl.com>; Thu, 21 Apr 2011 11:18:15 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfc.amsl.com (Postfix) with ESMTP id 875D6E06A0 for <v6ops@ietf.org>; Thu, 21 Apr 2011 11:18:15 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LK000D2DLC5DFI1@mail-out.apple.com> for v6ops@ietf.org; Thu, 21 Apr 2011 11:18:14 -0700 (PDT)
X-AuditID: 11807134-b7c8cae000005108-ea-4db074e54a2a
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id 00.89.20744.6E470BD4; Thu, 21 Apr 2011 11:18:14 -0700 (PDT)
Received: from [17.193.13.64] by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LK000FZDLIDZO60@koseret.apple.com> for v6ops@ietf.org; Thu, 21 Apr 2011 11:18:13 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <alpine.LRH.2.02.1104212051370.22232@netcore.fi>
Date: Thu, 21 Apr 2011 11:18:14 -0700
Message-id: <E3F738B6-5E84-435A-A10F-08FFA27EC19D@apple.com>
References: <4984B8F2-AC42-491E-9C2B-BE999B279759@cisco.com> <alpine.LRH.2.02.1104211405450.14690@netcore.fi> <AEAA108B-BDD3-4810-8464-A483D572EADF@cisco.com> <alpine.LRH.2.02.1104212051370.22232@netcore.fi>
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.1216)
X-Brightmail-Tracker: AAAAAA==
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Apr 2011 18:18:16 -0000

On Apr 21, 2011, at 11:01 , Pekka Savola wrote:
> 
> Are you hoping that even if they don't change their opinion, they will conform to the RFC?

I'd like to note here that all of Apple's currently shipping products expressly require human intervention to enable 6to4 tunneling.

About three years ago, for a brief period of time, Apple sold a few hundred thousand AirPort Extreme base stations that enabled 6to4 tunneled IPv6 routing in their default configuration.  Apple didn't need an RFC to figure out precisely how and why this wasn't a very good idea, and changed the default configuration.

Until a few months ago, the only way it was possible for an Apple product to be configured into a 6to4 tunneling mode without express human intervention was by inadvertently importing a saved configuration from one of those older AirPort Extreme base stations into a newer AirPort product.  With the latest 7.5.2 release of AirPort/TimeCapsule firmware, even *that* isn't possible anymore.

Apple is already in absolute total conformance with the language in this draft.  I still oppose its publication for the reasons I've already stated, which have nothing to do with any implications of the recommendations it contains on Apple's business plans.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking