IETF Logo Mail Archive

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

<R.Jesske@telekom.de> Fri, 23 January 2015 06:45 UTC

Return-Path: <R.Jesske@telekom.de>
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 1946C1A024C for <insipid@ietfa.amsl.com>; Thu, 22 Jan 2015 22:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level:
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, 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 BTwfVYI6_i1O for <insipid@ietfa.amsl.com>; Thu, 22 Jan 2015 22:45:07 -0800 (PST)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [80.149.113.247]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72CCB1A1A47 for <insipid@ietf.org>; Thu, 22 Jan 2015 22:45:06 -0800 (PST)
Received: from qdezc2.de.t-internal.com ([10.125.181.10]) by tcmail31.telekom.de with ESMTP; 23 Jan 2015 07:45:04 +0100
X-IronPort-AV: E=Sophos;i="5.09,453,1418079600"; d="scan'208";a="201735846"
Received: from he110889.emea1.cds.t-internal.com ([10.134.92.130]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES128-SHA; 23 Jan 2015 07:45:03 +0100
Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE110889.emea1.cds.t-internal.com ([fe80::841f:f92c:15ca:8526%16]) with mapi; Fri, 23 Jan 2015 07:45:03 +0100
From: R.Jesske@telekom.de
To: paulej@packetizer.com, pkyzivat@alum.mit.edu, insipid@ietf.org
Date: Fri, 23 Jan 2015 07:45:02 +0100
Thread-Topic: [Insipid] Reviews for INSIPID Session-ID solution draft Version 11
Thread-Index: AdA2yTNjK2BhKDOfSte+YL0XYHWIbwADtw1w
Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01E5F845F5B4@HE113667.emea1.cds.t-internal.com>
References: <em2466bfc4-67fc-471d-a67c-f68f79e9fd9c@sydney> <em98bc163b-eb9a-404d-9a40-2093bb5e792f@sydney>
In-Reply-To: <em98bc163b-eb9a-404d-9a40-2093bb5e792f@sydney>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/D4AY04gtY-sobKnCfOOQuPY5ReA>
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: Fri, 23 Jan 2015 06:45:10 -0000

For me OK.

Best Regards
Roland

-----Ursprüngliche Nachricht-----
Von: insipid [mailto:insipid-bounces@ietf.org] Im Auftrag von Paul E. Jones
Gesendet: Freitag, 23. Januar 2015 05:58
An: Paul E. Jones; Paul Kyzivat; insipid@ietf.org
Betreff: Re: [Insipid] Reviews for INSIPID Session-ID solution draft Version 11

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.

------ 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

v2.23.0 | Report a Bug | By Email