IETF Logo Mail Archive

Re: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?

Fred Baker <fredbaker.ietf@gmail.com> Tue, 14 December 2021 23:12 UTC

Return-Path: <fredbaker.ietf@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 5E6B23A0B58 for <v6ops@ietfa.amsl.com>; Tue, 14 Dec 2021 15:12:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 PYD7BvvuraG1 for <v6ops@ietfa.amsl.com>; Tue, 14 Dec 2021 15:12:03 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 B8A6B3A0B54 for <v6ops@ietf.org>; Tue, 14 Dec 2021 15:12:03 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id m24so14787937pls.10 for <v6ops@ietf.org>; Tue, 14 Dec 2021 15:12:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZxrMXkjqP8L0966rb9W7NIEaMYYbEybDyhg30y7nJgA=; b=eLJ1Gch9dEoyLcSuKhNtxe2wDBYbRHhe3Tft0OlgMdlKlfcakZDW2vycP1Bk5EGRTd 6xA0oKUr+25ikKgy2TnclGNkgaTO+t6rBGevPjCa9dXLcmDREVGNW9Gt2Mzhg8o3XDae rp6b5ujUcHd4IAVD0a1qOAAo5H+XvXSBDm3l323YA2XI6nI8wdxF6hXEQlXIJDIv4Mr7 msvrEeZrH/8p3R1H66BVLcgSu8chf6JtudBisl5Avr5fML7DA1QH01nII4wyl5PcRknQ f+lmdj63p72zvaL8C1LoskzIKOCoSLa+3irkb0UO0a3QtQQnbm95EzYxGXgDgDOfRVYG RacA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZxrMXkjqP8L0966rb9W7NIEaMYYbEybDyhg30y7nJgA=; b=FnJWTTcGmTGd+FgO2e1Awil91CdjeWlkworjhIGU3dw2aL4WX7H5oieEbqSF+QiibQ nUN3imLyryzrUhkgUpcHLm/RzsmtuuPIXLSVoNMZ82tX+RS9IsvaLWFmFm89N1fdVhVr QTXdA/gpjQnkun/o6bPDYnWiNcgc3KyVjJ/Zr8/f6O4IiKAATF7EZu5hdbkRD1Dbmx0H N0cmxT9Pt3NhKKqyVC1/UPLw42tsHX+FsaSVwfrlacbcGWywI/Hp0qoxdulPPRS66B6S Zj04vpHRkl0PfvSa4Ip9+IQeucTan3R7C55th1i13vUXAHUK0bePmK4vMwQXj08zQZed kKCw==
X-Gm-Message-State: AOAM530xrPiwwuHKfdxbN8A9sNmiVKYGDCtYv9kTstz/5LFdAMvOD1Vz cH5Jc0e5Sfhl1o9kqgUtNaOLU498jJk=
X-Google-Smtp-Source: ABdhPJzObyhb22AfW9FIXOGCr1PO8JJhHwn4DlRSYD2Rha82IQbNYQ87oBHrwrvAZjaJ98L4eGvM4A==
X-Received: by 2002:a17:90b:4b4c:: with SMTP id mi12mr8619021pjb.66.1639523522132; Tue, 14 Dec 2021 15:12:02 -0800 (PST)
Received: from smtpclient.apple (ip70-185-177-201.sb.sd.cox.net. [70.185.177.201]) by smtp.gmail.com with ESMTPSA id d12sm153784pfu.91.2021.12.14.15.12.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Dec 2021 15:12:01 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <932B1725-6BA9-4C2E-AE45-6C8DECB640B5@employees.org>
Date: Tue, 14 Dec 2021 15:12:00 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE0D482D-667B-4CF3-A124-3CBF33DD11BA@gmail.com>
References: <CAKD1Yr0z-XckGv5L_9qu5w_6mU=O1h5nZWoTNw6GmStHQ8tzYA@mail.gmail.com> <932B1725-6BA9-4C2E-AE45-6C8DECB640B5@employees.org>
To: Ole Troan <otroan@employees.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/xG9IuvDwNh8YxlYfXgYlPuYMfug>
Subject: Re: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?
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: Tue, 14 Dec 2021 23:12:09 -0000


> On Nov 24, 2021, at 12:03 AM, Ole Troan <otroan@employees.org> wrote:
> 
>> On 24 Nov 2021, at 03:26, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org> wrote:
>> 
>> Is there any data on what IPv4aaS transition mechanisms are deployed by ISPs today? I was approached by a router vendor asking me "how they should provide IPv6-only" and I was looking for data on which mechanisms are most common
> 
> IPv4aaS != IPv6 only

I would agree; IPv4aas is a way of providing IPv4 in a network that doesn't implement it. Something-over-IPv6 is a set of ways to do so; it could be done with Bluetooth Low Energy, MPLS, or any of several other things. My suggestion would be:

   - first, make sure you can run IPv6-only. Turning IPv4 off can be harder than you think. 
   - second, ask yourself what you mean by that. Do you want to run IPv4 in tunnels *over* an IPv6 network connecting edges? Do you want to connect an IPv4-only host using an IPv6 network to connect to another host somewhere else? Second, read section 4.3 of https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-ipv6-deployment.
   - You might look at RFC 6333, DS-Lite.

v2.23.0 | Report a Bug | By Email