IETF Logo Mail Archive

Re: [v6ops] Some comments on draft-ietf-v6ops-ipv6-deployment

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 22 April 2022 20:05 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 526773A14DF for <v6ops@ietfa.amsl.com>; Fri, 22 Apr 2022 13:05:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WdVoTMJZlcsC for <v6ops@ietfa.amsl.com>; Fri, 22 Apr 2022 13:05:52 -0700 (PDT)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5BAF3A14DE for <v6ops@ietf.org>; Fri, 22 Apr 2022 13:05:52 -0700 (PDT)
Received: by mail-pl1-x629.google.com with SMTP id h12so9467573plf.12 for <v6ops@ietf.org>; Fri, 22 Apr 2022 13:05:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=+aWb3CmKbH/fypu60UE/GhL0iYz/qsubb6OrDJPqZWo=; b=WhQffS8odbwfJZauLDLo6jJQ3iBcFjq8/Ac4RblPLuSa6XDj8kd+nKWOaXTvCdMC7m MjLIINYYTMVaEPZ4SKYbB1J1SdyCBRpnyIhUa3J16LypoxnD/q/KVNfK60OqyD/WVWhr suKtU4ZV+16C4PLTrLJKlmRbBE1ILBKEBPQr6/a2iBIe+jpRwD1iQ8JwGxad793RAC7J ZeBFhxkukvKkUVbS0MzZ/VV+7s2XkIto6vTRDRUtcEAuOyvuBDCjpjdD3fIWFUrNEuCg rpcbBXGo+/sxd2iOCvyKoEUG9iYJjz7S/WT4nReZfsSjTslpZelqEJG4vGoWQd8FZDSY cp0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+aWb3CmKbH/fypu60UE/GhL0iYz/qsubb6OrDJPqZWo=; b=VSDSfKnO15xi9mHLaD1UuX+86NCQ5D9UHv7Uwo4OyIhRguKiWEn9/+Gir5vzzuXhpl rWE+k/nbo8ov/hJB4B7MqnLCCNhvnxQmpXHDdUvQeR36HGpMnO9EP9Gl4llxiyjUeEqU DRiS1XT5z2CcxMDh1lFaQhI57IrEnezCKZuF4tRqDYrpD9u+hOLHMT/YGJmVO65N/YA6 EKbwcPXOreziCDEiLPKOzHY0gR8oY5BY0pAB1pJ03l8QafbN4Kdyhv7cEbajYA1Y99p9 xzSqQLjvaO4NeOM7p9QgfPl8gzV0t3+KGZDva4lX51idZLWqvCFEhyGD4W+Vs+L52NvV EIMA==
X-Gm-Message-State: AOAM532uugRifRo8tCcJMZdUUub1FGV4ExSqB8tzzx3VN2u/H1OwJ6ot U4PPdkghTnTH+MBFiXCIqSZZCceJvsaekGsu
X-Google-Smtp-Source: ABdhPJzcO50yju4aXvh1KL5bE7BcS52udSkfuONmoljlhFAQeiziAYc45aBgvxclI0BuWabcEGDXzA==
X-Received: by 2002:a17:902:9b87:b0:156:bf3e:9ab5 with SMTP id y7-20020a1709029b8700b00156bf3e9ab5mr6244927plp.119.1650657951675; Fri, 22 Apr 2022 13:05:51 -0700 (PDT)
Received: from [10.248.23.127] ([125.168.223.160]) by smtp.gmail.com with ESMTPSA id y5-20020a17090a600500b001cd4989ff62sm6979782pji.41.2022.04.22.13.05.49 for <v6ops@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 22 Apr 2022 13:05:50 -0700 (PDT)
To: v6ops@ietf.org
References: <3008655b-2af6-7df0-1302-63cf81bad8b4@edgeuno.com> <9064DD1F-48F4-4A17-BDEC-72C0308B9314@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d920b82b-d6cf-b91a-ae92-981973342120@gmail.com>
Date: Sat, 23 Apr 2022 08:05:46 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <9064DD1F-48F4-4A17-BDEC-72C0308B9314@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3lRn3uTFYJEgfs9nUneFeZpAUB8>
Subject: Re: [v6ops] Some comments on draft-ietf-v6ops-ipv6-deployment
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 22 Apr 2022 20:05:56 -0000

On 23-Apr-22 07:23, Fred Baker wrote:
> 
> 
>> On Apr 22, 2022, at 4:48 AM, Fernando Gont <fernando.gont=40edgeuno.com@dmarc.ietf.org> wrote:
>>
>> Isn't IPv6 *fully* incompatible with IPv4?
> 
> I hear this a lot, and I think it's backwards, because it leads one to the presupposition that if only <something> had been done differently, IPv6 would have been backward-compatible with IPv4. "Those stupid people" and all that.
> 
> No, IPv4 isn't forward-compatible with *anything*, even putting some set of bits into IPv4 options. Backward-compatibility implies that the new capability can be deployed without changing any existing systems. What could have been deployed without changing all of the existing-and-deployed systems to accommodate it?

Yes, it might be worth a carefully written paragraph explaining that it is IPv4's fault that IPv6 (or any other IPng whatever) is not "compatible".

    Brian

v2.23.0 | Report a Bug | By Email