Re: [Asap] Robert Wilton's No Objection on draft-ietf-asap-siptrunkingcapability-link-03: (with COMMENT)

["Derek Engi (deengi)" <[e-mail]>]

Hi Rob, thanks for the review. Here are our comments:

>> is I-D.ietf-asap-sip-auto-peer just an example of what might be
>> found using 'sip-trunking-capability' or is it the only capability document
>>that would expect to be found at that location?

The sip-auto-peer document defines a method to automatically setup peering between a provider and a customer network via a published capability set. This draft simply defines the link relation that would facilitate such communication.

>> (a) Informational rather than Standards Track
>> (b) ietf-asap-sip-auto-peer is only an informative reference
rather than a normative reference

Originally, we had this draft in the standards track, but after discussion with the working group chair we decided on decoupling the link type registration from the capability set definition itself. We foresee other use cases for the link relation not necessarily defined in the capability set documentation and think that any normative information should be defined in the implementation documents rather than this draft, which is more informational.

>> (c) This as a separate document to ietf-asap-sip-auto-peer
Yes, this decision was the result of discussion in the working group where it was thought best to disassociate the link relation registration from capability set definition and implementation specification.

Thanks again for the support and feedback.
Derek
--
Derek Engi
[e-mail]


From: Robert Wilton via Datatracker <[e-mail]>
Date: Wednesday, April 12, 2023 at 6:40 AM
To: The IESG <[e-mail]>
Cc: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: Robert Wilton's No Objection on draft-ietf-asap-siptrunkingcapability-link-03: (with COMMENT)
Robert Wilton has entered the following ballot position for
draft-ietf-asap-siptrunkingcapability-link-03: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-asap-siptrunkingcapability-link/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

Thanks for this short document.

>From reading this document, it wasn't clear to me as to what the exact
relationship is between this document and I-D.ietf-asap-sip-auto-peer.
Specifically, is I-D.ietf-asap-sip-auto-peer just an example of what might be
found using 'sip-trunking-capability' or is it the only capability document
that would expect to be found at that location?  Based on the answer to this
question, it might be helpful for the text in section 4 to be more proscriptive
of the relationship, and perhaps check that the text is section 1 and 2 also
describes this clearly.

In terms of document process, I was slightly surprised to see:
(a) this as Informational rather than Standards Track - I guess that
Informational is sufficient, but Standards Track may have been clearer to a
reader; (b) that ietf-asap-sip-auto-peer is only an informative reference
rather than a normative reference (which goes back to my original question
above); (c) this as a separate document to ietf-asap-sip-auto-peer, which also
goes back to my original question above.

Regards,
Rob