Re: Stateful SLAAC (draft-ietf-v6ops-unique-ipv6-prefix-per-host)

Fred Baker <fredbaker.ietf@gmail.com> Fri, 10 November 2017 04:12 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8F4120713; Thu, 9 Nov 2017 20:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 GLhbl6QxyO0e; Thu, 9 Nov 2017 20:12:49 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 24C4B129434; Thu, 9 Nov 2017 20:12:49 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id b9so154127wmh.0; Thu, 09 Nov 2017 20:12:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=7KhVdFPdTuHMq04G/wwycGWHHxDLD7v/myix8Vys2bM=; b=jf7K7Q9izN3kP/O9ShCebTbCCQ0VvWzid1hnu7SaAnSOlamHg/PWhwFjuW/7ZNguE5 U2vTf8bgYX9UYrLY49V8zt9x3j58pxGNoqE37muI/onUtUiIAAup5Tk3ALWtgt7JgfQs 7qv1qaulBi4dEreoD1RSgJMWmBO0vvpktRwzzMg7brUmbkyW6TZLYLfZVhYOekzfHRoD 8ZNPZaTjTKVzXd4aSD/wh9azVmjuijuNH+Ztv/0Zj3gLbaCeXMFqYMnojQ6PKEcrQMxr 3988r/ovaWAGH8zJKrDDG3Et87xzQLpBJZQcSHLpE94Kh/EDd1uQ4xpRZyc2/OjsY277 HOcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=7KhVdFPdTuHMq04G/wwycGWHHxDLD7v/myix8Vys2bM=; b=ldlhZfgEpWvzZ0JaPjRb44HRpEzXX6s/6IO3lHwOiQnbYlrmZnCqSHlUVGWw44Pa2O Y49k5acbQQcB14wkS3FEYFnJQqdLFzeiC2l7k9nNAqNVYDXkrq1Hafpa6eqD+pTEIN2O bkGlqlFd++4rLHnpjMeug/trTndj/1n3DrYMDBVCA/tZik+ouWSq9rgu5CsFJGQK1y4X J5lCuGndoB+tfmI4P8G4yVWrYZAiaK0AY1GlDvbP/nbV4rP/oYR7pdVfTJFmdQS/6PDC zUOnnRcci4Tzg1OTTs29nz/QR2w6p2OUGP+QXT9qrxo5nqHlADadQbO2gKx09MGm81Tc DJVA==
X-Gm-Message-State: AJaThX7U6TvAEsxEc2vzAAo1PrlYvuNpM5rmUAvsQvfUjB74Xq1oK/wQ IsUepcPgGLyCADW8Nyi5yOw=
X-Google-Smtp-Source: AGs4zMZwGL59e3RxGCtLE6VMLEntOj6+ieCLVtaNNAI2P0TzSZi1whO1ROGc9XeqE5PPTefmoH/Nbw==
X-Received: by 10.28.19.130 with SMTP id 124mr33560wmt.108.1510287167689; Thu, 09 Nov 2017 20:12:47 -0800 (PST)
Received: from 198.66.20.149.in-addr.arpa (198.66.20.149.in-addr.arpa. [149.20.66.198]) by smtp.gmail.com with ESMTPSA id b81sm250629wmh.16.2017.11.09.20.12.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Nov 2017 20:12:46 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <83BF7A33-9A52-43EE-996E-0B5F54D67AFF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4A1A49D9-8A4B-4F81-8D64-40B087EAE376"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.11\))
Subject: Re: Stateful SLAAC (draft-ietf-v6ops-unique-ipv6-prefix-per-host)
Date: Fri, 10 Nov 2017 06:48:25 +0530
In-Reply-To: <CAKD1Yr0_a2Qm8U4oK+BQU57DeDUD9i-o_+G+YhnH4pVXRxmxxQ@mail.gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>, "6man-ads@tools.ietf.org" <6man-ads@ietf.org>, "v6ops-ads@ietf.org" <v6ops-ads@ietf.org>, draft-ietf-v6ops-unique-ipv6-prefix-per-host@tools.ietf.org
To: Lorenzo Colitti <lorenzo@google.com>
References: <be9724f5-2ff5-d90c-2749-ecae2c628b78@si6networks.com> <CAKD1Yr0_a2Qm8U4oK+BQU57DeDUD9i-o_+G+YhnH4pVXRxmxxQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.5.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QZAg8lBn0kCdb7wu9m9mvPH1YaE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Nov 2017 04:12:50 -0000


> On Nov 9, 2017, at 8:28 AM, Lorenzo Colitti <lorenzo@google.com>; wrote:
> 
> On Tue, Nov 7, 2017 at 6:13 AM, Fernando Gont <fgont@si6networks.com>; wrote:
> While reviewing this document a few days ago, I found that Section 4
> (page 5) contains what is a protocol spec, rather than an operational
> BCP. It contains rules regarding how to set the link-layer address (to a
> unicast address) for IPv6 multicasted RAs, and how a SLAAC router should
> now remember which prefix has been "leased" to which node -- something
> that seems to be way outside of the v6ops charter, and that should have
> been done in 6man, instead.
> 
> I don't see how this is a protocol change. Sending RAs unicast is already allowed by RFC 4861, so this is just an operational practice.

I understand the concern to be sending to a multicast address at the network layer and a unicast address at the link layer. If 4861 allows the RA to be sent unicast, it is probably unicast at both layers. I suspect that if we change to doing what 4861 describes we'll be fine.