Skip to main content

Last Call Review of draft-ietf-asap-siptrunkingcapability-link-03

Request Review of draft-ietf-asap-siptrunkingcapability-link
Requested revision No specific revision (document currently at 05)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2023-03-22
Requested 2023-03-08
Authors Kaustubh Inamdar , Sreekanth Narayanan , Derek Engi , Gonzalo Salgueiro
I-D last updated 2023-03-18
Completed reviews Genart Last Call review of -03 by Dan Romascanu (diff)
Secdir Last Call review of -03 by Christopher A. Wood (diff)
Artart Last Call review of -03 by Tim Bray (diff)
Opsdir Last Call review of -03 by Joe Clarke (diff)
Assignment Reviewer Dan Romascanu
State Completed
Review review-ietf-asap-siptrunkingcapability-link-03-genart-lc-romascanu-2023-03-18
Posted at
Reviewed revision 03 (document currently at 05)
Result Ready w/nits
Completed 2023-03-18
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-asap-siptrunkingcapability-link-03
Reviewer: Dan Romascanu
Review Date: 2023-03-18
IETF LC End Date: 2023-03-22
IESG Telechat date: Not scheduled for a telechat


This is a short and clear document describing the usage of the
'sip-trunking-capability' link relation type by an enterprise SIP network to
retrieve a SIP trunking capability set document containing the capabilities and
configuration requirements of an ITSP.

Major issues:

Minor issues:

Nits/editorial comments:

1. The description of the 'sip-trunking-capability' link relation by IANA does
not seem to be fully consistent with the scope of the document as defined in
Section 1.

In Section 1:

The capability set document
   [I-D.ietf-asap-sip-auto-peer] encapsulates a set of characteristics
   of an ITSP, which when retrieved by enterprise telephony network
   devices allows for automated establishment of SIP [RFC3261] trunking
   between the two telephony networks.

Description:  Refers to a capability set document that defines
      parameters or configuration requirements for automated peering and
      communication channel negotiation of the Session Initiation
      Protocol (SIP).

I would consider mentioning explicitly 'SIP trunking' in the Description of the
'sip-trunking-capability' link relation in the registry.

2. Should not  [I-D.ietf-asap-sip-auto-peer] be a Normative Reference?