IETF Logo Mail Archive

Re: [dispatch] draft-allen-dispatch-poc-instanceid-usage-02

worley@ariadne.com (Dale R. Worley) Fri, 24 April 2015 02:32 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 047201A00F7 for <dispatch@ietfa.amsl.com>; Thu, 23 Apr 2015 19:32:12 -0700 (PDT)
X-Quarantine-ID: <HJZxK2uTn-VA>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "From"
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJZxK2uTn-VA for <dispatch@ietfa.amsl.com>; Thu, 23 Apr 2015 19:32:11 -0700 (PDT)
Received: from resqmta-po-07v.sys.comcast.net (resqmta-po-07v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:166]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2C11A0067 for <dispatch@ietf.org>; Thu, 23 Apr 2015 19:32:02 -0700 (PDT)
Received: from resomta-po-10v.sys.comcast.net ([96.114.154.234]) by resqmta-po-07v.sys.comcast.net with comcast id KeXg1q00553iAfU01eY2qo; Fri, 24 Apr 2015 02:32:02 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-10v.sys.comcast.net with comcast id KeY11q00S1KKtkw01eY2S5; Fri, 24 Apr 2015 02:32:02 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id t3O2W12F020277 for <dispatch@ietf.org>; Thu, 23 Apr 2015 22:32:01 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t3O2W1tI020274; Thu, 23 Apr 2015 22:32:01 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
From: worley@alum.mit.edu
To: dispatch@ietf.org
In-Reply-To: <9238BBB44BF24943AB06F370EBCC3E4C29A33474@ROCMXUS21.cs.myharris.net> (pmonnes@harris.com)
Sender: worley@ariadne.com
Date: Thu, 23 Apr 2015 22:32:00 -0400
Message-ID: <87r3ra2r4v.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1429842722; bh=I53YPYdDDxDrYd6B2RR9cONZuvipUbtpCzghjLfNEsE=; h=Received:Received:Received:Received:From:From:To:Subject:Date: Message-ID; b=tuNmcNqlji0pVX4nnmVaSKI1blukNbBg0vsvmbpHBjomQ9tF/cieHbbrYUwk7+5lp KGxKZ7R3Fdu6d+1DGaP9e/aEjEI64zOhIX2p3z50pGIGfBL4OGmiTgw0z8jcVXD1Re g9d2sc/xOxdqGzyURfUsq//OAhsqLyBiryIg4ZR2biX/waKzFow+mPjiX0ywrct0ud Z9RCHpFzFNKyjTQbAPPbyK3Io78458iPnQr4Q6ozmYcOd7sJWw/TTvqhkg5+MtWl6k ZyLUM271gJrDteak499TC+QocBPhPuzuaHhFvQyULPXTmm76GvYAFXUNbZvvaffewE cf2yaqi7hKJ+Q==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/wyGsewHJyer4gtmABhaBnGszWGY>
Subject: Re: [dispatch] draft-allen-dispatch-poc-instanceid-usage-02
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 02:32:12 -0000

"Monnes, Peter" <pmonnes@harris.com> writes:
> I've reviewed and support the publication of the Internet draft:
> "Session Initiation Protocol (SIP) Instance ID usage by the Open
> Mobile Alliance Push-to-talk over Cellular
> draft-allen-dispatch-poc-instanceid-usage-02".

The issues this draft addresses should be resolved.  (I haven't studied
the issues enough myself to know if this draft covers them properly, but
it appears to do so to the extent of my knowledge.)

The draft could use some editing.  In particular, section 2 references a
things that should be properly footnoted.  For example:

OMA PoC 1.0
OMA PoC 2.0
OMA PoC 3.0
Open Mobile Alliance [the URL is given inline, whereas a footnote would
be better]
"another update of the OMA PoC enabler for Push-To-Talk over 3GPP Long
Term Evolution (LTE) networks"
"OMA has defined an architecture..."

Also, the word "enabler" is used (also in the abstract), but not in a
standard way, so needs defining.

Dale

v2.23.0 | Report a Bug | By Email