Automatic Peering for SIP Trunks
draft-kinamdar-dispatch-sip-audo-peer-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-09-11 | ||
| Replaced by | draft-kinamdar-dispatch-sip-auto-peer | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-kinamdar-dispatch-sip-auto-peer | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-kinamdar-dispatch-sip-audo-peer-00.txt
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.
Authors
Kaustubh Inamdar
(kinamdar@cisco.com)
Sreekanth Narayanan
(sreenara@cisco.com)
Cullen Jennings
(fluffy@iii.ca)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)