draft-ietf-mif-current-practices-01.txt   draft-ietf-mif-current-practices-02.txt 
Internet Engineering Task Force M. Wasserman, Ed. Internet Engineering Task Force M. Wasserman, Ed.
Internet-Draft Painless Security, LLC Internet-Draft Painless Security, LLC
Intended status: Informational P. Seite, Ed. Intended status: Informational P. Seite, Ed.
Expires: December 12, 2010 France Telecom - Orange Expires: December 30, 2010 France Telecom - Orange
June 10, 2010 June 28, 2010
Current Practices for Multiple Interface Hosts Current Practices for Multiple Interface Hosts
draft-ietf-mif-current-practices-01 draft-ietf-mif-current-practices-02
Abstract Abstract
An increasing number of hosts are operating in multiple-interface An increasing number of hosts are operating in multiple-interface
environments, where different network interfaces are providing environments, where different network interfaces are providing
unequal levels of service or connectivity. This document summarizes unequal levels of service or connectivity. This document summarizes
current practices in this area, and describes in detail how some current practices in this area, and describes in detail how some
common operating systems cope with these challenges. common operating systems cope with these challenges.
Status of this Memo Status of this Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 12, 2010. This Internet-Draft will expire on December 30, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 22 skipping to change at page 2, line 22
2.3. Stack-Level Solutions to Specific Problems . . . . . . . . 4 2.3. Stack-Level Solutions to Specific Problems . . . . . . . . 4
2.3.1. DNS Resolution Issues . . . . . . . . . . . . . . . . 5 2.3.1. DNS Resolution Issues . . . . . . . . . . . . . . . . 5
2.3.2. Routing . . . . . . . . . . . . . . . . . . . . . . . 5 2.3.2. Routing . . . . . . . . . . . . . . . . . . . . . . . 5
2.3.3. Address Selection Policy . . . . . . . . . . . . . . . 5 2.3.3. Address Selection Policy . . . . . . . . . . . . . . . 5
3. Current Practices in Some Operating Systems . . . . . . . . . 6 3. Current Practices in Some Operating Systems . . . . . . . . . 6
3.1. Mobile Handset Operating Systems . . . . . . . . . . . . . 6 3.1. Mobile Handset Operating Systems . . . . . . . . . . . . . 6
3.1.1. Nokia S60 3rd Edition, Feature Pack 2 . . . . . . . . 7 3.1.1. Nokia S60 3rd Edition, Feature Pack 2 . . . . . . . . 7
3.1.2. Microsoft Windows Mobile 2003 Second Edition . . . . . 8 3.1.2. Microsoft Windows Mobile 2003 Second Edition . . . . . 8
3.1.3. BlackBerry . . . . . . . . . . . . . . . . . . . . . . 9 3.1.3. BlackBerry . . . . . . . . . . . . . . . . . . . . . . 9
3.1.4. Google Android . . . . . . . . . . . . . . . . . . . . 9 3.1.4. Google Android . . . . . . . . . . . . . . . . . . . . 9
3.1.5. Qualcomm Brew . . . . . . . . . . . . . . . . . . . . 9 3.1.5. Qualcomm Brew . . . . . . . . . . . . . . . . . . . . 10
3.1.6. Arena Connection Manager . . . . . . . . . . . . . . . 11 3.1.6. Arena Connection Manager . . . . . . . . . . . . . . . 11
3.1.7. Access selection . . . . . . . . . . . . . . . . . . . 11 3.1.7. Access selection . . . . . . . . . . . . . . . . . . . 11
3.2. Desktop Operating Systems . . . . . . . . . . . . . . . . 13 3.2. Desktop Operating Systems . . . . . . . . . . . . . . . . 13
3.2.1. Microsoft Windows . . . . . . . . . . . . . . . . . . 13 3.2.1. Microsoft Windows . . . . . . . . . . . . . . . . . . 13
3.2.1.1. Routing . . . . . . . . . . . . . . . . . . . . . 13 3.2.1.1. Routing . . . . . . . . . . . . . . . . . . . . . 13
3.2.1.2. Outbound and Inbound Addresses . . . . . . . . . . 13 3.2.1.2. Outbound and Inbound Addresses . . . . . . . . . . 13
3.2.1.3. DNS Configuration . . . . . . . . . . . . . . . . 13 3.2.1.3. DNS Configuration . . . . . . . . . . . . . . . . 14
3.2.2. Linux and BSD-based Operating Systems . . . . . . . . 15 3.2.2. Linux and BSD-based Operating Systems . . . . . . . . 15
3.2.3. Apple Mac OS X . . . . . . . . . . . . . . . . . . . . 16 3.2.3. Apple Mac OS X . . . . . . . . . . . . . . . . . . . . 16
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
9.1. Normative References . . . . . . . . . . . . . . . . . . . 18 9.1. Normative References . . . . . . . . . . . . . . . . . . . 18
9.2. Informative References . . . . . . . . . . . . . . . . . . 18 9.2. Informative References . . . . . . . . . . . . . . . . . . 18
skipping to change at page 9, line 23 skipping to change at page 9, line 23
3.1.3. BlackBerry 3.1.3. BlackBerry
In BlackBerry devices [BLACKBERRY] Java applications can use one of In BlackBerry devices [BLACKBERRY] Java applications can use one of
two wireless gateways to proxy the connection to the Internet or to a two wireless gateways to proxy the connection to the Internet or to a
corporate network. The application can be designed to always use the corporate network. The application can be designed to always use the
default Internet gateway, or to use a more preferred enterprise default Internet gateway, or to use a more preferred enterprise
gateway when available. The intent is to hide connectivity issues gateway when available. The intent is to hide connectivity issues
from users. from users.
DISCUSS: How does the Blackberry decides when a WLAN interface, a A BlackBerry device [BLACKBERRY] can access different destinations
cellular interface or some other physical interface is used? using multiple access (wireless/wired) networks simultaneously. A
device can also access the same destination using multiple access
networks simultaneously. The device can select the network interface
to be used in various ways. For instance, it can use the default
network interface (or the default access network) or choose from
available active network interfaces based on cost, type-of-service
and/or use preference. Multiple network interfaces can be associated
with a single IP stack or multiple IP stacks.
3.1.4. Google Android 3.1.4. Google Android
The Android reference documentation describes the android.net package The Android reference documentation describes the android.net package
[ANDROID] and the ConnectivityManager class that applications can use [ANDROID] and the ConnectivityManager class that applications can use
to request a route to a specified destination address via a specified to request a route to a specified destination address via a specified
network interface (3GPP or Wifi). Applications also ask Connection network interface (3GPP or Wifi). Applications also ask Connection
Manager for permission to start using a network feature. The Manager for permission to start using a network feature. The
Connectivity Manager monitors changes in network connectivity and Connectivity Manager monitors changes in network connectivity and
attempts to failover to another network if connectivity to an active attempts to failover to another network if connectivity to an active
skipping to change at page 17, line 7 skipping to change at page 17, line 11
This document describes current operating system implementations and This document describes current operating system implementations and
how they handle the issues raised in the MIF problem statement. how they handle the issues raised in the MIF problem statement.
While it is possible that the currently implemented mechanisms While it is possible that the currently implemented mechanisms
described in this document may affect the security of the systems described in this document may affect the security of the systems
described, this document merely reports on current practice. It does described, this document merely reports on current practice. It does
not attempt to analyze the security properties (or any other not attempt to analyze the security properties (or any other
architectural properties) of the currently implemented mechanisms. architectural properties) of the currently implemented mechanisms.
7. Change Log 7. Change Log
The following changes were made between versions -00 and -01: The following changes were made between versions -00 and -02:
o Added information on usage of suffix with Windows. o Added information on usage of suffix with Windows.
o new section describing Qualcomm AMSS/Brew Multi-interface handling o new section describing Qualcomm AMSS/Brew Multi-interface handling
o Considerations on access selection for some current connection o Considerations on access selection for some current connection
managers. managers.
o Added information on multiple-interface scenarios with Google o Added information on multiple-interface scenarios with Google
Android. Android.
o Clarifications of Arena connection manager o Clarifications on Arena connection manager
o Clarifications on multiple interface handling with RIM blackberry.
o Added new contributors. o Added new contributors.
8. Contributors 8. Contributors
The following people contributed most of the per-Operating System The following people contributed most of the per-Operating System
information found in this document: information found in this document:
o Marc Blanchet, Viagenie o Marc Blanchet, Viagenie
skipping to change at page 18, line 7 skipping to change at page 18, line 14
o Teemu Savolainen, Nokia o Teemu Savolainen, Nokia
o Tao Sun, China Mobile o Tao Sun, China Mobile
o George Tsirtsis, Qualcomm. o George Tsirtsis, Qualcomm.
o David Freyermuth, France telecom. o David Freyermuth, France telecom.
o Aurelien Collet, Altran. o Aurelien Collet, Altran.
o Giyeong Son, RIM.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-mif-problem-statement] [I-D.ietf-mif-problem-statement]
Blanchet, M. and P. Seite, "Multiple Interfaces Problem Blanchet, M. and P. Seite, "Multiple Interfaces Problem
Statement", draft-ietf-mif-problem-statement-04 (work in Statement", draft-ietf-mif-problem-statement-04 (work in
progress), May 2010. progress), May 2010.
9.2. Informative References 9.2. Informative References
 End of changes. 9 change blocks. 
10 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/