IETF Logo Mail Archive

Re: [mif] MIF API - Access Network Selection

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 01 August 2012 21:29 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8223D21F8A24 for <mif@ietfa.amsl.com>; Wed, 1 Aug 2012 14:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.554
X-Spam-Level:
X-Spam-Status: No, score=-3.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RaFSlo00A-WC for <mif@ietfa.amsl.com>; Wed, 1 Aug 2012 14:29:36 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id CDBEE21F8A1F for <mif@ietf.org>; Wed, 1 Aug 2012 14:29:35 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so8464296ggn.31 for <mif@ietf.org>; Wed, 01 Aug 2012 14:29:35 -0700 (PDT)
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=tihH78aKEUcqn2rBhjD9JKr2hqJMVxHwZBh6eO9Qq8Y=; b=h8o17O9o52GV9fC9XreTBwMFXIK+/k9Wm3677aHg64Oj8UHAYH0xQkn0C7vetQzNbZ M6Hd2SbRr0SeVsiCslKAnKV5LNUjjFANunAS8u5X5dJbwrsuygu5slKeRkOCVtlosKCx ILTZgN96yVH4qHyXLKjqZPr/X8q/4RxOi8KnvIIaCyT5f3RroY+v2UGK/3TaQ+xl66tz +F+9eDVu+PcFD3k2YUmzb0X/Z6fN0rOc0J/n8aOdrdOunPQ40cGw7OqdZe0RK1U/vUzA IsD3hyozEcd32ohZOEW+btkz24Y8mhNFey8vL/2+f+QHSQi3CpytmbcsuXKDaOMJoi8K /46w==
MIME-Version: 1.0
Received: by 10.50.17.230 with SMTP id r6mr6723715igd.63.1343856574738; Wed, 01 Aug 2012 14:29:34 -0700 (PDT)
Received: by 10.231.207.167 with HTTP; Wed, 1 Aug 2012 14:29:34 -0700 (PDT)
In-Reply-To: <086FCD42-FC16-4F24-8032-7F763731BB2B@nominum.com>
References: <CAC8QAccpQTO2u2z00r-s_hc_bA+usFKnHN-zfMOMvnbnc3kE6g@mail.gmail.com> <086FCD42-FC16-4F24-8032-7F763731BB2B@nominum.com>
Date: Wed, 01 Aug 2012 16:29:34 -0500
Message-ID: <CAC8QAcdG2cZiWPmrELP5Jm4DYXME2ZxC1cS_LA8txKubsMayeg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: mif@ietf.org
Subject: Re: [mif] MIF API - Access Network Selection
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 01 Aug 2012 21:29:36 -0000

Hi Ted,

On Wed, Aug 1, 2012 at 4:16 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> On Aug 1, 2012, at 2:11 PM, Behcet Sarikaya wrote:
>
> Is selecting one network versus the other part of this API work?
>
>
> By "network" do you mean something like two access points, or do you mean
> two interfaces?

Yes, it could be multiple APs or Base Stations.

>The expectation is that we will attempt to use any network
> we are actually connected to.   The connection manager is responsible for
> choosing which access point to connect to,

Where is connection manager specified? a Mif document?

> and until that decision is made,
> we aren't connected to a network on that interface from the perspective of
> the MIF API.   Similarly for a wireline connection in a market where more
> than one provider shares the wireline.
>

Regards,

Behcet

v2.23.0 | Report a Bug | By Email