Re: [mif] Hybrid Access Problem

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 11 November 2014 06:26 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83F2F1A6F6F for <mif@ietfa.amsl.com>; Mon, 10 Nov 2014 22:26:42 -0800 (PST)
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 sBct-mBY1w6u for <mif@ietfa.amsl.com>; Mon, 10 Nov 2014 22:26:40 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B2921AD079 for <mif@ietf.org>; Mon, 10 Nov 2014 22:26:38 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id sAB6QaMu003082 for <mif@ietf.org>; Tue, 11 Nov 2014 07:26:36 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7D1F1200E8C for <mif@ietf.org>; Tue, 11 Nov 2014 07:26:52 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 7552C2007F2 for <mif@ietf.org>; Tue, 11 Nov 2014 07:26:52 +0100 (CET)
Received: from [127.0.0.1] ([132.166.84.23]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id sAB6QQ2b015603 for <mif@ietf.org>; Tue, 11 Nov 2014 07:26:35 +0100
Message-ID: <5461AC11.8070600@gmail.com>
Date: Tue, 11 Nov 2014 07:26:25 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: mif@ietf.org
References: <01FE63842C181246BBE4CF183BD159B449037ECA@nkgeml504-mbx.china.huawei.com> <D0765101.175805%sgundave@cisco.com> <005401cff509$3719eb30$a54dc190$@com> <D0869CBD.177FDF%sgundave@cisco.com> <1BC71728-94D7-48A3-B01D-0645DF8314F3@yegin.org> <8C1BB9C8-4F4E-4316-8ADA-8F8633EC40E9@gmail.com>
In-Reply-To: <8C1BB9C8-4F4E-4316-8ADA-8F8633EC40E9@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/Gl3LH07pqbiVWXl_RM_6A72DwoE
Subject: Re: [mif] Hybrid Access Problem
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Nov 2014 06:26:42 -0000

Le 11/11/2014 05:08, Margaret Wasserman a écrit :
>
>
> Let me see if I can start a technical discussion here...
>
> If you have an ISP today that has two different access networks
> available, such as one 3GPP network and one DSL network, how do(es) the
> gateway box(es) (connected to both networks) decide where it should send
> each packet it receives?  I think there are several possible cases here;
>
> (1) There is one gateway attached to both outbound networks.  This has
> two sub-cases:
>
> (1.1) Hosts behind the single gateway have separate addresses on the two
> attached networks.  In that case, the gateway is constrained to send
> packets over the outgoing network that uses the address prefix that
> matches the source address, or the packets will be thrown away by
> ingress filters on the other side.  So, the network choice is made by
> the hosts.
>
> (1.2) Hosts behind the gateway have only one address each.  This has two
> sub-cases:
>
> (1.2.1) The gateway has separate addresses on the two networks, and does
> some sort of translation from internal to external addresses in the
> prefix of the "right" outgoing link.

I agree with most points above.

>
> (1.2.2) The gateway has only one IP address that is somehow shared
> across the two links.

I think this is hardly possible, in the context of this CPE scenario. 
Even though operators recently are able to control both cellular and DSL 
offerings to end users they really have distinct networks for each. 
'Distinct' in that they are very remote one from another in terms of IP 
hops - makes it hard to have a common IP address shared across two 
egress links of CPE.

Unless of course we speak tunnels.

> (2)  There are two gateways, each attached to a single outbound network.
>   In this case, hosts will always have separate addresses for the two
> networks, and will need to make a decision about which outbound network
> to use.

This is a difficult case as well but here I think we talk one single CPE 
with multiple egress interfaces.

I think we need to clarify this.

> Cases 1.1 and 2 are essentially the same from a host standpoint, in that
> the host needs to make a network choice.  This is a problem we have
> discussed in MIF -- What sort of information does/should the host need
> to make that choice, and how is that information communicated to the host?

And, alternatively, how does the host make such choices and communicate 
them to the network.

And, alt2, how does the CPE make choices and communicate them to its 
upper gateways.

>
> Case 1.2.1 is a typical case of how NAT (or NPTv6) can be used for
> multi-homing.  The IETF generally prefers to avoid recommending
> solutions that use NAT, but do we have a better answer?

Yes tunnelling.

Alex

>
> Case 1.2.2 becomes a layer 2 problem and is probably outside the scope
> of the IETF.
>
> Are there cases that I am missing here?
>
> Margaret
>
>
>
>
>
>
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>