Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

Ted Lemon <mellon@fugue.com> Tue, 29 October 2019 09:43 UTC

Return-Path: <mellon@fugue.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 5C43112010F for <v6ops@ietfa.amsl.com>; Tue, 29 Oct 2019 02:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 u1uC-BdmYD2N for <v6ops@ietfa.amsl.com>; Tue, 29 Oct 2019 02:43:51 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 49D641200B8 for <v6ops@ietf.org>; Tue, 29 Oct 2019 02:43:51 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id 15so11549734qkh.6 for <v6ops@ietf.org>; Tue, 29 Oct 2019 02:43:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=nNr+i4ftkB77hIT9LofLK/cu2Cm5pLHH+2YcDQKCrc0=; b=B3ts0tZbyZhuYFTBaB1C0WTAKdhQpHjJCNJ+3hw7pRynbskht8926ZKt5s+KeqAQf0 5B1DoN0q445556Nv3aECB2lzOCoPrzGejm+Nh5o4F53yXJ3npf/9JQBiAF9e17Q6jhQw fpBvvVHVR9R7s8hu1hlEFH4/BrLx224iQQrAhX5gnfcOXTYc10zjFGPeAfmZ/a74sFsQ JL+anvEewawXpKhQ8G4xqHRlx2yWWNnzI8MmMcZjgfIpT4j0kFU2WykVEnIY7SqEFBwB n/NjCL2kLID4pPKyX4ewnDJKMtvT1YFzL4Y3Wh6wZlB9afc5W0KHO0xFuL+HtWfQM7HP xkXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=nNr+i4ftkB77hIT9LofLK/cu2Cm5pLHH+2YcDQKCrc0=; b=reeZneLPnKs5Jh0i3SMZfw5WdViTcalTzOuVkzm/s1eKFnqebquh369zj07M+sk2lZ zMzdqF2UQe4MiRjSHckH7Z6qiTl35n4iRMGwfuW8bZsEFh6D9QtZBf2s2Az1Asq8KyST RYIi31cCBqxgxFMnVHOF9bDqBJL/03Hjf5kIQlRVjifH3Ulz8eXD1nCX71+pWvcCyCQA JD0nKaKEK+zGCz0gf0G3blckpS+kpM5bDukfy9kbBZpZ44hu0SUeBVuGqNZAqf2AbUt+ IzzMzGM2EmjPiHjg2u+XEu6Rn34Nu+hLGozoDEs/ZLlRtKDRPjXkcchQUUE9dvY6VDld Y1Wg==
X-Gm-Message-State: APjAAAXgrT2D8hrDomz43R85vHp4IcAuI8A1OzkQftFNdVlKar+aNNPR 78Isj+xNIMliswHWqdUkwqf3L0KI9ALXYg==
X-Google-Smtp-Source: APXvYqzexSViujWlSVfaruPupbpp7BohRkG8uz66wIWW0mfe73Cqe4nxd21w/n6BTYMPQqpQdFeJUw==
X-Received: by 2002:a37:bf02:: with SMTP id p2mr20789652qkf.42.1572342229996; Tue, 29 Oct 2019 02:43:49 -0700 (PDT)
Received: from ?IPv6:2601:18b:300:36ee:9be:fcfd:8f35:ceef? ([2601:18b:300:36ee:9be:fcfd:8f35:ceef]) by smtp.gmail.com with ESMTPSA id n56sm9933532qtb.73.2019.10.29.02.43.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 29 Oct 2019 02:43:49 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 29 Oct 2019 05:43:48 -0400
Message-Id: <BCFEF731-F3A0-472A-B5D3-68F9AB4C97C8@fugue.com>
References: <FA25340B-0CBA-407D-85EB-FB1E26FA3EFF@delong.com>
Cc: Philip Homburg <pch-v6ops-9@u-1.phicoh.com>, v6ops@ietf.org
In-Reply-To: <FA25340B-0CBA-407D-85EB-FB1E26FA3EFF@delong.com>
To: Owen DeLong <owen@delong.com>
X-Mailer: iPad Mail (17A878)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Vi4IMT5mjkW6g38pKTHXVp2uuUE>
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: Tue, 29 Oct 2019 09:43:53 -0000

On Oct 28, 2019, at 11:00 PM, Owen DeLong <owen@delong.com> wrote:
> 
> There’s a difference between networks where hostile hosts can occur in extreme circumstances (what you describe) and networks where hostile hosts are expected as a normal occurrence (what I was intending to describe).

I’m not following your distinction.   Bot infections can happen at any time, on any network.