IETF Logo Mail Archive

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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 23 June 2014 15:13 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 EDF821B2B0B for <v6ops@ietfa.amsl.com>; Mon, 23 Jun 2014 08:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 M3_uT43HWcrB for <v6ops@ietfa.amsl.com>; Mon, 23 Jun 2014 08:12:50 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E48981B2B19 for <v6ops@ietf.org>; Mon, 23 Jun 2014 08:12:21 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s5NFCJcV023753 for <v6ops@ietf.org>; Mon, 23 Jun 2014 17:12:19 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3EDF2203DC1 for <v6ops@ietf.org>; Mon, 23 Jun 2014 17:14:14 +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 3669B200B3B for <v6ops@ietf.org>; Mon, 23 Jun 2014 17:14:14 +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 s5NFC9a8025598 for <v6ops@ietf.org>; Mon, 23 Jun 2014 17:12:19 +0200
Message-ID: <53A843C9.1040002@gmail.com>
Date: Mon, 23 Jun 2014 17:12:09 +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: <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com> <5384937A.90409@foobar.org> <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> <20140531214908.10FEE1719BB4@rock.dv.isc.org> <m1WqrFK-0000BHC@stereo.hq.phicoh.net> <23125E9D-85A1-49EB-ACE6-DB5EAC67EE02@nominum.com> <CAKD1Yr0pvet1oOip-Y2Xi_h2mSZfW1R5HtfiAGbDEns0dY-d2A@mail.gmail.com> <2A4B72CD-EDF3-4D11-AC39-B65892F9173F@nominum.com> <CAKD1Yr2NH4Kca4EvhjN2XnDbt8F2eS56ipxu3npH9yOh1bmQaA@mail.gmail.com> <F12F173B-9FF2-4EF8-B11E-33AEDA24961F@nominum.com> <20140602013829.875B917236AC@rock.dv.isc.org>
In-Reply-To: <20140602013829.875B917236AC@rock.dv.isc.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/8Ni4NETuSICfS49x5t35EEoSRL4
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: Mon, 23 Jun 2014 15:13:01 -0000

Le 02/06/2014 03:38, Mark Andrews a écrit :
>
> In message <F12F173B-9FF2-4EF8-B11E-33AEDA24961F@nominum.com>, Ted Lemon writes
> :
>> On Jun 1, 2014, at 9:01 PM, Lorenzo Colitti <lorenzo@google.com> wrote:
>>> And this problem is specific to IPv6 because...?
>>
>> IPv4 never claimed to provide ubiquitous support for multihoming.   IPv6 kind
>>   of does.
>
> IPv6 adds multiple addresses on a interface.

Hmmm, I have recollections of discovering multiple IPv4 addresses per 
interface before there was an IPv6 stack.

Alex

    Multihoming support is
> transport family agnostic.
>
> Multihoming support is supposed to be done in IPv4 applications
> unless you have a very good reason to not support it or do you think
> SHOULD means it is a optional part of IPv4?
>
> RFC 1123
>
>     2.3  Applications on Multihomed hosts
>
>        When the remote host is multihomed, the name-to-address
>        translation will return a list of alternative IP addresses.  As
>        specified in Section 6.1.3.4, this list should be in order of
>        decreasing preference.  Application protocol implementations
>        SHOULD be prepared to try multiple addresses from the list until
>        success is obtained.  More specific requirements for SMTP are
>        given in Section 5.3.4.
>
>        When the local host is multihomed, a UDP-based request/response
>        application SHOULD send the response with an IP source address
>        that is the same as the specific destination address of the UDP
>        request datagram.  The "specific destination address" is defined
>        in the "IP Addressing" section of the companion RFC [INTRO:1].
>
>        Similarly, a server application that opens multiple TCP
>        connections to the same client SHOULD use the same local IP
>        address for all.
>
> All dual stack machines are multihomed.  HE is basically about fast
> failover when the destination addresses are unreachable.  This is not
> hard to do.  From memory BSD 4.2 supported non blocking connect
> which is all that is required from the IP stack to do fast failover.
>
> Mark
>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email