draft-ietf-mif-current-practices-04.txt   draft-ietf-mif-current-practices-05.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: April 24, 2011 France Telecom - Orange Expires: April 28, 2011 France Telecom - Orange
October 21, 2010 October 25, 2010
Current Practices for Multiple Interface Hosts Current Practices for Multiple Interface Hosts
draft-ietf-mif-current-practices-04 draft-ietf-mif-current-practices-05
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 April 24, 2011. This Internet-Draft will expire on April 28, 2011.
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 35 skipping to change at page 2, line 35
3.1.8. Access selection . . . . . . . . . . . . . . . . . . . 12 3.1.8. Access selection . . . . . . . . . . . . . . . . . . . 12
3.2. Desktop Operating Systems . . . . . . . . . . . . . . . . 14 3.2. Desktop Operating Systems . . . . . . . . . . . . . . . . 14
3.2.1. Microsoft Windows . . . . . . . . . . . . . . . . . . 14 3.2.1. Microsoft Windows . . . . . . . . . . . . . . . . . . 14
3.2.1.1. Routing . . . . . . . . . . . . . . . . . . . . . 14 3.2.1.1. Routing . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . 14
3.2.2. Linux and BSD-based Operating Systems . . . . . . . . 16 3.2.2. Linux and BSD-based Operating Systems . . . . . . . . 16
3.2.3. Apple Mac OS X . . . . . . . . . . . . . . . . . . . . 17 3.2.3. Apple Mac OS X . . . . . . . . . . . . . . . . . . . . 17
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 18
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19
9.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 19
9.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
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.
skipping to change at page 12, line 40 skipping to change at page 12, line 40
connection sharing. connection sharing.
3.1.8. Access selection 3.1.8. Access selection
This section describes the behavior of connection managers in This section describes the behavior of connection managers in
presence of multiple points of attachment for a same interface. The presence of multiple points of attachment for a same interface. The
section focuses on WLAN interface, it is described how does the section focuses on WLAN interface, it is described how does the
connection manager deal with the list of preferred SSID and how does connection manager deal with the list of preferred SSID and how does
it select the SSID for attachment. Current implementation of it select the SSID for attachment. Current implementation of
connection managers are considered for the following handsets: LG connection managers are considered for the following handsets: LG
Pathfinder, HTC Android, RIM BlackBerry , iPhone (3G and 3GS). Pathfinder, Android/HTC magic, RIM BlackBerry , iPhone (3G and 3GS).
When the terminal is under coverage of different WLAN networks with When the terminal is under coverage of different WLAN networks with
different SSIDs: different SSIDs:
connection managers, excepted for the RIM Blackberry, construct connection managers, excepted for the RIM Blackberry, construct
the list of preferred SSID giving priority to the last SSID on the list of preferred SSID giving priority to the last SSID on
which they have managed to attach. The user is not allowed to which they have managed to attach. The user is not allowed to
define its preferred access. So, if the terminal discovers and define its preferred access. So, if the terminal discovers and
manages to attach to SSID1, SSID1 becomes the preferred access for manages to attach to SSID1, SSID1 becomes the preferred access for
future attachment. If the terminal moves out of SSID1 coverage future attachment. If the terminal moves out of SSID1 coverage
skipping to change at page 15, line 20 skipping to change at page 15, line 20
3. Suffix to control Dynamic DNS Updates: determine which DNS server 3. Suffix to control Dynamic DNS Updates: determine which DNS server
will receive a dynamic update for a name with a certain suffix. will receive a dynamic update for a name with a certain suffix.
4. Suffix in the Name Resolution Policy Table [NRPT] to aid in 4. Suffix in the Name Resolution Policy Table [NRPT] to aid in
identifying a Namespace that requires special handling (feature identifying a Namespace that requires special handling (feature
available only after Windows 7 and its server counterpart, available only after Windows 7 and its server counterpart,
Windows Server 2008 R2). Windows Server 2008 R2).
However, this section focuses on the interface-specific suffix list However, this section focuses on the interface-specific suffix list
since it is the only suffix usage in the scope of MIF. since it is the only suffix usage in the scope of this document.
DNS configuration information can be host-wide or interface specific. DNS configuration information can be host-wide or interface specific.
Host-wide DNS configuration is input via static configuration or, in Host-wide DNS configuration is input via static configuration or, in
sites that use Active Directory, Microsoft's Group Policy. Interface sites that use Active Directory, Microsoft's Group Policy. Interface
specific DNS configuration can be input via static configuration or specific DNS configuration can be input via static configuration or
via DHCP. via DHCP.
The host-wide configuration consists of a primary DNS suffix to be The host-wide configuration consists of a primary DNS suffix to be
used for the local host, as well as a list of suffix that can be used for the local host, as well as a list of suffix that can be
appended to names being queried. Before Windows Vista and Windows appended to names being queried. Before Windows Vista and Windows
skipping to change at page 17, line 15 skipping to change at page 17, line 15
The most configurable DHCP clients can be set to define a primary The most configurable DHCP clients can be set to define a primary
interface to use only that interface for the global configuration interface to use only that interface for the global configuration
data. However, this is limited, since a mobile host might not always data. However, this is limited, since a mobile host might not always
have the same set of interfaces available. Connection managers may have the same set of interfaces available. Connection managers may
help in this situation. help in this situation.
Some distributions also have a connection manager. However, most Some distributions also have a connection manager. However, most
connection managers serve as a GUI to the DHCP client, therefore not connection managers serve as a GUI to the DHCP client, therefore not
changing the functionality described above. changing the functionality described above.
Linux implements [RFC3484] for source address selection in IPv6.
However, the address sorting rules from [RFC3484] are not always
adequate. For this reason, Linux allows the system administrator to
dynamically change the sorting. This can be achieved with the /etc/
gai.conf file.
For incoming packets, Linux will check if the destination address
matches one of the addresses assigned to its interfaces. By default,
Linux implements the weak host model [RFC1122] on both IPv4 and IPv6.
However, Linux can also be configured to support the strong host
model.
3.2.3. Apple Mac OS X 3.2.3. Apple Mac OS X
This section is based on testing Mac OS X (version 10.5.6). This section is based on testing Mac OS X (version 10.5.6).
When using multiple interfaces on Mac OS X, global configuration data When using multiple interfaces on Mac OS X, global configuration data
such as default routes and the DNS server list are taken from the such as default routes and the DNS server list are taken from the
DHCP data received on the primary interface. Therefore, the order in DHCP data received on the primary interface. Therefore, the order in
which the interfaces receive their configuration data is not which the interfaces receive their configuration data is not
relevant. For example, if the primary interface receives its relevant. For example, if the primary interface receives its
configuration data first, then the second interface receives its configuration data first, then the second interface receives its
skipping to change at page 18, line 5 skipping to change at page 18, line 15
6. Security Considerations 6. Security Considerations
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. Contributors
The following changes were made between versions -00 and -02:
o Added information on usage of suffix with Windows.
o new section describing Qualcomm AMSS/Brew Multi-interface handling
o Considerations on access selection for some current connection
managers.
o Added information on multiple-interface scenarios with Google
Android.
o Clarifications on Arena connection manager
o Clarifications on multiple interface handling with RIM blackberry.
o Added new 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
o Hua Chen, Leadcoretech, Ltd. o Hua Chen, Leadcoretech, Ltd.
o Yan Zhang, Leadcoretech Ltd. o Yan Zhang, Leadcoretech Ltd.
skipping to change at page 19, line 4 skipping to change at page 18, line 41
o Shyam Seshadri, Microsoft Corporation o Shyam Seshadri, Microsoft Corporation
o Dave Thaler, Microsoft Corporation o Dave Thaler, Microsoft Corporation
o Kevin Chin, Microsoft Corporation o Kevin Chin, Microsoft Corporation
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. o Giyeong Son, RIM.
9. References 8. References
8.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-07 (work in Statement", draft-ietf-mif-problem-statement-07 (work in
progress), August 2010. progress), August 2010.
9.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>.
[BLACKBERRY] [BLACKBERRY]
Research In Motion Limited, "BlackBerry Java Development Research In Motion Limited, "BlackBerry Java Development
Environment - Fundamentals Guide: Wireless gateways", Environment - Fundamentals Guide: Wireless gateways",
2009, <http://na.blackberry.com/eng/deliverables/5827/ 2009, <http://na.blackberry.com/eng/deliverables/5827/
Wireless_gateways_447132_11.jsp>. Wireless_gateways_447132_11.jsp>.
 End of changes. 11 change blocks. 
37 lines changed or deleted 28 lines changed or added

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