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

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