Re: [v6ops] disconnected homenets (was: #2 Regarding isolated networks)

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 23 June 2014 14:57 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 3D7B21A0653 for <v6ops@ietfa.amsl.com>; Mon, 23 Jun 2014 07:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.283
X-Spam-Level:
X-Spam-Status: No, score=-2.283 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 GvspgO5oB73W for <v6ops@ietfa.amsl.com>; Mon, 23 Jun 2014 07:56:59 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 890E41B2AFA for <v6ops@ietf.org>; Mon, 23 Jun 2014 07:56:51 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s5NEunim027276 for <v6ops@ietf.org>; Mon, 23 Jun 2014 16:56:49 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E5B56202B3A for <v6ops@ietf.org>; Mon, 23 Jun 2014 16:58:43 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DA592201086 for <v6ops@ietf.org>; Mon, 23 Jun 2014 16:58:43 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s5NEuZoe014568 for <v6ops@ietf.org>; Mon, 23 Jun 2014 16:56:49 +0200
Message-ID: <53A84023.1060008@gmail.com>
Date: Mon, 23 Jun 2014 16:56:35 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6B9A@nkgeml506-mbx.china.huawei.com> <1401141423.52956.YahooMailNeo@web162206.mail.bf1.yahoo.com> <5383C2CF.6040205@gmail.com> <1401230263.69077.YahooMailNeo@web162206.mail.bf1.yahoo.com> <53854B03.8040702@gmail.com> <1401312298.99614.YahooMailNeo@web162205.mail.bf1.yahoo.com>
In-Reply-To: <1401312298.99614.YahooMailNeo@web162205.mail.bf1.yahoo.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/ilU_FfE9p1vz-IXoj1vOP7lKPno
Subject: Re: [v6ops] disconnected homenets (was: #2 Regarding isolated networks)
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: <http://www.ietf.org/mail-archive/web/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, 23 Jun 2014 14:57:01 -0000

Old email, sorry.

Le 28/05/2014 23:24, Mark ZZZ Smith a écrit :
[...]
> The use case I like to imagine is a home user streaming a video from
> their NAS to their TV over their internal network. That should use
> ULAs so that a failure of their Internet connection/Global addressing
> has no impact on watching their movie. If the movie failed because
> the Internet connection/global addressing failed, that user will call
> the ISP's helpdesk. But why should it fail! The home users internal
> network is fine, it is only external connectivity that has failed.

I hope this requirement is considered in the homenet architecture 
discussion.

Too often the in-home Internet-disconnected network can not work internally.

Alex

>
> People might argue that enterprise networks are different and they
> are - they're simpler! Enterprise networks have technical staff on
> hand that can troubleshoot networks and resolve faults. If you can
> make IPv6 work seamlessly for home networks and their non-technical
> "operators", you've solved the harder problem. Since enterprise
> networks also value the same things home networks do - seamless
> operation, robustness against failure, stable internal connectivity,
> you've solved most of the enterprise network problems too.
>
>> It doesn't conform to RFC 7084 either, which clearly
>
>> states that "prefix(es) (and ULA prefix if configured...)" must be
>> advertised.
>>
>
> The precursor to 7084 (6204) was in development at the time, but it
> wouldn't have helped because they were ignoring our feedback.
> (Another CPE vendor was much better and almost too keen - they were
> sending me new software to test within 24 hours after reporting an
> IPv6 issue.)
>
> Regards, Mark.
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>