A new Request for Comments is now available in online RFC libraries.

        RFC 10006

        Title:      Automatic SIP Trunking and Peering
        Author:     K. Inamdar,
                    S. Narayanan,
                    C. Jennings
        Status:     Proposed Standard
        Stream:     IETF
        Date:       August 2026
        Mailbox:    [email protected],
                    [email protected],
                    [email protected]
        Pages:      43


        I-D Tag:    draft-ietf-asap-sip-auto-peer-41

        URL:        https://www.rfc-editor.org/info/rfc10006

        DOI:        10.17487/RFC10006

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.

This document is a product of the Automatic SIP trunking And Peering Working 
Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org

Reply via email to