[Gen-art] Review of draft-holmberg-dispatch-mcptt-rp-namespace-03

Fernando Gont <fgont@si6networks.com> Fri, 16 December 2016 21:46 UTC

Return-Path: <fgont@si6networks.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 E7B74128BA2; Fri, 16 Dec 2016 13:46:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Fernando Gont <fgont@si6networks.com>
To: gen-art@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148192479491.14716.7292445992537423386.idtracker@ietfa.amsl.com>
Date: Fri, 16 Dec 2016 13:46:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/hmccpu4Gugc_zWD8sUSJ07f_vEM>
Cc: ietf@ietf.org, draft-holmberg-dispatch-mcptt-rp-namespace.all@ietf.org
Subject: [Gen-art] Review of draft-holmberg-dispatch-mcptt-rp-namespace-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 16 Dec 2016 21:46:35 -0000

Reviewer: Fernando Gont
Review result: Ready with Nits

** Technical **

* Section 3, pages 3-4:
>    Intended algorithm for mcpttq is queuing.
> 
>    New Warning code: No.
> 
>    New SIP response code: No.

Is this kind of thing really needed/required in the registry?



** Editorial **

* Section 1, page 2:
>    The third generation partnership project (3GPP)

May be you should capitalize these? (i.e., "Third Generation...")


* Section 1, page 2:
> In addition to this a commercial PTT
>    service for non-professional use (e.g., groups of people on
holiday)

Please insert a comma after "this".


* Section 1, page 3:
> MCPTT data transfer currently under development can
>    benefit from a queueing mechanism.

"data transfer..." protocols?


* Section 2, page 3:
> The use of this namespace outside such network is
>    undefined.

s/network/networks/


* Section 5, page 5:
> 5.  IANA Considerations
> 
>    Abiding by the rules established within [RFC4412] and [RFC7134],
this
>    is an Informative RFC registering two new namespaces, their
>    associated priority-values, and intended algorithms.

s/registering/creating/ ?