datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage
draft-ietf-dime-extended-naptr-09

RFC
Document Stream: IETF
Last updated: 2011-08-03
Replaces: draft-jones-dime-extended-naptr
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: Submitted to IESG for Publication (dime)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6408
IANA Action State: RFC-Ed-Ack 
Responsible AD: Dan Romascanu
IESG Note: Sebastien Decugis (sdecugis@freediameter.net) is the document shepherd.
Send notices to: dime-chairs@tools.ietf.org, draft-ietf-dime-extended-naptr@tools.ietf.org, sdecugis@freediameter.net

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-dime-extended-naptr.

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]

Authors:
Jouni Korhonen <jouni.nospam@gmail.com>
Lionel Morand <lionel.morand@orange-ftgroup.com>
Mark Jones <mark@azu.ca>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)