Re: [mif-arch-dt] sections 4.3 and 4.4

"Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com> Mon, 23 September 2013 14:17 UTC

Return-Path: <JuanCarlos.Zuniga@InterDigital.com>
X-Original-To: mif-arch-dt@ietfa.amsl.com
Delivered-To: mif-arch-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E45F21F9AD5 for <mif-arch-dt@ietfa.amsl.com>; Mon, 23 Sep 2013 07:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level:
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001]
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 mtlE1NnNsaIa for <mif-arch-dt@ietfa.amsl.com>; Mon, 23 Sep 2013 07:16:52 -0700 (PDT)
Received: from smtp-out1.interdigital.com (smtp-out1.interdigital.com [64.208.228.135]) by ietfa.amsl.com (Postfix) with ESMTP id 5F36721F9E98 for <mif-arch-dt@ietf.org>; Mon, 23 Sep 2013 07:16:52 -0700 (PDT)
Received: from SAM.InterDigital.com ([10.30.2.11]) by smtp-out1.interdigital.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 23 Sep 2013 10:16:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CEB867.8612F7F6"
Date: Mon, 23 Sep 2013 10:16:39 -0400
Message-ID: <D60519DB022FFA48974A25955FFEC08C054A4869@SAM.InterDigital.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mif-arch-dt] sections 4.3 and 4.4
Thread-Index: Ac6kinvcJ6sWQAGbQ7qFjnsMydg1KAGYwBQgA156JJA=
References: <Prayer.1.3.5.1308010729000.16712@hermes-2.csi.cam.ac.uk> <COL125-W16BB859A16CE25C980383AB1340@phx.gbl>
From: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>
To: mif-arch-dt@ietf.org
X-OriginalArrivalTime: 23 Sep 2013 14:16:41.0286 (UTC) FILETIME=[86318E60:01CEB867]
Cc: pierrick.seite@orange.com
Subject: Re: [mif-arch-dt] sections 4.3 and 4.4
X-BeenThere: mif-arch-dt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIF Architecture Design Team mailing list <mif-arch-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif-arch-dt>, <mailto:mif-arch-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif-arch-dt>
List-Post: <mailto:mif-arch-dt@ietf.org>
List-Help: <mailto:mif-arch-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif-arch-dt>, <mailto:mif-arch-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2013 14:17:00 -0000

Hi Dmtry,

 

This is text for 4.4:

 

4.4.Relationship to interface management and connection managers

 

Current devices such as mobile handsets make use of proprietary
mechanisms and custom applications to manage connectivity with multiple
interfaces and multiple PVDs. These mechanisms or applications are
commonly known as connection managers [RFC 6419]. 

 

Connection managers sometimes rely on policy servers to allow the
PVD-aware node making the PVD selection. They can also make use of
routing guidance from the network (e.g. 3GPP ANDSF [REF ANDSF]).
Although connection managers solve some connectivity problems, they
seldom address the PVD selection in a comprehensive manner. Moreover,
even with proprietary solutions, it is very challenging to present a
coherent behaviour to the end user of the device, as different platforms
present different behaviours even when connected to the same network,
with the same type of interface, and for the same purpose. 

 

JC