Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-07.txt

Adam Roach <adam@nostrum.com> Fri, 15 March 2019 18:27 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29FC2130E70 for <sipcore@ietfa.amsl.com>; Fri, 15 Mar 2019 11:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 bEgKmINtQZRu for <sipcore@ietfa.amsl.com>; Fri, 15 Mar 2019 11:27:31 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B54FD130ED0 for <sipcore@ietf.org>; Fri, 15 Mar 2019 11:27:31 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x2FIRRSo007899 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 15 Mar 2019 13:27:28 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1552674448; bh=3bCef/FBkTS573hIAliCRGuSPVB/X28/4+GSqOfnHz4=; h=Subject:To:References:From:Date:In-Reply-To; b=cNDXqbguwXSKmIR2FvMHjQJ9qyvnzVw+S0m1BFWlOPM96wY4f9Ie1y1NS6JJQSHkb 6jDEfP6v/DQ6Cd4QnMoPZGZicTL/9BG+WUlKEepB+R715KuE7i+TuZxAsngm7Bn1Gg yCvuYEcxv42MJm5NbU7HmTeTk/WELHi54M1Wgs6o=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, sipcore@ietf.org
References: <155267314057.22026.2988782249297748458@ietfa.amsl.com> <19111e0e-50fa-13fe-5639-8f8f2389acee@alum.mit.edu>
From: Adam Roach <adam@nostrum.com>
Message-ID: <041b7d55-21bc-0d82-1bec-c69ac7a63e9a@nostrum.com>
Date: Fri, 15 Mar 2019 13:27:22 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <19111e0e-50fa-13fe-5639-8f8f2389acee@alum.mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/prnWbAIuyR7NQUbpZVeycNhJbMI>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-07.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Fri, 15 Mar 2019 18:27:33 -0000

On 3/15/19 1:22 PM, Paul Kyzivat wrote:
> Is there a reason why isup-location-value is case sensitive? Most 
> stuff in sip is not. 


The initial draft was ambiguous, although the use of all-caps implied 
(to me, at least) an intention for case-sensitivity. I don't care how 
it's resolved, but it can't be ambiguous. It may well be that 
case-insensitivity is the right choice here.

(I note that we didn't try to use mnemonic tokens for cause-code; I 
suspect we could have simply defined location as an integer -- but I get 
the impression that we have implementations in the field already, so 
it's probably too late to make such a change.)

/a