* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Asap Status Pages

Automatic SIP trunking And Peering (Active WG)
Art Area: Barry Leiba, Murray Kucherawy | 2020-Jul-24 —  
Chairs
 
 


2020-07-24 charter

Automatic SIP trunking And Peering (asap)
-----------------------------------------

 Charter

 Current Status: Active

 Chairs:
     Adam Roach <adam@nostrum.com>
     Gonzalo Salgueiro <gsalguei@cisco.com>

 Applications and Real-Time Area Directors:
     Murray Kucherawy <superuser@gmail.com>
     Barry Leiba <barryleiba@computer.org>

 Applications and Real-Time Area Advisor:
     Murray Kucherawy <superuser@gmail.com>

 Mailing Lists:
     General Discussion: asap@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/asap
     Archive:            https://mailarchive.ietf.org/arch/browse/asap/

Description of Working Group:

  The deployment of a Session Initiation Protocol (SIP)-based infrastructure in enterprise and service provider communication networks has been gradually increasing over the last few years. Consequently, direct IP peering between enterprise and service provider networks is replacing traditional methods of interconnection between these networks, such as analog lines and time-division multiplexing (TDM)-based digital circuits.

  Currently published standards provide a strong foundation over which direct IP peering can be realized. However, given the sheer number of these standards, it is often unclear which behavioural subsets, extensions to baseline protocols and operating principles ought to be configured by the enterprise network administrator to ensure successful IP peering with a SIP service provider network. This lack of context often leads to interoperability issues between enterprise and service provider SIP networks. As a result, a significant amount of time is spent by enterprise network administrators in troubleshooting these interoperability issues individually or with enterprise equipment manufacturer and service provider support teams. Consequently, there is an increase in the time taken to deploy SIP trunking between enterprise and service provider networks.

  The ASAP working group will define a descriptive capability set, which is populated by a SIP service provider, and which, when communicated to an enterprise network, encapsulates sufficient information to set up SIP trunking with the service provider network. In addition to defining a descriptive capability set, the ASAP working group will define a data model for the capability set, a service discovery mechanism and a transport mechanism for the capability set. The aforementioned deliverables of the ASAP working group are collectively referred to as “SIP Auto Peer”.

  The scope of the ASAP working group is:

  * A capability set that encapsulates sufficient information to ensure smooth IP peering between enterprise and service provider SIP networks.

  * A data model for the capability set.

  * An HTTPS-based transport mechanism for the capability set.

  * A mechanism to discover the server(s) in the SIP service provider network that hosts the capability set.

  * A mechanism to extend the data model to allow the encoding of proprietary parameters.

  The following are out of scope:

  * Extensions to SIP that enable an enterprise network to solicit and obtain a descriptive capability set from a SIP service provider.

  * A workflow/mechanism that allows service providers to directly configure devices in the enterprise network.

  The group will produce:

  * Specification for SIP Auto Peer

  This group will co-ordinate with the SIPCORE working group and the SIPConnect efforts carried out by the SIP Forum.


Goals and Milestones:
  Jun 2021 - SIP Automatic Peering specification submitted for publication to the IESG.


All charter page changes, including changes to draft-list, rfc-list and milestones:



Generated from PyHt script /wg/asap/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -