IETF Logo Mail Archive

[Last-Call] Artart last call review of draft-ietf-sipcore-multiple-reasons-01

Todd Herr via Datatracker <noreply@ietf.org> Tue, 04 October 2022 14:51 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: last-call@ietf.org
Delivered-To: last-call@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 887D8C14F745; Tue, 4 Oct 2022 07:51:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Todd Herr via Datatracker <noreply@ietf.org>
To: art@ietf.org
Cc: draft-ietf-sipcore-multiple-reasons.all@ietf.org, last-call@ietf.org, sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <166489506654.55126.364787661116985431@ietfa.amsl.com>
Reply-To: Todd Herr <todd.herr@valimail.com>
Date: Tue, 04 Oct 2022 07:51:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/hCaBY4TasfhxiVM_dtNpRW2FjrA>
Subject: [Last-Call] Artart last call review of draft-ietf-sipcore-multiple-reasons-01
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Oct 2022 14:51:06 -0000

Reviewer: Todd Herr
Review result: Ready with Nits

As someone unfamiliar with SIP Reason Header Fields, I'm of the opinion that
perhaps an example of a header field with multiple values might be instructive
as a contrast to the examples shown in RFC 3326, but I do not feel strongly
enough about this to hold up the document.

v2.23.0 | Report a Bug | By Email