Re: A Plea for Architectural & Specification Stability with IPv6

Hesham Soliman <hesham@elevatemobile.com> Sun, 16 March 2014 12:12 UTC

Return-Path: <hesham@elevatemobile.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1D4B1A00FB for <ipv6@ietfa.amsl.com>; Sun, 16 Mar 2014 05:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 5Rc3TL8GQzCR for <ipv6@ietfa.amsl.com>; Sun, 16 Mar 2014 05:12:05 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id 957E21A02E2 for <ipv6@ietf.org>; Sun, 16 Mar 2014 05:11:55 -0700 (PDT)
Received: from [203.219.211.243] (helo=[192.168.0.8]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1WP9us-00020v-U2; Sun, 16 Mar 2014 23:11:47 +1100
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Sun, 16 Mar 2014 23:11:42 +1100
Subject: Re: A Plea for Architectural & Specification Stability with IPv6
From: Hesham Soliman <hesham@elevatemobile.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>, Lorenzo Colitti <lorenzo@google.com>, RJ Atkinson <rja.lists@gmail.com>
Message-ID: <CF4BDFA1.4C25C%hesham@elevatemobile.com>
Thread-Topic: A Plea for Architectural & Specification Stability with IPv6
References: <E2C06D73-99FF-42B5-A3BE-337C307BCB0E@gmail.com> <CAKD1Yr0fjSWfPDkvc9Z53xBKxMGzYcVGzH3tLUGbjCKmgR_Duw@mail.gmail.com> <1394844420.87212.YahooMailNeo@web162206.mail.bf1.yahoo.com>
In-Reply-To: <1394844420.87212.YahooMailNeo@web162206.mail.bf1.yahoo.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-User: hesham@elevatemobile.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/bSB-L2_zmom-_HSY6cWoN8RTC5A
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 16 Mar 2014 12:12:08 -0000

>>
>>Continued tinkering with IPv6 - especially tinkering with it to make it
>>look more and more like IPv4 in order to reduce imagined "barriers to
>>adoption" - will just erode IPv6's long-term advantages by eliminating
>>the simplification, robustness, and benefits that IPv6 as it is today
>>*does* provide -- and it won't lead to adoption anyway, because lack of
>>adoption is not a technical issue.

=> Thank you for this sentence, whoever said it! I have been working on
deployment issues with operators and I never saw this imagined barrier. If
anything, I see operations people excited about learning a new technology.
Maybe I was lucky. 

Hesham