IETF Logo Mail Archive

Re: [v6ops] new draft: draft-vyncke-v6ops-ipv6-only-thin-clients

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 27 June 2015 23:54 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F02441ACDEB for <v6ops@ietfa.amsl.com>; Sat, 27 Jun 2015 16:54:16 -0700 (PDT)
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 hnaVtI7wpOOU for <v6ops@ietfa.amsl.com>; Sat, 27 Jun 2015 16:54:15 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 833D71ACDF1 for <v6ops@ietf.org>; Sat, 27 Jun 2015 16:54:15 -0700 (PDT)
Received: by paceq1 with SMTP id eq1so86159515pac.3 for <v6ops@ietf.org>; Sat, 27 Jun 2015 16:54:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wuNCPBKzw+VNRkkODj1bZBLcjI3ONHLS58gQpErJyks=; b=rejaVd2x1lsMirF+ClYKIlc86nQWcON4C7+UC/mgt/v3eX5ntJ+Ep8cFMJboiEL3fj Id1H0czLbJYI8ai5R1sjoum7ObCXCfNI4oOm5AWZdV0SOJFqz38cid3xjtH9RSGk1UT8 GYB4WUk2odm1MUr5sOI/0KVwbUr9Umzus1/klVke0YZ8wNiBp+vjIL39lbMEVhtM8W5J 9bsaS4qQbjJcPQqHcOTlD5wLPgjCnEkQ/Yf1wLT5fYD+BheH2HzvYbGWoOI0l9LqYzzy 3dCe/QliMdiUHN62E1sEmi52p7Zf3m9f7gN+8JVgr9LTIid1Y8pWSB9ZDsL2tQcrpGIP 88Lg==
X-Received: by 10.70.129.73 with SMTP id nu9mr17232655pdb.166.1435449255235; Sat, 27 Jun 2015 16:54:15 -0700 (PDT)
Received: from ?IPv6:2406:e007:7d57:1:28cc:dc4c:9703:6781? ([2406:e007:7d57:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id cz1sm1369120pdb.44.2015.06.27.16.54.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 27 Jun 2015 16:54:13 -0700 (PDT)
Message-ID: <558F37A1.101@gmail.com>
Date: Sun, 28 Jun 2015 11:54:09 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: v6ops list <v6ops@ietf.org>
References: <201506271147.t5RBl19P016483@irp-lnx1.cisco.com> <4C545B41-FE57-4B99-9635-B02BE22CC1BA@cisco.com> <75B6FA9F576969419E42BECB86CB1B89168AC6EE@xmb-rcd-x06.cisco.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B89168AC6EE@xmb-rcd-x06.cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/BftYLXewC2V8j4JnVMKdhEZRMng>
Cc: <>
Subject: Re: [v6ops] new draft: draft-vyncke-v6ops-ipv6-only-thin-clients
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 27 Jun 2015 23:54:17 -0000

> 1.  Wake-on-Lan
...
>    for a specific host.  This is called the magic packet: with the
>    Ethernet payload having somewhere 6 bytes containing 0xFF followed by
>    16 times the network interface datalink-layer address.

How is this going to work with surveillance-averse clients that change
their MAC address from time to time? I think wake-on-lan is going to
need a complete rethink (including IPv6, of course) because of this.

It seems to me that to solve this *and* the PXE issue, there's going
to end up being some requirement for the thin client to wake itself
up periodically and execute some sort of discovery process. (Something
we are going to need in the Anima WG, too, IMHO.)

Regards
   Brian

v2.23.0 | Report a Bug | By Email