[mif-arch-dt] sections 4.3 and 4.4

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

Hi all,

 

As mentioned before, Pierrick and I would like to suggest some text for
sections 4.3 and 4.4.

 

Comments are welcome.

 

Best regards,

 

Juan Carlos & Pierrick

 

4.3.  Connectivity tests

 

Although some provisioning domains appear to be valid candidates for PVD
selection (e.g. good L2 quality, consistent connection parameters,
etc.), they may provide limited or no connectivity to the desired
network or the Internet. For example, some PVDs provide L3 connectivity
but require the node to authenticate through a web portal to get full
access to the Internet. If the PVD-aware node knows the PVD, it can
perform authentication operations; otherwise, the node may stay with a
limited network connectivity without full knowledge about this.  Hence,
once the node is attached to a PVD, it should check IP connectivity and
trigger PVD reselection if need be. Also, once the node is attached to a
new valid PVD, the end-to-end IP connectivity could be disrupted. A
mechanism is thus needed to check current connectivity and trigger PVD
reselection if necessary.

 

Usually, the node can perform these tests by trying to reach a dedicated
web server (e.g. connection managers may be able to address this problem
[RFC 6419]). A better solution would be to make the node aware of the
characteristics of the PVD in order to make the appropriate selection.
This could be realized leveraging some 3GPP and IEEE mechanisms, which
allow to expose some of PVD characteristics to the node (e.g. 3GPP
Access Network Discovery and Selection Function (ANDSF) [REF ANDSF],
IEEE 802.11u/ANQP [REF 802.11u]). 

 

 

 

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. 

 

 

 

From: [e-mail] [mailto:[e-mail]]
On Behalf Of Hui Deng
Sent: Thursday, August 29, 2013 3:36 AM
To: [e-mail]
Subject: [mif-arch-dt] Restart the teleconf

 

Hello all,
 
We plan to restart our regular biweek teleconf from the September 9th
(Monday) same time
will send out teleconf invitation next week (one week before the
teleconf)
 
Thanks a lot for your attendance.
Best regards,
 
-Hui