Re: [Insipid] Reviews for INSIPID Session-ID solution draft Version 11

On 1/22/15 11:58 PM, Paul E. Jones wrote:
> Specifically, how about this at the end of section 5?
>
> NOTE: The Session-ID header-value is technically case-INSENSITIVE, but
> only lowercase characters are allowed in the sess-uuid components of the
> syntax.

Its better than nothing. But I think it would be better to make a 
normative requirement to support reception of uuids in either case, 
while requiring that they be sent in lower case. This makes it clear 
that it is only an accommodation to non-conforming implementations.

	Thanks,
	Paul

> ------ Original Message ------
> From: "Paul E. Jones" <paulej@packetizer.com>
> To: "Paul Kyzivat" <pkyzivat@alum.mit.edu>; insipid@ietf.org
> Sent: 1/22/2015 11:53:48 PM
> Subject: Re: [Insipid] Reviews for INSIPID Session-ID solution draft
> Version 11
>
>> Paul,
>>
>>>>>> I think it would be worth to mention that the UUID is case
>>>>>> insensitive
>>>>>> as defined in RFC 4122
>>>>>
>>>>> The text currently states that the UUID characters are lower-case. The
>>>>> syntax also enforces this. The RFC 4122 text is funny, because it says
>>>>> "lower case characters and are case insensitive". I don't know what
>>>>> that means, except that "F" is not a valid character. Rather than
>>>>> create confusing language, I'd rather just leave the text as it is in
>>>>> saying the characters are lowercase.
>>>>
>>>> [RJ] OK
>>>
>>> The *safest* (belt and suspenders) way of dealing with this would be
>>> to require that senders always insert lower case, but require that
>>> receivers properly process either upper/lower case.
>>>
>>> IMO it *should* always have been case-insensitive. IIRC the reason it
>>> isn't that way is because Kaplan was case sensitive and there are
>>> implementations in the wild that depend on it.
>>
>> I just looked at RFC 7239 and found this:
>>
>>    NOTE: The sess-id value is technically case-INSENSITIVE, but only
>>    lowercase characters are allowed.
>>
>> Shall we include the same text in our draft?
>>
>> Paul
>>
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>
>