Re: [v6ops] question about draft-jjmb-v6ops-unique-ipv6-prefix-per-host

Ole Troan <otroan@employees.org> Mon, 03 July 2017 07:23 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 520D3129AE3 for <v6ops@ietfa.amsl.com>; Mon, 3 Jul 2017 00:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 Dc2O_m9UhA9r for <v6ops@ietfa.amsl.com>; Mon, 3 Jul 2017 00:23:29 -0700 (PDT)
Received: from accordion.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0393127735 for <v6ops@ietf.org>; Mon, 3 Jul 2017 00:23:28 -0700 (PDT)
Received: from h.hanazo.no (77.16.64.96.tmi.telenormobil.no [77.16.64.96]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by accordion.employees.org (Postfix) with ESMTPSA id 5B4CF2D502A; Mon, 3 Jul 2017 07:23:25 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 3A639E535725; Mon, 3 Jul 2017 09:23:24 +0200 (CEST)
From: Ole Troan <otroan@employees.org>
Message-Id: <645EA227-F9E8-4B15-878B-83BC8FD9809A@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_75C16191-4A81-474B-A447-3C9CCC6D30B4"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 03 Jul 2017 09:23:23 +0200
In-Reply-To: <CAKD1Yr1UNvfrozET0Ay4LCtZe-NSBAGwbCcpye7JhGtpzyT2Sg@mail.gmail.com>
Cc: Jordi Palet Martinez <jordi.palet@consulintel.es>, "v6ops@ietf.org WG" <v6ops@ietf.org>
To: Lorenzo Colitti <lorenzo@google.com>
References: <5348A2C7-D762-470B-9BC9-86B8A09E6369@consulintel.es> <CAKD1Yr1UNvfrozET0Ay4LCtZe-NSBAGwbCcpye7JhGtpzyT2Sg@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/HVxzdRrCO5BUag6IIC_bKnq-f8c>
Subject: Re: [v6ops] question about draft-jjmb-v6ops-unique-ipv6-prefix-per-host
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, 03 Jul 2017 07:23:30 -0000

> -1
> 
> I think "per host" is the best title. It clearly explains that the network provides a unique prefix for every host. Of course, a host may be connected to other networks at the same time, but that is true whether this draft is in use or not.
> 
> "Per link" is not a good title, because a link almost always has a unique prefix, even though in general there may be many hosts on it.

in my implementation I have a unique link per host.

Ole