IETF Logo Mail Archive

Re: [v6ops] Updating RFC 7084 - alternate logic

Gert Doering <gert@space.net> Mon, 05 December 2022 14:16 UTC

Return-Path: <gert@space.net>
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 1FC75C14CE21 for <v6ops@ietfa.amsl.com>; Mon, 5 Dec 2022 06:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=space.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0nSNahsu70Xp for <v6ops@ietfa.amsl.com>; Mon, 5 Dec 2022 06:16:03 -0800 (PST)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0166C14CF09 for <v6ops@ietf.org>; Mon, 5 Dec 2022 06:16:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1670249764; x=1701785764; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=tg5aOUDEW2w9sutKqp2vAtSxe4WSrYKsp8UfbZk9yao=; b=W47kFlrsAJU0Qhl4lajY5lVH0lHNC97yeHHokZ9nYbpy7B7q7EQ7G05M e7M8WSmKOXec28WFzSWtjdeZ75TO4imZUaoXYNHmR8xlUH0KJk1dmjirm ptKzqawHQed9G3tpwTHcaDDChB2heQVneIFzsEGHjF6/WjJd7W0RASLR8 9oQ9V6HL0aUuC2GOlDe/dVKfpU9d9I6XLX+r3tT6xusVITlh2Xcaf/I88 0Qj3Gm7nQY4AzYzrvQl3SzqYfSfd9t3QosTWLgqLYrea2TzNuAzvWr1C8 9eytePaBGF0fLnonwXJtFgCvQCNSA9eTfw6X83xPaNaTaamlrW9OtxIqu g==;
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Dec 2022 15:15:59 +0100
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 18C8241FF8 for <v6ops@ietf.org>; Mon, 5 Dec 2022 15:15:58 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id ED41640C06; Mon, 5 Dec 2022 15:15:57 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id E4624110A0C; Mon, 5 Dec 2022 15:15:57 +0100 (CET)
Date: Mon, 05 Dec 2022 15:15:57 +0100
From: Gert Doering <gert@space.net>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Gert Doering <gert@space.net>, Esko Dijk <esko.dijk@iotconsultancy.nl>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <Y439HZAYY540zT2O@Space.Net>
References: <CAJgLMKs=CTBAdW=-GaFT+j+rjnd=sdDe6ytoqpZhYE1KW29jUQ@mail.gmail.com> <CWXP123MB51634A6A6D20796AE43A6207D3159@CWXP123MB5163.GBRP123.PROD.OUTLOOK.COM> <db23f437-7dd8-ad24-0c72-e3164dd43f4a@gmail.com> <CWXP123MB516311D9A5E90628BC8E8FD2D3149@CWXP123MB5163.GBRP123.PROD.OUTLOOK.COM> <DU0P190MB1978713EFCC2841F4B762F05FD149@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <5782557e-e2d8-48c0-b75c-d67d7e6cb228@gmail.com> <DU0P190MB19782F86F06A030BD9AC4836FD189@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <9169a670-1141-d688-fd7c-68f06c221378@gmail.com> <Y4313SQDIpYMfclu@Space.Net> <ee4c1b38-d25a-62e2-f815-71aa0e368b9e@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="fF2xzD8oETu8ICpD"
Content-Disposition: inline
In-Reply-To: <ee4c1b38-d25a-62e2-f815-71aa0e368b9e@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Eh3K-bHE2CqkY-H4t-AvMi824Ng>
Subject: Re: [v6ops] Updating RFC 7084 - alternate logic
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 05 Dec 2022 14:16:08 -0000

Hi,

On Mon, Dec 05, 2022 at 02:57:28PM +0100, Alexandre Petrescu wrote:
> But it is not that straightforward.

It is :-)

> For that to work, one possibility would be a for the AP in router mode 
> to run a DHCPv6 Relay.  But as far as I know there are no WiFi access 
> points that run DHCPv6 Relay software.

If the "AP in router mode" wants to do routing, and IPv6, it needs
to understand prefixes left *and right*.  So for the "right side prefix",
it needs to speak DHCPv6-PD anyway, to get a prefix assigned from the
ISP router.

In IPv4 land, all these "things in router mode" will just do hierarchical
NAT44, but that's not how you do IPv6.

> Another possibility would be that the snac router is precofigured with 
> the address of the DHCPv6 server (ISP's inhome router), so it does not 
> need to discover it across IP hops, because multicast discovery across 
> IP hops does not work.

You cannot do DHCPv6-PD across a non-participating intermediate router,
because that router needs to add forwarding entries.  And no, "having
a routing protocol on the right side" is not *less* complicated than
just having DHCPv6-PD support.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

v2.23.0 | Report a Bug | By Email