From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4A7E93B29D for ; Tue, 25 Oct 2022 23:30:22 -0400 (EDT) Received: by mail-wm1-x32b.google.com with SMTP id v130-20020a1cac88000000b003bcde03bd44so539404wme.5 for ; Tue, 25 Oct 2022 20:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mhi4njS8q6MlE5FklCQmooC+vfv0s86qisDMHXePPMs=; b=JeagenbDPAonbRaqLoVIjJrzW25LC+xX8M6VSN4BTdH4++rcgE4jsagHHpIeQcGw5q S8qw+rDRQjlEj3EcHtbS6E4bhHxahEfObY3v+B2guFY2Qc4ykgVF7irUS/oHcjjj9myx LU4WQEX+VC7Vq1ljYyjh2Hc2Eavq06iVNJHX/aiABVHeaLnZqXTgVfBZgHchg9NtlGvq cczmhlg8Ti4ehLWCIrejdXVPrmhY9fA18Tou72+kZGT0hBHkfqdskBDwyfncDgZPNrb5 JU1dEhkTth8bmSnYbpFoXc1Pu/CMTUI1gpE48izpv/pAtYKfhcaMV/Ux+3y//DRimYhm xxDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mhi4njS8q6MlE5FklCQmooC+vfv0s86qisDMHXePPMs=; b=FzA4CJPCoF1c3iRF5EAONwzf1hPv1xSPJ7aBV9iXoZBBxnEFvCWTPSbMCEtzqyX3OI cotTNFG22DOvoMHkguYQoDgNzUiXVirxHItZT3cs7ACqgqxA1++APw+nF6uw/Rw+IKKc QA2iIxDuSz7MlyC+sZEFwxlIUbEFIjnBgfNRSZ136XAU77XChJmkLYtvivW0H5l/vTzt eLXRwCOoFX7idiaohX+hxWYGH2/0HW4fJfAtJdKYNoBQf/C9jLmtlmxHxw0zUkO8QRr5 xRgZtNpFAqkqI5GH0UEqfzTXT/0yVGEFMUBFM1whRuxoFgV3wW9EnKnilBoYNcRbsswR 8LjQ== X-Gm-Message-State: ACrzQf1BcKlPMwsLWndp9wypk2OtE6k76qoxJd+YCWtPKcfLBJiK8XEy EFzxwkxDXm61H8KNYaXoTcalO3VyAugbYUH3xBqKRzv7 X-Google-Smtp-Source: AMsMyM7S28xS6WcLMS5jbkYq9CGWgTOv+TyjsqI0nQtdU4oCZBouTWicSF/dJzck77T8bZydggGTD5Upyqkg1jB8D2o= X-Received: by 2002:a05:600c:2104:b0:3c6:b7f0:cfd0 with SMTP id u4-20020a05600c210400b003c6b7f0cfd0mr860503wml.128.1666755020313; Tue, 25 Oct 2022 20:30:20 -0700 (PDT) MIME-Version: 1.0 From: Dave Taht Date: Tue, 25 Oct 2022 20:30:08 -0700 Message-ID: To: libreqos@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [LibreQoS] how are you doing on ipv4 address supply? X-BeenThere: libreqos@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Many ISPs need the kinds of quality shaping cake can do List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2022 03:30:22 -0000 in my continued rip-van-winkle, living in the third world (california) way, I am curious as to how y'all are managing your ipv4 address supply and if you are deploying ipv6 to any extent? In all this discussion of multi-gbit fiber, my own direct experience is that AT&T's fiber rollout had very flaky ipv6, and more and more services (like starlink) are appearing behind cgnats, which have their own capex and opex costs. I see a lot of rfc1918 being used as the operational overlay elsewhere, tons of tunnels, also. --=20 This song goes out to all the folk that thought Stadia would work: https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-69813666656= 07352320-FXtz Dave T=C3=A4ht CEO, TekLibre, LLC