Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?

Ole Troan <otroan@employees.org> Mon, 20 November 2017 08:43 UTC

Return-Path: <otroan@employees.org>
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 9FEB61294BD for <v6ops@ietfa.amsl.com>; Mon, 20 Nov 2017 00:43:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 F6sM3PwGF5PU for <v6ops@ietfa.amsl.com>; Mon, 20 Nov 2017 00:43:01 -0800 (PST)
Received: from accordion.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77F1A12941C for <v6ops@ietf.org>; Mon, 20 Nov 2017 00:43:01 -0800 (PST)
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by accordion.employees.org (Postfix) with ESMTPSA id 374E92D5125; Mon, 20 Nov 2017 08:43:01 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 9DEB1200C8F0A1; Mon, 20 Nov 2017 09:42:59 +0100 (CET)
From: Ole Troan <otroan@employees.org>
Message-Id: <ABF8D7E4-BF1A-422F-9652-69394E000913@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_6B10F4DD-CB3D-4F21-BDBD-562DF57B0425"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Date: Mon, 20 Nov 2017 09:42:58 +0100
In-Reply-To: <CAKD1Yr2=qVdGNzvwCXaofhH=fBaQS0M05Lg6MKF3MEze7UUfXg@mail.gmail.com>
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "v6ops@ietf.org" <v6ops@ietf.org>
To: Lorenzo Colitti <lorenzo@google.com>
References: <7FC2CA6E-8BF7-47BC-9164-1877FAF83FD0@gmail.com> <962041fbaee844b5a4cdd82012440dbe@XCH15-06-08.nw.nos.boeing.com> <CAKD1Yr2=qVdGNzvwCXaofhH=fBaQS0M05Lg6MKF3MEze7UUfXg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/aB0bLg3fpf14ArB7BcC3RWA2rQ8>
Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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, 20 Nov 2017 08:43:02 -0000

Lorenzo,

> The way I understood the comment was that the draft needs more supporting
> text on the rationale for doing what the document describes (e.g., the benefit
> for not having to place the upstream interface in promiscuous mode, efficiencies
> for not doing link-scoped multicasting over the upstream interface, avoiding
> disturbance of other nodes on the upstream link, etc.
> 
> I did not think the comment was asking to expand the document to cover all
> methods of conveying a /64 to the host (e.g., unique-ipv6-prefix-per-host,
> 3GPP, etc.). This document only concerns methods that meet the description
> of prefix delegation as described for examples such as DHCPv6 PD.
> 
> FWIW my comment at the mike was asking for the latter as well. There are many ways that a host can get a dedicated prefix, and we should provide guidance on what a host should do in this situation. Also if we look at current deployments, way more hosts get dedicated prefixes via RAs then via PD: all 3GPP networks provide a dedicated prefix, and very few hosts implement DHCPv6 prefix delegation. So focusing on DHCPv6 PD is focusing on a niche use case.

The "dedicated" prefix over 3GPP networks is not something that you can generalise right?
It is a property implied by that particular link-layer.

Cheers,
Ole