Re: [sipcore] WGLC: draft-ietf-sipcore-location-conveyance

"James M. Polk" <jmpolk@cisco.com> Tue, 29 March 2011 08:45 UTC

Return-Path: <jmpolk@cisco.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 B32C93A69FC for <sipcore@core3.amsl.com>; Tue, 29 Mar 2011 01:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 Sd+0zFJ2ylbK for <sipcore@core3.amsl.com>; Tue, 29 Mar 2011 01:45:39 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id A11483A68CE for <sipcore@ietf.org>; Tue, 29 Mar 2011 01:45:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1091; q=dns/txt; s=iport; t=1301388430; x=1302598030; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=cJb3bRyWGpnwMj0FixbBmMgEwvajOTpfJWRv9vthRFw=; b=GHKja/sno2L/uAIwhrsVqEEs1vy2Q1oR3QuM/uvMD9CztQWdU66R39Mi beuaN7Dnw/ssIc8yMymJJnvdWsQQgSWsdnJVOdbWoJBzqfMAR6TEox9t8 hPy8Ewc3xZ1+MKb9XUD1xNF3c6OmHtXWzYvKSPwk+VgolTyv5Yh9wfsV+ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAO2bkU2rRDoG/2dsb2JhbAClRnenTZxChWoEhTw
X-IronPort-AV: E=Sophos;i="4.63,260,1299456000"; d="scan'208";a="284736050"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 29 Mar 2011 08:47:10 +0000
Received: from jmpolk-wxp01.cisco.com ([10.89.8.40]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2T8l7uW032563; Tue, 29 Mar 2011 08:47:08 GMT
Message-Id: <201103290847.p2T8l7uW032563@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 29 Mar 2011 03:47:05 -0500
To: Robert Sparks <rjsparks@nostrum.com>, SIPCORE Chairs <sipcore-chairs@tools.ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <C7E060E7-9B2E-4FB3-9600-0A2B7776B403@nostrum.com>
References: <4D6C31DC.80005@nostrum.com> <C7E060E7-9B2E-4FB3-9600-0A2B7776B403@nostrum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: draft-ietf-sipcore-location-conveyance@tools.ietf.org, "SIPCORE (Session Initiation Protocol Core) WG" <sipcore@ietf.org>
Subject: Re: [sipcore] 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: Tue, 29 Mar 2011 08:45:42 -0000

At 03:45 PM 3/9/2011, Robert Sparks wrote:
>There are a couple of larger and several small things to also 
>address in this document before requesting publication.
>
>The larger things:
>
>3) I can't figure out what the paragraph in section 4.4 that starts 
>"Additionally, if a sip entity cannot..." and goes
>onto talk about 503's is trying to say. I think some surrounding 
>context must have been lost or not captured.
>Why would we be recommending sending a 503 here?

pick on this one point, there was an error code for that basically 
said "couldn't process the location you just sent me, but it's ok to 
try again" *and* "couldn't process the location you just sent me, 
don't try to resend it for a while". Jon didn't like the idea of 
something that he feels duplicates the 503 with a retry after header 
field. He was on a mission to reduce the number of geolocation-error 
codes, and these two go whacked. That's where this text comes from. 
I'll get with him about writing this section better - or do you have 
an alternate plan we should pursue?

James