IETF Logo Mail Archive

Re: [mif] MIF API - Access Network Selection

Ted Lemon <Ted.Lemon@nominum.com> Wed, 01 August 2012 22:02 UTC

Return-Path: <Ted.Lemon@nominum.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 B281611E836D for <mif@ietfa.amsl.com>; Wed, 1 Aug 2012 15:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.553
X-Spam-Level:
X-Spam-Status: No, score=-106.553 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 bC44-g6z9hF4 for <mif@ietfa.amsl.com>; Wed, 1 Aug 2012 15:02:37 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id BA15F11E8195 for <mif@ietf.org>; Wed, 1 Aug 2012 15:02:36 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUBmnfD/KwFv5XQ8ZHKB/GFV6nCrXasBj@postini.com; Wed, 01 Aug 2012 15:02:36 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CA0911B830D for <mif@ietf.org>; Wed, 1 Aug 2012 15:02:35 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id BE58119005D; Wed, 1 Aug 2012 15:02:35 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Wed, 1 Aug 2012 15:02:35 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<sarikaya@ieee.org>" <sarikaya@ieee.org>, Behcet Sarikaya <sarikaya2012@gmail.com>
Thread-Topic: MIF API - Access Network Selection
Thread-Index: AQHNcCpCx3vi/hqDfku3VfHWCfpMfZdF6s2AgAADtACAAAk5gA==
Date: Wed, 01 Aug 2012 22:02:34 +0000
Message-ID: <037E6537-B7EF-449A-8581-864C798171A2@nominum.com>
References: <CAC8QAccpQTO2u2z00r-s_hc_bA+usFKnHN-zfMOMvnbnc3kE6g@mail.gmail.com> <086FCD42-FC16-4F24-8032-7F763731BB2B@nominum.com> <CAC8QAcdG2cZiWPmrELP5Jm4DYXME2ZxC1cS_LA8txKubsMayeg@mail.gmail.com>
In-Reply-To: <CAC8QAcdG2cZiWPmrELP5Jm4DYXME2ZxC1cS_LA8txKubsMayeg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_037E6537B7EF449A8581864C798171A2nominumcom_"
MIME-Version: 1.0
Cc: "<mif@ietf.org>" <mif@ietf.org>
Subject: Re: [mif] MIF API - Access Network Selection
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 01 Aug 2012 22:02:37 -0000

On Aug 1, 2012, at 2:29 PM, Behcet Sarikaya wrote:
Where is connection manager specified? a Mif document?

I think that the MIF API sets a baseline for what the connection manager has to be able to do.   I think that a single connection manager spec from the MIF working group would be presumptuous, because the precise functioning of the connection manager is really something that's core to the business of a lot of customers of the MIF API.   So as long as the connection manager implementation supports the functionality required by the MIF API, I don't think we should try to go any further than that.

v2.23.0 | Report a Bug | By Email