Re: [homenet] Let's make in-home ULA presence a MUST !?

Mikael Abrahamsson <swmike@swm.pp.se> Tue, 14 October 2014 10:14 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2921A7032 for <homenet@ietfa.amsl.com>; Tue, 14 Oct 2014 03:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.229
X-Spam-Level:
X-Spam-Status: No, score=-2.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, PLING_QUERY=0.994, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] 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 wslaBL5yovIP for <homenet@ietfa.amsl.com>; Tue, 14 Oct 2014 03:14:37 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76E891A702A for <homenet@ietf.org>; Tue, 14 Oct 2014 03:14:37 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E3F7EA1; Tue, 14 Oct 2014 12:14:35 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1413281675; bh=z7WfXU8rdmGlkgLExn5uqnqvAWa2PF0tT6JlUWo68bw=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=SwCzt6qWCkHZQYe0J72BL3tJWWLTz5BBSI/oBuwWzfYYzufW5utoOdM9ySD1vpcJq FTTjU6N7HZFyJfl5A+TIco1lI0O97YJz15dAhq2qRUegpf3THbC9gAPYNTUhxWTL2/ 7++ch2/ndQo7oFv8BWcmhDF2rDjt2fNbY5do+j9M=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id DD4B49F; Tue, 14 Oct 2014 12:14:35 +0200 (CEST)
Date: Tue, 14 Oct 2014 12:14:35 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <5846C516-121C-4441-A8D8-62A77C6499D7@darou.fr>
Message-ID: <alpine.DEB.2.02.1410141209230.30853@uplift.swm.pp.se>
References: <72CC13D1-7E7A-4421-B23E-16D8FFAEEB58@darou.fr> <CAAedzxp1R-C5E9RJVMVLRJxPc0w4zooPtqnvWK9eggpZu4=xtg@mail.gmail.com> <alpine.DEB.2.02.1410141020360.30853@uplift.swm.pp.se> <C52D3324-3015-45E0-88CF-D2A778D246B8@iki.fi> <5846C516-121C-4441-A8D8-62A77C6499D7@darou.fr>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/hzwv6XA5xuyQ5Te2x-2kKWU4_iU
Cc: Erik Kline <ek@google.com>, HOMENET Working Group <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Let's make in-home ULA presence a MUST !?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Oct 2014 10:14:40 -0000

On Tue, 14 Oct 2014, Pierre Pfister wrote:

> Looks like a good default policy to me.
> So there always is at least one IPv6 prefix (if not a GUA, generate a ULA).
>
> It still provides always-on IPv6 connectivity. And would therefore simplify protocol design and implementation.
>
> Does it seems like a better compromise to you (Mikael, Erik, Wuyts) ?

I would like to see the following (configurable):

If you have GUA, don't use ULA.
When last GUA lease expires, just keep this GUA until something else shows 
up, then deprecate and move away from it.

I would really prefer to have RIO so host doesn't see default route using 
this GUA with no connectivity.

My rationale for this is to avoid to have GUA expire and popping up ULA, 
and then deprecating ULA again when GUA shows up.

Advantage of deprecating GUA as soon as outside connectivity goes away is 
that using 0 lifetime RAs for this prefix when there is no outside 
connectivity and popping up ULA, means RFC6724 hosts will do the right 
thing.

I'm conflicted as to what the correct behaviour is. RFC3484 hosts probably 
doesn't support RIO either, so we're screwed either way.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se