Re: [Asap] Publication has been requested for draft-ietf-asap-siptrunkingcapability-link-02

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

Hi Murray, thanks again for the feedback. We have uploaded a new draft of the document:

https://datatracker.ietf.org/doc/html/draft-ietf-asap-siptrunkingcapability-link-03

We had previously linked the SIP Auto Peer draft when defining the need for the capability set, but we think it adds value per your comment to include the link in the introduction when first referencing the capability set document. We have also included the reference to SIP in the same section, as well as updated some acknowledgements for the folks who have helped us along the way.

Let us know if there is anything else we can provide, cheers!
Derek

--
Derek Engi
[e-mail]


From: Murray S. Kucherawy <[e-mail]>
Date: Tuesday, March 7, 2023 at 12:30 AM
To: Derek Engi (deengi) <[e-mail]>
Cc: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: Re: [Asap] Publication has been requested for draft-ietf-asap-siptrunkingcapability-link-02
Hi,

I think one of your early non-Abstract references to "capability set" should include a direct reference to I-D.ietf-asap-sip-auto-peer just so the reader knows where to go looking.  Leaving it for just the References section isn't as direct as people probably expect it to be.

Yes, please submit a new version with the minor changes, and I'll request Last Call when I see it.

-MSK

On Fri, Mar 3, 2023 at 7:30 AM Derek Engi (deengi) <[e-mail]<mailto:[e-mail]>> wrote:
Hi Murray, thank you for your review and the feedback. I’ve put our responses inline below.

One question: In preparation for IESG review, should we publish a new version of this draft? At this point we have only two minor edits in the queue (updating acknowledgments & adding reference to SIP).

Thanks,
Derek

--
Derek Engi
[e-mail]<mailto:[e-mail]>


From: Asap <[e-mail]<mailto:[e-mail]>> on behalf of Murray S. Kucherawy <[e-mail]<mailto:[e-mail]>>
Date: Monday, February 27, 2023 at 4:03 AM
To: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Asap] Publication has been requested for draft-ietf-asap-siptrunkingcapability-link-02
Hi, thanks for sending this along.  Just a couple of questions:

Where is the layout of a capability set document specified?  If as a client I am going to request one, I should know how to parse and apply the answer.

<DE> The capability set document is defined in the ASAP draft (https://datatracker.ietf.org/doc/html/draft-ietf-asap-sip-auto-peer) that we have referenced informatively. This draft simply registers with IANA the link relation that document (and potentially others in the future) makes use of.

Also, I think this should include at least an informative reference to SIP itself.

<DE> Agreed, we'll include an inline reference to RFC3261.

-MSK

On Sat, Feb 18, 2023 at 10:50 AM Jean Mahoney via Datatracker <[e-mail]<mailto:[e-mail]>> wrote:
Jean Mahoney has requested publication of draft-ietf-asap-siptrunkingcapability-link-02 as Informational on behalf of the ASAP working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-asap-siptrunkingcapability-link/