RFC 9409: The 'sip-trunking-capability' Link Relation Type
In plain English — editorial summary, not part of the RFC
This Informational document defines the 'sip-trunking-capability' link relation type that may be used by an enterprise telephony Session Initiation Protocol (SIP) network to retrieve a SIP trunking capability set document, which contains the capabilities and configuration requirements of an Internet Telephony Service Provider (ITSP). These technical requirements allow for seamless peering between SIP-based enterprise telephony networks and the ITSP.
Document record
- Document ID
- RFC9409
- Published
- July 2023
- Authors
- K. Inamdar; S. Narayanan; D. Engi; G. Salgueiro
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 7989End-to-End Session Identification in IP-Based Multimedia Communication NetworksCurrent
October 2016
- RFC 7702Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): GroupchatCurrent
December 2015
- RFC 7573Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat SessionsCurrent
June 2015
- RFC 5954Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261Current
August 2010
- RFC 4896Signaling Compression (SigComp) Corrections and ClarificationsCurrent
June 2007
- RFC 4479A Data Model for PresenceCurrent
July 2006
- RFC 3969The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)Updated
December 2004
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?