Re: [Sipping] RFC3680 and draft-ietf-sipping-gruu-reg-event-08 :are quotes part of parameter values?

Jonathan Rosenberg <jdrosen@cisco.com> Thu, 08 March 2007 13:00 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPIE5-0005oa-2Z; Thu, 08 Mar 2007 08:00:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPIE2-0005cs-OL for sipping@ietf.org; Thu, 08 Mar 2007 08:00:06 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPIE1-00025g-31 for sipping@ietf.org; Thu, 08 Mar 2007 08:00:06 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-2.cisco.com with ESMTP; 08 Mar 2007 05:00:04 -0800
X-IronPort-AV: i="4.14,264,1170662400"; d="scan'208"; a="364594532:sNHT51406620"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l28D03Sf011809; Thu, 8 Mar 2007 08:00:03 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l28D03Zn020745; Thu, 8 Mar 2007 13:00:03 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Mar 2007 08:00:03 -0500
Received: from [172.17.11.12] ([10.82.241.210]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Mar 2007 08:00:03 -0500
Message-ID: <45F008D2.9070108@cisco.com>
Date: Thu, 08 Mar 2007 08:00:02 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] RFC3680 and draft-ietf-sipping-gruu-reg-event-08 :are quotes part of parameter values?
References: <007401c760c7$90cfe2d0$0601a8c0@BEMBUSTER> <45EEF58E.90004@cisco.com> <001101c760e2$e9b69180$5900a8c0@Codalogic> <45EF06DF.6030503@cisco.com>
In-Reply-To: <45EF06DF.6030503@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Mar 2007 13:00:03.0248 (UTC) FILETIME=[AFDC6300:01C76181]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4490; t=1173358803; x=1174222803; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:=20Re=3A=20[Sipping]=20RFC3680=20and=20draft-ietf-sipping-gruu-r eg-event-08=20=3Aare=0A=20quotes=20part=20of=20parameter=20values? |Sender:=20 |To:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>; bh=pJlocKpxPS99sniGGJeuDTKO3L8zWxy1LsI16QaYaWw=; b=kGUs3D+EAaYVDyA+RwvLc4ya2uFb1Vgpgnv7hYZ7VxbUnJfJXy/zTrBvZFjLn8rpXne0LV+d qBl5ZYXwvNdx9SMRiA0h73DljVu/AtRcyFlAFYEjMlaRaPHI4kJ6/8K6;
Authentication-Results: rtp-dkim-2; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Cc: sipping <sipping@ietf.org>, Pete Cordell <pete@tech-know-ware.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

For unknown params, the XML *must* contain the quotes if they were 
present in the contact param, for the very reason Paul is indicating 
below. This has nothing to do with xml practices, it has to do with 
including the quotes if they were tere.

For pub-gruu I think the quotes are not needed since we know the format 
of what is contained there.

-Jonathan R.

Paul Kyzivat wrote:

> Maybe this is more of an xml best practices question, or maybe it isn't 
> an xml question at all.
> 
> In the case of the <unknown-param>, some unknown parameters may have 
> values with quotes, and some may have values without quotes. So the only 
> way to faithfully represent the information is to include the quotes in 
> the xml.
> 
> In the case of <pub-gruu>, the parameter value will always have quotes, 
> so they may be considered redundant. Whether to require them or not is a 
> style issue, as well as a documentation issue to make clear what the 
> expectation is.
> 
> I do agree that this is an area of potential confusion. Would people 
> prefer to see the quotes included here for consistency?
> 
>     Thanks,
>     Paul
> 
> Pete Cordell wrote:
> 
>> This doesn't look like an XML question.  (The quotes are fine where 
>> they are.)
>>
>> I think Jeroen is saying, if an example of <unknown-param> is (with 
>> quotes):
>>   <unknown-param
>>   
>> name="+sip.instance">"&lt;urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6&gt;"</unknown-param> 
>>
>>
>> should the <pub-gruu> be (with quotes):
>>   <gr:pub-gruu>"sip:user@example.com;gr=hha9s8d-999a"</gr:pub-gruu>
>>
>> Or, if <pub-gruu> is (without quotes):
>>   <gr:pub-gruu>sip:user@example.com;gr=hha9s8d-999a</gr:pub-gruu>
>>
>> should <unknown-param> be (without quotes):
>>   <unknown-param
>>   
>> name="+sip.instance">&lt;urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6&gt;</unknown-param> 
>>
>>
>> Or, should they be as they currently are.  It's up to you.  XML does 
>> not care!
>>
>> HTH,
>>
>> Pete.
>> ----- Original Message ----- From: "Paul Kyzivat" <pkyzivat@cisco.com>
>> To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
>> Cc: "sipping" <sipping@ietf.org>
>> Sent: Wednesday, March 07, 2007 5:25 PM
>> Subject: Re: [Sipping] RFC3680 and 
>> draft-ietf-sipping-gruu-reg-event-08 :are quotes part of parameter 
>> values?
>>
>>
>>> I'm afraid this is beyond my feeble understanding of xml. So I don't 
>>> know what is correct here. Can an xml guru enlighten me?
>>>
>>> Thanks,
>>> Paul
>>>
>>> Jeroen van Bemmel wrote:
>>>
>>>> RFC3680 defines the <unknown-param> element for Contact parameters 
>>>> such as callee capabilities, but gives no examples. The 
>>>> gruu-reg-event draft contains examples which illustrate the use of 
>>>> this element for the "+sip.instance" parameter:
>>>>  <unknown-param 
>>>> name="+sip.instance">"&lt;urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6&gt;"</unknown-param> 
>>>>
>>>> <gr:pub-gruu>sip:user@example.com;gr=hha9s8d-999a</gr:pub-gruu>
>>>>  There appears to be an inconsistency here: both the pub-gruu and 
>>>> the +sip.instance parameter are contained in quotes as part of the 
>>>> Contact header. These quotes are reflected in the <unknown-param> 
>>>> element, but not in the <pub-gruu> element.
>>>>  Looks like a potential interop issue to me. I understand the 
>>>> reasoning behind the above XML fragment, and I agree, but perhaps it 
>>>> is worth pointing out the quoting (ideally in RFC3680, but 
>>>> second-best in reg-event)
>>>>  Regards,
>>>> Jeroen
>>
>>
>> -- 
>> =============================================
>> Pete Cordell
>> Tech-Know-Ware Ltd
>> for XML to C++ data binding visit
>> http://www.tech-know-ware.com/lmx/
>> http://www.codalogic.com/lmx/
>> =============================================
>>
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP