Re: [mif] Hybrid Access Problem

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 11 November 2014 23:32 UTC

Return-Path: <sarikaya2012@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 1098D1A6FE6 for <mif@ietfa.amsl.com>; Tue, 11 Nov 2014 15:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 c2TkpLrIAki0 for <mif@ietfa.amsl.com>; Tue, 11 Nov 2014 15:32:15 -0800 (PST)
Received: from mail-yh0-x22e.google.com (mail-yh0-x22e.google.com [IPv6:2607:f8b0:4002:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 450F71A6FE1 for <mif@ietf.org>; Tue, 11 Nov 2014 15:32:15 -0800 (PST)
Received: by mail-yh0-f46.google.com with SMTP id t59so463424yho.5 for <mif@ietf.org>; Tue, 11 Nov 2014 15:32:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=0y/tc2DBWGgmWEvJM1vSLA1uytLS1iubQ0/uxxxNTsM=; b=QPcuZ/LgqVqmfTCjrOLlwtQV8FVFRLyXXAQyOn486pVdKkyK3l5BrwI7B1wGNAUtoz 5wPD/xVdrzsFPI5I9u1wHc5MCBBeGpfsPBwXVvrcu6cw5UOM4ydn4bwjDQeRsSXcr+oO WtbqABjJQXPES98eEnO9m6tAygCAVdISdJgNJsyR5BMMCBf130lelW9IyMLgZ2pQbA9a SPhEvtauuQC67u2c81fwQroOA6yQYKHGh2omzUE8fBZjllWXCNYk5ux94Sg0aHFLg5Zl ZiNdi9/Vk3mM/hBCgDUHM0NFnHZD4PQ6WALMHT4Yny+ZCKjthV1ASk4P5PdTwBTKHelw qUjQ==
MIME-Version: 1.0
X-Received: by 10.236.60.195 with SMTP id u43mr267627yhc.142.1415748734474; Tue, 11 Nov 2014 15:32:14 -0800 (PST)
Received: by 10.170.71.198 with HTTP; Tue, 11 Nov 2014 15:32:14 -0800 (PST)
In-Reply-To: <8C1BB9C8-4F4E-4316-8ADA-8F8633EC40E9@gmail.com>
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>
Date: Tue, 11 Nov 2014 17:32:14 -0600
Message-ID: <CAC8QAcfCSHiSPaeihb7iqhYsPBR2sgY+bT01T_Ah2VzuESb7xQ@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Margaret Wasserman <margaretw42@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/8ERGu9LnQrjB7g-GChGf_np6tJs
Cc: "mif@ietf.org List" <mif@ietf.org>
Subject: Re: [mif] Hybrid Access Problem
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
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 23:32:17 -0000

On Mon, Nov 10, 2014 at 10:08 PM, Margaret Wasserman
<margaretw42@gmail.com> wrote:
>
>
> 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.
>

This case is not valid because both attached networks belong to the
same operator. Also the hosts do not get separate addresses from the
attached networks, I think.

> (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.
>

Yes, I think this is the case.

> (1.2.2) The gateway has only one IP address that is somehow shared across
> the two links.
>
> (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.
>
> 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?
>
> 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?
>

This could be the case.

I want to also say here that CPE here is not a mobile router.
There might be mobile routers that are connected to two networks but
not in this case, I think.

Regards,

Behcet
> 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
>