draft-ietf-sipcore-dns-dual-stack-03.txt   draft-ietf-sipcore-dns-dual-stack-04.txt 
SIPCORE O. Johansson SIPCORE O. Johansson
Internet-Draft Edvina AB Internet-Draft Edvina AB
Updates: RFC 6157 (if approved) G. Salgueiro Updates: RFC 3263 (if approved) G. Salgueiro
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: August 4, 2016 V. Gurbani Expires: August 26, 2016 V. Gurbani
Bell Labs, Alcatel-Lucent Bell Labs, Alcatel-Lucent
D. Worley, Ed. D. Worley, Ed.
Ariadne Internet Services Ariadne
February 1, 2016 February 23, 2016
Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP
Network Network
draft-ietf-sipcore-dns-dual-stack-03 draft-ietf-sipcore-dns-dual-stack-04
Abstract Abstract
RFC 3263 defines how a Session Initiation Protocol (SIP) RFC 3263 defines how a Session Initiation Protocol (SIP)
implementation, given a SIP Uniform Resource Identifier (URI), should implementation, given a SIP Uniform Resource Identifier (URI), should
locate the next hop SIP server using Domain Name System (DNS) locate the next hop SIP server using Domain Name System (DNS)
procedures. As SIP networks increasingly transition from IPv4-only procedures. As SIP networks increasingly transition from IPv4-only
to dual-stack, a quality user experience must be ensured for dual- to dual-stack, a quality user experience must be ensured for dual-
stack SIP implementations. This document updates the DNS procedures stack SIP implementations. This document updates the DNS procedures
described in RFC 3263 for dual-stack SIP implementations in described in RFC 3263 for dual-stack SIP implementations in
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 August 4, 2016. This Internet-Draft will expire on August 26, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 33 skipping to change at page 2, line 33
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 3 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. DNS Procedures in a Dual-Stack Network . . . . . . . . . . . 4 4. DNS Procedures in a Dual-Stack Network . . . . . . . . . . . 4
4.1. Dual-Stack SIP UA DNS Record Lookup Procedure . . . . . . 4 4.1. Dual-Stack SIP UA DNS Record Lookup Procedure . . . . . . 4
4.2. Indicating Address Family Preference in DNS SRV Records . 5 4.2. Indicating Address Family Preference in DNS SRV Records . 5
5. Clarification of RFC 6157 . . . . . . . . . . . . . . . . . . 5 5. Clarification of RFC 6157 . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
9. Revision History . . . . . . . . . . . . . . . . . . . . . . 6 9. Revision History . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Changes from draft-ietf-sipcore-dns-dual-stack-02 to 9.1. Changes from draft-ietf-sipcore-dns-dual-stack-03 to
draft-ietf-sipcore-dns-dual-stack-04 . . . . . . . . . . 6
9.2. Changes from draft-ietf-sipcore-dns-dual-stack-02 to
draft-ietf-sipcore-dns-dual-stack-03 . . . . . . . . . . 6 draft-ietf-sipcore-dns-dual-stack-03 . . . . . . . . . . 6
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP, [RFC3261]) and the additional The Session Initiation Protocol (SIP, [RFC3261]) and the additional
documents that extended it provide support for both IPv4 and IPv6. documents that extended it provide support for both IPv4 and IPv6.
However, this support does not fully extend to the highly hybridized However, this support does not fully extend to the highly hybridized
environments that are characteristic of the transitional migratory environments that are characteristic of the transitional migratory
phase from IPv4 to IPv6 networks. During this phase, many server and phase from IPv4 to IPv6 networks. During this phase, many server and
client implementations run on dual-stack hosts. In such client implementations run on dual-stack hosts. In such
skipping to change at page 3, line 20 skipping to change at page 3, line 20
Eyeballs to SIP to provide enhanced performance, and consequently Eyeballs to SIP to provide enhanced performance, and consequently
user experience, in highly hybridized dual-stack SIP networks. The user experience, in highly hybridized dual-stack SIP networks. The
procedures described herein are such that a dual-stack client should procedures described herein are such that a dual-stack client should
look up both A and AAAA records in DNS and then select the best way look up both A and AAAA records in DNS and then select the best way
to set up a network flow. The details of how the latter is done is to set up a network flow. The details of how the latter is done is
considered out of scope for this document. See the Happy Eyeballs considered out of scope for this document. See the Happy Eyeballs
algorithm and implementation and design considerations in RFC 6555 algorithm and implementation and design considerations in RFC 6555
[RFC6555] for more information about issues with setting up dual- [RFC6555] for more information about issues with setting up dual-
stack network flows. stack network flows.
This document updates [RFC6157] as described in Section Section 5. This document clarifies the interaction of [RFC3263] with [RFC6157]
as described in Section 5.
2. Notational Conventions 2. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Terminology 3. Terminology
RFC 3261 [RFC3261] defines additional terms used in this document RFC 3261 [RFC3261] defines additional terms used in this document
skipping to change at page 6, line 23 skipping to change at page 6, line 26
The authors would like to acknowledge the support and contribution of The authors would like to acknowledge the support and contribution of
the SIP Forum IPv6 Working Group. This document is based on a lot of the SIP Forum IPv6 Working Group. This document is based on a lot of
tests and discussions at SIPit events, organized by the SIP Forum. tests and discussions at SIPit events, organized by the SIP Forum.
This document has benefited from the expertise and review feedback of This document has benefited from the expertise and review feedback of
many participants of the IETF DISPATCH and SIPCORE WG mailing lists many participants of the IETF DISPATCH and SIPCORE WG mailing lists
as well as those on the SIP Forum IPv6 Task Group mailing list. The as well as those on the SIP Forum IPv6 Task Group mailing list. The
authors wish to specifically call out the efforts and express their authors wish to specifically call out the efforts and express their
gratitude for the detailed and thoughtful comments and corrections of gratitude for the detailed and thoughtful comments and corrections of
Dan Wing, Brett Tate, Rifaat Shekh-Yusef, Carl Klatsky, Mary Barnes, Dan Wing, Brett Tate, Rifaat Shekh-Yusef, Carl Klatsky, Mary Barnes,
Keith Drage and Cullen Jennings. Keith Drage, Cullen Jennings and Simon Perreault.
The authors also thank the SIPCORE WG chairs, Paul Kyzivat and Adam The authors also thank the SIPCORE WG chairs, Paul Kyzivat and Adam
Roach, and assigned Area Director, Richard Barnes, for their support Roach, and assigned Area Director, Richard Barnes, for their support
and thorough evaluation of this work. and thorough evaluation of this work.
9. Revision History 9. Revision History
[Note to RFC Editor: Please remove this entire section upon [Note to RFC Editor: Please remove this entire section upon
publication as an RFC.] publication as an RFC.]
9.1. Changes from draft-ietf-sipcore-dns-dual-stack-02 to draft-ietf- 9.1. Changes from draft-ietf-sipcore-dns-dual-stack-03 to draft-ietf-
sipcore-dns-dual-stack-04
Changed the "updates" specification to add RFC 3263 and remove RFC
6157.
Added Simon Perreault to the acknowledgments.
Minor wording changes.
9.2. Changes from draft-ietf-sipcore-dns-dual-stack-02 to draft-ietf-
sipcore-dns-dual-stack-03 sipcore-dns-dual-stack-03
Described the relationship to RFC 3263 as "update", since the
existing wording in 3263 is not what we want. Arguably, the new
wording is what was intended in 3263, but the existing wording either
does not say that or says it in a way that is easily misunderstood.
Described the relationship to RFC 6157 as "clarification", since the
described interaction between 3263 and 6157 appears to be the only
reasonable interpretation.
Revised wording, punctuation, and capitalization in various places. Revised wording, punctuation, and capitalization in various places.
Clarified that this draft does not document Happy Eyeballs for SIP, Clarified that this draft does not document Happy Eyeballs for SIP,
but is preparatory for it. but is preparatory for it.
Attempted to use "update" for text that is definitively a change to Attempted to use "update" for text that is definitively a change to
the preexisting text and "clarify" for text that is a more clear the preexisting text and "clarify" for text that is a more clear
statement of the (presumed) intention of the preexisting text. statement of the (presumed) intention of the preexisting text.
Removed normative words from section 1, the introduction. Removed normative words from section 1, the introduction.
 End of changes. 11 change blocks. 
11 lines changed or deleted 33 lines changed or added

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