Re: [Int-area] Google Statistics for IPv6 adoption.

Steve Crocker <> Sun, 16 April 2017 17:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 53ACB127775; Sun, 16 Apr 2017 10:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tznRhHyQNMcl; Sun, 16 Apr 2017 10:02:28 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EB05D127735; Sun, 16 Apr 2017 10:02:27 -0700 (PDT)
Received: from; Sun, 16 Apr 2017 17:02:27 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_2C966588-8643-4E8B-80E3-A977A81DCD37"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Steve Crocker <>
In-Reply-To: <>
Date: Sun, 16 Apr 2017 13:02:25 -0400
Cc: "Stephen D. Crocker" <>, "" <>, "" <>, "" <>, "" <>, "" <>
Message-Id: <>
References: <> <> <> <> <>
To: Khaled Omar <>
X-Mailer: Apple Mail (2.3124)
Archived-At: <>
Subject: Re: [Int-area] Google Statistics for IPv6 adoption.
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 16 Apr 2017 17:02:29 -0000

There was a flag day for the transition from NCP to TCP/IP.  There will never be another flag day.  Any transition solution, whether from IPv4 to IPv6 or a successor protocol elsewhere on the stack, has to be designed to permit overlap and interoperability during the very long period when both the old and new protocols will be operating.

Further, there will have to be two incentives at work for the transition to succeed.  One is in favor of the the new protocol.  The other is against the old protocol.  If the former is missing, the new protocol won’t be adopted.  If the latter is missing, the old protocol will persist indefinitely.

To repeat: there will never be another flag day.  If this is one of your assumptions, step back and think about the problem again.


> On Apr 16, 2017, at 11:15 AM, Khaled Omar <> wrote:
> That's right, and there should be a place like the IETF that should organize this process until all technology companies prepare the updates and there should be a flag day for the deployment,
> If a host still not updated, will not gain access to the Internet until updating the OS.