Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
Ray Hunter <v6ops@globis.net> Wed, 29 October 2014 12:05 UTC
Return-Path: <v6ops@globis.net>
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 A7EF31A0078; Wed, 29 Oct 2014 05:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level:
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 RaBZD6tjAfig; Wed, 29 Oct 2014 05:05:47 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id D16471A0076; Wed, 29 Oct 2014 05:05:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 6B1E7871612; Wed, 29 Oct 2014 13:05:45 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYhcOzxypzPf; Wed, 29 Oct 2014 13:05:45 +0100 (CET)
Received: from Rays-iMac.local (092-111-140-211.static.chello.nl [92.111.140.211]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 3F00D871611; Wed, 29 Oct 2014 13:05:45 +0100 (CET)
Message-ID: <5450D7ED.9010806@globis.net>
Date: Wed, 29 Oct 2014 13:05:01 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
References: <20141020204033.GD236844@jupiter.n2.diac24.net> <20141022190653.GB868521@jupiter.n2.diac24.net> <DFE4317C-E4B6-44AB-AED4-2FBBBD2888DA@cisco.com> <B445E8FD-13EE-4014-8D1C-7C9D4A188D2D@cisco.com> <544FF3F2.3050206@gmail.com> <20141029062837.GH5186@eidolon> <B6D9E5BD-8903-4133-8947-BB8AEAD97AA4@cisco.com>
In-Reply-To: <B6D9E5BD-8903-4133-8947-BB8AEAD97AA4@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/dqCMBs1yzW05lIdJ6Kl9tdx8Oyc
Cc: Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>, David Lamparter <equinox@diac24.net>
Subject: Re: [homenet] dst/src routing drafts (for IETF-91 rtgwg)
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: Wed, 29 Oct 2014 12:05:48 -0000
Fred Baker (fred) wrote: > On Oct 28, 2014, at 11:28 PM, David Lamparter<equinox@diac24.net> wrote: > >> What I'm personally wondering most in this regard is: to what extent >> will larger networks deploy multiple prefixes to the hosts? > > Well, define “larger”. Any network that gets a PI prefix is unlikely to deploy multiple prefixes. The question is at what size network is makes sense to obtain an AS number and a PI prefix, and use BGP to talk with one’s upstream. I don't agree with this statement for the following reasons. Availability: There are many enterprises that have very numerous far-flung sales-office type locations which do not host any critical data or applications, but which could benefit from higher availability than that provided by a single ISP provider (some of which are currently served by a specialised box offering a Very Small Office Service running dual IPSec tunnels to a central site, which then performs the break out to the corporate intranet/Internet) Latency: There are many sites which could benefit from local Internet breakout to regional cloud services, where you don't want to suffer the latency associated with a back haul from an office in Australia to a regional hub in Hong Kong, or even East coast US to West coast US and back. You'd still also want some back up via the central breakout if the local breakout failed. Cost: There are cost savings to be made in many countries where private network services are still many orders of magnitude more expensive than plain old Internet. So Internet offload for non-mission-critical traffic can be very attractive. If you could achieve this via direct host-server connections using address selection rules or multipath TCP; rather than via PBR, GRE tunnels + NAT, that would be a lot simpler. > Wherever that boundary is, below that networks will use PA prefixes. The question then becomes: will they multi home? > > And I think the answer today is that we don’t know the answer. This I agree with. -- Regards, RayH
- Re: [homenet] dst/src routing drafts (for IETF-91… David Lamparter
- Re: [homenet] dst/src routing drafts (for IETF-91… Fred Baker (fred)
- Re: [homenet] dst/src routing drafts (for IETF-91… Ole Troan
- Re: [homenet] dst/src routing drafts (for IETF-91… Gert Doering
- Re: [homenet] dst/src routing drafts (for IETF-91… Tim Chown
- Re: [homenet] dst/src routing drafts (for IETF-91… Brian E Carpenter
- Re: [homenet] dst/src routing drafts (for IETF-91… David Lamparter
- Re: [homenet] dst/src routing drafts (for IETF-91… Fred Baker (fred)
- Re: [homenet] dst/src routing drafts (for IETF-91… Ray Hunter
- Re: [homenet] dst/src routing drafts (for IETF-91… Jim Gettys
- Re: [homenet] dst/src routing drafts (for IETF-91… Fred Baker (fred)
- Re: [homenet] dst/src routing drafts (for IETF-91… Michael Richardson
- Re: [homenet] dst/src routing drafts (for IETF-91… David Lamparter
- Re: [homenet] dst/src routing drafts (for IETF-91… Ole Troan
- Re: [homenet] dst/src routing drafts (for IETF-91… Ray Hunter