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

Lorenzo Colitti <lorenzo@google.com> Mon, 20 November 2017 01:42 UTC

Return-Path: <lorenzo@google.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 CF727126B72 for <v6ops@ietfa.amsl.com>; Sun, 19 Nov 2017 17:42:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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=google.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 hJKONENtM5J2 for <v6ops@ietfa.amsl.com>; Sun, 19 Nov 2017 17:42:41 -0800 (PST)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 8BABF1201F8 for <v6ops@ietf.org>; Sun, 19 Nov 2017 17:42:41 -0800 (PST)
Received: by mail-io0-x236.google.com with SMTP id i38so14170318iod.2 for <v6ops@ietf.org>; Sun, 19 Nov 2017 17:42:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KuUYX2DvPlvQl/G5oYiGD3j/ToxGHpR3wQbyZpqIh4Q=; b=jp8Bx80blGcyfLrLgZI9UvIObnCwvu8aR0bZT4mIfrS6Re/pKc28D79fW+guWAPq3G RT5MUvUQhde4jc3csnSqfdtNo22WIYsypiliOmdbX6NzLStpdZtZ03GjiwI1dGaz3djV 7xBLmtdcSGKc6tKvWMOHpMpSLtOkyywJyIssmmOorpJy9ri4MoQVoFjZur+M8rIRPTcA s4ScKXGOaKH3fgMclasaGDVIytLJCqWNl0G254K4NHne+a1NblrtbPzEkIlr7TbtN5GO 0iZYXS0GXDDliAY8OY/h8OVuKpch86Wp0Mf+FXU9nRXbYbpg55h+JGhQ3VSq/6j5xhX3 c1bA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KuUYX2DvPlvQl/G5oYiGD3j/ToxGHpR3wQbyZpqIh4Q=; b=RQ8yxfzY9AoDEr/t/CGhDeSgVjYmPSpDF8jq8TTKdWMGl+S50xGoGrspkNKQuTrBQq fLkTYS4L7EXiZxLFTpBDc5+Uo2NMCzYGx9yJsi5Snv25O+kTTxhuhmoqwZb+cZYz68Pv slf38QBtaM4ZjOohdyDRDqmRIFcd2M2IHKZuqfvPHHBWRBwMx7OpommEs3ZWvgQGj6fT 6tgflu2h+u4JyFbaeW7dL25hUTF3XU/mkQv1YjLSQdja+pF7SgJHsiRJrv13g7t/6tqe KI/9G/zkGrbYR/fjcPGWUk65FhJ+4dacczEgDoe825CI5pg9eCaZ0Vk7sCJpNnYxVgz+ mOdw==
X-Gm-Message-State: AJaThX7nXhPc0q7qH0u85hd6oMmzc36mAuDE90mhK6ukfko76aBWvD+S Na+Uqk4FMyR+tEL1Vv/w9hVK2d9TEFphf/PRQph/8A==
X-Google-Smtp-Source: AGs4zMZBAaIT/5VsR+xzaGMcvo74MV2gNh8vXyAt20Revx4gYcULR2z7fKTaktANR/3SDiOvoaspD98M616uTX1uoCY=
X-Received: by 10.107.16.206 with SMTP id 75mr12064750ioq.83.1511142160537; Sun, 19 Nov 2017 17:42:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.16.155 with HTTP; Sun, 19 Nov 2017 17:42:19 -0800 (PST)
In-Reply-To: <962041fbaee844b5a4cdd82012440dbe@XCH15-06-08.nw.nos.boeing.com>
References: <7FC2CA6E-8BF7-47BC-9164-1877FAF83FD0@gmail.com> <962041fbaee844b5a4cdd82012440dbe@XCH15-06-08.nw.nos.boeing.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 20 Nov 2017 10:42:19 +0900
Message-ID: <CAKD1Yr2=qVdGNzvwCXaofhH=fBaQS0M05Lg6MKF3MEze7UUfXg@mail.gmail.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: Fred Baker <fredbaker.ietf@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="001a113eda96afb1a7055e6033a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/HxUUd-e5t0XtShSytqyTI8NAf1o>
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 01:42:43 -0000

On Thu, Nov 16, 2017 at 2:55 PM, Templin, Fred L <Fred.L.Templin@boeing.com>
wrote:

> 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.