Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
Owen DeLong <owen@delong.com> Sun, 27 October 2019 04:48 UTC
Return-Path: <owen@delong.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 5F1D8120025 for <v6ops@ietfa.amsl.com>; Sat, 26 Oct 2019 21:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=delong.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 49fodKaGWRpN for <v6ops@ietfa.amsl.com>; Sat, 26 Oct 2019 21:48:21 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id B3D9C12001A for <v6ops@ietf.org>; Sat, 26 Oct 2019 21:48:19 -0700 (PDT)
Received: from kiev.delong.com (kiev.delong.com [IPv6:2620:0:930:0:0:0:200:5]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id x9R4mAxd028564 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 26 Oct 2019 21:48:14 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com x9R4mAxd028564
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delong.com; s=mail; t=1572151698; bh=Ikh/rXSMq71HYXizxJtwDyOY8GVwEQdIRM23ivZ2z8c=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=J3jmlGkvCwwoHuS1izJkSI1WtCbNsmxHxlgOAEd82pPit63CrpwEBrj6CQA7+y+ha VUvhFqhORrMKEAUn11BcAJIK9O22p88qlXQk8mnQXbeR8Q1YSX/clZPZUyhlQKit0B ldb54KXK4pRfRJWS/DzVctEFhk71lxEnOqp7zYlg=
From: Owen DeLong <owen@delong.com>
Message-Id: <7C142F1F-04C6-48A2-A65A-7CADD3691ECF@delong.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F20575FC-0DC7-479C-94C8-B953F19CF3AF"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sat, 26 Oct 2019 21:48:10 -0700
In-Reply-To: <48c864c7-589d-23cf-417e-6f4ec012a76a@si6networks.com>
Cc: Philip Homburg <pch-v6ops-9@u-1.phicoh.com>, v6ops@ietf.org
To: Fernando Gont <fgont@si6networks.com>
References: <m1iNIFE-0000IwC@stereo.hq.phicoh.net> <d1b6855d-bde9-7b53-4809-0846bb9772e4@si6networks.com> <7C913CC2-938F-449C-9750-85C36EC05E38@delong.com> <48c864c7-589d-23cf-417e-6f4ec012a76a@si6networks.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Sat, 26 Oct 2019 21:48:18 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6q-rsjAQEjYHCQVGpGIijzSM27w>
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: Sun, 27 Oct 2019 04:48:24 -0000
>> It is worth noting that these values are tunable by the administrator >> and the >> RFC suggested defaults should never be a hard-coded value. >> >> With the following exception, I don’t advocate modifying this on the client >> side: >> +Section 5.5.3 of RFC4862 should be amended to specifically >> allow the immediate deprecation of a prefix by sending a valid >> lifetime of 0 seconds. Hosts should be required to honor >> this as a signal that the prefix is no longer valid. > > Could you please elaborate on this one? I’m not sure what I could do to elaborate. The addition of a specific call-out that even if the current behavior of ≤2 hours = 2 hours is to be preserved, there should be a special case for “0 seconds” which causes the prefix to be immediately deprecated with extreme prejudice. Hosts should be required to treat an RA containing a prefix with a 0 second valid lifetime as an invalid prefix and immediately deprecate it from the interface if it is in use. > > > >> I do think that generally speaking, your proposed modifications to CPE and >> router behavior should be standardized and implemented. >> >>> A better mitigation is to affect the preferred and possibly the valid >>> lifetimes in response to consecutive RAs from the same router that lack >>> the original (stale) prefix. e.g., after two consecutive RAs that do not >>> contain the existing prefix, reduce the preferred lifetime. After two >>> additional RAs, reduce the valid lifetime. >> >> In the crash scenarios you describe, you’re assuming a single router on >> the network or >> at least only one router announcing the prefix(es) in question with no >> persistent >> memory of the prefixes it was announcing across a reboot. In such a >> scenario, >> it seems to me that the following are also likely valid assumptions: >> >> +The network has significant excess bandwidth compared to demand. >> +The small overhead of frequent RAs and short lifetimes is probably >> an acceptable tradeoff in this environment. >> >> However, there are lots of other scenarios in the world where those >> assumptions >> won’t hold true and we should not seek to solve this problem (which is >> generally >> applicable to residential and SMB environments) at the expense of all of >> those >> other professionally administered environments. > > Even with the default RA frequency, if you were to unprefer a prefix > upon, say, second RA that doesn't advertise it, and say, remove the > prefix after many other RAs are received, that would be a *big* > improvement to what we have now. I don’t like this idea because I can think of some scenarios where you may receive multiple RAs from router A not containing the prefix in the same time frame that router B has not sent an additional RA containing the prefix, but it will do so in its next RA. There is no requirement for all routers on the same link to provide the same set of PIOs, nor are they required to use the same advertisement timers. I agree that it’s a bit of a corner case and it’s certainly not an ideal way to configure a network, but it is not entirely unlikely to happen in the real world, it is within the current RFCs, it is valid functionality and it is not broken by the expected behaviors today. >> In section 3.2.1, you advocate setting the A and L bits to their >> previous values >> for prefixes which are being deprecated. IMHO, this is incorrect and the >> announcements calling for immediate deprecation should also indicate that >> the prefix should no longer be auto-configured and should no longer be >> considered on-link. > > Not sure I follow. Could you please elaborate? Sure… In section 3.2.1 of your document, you advocate that if the previously valid PIOs were set A=1 and/or L=1, then those values of the A and L bits should be preserved in the RAs sent to deprecate them. My argument is that since you are attempting to make this a prefix that hosts will no longer autoconfigure (A) and will no longer consider on-link (L), that in reality, regardless of the previous state of the A and L bits in the RAs announcing the prefix in a valid PIO, the new RAs since the prefix has been deprecated should be sent with A=0, L=0 in order to signal the host that this prefix should not be auto configured and should no longer be considered on-link. >> Is there some unfortunate widely deployed behavior that interacts poorly >> with setting A and L to 0 for these previously valid prefixes? >> >> Finally, An editorial note… In Section 3, you state “Finally, Section >> 2.5 analyzes…” >> I believe this is intended to be a reference to section 3.2.2. > > Nope. Section 3.2.2 talks about the interaction between dhcpv6-pd and > slaac. BUt it is section 2.5 that discusses other considerations for > dynamic/stable prefixes. For example, stable prefixes are not nice for > privacy. Fair enough, but in that case, I don’t think I would put it after the description of section 3.2, nor would I use the word “Finally” as a lead-in to a back-reference. Owen
- [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