IETF Logo Mail Archive

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

Lorenzo Colitti <lorenzo@google.com> Mon, 20 November 2017 10:21 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 11A85129527 for <v6ops@ietfa.amsl.com>; Mon, 20 Nov 2017 02:21:37 -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 ifu5CADf2sPg for <v6ops@ietfa.amsl.com>; Mon, 20 Nov 2017 02:21:36 -0800 (PST)
Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (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 0244A120046 for <v6ops@ietf.org>; Mon, 20 Nov 2017 02:21:35 -0800 (PST)
Received: by mail-it0-x235.google.com with SMTP id m191so11213735itg.2 for <v6ops@ietf.org>; Mon, 20 Nov 2017 02:21:35 -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=eVhiLkIEGHXN7hHg0pIl23V7p37zeeDyprJByZlHCiY=; b=MzI7q0YViC6MPGNwVcs0Rn0/Sh7CzmteRbWSwleDkcqbsYUcHu8F7xQnakzI/CLi92 Zx51qDddH93Osm2nkkquZ0wuvXVwzoMetq+4SOY+702mJMToWx/Om7t12tLksOY2C6/n t2PLXNRVinTxNu+Bl4PpV4iqZt8cUn9i7Gd8iOnyvyoO6CWD50FeMDZSeldxM0RQz9Dc Tp5G/xrhCsuGX5MJvFEyPnwf5iD+uImS5VfUyAVZh0+CI/hjhpr4a3joDKw3vDTDh+/x FxbdEn1PNFjqnx73bOvxU/2X0W1AIu/00BG1KivVWB/o8vzwuncJL0PnYUcfiIrmidPv gnBQ==
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=eVhiLkIEGHXN7hHg0pIl23V7p37zeeDyprJByZlHCiY=; b=ZH54SAdMY1qGH/wHyembME8lpudYiGylbVU74auysRf2WSCNe+6jtJdHVx+QEIa9Kv fUCYgMj9sXJTbgHUTxWF7odzEyAzZaL9AlhPRfFyQBOaZaNZxywLsHwcoB2WMOhXb1pB i2HLKVoW97oc0i3OlqCfUjMAZ/YjuQpZEL8l1jkkT2AGDJnQ0ObCt6M3vOMnaKkT2s6J 30zvAO8RrdY16xL30pSJW34BilYg446uFf41lZnCo+i9iLt5M6tyKzMvtwkYfi5HVOLj lubyUQJXPr7CqARWnLag+rQ7zJa1iFD2tWoAmaIFF7hR3+esLLIsKMSQxYxV4VwAjebY gbXA==
X-Gm-Message-State: AJaThX52ysK+6vA1hLZSLncAYvZPXKmTPF0j+MTInVSgUxH+7rI3OL3O f6V65U0FRbPBqqc1FGOohwuNNbPAudhLXC2L7NcMBg==
X-Google-Smtp-Source: AGs4zMbPCK8823fPVEIW3/QAM6ieEvEFJVdmHh8YkqvNr4tRsodhO0L/iosqo+b8TFmADbpx5cQqYIlc3Hvg/3iLxI0=
X-Received: by 10.36.14.207 with SMTP id 198mr19269025ite.66.1511173295017; Mon, 20 Nov 2017 02:21:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.16.155 with HTTP; Mon, 20 Nov 2017 02:21:14 -0800 (PST)
In-Reply-To: <D300BD4F-29C2-4546-B601-8E109773F9B8@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> <CAKD1Yr0ZF-0QXTwtUaA4HQ0meS0=REhUD-TJWXvAxL1VtA4OOA@mail.gmail.com> <D300BD4F-29C2-4546-B601-8E109773F9B8@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 20 Nov 2017 19:21:14 +0900
Message-ID: <CAKD1Yr0BH_qi25a65fowkiO2HZOqQ=uT7dgXr1epK=XpsgjUrQ@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="001a1143f5347217c9055e67734b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/qRYtIwL4bVf9dZKgs_j3STHgrH0>
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 10:21:37 -0000

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

> > 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.
>
> I really don't want to see the hack of 7278 spread further.
> My point was that there is no way for the host to know this prefix is
> dedicated to it, apart from making a guess based on data-link layer type.
>

Sure, in general there is no way for the host to know (at least currently).
But there are lots of things that we can say the host can/should do if it
does know that the prefix is dedicated to it. Two ways it can know are a)
it's a 3GPP link and b) it received a prefix delegation.

v2.23.0 | Report a Bug | By Email