Re: Last Call: <draft-ietf-insipid-session-id-reqts-08.txt> (Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks) to Informational RFC

SM <sm@resistor.net> Sat, 14 September 2013 16:07 UTC

Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB6B111E81E9 for <ietf@ietfa.amsl.com>; Sat, 14 Sep 2013 09:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level:
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8nPVB+R65-RI for <ietf@ietfa.amsl.com>; Sat, 14 Sep 2013 09:07:45 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EC4AD11E81B7 for <ietf@ietf.org>; Sat, 14 Sep 2013 09:07:44 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r8EG7d9t006468 for <ietf@ietf.org>; Sat, 14 Sep 2013 09:07:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1379174863; bh=2cG7ElOoqBhrkLdkPwk6jcyufI5apkMNODyFLMmH+FU=; h=Date:To:From:Subject:In-Reply-To:References; b=mVZHu+sQxYzLy7cfPKpLl3Wh6uSDEmKaxhlv+4NvXJY6GeXWLDjVVHWFSORpKfzbF H6n5xDAkmhdQOLh6LfsPV35voFaVUs7AqxqhDIRQapip6zs51hCcdUXW80PNY4jpAC 81UtwU1B+7YT/m7+PjZ3DxBMabCAIhCVynQfFMCQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1379174863; i=@resistor.net; bh=2cG7ElOoqBhrkLdkPwk6jcyufI5apkMNODyFLMmH+FU=; h=Date:To:From:Subject:In-Reply-To:References; b=kdT2laJUXHERimB8KG7tfBx21LZ4XA7SNmnAL5a6F4ejFwuNxqELPkOLpDZbrpOsI G24jVA/Zi73j5V46gJTXx3PBu91ooUkUTvLrIsXqdX2IATL9JEuWFrlw3yga16ug2r C3m4AW+ZCzYvftEWvh1yiqvnD+FlO7qxxDj5aDvg=
Message-Id: <6.2.5.6.2.20130914084457.0dd0b0a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 14 Sep 2013 09:03:30 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-insipid-session-id-reqts-08.txt> (Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks) to Informational RFC
In-Reply-To: <20130910164051.26974.65993.idtracker@ietfa.amsl.com>
References: <20130910164051.26974.65993.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Sep 2013 16:07:46 -0000

At 09:40 10-09-2013, The IESG wrote:
>The IESG has received a request from the INtermediary-safe SIP session ID
>WG (insipid) to consider the following document:
>- 'Requirements for an End-to-End Session Identification in IP-Based
>    Multimedia Communication Networks'
>   <draft-ietf-insipid-session-id-reqts-08.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-09-24. Exceptionally, comments may be

Section 4.5 of the draft discusses about logging.  It mentions that 
"creating a common header field value through all SIP entities will 
greatly reduce any challenge for the purpose of" ... "communication tracking".

I look a quick look at Reference [6].  It mentions that the IMEI 
shall be used for generating an identifier.  Is the IMEI covered by REQ4?

Regards,
-sm