draft-ietf-sipcore-dns-dual-stack-05.txt   draft-ietf-sipcore-dns-dual-stack-06.txt 
SIPCORE O. Johansson SIPCORE O. Johansson
Internet-Draft Edvina AB Internet-Draft Edvina AB
Updates: 3263 (if approved) G. Salgueiro Updates: 3263 (if approved) G. Salgueiro
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: October 17, 2016 V. Gurbani Expires: November 3, 2016 V. Gurbani
Bell Labs, Alcatel-Lucent Bell Labs, Alcatel-Lucent
D. Worley, Ed. D. Worley, Ed.
Ariadne Ariadne
April 15, 2016 May 2, 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-05 draft-ietf-sipcore-dns-dual-stack-06
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 October 17, 2016. This Internet-Draft will expire on November 3, 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 27 skipping to change at page 2, line 27
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. DNS Procedures in a Dual-Stack Network . . . . . . . . . . . 4 3. DNS Procedures in a Dual-Stack Network . . . . . . . . . . . 4
3.1. Dual-Stack SIP UA DNS Record Lookup Procedure . . . . . . 4 3.1. Dual-Stack SIP UA DNS Record Lookup Procedure . . . . . . 4
3.2. Indicating Address Family Preference in DNS SRV Records . 5 3.2. Indicating Address Family Preference in DNS SRV Records . 5
4. Clarification of RFC 6157 . . . . . . . . . . . . . . . . . . 5 4. Clarification of interaction with RFC 6724 . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
8. Revision History . . . . . . . . . . . . . . . . . . . . . . 7 8. Revision History . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Changes from draft-ietf-sipcore-dns-dual-stack-04 to 8.1. Changes from draft-ietf-sipcore-dns-dual-stack-05 to
draft-ietf-sipcore-dns-dual-stack-05 . . . . . . . . . . 7 draft-ietf-sipcore-dns-dual-stack-06 . . . . . . . . . . 7
8.2. Changes from draft-ietf-sipcore-dns-dual-stack-03 to 8.2. Changes from draft-ietf-sipcore-dns-dual-stack-04 to
draft-ietf-sipcore-dns-dual-stack-05 . . . . . . . . . . 8
8.3. Changes from draft-ietf-sipcore-dns-dual-stack-03 to
draft-ietf-sipcore-dns-dual-stack-04 . . . . . . . . . . 8 draft-ietf-sipcore-dns-dual-stack-04 . . . . . . . . . . 8
8.3. Changes from draft-ietf-sipcore-dns-dual-stack-02 to 8.4. Changes from draft-ietf-sipcore-dns-dual-stack-02 to
draft-ietf-sipcore-dns-dual-stack-03 . . . . . . . . . . 8 draft-ietf-sipcore-dns-dual-stack-03 . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 9 9.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
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.
skipping to change at page 3, line 22 skipping to change at page 3, line 24
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.
Section 4 of this document clarifies the interaction of [RFC3263] Section 4 of this document clarifies the interaction of [RFC3263]
with [RFC6157]. with [RFC6157] and [RFC6724].
2. Terminology 2. Terminology
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].
RFC 3261 [RFC3261] defines additional terms used in this document RFC 3261 [RFC3261] defines additional terms used in this document
that are specific to the SIP domain such as "proxy", "registrar", that are specific to the SIP domain such as "proxy", "registrar",
"redirect server", "user agent server" or "UAS", "user agent client" "redirect server", "user agent server" or "UAS", "user agent client"
skipping to change at page 5, line 30 skipping to change at page 5, line 35
differences in their IPv4 or IPv6 network paths. In this common differences in their IPv4 or IPv6 network paths. In this common
scenario it is often necessary for a dual-stack client to indicate a scenario it is often necessary for a dual-stack client to indicate a
preference for either IPv4 or IPv6. A service may use DNS SRV preference for either IPv4 or IPv6. A service may use DNS SRV
records to indicate such a preference for an address family. This records to indicate such a preference for an address family. This
way, a server with a high-latency and/or low-capacity IPv4 tunnel may way, a server with a high-latency and/or low-capacity IPv4 tunnel may
indicate a preference for being contacted using IPv6. A server that indicate a preference for being contacted using IPv6. A server that
wishes to do this can use the lowest SRV priority to publish wishes to do this can use the lowest SRV priority to publish
hostnames that only resolve in IPv6 and the next priority with host hostnames that only resolve in IPv6 and the next priority with host
names that resolve in both address families. names that resolve in both address families.
4. Clarification of RFC 6157 4. Clarification of interaction with RFC 6724
Section 5 of [RFC6157] specifies that the addresses from the address Section 5 of [RFC6157] specifies that the addresses from the address
records for a single target DNS name for a server's DNS name must be records for a single target DNS name for a server's DNS name must be
contacted in the order specified by the Source and Destination contacted in the order specified by the Source and Destination
Address Selection algorithms defined in [RFC6724] (the successor of Address Selection algorithms defined in [RFC6724] (the successor of
[RFC3484]). Typically, this is done by using the getaddrinfo() [RFC3484]). Typically, this is done by using the getaddrinfo()
function to translate the target DNS name into a list of IPv4 and/or function to translate the target DNS name into a list of IPv4 and/or
IPv6 addresses in the order in which they are to be contacted, as IPv6 addresses in the order in which they are to be contacted, as
that function implements [RFC6724]. that function implements [RFC6724].
skipping to change at page 7, line 35 skipping to change at page 7, line 38
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, Cullen Jennings, Simon Perreault, Paul Kyzivat, Adam Keith Drage, Cullen Jennings, Simon Perreault, Paul Kyzivat, Adam
Roach, and Richard Barnes. Roach, and Richard Barnes. Adam Roach devised the example in
Section 4.
8. Revision History 8. 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.]
8.1. Changes from draft-ietf-sipcore-dns-dual-stack-04 to draft-ietf- 8.1. Changes from draft-ietf-sipcore-dns-dual-stack-05 to draft-ietf-
sipcore-dns-dual-stack-06
Acknowledged Adam Roach for providing the example in Section 4.
Correct references to [RFC6157] vs. references to [RFC6724].
8.2. Changes from draft-ietf-sipcore-dns-dual-stack-04 to draft-ietf-
sipcore-dns-dual-stack-05 sipcore-dns-dual-stack-05
Simplified the acknowledgments. Simplified the acknowledgments.
Improve wording and punctuation. Improve wording and punctuation.
Rewrote Section 4 based on critiques on the Sipcore list. Included Rewrote Section 4 based on critiques on the Sipcore list. Included
an example by Adam Roach. an example by Adam Roach.
Replaced "RR's" with "records" per suggestion by Jean Mahoney. Replaced "RR's" with "records" per suggestion by Jean Mahoney.
8.2. Changes from draft-ietf-sipcore-dns-dual-stack-03 to draft-ietf- 8.3. Changes from draft-ietf-sipcore-dns-dual-stack-03 to draft-ietf-
sipcore-dns-dual-stack-04 sipcore-dns-dual-stack-04
Changed the "updates" specification to add RFC 3263 and remove RFC Changed the "updates" specification to add RFC 3263 and remove RFC
6157. 6157.
Added Simon Perreault to the acknowledgments. Added Simon Perreault to the acknowledgments.
Minor wording changes. Minor wording changes.
8.3. Changes from draft-ietf-sipcore-dns-dual-stack-02 to draft-ietf- 8.4. 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 Described the relationship to RFC 3263 as "update", since the
existing wording in 3263 is not what we want. Arguably, the new existing wording in 3263 is not what we want. Arguably, the new
wording is what was intended in 3263, but the existing wording either 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. 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 the relationship to RFC 6157 as "clarification", since the
described interaction between 3263 and 6157 appears to be the only described interaction between 3263 and 6157 appears to be the only
reasonable interpretation. reasonable interpretation.
skipping to change at page 9, line 31 skipping to change at page 9, line 42
[RFC3263] Rosenberg, J. and H. Schulzrinne, "Session Initiation [RFC3263] Rosenberg, J. and H. Schulzrinne, "Session Initiation
Protocol (SIP): Locating SIP Servers", RFC 3263, Protocol (SIP): Locating SIP Servers", RFC 3263,
DOI 10.17487/RFC3263, June 2002, DOI 10.17487/RFC3263, June 2002,
<http://www.rfc-editor.org/info/rfc3263>. <http://www.rfc-editor.org/info/rfc3263>.
[RFC6157] Camarillo, G., El Malki, K., and V. Gurbani, "IPv6 [RFC6157] Camarillo, G., El Malki, K., and V. Gurbani, "IPv6
Transition in the Session Initiation Protocol (SIP)", Transition in the Session Initiation Protocol (SIP)",
RFC 6157, DOI 10.17487/RFC6157, April 2011, RFC 6157, DOI 10.17487/RFC6157, April 2011,
<http://www.rfc-editor.org/info/rfc6157>. <http://www.rfc-editor.org/info/rfc6157>.
[RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown,
"Default Address Selection for Internet Protocol Version 6
(IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012,
<http://www.rfc-editor.org/info/rfc6724>.
9.2. Informative References 9.2. Informative References
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>. <http://www.rfc-editor.org/info/rfc3261>.
[RFC3484] Draves, R., "Default Address Selection for Internet [RFC3484] Draves, R., "Default Address Selection for Internet
Protocol version 6 (IPv6)", RFC 3484, Protocol version 6 (IPv6)", RFC 3484,
skipping to change at page 10, line 5 skipping to change at page 10, line 25
[RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms [RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms
for IPv6 Hosts and Routers", RFC 4213, for IPv6 Hosts and Routers", RFC 4213,
DOI 10.17487/RFC4213, October 2005, DOI 10.17487/RFC4213, October 2005,
<http://www.rfc-editor.org/info/rfc4213>. <http://www.rfc-editor.org/info/rfc4213>.
[RFC6555] Wing, D. and A. Yourtchenko, "Happy Eyeballs: Success with [RFC6555] Wing, D. and A. Yourtchenko, "Happy Eyeballs: Success with
Dual-Stack Hosts", RFC 6555, DOI 10.17487/RFC6555, April Dual-Stack Hosts", RFC 6555, DOI 10.17487/RFC6555, April
2012, <http://www.rfc-editor.org/info/rfc6555>. 2012, <http://www.rfc-editor.org/info/rfc6555>.
[RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown,
"Default Address Selection for Internet Protocol Version 6
(IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012,
<http://www.rfc-editor.org/info/rfc6724>.
Authors' Addresses Authors' Addresses
Olle E. Johansson Olle E. Johansson
Edvina AB Edvina AB
Runbovaegen 10 Runbovaegen 10
Sollentuna SE-192 48 Sollentuna SE-192 48
SE SE
Email: oej@edvina.net Email: oej@edvina.net
 End of changes. 15 change blocks. 
20 lines changed or deleted 30 lines changed or added

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