[sipcore] Additional editorial suggestions (was Re: WGLC: draft-ietf-sipcore-location-conveyance)

Robert Sparks <rjsparks@nostrum.com> Wed, 09 March 2011 21:45 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 65FC23A6AE0 for <sipcore@core3.amsl.com>; Wed, 9 Mar 2011 13:45:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level:
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nl8XuiWnDVGo for <sipcore@core3.amsl.com>; Wed, 9 Mar 2011 13:45:41 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 05B823A6AE3 for <sipcore@ietf.org>; Wed, 9 Mar 2011 13:45:38 -0800 (PST)
Received: from dn3-177.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p29LksQ5039235 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 9 Mar 2011 15:46:54 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <4D6C31DC.80005@nostrum.com>
Date: Wed, 09 Mar 2011 15:46:53 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E762DE9-87F6-4765-9E44-21EF5548662D@nostrum.com>
References: <4D6C31DC.80005@nostrum.com>
To: SIPCORE Chairs <sipcore-chairs@tools.ietf.org>
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "draft-ietf-sipcore-location-conveyance@tools.ietf.org" <draft-ietf-sipcore-location-conveyance@tools.ietf.org>, "SIPCORE (Session Initiation Protocol Core) WG" <sipcore@ietf.org>
Subject: [sipcore] Additional editorial suggestions (was Re: WGLC: draft-ietf-sipcore-location-conveyance)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2011 21:45:42 -0000

Hi document editors -

Here are a few additional suggestions that are purely editorial that I think would 
make the document stronger - please consider them, but its up to you whether to 
do anything with them.

a) I suggest "your favorite local pizza delivery service" instead of "Pizza Hut"

b) Replace 'The only conceivable way forward, when a second location is placed into
the same SIP request by a SIP intermediary is to take a "you break it, you bought it" philosophy
with respect to the inserting SIP intermediary' with 'This document takes a "you break it, you bought it"
approach to dealing with second locations placed into a SIP request by an intermediary entity.'

c) Delete the parenthetical '(we are not going to discuss any other reasons in this document, and
there are many)'. That's obvious and distracts from the point.

d) Replace 'SIP intermediaries are NOT RECOMMENDED to modify existing locationValue(s),
and further not to delete any either' with 'SIP intermediaries SHOULD NOT modify or remove any
existing locationValue(s).'

e) Replace the first sentence of the paragraph at the end of page 10 with
'A Geolocation-Routing header-value that is set to "no" has no special security properties. It is
at most a request for behavior within SIP intermediaries.'

f) Replace 'SIP intermediaries MUST NOT add, modify or delete the location in a 424 response.'
with 'SIP intermediaries that are forwarding (as opposed to generating) a 424 response MUST
NOT add, modify, or delete any location appearing in that response.'

g) Delete the '- etc...' bullet in the non-exclusive list of reasons for 1XX in section 4.4
 
h) Delete 'At this time,' in the paragraph after that list. This document won''t alter things at
any other time either. 

i) Replace "This was first brought up in section 3.2." with "The end of section 3.2 discusses
how transaction timing considerations lead to this requirement."


RjS



On Feb 28, 2011, at 5:38 PM, Adam Roach - SIPCORE Chair wrote:

> [as chair]
> 
> The current editor of draft-ietf-sipcore-location-conveyance believes that the document has no remaining technical issues[1], and is ready for evaluation. Today, we are starting a two-week working group last call period. This last call period ends on Tuesday, March 15th.
> 
> The latest version of the document can be retrieved here:
> 
> http://tools.ietf.org/html/draft-ietf-sipcore-location-conveyance
> 
> Any comments on the document should be sent to the SIPCORE mailing list.
> 
> /a
> 
> [1] John Elwell's editorial comments of February 25th have been noted by the authors, and will be treated as WGLC comments.