Last Call Review of draft-ietf-sipcore-originating-cdiv-parameter-05
review-ietf-sipcore-originating-cdiv-parameter-05-opsdir-lc-liu-2018-10-27-00

Request Review of draft-ietf-sipcore-originating-cdiv-parameter
Requested rev. no specific revision (document currently at 08)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2018-10-26
Requested 2018-10-12
Other Reviews Secdir Last Call review of -05 by Kyle Rose (diff)
Genart Last Call review of -05 by Vijay Gurbani (diff)
Review State Completed
Reviewer Will LIU
Review review-ietf-sipcore-originating-cdiv-parameter-05-opsdir-lc-liu-2018-10-27
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/hERSkm_2ipE9csh4YNO51I4j_2M
Reviewed rev. 05 (document currently at 08)
Review result Ready
Draft last updated 2018-10-27
Review completed: 2018-10-27

Review
review-ietf-sipcore-originating-cdiv-parameter-05-opsdir-lc-liu-2018-10-27

Hi all,

I have reviewed draft-ietf-sipcore-originating-cdiv-parameter-05 as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments.

“The P-Served-User header field is used to convey the identity of the
   served user and the session case that applies to this particular
   communication session and application invocation.  This document
   updates RFC5502 by defining a new P-Served-User header field
   parameter, "orig-cdiv".  The parameter conveys the session case used
   by a proxy when handling an originating session after Call Diversion
   (CDIV) services have been invoked for the served user.  This document
   also fixes the ABNF in RFC 5502 and provides more guidance for using
   the P-Served-User header field in IP networks.”

My overall view of the document is 'Ready' for publication.


** Technical **

No. (As a new reviewer to SIP)

** Editorial **

As noted by author,   [RFCXXXX↓] need to be replaced with the RFC number of this document.


Regards,
Will (Shucheng LIU)