Re: [v6ops] draft-ietf-v6ops-host-addr-availability WGLC

Mark Smith <markzzzsmith@gmail.com> Thu, 24 September 2015 01:18 UTC

Return-Path: <markzzzsmith@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 075E01B3456 for <v6ops@ietfa.amsl.com>; Wed, 23 Sep 2015 18:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level:
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 nG43KgzSgeeH for <v6ops@ietfa.amsl.com>; Wed, 23 Sep 2015 18:18:31 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 96C2E1B3427 for <v6ops@ietf.org>; Wed, 23 Sep 2015 18:18:31 -0700 (PDT)
Received: by ioiz6 with SMTP id z6so61426232ioi.2 for <v6ops@ietf.org>; Wed, 23 Sep 2015 18:18:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ALYwBc1WJw8hGZUe772e1GrAnNeH63GyhVtbGs/xNIs=; b=0Zlv4vZRAwt1BgU6ldNva0vwDL9qMaEYqUZRxX4qvLpFzTPibd+eAONo10fVKTAWTT TDwtuCDYPONCWj58C37UCTyNcgVd4E6MxOXOwD7ywxfYGz4ZtaKFbpdCmyLvMuzc5lgd V0RvWRXVqU5trlBBZv0H90+lCOgPpG/Vlt9iOPZZSluKnoT51iuf9NfAZUSKh7lsg75P gWB2NzLePRg3Lyyuv+2sd7CbvY3j3d7ka+3RbO2xvnmxbpTbvwj0T2zTWDj9CyGgn8yP Hh/zU+NaNl1mfcC1waC2SxIyJUK4f6wRf+IbF8zxfQm9eDCFxGOwx5NQuEsNgd6AdYFC YA9g==
MIME-Version: 1.0
X-Received: by 10.107.164.197 with SMTP id d66mr39758809ioj.85.1443057510821; Wed, 23 Sep 2015 18:18:30 -0700 (PDT)
Received: by 10.107.142.148 with HTTP; Wed, 23 Sep 2015 18:18:30 -0700 (PDT)
Received: by 10.107.142.148 with HTTP; Wed, 23 Sep 2015 18:18:30 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1509221519550.8750@uplift.swm.pp.se>
References: <201509201800.t8KI02hV014499@irp-lnx1.cisco.com> <56000864.2080600@gmail.com> <CAO42Z2yN+S9R3B2FhwsSCOC3goRAmtNWP74_SxtNdip3xqcd+Q@mail.gmail.com> <alpine.DEB.2.02.1509221102220.8750@uplift.swm.pp.se> <CAO42Z2zDu02jUOLfoNe_emXOxrOMqS0EY944jacit5TpP68Qbg@mail.gmail.com> <alpine.DEB.2.02.1509221519550.8750@uplift.swm.pp.se>
Date: Thu, 24 Sep 2015 11:18:30 +1000
Message-ID: <CAO42Z2y_XsHoV+R1=3rk8fstFDXrckAMH5_Z8brqwJy0Y-eoDQ@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary="001a1141c8e252b4b00520740220"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/chGpumfQn-Imq3R5TKlg4QLuatY>
Cc: v6ops list <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-host-addr-availability WGLC
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: Thu, 24 Sep 2015 01:18:33 -0000

On 22 Sep 2015 11:22 pm, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:
>
> On Tue, 22 Sep 2015, Mark Smith wrote:
>
>> I've never been completely sure whether IPv6 supports the weak or strong
host model, or whether it is possible for a host/implementation to be one
or the other.
>
>
> I'd say a bit of both.
>
> I find that systems that will respond to an arp query for its eth1
address and the arp request comes in on eth0 to be fundamentally broken.
Some people do not agree. From this aspect, I'd say my take is that IPv6
uses the strong hos model.
>

I agree, and I think it is probably because I first got exposed to
multi-address issues on routers, and they followed the strong "host" model.
Addresses are assigned to interfaces, and if the interface goes down or is
taken down, the associated addresses become unavailable. I find that very
intuitive because the address state follows the interface state.

> However, most hosts will glady send out traffic sourced from eth0 IPv6
address via eth1, if that happens to be the best default route for the
node, indicating weak host model.
>
> With hosts implementing MIF, I hope most things will be strong host model
only.
>

OTOH, if an interface suffers a transient fault, should all of the sockets
that are using the interface's addresses be immediately destroyed? I'd say
no, but that then means the weak host model is the better and more robust
one.

Actually, this has reminded me of probably what I'd prefer on hosts. Weak
host model by default, meaning addresses and associated sockets survive
transient link faults, strong host model if interfaces are administratively
taken down, so addresses and associated sockets disappear when intended by
an operator or process.

I think this starts to uncover two different behaviours behind the strong
and weak host models:

- is an address still available for a host to use/listen to if the
interface the address is associated with goes down and/or is taken down
administratively?

- if the address is still available when the associated interface is down,
should packets using that address be routed out other interfaces, or should
they be dropped.

Regards,
Mark.

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