Automatic Peering for SIP Trunks
draft-kinamdar-dispatch-sip-auto-peer-04
ASAP K. Inamdar
Internet-Draft S. Narayanan
Intended status: Standards Track C. Jennings
Expires: April 24, 2021 Cisco Systems
October 21, 2020
Automatic Peering for SIP Trunks
draft-kinamdar-dispatch-sip-auto-peer-04
Abstract
This draft specifies a configuration workflow to enable enterprise
Session Initiation Protocol (SIP) networks to solicit the capability
set of a SIP service provider network. The capability set can
subsequently be used to configure features and services on the
enterprise edge element, such as a Session Border Controller (SBC),
to ensure smooth peering between enterprise and service provider
networks.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 24, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Inamdar, et al. Expires April 24, 2021 [Page 1]
Internet-Draft SIP Auto Peer October 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3
3. Reference Architecture . . . . . . . . . . . . . . . . . . . 3
4. Configuration Workflow . . . . . . . . . . . . . . . . . . . 5
5. Overview of Operations . . . . . . . . . . . . . . . . . . . 6
6. HTTP Transport . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. HTTP Methods . . . . . . . . . . . . . . . . . . . . . . 7
6.2. Integrity and Confidentiality . . . . . . . . . . . . . . 7
6.3. Authenticated Client Identity . . . . . . . . . . . . . . 7
6.4. Encoding the Request . . . . . . . . . . . . . . . . . . 8
6.5. Generating the response . . . . . . . . . . . . . . . . . 8
6.6. Identifying the Request Target . . . . . . . . . . . . . 8
7. State Deltas . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Encoding the Service Provider Capability Set . . . . . . . . 9
9. Data Model for Capability Set . . . . . . . . . . . . . . . . 9
9.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 9
9.2. YANG Model . . . . . . . . . . . . . . . . . . . . . . . 11
9.3. Node Definitions . . . . . . . . . . . . . . . . . . . . 17
9.4. Extending the Capability Set . . . . . . . . . . . . . . 24
10. Example Capability Set Document Encoding . . . . . . . . . . 25
10.1. XML Capability Set Document . . . . . . . . . . . . . . 25
11. Example Exchange . . . . . . . . . . . . . . . . . . . . . . 27
12. Security Considerations . . . . . . . . . . . . . . . . . . . 27
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
13.1. Normative References . . . . . . . . . . . . . . . . . . 28
13.2. Informative References . . . . . . . . . . . . . . . . . 28
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction
The deployment of a Session Initiation Protocol (SIP)-based
infrastructure in enterprise and service provider communication
networks is increasing at a rapid pace. Consequently, direct IP
peering between enterprise and service provider networks is quickly
replacing traditional methods of interconnection between enterprise
and service provider networks. Currently published standards provide
a strong foundation over which direct IP peering can be realized.
Show full document text