My question was if access network selection is part of the MIF API. The answer is no. It is the job of so-called connection manager, a functionality usually provided by the operating system, i.e. iOS/Android, etc. It also means the answer is it is implementation issue.
Yes? Behcet On Thu, Aug 2, 2012 at 4:01 AM, <[email protected]> wrote: > Hi, > > > > Sorry for jumping into the discussion but, actually, this is a very > interesting point. > > > > Couple of IETF ago, we discussed the interest for a “connection manager” > item in MIF. Actually, Ted gives a good summary of the consensus in MIF. > 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 . > > > > Pierrick > > > > De : [email protected] [mailto:[email protected]] De la part de Ted > Lemon > Envoyé : jeudi 2 août 2012 00:03 > À : <[email protected]>; Behcet Sarikaya > Cc : <[email protected]> > Objet : Re: [mif] MIF API - Access Network Selection > > > > 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. > > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete > altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages > that have been modified, changed or falsified. > Thank you. _______________________________________________ mif mailing list [email protected] https://www.ietf.org/mailman/listinfo/mif
