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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 29 June 2015 08:32 UTC

Return-Path: <alexandru.petrescu@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 10C9C1A8838 for <v6ops@ietfa.amsl.com>; Mon, 29 Jun 2015 01:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.583
X-Spam-Level:
X-Spam-Status: No, score=-3.583 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 bmmCE2awkhUM for <v6ops@ietfa.amsl.com>; Mon, 29 Jun 2015 01:32:02 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFA881A883C for <v6ops@ietf.org>; Mon, 29 Jun 2015 01:32:01 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t5T8W0YC011320 for <v6ops@ietf.org>; Mon, 29 Jun 2015 10:32:00 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6E449201620 for <v6ops@ietf.org>; Mon, 29 Jun 2015 10:35:02 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 63C762015FA for <v6ops@ietf.org>; Mon, 29 Jun 2015 10:35:02 +0200 (CEST)
Received: from [127.0.0.1] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t5T8Vwf0007365 for <v6ops@ietf.org>; Mon, 29 Jun 2015 10:31:59 +0200
Message-ID: <5591027E.5040005@gmail.com>
Date: Mon, 29 Jun 2015 10:31:58 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
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@ietf.org
References: <201506271147.t5RBl19P016483@irp-lnx1.cisco.com>
In-Reply-To: <201506271147.t5RBl19P016483@irp-lnx1.cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/AZeC8FDVv_2FpeoGYCRxzqxAjoA>
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: Mon, 29 Jun 2015 08:32:04 -0000

> IPv6-Only for Wired Thin-Clients

Examples of recent wired thin clients please?  I am left at the point 
where HP's Apollo workstation and Sun's network computers disappeared 
from the market?

The initial issues presented - "Wake-on-LAN" and "PXE" - are valid in my 
thick laptop as well.

draft says:
>    In IPv6, there is no directed broadcast for good reason.  Only a
>    link-local multicast group such as ff02::1 for all link-local hosts.
>    So, the magic packet for a single host could be sent to this
>    multicast group, reaching all link-local hosts (as switches and
>    routers will forward this packet to all ports/interfaces) and waking
>    up the sleeping node.  But, there is no solution for a remote
>    operator to send this magic packet...

A 'directed broadcast' in IPv4 parlance RFC2644, that needs to reach 
across-the-subnet groups, would mean a classical IPv6 multicast group 
with global scope.  The thin clients on a subnet would join this 
multicast group before going to sleep.

I guess this would work.

I guess this would benefit from a registration of particular multicast 
group.

Or otherwise is there a problem in that the magic packet is a non-IP 
packet?  If yes then either we make the magic packet an IP packet (IPv4 
and IPv6) or we request IEEE to implement link-layer across-the-subnet 
multicast, if such a thing could exist.

Other issues to be suggested to an IPv6-only draft: a recent SDN 
implementation absolutely needs IPv4 to make IPv6 work, details on the 
web.  But this may be too high level?

Alex


Le 27/06/2015 13:47, fred@cisco.com a écrit :
> A new draft has been posted, at http://tools.ietf.org/html/draft-vyncke-v6ops-ipv6-only-thin-clients. Please take a look at it and comment.
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>