Opsdir last call review of draft-ietf-sipcore-callinfo-spam-04

Nagendra Kumar via Datatracker <noreply@ietf.org> Fri, 13 September 2019 02:04 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Nagendra Kumar via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-sipcore-callinfo-spam.all@ietf.org, sipcore@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-sipcore-callinfo-spam-04
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Nagendra Kumar <naikumar@cisco.com>
Message-ID: <156834028538.16481.16157896877930138059@ietfa.amsl.com>
Date: Thu, 12 Sep 2019 19:04:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mhFM3kFnAntHTTJAkCHjRbo-Wao>

Reviewer: Nagendra Kumar
Review result: Has Nits

Quick Summary:

The draft proposes new Call-Info Header fields to label the type/nature of the
call.

Overall the draft appears to be well written. There are some nits as defined in
the GenArt.  In addition to those nits, the below text in IANA section seems
incorrect and the order should be changed:

    +--------------+----------------+-------------------+------------+
    | Header Field | Parameter Name | Predefined Values | Reference  |
    +--------------+----------------+-------------------+------------+
    | [this RFC]   | Call-Info      | confidence        | No         |

I don't have any other concerns or comments in terms of the operational aspects
of this draft.

Thanks,
Nagendra

Opsdir last call review of draft-ietf-sipcore-cal… Nagendra Kumar via Datatracker