[rfc-dist] RFC 5113 on Network Discovery and Selection Problem
rfc-editor at rfc-editor.org
Fri Jan 25 16:36:04 PST 2008
A new Request for Comments is now available in online RFC libraries.
Title: Network Discovery and Selection Problem
Author: J. Arkko, B. Aboba,
J. Korhonen, Ed.,
Date: January 2008
Mailbox: jari.arkko at ericsson.com,
bernarda at microsoft.com,
jouni.korhonen at teliasonera.com, farooq.bari at att.com
I-D Tag: draft-ietf-eap-netsel-problem-09.txt
When multiple access networks are available, users may have
difficulty in selecting which network to connect to and how to
authenticate with that network. This document defines the network
discovery and selection problem, dividing it into multiple sub-
problems. Some constraints on potential solutions are outlined, and
the limitations of several solutions (including existing ones) are
discussed. This memo provides information for the Internet community.
This document is a product of the Extensible Authentication Protocol
Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist