Subject: [mif] TR: I-D Action:draft-seite-mif-connection-manager-02.txt

From: <[email-masked]>
Date: Fri, 5 Nov 2010 15:10:29 +0100

Hi all,

We have posted a new version of "Connection Manager requirements"

https://datatracker.ietf.org/doc/draft-seite-mif-connection-manager/ 

The problem statement highlights complex issues (e.g. address/namespace overlap, interface selection) that could not be solved with simple modification of terminal configuration management; it may require sophisticated mechanisms such as connection manager. Specification of such an application is out of scope of the IETF, however, we think that the WG could document best current practices with regards to the use of information/services from a MIF API (as it will be specified by the WG). This is the goal of this document.

This version also describes multiple-interfaces management for some 3GPP use-cases (e.g. multiple PDN connectivity). 

Comments are more than welcome, thanks.

Regards,
Pierrick
> -----Message d'origine-----
> De : [email-masked] [mailto:[email-masked]]
> De la part de [email-masked]
> Envoyé : lundi 25 octobre 2010 23:30
> À : [email-masked]
> Objet : I-D Action:draft-seite-mif-connection-manager-02.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 	Title           : Connection Manager requirements
> 	Author(s)       : P. Seite, et al.
> 	Filename        : draft-seite-mif-connection-manager-02.txt
> 	Pages           : 20
> 	Date            : 2010-10-25
> 
> It is a common practice for multiple interface terminals to use a
> connection manager to perform provisioning domain selection and
> interface configuration.  The concept of connection managers for
> personal computers is well known, and similar logic is now common in
> mobile phones that have multiple radio interfaces [3GPP TS 23.402].
> The Problem Statement document highlights the lack of standardized
> behavior for terminals in regard to managing multiple interfaces and
> their respective properties.  To address this issue, this document
> proposes a set of functional requirements for a generic MIF
> Connection Manager.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-seite-mif-connection-manager-
> 02.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.