Re: [Gen-art] Gen-art LC review of draft-saintandre-impp-call-info-02

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Tue, 07 May 2013 15:36 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 206BF21F84F8 for <gen-art@ietfa.amsl.com>; Tue, 7 May 2013 08:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTlf5gKlbDPB for <gen-art@ietfa.amsl.com>; Tue, 7 May 2013 08:35:53 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6159621F84D9 for <gen-art@ietf.org>; Tue, 7 May 2013 08:35:53 -0700 (PDT)
X-AuditID: c1b4fb30-b7f3a6d0000007a4-dd-51891f58cc7a
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 94.9F.01956.85F19815; Tue, 7 May 2013 17:35:52 +0200 (CEST)
Received: from [131.160.126.23] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.279.1; Tue, 7 May 2013 17:35:51 +0200
Message-ID: <51891F56.9000306@ericsson.com>
Date: Tue, 07 May 2013 18:35:50 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
References: <5176EB42.3030501@dial.pipex.com> <BD017FC5-EE95-4ED6-9B52-2AAFA8ADDDD2@cisco.com> <51796EC8.3090508@nostrum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134A0221@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1134A0221@xmb-aln-x02.cisco.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyM+JvrW6EfGegwZJ1QhZ7/i5it3h56BGj xbbjghYdk9ksrr76zGLxrmcZq8XeW7+ZLVZsOMBqcW95C5sDp8ff9x+YPKb83sjqcXzFTnaP nbPusnssWfKTyeP5wWusHrN2PmHx+HL5M1sARxSXTUpqTmZZapG+XQJXxuVNU1gKXglWTLgp 0MC4mq+LkZNDQsBEYs26PkYIW0ziwr31bF2MXBxCAqcYJeY/ucgCkhASWM0o8eqrM4jNK6At cfv9I6A4BweLgIrEtde6IGE2AQuJLbfug5WLCkRJ/Hu7mxGiXFDi5MwnYHERAUOJpj3zmEDm MwusZJZ4/24/I8gcYQEXiadfjSFW7WOUWP3JCsTmFPCVuNDykQniNkmJRdM6weYwC+hJTLna wghhy0tsfzuHGaJXW2L5sxaWCYxCs5CsnoWkZRaSlgWMzKsY2XMTM3PSy803MQKj5OCW3wY7 GDfdFzvEKM3BoiTOm8zVGCgkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBUbWn3fLbYYvD9jxf evUr/ka5b9Kfx/7/v9lhoeSJUlu1gzpmm3GdTFXtkjwgymo0Wfb8zE0BxstqghNq9hrLLlsf E/JPJ9Y2QzFtuV32kr+BG1rjr+R2Zm9bIX3X9Z6ezRb1NkajPtsj95csXX4t0jiz2XvueqZQ ldSKgIAl+tqX1S/OMhNXYinOSDTUYi4qTgQAsX97hmACAAA=
Cc: Adam Roach <adam@nostrum.com>, General Area Review Team <gen-art@ietf.org>, "Peter Saint-Andre (psaintan)" <psaintan@cisco.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "<mary.barnes@nortel.com>" <mary.barnes@nortel.com>, "<draft-saintandre-impp-call-info.all@tools.ietf.org>" <draft-saintandre-impp-call-info.all@tools.ietf.org>, Mary Barnes <mary.h.barnes@gmail.com>
Subject: Re: [Gen-art] Gen-art LC review of draft-saintandre-impp-call-info-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 15:36:00 -0000

Hi,

yes, fixing registry issues are orthogonal to progressing this draft.

Cheers,

Gonzalo

On 26/04/2013 2:09 AM, Cullen Jennings (fluffy) wrote:
> 
> On Apr 25, 2013, at 11:58 AM, Adam Roach <adam@nostrum.com> wrote:
> 
>> On 4/24/13 09:19, Peter Saint-Andre wrote:
>>> Hi Elwyn, thanks for the review.
>>>
>>> On Apr 23, 2013, at 2:12 PM, Elwyn Davies wrote:
>>>> Generic comment about SIP Header Field Parameters registry: For the uninitiated this registry is rather opaque.  Some parameters, such as the Call-Info purpose parameter for which an extra value is defined here, have predefined values.  However the predefined values themselves are not in the registry and just giving a whole RFC reference for places where values are defined is not very helpful. For example, in the case of Call-Info, the initial predefined values of purpose are buried in the Call-Info rule in the ABNF in Section 25.1 of RFC 3261;  also, Section 20.9 describes the predefined values (such as "icon") as 'parameters' rather than values of 'purpose'.  It would probably be helpful to either improve the references in the registry table or actaully quote the possible predefined values in the table.
>>>>
>>>
>>> I agree, but as you say that's an issue with the SIP Header Field Parameters registry in general. I started to go down the path of fixing the registry as a whole, but I think I'd rather leave that for 3261bis to tackle (sometime before the heat death of the universe).
>>
>> Yes, the registry is a mess, largely due to the rather whimsical preferences -- which would vary from year to year -- of the SIP community regarding which fields needed a registry and which did not. It's grown to be the way it is somewhat organically, and I agree that the overall SIP registry is something of a mess.
>>
>> I'm not sure we need to wait for a 3261bis to fix things, as I doubt we could find someone with the fortitude to take on an effort that large. It might be worth finding someone to work on a "registry overhaul" document that attempts to make the whole thing more coherent. I'll be keeping this in mind as a potential SIPCORE item.
>>
>> /a
> 
> +1
> 
> More importantly, I don't think this draft could reasonably take on cleaning up that mess. 
> 
>