draft-ietf-dime-extended-naptr-04.txt   draft-ietf-dime-extended-naptr-05.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: July 10, 2011 Orange Labs Expires: August 13, 2011 Orange Labs
January 6, 2011 February 9, 2011
Diameter Extended NAPTR Diameter S-NAPTR Usage
draft-ietf-dime-extended-naptr-04 draft-ietf-dime-extended-naptr-05
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 mechanism do not reveal the Diameter applications that
each node supports. A peer outside the realm would have to perform a each node supports. A peer outside the realm would have to perform a
Diameter capability exchange with every node until it discovers one Diameter capability exchange with every node until it discovers one
that supports the required application. This document describes an that supports the required application. This document describes an
improvement using an extended format for the Straightfoward-NAPTR improvement using an extended format for the Straightfoward-NAPTR
skipping to change at page 2, line 8 skipping to change at page 2, line 8
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 July 10, 2011. 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
skipping to change at page 3, line 23 skipping to change at page 3, line 23
5. Extended NAPTR-based Diameter Peer Discovery . . . . . . . . . 6 5. Extended NAPTR-based Diameter Peer Discovery . . . . . . . . . 6
6. Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . 7 6. Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. IETF Diameter Application Service Tags . . . . . . . . . . 8 7.1. IETF Diameter Application Service Tags . . . . . . . . . . 8
7.2. 3GPP Diameter Application Service Tags . . . . . . . . . . 8 7.2. 3GPP Diameter Application Service Tags . . . . . . . . . . 8
7.3. WiMAX Forum Diameter Application Service Tags . . . . . . 9 7.3. WiMAX Forum Diameter Application Service Tags . . . . . . 9
7.4. Vendor-Specific Diameter Application Service Tags . . . . 9 7.4. Vendor-Specific Diameter Application Service Tags . . . . 9
7.5. Diameter Application Protocol Tags . . . . . . . . . . . . 10 7.5. Diameter Application Protocol Tags . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 10. Editor's Notes . . . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Normative References . . . . . . . . . . . . . . . . . . . 10 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . . 12 11.1. Normative References . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 11.2. Informative References . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
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.
skipping to change at page 8, line 6 skipping to change at page 8, line 6
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 (CER/CEA). For communicated during Diameter capability negotiation (CER/CEA). For
this reason, NAPTR-based Diameter peer discovery for an application this reason, NAPTR-based Diameter peer discovery for an application
defining client/server roles should only be used by a client to defining client/server roles should only be used by a client to
discover servers. discover servers.
7. IANA Considerations 7. IANA Considerations
7.1. IETF Diameter Application Service Tags 7.1. IETF Diameter Application Service Tags
IANA is requested to reserve the following S-NAPTR Application IANA is requested to reserve a value of "aaa" for Diameter in the
Service Tags for existing IETF Diameter applications in the S-NAPTR S-NAPTR Application Service Tag registry created by [RFC3958]. IANA
Application Service Tag registry created by [RFC3958]. is also requested to reserve the following S-NAPTR Application
Service Tags for existing IETF Diameter applications in the same
registry.
+------------------+----------------------------+ +------------------+----------------------------+
| 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] |
skipping to change at page 10, line 37 skipping to change at page 10, line 37
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.
9. Acknowledgments 9. Acknowledgments
We would like to thank Avi Lior, Itsuma Tanaka and Lionel Morand for We would like to thank Glen Zorn, Avi Lior, Itsuma Tanaka, Lionel
their comprehensive review comments. Morand and Sebastien Decugis for their comprehensive review comments.
10. References 10. Editor's Notes
10.1. Normative References This section to be removed prior to publication.
This draft updates sections of RFC3588 that are also being updated by
RFC3588bis. At the time this draft was started, it was uncertain
whether RFC3588bis would be published first. The authors of this
draft decided to proceed optimistically assuming this draft would be
published first with the understanding that minor updates are
required if this is not the case.
The application-neutral aspects of Diameter S-NAPTR usage (e.g "aaa:
diameter.sctp") were also contributed to RFC3588bis to ensure that it
would be functionally complete if it got published first and this
draft would come along later to add the application-specific S-NAPTR
entries (e.g."aaa+ap5:diameter.sctp").
Depending on the publication order, the S-NAPTR Application Service
Tag registry value of "aaa" and the S-NAPTR Application Protocol Tags
values ("diameter.tcp"/"diameter.sctp"/"diameter.tls.tcp") will need
to be removed either from this draft or RFC3588bis.
11. References
11.1. Normative References
[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 12, line 25 skipping to change at page 13, line 5
[TS29.273] [TS29.273]
3rd Generation Partnership Project, "3GPP TS 29.273; 3rd Generation Partnership Project, "3GPP TS 29.273;
Technical Specification Group Core Network and Terminals; Technical Specification Group Core Network and Terminals;
Evolved Packet System; 3GPP EPS AAA interfaces (Release Evolved Packet System; 3GPP EPS AAA interfaces (Release
8)", http://www.3gpp.org/ftp/Specs/html-info/29273.htm. 8)", http://www.3gpp.org/ftp/Specs/html-info/29273.htm.
[WiMAX] WiMAX Forum, "WiMAX Release 1.5", http:// [WiMAX] WiMAX Forum, "WiMAX Release 1.5", http://
www.wimaxforum.org/resources/documents/technical/T33. www.wimaxforum.org/resources/documents/technical/T33.
10.2. Informative References 11.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. 9 change blocks. 
17 lines changed or deleted 42 lines changed or added

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