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

Mark ZZZ Smith <> Mon, 29 June 2015 02:35 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 36C9A1B2E79 for <>; Sun, 28 Jun 2015 19:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 3.202
X-Spam-Level: ***
X-Spam-Status: No, score=3.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sxvaa1h7eOmz for <>; Sun, 28 Jun 2015 19:35:08 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 897091B2E78 for <>; Sun, 28 Jun 2015 19:35:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s2048; t=1435545307; bh=ftzhlXUVckEnSAxCKqpUUmvwgOM8on819M8WJlrm6tQ=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=uAw5SeKJoHO0nL+KOFui/dH42d75ljnEomOWXBxNPzEdkmvul1oFHn+iFLP1tc2zdw4muv5rhEGv1BkASeATelYwsAXb1yoDGKlsYUE1CHurYmfvMUgNtYkS2Ju6OsFjI80kvaX1yh6N3taf8FHhXIu6eEC20CbL5K/owqN5TGK4q7N7SNjWXgk/LQTjTL5+yB0eq2CHqLAWkv7TpI5l5b8uBsRnNkYN5JtmUOzJ6Xcce4MJwxaq9yeuFKOAlbRtBiCVcbDjGfTTAxmCN4igKz25OZRN0yxNLkKxJyrKls+MAnTSnBPV7GNbvWwZpAVxDgM5Rqc8I3/4LGGDUIjUxg==
Received: from [] by with NNFMP; 29 Jun 2015 02:35:07 -0000
Received: from [] by with NNFMP; 29 Jun 2015 02:32:07 -0000
Received: from [] by with NNFMP; 29 Jun 2015 02:32:07 -0000
Received: from [] by with NNFMP; 29 Jun 2015 02:32:07 -0000
Received: from [] by with NNFMP; 29 Jun 2015 02:32:07 -0000
X-Yahoo-Newman-Property: ymail-4
X-YMail-OSG: xp8v560VM1ntSNIoDj9TmPIaxKcQJ4JeKy9imD99zn2WCeTPNF46i.FwpJT2kLY ntDECtnTXby4vnwJfkkDpGP0m9KR9YZrHhup4TQTMrWMIV4G8P_sDnqpZAXCYeLz0MqIL6tu.Zf_ Q05.E5gaBubd91RWJwF1AkRDtwKECy5Qh3OBsYWfxoH_C1Brqo7PwwN_AEe5CBgi08ugThuyP_IM z6rybuOHXaqYMYIKALXD1Uc7oznEL935RtOqVyqJj2MibEX7pH6Lac.oF.KW9fM.R0H6Pfd_90tk jPkmtejpJKyEqi3ipBNi8_s_BDsriRGg7hHUhJWQFpaA8O2nXThQVvSOpwbXgPl0PSfVKrnYYf0u S8Z4FTHoQqIiyUy9Dhpml5tqRLLMpXlsc3dNJjIb5eqV7FyntRNk6Vsc15T7o61dttdZVW08ulyn RpfH5AmqwZz2LOxRWtdJ0yrRL9YnCSE4LXsqFnB0x03V73vvJk5qPniVSzQlbSYWaAsy9gIg6o55 Rygmip3N0VcJdkhbql9OE2B_28oqWiwgpm2Mmm6D4Vh0fZhy.RGy3b_QDfpg.
Received: by; Mon, 29 Jun 2015 02:32:06 +0000
Date: Mon, 29 Jun 2015 02:32:06 +0000 (UTC)
From: Mark ZZZ Smith <>
To: Brian E Carpenter <>, v6ops list <>
Message-ID: <>
In-Reply-To: <>
References: <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_1601695_284066729.1435545126209"
Archived-At: <>
Subject: Re: [v6ops] new draft: draft-vyncke-v6ops-ipv6-only-thin-clients
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <>
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 29 Jun 2015 02:35:10 -0000

      From: Brian E Carpenter <>
 To: v6ops list <> 
 Sent: Sunday, 28 June 2015, 9:54
 Subject: Re: [v6ops] new draft: draft-vyncke-v6ops-ipv6-only-thin-clients
> 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.

/ As I haven't worked on a network that uses WoL, I was thinking that it must already be pretty onerous to be maintaining a list of devices and their MAC addresses for WoL purposes. 
/ There seem to be a number of other WoL methods; here are the list of WoL packet types/events that can be set using the Linux 'ethtool' utility for a NIC:

--       wol p|u|m|b|a|g|s|d...              Sets Wake-on-LAN options.  Not all devices  support  this.   The              argument  to  this  option  is a string of characters specifying              which options to enable.
              p   Wake on PHY activity              u   Wake on unicast messages              m   Wake on multicast messages              b   Wake on broadcast messages              a   Wake on ARP              g   Wake on MagicPacket™              s   Enable SecureOn™ password for MagicPacket™              d   Disable (wake on  nothing).   This  option                  clears all previous options.
       sopass xx:yy:zz:aa:bb:cc              Sets  the  SecureOn™ password.  The argument to this option must              be 6 bytes in Ethernet MAC hex format (xx:yy:zz:aa:bb:cc).--
/ Looking at the WoL spec referenced, that looks to be the MagicPacket option mentioned above. Perhaps networks using WoL are using more coarse methods which would continue to work even with changing MAC addresses.

/ Regards,/ Mark.

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


v6ops mailing list