Subject: [mif] FW: New Version Notification for draft-seite-mif-cm-01.txt

From: "Zuniga, Juan Carlos" <[email-masked]>
Date: Wed, 6 Mar 2013 11:14:08 -0500

Hi all,

After our presentation on the Connection Management draft at IETF85 in Atlanta, we got an action item to update our draft to align the architecture with the MIF API one, to highlight the connection management problems, and to submit the 802.21 annex as a separate document.

We have updated our draft accordingly and have also submitted a new informational draft as requested:

http://tools.ietf.org/html/draft-seite-mif-cm-01 

http://tools.ietf.org/html/draft-zuniga-mif-802-21-overview-00 

Comments are welcome.

Juan-Carlos & Pierrick

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: Friday, February 22, 2013 9:37 AM
> To: [email-masked]
> Cc: Zuniga, Juan Carlos
> Subject: New Version Notification for draft-seite-mif-cm-01.txt
> 
> 
> A new version of I-D, draft-seite-mif-cm-01.txt
> has been successfully submitted by Pierrick Seite and posted to the
> IETF repository.
> 
> Filename:	 draft-seite-mif-cm
> Revision:	 01
> Title:		 MIF API for Connection Management
> Creation date:	 2013-02-19
> Group:		 Individual Submission
> Number of pages: 17
> URL:             http://www.ietf.org/internet-drafts/draft-seite-mif-cm-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-seite-mif-cm
> Htmlized:        http://tools.ietf.org/html/draft-seite-mif-cm-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-seite-mif-cm-01
> 
> Abstract:
>    There is currently a need to present a coherent connection
> management
>    behaviour for different terminal platforms (e.g. mobile phones, PCs,
>    tablets, etc.).  This document discusses how a connection manager
> can
>    use the MIF API to provide this coherent behaviour and enhance the
>    end user's experience when a terminal is able to connect to multiple
>    interfaces.  The goal of this document is not to define a connection
>    manager specification, but to focus on the interaction with the MIF
>    API and suggest relevant generic messages for the interface.
> 
>    This document is for discussion and its intention is to help
>    clarifying the utilization of the MIF API in a connection management
>    context and propose some relevant considerations.
> 
> 
> 
> 
> The IETF Secretariat