%% You should probably cite rfc6408 instead of this I-D. @techreport{ietf-dime-extended-naptr-09, number = {draft-ietf-dime-extended-naptr-09}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-dime-extended-naptr/09/}, author = {Jouni Korhonen and Lionel Morand and Mark Jones}, title = {{Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage}}, pagetotal = 14, year = 2011, month = aug, day = 3, abstract = {The Diameter base protocol specifies mechanisms whereby a given realm may advertise Diameter nodes and the supported transport protocol. However, these mechanisms do not reveal the Diameter applications that each node supports. A peer outside the realm would have to perform a Diameter capability exchange with every node until it discovers one that supports the required application. This document updates RFC 3588, "Diameter Base Protocol", and describes an improvement using an extended format for the Straightforward-Naming Authority Pointer (S-NAPTR) application service tag that allows for discovery of the supported applications without doing Diameter capability exchange beforehand. {[}STANDARDS-TRACK{]}}, }