draft-ietf-dime-extended-naptr-01.txt   draft-ietf-dime-extended-naptr-02.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 May 4, 2010 Intended status: Standards Track September 2, 2010
Expires: November 5, 2010 Expires: March 6, 2011
Diameter Extended NAPTR Diameter Extended NAPTR
draft-ietf-dime-extended-naptr-01 draft-ietf-dime-extended-naptr-02
Abstract Abstract
This document describes an extended format for the S-NAPTR This document describes an extended format for the S-NAPTR
Application Service Tag used in dynamic Diameter agent discovery. Application Service Tag used in dynamic Diameter agent discovery.
The extended format allows NAPTR queries to contain Diameter The extended format allows NAPTR queries to contain Diameter
Application-Id information. Application-Id information.
Requirements Language Requirements Language
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 5, 2010. This Internet-Draft will expire on March 6, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 3, line 11 skipping to change at page 3, line 11
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Extended NAPTR Service Field Format . . . . . . . . . . . . . . 4 3. Extended NAPTR Service Field Format . . . . . . . . . . . . . . 4
4. Extended NAPTR-based Diameter Peer Discovery . . . . . . . . . 5 4. Extended NAPTR-based Diameter Peer Discovery . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 5. Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. IETF Diameter Application Service Tags . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
5.2. Vendor-Specific Diameter Application Service Tags . . . . . 7 6.1. IETF Diameter Application Service Tags . . . . . . . . . . 7
5.3. Diameter Application Protocol Tags . . . . . . . . . . . . 7 6.2. Vendor-Specific Diameter Application Service Tags . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 6.3. Diameter Application Protocol Tags . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
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
skipping to change at page 6, line 44 skipping to change at page 6, line 44
the client continues processing the NAPTR as described in the client continues processing the NAPTR as described in
[RFC3588] and [RFC2915]. [RFC3588] and [RFC2915].
If "X" does not match a transport protocol supported by the If "X" does not match a transport protocol supported by the
client, the peer discovery is abandoned. client, the peer discovery is abandoned.
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].
5. IANA Considerations 5. Usage Guidelines
5.1. IETF Diameter Application Service Tags Diameter is a peer to peer protocol whereas most of the 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
communicated during Diameter capability negotiation (CER/CEA). For
this reason, NAPTR-based Diameter peer discovery for an application
defining client/server roles should only be used by a client to
discover servers.
6. IANA Considerations
6.1. IETF Diameter Application Service Tags
IANA is requested to reserve the following S-NAPTR Application IANA is requested to reserve the following S-NAPTR Application
Service Tags for existing IETF Diameter applications: Service Tags for existing IETF Diameter applications:
+------------------+----------------------------------+ +------------------+----------------------------+
| Tag | Diameter Application | | Tag | Diameter Application |
+------------------+----------------------------------+ +------------------+----------------------------+
| aaa+ap1 | NASREQ [RFC3588] | | aaa+ap1 | NASREQ [RFC3588] |
| aaa+ap2 | Mobile IPv4 [RFC4004] | | aaa+ap2 | Mobile IPv4 [RFC4004] |
| aaa+ap3 | Base Accounting [RFC3588] | | aaa+ap3 | Base Accounting [RFC3588] |
| aaa+ap4 | Credit Control [RFC4006] | | aaa+ap4 | Credit Control [RFC4006] |
| aaa+ap5 | EAP [RFC4072] | | aaa+ap5 | EAP [RFC4072] |
| aaa+ap6 | SIP [RFC4740] | | aaa+ap6 | SIP [RFC4740] |
| aaa+ap7 | Mobile IPv6 IKE [RFC5778] | | aaa+ap7 | Mobile IPv6 IKE [RFC5778] |
| aaa+ap8 | Mobile IPv6 Auth [RFC5778] | | aaa+ap8 | Mobile IPv6 Auth [RFC5778] |
| aaa+ap9 | QoS [I-D.ietf-dime-diameter-qos] | | aaa+ap9 | QoS [RFC5866] |
| aaa+ap4294967295 | Relay [RFC3588] | | aaa+ap4294967295 | Relay [RFC3588] |
+------------------+----------------------------------+ +------------------+----------------------------+
Editor's Note: Update the table with the RFC number assigned to the
Diameter QoS Application.
Future IETF Diameter applications MUST reserve the S-NAPTR Future IETF Diameter applications MUST reserve the S-NAPTR
Application Service Tag corresponding to the allocated Diameter Application Service Tag corresponding to the allocated Diameter
Application ID. Application ID.
5.2. Vendor-Specific Diameter Application Service Tags 6.2. Vendor-Specific Diameter Application Service Tags
Vendor-Specific Diameter Application IDs are allocated by IANA Vendor-Specific Diameter Application IDs are allocated by IANA
according to the "First Come First Served" policy and do not require according to the "First Come First Served" policy and do not require
an IETF specification. However, the S-NAPTR Application Service Tag an IETF specification. However, the S-NAPTR Application Service Tag
registry created by [RFC3958] defines a registration policy of registry created by [RFC3958] defines a registration policy of
"Specification Required" with a further stipulation that the "Specification Required" with a further stipulation that the
"specification" is an RFC (of any category). If a Vendor-Specific "specification" is an RFC (of any category). If a Vendor-Specific
Diameter Application requires the functionality defined in this Diameter Application requires the functionality defined in this
document, an RFC of any category MUST be published which reserves the document, an RFC of any category MUST be published which reserves the
S-NAPTR Application Service Tag corresponding to the Vendor-Specific S-NAPTR Application Service Tag corresponding to the Vendor-Specific
Diameter Application ID. Diameter Application ID.
5.3. Diameter Application Protocol Tags 6.3. Diameter Application Protocol Tags
IANA is requested to reserve the following S-NAPTR Application IANA is requested to reserve the following S-NAPTR Application
Protocol Tags for the Diameter transport protocols: Protocol Tags for the Diameter transport protocols:
+------------------+----------+ +------------------+----------+
| Tag | Protocol | | Tag | Protocol |
+------------------+----------+ +------------------+----------+
| diameter.tcp | TCP | | diameter.tcp | TCP |
| diameter.sctp | SCTP | | diameter.sctp | SCTP |
| diameter.tls.tcp | TLS/TCP | | diameter.tls.tcp | TLS/TCP |
+------------------+----------+ +------------------+----------+
6. Security Considerations 7. Security Considerations
This document specifies an enhancement to RFC 3588 Diameter base This document specifies an enhancement to RFC 3588 Diameter base
protocol defined NAPTR service field format and also modifications to protocol defined NAPTR service field format and also modifications to
the NAPTR processing logic defined. The enhancements and the NAPTR processing logic defined. The enhancements and
modifications are based on the S-NAPTR, which is actually a modifications are based on the S-NAPTR, which is actually a
simplification of the NAPTR, and therefore the same security simplification of the NAPTR, and therefore the same security
considerations described in RFC 3588 are applicable to this document. considerations described in RFC 3588 are applicable to this document.
No further extensions are required beyond the security mechanisms No further extensions are required beyond the security mechanisms
offered by RFC 3588. However, a malicious host doing S-NAPTR queries offered by RFC 3588. However, a malicious host doing S-NAPTR queries
learns applications supported by Diameter agents in a certain realm learns applications supported by Diameter agents in a certain realm
faster, which might help the malicious host to scan potential targets faster, which might help the malicious host to scan potential targets
for an attack more efficiently when some applications have known for an attack more efficiently when some applications have known
vulnerabilities. vulnerabilities.
7. References 8. References
7.1. Normative References
[I-D.ietf-dime-diameter-qos] 8.1. Normative References
Sun, D., McCann, P., Tschofenig, H., ZOU), T., Doria, A.,
and G. Zorn, "Diameter Quality of Service Application",
draft-ietf-dime-diameter-qos-15 (work in progress),
March 2010.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782, specifying the location of services (DNS SRV)", RFC 2782,
February 2000. February 2000.
skipping to change at page 9, line 29 skipping to change at page 9, line 32
[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.
[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.
7.2. Informative References [RFC5866] Sun, D., McCann, P., Tschofenig, H., Tsou, T., Doria, A.,
and G. Zorn, "Diameter Quality-of-Service Application",
RFC 5866, May 2010.
8.2. Informative References
[RFC2915] Mealling, M. and R. Daniel, "The Naming Authority Pointer [RFC2915] Mealling, M. and R. Daniel, "The Naming Authority Pointer
(NAPTR) DNS Resource Record", RFC 2915, September 2000. (NAPTR) DNS Resource Record", RFC 2915, September 2000.
Authors' Addresses Authors' Addresses
Mark Jones Mark Jones
Bridgewater Systems Bridgewater Systems
Email: mark@azu.ca Email: mark@azu.ca
 End of changes. 13 change blocks. 
43 lines changed or deleted 49 lines changed or added

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