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

"Suresh Krishnan" <suresh.krishnan@ericsson.com> Tue, 16 August 2016 23:30 UTC

Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: insipid@ietf.org
Delivered-To: insipid@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7129012D0C5; Tue, 16 Aug 2016 16:30:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147139025342.19839.14606551168506879969.idtracker@ietfa.amsl.com>
Date: Tue, 16 Aug 2016 16:30:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/Uvczsl_54blMdV8nWU9Yq0EAFE8>
Cc: insipid@ietf.org, insipid-chairs@ietf.org, draft-ietf-insipid-session-id@ietf.org, christer.holmberg@ericsson.com
Subject: [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
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: Tue, 16 Aug 2016 23:30:53 -0000

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.


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

* Agree with Alissa's DISCUSS regarding persistence