Re: [v6ops] WGLC: draft-ietf-v6ops-unique-ipv6-prefix-per-host-02 - multiple prefixes per device

otroan@employees.org Thu, 16 March 2017 09:45 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 8FAF5126DD9 for <v6ops@ietfa.amsl.com>; Thu, 16 Mar 2017 02:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 TFDbkfe3Gul2 for <v6ops@ietfa.amsl.com>; Thu, 16 Mar 2017 02:45:35 -0700 (PDT)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id CF7181272E1 for <v6ops@ietf.org>; Thu, 16 Mar 2017 02:45:34 -0700 (PDT)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 16 Mar 2017 09:45:34 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 3571FD788D; Thu, 16 Mar 2017 02:45:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=eaQWA9YrTgQVT7+shXXiqhsUvnE=; b= LlqsFdkNHY05PfzrvJYcfDmkxIabVxAcLLVg2P+JAIfpqlMa92DQBkCQROAWahT6 jeuuIICEcqqLcgzImp9xhASkZ2SS5QDjtsLN4A7xnsQzOW/beHsjE+48eospRyW5 TOr2kkN2Q72qvbRegSdZSugmCbzB1kQLzw/C/esCN+c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=pZ00awe3FSQmY5jgj+8sEyh CQKvw0FIRvYIQGqdsv31vRx0/NtJkvlBxMwoBpI5oA2Oyy2fM1i/RL/MYTxmFTaE pLupLMyDFjemiE6XI8aG6NllJ7GTOSDkNghGtWpWsCc4/8je9Qhb/Arn1W1FWxed FJKZvqpxQ6D8TVU9R3Ww=
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id BCC6AD788B; Thu, 16 Mar 2017 02:45:33 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id E68189F16887; Thu, 16 Mar 2017 10:45:31 +0100 (CET)
From: otroan@employees.org
Message-Id: <39A15217-1802-4CE0-8303-1981D399A6A7@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_800B9481-591E-4DD2-A1E4-7AD529332525"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Thu, 16 Mar 2017 10:45:31 +0100
In-Reply-To: <EF0F4950-F238-4001-BA74-D9440524BEFA@gmail.com>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
To: Fred Baker <fredbaker.ietf@gmail.com>
References: <BLUPR0501MB2051704E825BCA03EEB09D79AE240@BLUPR0501MB2051.namprd05.prod.outlook.com> <c8c0f5be-28bb-ba31-16da-7fc7e3fccec0@gmail.com> <20170316082639.GF2367@Space.Net> <29F9E911-E637-456D-A930-3316FFD93C41@jisc.ac.uk> <27AE6A05-C742-44BF-98E8-BFCEC72316F2@employees.org> <EF0F4950-F238-4001-BA74-D9440524BEFA@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CNQPLf9rRFPPwJdqjLTC-qDuf-Y>
Subject: Re: [v6ops] WGLC: draft-ietf-v6ops-unique-ipv6-prefix-per-host-02 - multiple prefixes per device
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: Thu, 16 Mar 2017 09:45:36 -0000

Fred,

>> A little flippant perhaps, but can you give an example of a node that isn't a router anymore?
>> I think the statement "All hosts are routers" is almost true.
>> 
>> Certainly my phones, laptops, lightbulbs are all routers.
> 
> </hat>
> 
> I'd like to understand your meaning, if you don't mind.
> 
> A router, per RFC 2460, is a system that receives a message, does no processing on its content, but repeats it to another system. A host is one that receives messages and processes their application layer content.

2460: router      - a node that forwards IPv6 packets not explicitly addressed to itself.

> I think it's fair to say that an iPhone etc has more than one interface; WiFi and LTE, perhaps. A laptop often has several interfaces such as physical and wireless Ethernet, USB, Bluetooth, and other things. Having multiple interfaces, however, does not qualify it as a router; what qualifies it as a router is when it receives a message and repeats it, usually on another interface.

Phones act as routers when they do tethering.
My laptop acts as a router when the hypervisor running on bare metal routes traffic between the physical NICs and a set of VMs and containers.

> Yes, an iPhone acting as a hot spot can route between its WiFi and LTE ports. If it is not configured as a hot spot, however, it generally uses its many interfaces as ways to receive messages, pass them to applications, and respond to them. Absent a specific (and unusual) configuration, an iPhone therefore is a host, not a router.

Correct, and switching between the two requires a single swipe with suitable finger.
And my lightbulbs, builds up a mesh and forward packets for each other. Aka router.

> Are you and I using the words in the same way? I get the feeling that you see multiple interfaces and infer "router".

No.
Sure, many nodes can be configured to act either as hosts or routers. In IPv4 the typical case is that it pretends to be a host northbound  to the network. Unfortunately that's how it is likely to pan out in IPv6 too...

Cheers,
Ole