RFC 10006: Automatic SIP Trunking and Peering
In plain English — editorial summary, not part of the RFC
This document specifies a framework that enables enterprise telephony Session Initiation Protocol (SIP) networks to solicit and obtain a capability set document from a SIP service provider. The capability set document encodes a set of characteristics that enable easy peering between enterprise and service provider SIP networks.
Document record
- Document ID
- RFC10006
- Published
- August 2026
- Authors
- K. Inamdar; S. Narayanan; C. Jennings
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 43
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9970Connected Identity for Secure Telephone Identity Revisited (STIR)Current
June 2026
- RFC 9888Out-of-Band Secure Telephone Identity Revisited (STIR) for Service ProvidersCurrent
June 2026
- RFC 9475Messaging Use Cases and Extensions for Secure Telephone Identity Revisited (STIR)Current
December 2023
- RFC 9409The 'sip-trunking-capability' Link Relation TypeCurrent
July 2023
- RFC 9060Secure Telephone Identity Revisited (STIR) Certificate DelegationCurrent
September 2021
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8862Best Practices for Securing RTP Media Signaled with SIPCurrent
January 2021
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?