IETF Logo Mail Archive

Re: [secdir] Secdir last call review of draft-atarius-dispatch-meid-urn-as-instanceid-05

Andrew Allen <aallen@blackberry.com> Fri, 08 December 2017 17:37 UTC

Return-Path: <aallen@blackberry.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC251273B1; Fri, 8 Dec 2017 09:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 SE-3c_fsSgGf; Fri, 8 Dec 2017 09:37:12 -0800 (PST)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DD05120713; Fri, 8 Dec 2017 09:37:11 -0800 (PST)
X-Spoof:
Received: from xct101cnc.rim.net ([10.65.161.201]) by mhs211cnc.rim.net with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Dec 2017 12:37:10 -0500
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT101CNC.rim.net ([fe80::9c22:d9c:c906:c488%16]) with mapi id 14.03.0319.002; Fri, 8 Dec 2017 12:37:10 -0500
From: Andrew Allen <aallen@blackberry.com>
To: Daniel Migault <daniel.migault@ericsson.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-atarius-dispatch-meid-urn-as-instanceid.all@ietf.org" <draft-atarius-dispatch-meid-urn-as-instanceid.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Secdir last call review of draft-atarius-dispatch-meid-urn-as-instanceid-05
Thread-Index: AQHTb8ztYiwncQZaBkOg9hPej4gGoaM5tPGg
Date: Fri, 08 Dec 2017 17:37:09 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD233AA7218B@XMB122CNC.rim.net>
References: <151270040464.5892.16248327802973779967@ietfa.amsl.com>
In-Reply-To: <151270040464.5892.16248327802973779967@ietfa.amsl.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.160.249]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/lZ_SwtRm1tBvuB7UPF-awcrsv60>
Subject: Re: [secdir] Secdir last call review of draft-atarius-dispatch-meid-urn-as-instanceid-05
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Dec 2017 17:37:15 -0000

Daniel

When talking about SIP and IMS Registered has a specific connotation means SIP registered.

The is no SIP Registration between the mobile device and the CS domain so using registered might be misleading. 

You are right that in the single radio case the mobile device is not simultaneously attached to both the IMS and CS domain. It would be in the dual radio case.

Maybe change that last sentence to

To achieve this the mobile device needs to communicate via both the IP/SIP/IMS domain and the circuit switched domain.

Andrew

-----Original Message-----
From: Daniel Migault [mailto:daniel.migault@ericsson.com] 
Sent: Thursday, December 7, 2017 9:33 PM
To: secdir@ietf.org
Cc: draft-atarius-dispatch-meid-urn-as-instanceid.all@ietf.org; ietf@ietf.org
Subject: Secdir last call review of draft-atarius-dispatch-meid-urn-as-instanceid-05

Reviewer: Daniel Migault
Review result: Ready

Hi, 

I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.

The summary of the review is Ready

Some comments / questions:

1.  Introduction

   This specification specifies how the URN namespace reserved for 3GPP2
   identities and its NSS for the MEID as specified in draft-atarius-
   dispatch-meid-urn [8] can be used as an instance-id as specified in
   RFC 5626 [2] and also as used by RFC 5627 [3].

<mglt> I think it would be good to have the acronyms (URN, 3GPP2, NSS,
MEID) expanded in the introduction section as it is being done in the abstract.</mglt> 


   3GPP2 defines High Rate Packet Data (HRPD) with high data rates and
   it dispenses with the 1x Circuit Switched (1xCS) infrastructure.
   This means that with HRPD networks, voice calls will need to be
   conducted using IP and IMS.  However, the transition to all IP, SIP
   based IMS networks worldwide will take a great many years from the
   time of this writing and mobile devices will need to operate in both
   IP/SIP/IMS mode and circuit switched mode.  This means that calls and
   sessions will need to be handed over between IP/SIP/IMS mode and
   circuit switched mode mid-call or mid-session.  To achieve this the
   mobile device needs to be simultaneously attached via both the
   IP/SIP/IMS domain and the circuit switched domain.

<mglt> I am questioning whether "registered" would not be better appropriated than "attached". My reading of attached is a dual radio case while "register" seems to include the single radio. 
I might be wrong as well.</mglt>

v2.23.0 | Report a Bug | By Email