Happy Eyeballs Extension for Multiple Interfaces
draft-ietf-mif-happy-eyeballs-extension-11
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2016-11-27
(latest revision 2016-11-13)
|
|
Replaces |
|
draft-chen-mif-happy-eyeballs-extension
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
Revised I-D Needed - Issue raised by AD, Other - see Comment Log
|
|
Document shepherd |
|
DENG Hui
|
|
Shepherd write-up |
|
Show
(last changed 2016-02-22)
|
| IESG |
IESG state |
|
AD Evaluation
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Terry Manderson
|
|
Send notices to |
|
"DENG Hui" <denghui02@hotmail.com>
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
None
|
Internet Engineering Task Force G. Chen
Internet-Draft China Mobile
Intended status: Informational C. Williams
Expires: May 17, 2017 Consultant
D. Wing
A. Yourtchenko
Cisco Systems, Inc.
November 13, 2016
Happy Eyeballs Extension for Multiple Interfaces
draft-ietf-mif-happy-eyeballs-extension-11
Abstract
This memo proposes extensions to the Happy Eyeball's algorithm
requirements defined in RFC6555 for use with the multiple
provisioning domain architecture. The Happy Eyeballs in MIF would
make the selection process smoother by using connectivity tests over
pre-filtered interfaces according to defined policy. This would
choose the best interface with an automatic fallback mechanism.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 17, 2017.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Chen, et al. Expires May 17, 2017 [Page 1]
Internet-Draft happy-eyeballs-mif November 2016
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. WiFi is broken . . . . . . . . . . . . . . . . . . . . . 3
3.2. Policy Conflict . . . . . . . . . . . . . . . . . . . . . 4
4. Happiness Parameters . . . . . . . . . . . . . . . . . . . . 4
4.1. Hard Set . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. Operator Policy . . . . . . . . . . . . . . . . . . . 5
4.1.2. User Preference . . . . . . . . . . . . . . . . . . . 5
4.2. Soft Set . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Provisioning Domain Identity . . . . . . . . . . . . 6
4.2.2. DNS Selection . . . . . . . . . . . . . . . . . . . . 6
4.2.3. Next Hop . . . . . . . . . . . . . . . . . . . . . . 6
4.2.4. Source Address Selection . . . . . . . . . . . . . . 6
4.2.5. Common Practice . . . . . . . . . . . . . . . . . . . 6
5. HE-MIF Process Requirements . . . . . . . . . . . . . . . . . 7
5.1. First Step, Filter . . . . . . . . . . . . . . . . . . . 7
5.2. Second Step, Sort . . . . . . . . . . . . . . . . . . . . 8
5.2.1. Interface Validation . . . . . . . . . . . . . . . . 8
5.2.2. Name Resolution . . . . . . . . . . . . . . . . . . . 8
5.2.3. Connection Establishment . . . . . . . . . . . . . . 8
6. Implementation Framework . . . . . . . . . . . . . . . . . . 9
7. Additional Considerations . . . . . . . . . . . . . . . . . . 9
7.1. Usage Scope . . . . . . . . . . . . . . . . . . . . . . . 9
7.2. Fallback Timeout . . . . . . . . . . . . . . . . . . . . 9
7.3. DNS Selections . . . . . . . . . . . . . . . . . . . . . 10
7.4. Flow Continuity . . . . . . . . . . . . . . . . . . . . . 11
7.5. Interworking with Happy Eyeball . . . . . . . . . . . . . 11
7.6. Multipath Applicability . . . . . . . . . . . . . . . . . 11
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
Show full document text