Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network
RFC 7984
| Document | Type |
RFC - Proposed Standard
(September 2016; No errata)
Updates RFC 3263
|
|
|---|---|---|---|
| Last updated | 2016-09-29 | ||
| Replaces | draft-johansson-sip-dual-stack | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Adam Roach | ||
| Shepherd write-up | Show (last changed 2016-06-02) | ||
| IESG | IESG state | RFC 7984 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ben Campbell | ||
| Send notices to | "Adam Roach" <adam@nostrum.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) O. Johansson
Request for Comments: 7984 Edvina AB
Updates: 3263 G. Salgueiro
Category: Standards Track Cisco Systems
ISSN: 2070-1721 V. Gurbani
Bell Labs, Nokia Networks
D. Worley, Ed.
Ariadne
September 2016
Locating Session Initiation Protocol (SIP) Servers
in a Dual-Stack IP Network
Abstract
RFC 3263 defines how a Session Initiation Protocol (SIP)
implementation, given a SIP Uniform Resource Identifier (URI), should
locate the next-hop SIP server using Domain Name System (DNS)
procedures. As SIP networks increasingly transition from IPv4-only
to dual-stack, a quality user experience must be ensured for dual-
stack SIP implementations. This document updates the DNS procedures
described in RFC 3263 for dual-stack SIP implementations in
preparation for forthcoming specifications for applying "Happy
Eyeballs" principles to SIP.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7984.
Johansson, et al. Standards Track [Page 1]
RFC 7984 Locating SIP Servers in IPv4/IPv6 September 2016
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
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. DNS Procedures in a Dual-Stack Network . . . . . . . . . . . 4
3.1. Dual-Stack SIP UA DNS Record Lookup Procedure . . . . . . 4
3.2. Indicating Address Family Preference in DNS SRV Records . 5
4. Clarification of Interaction with RFC 6724 . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . 8
6.2. Informative References . . . . . . . . . . . . . . . . . 8
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
The Session Initiation Protocol (SIP) [RFC3261] and the additional
documents that extended it provide support for both IPv4 and IPv6.
However, this support does not fully extend to the highly hybridized
environments that are characteristic of the transitional migratory
phase from IPv4 to IPv6 networks. During this phase, many server and
client implementations run on dual-stack hosts. In such
environments, a dual-stack host will likely suffer greater connection
delay, and by extension an inferior user experience, than an
IPv4-only host. The need to remedy this diminished performance of
dual-stack hosts led to the development of the "Happy Eyeballs"
[RFC6555] algorithm, which has since been implemented in many
protocols and applications.
Johansson, et al. Standards Track [Page 2]
RFC 7984 Locating SIP Servers in IPv4/IPv6 September 2016
This document updates the DNS lookup procedures of RFC 3263 [RFC3263]
in preparation for the specification of the application of Happy
Eyeballs to SIP. Happy Eyeballs will provide enhanced performance,
and consequently enhanced user experience, in highly hybridized dual-
stack SIP networks. The procedures described herein are such that a
Show full document text