Re: INFO: Case Sensitivity

Well now I'm really confused.

I liked your 3 before

Case _sensitive_ comparison.
and
Never register both "Foo" and "foo".

So, now I prefer a red "4".

RjS

On Nov 19, 2008, at 7:09 PM, Eric Burger wrote:

> My mistake: small typo.  #3 should be "Keep case INSENSITIVE  
> comparison, and tell IANA not to register multiple package names  
> that might collide in the event someone does to case insensitive  
> comparisons (liberal in what you receive)."
>
> So, we have for your choices:
> 1. Keep case sensitive comparison, just like RFC 3265 mandates and  
> experience shows promotes interoperability
>
> 2. Use case insensitive comparison, like RFC 3261 suggests
>
> 3. Keep case INSENSITIVE comparison, and tell IANA not to register  
> multiple package names that might collide in the event someone does  
> to case insensitive comparisons (liberal in what you receive)
>
>
> On Nov 19, 2008, at 7:05 PM, Paul Kyzivat wrote:
>
>> I think I will abstain. I didn't realize that 3265 called for case  
>> sensitive comparisons. IMO it is the oddball among headers, but it  
>> is a good precedent here.
>>
>> 	Thanks,
>> 	Paul
>>
>> Eric Burger wrote:
>>> We had a long discussion about case sensitivity for Info Package  
>>> names. The current text follows RFC 3265 and avoids charset and  
>>> I18N issues, by mandating octet-by-octet comparison.
>>> Some folks pointed out that RFC 3261 says that headers and header  
>>> values should be case insensitive.
>>> Please vote:
>>> 1. Keep case sensitive comparison, just like RFC 3265 mandates and  
>>> experience shows promotes interoperability
>>> 2. Use case insensitive comparison, like RFC 3261 suggests
>>> 3. Keep case sensitive comparison, and tell IANA not to register  
>>> multiple package names that might collide in the event someone  
>>> does to case insensitive comparisons (liberal in what you receive)
>>> ------------------------------------------------------------------------
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use [email protected] for questions on current sip
>>> Use [email protected] for new developments on the application of sip
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [email protected] for questions on current sip
> Use [email protected] for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip