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

["Eric Vyncke (evyncke)" <[e-mail]>]

Thank you, Derek, for your reply.

I still think that the point in 1) (whether "enterprise" is a well-defined term) would benefit by having a different text for clarity, but this is cosmetic and non-blocking of course.

Regards;

-éric


From: "Derek Engi (deengi)" <[e-mail]>
Date: Tuesday, 11 April 2023 at 15:48
To: Eric Vyncke <[e-mail]>, The IESG <[e-mail]>
Cc: "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: Re: Éric Vyncke's No Objection on draft-ietf-asap-siptrunkingcapability-link-03: (with COMMENT)

Hi Éric, thanks for taking to the time to review. Here are our responses to your comments:

>> 1) is "an enterprise telephony SIP" defined and accepted in the SIP community ?
>> (I refer here to "enterprise"

After a chat with the rest of the authors, Enterprise SIP telephony network refers to an enterprise network interconnecting with their service providers (ITSPs) over a SIP trunk. The enterprise network internally can potentially use a bunch of telephony protocols, however, the signaling with the service provider is SIP. In the context of SIP trunking, we believe this is well understood.

>> 2) the abstract starts with "This specification defines", is an informational
>> document a specification ?

Fair point, we will update this to “This informational document”. This was carry over from before we made the switch to the informational track.

>> 3) s/https://capserver.ssp1.com/capserver/capdoc.json/https://capserver.ssp1.example.com/capserver/capdoc.json/

Agreed, we received another call out on this inconsistency and will make sure there is parity in the link relation draft and the ASAP draft that defines the capability set document.

Thanks again for the feedback and the support.
Derek

--
Derek Engi
[e-mail]


From: Éric Vyncke via Datatracker <[e-mail]>
Date: Friday, April 7, 2023 at 5:55 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: Éric Vyncke's No Objection on draft-ietf-asap-siptrunkingcapability-link-03: (with COMMENT)
Éric Vyncke 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:
----------------------------------------------------------------------

Thanks for the work done in this document.

Some comments though:

1) is "an enterprise telephony SIP" defined and accepted in the SIP community ?
(I refer here to "enterprise"

2) the abstract starts with "This specification defines", is an informational
document a specification ?

3)
s/https://capserver.ssp1.com/capserver/capdoc.json/https://capserver.ssp1.example.com/capserver/capdoc.json/

Hope this helps to improve the document,

Regards

-éric