Re: [sipcore] SIPCORE Location Conveyance -00 submitted

"Elwell, John" <john.elwell@siemens-enterprise.com> Thu, 02 July 2009 18:10 UTC

Return-Path: <john.elwell@siemens-enterprise.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 812BC3A6DC1 for <sipcore@core3.amsl.com>; Thu, 2 Jul 2009 11:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level:
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599]
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 l1+++Y0WZz9U for <sipcore@core3.amsl.com>; Thu, 2 Jul 2009 11:10:41 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 04D4528C0E0 for <sipcore@ietf.org>; Thu, 2 Jul 2009 11:10:41 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([172.23.15.171]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KM60094L2IF9J@siemenscomms.co.uk> for sipcore@ietf.org; Thu, 02 Jul 2009 19:11:03 +0100 (BST)
Date: Thu, 02 Jul 2009 19:11:03 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
In-reply-to: <XFE-SJC-212zRL25AEx00004ba7@xfe-sjc-212.amer.cisco.com>
To: "James M. Polk" <jmpolk@cisco.com>, sipcore@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D00218C334@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: quoted-printable
Thread-Topic: [sipcore] SIPCORE Location Conveyance -00 submitted
Thread-Index: Acn7OncpPDgdPzwtTfi8wTc31SN8GQABbMjg
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <XFE-SJC-2126pkNzPZr0000321d@xfe-sjc-212.amer.cisco.com> <0D5F89FAC29E2C41B98A6A762007F5D00218BF89@GBNTHT12009MSX.gb002.siemens.net> <XFE-SJC-212zRL25AEx00004ba7@xfe-sjc-212.amer.cisco.com>
Subject: Re: [sipcore] SIPCORE Location Conveyance -00 submitted
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: Thu, 02 Jul 2009 18:10:42 -0000

 

> -----Original Message-----
> From: James M. Polk [mailto:jmpolk@cisco.com] 
> Sent: 02 July 2009 18:28
> To: Elwell, John; sipcore@ietf.org
> Subject: RE: [sipcore] SIPCORE Location Conveyance -00 submitted
> 
> At 04:50 AM 7/2/2009, Elwell, John wrote:
> > > - I toned down the 2119 text for servers inserting location into a
> > > request from SHOULD NOT to not RECOMMENDED, based on WG comment.
> >[JRE] Why does this constitute a toning down? I though SHOULD NOT and
> >NOT RECOMMENDED were the same in RFC 2119. Can somebody 
> please explain
> >the subtle distinction?
> 
> I thought (think?) (NOT) RECOMMENDED doesn't need to be implemented, 
> and SHOULD (NOT) does, for PS to DS movement.
[JRE] RFC 2119 states:
"4. SHOULD NOT   This phrase, or the phrase "NOT RECOMMENDED" mean that
   there may exist valid reasons in particular circumstances when the
   particular behavior is acceptable or even useful, but the full
   implications should be understood and the case carefully weighed
   before implementing any behavior described with this label."

Therefore they mean the same thing.

> 
> I can change the text to "inadvisable"  otherwise
[JRE] If you want to tone it down, you would indeed need to use
non-normative text. But it depends what the WG wants - I don't have an
opinion.

John



> 
> 
> >John
> >
> 
>