IETF Logo Mail Archive

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

Richard Patterson <richard@helix.net.nz> Wed, 15 December 2021 12:37 UTC

Return-Path: <richard@helix.net.nz>
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 812903A0FB6 for <v6ops@ietfa.amsl.com>; Wed, 15 Dec 2021 04:37:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=helix-net-nz.20210112.gappssmtp.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 8lne3asoCc6r for <v6ops@ietfa.amsl.com>; Wed, 15 Dec 2021 04:37:47 -0800 (PST)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 C25F83A0AF1 for <v6ops@ietf.org>; Wed, 15 Dec 2021 04:37:46 -0800 (PST)
Received: by mail-io1-xd31.google.com with SMTP id e128so29831124iof.1 for <v6ops@ietf.org>; Wed, 15 Dec 2021 04:37:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helix-net-nz.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=z2Zung30WqDoeZdgdqwf1fer3RIkLIaExbsuKHWoiU8=; b=SW6g/fl9DVeyUDI8hsiPZtpPwvt/3/57tbhcNnV5egBYgMuuLjoi23HXp/aweuVG28 2nPUDI/8HgoRRjVEA+afYM5uc1HH63hjHwlsGRZJgdgHSKbU0JgEPJO61emARlHfZs9e /ZLQ07DtJkhp0mXAbEqjmQH2hf9Or6HmFLWTRiHgOuCFy1rVP9bST0Tae1IHfNWrkp3N GFpgFbVGf4LVfXAVNaBCJTjHeVd5bqeREMqdjvCt2Df2mmps9cvxVqrNhF9XXGkWavR5 yuko/BkxQFgWh05OdlAcrYA4UfEze/dfeWO7m7x5+q4KdJZDzDyU6XIHTrmG0h6hGKMq BIuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=z2Zung30WqDoeZdgdqwf1fer3RIkLIaExbsuKHWoiU8=; b=6VsyB049+EVKrRA/sI3O6UFlIcBQfH05IzmKEzPeqLdY+B8DYxJ2wf1tb2GlEXex4r QciPGRL59QdIbbR+CzoPOHBkiZNCqNwNBFm/2KqE6KxPBk99Wpv/VZ6FMRG/oIkRpY8U WzeGeQ9jwcN7NTx9fsnzukvIEDtmp7cbB/ZdWhotLP5XJOAME/KWfUfrHFo9ucJJFFle cnsqJ37Vp5cEBaU6A+EEL4AbrascVCuhNFgnDqa8crGbBp6tgFLXy0q9ukDREvXrSQQ4 CXq+K0Fs9pX8TUEAMNyghTkRzfZ1VK5jUnmyTjFFkbGSqapzh3gjeUlwg8wsEnbVXy3g YLYQ==
X-Gm-Message-State: AOAM530dxD5Cy3YuSt2uYvb6jTOfhn7apFJlSobLVocIHvMwNGB01OkA bL/rVVUedAIiFQ7q2zgNpYCWBUxPp78UiQ==
X-Google-Smtp-Source: ABdhPJx59Gw7FvYMKhbJsIbi/bPD3exvBE2tKLAYUVRYqqftBnVMCMh1bP5f3qm84PITRBP/frRBEA==
X-Received: by 2002:a05:6638:3808:: with SMTP id i8mr5525586jav.118.1639571864326; Wed, 15 Dec 2021 04:37:44 -0800 (PST)
Received: from mail-io1-f49.google.com (mail-io1-f49.google.com. [209.85.166.49]) by smtp.gmail.com with ESMTPSA id t6sm987587ios.13.2021.12.15.04.37.43 for <v6ops@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Dec 2021 04:37:43 -0800 (PST)
Received: by mail-io1-f49.google.com with SMTP id z18so29822347iof.5 for <v6ops@ietf.org>; Wed, 15 Dec 2021 04:37:43 -0800 (PST)
X-Received: by 2002:a5e:d602:: with SMTP id w2mr6322365iom.121.1639571862963; Wed, 15 Dec 2021 04:37:42 -0800 (PST)
MIME-Version: 1.0
References: <CAKD1Yr0z-XckGv5L_9qu5w_6mU=O1h5nZWoTNw6GmStHQ8tzYA@mail.gmail.com> <932B1725-6BA9-4C2E-AE45-6C8DECB640B5@employees.org> <CE0D482D-667B-4CF3-A124-3CBF33DD11BA@gmail.com>
In-Reply-To: <CE0D482D-667B-4CF3-A124-3CBF33DD11BA@gmail.com>
From: Richard Patterson <richard@helix.net.nz>
Date: Wed, 15 Dec 2021 12:37:32 +0000
X-Gmail-Original-Message-ID: <CAHL_VyAOGpNpt4RSsUsUqkgnNHWGii0=hw9sf69C5qE1kpgq8A@mail.gmail.com>
Message-ID: <CAHL_VyAOGpNpt4RSsUsUqkgnNHWGii0=hw9sf69C5qE1kpgq8A@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000079cd1105d32e9206"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BDC4LzN62-3iY72dvpMTddr4GZc>
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: Wed, 15 Dec 2021 12:37:53 -0000

On Tue, 14 Dec 2021 at 23:12, Fred Baker <fredbaker.ietf@gmail.com> wrote:

> > On Nov 24, 2021, at 12:03 AM, Ole Troan <otroan@employees.org> wrote:
> > IPv4aaS != IPv6 only
>
> I would agree; IPv4aas is a way of providing IPv4 in a network that
> doesn't implement it.
>

Context is key, is someone talking about an IPv6-only packet flow, or a
particular device or service in the network?  Are they talking about the
control plane or data plane?  If it's not clear, ask them for clarification.

It's a matter of perspective, from an IPv4aaS end-to-end packet flow, of
course there's IPv4 in the mix, but the Access Node won't see any frames
with 0x0800 ethertype, so from my Access Team's perspective, the service is
IPv6-only to them.
Likewise a BNG requires no DHCPv4 server configuration or IPv4 routes, and
RADIUS only needs to keep track of IPv6 address family sessions...... and
so on and so forth.

IPv4aaS != IPv6-only *from an end-to-end packet flow perspective*.

-Rich

v2.23.0 | Report a Bug | By Email