Subject: [Asap] ASAP new version

From: "Kaustubh Inamdar (kinamdar)" <[email-masked]>
Date: Mon, 7 Jun 2021 14:53:06 +0000

Hi All,

A new version of the draft has been published (https://datatracker.ietf.org/doc/draft-ietf-asap-sip-auto-peer/) Major edits include:

1. A section on Webfinger for auto discovery of the capability set resource hosted by the SIP service provider. A generic WebFinger query to the domain name of the SIP service provider network would likely return a link array in the response with several resources. Additionally, it might not be readily apparent as to which resource URL corresponds to the capability set document. In order to streamline the query/response exchange, it might make sense for us to define a new link relation type that is specific to this effort. Please refer to section 4.5 of the current document.

2. A container in the YANG model that has nodes specific to STIR. More succinctly, we have added parameters that communicate the following:

    a) Is SIP service provider that the enterprise peers with, STIR compliant.

    b) Is the SIP service provider willing to delegate authority over a set of telephone numbers.

    C) The ACME directory URL to obtain delegate certificates.

NOTE: We make the assumption that the ACME account has been pre-authorised and as a consequence, the ACME client (enterprise edge element) would not be required to fulfil a challenge, such as acquiring and presenting an ATC token.

Thoughts/observations on the STIR section are welcome.

Also, it might be useful to have the SIP service provider being capable of providing a capability set document that is applicable at a future date. However, perhaps, providing multiple capability sets in a document might not be the cleanest approach. The following approaches might be more tenable -

A) Use WebFinger to find out if an new capability set document is available.

B) Enhance the YANG model to include elements that accommodate the specifics of a future applicable version of the capability set document. For example:

  <revision>

     <notBefore>Some_future_date</notBefore>

     <location>URL to fetch future version</location>

   </revision>

Option B above might be cleaner as it removes any dependencies on WebFinger.

--Kaustubh