draft-ietf-dime-extended-naptr-05.txt   draft-ietf-dime-extended-naptr-06.txt 
Diameter Maintenance and M. Jones Diameter Maintenance and M. Jones
Extensions (DIME) Bridgewater Systems Extensions (DIME) Bridgewater Systems
Internet-Draft J. Korhonen Internet-Draft J. Korhonen
Updates: 3588 (if approved) Nokia Siemens Networks Updates: 3588 (if approved) Nokia Siemens Networks
Intended status: Standards Track L. Morand Intended status: Standards Track L. Morand
Expires: August 13, 2011 Orange Labs Expires: September 8, 2011 Orange Labs
February 9, 2011 March 7, 2011
Diameter S-NAPTR Usage Diameter S-NAPTR Usage
draft-ietf-dime-extended-naptr-05 draft-ietf-dime-extended-naptr-06
Abstract Abstract
The Diameter base protocol specifies mechanisms whereby a given realm The Diameter base protocol specifies mechanisms whereby a given realm
may advertise Diameter nodes and the supported transport protocol. may advertise Diameter nodes and the supported transport protocol.
However, these mechanism do not reveal the Diameter applications that However, these mechanisms do not reveal the Diameter applications
each node supports. A peer outside the realm would have to perform a that each node supports. A peer outside the realm would have to
Diameter capability exchange with every node until it discovers one perform a Diameter capability exchange with every node until it
that supports the required application. This document describes an discovers one that supports the required application. This document
improvement using an extended format for the Straightfoward-NAPTR updates [RFC3588] and describes an improvement using an extended
(S-NAPTR) Application Service Tag that allows for discovery of the format for the Straightforward-NAPTR (S-NAPTR) Application Service
supported applications without doing Diameter capability exchange Tag that allows for discovery of the supported applications without
beforehand. doing Diameter capability exchange beforehand.
Requirements Language Requirements Language
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on September 8, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 13, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Extended NAPTR Service Field Format . . . . . . . . . . . . . 4 3. Extended NAPTR Service Field Format . . . . . . . . . . . . . 3
3.1. IETF Standard Track Diameter Applications . . . . . . . . 5 3.1. IETF Standard Track Diameter Applications . . . . . . . . 4
3.2. Vendor-specific Diameter Applications . . . . . . . . . . 5 3.2. Vendor-specific Diameter Applications . . . . . . . . . . 4
4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 6 4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 5
5. Extended NAPTR-based Diameter Peer Discovery . . . . . . . . . 6 5. Extended NAPTR-based Diameter Peer Discovery . . . . . . . . . 5
6. Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . 7 6. Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. IETF Diameter Application Service Tags . . . . . . . . . . 8 7.1. IETF Diameter Application Service Tags . . . . . . . . . . 7
7.2. 3GPP Diameter Application Service Tags . . . . . . . . . . 8 7.2. 3GPP Diameter Application Service Tags . . . . . . . . . . 7
7.3. WiMAX Forum Diameter Application Service Tags . . . . . . 9 7.3. WiMAX Forum Diameter Application Service Tags . . . . . . 8
7.4. Vendor-Specific Diameter Application Service Tags . . . . 9 7.4. Vendor-Specific Diameter Application Service Tags . . . . 8
7.5. Diameter Application Protocol Tags . . . . . . . . . . . . 10 7.5. Diameter Application Protocol Tags . . . . . . . . . . . . 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
10. Editor's Notes . . . . . . . . . . . . . . . . . . . . . . . . 10 10. Editor's Notes . . . . . . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
11.1. Normative References . . . . . . . . . . . . . . . . . . . 11 11.1. Normative References . . . . . . . . . . . . . . . . . . . 10
11.2. Informative References . . . . . . . . . . . . . . . . . . 13 11.2. Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
The Diameter base protocol [RFC3588] specifies three mechanisms for The Diameter base protocol [RFC3588] specifies three mechanisms for
the Diameter peer discovery. One of these involves the Diameter the Diameter peer discovery. One of these involves the Diameter
implementation performing a NAPTR query [RFC3403] for a server in a implementation performing a NAPTR query [RFC3403] for a server in a
particular realm. These NAPTR records provide a mapping from a particular realm. These NAPTR records provide a mapping from a
domain, to the SRV record [RFC2782] or A/AAAA record domain, to the SRV record [RFC2782] or A/AAAA record
[RFC1035][RFC3596] for contacting a server with the specific [RFC1035][RFC3596] for contacting a server with the specific
transport protocol in the NAPTR services field. transport protocol in the NAPTR services field.
The extended NAPTR usage for Diameter peer discovery defined by this The extended NAPTR usage for Diameter peer discovery defined by this
document is based on the Straightfoward-NAPTR (S-NAPTR) Dynamic document is based on the Straightforward-NAPTR (S-NAPTR) Dynamic
Delegation Discovery System (DDDS) Application defined in [RFC3958]. Delegation Discovery System (DDDS) Application defined in [RFC3958].
This document updates the Diameter peer discovery procedure described This document updates the Diameter peer discovery procedure described
in Section 11.6 of [RFC3588] and defines S-NAPTR Application Service in Section 11.6 of [RFC3588] and defines S-NAPTR Application Service
and Application Protocol Tag values that permit the discovery of and Application Protocol Tag values that permit the discovery of
Diameter peers that support a specific Diameter application and Diameter peers that support a specific Diameter application and
transport protocol. transport protocol.
2. Terminology 2. Terminology
The Diameter base protocol specification (Section 1.4 of [RFC3588]) The Diameter base protocol specification (Section 1.4 of [RFC3588])
and the Straightforward-NAPTR (S-NAPTR) DDDS application (section 2.1 and the Straightforward-NAPTR (S-NAPTR) DDDS application (section 2.1
in [RFC3958]) define the terminology used in this document. in [RFC3958]) define the terminology used in this document.
3. Extended NAPTR Service Field Format 3. Extended NAPTR Service Field Format
The NAPTR Service Field format defined by the S-NAPTR DDDS The NAPTR Service Field format defined by the S-NAPTR DDDS
application in [RFC3958] follows this ABNF: application in [RFC3958] follows this Augmented Backus-Naur Form
(ABNF, [RFC5234]):
service-parms = [ [app-service] *(":" app-protocol)] service-parms = [ [app-service] *(":" app-protocol)]
app-service = experimental-service / iana-registered-service app-service = experimental-service / iana-registered-service
app-protocol = experimental-protocol / iana-registered-protocol app-protocol = experimental-protocol / iana-registered-protocol
experimental-service = "x-" 1*30ALPHANUMSYM experimental-service = "x-" 1*30ALPHANUMSYM
experimental-protocol = "x-" 1*30ALPHANUMSYM experimental-protocol = "x-" 1*30ALPHANUMSYM
iana-registered-service = ALPHA *31ALPHANUMSYM iana-registered-service = ALPHA *31ALPHANUMSYM
iana-registered-protocol = ALPHA *31ALPHANUMSYM iana-registered-protocol = ALPHA *31ALPHANUMSYM
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
DIGIT = %x30-39 ; 0-9 DIGIT = %x30-39 ; 0-9
skipping to change at page 5, line 9 skipping to change at page 4, line 11
; The app-service and app-protocol tags are limited to 32 ; The app-service and app-protocol tags are limited to 32
; characters and must start with an alphabetic character. ; characters and must start with an alphabetic character.
; The service-parms are considered case-insensitive. ; The service-parms are considered case-insensitive.
This specification refines the "iana-registered-service" tag This specification refines the "iana-registered-service" tag
definition for the discovery of Diameter agents supporting a specific definition for the discovery of Diameter agents supporting a specific
Diameter application as defined below. Diameter application as defined below.
iana-registered-service = aaa-service / ALPHA *31ALPHANUMSYM iana-registered-service = aaa-service / ALPHA *31ALPHANUMSYM
aaa-service = "aaa+ap" appln-id aaa-service = "aaa+ap" appln-id
appln-id = *DIGIT appln-id = DIGIT *DIGIT
; Application identifier expressed as a ; Application identifier expressed as a
; decimal integer. ; decimal integer.
This specification also refines the "iana-registered-protocol" tag This specification also refines the "iana-registered-protocol" tag
definition for the discovery of Diameter agents supporting a specific definition for the discovery of Diameter agents supporting a specific
Diameter transport protocol as defined below. Diameter transport protocol as defined below.
iana-registered-protocol = aaa-protocol / ALPHA *31ALPHANUMSYM iana-registered-protocol = aaa-protocol / ALPHA *31ALPHANUMSYM
aaa-protocol = "diameter." aaa-transport aaa-protocol = "diameter." aaa-transport
aaa-transport = "tcp" / "sctp" / "tls.tcp" aaa-transport = "tcp" / "sctp" / "tls.tcp"
skipping to change at page 6, line 34 skipping to change at page 5, line 36
of [RFC3588]. This specification updates the NAPTR query procedure of [RFC3588]. This specification updates the NAPTR query procedure
in the Diameter peer discovery mechanism by allowing the querying in the Diameter peer discovery mechanism by allowing the querying
node to determine which applications are supported by resolved node to determine which applications are supported by resolved
Diameter peers. Diameter peers.
The extended format NAPTR records provide a mapping from a domain to The extended format NAPTR records provide a mapping from a domain to
the SRV record or A/AAAA record for contacting a server supporting a the SRV record or A/AAAA record for contacting a server supporting a
specific transport protocol and Diameter application. The resource specific transport protocol and Diameter application. The resource
record will contain an empty regular expression and a replacement record will contain an empty regular expression and a replacement
value, which is the SRV record or the A/AAAA record for that value, which is the SRV record or the A/AAAA record for that
particular transport protocol. If the server supports multiple particular transport protocol.
transport protocols, there will be multiple NAPTR records, each with
a different Services Field value and potentially different list of
supported Diameter applications.
The assumption for this mechanism to work is that the DNS The assumption for this mechanism to work is that the DNS
administrator of the queried domain has first provisioned the DNS administrator of the queried domain has first provisioned the DNS
with extended format NAPTR entries. The steps below replace the with extended format NAPTR entries. The steps below replace the
NAPTR query procedure steps in Section 5.2 of [RFC3588]. NAPTR query procedure steps in Section 5.2 of [RFC3588].
a. The Diameter implementation performs a NAPTR query for a server in a. The Diameter implementation performs a NAPTR query for a server in
a particular realm. The Diameter implementation has to know in a particular realm. The Diameter implementation has to know in
advance which realm to look for a Diameter agent in and which advance which realm to look for a Diameter agent in and which
Application Identifier it is interested in. For example, the Application Identifier it is interested in. For example, the
realm could be deduced from the NAI in the User-Name AVP or realm could be deduced from the NAI in the User-Name AVP or
extracted from the Destination-Realm AVP. extracted from the Destination-Realm AVP.
b. If the returned NAPTR service fields contain entries formatted as b. If the returned NAPTR service fields contain entries formatted as
"aaa+apX:Y" where "X" indicates the Application Identifier and "Y" "aaa+apX:Y" where "X" indicates the Application Identifier and "Y"
indicates the transport protocol, the target realm supports the indicates the supported transport protocol(s), the target realm
extended format for NAPTR-based Diameter peer discovery defined in supports the extended format for NAPTR-based Diameter peer
this document. discovery defined in this document.
If "X" contains the required Application Identifier and "Y" If "X" contains the required Application Identifier and "Y"
matches a supported transport protocol, the Diameter matches a supported transport protocol, the Diameter
implementation resolves the "replacement" field entry to a implementation resolves the "replacement" field entry to a
target host using the lookup method appropriate for the "flags" target host using the lookup method appropriate for the "flags"
field. field.
If "X" does not contain the required Application Identifier or If "X" does not contain the required Application Identifier or
"Y" does not match a supported transport protocol, the Diameter "Y" does not match a supported transport protocol, the Diameter
implementation abandons the peer discovery. implementation abandons the peer discovery.
c. If the returned NAPTR service fields contain entries formatted as c. If the returned NAPTR service fields contain entries formatted as
"AAA+D2X" where "X" indicates the transport protocol, the target "aaa:X" where "X" indicates the supported transport protocol(s),
realm supports the NAPTR-based Diameter peer discovery defined in the target realm supports Diameter but does not support the
[RFC3588]. extended format for NAPTR-based Diameter peer discovery defined in
this document.
If "X" matches a supported transport protocol, the Diameter If "X" matches a supported transport protocol, the Diameter
implementation continues processing the NAPTR as described in implementation resolves the "replacement" field entry to a
[RFC3588] and [RFC2915]. target host using the lookup method appropriate for the "flags"
field.
If "X" does not match a supported transport protocol, the If "X" does not match a supported transport protocol, the
Diameter implementation abandons the peer discovery. Diameter implementation abandons the peer discovery.
d. If the target realm does not support NAPTR-based Diameter peer d. If the target realm does not support NAPTR-based Diameter peer
discovery, the client proceeds with the next peer discovery discovery, the client proceeds with the next peer discovery
mechanism described in Section 5.2 of [RFC3588]. mechanism described in Section 5.2 of [RFC3588].
6. Usage Guidelines 6. Usage Guidelines
skipping to change at page 12, line 17 skipping to change at page 11, line 17
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072, Authentication Protocol (EAP) Application", RFC 4072,
August 2005. August 2005.
[RFC4740] Garcia-Martin, M., Belinchon, M., Pallares-Lopez, M., [RFC4740] Garcia-Martin, M., Belinchon, M., Pallares-Lopez, M.,
Canales-Valenzuela, C., and K. Tammi, "Diameter Session Canales-Valenzuela, C., and K. Tammi, "Diameter Session
Initiation Protocol (SIP) Application", RFC 4740, Initiation Protocol (SIP) Application", RFC 4740,
November 2006. November 2006.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5778] Korhonen, J., Tschofenig, H., Bournelle, J., Giaretta, G., [RFC5778] Korhonen, J., Tschofenig, H., Bournelle, J., Giaretta, G.,
and M. Nakhjiri, "Diameter Mobile IPv6: Support for Home and M. Nakhjiri, "Diameter Mobile IPv6: Support for Home
Agent to Diameter Server Interaction", RFC 5778, Agent to Diameter Server Interaction", RFC 5778,
February 2010. February 2010.
[RFC5866] Sun, D., McCann, P., Tschofenig, H., Tsou, T., Doria, A., [RFC5866] Sun, D., McCann, P., Tschofenig, H., Tsou, T., Doria, A.,
and G. Zorn, "Diameter Quality-of-Service Application", and G. Zorn, "Diameter Quality-of-Service Application",
RFC 5866, May 2010. RFC 5866, May 2010.
[TS29.215] [TS29.215]
 End of changes. 17 change blocks. 
70 lines changed or deleted 55 lines changed or added

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