[Gen-art] Genart last call review of draft-ietf-sipcore-sip-push-21

Stewart Bryant <stewart.bryant@gmail.com> Wed, 19 December 2018 15:49 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 562FD129508; Wed, 19 Dec 2018 07:49:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Cc: sipcore@ietf.org, ietf@ietf.org, draft-ietf-sipcore-sip-push.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154523455825.2864.6694264562010996848@ietfa.amsl.com>
Date: Wed, 19 Dec 2018 07:49:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Vk4JNDzhue5Bbm4vQ2uS-saGFWM>
Subject: [Gen-art] Genart last call review of draft-ietf-sipcore-sip-push-21
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2018 15:49:19 -0000

Reviewer: Stewart Bryant
Review result: Ready with Nits

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-sipcore-sip-push-21
Reviewer: Stewart Bryant
Review Date: 2018-12-19
IETF LC End Date: 2018-12-21
IESG Telechat date: Not scheduled for a telechat

Summary: A well written document with some minor points that could use a little

Major issues: None

Minor issues:

In Figure 1 the following is included:

     REGISTER sip:alice@example.com SIP/2.0
     Via: SIP/2.0/TCP alicemobile.example.com:5060;branch=z9hG4bKnashds7
     Max-Forwards: 70
     To: Alice <sip:alice@example.com>
     From: Alice <sip:alice@example.com>;tag=456248
     Call-ID: 843817637684230@998sdasdh09
     CSeq: 1826 REGISTER
     Contact: <sip:alice@alicemobile.example.com;
     Expires: 7200
     Content-Length: 0

SB> However I don't at this stage of the text see the relationship between the
packet flow digram and the text that follows.

   Contact: IESG (iesg@ietf.org)

SB> Is the whole IESG the most appropriate first point of contact?


Nits/editorial comments:
Presumably the references to RFC XXXX will be replaced by RFC <this RFC> but
that does not seem to be noted in the text


   As dicussed in [RFC4320] and [RFC4321], non-INVITE transactions must
SB> Typo s/dicussed/discussed/


   Example: pn-prid = 00fc13adff78512

   For more information about the APNs Topic and device token:

SB> Is the following part of the example? If so it could usefully be delimited
as SB>  such, otherwise, I don't understand why it is not a normal document
 SB> reference.


SB> Similarly in the following section