[v6ops] Re: Dynamic addresses
Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 16 August 2024 22: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 57B2CC15109E for <v6ops@ietfa.amsl.com>; Fri, 16 Aug 2024 15:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SVC0ceKctmgr for <v6ops@ietfa.amsl.com>; Fri, 16 Aug 2024 15:05:23 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEF88C14CE31 for <v6ops@ietf.org>; Fri, 16 Aug 2024 15:05:23 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id d2e1a72fcca58-710d0995e21so1989928b3a.1 for <v6ops@ietf.org>; Fri, 16 Aug 2024 15:05:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723845923; x=1724450723; darn=ietf.org; h=content-transfer-encoding:in-reply-to:cc:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=VFQSdv3lWDLl9lTdbdqhsAVpH9+rQH16E5JEzEO5O+0=; b=a1XkDHK28YXR8GAy35oOD8R0UBvShCjpD0TRy8fIbS3Iw9yLCQ8/jrwP7tfNI/ZfTq H4yq0s459sQt75dlv1xq4MD1KgIq4EV+tszqpNCfAvU1QTj/9UYChOMOIhL36TAjMqCh nSEXMMmktPvNK0Ge1L3IqeHn/DHCo2l2lkm1Oo42ESqj4AbIIDCsZD99045yQnU1hjhM xnaAV+bLXTGKs8sRT0CEmfVyc8BBfi97HTNNGK6E/JTJPW0uuYp3Xifr/GqFO656qbFk G23mTe4Kxzb1ZvGNYs5a2i4kunArPnjV1l6UmCOwx89oYDEEyIwYlDcmpj6+wgzgXR2m 1DNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723845923; x=1724450723; h=content-transfer-encoding:in-reply-to:cc:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=VFQSdv3lWDLl9lTdbdqhsAVpH9+rQH16E5JEzEO5O+0=; b=dwY/mKxCG11OWpM6b8rWrvjTdAiBPJcwusaAkJfSdwztgHOQl0L1xVU+gp+afg7Pxw gFWQ4iuF47VjIgF60FfLf27TckryJFsnjyvIKplxXHk0po3+86vXrYdkEOnInjqJ/Llc kojyEzQZFMB8sLNWfMxEa7LSx/nzWurBb6deA2caBphg1D8JCab3E26TSQK0tuuhCclT e2PaAHXbr92MG1fBRDxO73atN1uMqFTJaV69AGq1CFw3ASgF0yVYxl7ShAiG056GcpnS 6MLNvaOiawVZhFEqOxoW1hXbYLwbdDKc+tdwAoGsi14rZVpwD14LKNvvilVGrH+yWuyv mFPw==
X-Gm-Message-State: AOJu0YwyYIbI1r/OHA1IowqpRdwn8kW49QS9/J6BMDEi5KpasdnRXWS1 Acmdj3tsuWrzTN2y4519F+Xq2AEq4pB9ZDDENquN293x/llsbiD5
X-Google-Smtp-Source: AGHT+IGtWlg9hBUOixpp707KAJ3W5Y1ZCK3VACbWhcyudp7RFPOdipPGLcXdLxND8jHi0RISODMhrg==
X-Received: by 2002:a05:6a20:6f05:b0:1c4:d5f6:867e with SMTP id adf61e73a8af0-1c90502fc16mr5372301637.34.1723845922951; Fri, 16 Aug 2024 15:05:22 -0700 (PDT)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7127aef610esm3054994b3a.129.2024.08.16.15.05.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 16 Aug 2024 15:05:22 -0700 (PDT)
Message-ID: <c0bc6540-81e3-4871-84bf-7a7199d4782f@gmail.com>
Date: Sat, 17 Aug 2024 10:05:18 +1200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: N.Leymann@telekom.de
References: <df01e0f8-1b0d-4792-be2c-89a59da7de49.ref@swbell.net> <CAPt1N1=rQp5U4_X=2WvCV358S9Qm+E+_+gs_mgUJHP_68dYLmg@mail.gmail.com> <d16406c6-e5d9-4aa4-a16e-7513d04d6b07@gmail.com> <CACyFTPEdh_SL3BJ6WcD18tpYzH=Q6gxYnXanTsHZxF4xQm7LuA@mail.gmail.com> <19b076c0-ff57-471a-8f66-6ad47d7169f4@gmail.com> <f469fd02-f67e-4aa3-80e1-e055e63fadd2@swbell.net> <CACyFTPGNUvKkF+hxg1xJPSRNWo4aZN+jtwO3GeMLmQ1pTY8x3g@mail.gmail.com> <CAPt1N1kLTuKjtvsJ5qGd_kjnc8K2HDc7OemMqtaSavGH6kAqJA@mail.gmail.com> <CACyFTPEjAq0kGHFwiNnqsmyhxavu6HhEBu6X7OQXAgaKpPqa1g@mail.gmail.com> <CAN-Dau05Q2GVydUb8DLfAXYNEtrKPkTFROOWT3cDMr5DSPD8Tg@mail.gmail.com> <a0134031-ce09-4c9e-ab8a-4789f889b4ef@nsrc.org> <CACyFTPHCG5EyjPwFDxqpj2oAW2R3xMnVBZdaQz9n2Et1pNMPUg@mail.gmail.com> <BEZP281MB20089D60D9C0CB7AE179698598812@BEZP281MB2008.DEUP281.PROD.OUTLOOK.COM> <CAN-Dau2sw+Jwcgxn=KhGicM-gpQpO8eY+11sBs4Q=QjCkV6BBQ@mail.gmail.com> <FRYP281MB20108151C6BDADB2A6FC2DC298812@FRYP281MB2010.DEUP281.PROD.OUTLOOK.COM>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <FRYP281MB20108151C6BDADB2A6FC2DC298812@FRYP281MB2010.DEUP281.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Message-ID-Hash: FNNC67WS3UTAEDEYSLXUGJNZ4DM7YD4N
X-Message-ID-Hash: FNNC67WS3UTAEDEYSLXUGJNZ4DM7YD4N
X-MailFrom: brian.e.carpenter@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: v6ops@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: Dynamic addresses
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UQXAST9XqPLtBbNInLRBxNDyWzI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>
On 17-Aug-24 03:55, N.Leymann@telekom.de wrote: > Hi, > > In our case new addresses are re-assigned (changed) in case the CPE disconnects from the network. Customer here (but not of telekom.de): Yes, my ISP used to do that, back when I was on ADSL. When the cable under the road became faulty due to water penetration, the CPE was disconnecting frequently, especially after heavy rain. So my v6 prefix was bouncing around. *Horrible* user experience; quite unacceptable (and of course voice service was disrupted too, so calling the hell desk was no fun either). Please change and follow BCOP 690. My ISP eventually did so. Brian > > This can be either caused by reboot, link failures, within a maintenance window, you name it… In addition > > some of the CPEs offer the option to change IP addresses regularly (e.g., once a day) for privacy reasons. > > Besides that, the addresses are stable. If there is no reconnect and/or privacy feature active they > > will change once or twice a year. > > regards > > Nic > > *Von:* David Farmer <farmer@umn.edu> > *Gesendet:* Freitag, 16. August 2024 16:46 > *An:* Leymann, Nicolai <N.Leymann@telekom.de> > *Cc:* contact=40daryllswer.com@dmarc.ietf.org; brian@nsrc.org; jmultach@swbell.net; v6ops@ietf.org > *Betreff:* Re: [v6ops] Re: Dynamic addresses > > > On Fri, Aug 16, 2024 at 05:45 <N.Leymann@telekom.de <mailto:N.Leymann@telekom.de>> wrote: > > Hi, > > *Von:* Daryll Swer <contact=40daryllswer.com@dmarc.ietf.org <mailto:40daryllswer.com@dmarc.ietf.org>> > *Gesendet:* Montag, 12. August 2024 06:07 > *An:* Brian Candler <brian@nsrc.org <mailto:brian@nsrc.org>> > *Cc:* The Multach's <jmultach@swbell.net <mailto:jmultach@swbell.net>>; v6ops@ietf.org <mailto:v6ops@ietf.org> > *Betreff:* [v6ops] Re: Dynamic addresses > > Getting a new IPv4/IPv6 allocation on session disconnect and reconnect > is a matter of network design. If the network design is that aggregate > address pools are routed to BRASes, and the end user's address is > allocated by the BRAS from its pool, then when you reconnect to a > different BRAS you'll get a different address. So be it. > > > Yeah, they/we typically route an aggregate pool to the BRAS/BNG. But also, > > > they are configured in HA mode with VRRP etc and the pools do not change. > > If they did change, we now have the problem with connectivity stability again, > > > and this brings up the old conversation about DHCPv6 HA (vendors solved it, > > > to my knowledge, using proprietary software). > > That’s what we are doing as well. We aggregate on the BNG and assign addresses > (IPv4 and IPv6) from the address pools of the BNG. For residential users > those addresses are dynamic. > > For business customers requiring a static address/prefix we backhaul them > to a different set of BNGs providing static addresses. Those BNGs have > their own pools for static assignments and allow to use the same, static address > even in case users are moving within our network (e.g., from one city to > another city). > > On one level, this seems reasonable; static customers pay more for the extra backhaul service to different BNGs with static pools. I understand that, and it appears acceptable to me. > > Regular customer addresses can change, and that's acceptable on one level. But how often do they change, and what triggers these changes? Is it simply due to rebooting and acquiring new addresses with each reboot? Or does it occur during customer rebalancing events, where the BNGs for some customers are changed, probably in an overnight change window? I'd like to know the frequency. > > While you can change their addresses, even regular customers deserve care and stability. Their addresses shouldn’t be altered haphazardly, too frequently, or unnecessarily. > > With my ISP, when I reboot, I usually get the same address. However, my address changes occasionally, I estimate once or twice a year. It is primarily stable but changes infrequently, which seems reasonable to me. > > There likely needs to be a service distinction between the statically addressed business class and the dynamically addressed consumer class customers. But there is a difference between a dynamic where addresses are changed occasionally, like once a month or less, and a crazy dynamic where addresses are changed haphazardly on every reboot or an overly frequent basis, like every few hours or daily. > > Thanks. > > > _______________________________________________ > v6ops mailing list -- v6ops@ietf.org > To unsubscribe send an email to v6ops-leave@ietf.org
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 The Multach's
- [v6ops] Re: Dynamic addresses Jatin
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Timothy Winters
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 The Multach's
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Timothy Winters
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Daryll Swer
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Ted Lemon
- [v6ops] Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses The Multach's
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Ted Lemon
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses Ted Lemon
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Ted Lemon
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Brian Candler
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Brian Candler
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Tim Chown
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Erik Auerswald
- [v6ops] Re: Dynamic addresses George Michaelson
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Daryll Swer
- [v6ops] Re: Dynamic addresses N.Leymann
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Tim Chown
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses N.Leymann
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Ted Lemon
- [v6ops] Re: Dynamic addresses David Farmer