Re: [mif] MIF API - Access Network Selection

["Zuniga, Juan Carlos" <[e-mail]>]

Ted, Pierrick,

 

I think specifying connection manager requirements is a good idea and
very much in line with the laundry list we were discussing during my
presentation. 

 

>From my side, I also would like to see a connection manager interface
that allows providing a common behavior from different devices operating
in the same managed network.

 

As Ted mentions, we can start by defining the list of API messages to
have more concrete examples and then have a more concrete discussion.

 

Regards,

 

Juan Carlos

 

From: [e-mail] [mailto:[e-mail]] On Behalf Of
Ted Lemon
Sent: Thursday, August 02, 2012 12:22 PM
To: List List
Subject: Re: [mif] MIF API - Access Network Selection

 

On Aug 2, 2012, at 2:01 AM, <[e-mail]>
<[e-mail]> wrote:

	Full specification of a Connection manager is out of the IETF
scope,  but it is expected from the MIF API to provide information and
functionalities that a connection manager may need. On the other hand,
I think that ongoing work in MIF ( implementation guideline or
specification of the high-level API) may provide guidance on how a
connection manager should use the MIF API .

 

In fact, the current work on the MIF API is assuming that the connection
manager may use, and indeed _require_ features of the operating system
which are not exposed in the MIF API.   The reason for this division is
that it's expected that the vendor of a device or operating system will
almost certainly have a single connection manager that controls the
connections of the machine, and that there is no way to anticipate the
context in which this connection manager will operate.   So its
deliverables are fairly clear, but its requirements are clear as mud.

 

If this is not in fact the consensus of the working group, then people
who know more about how connection managers work (if there are any who
can participate) should be proposing additional API messages.

 

For my part, I think that we have a pretty clear and manageable job to
do if we just solve the problem of providing the minimal functionality
that a high-level API or smart application would need.