RFC 6408: Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6408
- Published
- November 2011
- Authors
- M. Jones; J. Korhonen; L. Morand
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 14
- Also known as
- —
- Updates:
- RFC 3588
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6412Terminology for Benchmarking Link-State IGP Data-Plane Route ConvergenceCurrent
November 2011
- RFC 6413Benchmarking Methodology for Link-State IGP Data-Plane Route ConvergenceCurrent
November 2011
- RFC 6414Benchmarking Terminology for Protection PerformanceCurrent
November 2011
- RFC 6397Multi-Threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) Routing Information Export Format with Geo-Location ExtensionsCurrent
October 2011
- RFC 6396Multi-Threaded Routing Toolkit (MRT) Routing Information Export FormatCurrent
October 2011
- RFC 6390Guidelines for Considering New Performance Metric DevelopmentCurrent
October 2011
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 6441Time to Remove Filters for Previously Unallocated IPv4 /8sCurrent
November 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?