RFC 7403: A Media-Based Traceroute Function for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
SIP already provides the ability to perform hop-by-hop traceroute for SIP messages using the Max-Forwards header field to determine the reachability path of requests to a target. A mechanism for media-loopback calls has also been defined separately, which enables test calls to be generated that result in media being looped back to the originator. This document describes a means of performing hop-by-hop traceroute-style test calls using the media-loopback mechanism to test the media path when SIP sessions go through media-relaying back-to-back user agents (B2BUAs).
Document record
- Document ID
- RFC7403
- Published
- November 2014
- Authors
- H. Kaplan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 7
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7406Extensions to the Emergency Services Architecture for Dealing With Unauthenticated and Unauthorized DevicesCurrent
December 2014
- RFC 7410A Property Types Registry for the Authentication-Results Header FieldObsoleted
December 2014
- RFC 7396JSON Merge PatchCurrent
October 2014
- RFC 7395An Extensible Messaging and Presence Protocol (XMPP) Subprotocol for WebSocketCurrent
October 2014
- RFC 7386JSON Merge PatchObsoleted
October 2014
- RFC 7380RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG2 Transport Stream (TS) Program Specific Information (PSI) Decodability Statistics Metrics ReportingCurrent
November 2014
- RFC 7378Trustworthy LocationCurrent
December 2014
- RFC 7377IMAP4 Multimailbox SEARCH ExtensionCurrent
October 2014
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?