IETF Logo Mail Archive

Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

Ted Lemon <mellon@fugue.com> Thu, 19 July 2018 02:09 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B833A130E78 for <homenet@ietfa.amsl.com>; Wed, 18 Jul 2018 19:09:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 nV-ADe_Onqn6 for <homenet@ietfa.amsl.com>; Wed, 18 Jul 2018 19:09:18 -0700 (PDT)
Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4D57126BED for <homenet@ietf.org>; Wed, 18 Jul 2018 19:09:18 -0700 (PDT)
Received: by mail-it0-x235.google.com with SMTP id w16-v6so7027778ita.0 for <homenet@ietf.org>; Wed, 18 Jul 2018 19:09:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PfDZDCOpffQ3m+vhqSNi1dBVqxcTHM4JRXtW2V5RpFY=; b=S77EgAygg/tcUPwY3QHA3WsdgGHge65+HPllQnWGOAdxRQ4JgrThES6r9AftSD2qpB v2oA+iQS81I7M/O1m3nbjxL6aHRiHOiZJ3QS8hVINdxwboS+YdSiJDXIWg1D7e0O50gN LK6/VoAvJLPKQ6/DKoQ9cOHKpPCNz4vQqTIZ8juKfIDACfNir12xTUy/3oeqATply9lO u5JEy/nAwqbIkUyR95D110Jur4IELEZXTNNaYXu4HA2lZdmeidjgzrrw26YFA1ulrs1h UdKcG6+rwHtk8XkVnX7qRKHuZnpReZNl+hr5cGwqXC2K5sw74G4NMmOrSgoV/R8EWZuA ahLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PfDZDCOpffQ3m+vhqSNi1dBVqxcTHM4JRXtW2V5RpFY=; b=tF3UzxoLKp93ogGumAV5zsj/rhxnvbsRU9WsM/8fdo7yK8OHtHurtM4UzW9xz8BOb0 AOQFu6xcZXSWn6dHntmbuOL6LZsm8lTDZHygNhCvvg2UMItTQJXFp+nqBAUejUSs0iYt N2qutpzR0DdTASbj5w4MLIsIFD1kHvYYVFtPOyKRX9invoxIuTllKS/+GudYsPxAyvyN wW6kvDZa0M5LQbbA43TPMydZ9wnwO+TeIxwPv3Rk/YHI1QhoIDM4p/f1JmI+JSyO+Zfb TJD/xu79x6yvxdAcRV/f7HJM/MYYOEpNPmpSuxkH0hDiv+4idcqHBVHnzAmKLtM7195U x7bQ==
X-Gm-Message-State: AOUpUlEBBcyWNRdWimXojjvp5H66WTGOUfsXBA0pUeEKKg3HgvPTXhAg C+LtMEMAUi6f4gio3gaTmiKZgqNr2M/exyNb5UUxNg==
X-Google-Smtp-Source: AAOMgpembo5323HnlOjyVX3fBpghvWhFYyEHMO06uG8mu3u/ZQrmLkowS6YfuAQsKHlrbaFIlSs17doQuMFZeXsh/y0=
X-Received: by 2002:a24:d485:: with SMTP id x127-v6mr4217871itg.82.1531966158028; Wed, 18 Jul 2018 19:09:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:5f86:0:0:0:0:0 with HTTP; Wed, 18 Jul 2018 19:08:37 -0700 (PDT)
In-Reply-To: <ce8e5d6e-cfce-bf89-48f6-1779d47132a6@gmail.com>
References: <87bmb4oy1w.wl-jch@irif.fr> <CAPt1N1nz+SAZNjUEFQ1GzmrskWW0DAmh1TNaN1icPsD-YPd69g@mail.gmail.com> <ce8e5d6e-cfce-bf89-48f6-1779d47132a6@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 18 Jul 2018 22:08:37 -0400
Message-ID: <CAPt1N1kJ-QRAsxXLooNXsLrVvs5w+WFp=y_YnF8z2vzdBRuQFg@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, HOMENET <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a85afe057150aa69"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/yexmV1XvRYKMhOvkA0cKFnpljSw>
Subject: Re: [homenet] In-network connectivity and HNCP: IPv6 ULA
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 19 Jul 2018 02:09:22 -0000

Sure.   If no services are advertised over IPv4, then we needn't offer IPv4
on the network at all.   But if we do offer IPv4 on the network, it should
be stable, and not vanish at the whim of the ISP.

On Wed, Jul 18, 2018 at 9:52 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Ted,
> On 19/07/2018 13:36, Ted Lemon wrote:
> > In order for IPv6 to be useful, you need naming to work. We had this
> > discussion when I brought this up last year. It should be possible for an
> > IPv6-only homenet to work. But if we want homenet to be widely adopted, I
> > do not think this is the correct default behavior:
>
> What "this" do you mean? Switching to ULAs to maintain local
> connectivity? What's the surprise? There's no reason there
> wouldn't be corresponding AAAA records, is there?
>
> > it violates the
> > principle of least surprise. Further, unless you prevent services from
> > advertising IPv4 addresses,
>
> We have a plan for that: draft-ietf-6man-ipv6only-flag-01
>
>     Brian
>
> > dropping the IPv4 uplink definitely will cause
> > connections to hang.
> >
> > On Wed, Jul 18, 2018 at 8:43 PM Juliusz Chroboczek <jch@irif.fr> wrote:
> >
> >> During his talk, Ted claimed that he lost all connectivity when his
> uplink
> >> went down.  This should not happen -- HNCP normally maintains an IPv6
> ULA
> >> that remains stable no matter what happens to DHCPv6 prefix delegations
> or
> >> DHCPv4 leases.  This is described in Section 6.5 of RFC 7788, and it is
> >> the default behaviour of hnetd.
> >>
> >> Either Ted had tweaked the configuration of hnetd (which one should not
> >> do -- hnetd does the right thing out of the box), or he was using
> software
> >> that doesn't speak IPv6 or ignores ULAs.  At any rate, HNCP does not
> have
> >> the issue that Ted described.
> >>
> >> -- Juliusz
> >>
> >> _______________________________________________
> >> homenet mailing list
> >> homenet@ietf.org
> >> https://www.ietf.org/mailman/listinfo/homenet
> >>
> >
> >
> >
> > _______________________________________________
> > homenet mailing list
> > homenet@ietf.org
> > https://www.ietf.org/mailman/listinfo/homenet
> >
>

v2.23.0 | Report a Bug | By Email