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(_at_)ietf(_dot_)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