IETF Logo Mail Archive

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

Lorenzo Colitti <lorenzo@google.com> Mon, 20 November 2017 08:50 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 9EF281294BD for <v6ops@ietfa.amsl.com>; Mon, 20 Nov 2017 00:50:45 -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 oXBW9mwQ8p5x for <v6ops@ietfa.amsl.com>; Mon, 20 Nov 2017 00:50:44 -0800 (PST)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 7FDD41294E8 for <v6ops@ietf.org>; Mon, 20 Nov 2017 00:50:32 -0800 (PST)
Received: by mail-io0-x22d.google.com with SMTP id 71so14956483ior.7 for <v6ops@ietf.org>; Mon, 20 Nov 2017 00:50:32 -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=99CfiQ1g0hBbGvaValLaYvThP0MaEinhMM/+c1WnU70=; b=H2MZUYedJo+SQRZB6TpDwC0TuOflaPmfJ5GKZLVSNnBA8YdyxeZlVN0KDuyAZEKUT7 JBriluCAIZwzrrb/YV795ZSVLkQjxKpfTC/XdJS2CPpOvJEz/pmG+dnn6gDYx0iTRX/l qW7uGYj4escA40onQsf1hXzJocXIPkXReEzbNL2CzJJCeu3tv3i2ysOB5UW8GP6+P+GA NICSxR2mmtJt4yFZKsin7x7uCv4CnTaR/Odv9btKsgF5Kt4GcOsgnxthYqOyXBIeQ1vm +oKbeyfLkFirVNeM/yAy06zzLZAPMvUjm5rHYQZqcjLmC2BpPfqWa46WfgeclgC42vNE NwMA==
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=99CfiQ1g0hBbGvaValLaYvThP0MaEinhMM/+c1WnU70=; b=NVNBVtT+9ADcTCg/K47Y/6QO5LDgtPVY9POeMsNMo+eZrK4IZgBV5eAOnTIvIQDZfA giZroWzzV6UnSR8tDoXgNnYxTBDadicJoYAUyeOf1tlbhsk2Yf3mniYTzEdOwofKCAsc q9UiBOUT3xOc+FYE9NxGyrLYVRsya/8+uAZQ11EOc3ORtoNpBzMLNhc+IrAwZT9WXW1t YNOxzL/GdJodA2hVhA+mQ8wfrqrlr3SuEMdXQvgbUfBijip4mL7x5W2TwPvo9mG+LIAy QPWd9+fpbqTlSneqUhmqTvCWfpMTxcH/sKCgnMjmRrpyItE8tUT+TXgMGDbmKj042QvY qLcg==
X-Gm-Message-State: AJaThX5yM1/53h9f34yVnbDk5kw1msd+3JhvzxFYdmpAoPKn32Y6rBpZ U8Wsb9sQgJe0ay/01GEnJw2sSSA1K2O/GfrMA1C30g==
X-Google-Smtp-Source: AGs4zMZZYGGMF/pUMA1zRqXhwU03m808Fr3FDbhdm73BnKluSMFPRB21ABqU9PV2QKP36Ig0L9X4ITXFXrctMikVKrk=
X-Received: by 10.107.16.206 with SMTP id 75mr13011183ioq.83.1511167830380; Mon, 20 Nov 2017 00:50:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.16.155 with HTTP; Mon, 20 Nov 2017 00:50:09 -0800 (PST)
In-Reply-To: <ABF8D7E4-BF1A-422F-9652-69394E000913@employees.org>
References: <7FC2CA6E-8BF7-47BC-9164-1877FAF83FD0@gmail.com> <962041fbaee844b5a4cdd82012440dbe@XCH15-06-08.nw.nos.boeing.com> <CAKD1Yr2=qVdGNzvwCXaofhH=fBaQS0M05Lg6MKF3MEze7UUfXg@mail.gmail.com> <ABF8D7E4-BF1A-422F-9652-69394E000913@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 20 Nov 2017 17:50:09 +0900
Message-ID: <CAKD1Yr0ZF-0QXTwtUaA4HQ0meS0=REhUD-TJWXvAxL1VtA4OOA@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="001a113eda96ba87f3055e662d6d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/7UEf9xJBJasUbXTq8vaMHtBafC4>
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:50:46 -0000

On Mon, Nov 20, 2017 at 5:42 PM, Ole Troan <otroan@employees.org> wrote:

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

I think there are properties we can generalize such as "hosts don't need to
send DAD packets to the network for any address formed from that prefix",
"hosts can likely form as many IPv6 addresses from that prefix without
causing ND cache scaling issues in the network", "hosts can use RFC 7278
tethering safely", etc.

v2.23.0 | Report a Bug | By Email