IETF Logo Mail Archive

Re: IPv6 Router Advertisement Option for Foobar Configuration

Warren Kumari <warren@kumari.net> Tue, 03 January 2012 17:00 UTC

Return-Path: <warren@kumari.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9676011E8080 for <ipv6@ietfa.amsl.com>; Tue, 3 Jan 2012 09:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.483
X-Spam-Level:
X-Spam-Status: No, score=-106.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ou8oX3ihhRrW for <ipv6@ietfa.amsl.com>; Tue, 3 Jan 2012 09:00:27 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 0B26511E8072 for <ipv6@ietf.org>; Tue, 3 Jan 2012 09:00:26 -0800 (PST)
Received: from dhcp-172-19-119-228.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id ACA6F1B405C3; Tue, 3 Jan 2012 12:00:23 -0500 (EST)
Subject: Re: IPv6 Router Advertisement Option for Foobar Configuration
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <82609C20-FC6F-4B5C-95DF-7AF9C922C0B6@puck.nether.net>
Date: Tue, 03 Jan 2012 12:00:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BFF082C-B910-4F67-BAA5-B2B81CFF9049@kumari.net>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com><4EF22786.2070908@dougbarton.us> <4EF2373B.6060905@gmail.com><4EF24007.3030300@dougbarton.us> <4EF258A5.1040106@gmail.com><4EF4344B.6040504@dougbarton.us> <CAKFn1SGXLB4CExh4i9bjN1oLNFv+AL3pKzy5SDgWdSeSACrvCw@mail.gmail.com> <750BF7861EBBE048B3E648B4BB6E8F4F21AF8700@crexc50p> <82609C20-FC6F-4B5C-95DF-7AF9C922C0B6@puck.nether.net>
To: Jared Mauch <jared@puck.nether.net>
X-Mailer: Apple Mail (2.1084)
Cc: 6man Mailing List <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2012 17:00:41 -0000

On Jan 3, 2012, at 9:17 AM, Jared Mauch wrote:

> 
> On Jan 3, 2012, at 9:13 AM, STARK, BARBARA H wrote:
> 
>> 4. [my favorite] Neither clients nor routers can predict whether they will find themselves in an environment where only one or the other is supported. So both clients and routers that expect to be fully interoperable must support both. The majority gets to double their complexity. So that a minority can simplify just a little bit.
>> 
> 
> I have to parrot this as well.  The increased complexity of IPv6 is commonly provided as a reason that one can't deploy IPv6.
<aol>
Me too!
</aol>

> 
> - Jared
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email