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

Paul Marks <pmarks@google.com> Wed, 29 November 2017 23:02 UTC

Return-Path: <pmarks@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 833561271FD for <v6ops@ietfa.amsl.com>; Wed, 29 Nov 2017 15:02:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-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 3p8pY793x-gi for <v6ops@ietfa.amsl.com>; Wed, 29 Nov 2017 15:02:13 -0800 (PST)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::22b]) (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 B17F412711A for <v6ops@ietf.org>; Wed, 29 Nov 2017 15:02:12 -0800 (PST)
Received: by mail-wr0-x22b.google.com with SMTP id l22so4914569wrc.11 for <v6ops@ietf.org>; Wed, 29 Nov 2017 15:02:12 -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=b6L54FbQBQmawYbgYhBUhTUSAf9gDhtoR/RlWDzLwJM=; b=o45zDj0eoOyzxfh7UjX2BYNt7CbSQPpBYYTrSR43UvH11NKsrQK3xo/oVOPCFTgK23 ZnanXyrgpnlgBDJBQ9bIYXzIe05SlV1a/INW9BpJf7AD/7gG3xhmQ4wZxzrk5f0oLGYw 4bWgDlkJMKNRzUAh1w0b3mHnvlm8Iszkn/5EuD0UPLSVe0kHRLpULTLwOoYBgqa4d0IN 0pfrxjF8RIVhG0A01XS1v9lRlOOS4VwA1UazenKI4HMa66j8Zx5Mt1OP/nKKafAqF9Io 6RebzFOYwHmPNLbgmzpI82QPZW0r58DlmGViffCVJWsbfIurzz1FQz7PIF3uu55UuQFd ZoVQ==
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=b6L54FbQBQmawYbgYhBUhTUSAf9gDhtoR/RlWDzLwJM=; b=CN2Kwq5H4KRl1Bp/Yd4oxg0c2KMM+nAc/6p4WeXfwrTYysnIpHAU/l9upjmfsvV7zz CGVzHB/Oa3BbiofqtyDPJPmJ62HLMnNuRSdW8AOsv9qrwV8W8qTSv/pVWB6dghPfTrHn JMUZ6dAyvsX4L6dIDN8pJ9BuiSBcfBe0sZBlY03qP7x/+eDvmXv73tsZpHF0xhOsA+eB rBKFkEkoKZEspHlEyaSJKDXitot212q5JH95L3U3x4t3grBfG/mNAvq5wCYVv7MMgRt4 M66BL4jgFkjztt6wFOmvaMmtPvRHOdhJRlODvcoo8N9uALA4rD8s83DgLOc63kvd5Kfj n7ZA==
X-Gm-Message-State: AJaThX51tkHjNaM9eL8eg1c10FGicSkaky/YSvFMuRynhUvKYyM/r4An VnnJJMd3G1Qu09I/TXU7aMsgzLzOVRZSZEkjHIazlwe2X+I=
X-Google-Smtp-Source: AGs4zMYz32w0rKjk7EU5AiJnlAliioPPXRFHO0xWlyiujON/dmkKH+whfQwEE3akbhJno1L+4IOZvIbEyO42BiKXS+0=
X-Received: by 10.223.144.36 with SMTP id h33mr321659wrh.180.1511996530970; Wed, 29 Nov 2017 15:02:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.161.4 with HTTP; Wed, 29 Nov 2017 15:01:49 -0800 (PST)
In-Reply-To: <42B4C703-00FF-4C44-984D-71D5A7736BE9@google.com>
References: <34cf035352254aadb3146dffb3baebb0@XCH15-06-08.nw.nos.boeing.com> <CAHaKRvJCabgnc3U-ouZ1ghmwYzOQ+H1fDHwKrac6ghxaH=+Zdw@mail.gmail.com> <42B4C703-00FF-4C44-984D-71D5A7736BE9@google.com>
From: Paul Marks <pmarks@google.com>
Date: Wed, 29 Nov 2017 15:01:49 -0800
Message-ID: <CAHaKRvJitKKC_AL57eekvr3QRhT42sx0qoSyDKF7xsFMCWtE9A@mail.gmail.com>
To: james woodyatt <jhw@google.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c06990621d570055f2720d3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ELiC4WBtH0H5wM9O-hip82KytpE>
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: Wed, 29 Nov 2017 23:02:14 -0000

On Wed, Nov 29, 2017 at 10:44 AM, james woodyatt <jhw@google.com> wrote:

> On Nov 28, 2017, at 17:31, Paul Marks <pmarks@google.com> wrote:
>
>
> When delegating to a host, I often wonder whether it's technically
> incorrect to use prefix::0 as a normal address.  Does anyone know for
> sure?
>
>
> RFC4291 pretty clearly specifies that [$prefix::] is one of the Subnet
> Router anycast addresses in the set of all subnets where n >= len($prefix),
> where the IID on the link type is (n - 128), and where the subnet prefix is
> [$prefix::/n].
>
>
RFC4291 says "a subnet prefix is associated with one link", but a pdhost
prefix is assigned to a host, which doesn't really behave like a link
(there's no neighbor discovery, for example.)

So, is a pdhost prefix actually a "subnet prefix" (with reserved
addresses), or something distinct?

I would advocate for permitting the host to do whatever it wants with the
(128-n) bits.  That could include "treat it like a regular subnet prefix"
or "build a service where every hash(content) gets an IP address."