Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
Jen Linkova <furry13@gmail.com> Mon, 28 October 2019 21:57 UTC
Return-Path: <furry13@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 AC56E120096 for <v6ops@ietfa.amsl.com>; Mon, 28 Oct 2019 14:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fIt4mV2PxGex for <v6ops@ietfa.amsl.com>; Mon, 28 Oct 2019 14:57:26 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 8372B12006B for <v6ops@ietf.org>; Mon, 28 Oct 2019 14:57:26 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id o3so16986590qtj.8 for <v6ops@ietf.org>; Mon, 28 Oct 2019 14:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=6rHXsU9cjVKV5vEUlqQLZ6f3wr1sTENWRJjqyZibFLM=; b=XJrC7zV13Va6gcMmYoDNRYZEpbuHM1k3Zw+uJYWh67EKWQw7oDQT0iSefck4TrFMmz YhmZma5/djz1TGaBfGpPy60mYKSKTc9nIMWy0HBNnhLP5QyGdMS4ZGpiQaOa8IdFuV1e LBBofC7xwZyra5O1VAkip/yHMKtFNjmx0RvEJvVxpxNk5unkFgWPYlthIzyLahzl+mEy ZiGUriMQBMW8jqkZ6vWKQID0/6D5W9gsqyoF68M+k64OcSb1TGEtgLqzAJ5QHk1T7JZV 9owttXvBUhcNcmQnb5M6M7YobOU3nVu61EZJBvWBxDITkzLiNmFVgws1Y9quivPgcDox RsVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=6rHXsU9cjVKV5vEUlqQLZ6f3wr1sTENWRJjqyZibFLM=; b=om3oGk6/Qgh3tlLNirfKwnowHuxsglM40mipsKwV8AJHXuTIhMfr4WFFUqin23tTGi +WDcLuP3TxK/YtPqj0ZZffZCZMQPwxu5Qn72SiIZju9AxJuUzsXbyYJU3QChTYUJIXfD O9BoWXtt7nUgtNun2Wmcnecoq8fHYS3bC8sFyCV+KNv3wmtkaPLxVJwwrvRYsX4vSAhE 9ip6EQTMHFu2LSA5z24n6b2/3+MAcvechFXCrIV2FHFuVcRILK711sfrFHWFYpRhI698 RG2uK8IuFxljl7CtQE5j5ZzTGP9NGwg1cKiQ99SCPP36mioGd16bG8bTKzdtN0XPRe1b gEbA==
X-Gm-Message-State: APjAAAVxKHaCuIRTSifGfh7oaUURsM1KyKQ/VR5fq7q1mULsLbyqnXh3 Rlle5K35ppUS3zr8V1NDdvWBRokOD5UEFQbXGwA=
X-Google-Smtp-Source: APXvYqyruFYxVt4Jc4eb/lAmwwx4/sgPDpF+JWqrjoz2VKjGB8lf6lvdkAzeW6TNR028FTpS5xAO73UtxhT8rYsiSeo=
X-Received: by 2002:ac8:53ca:: with SMTP id c10mr830826qtq.94.1572299845279; Mon, 28 Oct 2019 14:57:25 -0700 (PDT)
MIME-Version: 1.0
References: <m1iNIFE-0000IwC@stereo.hq.phicoh.net> <d1b6855d-bde9-7b53-4809-0846bb9772e4@si6networks.com> <CAO42Z2x7vudujw5t++obry56g=VNjQXXTHFK8pBPk0jmk78Bcg@mail.gmail.com> <CAJoHkZ8pTjszP0vw4BjX0HUhmPa6wJONzdy2JEm5iqAfBUvjRg@mail.gmail.com> <CAO42Z2wCYi4KWTEz1hUSPVr9+hu8GaHRkPuvQQ2P00knvnPaaQ@mail.gmail.com> <848BA3B3-36B4-4C42-86D0-88759BC45D5A@employees.org>
In-Reply-To: <848BA3B3-36B4-4C42-86D0-88759BC45D5A@employees.org>
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 29 Oct 2019 08:57:13 +1100
Message-ID: <CAFU7BARBHGcxzULO-aVr+c5CJW6UCsNRkrgQSRdB7vtpYZw85w@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: Mark Smith <markzzzsmith@gmail.com>, v6ops list <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0cFG8nWe0RWNA_vvt9LOVZD3IL8>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
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: Mon, 28 Oct 2019 21:57:29 -0000
On Thu, Oct 24, 2019 at 9:47 PM Ole Troan <otroan@employees.org> wrote: > Right. Instant/flash renumbering is not supported in IP networks. Oh. Surprise. After I've been doing it all the time....;) Actually it would be helpful to define requirements/expectations. I read it as: R1: [MUST HAVE] after the renumbering host is able to open new connections R2: [NICE TO HAVE] old connections survive the renumbering. IMHO we shall at least enumerate the most common scenarios where R1 is not happening and look what can be done here. If we have a scenario when hosts end up with totally broken connectivity we can: 1) say 'oh just don't do that' - however before we do this (== produce some BCPs) it's worth analysing if it's feasible and, more importantly: --- is the party affected by the issue is the same party which is supposed to follow the BCP? --- are we talking about 'fix all hosts'? (when did we deal last time with the scenario 'a machine re-authenticated via 802.1x successfully, changed the VLAN but kept the old IPv6 prefix'? 2) See if there is a way to mitigate at least part of the problem by making the protocol more robust (isn't all DNA work is actually in the same problem space?) > IPv6 does nothing to help with this, well, assuming a network hiding behind NAT, it makes it harder. > Apart from "does not work", what more can the IETF say or do here? Try to make the Internet work better, maybe? :) > > On 24 Oct 2019, at 12:43, Mark Smith <markzzzsmith@gmail.com> wrote: > > > > > > > > On Thu, 24 Oct 2019, 20:59 Trevor Warwick, <twarwick@gmail.com> wrote: > > > > On Thu, 24 Oct 2019 at 09:18, Mark Smith <markzzzsmith@gmail.com> wrote: > > > > > > I thought about this in the exact context of the scenario of this draft. Although the design of the broadband deployment I worked on always planned to give out stable prefixes, I worked through this scenario and realised that so many complex issues disappear if you provide stable prefixes. > > > > Fundamentally, if an ISP is selling an always on link to the same location, then the addressing should be as permanent as the link delivery location is. > > > > > > If you're an ISP today, and using DHCPv6-PD to hand out IPv6 prefixes, what are the possible scenarios if you don't try hard to keep the prefixes stable? > > > > Why don't you want to try hard? Not trying hard gives customers a bad experience. They're paying you to try hard to give them the best suitable service you can give them. > > > > > > - You could be running a closed environment where all customers are forced to use your CPE, in which case you can make sure that your CPE has various hacks added to try to cope with prefix instability and avoid customer hosts experiencing connectivity issues when prefixes change. Maybe you can make this work well enough, and advanced customers who don't want to use your CPE are just out of luck. > > > > - If you're in an environment where customers can chose their own CPE, then it seems almost guaranteed that there will be connectivity problems when the prefix changes, because many CPE implementations don't handle this situation at all. So you're then relying on hosts falling back seamlessly to IPv4, in order to continue to have connectivity. In which case, I'd wonder why you're bothering to provide an IPv6 service in the first place. > > > > See what I said about selling an always on service to a fixed location, and the addressing having the same amount of stability as the service and link itself. > > > > The reason this problem really exists is that ISPs have fundamentally continued to treat residential, always on broadband customers although they were still dial up customers. Nothing has changed - per BRAS (NAS) IP address pools, pool route aggregation at the router, customer gets a single IPv4 address when they attach, that can change each time they attach. PPPoE is making Ethernet connectivity resemble dial up connectivity. > > > > Now this dial up model is trying to be applied to semi-permanent IPv6 services, where it's even less applicable now that customers get their own routed address space on a semi-permanent link. > > > > Treat all customers as routed subnet SOHO customers, so they get the same prefix regardless of which BRAS they attach to. Move the route aggregation boundary to a higher level to e.g. a cluster of BRASes, or a region. > > > > Use an IPv6 address provisioning model that suites and matches the service they're paying for, not a nearly 30 year old dial up model. > > > > If your customers can BYO their CPE, then stable prefixes are the only choice. > > > > See slide 6. > > > > Residential IPv6 CPE - What Not to Do and Other Observations > > https://www.slideshare.net/mobile/markzzzsmith/residential-ipv6-cpe-what-not-to-do-and-other-observations > > > > > > > > > > I do think this is an important problem that needs to be solved, for this context and the others mentioned in the draft. > > > > > > _______________________________________________ > > v6ops mailing list > > v6ops@ietf.org > > https://www.ietf.org/mailman/listinfo/v6ops > > _______________________________________________ > > v6ops mailing list > > v6ops@ietf.org > > https://www.ietf.org/mailman/listinfo/v6ops > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops -- SY, Jen Linkova aka Furry
- [v6ops] SLAAC renum: Problem Statement & Operatio… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Trevor Warwick
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Eric Vyncke (evyncke)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… JORDI PALET MARTINEZ
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Brian E Carpenter
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Gert Doering
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Clark Gaylord
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Nick Hilliard
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Richard Patterson
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Brian E Carpenter
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Brian E Carpenter
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Nick Hilliard
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Brian E Carpenter
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Bernie Volz (volz)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Kristian McColm
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Jen Linkova
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Brian E Carpenter
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Jen Linkova
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Jen Linkova
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Philip Homburg
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Timothy Winters
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Nick Hilliard
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Timothy Winters
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Timothy Winters
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Bernie Volz (volz)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… JORDI PALET MARTINEZ
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Bernie Volz (volz)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Bernie Volz (volz)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Radu-Adrian Feurdean
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- [v6ops] A broken promise - "You said PD Prefix Va… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] A broken promise - "You said PD Prefi… Naveen Kottapalli
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Radu-Adrian Feurdean
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Bernie Volz (volz)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Mark Smith
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] A broken promise - "You said PD Prefi… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] A broken promise - "You said PD Prefi… Sander Steffann
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fernando Gont
- Re: [v6ops] A broken promise - "You said PD Prefi… Philip Homburg
- Re: [v6ops] A broken promise - "You said PD Prefi… Ole Troan
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Mark Smith
- Re: [v6ops] A broken promise - "You said PD Prefi… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] A broken promise - "You said PD Prefi… sthaug
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Ole Troan
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Bernie Volz (volz)
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Bernie Volz (volz)
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Ole Troan
- Re: [v6ops] A broken promise - "You said PD Prefi… Fernando Gont
- Re: [v6ops] A broken promise - "You said PD Prefi… Bernie Volz (volz)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Ole Troan
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Fred Baker
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Bernie Volz (volz)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] A broken promise - "You said PD Prefi… Owen DeLong
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] A broken promise - "You said PD Prefi… Owen DeLong
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] A broken promise - "You said PD Prefi… sthaug
- Re: [v6ops] A broken promise - "You said PD Prefi… Owen DeLong
- Re: [v6ops] A broken promise - "You said PD Prefi… Philip Homburg
- Re: [v6ops] A broken promise - "You said PD Prefi… Owen DeLong
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Bernie Volz (volz)
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Alexandre Petrescu
- Re: [v6ops] SLAAC renum: Problem Statement & Oper… Owen DeLong
- Re: [v6ops] A broken promise - "You said PD Prefi… Fernando Gont
- Re: [v6ops] A broken promise - "You said PD Prefi… Ole Troan
- Re: [v6ops] A broken promise - "You said PD Prefi… Ole Troan
- Re: [v6ops] A broken promise - "You said PD Prefi… Fernando Gont
- Re: [v6ops] A broken promise - "You said PD Prefi… Alexandre Petrescu
- Re: [v6ops] A broken promise - "You said PD Prefi… Philip Homburg
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Mark Smith
- Re: [v6ops] A broken promise - "You said PD Prefi… Fernando Gont
- Re: [v6ops] A broken promise - "You said PD Prefi… Mark Smith
- Re: [v6ops] A broken promise - "You said PD Prefi… Philip Homburg
- Re: [v6ops] A broken promise - "You said PD Prefi… Philip Homburg
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Richard Patterson
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Richard Patterson
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Mark Smith
- Re: [v6ops] A broken promise - "You said PD Prefi… Ted Lemon
- Re: [v6ops] A broken promise - "You said PD Prefi… Mark Smith
- Re: [v6ops] A broken promise - "You said PD Prefi… Ole Troan
- Re: [v6ops] A broken promise - "You said PD Prefi… Mark Andrews
- Re: [v6ops] A broken promise - "You said PD Prefi… Fernando Gont
- Re: [v6ops] A broken promise - "You said PD Prefi… Fernando Gont
- [v6ops] What problem are we trying to solve? (Re:… Mark Smith
- Re: [v6ops] A broken promise - "You said PD Prefi… Owen DeLong
- Re: [v6ops] A broken promise - "You said PD Prefi… Owen DeLong
- Re: [v6ops] What problem are we trying to solve? … Tassos Chatzithomaoglou
- Re: [v6ops] What problem are we trying to solve? … Fernando Gont
- Re: [v6ops] What problem are we trying to solve? … Fernando Gont
- Re: [v6ops] What problem are we trying to solve? … Tassos Chatzithomaoglou
- Re: [v6ops] What problem are we trying to solve? … Mark Smith
- Re: [v6ops] What problem are we trying to solve? … Fred Baker
- Re: [v6ops] What problem are we trying to solve? … Tassos Chatzithomaoglou
- Re: [v6ops] What problem are we trying to solve? … Richard Patterson
- Re: [v6ops] What problem are we trying to solve? … Ted Lemon
- Re: [v6ops] What problem are we trying to solve? … Ted Lemon
- Re: [v6ops] What problem are we trying to solve? … Tassos Chatzithomaoglou
- Re: [v6ops] What problem are we trying to solve? … Ted Lemon
- Re: [v6ops] What problem are we trying to solve? … Ole Troan