draft-ietf-mif-current-practices-11.txt   draft-ietf-mif-current-practices-12.txt 
Internet Engineering Task Force M. Wasserman Internet Engineering Task Force M. Wasserman
Internet-Draft Painless Security, LLC Internet-Draft Painless Security, LLC
Intended status: Informational P. Seite Intended status: Informational P. Seite
Expires: October 29, 2011 France Telecom - Orange Expires: January 29, 2012 France Telecom - Orange
April 27, 2011 July 28, 2011
Current Practices for Multiple Interface Hosts Current Practices for Multiple Interface Hosts
draft-ietf-mif-current-practices-11 draft-ietf-mif-current-practices-12
Abstract Abstract
An increasing number of hosts are operating in multiple-interface An increasing number of hosts are operating in multiple-interface
environments. This document summarizes current practices in this environments. This document summarizes current practices in this
area, and describes in detail how some common operating systems cope area, and describes in detail how some common operating systems cope
with challenges ensue from this context. with challenges ensue from this context.
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 October 29, 2011. This Internet-Draft will expire on January 29, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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.1. DNS Resolution Issues . . . . . . . . . . . . . . . . 5 2.3.1. DNS Resolution Issues . . . . . . . . . . . . . . . . 5
2.3.2. First hop selection . . . . . . . . . . . . . . . . . 5 2.3.2. First hop selection . . . . . . . . . . . . . . . . . 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 and Windows Phone 7 . . . . . 9 3.1.2. Microsoft Windows Mobile and Windows Phone 7 . . . . . 9
3.1.3. RIM BlackBerry . . . . . . . . . . . . . . . . . . . . 10 3.1.3. RIM BlackBerry . . . . . . . . . . . . . . . . . . . . 10
3.1.4. Google Android . . . . . . . . . . . . . . . . . . . . 11 3.1.4. Google Android . . . . . . . . . . . . . . . . . . . . 11
3.1.5. Qualcomm Brew . . . . . . . . . . . . . . . . . . . . 12 3.1.5. Qualcomm Brew . . . . . . . . . . . . . . . . . . . . 12
3.1.6. Leadcore Tech. Arena . . . . . . . . . . . . . . . . . 13 3.1.6. Leadcore Tech. Arena . . . . . . . . . . . . . . . . . 14
3.2. Desktop Operating Systems . . . . . . . . . . . . . . . . 13 3.2. Desktop Operating Systems . . . . . . . . . . . . . . . . 14
3.2.1. Microsoft Windows . . . . . . . . . . . . . . . . . . 14 3.2.1. Microsoft Windows . . . . . . . . . . . . . . . . . . 14
3.2.1.1. First hop selection . . . . . . . . . . . . . . . 14 3.2.1.1. First hop selection . . . . . . . . . . . . . . . 14
3.2.1.2. Outbound and Inbound Addresses . . . . . . . . . . 14 3.2.1.2. Outbound and Inbound Addresses . . . . . . . . . . 14
3.2.1.3. DNS Configuration . . . . . . . . . . . . . . . . 14 3.2.1.3. DNS Configuration . . . . . . . . . . . . . . . . 15
3.2.2. Linux and BSD-based Operating Systems . . . . . . . . 15 3.2.2. Linux and BSD-based Operating Systems . . . . . . . . 16
3.2.2.1. First hop selection . . . . . . . . . . . . . . . 16 3.2.2.1. First hop selection . . . . . . . . . . . . . . . 16
3.2.2.2. Outbound and Inbound Addresses . . . . . . . . . . 16 3.2.2.2. Outbound and Inbound Addresses . . . . . . . . . . 17
3.2.2.3. DNS Configuration . . . . . . . . . . . . . . . . 17 3.2.2.3. DNS Configuration . . . . . . . . . . . . . . . . 17
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 20
8.2. Informative References . . . . . . . . . . . . . . . . . . 20 8.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
Multiple-interface hosts face several challenges not faced by single- Multiple-interface hosts face several challenges not faced by single-
interface hosts, some of which are described in the MIF problem interface hosts, some of which are described in the MIF problem
statement, [I-D.ietf-mif-problem-statement]. This document statement, [I-D.ietf-mif-problem-statement]. This document
summarizes how current implementations deal with the problems summarizes how current implementations deal with the problems
identified in the MIF problem statement. identified in the MIF problem statement.
Publicly-available information about the multiple-interface solutions Publicly-available information about the multiple-interface solutions
skipping to change at page 6, line 13 skipping to change at page 6, line 13
to update this default policy, and there is no standard way to do so. to update this default policy, and there is no standard way to do so.
In some cases, the routing decision (including which interface to In some cases, the routing decision (including which interface to
use) is made before source address selection is performed, and a use) is made before source address selection is performed, and a
source address is chosen from the outbound interface. In other source address is chosen from the outbound interface. In other
cases, source address selection is performed before, or independently cases, source address selection is performed before, or independently
from outbound interface selection. from outbound interface selection.
3. Current Practices in Some Operating Systems 3. Current Practices in Some Operating Systems
The following sections briefly describe the current multiple- The material presented in this section is derived from contributions
interface host implementations on some widely-used operating systems. from people familiar with the Operating Systems described, and those
Please refer to the References section for pointers to original people are listed in Section 7. The authors and the IETF take no
documentation on most of these systems, including further details. position about the Operating Systems described, and understand that
other Operating Systems also exist. Furthermore, it should be
understood that Section 3 describes particular behaviors that were
believed to be current at the time of documentation: earlier and
later versions of the Operating Systems described may exhibit
different behaviors. Please refer to the References section for
pointers to original documentation, including further details.
3.1. Mobile Handset Operating Systems 3.1. Mobile Handset Operating Systems
Cellular devices typically run a variety of applications in parallel, Cellular devices typically run a variety of applications in parallel,
each with different requirements for IP connectivity. A typical each with different requirements for IP connectivity. A typical
scenario is shown in figure 1, where a cellular device is utilizing scenario is shown in figure 1, where a cellular device is utilizing
WLAN access for web browsing and GPRS access for transferring WLAN access for web browsing and GPRS access for transferring
multimedia messages (MMS). Another typical scenario would be a real- multimedia messages (MMS). Another typical scenario would be a real-
time VoIP session over one network interface in parallel with best time VoIP session over one network interface in parallel with best
effort web browsing on another network interface. Yet another effort web browsing on another network interface. Yet another
skipping to change at page 19, line 47 skipping to change at page 20, line 16
o Giyeong Son, RIM. o Giyeong Son, RIM.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-mif-problem-statement] [I-D.ietf-mif-problem-statement]
Blanchet, M. and P. Seite, "Multiple Interfaces and Blanchet, M. and P. Seite, "Multiple Interfaces and
Provisioning Domains Problem Statement", Provisioning Domains Problem Statement",
draft-ietf-mif-problem-statement-13 (work in progress), draft-ietf-mif-problem-statement-15 (work in progress),
April 2011. May 2011.
8.2. Informative References 8.2. Informative References
[ANDROID] Google Inc., "Android developers: package android.net", [ANDROID] Google Inc., "Android developers: package android.net",
2009, <http://developer.android.com/reference/android/net/ 2009, <http://developer.android.com/reference/android/net/
ConnectivityManager.html>. ConnectivityManager.html>.
[ANDROID-RFC3484] [ANDROID-RFC3484]
Gunderson, S., "RFC 3484 support for Android", 2010, <http Gunderson, S., "RFC 3484 support for Android", 2010, <http
://gitorious.org/0xdroid/bionic/commit/ ://gitorious.org/0xdroid/bionic/commit/
 End of changes. 11 change blocks. 
20 lines changed or deleted 26 lines changed or added

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