Return-Path: X-Original-To: ietf@mail2.ietf.org Delivered-To: ietf@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4A4E61000543D for ; Fri, 12 Jun 2026 03:54:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781261672; bh=txn9i9r6LMvHRBg546s4u9ylZigTRqh7++Mqgq6rWWQ=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=WwL97zS7Fsqpv2AIjGH2De2vpGANQxKwbI+J+SNGkBzeMeXaKVEDQOND5XjiRaqot NmP9FrKJusIYRYXDuOorHNQIoC6LjAO4BmsJMGdJT6b8m6bZ9EAPvQj32LyWkx4MoV INdRtAXZMyNY0UWuetIw43ugjxhgsHCqBsHGCF8A= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AC1VCmkAR5qS for ; Fri, 12 Jun 2026 03:54:30 -0700 (PDT) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 mail2.ietf.org (Postfix) with ESMTPS id 7F1A81000542B for ; Fri, 12 Jun 2026 03:54:30 -0700 (PDT) Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-68acf0a15b3so1369878a12.1 for ; Fri, 12 Jun 2026 03:54:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1781261669; x=1781866469; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=MDXQ8sV2+uGdtlUHTKUWfoxhBJywML9pMOnKTEOgoEY=; b=Znxp7Cw6ZO7Mci9EwAdsc71Gxw6rRJdV7WHyqdS+SdXkMKH7Nt9zJ09jJlVWt8Yl7F XGYxBq+GG4T6krBX8Q9OgeOuem1YQsDjo29DdEHoLdak4dq2Sz9BGmKw5UJ9/DvuLwBs pI7vvMVslzsI6xwNUjVmVgJgK3fY0p1u6+NFnuv7qNU5/pniKni2wVLIj3ANo6y3ksDl 6F+SNTozfElHai3H5tBDw1Md7+m+MZShHHhoSErtdQ4tQnMtw/i6EXnFHVmznC5eS42x wM0tTmp2TAJvjCx7jCJsn4UN40KpTIURt81Y7VWdfq5bh1YEpvIy++NtjBqqROtHTp71 B/Gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1781261669; x=1781866469; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-gg:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=MDXQ8sV2+uGdtlUHTKUWfoxhBJywML9pMOnKTEOgoEY=; b=hYjRNhIu37To6TCfqcvVQj8Rnqz5a0c1FBLsKfj9kN17nzjuBPZ8TZl417VJjfILpY tk8eTI8m/a7iARsh5WdRCHF5KbZ5OMXq/x5ehHND1Lvs45Rihd4nGW8wct2coMKx8dLW MccWYnd40R0CWuBQzSM1jVBeriJA8isFTWbo8VmhGx+JKMs9y7VG7ouIvThxbZefXw2J 4fwx//jzn/R9uFqQ74c1PBEzhoAWGRNfbDmrP/LKTQuF6NVtjgSqgTVejjFHHwLa9VhM ZqRN8LX8UNP8zXIkA4t9qpkF4SzJIlZElsiGNTUBh6cNr2zr2bhPoDvPONXPXiugGTS9 LuGQ== X-Forwarded-Encrypted: i=1; AFNElJ+fEpMggUyQOwvDINy61bsX3IIj1LhKAOpVXF0sqQbuWoqoh8b5rU3E6C5KGqpNHp9tZcdS@ietf.org X-Gm-Message-State: AOJu0Yx6Ku4W8JButXRtun4Se30j8x+cwKnSHyrea7dmmqy5IkNNs3tu aMenHRKBKSHt8XrBsla4OM40OY6ZhJKQ61F4TzpH9vW4gRsKmznwtflZ X-Gm-Gg: Acq92OGG37UcxESG6I1BPBBX5zJGy/lchk5UKsKyakioIjq6DS8wMNWit8wrvqmJvYc xaXLMx6JWIodevII+M4YhS0H4t2vW2e3YJ7LWp+OUr9YZsK8kyaARylRSJs/IcljFFaSpCcHzCM 5UbhJs2MH2/6irUKmQrAf0fOf8po0jlGYk8GSunnDAAHYBGfEZ93RotkW2PAvg5XtlQsFU9kGW9 OXwQgmNSM9WnJL7nJhZwPfItyqHKFlXFdGRLjjFKNhiNwCG0O6FwSa4nuxCS7fr50G6OnVY+xCx qdQ/IEQmw2f/J+gx4Gv18PbgUc6ZMuU40a5rUhgFq/5PgiolnhnakbMax9YmBAs1BSVe1FQmknk i6L9kixzSWwVHoVXTGe11Mc1QxHqMqTWGGUP5KhX/bRr1Yp1JfAezP188fl4RA7lgmC9PaAwkXt W35Aux0Vj15Yx70j//xq+fro/ryJQmwKC6CFZcpjvkCi+ox5uwiO6VtI4c3t8trA== X-Received: by 2002:a17:906:8a66:b0:bed:e575:d54d with SMTP id a640c23a62f3a-bfe2b0f3c26mr73781866b.42.1781261669096; Fri, 12 Jun 2026 03:54:29 -0700 (PDT) Received: from smtpclient.apple (5f220210.bb.online.no. [95.34.2.16]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-bfdb8b1bb64sm93931866b.52.2026.06.12.03.54.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 12 Jun 2026 03:54:28 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-83CDE0C6-80B6-4879-9A66-073D051BCA3C Content-Transfer-Encoding: 7bit From: =?utf-8?Q?Ole_Tr=C3=B8an?= Mime-Version: 1.0 (1.0) Subject: Re: [v6ops] Re: [Witarea] Re: How to make an elegant IPv4 outage Date: Fri, 12 Jun 2026 12:54:16 +0200 Message-Id: <7A4223CC-8480-4DF5-AFC3-C805DC42DD17@gmail.com> References: In-Reply-To: To: Tim Chown X-Mailer: iPhone Mail (23F77) Message-ID-Hash: E7SJDWT54AGNS3QMTYLZU2XPVEUB7AH6 X-Message-ID-Hash: E7SJDWT54AGNS3QMTYLZU2XPVEUB7AH6 X-MailFrom: otroan.ietf@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Phillip Hallam-Baker , Franck Martin , Philipp Tiesel , Xipengxiao , S Moonesamy , witarea , ietf , v6ops X-Mailman-Version: 3.3.9rc6 Precedence: list List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --Apple-Mail-83CDE0C6-80B6-4879-9A66-073D051BCA3C Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Tim, =EF=BB=BF > Well, that=E2=80=99s 6man, this is v6ops. If bad operational procedures a= re followed, we should highlight those with pointers to the good. Doesn=E2=80= =99t have to name names I suppose. You could. But it=E2=80=99s a world of inconsistency. DHCPv6 PD lifetimes wa= s recommended to mirror the lifetime of the customer contract. But then you g= ot into issues with state maintenance on intermediate routers, and ended up w= ith short lifetimes, so RR has no visibility into the actual lifetime of the= prefix.=20 Then providers raised the issue of rebalancing customers between eg CMTSs, w= here maintaining the same prefix has a cost. And I am sure a desire for tiered products.=20 A combination of ipv6 protocols, business practices and operational reality.= Ole >=20 > On 12/06/2026, 10:48, "Ole Tr=C3=B8an" wrote: >=20 >=20 > Perhaps we need to start draft-v6ops-ipv6-dinosaurs and start to name and s= hame such organisations and what they=E2=80=99re doing wrong=E2=80=A6 polite= but objective critique and pointers in the doc to best practice. >=20 > It may produce a better outcome if we instead focus on fixing the gaps in i= pv6. =20 >=20 > Ole >=20 >=20 >=20 > On 11/06/2026, 21:03, "Phillip Hallam-Baker" wrote= : >=20 > Just got off the phone with a very large ISP after a failed attempt to get= an IPv6 address. >=20 > Turns out that I can have IPv6 but only dynamic and only if I am on dynami= c IPv4. I cannot get IPv6 for my service with static IPv4 addresses. >=20 > Seems to me that we are still a long way away from being able to shutter I= Pv4 completely. >=20 > What I have not yet tried but should is trying to use the IPv6 mapping of m= y IPv4 addresses. > _______________________________________________ > v6ops mailing list -- v6ops@ietf.org > To unsubscribe send an email to v6ops-leave@ietf.org --Apple-Mail-83CDE0C6-80B6-4879-9A66-073D051BCA3C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Tim,
=EF= =BB=BF
Well, that=E2=80=99s 6man, this is v6ops.  If bad operational procedure= s are followed, we should highlight those with pointers to the good.  D= oesn=E2=80=99t have to name names I suppose.
You could. But it=E2=80=99s a world of inconsistency. DHCPv6 PD= lifetimes was recommended to mirror the lifetime of the customer contract. B= ut then you got into issues with state maintenance on intermediate routers, a= nd ended up with short lifetimes, so RR has no visibility into the actual li= fetime of the prefix. 
Then providers raised the issue of reb= alancing customers between eg CMTSs, where maintaining the same prefix has a= cost.
And I am sure a desire for tiered products. 
A combination of ipv6 protocols, business practices and operational reality= .

Ole



On 12/06/202= 6, 10:48, "Ole Tr=C3=B8an" <otroan.ietf@gmail.com> wrote:


Perhaps we need to start draft-v6ops-ipv6-dinosaurs and start to name and sh= ame such organisations and what they=E2=80=99re doing wrong=E2=80=A6 polite b= ut objective critique and pointers in the doc to best practice.

It may produ= ce a better outcome if we instead focus on fixing the gaps in ipv6.  

Ole



On 11/06/202= 6, 21:03, "Phillip Hallam-Baker" <phill@hallambaker.com> wrote:

Ju= st got off the phone with a very large ISP after a failed attempt to get an I= Pv6 address.
Tu= rns out that I can have IPv6 but only dynamic and only if I am on dynamic IP= v4. I cannot get IPv6 for my service with static IPv4 addresses.
Se= ems to me that we are still a long way away from being able to shutter IPv4 c= ompletely.
Wh= at I have not yet tried but should is trying to use the IPv6 mapping of my I= Pv4 addresses.
_______________________________________________
v6ops mailing list -- v6ops@ietf.org
To unsubscribe send an email to v6ops-leave@ietf.org
= --Apple-Mail-83CDE0C6-80B6-4879-9A66-073D051BCA3C--