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

Paul Kyzivat <pkyzivat@alum.mit.edu> Sat, 24 January 2015 15:34 UTC

Return-Path: <prvs=6466e0d26b=pkyzivat@alum.mit.edu>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8CC1A3BA6 for <insipid@ietfa.amsl.com>; Sat, 24 Jan 2015 07:34:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tl_tE9dohaRS for <insipid@ietfa.amsl.com>; Sat, 24 Jan 2015 07:34:47 -0800 (PST)
Received: from alum-mailsec-scanner-8.mit.edu (alum-mailsec-scanner-8.mit.edu [18.7.68.20]) by ietfa.amsl.com (Postfix) with ESMTP id 536271A3B9F for <insipid@ietf.org>; Sat, 24 Jan 2015 07:34:45 -0800 (PST)
X-AuditID: 12074414-f797f6d000004084-1a-54c3bb947d66
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 1B.B1.16516.49BB3C45; Sat, 24 Jan 2015 10:34:44 -0500 (EST)
Received: from Paul-Kyzivats-MacBook-Pro.local (c-50-138-229-151.hsd1.ma.comcast.net [50.138.229.151]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id t0OFYhF5014636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 24 Jan 2015 10:34:43 -0500
Message-ID: <54C3BB93.8030508@alum.mit.edu>
Date: Sat, 24 Jan 2015 10:34:43 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>, insipid@ietf.org
References: <em73d79643-a12b-4d43-b365-aa62462f26d9@sydney>
In-Reply-To: <em73d79643-a12b-4d43-b365-aa62462f26d9@sydney>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnleLIzCtJLcpLzFFi42IRYndR1J2y+3CIQdtuOYv5958xWZy/sIHJ gcljyZKfTB4N+46yBzBFcdskJZaUBWem5+nbJXBnnN/wgaXgs2TF3+1XGRsYZ4h2MXJySAiY SGzr7WCGsMUkLtxbz9bFyMUhJHCZUaLzVzsjhPOcSeLpidNMIFW8AtoSW65fYwSxWQRUJTY+ egxmswloScw59J8FxBYVSJZYs3USO0S9oMTJmU/A4iICthIH51xhBbGFBQIl5v/ewAZiCwlY S/yb/gBsPqeAjcSlB+vBapgFzCS6tnYxQtjyEtvfzmGewMg/C8nYWUjKZiEpW8DIvIpRLjGn NFc3NzEzpzg1Wbc4OTEvL7VI10IvN7NELzWldBMjJChFdjAeOSl3iFGAg1GJhzeA8XCIEGti WXFl7iFGSQ4mJVHeBmagEF9SfkplRmJxRnxRaU5q8SFGCQ5mJRHeCxuAcrwpiZVVqUX5MClp DhYlcd5vi9X9hATSE0tSs1NTC1KLYLJ6HBwCXz6e+8QocOlN91dGKZa8/LxUJQlew11AowSL UtNTK9Iyc0oQGpg4OEHWcUmJFKfmpaQWJZaWZMSD4ja+GBi5ICkeoEsYQdp5iwsSc4GiEK2n GBWlxHk5QRICIImM0jy4sbB09IpRHOhvYV4LkCoeYCqD634FNJgJaHDB9gMgg0sSEVJSDYyz HA4ulT0rsVrQ6/Phy/Z7N3nfliwudPI7IrjoLevNq4J370mq7/lzLWnBZ7fk1zk3nU6ds//A +Vymceu0U12pnx6uP743tW7CtgmT14V4PG2SyU746dn00tnk1oqjURWTEmSnqv5vrO+dctan dfZ+g+WXfn2J2Lw5IWMzW5Dms/6rqUbh82arKrEUZyQaajEXFScCAJQ0KIsiAwAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/2VWxkmjnv1LJ8QJjdmjtcJPtcGo>
Subject: Re: [Insipid] Reviews for INSIPID Session-ID solution draft Version 11
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 15:34:50 -0000

WFM

On 1/23/15 7:49 PM, Paul E. Jones wrote:
> OK.  How about this?
>
> "The Session-ID header-value is technically case-INSENSITIVE, but only
> lowercase characters are allowed in the sess-uuid components. Receiving
> entities MUST treat sess-uuid components as case-insensitive and not
> produce an error if an uppercase character is received in a sess-uuid."
>
> Do you have better wording than "component"?  I don't like that, but I
> guess that's clear.  I'm open to suggested changes.
>
> Paul
>
> ------ Original Message ------
> From: "Paul Kyzivat" <pkyzivat@alum.mit.edu>
> To: "Paul E. Jones" <paulej@packetizer.com>; insipid@ietf.org
> Sent: 1/23/2015 10:54:45 AM
> Subject: 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
>>>
>>>
>>
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>
>