Re: [Insipid] Suresh Krishnan's Discuss on draft-ietf-insipid-session-id-26: (with DISCUSS and COMMENT)

"Paul Giralt (pgiralt)" <pgiralt@cisco.com> Wed, 17 August 2016 02:26 UTC

Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57BDD12D17B; Tue, 16 Aug 2016 19:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.768
X-Spam-Level:
X-Spam-Status: No, score=-15.768 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 5fDwIwKeW8O6; Tue, 16 Aug 2016 19:26:20 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CBF912D179; Tue, 16 Aug 2016 19:26:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4760; q=dns/txt; s=iport; t=1471400780; x=1472610380; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=heZ0dG7J7M158Bd5XgxjdtJF8OhXt0zbAXBs6FO/XkI=; b=Ak/cQUCkGRZxiDuXbu9lnyDvr8fB9KGK1eiOPAh9tZLnqaVqxm8ksRJq yP0SAVSPn2a9glXnjPK1qfPp/yjhtrNFoUV24c0uwmOvXUZtNxwgXLpF0 GPEKXEgOr3rArNpXdq4obbp8REC5araHvlhgv+Y2ssnKYjwSuN7OUL6Qx s=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BFAgDnyrNX/4oNJK1eAYNEVnwHtzqCD4F9JIV5AoFcOBQCAQEBAQEBAV4nhF4BAQQBI1YFCwIBCBgqAgIyJQIEDgUOiBsIDq5ZkC4BAQEBAQEBAQEBAQEBAQEBAQEBAQEOCQWGKoF4glWEEhEBToJPK4IvBYgqkRoBgz2Bc2+Ie4FrhFyJAYw5g3cBHjaCEhwXgTVuAYUqN38BAQE
X-IronPort-AV: E=Sophos;i="5.28,529,1464652800"; d="asc'?scan'208";a="141269101"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Aug 2016 02:26:19 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u7H2QFmm023356 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 17 Aug 2016 02:26:15 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 16 Aug 2016 22:26:14 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Tue, 16 Aug 2016 22:26:14 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: Suresh Krishnan's Discuss on draft-ietf-insipid-session-id-26: (with DISCUSS and COMMENT)
Thread-Index: AQHR+BY9xIffpVDqJ0+YO7L0tIxS0KBMsFUA
Date: Wed, 17 Aug 2016 02:26:14 +0000
Message-ID: <3A0998BB-B2DC-45D3-B86E-F46405C284F5@cisco.com>
References: <147139025342.19839.14606551168506879969.idtracker@ietfa.amsl.com>
In-Reply-To: <147139025342.19839.14606551168506879969.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.123.204]
Content-Type: multipart/signed; boundary="Apple-Mail=_AA08AF2E-6324-4229-80C1-94B40CE38706"; protocol="application/pgp-signature"; micalg="pgp-sha512"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/ASuCpJqSNDepuahsgn5Um5pLb4Y>
Cc: "insipid-chairs@ietf.org" <insipid-chairs@ietf.org>, "insipid@ietf.org" <insipid@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-insipid-session-id@ietf.org" <draft-ietf-insipid-session-id@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Insipid] Suresh Krishnan's Discuss on draft-ietf-insipid-session-id-26: (with DISCUSS and COMMENT)
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 17 Aug 2016 02:26:22 -0000

Suresh, thanks for the comments. Please see inline…

> On Aug 16, 2016, at 7:30 PM, Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
> 
> Suresh Krishnan has entered the following ballot position for
> draft-ietf-insipid-session-id-26: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> * Section 5
> 
> I do have a concern about backward compatibility regarding the sess-uuid.
> Looks like this document allows the sess-uuid to contain either uppercase
> or lowercase hex digits ("sess-uuid           = 32(DIGIT / %x41-46 /
> %x61-66)") while the legacy version in RFC7329 does not allow uppercase
> hex digits. Looks like a compliant implementation of the spec using upper
> case hex digits will fail to interoperate with a legacy implementation. I
> do not have a particular preference, but either this rule needs to be
> tightened or there needs to be some text added to Section 11 to say this
> will cause an interoperability issue.
> 



This was a last-minute change made as a result of comments from Elwyn in gen-art review. The concern was that RFC 7329 specifies the identifier is lowercase, however it then points out:

   NOTE: The sess-id value is technically case-INSENSITIVE, but only
   lowercase characters are allowed.

This means that a complaint implementation of 7329 should treat the characters as case-INSENSITIVE and therefore not have a problem.

We could back out the change and require lower-case to ensure this is not an issue. It just seemed strange that we are requiring lower case while simultaneously saying that the case doesn’t actually matter, hence the change.



> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> * Section 4.1
> 
> The namespace ID in section 4.1 is specified as the initialization of a C
> structure as described in Appendix C of RFC4122. It is missing a
> semicolon at the end to make it legal.
> 
> OLD:
>       uuid_t NameSpace_SessionID = {
>           /* a58587da-c93d-11e2-ae90-f4ea67801e29 */
>           0xa58587da,
>           0xc93d,
>           0x11e2,
>           0xae, 0x90, 0xf4, 0xea, 0x67, 0x80, 0x1e, 0x29
>       }
> 
> NEW:
>       uuid_t NameSpace_SessionID = {
>           /* a58587da-c93d-11e2-ae90-f4ea67801e29 */
>           0xa58587da,
>           0xc93d,
>           0x11e2,
>           0xae, 0x90, 0xf4, 0xea, 0x67, 0x80, 0x1e, 0x29
>       };
> 

Thank you. Will fix this.


> * Agree with Alissa's DISCUSS regarding persistence
> 
> 

Please see my notes in response to Alissa and let me know your thoughts.


-Paul