Automatic Peering for SIP Trunks
draft-kinamdar-dispatch-sip-audo-peer-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kaustubh Inamdar , Sreekanth Narayanan , Cullen Fluffy Jennings | ||
| Last updated | 2019-09-11 | ||
| Replaced by | draft-kinamdar-dispatch-sip-auto-peer | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Associated None milestone |
|
||
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-kinamdar-dispatch-sip-auto-peer | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Sreekanth Narayanan
Cullen Fluffy Jennings
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)