Re: [v6ops] PI [ULA draft revision #2 Regarding isolated networks]

Gert Doering <gert@space.net> Sat, 31 May 2014 21:31 UTC

Return-Path: <gert@Space.Net>
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 D26F01A00CA for <v6ops@ietfa.amsl.com>; Sat, 31 May 2014 14:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 cvd5Vs3sCmFa for <v6ops@ietfa.amsl.com>; Sat, 31 May 2014 14:31:41 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC3091A00C3 for <v6ops@ietf.org>; Sat, 31 May 2014 14:31:40 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 78CE7602AA for <v6ops@ietf.org>; Sat, 31 May 2014 23:31:33 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 47FB16012B for <v6ops@ietf.org>; Sat, 31 May 2014 23:31:33 +0200 (CEST)
Received: (qmail 24923 invoked by uid 1007); 31 May 2014 23:31:33 +0200
Date: Sat, 31 May 2014 23:31:33 +0200
From: Gert Doering <gert@space.net>
To: Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>
Message-ID: <20140531213133.GB46558@Space.Net>
References: <m2iooq4oqi.wl%randy@psg.com> <5385762E.5020901@dougbarton.us> <5385AA97.1050207@fud.no> <53864DCB.5070202@gmail.com> <53865EA2.9000502@fud.no> <02dc01cf7c06$cc6a4bc0$4001a8c0@gateway.2wire.net> <97390E9C-460F-4D08-AFCE-E4A991E2B0E4@cisco.com> <46D22F62-3528-4B9D-9FCF-C9C7466A9ABA@delong.com> <20140531104145.GQ46558@Space.Net> <m1WqqZ4-0000DqC@stereo.hq.phicoh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <m1WqqZ4-0000DqC@stereo.hq.phicoh.net>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/nLvx8BqdQd6ahktzL4XXqsU9x60
Cc: V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] PI [ULA draft revision #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: Sat, 31 May 2014 21:31:44 -0000

Hi,

On Sat, May 31, 2014 at 11:11:42PM +0200, Philip Homburg wrote:
> >Maybe you should step down from your "I have PI, I like it, everybody must
> >have PI" soapbox and actually look at what, for example, homenet has 
> >achieved in the last years.  This stuff looks complicated (and under the
> >hood, it is), but the end user experience "take this box, plug in a number
> >of ISPs, things work, no further configuration is needed(*)" is nothing you
> >can match with a PI network.
> 
> I can see how you can do do multiple PA prefixes client side. Done that
> for years now. Even with different routers providing the upstreams. No problem
> there.
> 
> But I have nothing to update my DNS zones. How do I reflect which links 
> are up or down? Is there even a draft for that? What's the BCP for TTL
> values, DNSSEC, etc?

This is where things get interesting.  You, Owen, I are not "the 99% home
users out there" - home users don't do DNS zones, because they do not 
control a DNS server...  (they do mDNS because it's automatic and works
fine for in-house purposes).   Where this falls apart, of course, is when
you need to setup some sort of "call me" service, like remote help, 
access your home disks from abroad, etc.

Some router vendors (AVM) have started to offer dyn-dns services that
attach the current (dynamic) prefix to a statically known host-id and
thus provide DNS to reach "home devices".  I'm not aware of specific 
drafts that govern how IETF thinks this *should* be done, though.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279