draft-ietf-dime-extended-naptr-07.txt   draft-ietf-dime-extended-naptr-08.txt 
Diameter Maintenance and Extensions M. Jones Diameter Maintenance and Extensions M. Jones
(DIME) Bridgewater Systems (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: November 10, 2011 Orange Labs Expires: November 10, 2011 Orange Labs
May 9, 2011 May 9, 2011
Diameter S-NAPTR Usage Diameter S-NAPTR Usage
draft-ietf-dime-extended-naptr-07 draft-ietf-dime-extended-naptr-08
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 mechanisms do not reveal the Diameter applications However, these mechanisms do not reveal the Diameter applications
that each node supports. A peer outside the realm would have to that each node supports. A peer outside the realm would have to
perform a Diameter capability exchange with every node until it perform a Diameter capability exchange with every node until it
discovers one that supports the required application. This document discovers one that supports the required application. This document
updates [RFC3588] and describes an improvement using an extended updates [RFC3588] and describes an improvement using an extended
skipping to change at page 2, line 29 skipping to change at page 2, line 29
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Extended NAPTR Service Field Format . . . . . . . . . . . . . 3 3. Extended NAPTR Service Field Format . . . . . . . . . . . . . 3
3.1. IETF Standard Track Diameter Applications . . . . . . . . 4 3.1. IETF Standard Track Diameter Applications . . . . . . . . 4
3.2. Vendor-specific Diameter Applications . . . . . . . . . . 4 3.2. Vendor-specific Diameter Applications . . . . . . . . . . 4
4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 5 4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 5
5. Extended NAPTR-based Diameter Peer Discovery . . . . . . . . . 5 5. Extended NAPTR-based Diameter Peer Discovery . . . . . . . . . 5
6. Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . 6 6. Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. IETF Diameter Application Service Tags . . . . . . . . . . 7 7.1. IETF Diameter Application Service Tags . . . . . . . . . . 7
7.2. 3GPP Diameter Application Service Tags . . . . . . . . . . 7 7.2. 3GPP Diameter Application Service Tags . . . . . . . . . . 8
7.3. WiMAX Forum Diameter Application Service Tags . . . . . . 8 7.3. WiMAX Forum Diameter Application Service Tags . . . . . . 8
7.4. Vendor-Specific Diameter Application Service Tags . . . . 8 7.4. Vendor-Specific Diameter Application Service Tags . . . . 9
7.5. Diameter Application Protocol Tags . . . . . . . . . . . . 9 7.5. Diameter Application Protocol Tags . . . . . . . . . . . . 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
10. Editor's Notes . . . . . . . . . . . . . . . . . . . . . . . . 9 10. Editor's Notes . . . . . . . . . . . . . . . . . . . . . . . . 10
11. Normative References . . . . . . . . . . . . . . . . . . . . . 10 11. Normative References . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 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 Naming Authority Pointer (NAPTR) query implementation performing a Naming Authority Pointer (NAPTR) query
[RFC3403] for a server in a particular realm. These NAPTR records [RFC3403] for a server in a particular realm. These NAPTR records
provide a mapping from a domain, to the SRV record [RFC2782] or provide a mapping from a domain, to the SRV record [RFC2782] or
A/AAAA record [RFC1035][RFC3596] for contacting a server with the A/AAAA record [RFC1035][RFC3596] for contacting a server with the
specific transport protocol in the NAPTR services field. specific transport protocol in the NAPTR services field.
skipping to change at page 4, line 11 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 *DIGIT appln-id = 1*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 22 skipping to change at page 6, line 22
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+apX" where "X" indicates the Application Identifier, the
target realm supports the extended format for NAPTR-based Diameter
peer discovery defined in this document.
If "X" contains the required Application Identifier, the
Diameter implementation resolves the "replacement" field entry
to a target host using the lookup method appropriate for the
"flags" field and attempts to connect using all supported
transport protocols following the order specified in section
2.1 of [RFC3588].
If "X" does not contain the required Application Identifier,
the Diameter implementation abandons the peer discovery.
d. If the returned NAPTR service fields contain entries formatted as
"aaa:X" where "X" indicates the supported transport protocol(s), "aaa:X" where "X" indicates the supported transport protocol(s),
the target realm supports Diameter but does not support the the target realm supports Diameter but does not support the
extended format for NAPTR-based Diameter peer discovery defined in extended format for NAPTR-based Diameter peer discovery defined in
this document. this document.
If "X" matches a supported transport protocol, the Diameter If "X" 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 match a supported transport protocol, the e. If the returned NAPTR service fields contain entries formatted as
Diameter implementation abandons the peer discovery. "aaa", the target realm supports Diameter but does not support the
extended format for NAPTR-based Diameter peer discovery defined in
this document. The Diameter implementation resolves the
"replacement" field entry to a target host using the lookup method
appropriate for the "flags" field and attempts to connect using
all supported transport protocols following the order specified in
section 2.1 of [RFC3588].
d. If the target realm does not support NAPTR-based Diameter peer f. 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
Diameter is a peer to peer protocol whereas most of the applications Diameter is a peer to peer protocol whereas most of the applications
that extend the base protocol behave like client/server applications. that extend the base protocol behave like client/server applications.
The role of the peer is not advertised in the NAPTR tags and not even The role of the peer is not advertised in the NAPTR tags and not even
communicated during Diameter capability negotiation (Capabilities- communicated during Diameter capability negotiation (Capabilities-
Exchange-Request and Capabilities-Exchange-Answer message exchange). Exchange-Request and Capabilities-Exchange-Answer message exchange).
 End of changes. 10 change blocks. 
11 lines changed or deleted 32 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/