Subject: Re: [dispatch] PROPOSED CHARTER FOR ASAP (Automatic SIP trunking And Peering)

From: Christer Holmberg <[email-masked]>
Date: Tue, 7 Jan 2020 16:53:30 +0000

Hi,

The suggested charter say that the scope includes defining a capability transport mechanism, but it also says that defining SIP extensions is outside the scope.

What is the reason for excluding possible SIP extensions in the scope? I do know that the there is a suggestion of using HTTP, but I don’t think that decision shall be made in the charter.

Regards,

Christer

From: dispatch <[email-masked]> on behalf of "Kaustubh Inamdar (kinamdar)" <[email-masked]>
Date: Monday, 6 January 2020 at 7.17
To: "[email-masked]" <[email-masked]>
Cc: Cullen Jennings <[email-masked]>, "[email-masked]" <[email-masked]>
Subject: Re: [dispatch] PROPOSED CHARTER FOR ASAP (Automatic SIP trunking And Peering)

Slight modification to the proposed charter…

PROPOSED CHARTER FOR ASAP (Automatic SIP trunking And Peering)

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. However, given the sheer number of these standards, it is often not clear which behavioural subsets, extensions to baseline protocols and operating principles ought to be configured by the enterprise network administrator to ensure successful peering with a SIP service provider network. This lack of context often leads to interoperability issues between enterprise and service provider SIP networks resulting in a large number of support cases being opened with enterprise equipment manufacturers and SIP service providers. Subsequently, deployment times for SIP trunking between enterprise and service provider networks increase significantly.

This work would define a descriptive capability set, which is populated by a SIP service provider, and which, when communicated to an enterprise network, provides the enterprise network with sufficient information to setup SIP trunking with the SIP service provider. Such a capability set would not only result in SIP trunking deployment times being drastically scaled down, but also would result in a significant decrease in interoperability issues between enterprise and service provider network. Additionally, operational costs for service providers and enterprise equipment manufactures would likely decrease as a result of fewer support cases.

The scope of activity includes:

·         Define a robust capability set which encapsulates sufficient information to ensure smooth IP peering between enterprise and service provider SIP networks.

·         Define a data model for the capability set.

·         Extensibility of the data model to allow proprietary parameters to be encoded.

·         A transport mechanism using which the capability set is communicated from the service provider network to the enterprise network.

This working group will not:

·         Define any extensions to SIP.

·         Provide a workflow/mechanism that allows service providers to directly configure devices in the enterprise network.

The group will produce

·         Requirements, Use Cases and Architecture draft.

·         Specification for SIP Auto Peer.

This workgroup will co-ordinate with the SIP Core workgroup and the SIPConnect efforts carried out by the SIP Forum.

Milestones:

<Date TBD> Send architecture draft to IESG

<Date TBD> Send protocol specification draft to IESG

Thanks,
Kaustubh

From: Kaustubh Inamdar <[email-masked]>
Date: Monday, 6 January 2020 at 07:12
To: "[email-masked]" <[email-masked]>
Cc: "[email-masked]" <[email-masked]>, Cullen Jennings <[email-masked]>
Subject: PROPOSED CHARTER FOR ASAP (Automatic SIP trunking And Peering)

All,
Following the presentation of SIP Auto Peer at IETF 106, Singapore (https://tools.ietf.org/html/draft-kinamdar-dispatch-sip-auto-peer-01) , there was consensus to form a mini workgroup to take this effort forward. To that end, we are looking to build consensus on a charter. The prosed charter can be found below. Comments, reviews, suggestions are welcome.

PRPOSED CHARTER FOR ASAP (Automatic SIP trunking And Peering)

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. However, given the sheer number of these standards, it is often not clear which behavioural subsets, extensions to baseline protocols and operating principles ought to be configured by the enterprise network administrator to ensure successful peering with a SIP service provider network. This lack of context often leads to interoperability issues between enterprise and service provider SIP networks resulting in a large number of support cases being opened with enterprise equipment manufacturers and SIP service providers. Subsequently, deployment times for SIP trunking between enterprise and service provider networks increase significantly.

This work would define a descriptive capability set, which is populated by a SIP service provider, and which, when communicated to an enterprise network, provides the enterprise network with sufficient information to setup SIP trunking with the SIP service provider. Such a capability set would not only result in SIP trunking deployment times being drastically scaled down, but also would result in a significant decrease in interoperability issues between enterprise and service provider network. Additionally, operational costs for service providers and enterprise equipment manufactures would likely decrease as a result of fewer support cases.

The scope of activity includes:

  *   Define a robust capability set which encapsulates sufficient information to ensure smooth IP peering between enterprise and service provider SIP networks.
  *   Define a data model for the capability set.
  *   Extensibility of the data model to allow proprietary parameters to be encoded.
  *   A transport mechanism using which the capability set is communicated from the service provider network to the enterprise network.

This working group will not:

  *   Define any extensions to SIP.
  *   Provide a workflow/mechanism that allows service providers to directly configure devices in the enterprise network.

The group will produce

  *   Requirements, Use Cases and Architecture draft.
  *   Specification for SIP Auto Peer.

Milestones:

<Date TBD> Send architecture draft to IESG

<Date TBD> Send protocol specification draft to IESG

Thanks,
Kaustubh