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

Paul Kyzivat <pkyzivat@cisco.com> Wed, 07 March 2007 18:39 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 1HP12y-00056L-9p; Wed, 07 Mar 2007 13:39:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HP12w-00050L-Rv for sipping@ietf.org; Wed, 07 Mar 2007 13:39:30 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HP12v-0005tn-FI for sipping@ietf.org; Wed, 07 Mar 2007 13:39:30 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-6.cisco.com with ESMTP; 07 Mar 2007 10:39:28 -0800
X-IronPort-AV: i="4.14,261,1170662400"; d="scan'208"; a="118914762:sNHT47566701"
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 l27IdStV008924; Wed, 7 Mar 2007 13:39:28 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l27IdSZn027117; Wed, 7 Mar 2007 18:39:28 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Mar 2007 13:39:27 -0500
Received: from [161.44.174.118] ([161.44.174.118]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Mar 2007 13:39:27 -0500
Message-ID: <45EF06DF.6030503@cisco.com>
Date: Wed, 07 Mar 2007 13:39:27 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Pete Cordell <pete@tech-know-ware.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>
In-Reply-To: <001101c760e2$e9b69180$5900a8c0@Codalogic>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Mar 2007 18:39:27.0579 (UTC) FILETIME=[EF88F2B0:01C760E7]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3332; t=1173292768; x=1174156768; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@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:=20Pete=20Cordell=20<pete@tech-know-ware.com>; bh=Ot56RRO1rgW2+Z7nrgPxVbechE+/6Ssp6xp2AZXqySE=; b=GgRarR8JlAQjmAiAx+m5qNxzEuomKDqylloFFfTtlk0xEmeBqLSo63xvwxKy6LyF9iZyKAdN WOKhtREjpG9vhTW0Rdys6A2A9ppMG3o78tFBRvekLHGSXfTeZrZIfbQ7;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: sipping <sipping@ietf.org>
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

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