Download TR-45.6 Combined Ballot Comments on LAES for cdma2000

TR-45.6 Combined Ballot Comments on LAES for cdma2000@ Voice over IP (TIA-1066) Post Ballot Resolution (16 August 05) FINISHED!
1. Do not populate this column (Editor will populate)
2. Please enter comment number nnn.
3. Enter your company name in the third column.
4. Enter the Section number in the fifth column.
5. Enter the Page number in the sixth column.
6. Enter the Line number in the seventh column. (If you want to indicate multiple lines, use ‘-‘. For example 24 – 26.)
7. Enter the Type of the comment in the eighth column.
E=Purely Editorial (can be left to the editor to fix)
T=Technical (requires a change to the technical content)
8. Editor will enter results of comment resolutions.
9. Enter your company’s comment or the supporting filename in the ninth column.
Provide an SF File only if the comment affects more than one section.
Please do not modify the width of the table
1.
#
Leave
Blank
(aaaa)
2.
#
3.
Source
(Company
Name)
(nnn) Company
name
CIU-3
1
2
4.
Section
2
Lucent
Abstract
5.
Page
6.
Line
v
6
v
9
7.
Typ
e
8.
Res.
9.
Comment/SF file ID
E,T
A,
AM,
W,
R
1. Provide a comment if the change is within one chapter and one section.
Proposed Text: (Must use revision mark)
Rational:
2. Or provide an SF File ID (Supporting File ID) if the comment affects
more than one section within one or more chapters.
SF File ID= SFaaaa-nnn-company (nnn=comment number entered by the
reviewer, same as column#2, aaaa comment number used/provided by
Editor from master list)
E
A
..for Lawfully Authorized Electronic Surveillance (LAES) for Voice over IP
(VoIP)…
Change to “which includes Voice over IP”. Why is this only applicable to VoIP
– implies isolating and reporting only VoIP.
AM
Page 1 of 36
3
001
CFRI
Forward
ix
17
E
Add “At the time of publication, work is also on-going in the area
of MMD intercept in TIA subcommittee TR-45.2 (insert formal
committee name), e.g., proposed ANS-TIA-1071 IP Multimedia
Subsystem Electronic Surveillance - Technical Aspects. “
AM
Note: check Table of Contents and realign page number for
Abstract to the right margin.
4
Motorola 1
Sprint
xi
10
E
A
xi
13
T
AM
6
Motorola 2
1
18-23
T
7
CIU-4
1
20-22
E
AM
(1st
insert
ion
accep
ted)
Mot
w/dra
ws
2nd
com
ment
AM
5
1
Remove from Forward:
As background information,
and jurisdictional areas of the legal authorization. NOTE: This para deleted
per Mot-3 resolution
Change General to read:
The network intercepts on identities found in communication-identifying
information at the IAP.
…is determined by the ability of the network to associate communication(s)
and communication-identifying information with the subject’s identity or
identities as derived from the lawful authorization.
Page 2 of 36
8
Motorola 3
1
23
T
AM
Add to General:
In order to deliver intercepted communications and communication-identifying
information, an LEA must serve the SP with the necessary legal authorization
identifying the intercept subject, the communications and information to be
accessed, and the jurisdictional areas of legal authorization. Remove this
paragraph text from fwd so this text is only located this location (in General).
Once the authorization is obtained, the SP shall perform delivery of the
intercept subject’s communication for transmission toward the government’s
procured equipment, facilities, or services.
An SP may be able to support LAES for VoIP without the SP having to modify
their networks or systems. Note: check for first use of acronyms.
Note: delete all “cdma2000®” in “cdma2000® VoIP instances EXCEPT for
that in the scope section.
9
1
Nortel
A
Comment #1: Correct the Purpose
Section 1.2 Purpose does not reflect the purpose of the standard in terms of
establishing a Safe Harbor specification for cdma2000 VoIP/MMD. This is
needed to distinguish between specifications which are not being created for a
Safe Harbor position. Add the following text to the purpose:
1.2 Purpose
10
CIU-5
2
10
E
A
11
CIU-6
2
11
E
A
12
CIU-7
2
13
E
A
The purpose of this Standard is to facilitate an SP’s assistance to law
enforcement. This Standard defines a method to support surveillance for
cdma2000® Voice over IP (VoIP) based on MMD. Compliance with this
standard is intended to establish a Safe Harbor position as necessary under the
CALEA statute.
…Network Perspective” identifies the triggering events, usage and information
to be report for the VoIP CII event messages and the application level CC
delivery formatted and information.
…Implementation Perspective” provides the cdma2000® Object Tree and
ASN.1 Modules.
Annex A (Normative): “SIP CII Surveillance Messages” provides the message
and parameter mappings from SIP standard signaling to surveillance messages
reported to the LEA by the SP for a VoIP intercept.
Page 3 of 36
13
Motorola 4
14
3
Lucent
15
2
Nortel
2
2
17
2
27-28
E
AM
Add to beginning of Reference section:
The following standards contain provisions which, through reference in this
text, constitute provisions of this Standard. At the time of publication, the
editions indicated were valid. All standards are subject to revision, and parties
to agreements based on this Standard are encouraged to investigate the
possibility of applying the most recent editions of the standards indicated
below.
A
Section refers to ANSI and TIA standards. For NAM, reference should be to
TIA document (TSB-151). Dele SR # and replace w/TSB-151. Title stays the
same. Need to split norm/inform references in Section 2 and TSB-151 goes
into inform.
Comment #2: Improve the Categorization of the References
AM
J-STD-025-B in 2 Reference is not an ANS. Create separate reference sections
for ANS and ATIS-TIA standards as follows.
American National Standards Institute (ANSI) Accredited standards:
ANSI
ATIS and TIA Standards:
[TIA-873]
16
CIU-8
2
30
T
Resol
ved
by 15
17
CIU-9
3
25
E
A
TIA-873, All-IP Core Network Multimedia
Domain: IP Multimedia Subsystem.
[NAM]
S.R0037-0 v3.0 IP Network Architecture Model
for cdma2000® Spread Spectrum Systems.
[025-B]
TIA/EIA-J-STD-025-B, Lawfully Authorized
Electronic Surveillance
J-STD-25B has not yet passed the second default ballot, so therefore should not
be referenced as an ANSI accredited standard in this document. Recommend a
separate section for TIA/ATIS approved documents that are not ANSI
accredited.
Collection Function (CF): where the intercepted communications and
communication-identifying information is collected by a law enforcement
agency (LEA).
Page 4 of 36
18
19
2
20
Motorola 5
3
28
T
W
Change Definition Section:
Communication-identifying information (CII): Signaling information available
at the Intercept Access Point for communication processing purposes that
identifies the origin, destination, or termination of each communication
generated or received by a subscriber by means of any equipment, facility, or
service of an SP. Network protocols (except LAESP) do not need to be
modified solely for the purpose of intercepting communication-identifying
information. The specific elements of communication-identifying information
that are reasonably available at an IAP may vary as the technology evolves.
Sprint
3
42
T
A
CIU-10
3
48
E
A
Delivery Function (DF): a logical entity in the Service Provider’s network
which delivers intercepted communications and communications-identifying
information toward one or more Collection Functions for each LEA requesting
intercept.
…. As used herein, also includes the acquisition of communication-identifying
information.
Acronym SIP URL should be included:
SIP URI. (This is referred to in Section 5) Add SIP URI in Section 3 and
globally change any SIP URL to SIP URI
Replace “User Equipment (UE)” with “Mobile Station (MS)” and put it in the
right order.
Should be made clear that the user is Law Enforcement: This section presents
the law enforcement user perspective….
…based on the Multi-Media Domain (MMD) in cdma2000®
Telecommunications Networks;…
Add the following sentence to the paragraph:
For purposes of this standard, the user is the LEA and not the intercept
subject.
21
4
Lucent
3
4
49
22
1
Qualcomm
3
4
60
23
5
Lucent
4.1
6
6
CIU-11
6
7
E
A
Sprint
6
12
T
Cove
red
by
com
ment
23
24
25
3
AM
E
A
AM
Page 5 of 36
26
Motorola 6
4.1
6
12
T
AM
Add the following:
An SP is required to provide access to the Multi-Media content or communication-identifying information for intercept subjects.
Communication-identifying information is encapsulated into discrete messages
which shall be transported to an LEA. During encapsulation, CII is not altered.
27
Motorola 7
6
16
E
A
Some circumstances dictate that the communication-identifying information,
content, or both, associated with an intercept subject need to be delivered to
more than one LEA Collection Function simultaneously. This will occur when
different LEAs are conducting independent investigations on the same subject.
The Delivery Function shall duplicate the content, communication-identifying
information, or both, and deliver only authorized information. No more than
five Collection Functions are required to be supported for any single intercept
subject.
Add:
4.2 General Background
Page 6 of 36
28
Motorola 8
6
18
T
AM
per
2005.
05.06
.06
Add:
The intercept function is viewed as five broad categories: access,
delivery, collection, service provider administration, and law
enforcement administration. These functions are discussed
functionally without regard to their implementation. The
relationships between these functional categories are shown in
Figure (X).
Service Provider
Access
Service Provider
Administration
Delivery
Lawful
Authorization
Law Enforcement
Collection
Administration
Law Enforcement Agency
Figure (X): Electronic Surveillance Model
The Access Function, consisting of one or more Intercept Access
Points (IAPs), isolates an intercept subject’s communicationidentifying information unobtrusively. The IAPs may vary
between SPs and may not be available on all systems.
The Delivery Function, consisting of one or more entities, is
responsible for delivering intercepted communications to one or
more Collection Functions. The Delivery Function(s) transports
messages which report communication-identifying information.
The physical delivery entities may be split into communicationidentifying information delivery and communication content
delivery, or may be combined.
[ED note: see next entry for continued text from this
comment]
Page 7 of 36
28 cont
Motorola-8
29
CIU-12
The Service Provider Administration Function is responsible for
controlling the SP Access and Delivery Functions.
The Collection Function is responsible for collecting and
analyzing intercepted communication-identifying information.
The Collection Function is the responsibility of the LEA. It is
assumed that the LEA collection equipment maintains current
state information concerning the associations between
communication identities. The collection equipment assumes that
the last reported association remains in effect until a subsequent
Multi-Media ES message explicitly changes that association.
The Law Enforcement Administration Function is responsible for
controlling the LEA Collection Function. The Law Enforcement
Administration Function is the responsibility of the LEA.
The lawful authorization, while neither a network entity nor an
interface reference point, is an important part of Multi-Media
Lawfully Authorized Electronic Surveillance (LAES). No
intercepts shall take place without specific lawful authorization.
6
19-21
E
E
30
2
Qualcomm
4.2.1
6
26
31
6
Lucent
4.2.1
6
26-50
32
7
Lucent
4.2.1
6-7
33
CIU-13
6
31
E
34
Motorola 9
6
31
E
35
CIU-14
6
32
E
The cdma2000® MMD system is a distributed architecture that provides MultiMedia services, which includes Voice over IP (VoIP) service. The architecture
is based on SIP standard signaling.
A
Replace “User Equipment (UE)” with “Mobile Station (MS)”. A definition
for MS was provided.
Clarification: Are IAPS required for every type of CSCF. That is, is each CSCF
A;
see
required to have an IAP or can the CSCFs be considered a collection of IAPs.
contr Otherwise, each CSCF will required their own LAES database. Discussion on
ibutio reflector.
n
2005.
08.15
.09
Architecture section (section 4.2) should be included in Stage 2 section, not Stage
A
1.Move to become “NEW” section 5.1 (prior to delivery)
Hand The following change may improve the text: “Registration accepts Handles
led
registration requests and makes its information available through the location
by 34 server (e.g., HSS);
AM
Change to:
(1) processes registration requests and makes its
information available through the location server (e.g.,
HSS);
AM
A
…location server (e.g., Home Subscriber System (HSS));
Page 8 of 36
36
Motorola 10
6
37
Motorola 11
6
36
E
AM
38
CIU-15
6
47
E
R
39
CIU-16
7
T
R
40
CIU-17
7
Figur
e1
Figur
e1
T
AM
41
CIU-18
7
38
E
A
42
7
39
E
W
7
7
40
41-44
E
4.2.1
A
W
4.2.1
7
7
42
43
E
T
A
W
43
44
8
Motorola 12
CIU-19
Lucent
45
46
3
CIU-20
Qualcomm
34
E
A
Change to:
(2) provides session control for the registered endpoint’s
sessions;
Change to:
(3) Provides endpoint(s) with service related information (e.g., notification of
tones/announcement together with location of additional media resources,
billing notification, and forwarding indication)
… in the home network and to proxy responses from the home network to the
mobile station.
Two boxes in Figure 1 are labeled “Breakout Gateway Control Function”. Is
one of them mislabeled?
The figure omits and consequently fails to address interception for services
addressed provided by specialized IMS based servers in the network. This
should be corrected. There are cases where communication/communication
information is communicated between the subject and the server in a secure
manner and only the server may be able to access the unencrypted
communications. Add Application Server to diagram.
Figure 2 shows a general functional Lawful Intercept (LI) architecture for a
cdma2000® Multi-…
Add new section “Functional Electronic Surveillance Architecture”
47
CIU-21
7
43-44
E/T
Resol
ved
by 31
48
CIU-22
7
44
T
A
49
CIU-23
7
45-46
T
7
47
Satisf
ied
by 51
W
50
9
Lucent
4.2.1
…and Communication-Identifying Information (CII)…
Clarification is needed that IMS SP is same as packet data network provider.
Recommend moving assumption to last sentence in paragraph.
…SP is providing both Communication Control and packet transport.
The Delivery Function (DF) can be separated into CII delivery and CC delivery
or can be combined into CII and CC delivery.
Where the text discusses the separation of a DF, the text should be clarified to
indicate whether two DFs are intended a CII DF and a CC DF (for example, the
following could be used: The Delivery Function (DF) can be separated into a
CII DF and a CC DF or can be combined into a single CII and CC DF.)
Add new text at end of paragraph: There may be one or more IAPs in the
network for both CII and CC.
This is a major shortfall. This document is limited in its capabilities to support
law enforcement by not providing for the separate delivery of VoIP.
Modify as follows: “Isolating and only reporting Voice over IP (VoIP) in the
Multi-Media Domain (MMD) is not required a part of this specification”.
Page 9 of 36
51
3
Nortel
AM
(usin
g T1.
678
soluti
on)
Comment #3: Correctly State the LI Solution Provided in the Specification
The following sentence is found at the end of 4.2.1 Architecture (italics added):
This statement is inconsistent with the purpose of the standard as stated in
1.2 Purpose (italics added):
“This Standard defines a method to support surveillance for
cdma2000® Voice over IP (VoIP) based on MMD.”
Change the sentence as follows:
52
53
11
Lucent
CIU-24
4.2.1
8
Fig 2
8
Figur
e2
W
E
A
The current LI solution in this standard provides an intercept method for all
MMD services. Isolating and only reporting Voice over IP (VoIP) in the
Multi-Media Domain (MMD) is for further study. (these insertions not needed
due to T1.678 solution)
Due to distributed nature of architecture, DFs may be in different networks and
correlation may not be possible. Should be noted that Inter-entity correlation is
not guaranteed.
Change “signalling" to “signaling” in both instances to align with spelling
elsewhere in the document.
Page 10 of 36
54
Motorola 14
8
35
T
AM
Add to section 4.2.2:
A Multi-Media IAP shall access communication-identifying packets sent or
received by the equipment, facilities, or services of an intercept subject when a
Multi-Media service is provided. IAPs may be on the Serving System or on the
Redirecting System. An IAP on the Redirecting System is only able to access
some packets delivered to the intercept subject (and possibly none of the
packets originated by the intercept subject). This paragraph is not accepted
If lawful interception is activated when a Multi-Media (e.g., VoIP) service is
already in use, interception should be initiated expeditiously. If lawful
interception is deactivated during a Multi-Media (e.g., VoIP) service,
interception should be discontinued in an expeditious manner. This paragraph
accepted as modified)
Communication-identifying information shall be sent to the Collection Function
when it is intercepted. The intercepted CII shall be delivered without
interpretation or modification, except for enveloping required to transport the
information to the Collection Function.
.
An SP shall be responsible for decrypting or decompressing, or ensuring the
government’s ability to decrypt or decompress, any communication or signaling
encrypted or compressed by a subscriber or customer, when the encryption or
compression was provided by the SP and the SP possesses the information
necessary to decrypt or decompress the communication or signaling. An SP that
provides the government with information about how to decrypt or decompress
a communication or signaling (e.g., identifying the type of compression
software used to compress the communication or signaling, directing the
government to the appropriate vendor that can provide decryption or
decompression equipment, or providing the encryption key used to encrypt the
communication or signaling) fully satisfies its obligation under the preceding
sentence. This paragraph accepted as modified. Move to 4.4 General
Capabilities.
Interception of CII does not constitute a guarantee that the intercepted CII was
also received by the subject or associates. For example, when signaling to a UE
is intercepted, it is not known whether the signaling is actually received by the
UE due to extraordinary network conditions (e.g., network congestion/failure
and air interface problems). Paragraph accepted as modified.
Only the communication (i.e., CC) transmitted to, or received from, the
intercept subject under surveillance shall be delivered to the LEA. Only the
Pageinformation
11 of 36 (i.e., CII) transmitted to, or received from, or associated with the
intercept subject’s equipment, facilities, or service under surveillance shall be
delivered to the LEA. Paragraph accepted as modified.
55
8
35
E
W
56
Motorola 13
CIU-25
8
36
E
AM
57
58
CIU-26
CIU-27
8
8
40
48
E
E
A
AM
59
CIU-28
8
49-51
T
60
61
CIU-29
CIU-30
8
8
53
53
E
T
A;
Conf
erenc
e
repor
ting
is
FFS
A
AM;
resol
ved
by
remo
ving
refs
to
spec
IAPs
W
62
10
Lucent
4.2.2
8
54
63
4
Qualcomm
4.2.2
8
54
T
W
64
CIU-31
9
8
E
A
65
CIU-32
9
9-10
T
A
Sprint
Motorola 15
9
9
14
20
E
E
A
W
66
67
4
Change section 4.2.2 from “Intercept Access Points” to “Multi-Media
Electronic Surveillance Access Points”.
With respect to Voice over IP within MMD, Intercept Access Points (IAPs) are
places in the network where VoIP communication information and content are
intercepted.
VoIP Communication-Identifying Information IAPs (CII-IAPs)
…act as Intercept Access Points. This does not preclude the use of other
network elements as IAPs in some SP implementations.
Not all CII is available at the CSCF. Some events are available at other entities
such as the MRFC (conferencing events).
CC-IAPs are as defined in Section 4.3.2.2
This section refers the reader to section 4.2.2.2 for the identification of the CCIAP. Section 4.2.2.2 does NOT identify what network element(s) may be CCIAPs but references the reader to section 4.3.2, which refers the reader to [025B] for cdma2000® packet data system and associated CII events. This
document should clearly identify what network element(s) may function as CCIAPs.
An additional bullet should be added for the Serving System Event as defined
in Section 4.2.2.2.
By looking at section 4.2.2.2 is not clear which element is responsible for the
intercepting CC.
…can be made available without the SP being unduly burdened with network
modifications. The determination of what does or does not “unduly burden”
the SP is beyond the scope of this specification. Network protocols….
…with network modifications. Network protocols (except LAES Protocol
[LAESP]) do not need to be modified solely for the purpose of passing
communication identifying information. The specific elements of
communication-identifying information that are reasonably available at any one
IAP may vary.
4.2.2.2 VoIP CC-IAPs
Add Section 4.3 “Assumptions”
Page 12 of 36
68
Motorola 16
9
20
T
W
Add to Assumptions Section:
Isolating and only reporting Voice over IP (VoIP) in the Multi-Media Domain
(MMD) is not a requirement of this specification.
Multi-Media LAES capabilities allow an SP to deliver the intercepted
communication-identifying information to an authorized LEA.
For interception to occur at an IAP, each intercept subject under surveillance must be readily identifiable within the network by identifiers appropriate and available to that IAP for that technology (e.g., IP address,
URLs). For interception of a communication involving an intercept subject, the communication must be reasonably available at the IAP. Therefore, a communication involving an intercept subject can be intercepted at
an Intercept Access Point if and only if that intercept subject is readily
identifiable at that IAP.
Synchronization of network element time-of-day clocks is not required.
There is no requirement to provide message integrity to ensure that the
message has not been altered in transmission.
There is no requirement to provide message sender authentication to ensure
the integrity of message sender identification.
Reporting of network signaling applied toward the associate is not required.
Whenever a capability is described in this Standard, it is assumed that LEAs
shall order and acquire adequate capacity in a timely manner for the capability
to be performed.
The communication-identifying information can only be delivered by a system
for activities on that system (e.g., home system, serving system).
This document defines requirements and capabilities to support electronic
surveillance of packet-mode telecommunications services in order to serve as a
standardized method to meet intercept obligations for such services.
For some types of messages used by the subject (e.g., SIP REQUEST), the
content may be transported with the communication-identifying information.
Page 13 of 36
CIU-33
Sprint
9
9
25-26
26
E
E
A
A
71
CIU-34
9
Sectio
n
4.3.1.
1
T
AM;
resol
ved
by
2005.
08.15
.20r1
72
CIU-35
9
35-36
T
A
T
A
69
70
5
73
5
Qualcomm
4.3
9
27
74
12
Lucent
4.3.1.1
9
38
9
9
41
48
10
2
10
9
T
11-13
E
CIU-36
CIU-37
75
76
77
13
80
4.3.1.1
CIU-38
78
79
Lucent
14
Lucent
Motorola 19
4.3.1.1
AM.
E
E
Remove “or an associate” (accepted)
Add new bullet after this one: An indication of redirection by an associate to
the subject relative to a subject’s communication is reported (e.g., REFER).
The text and the example are not consistent. Either the text should be changed
A
to focus on a session initiation request or the example should be changed to
BYE. Example changed to BYE
Bullet list – is this an exhaustive list or illustrative. Add Note: The above list
AM
is not an all inclusive list. At end of list before section 4.3.1.2
Remove bulleted item as it is not CII information. 4.3.1 and 4.3.1.1.stays the
AM
same. 4.3.1.2 becomes 4.3.2 and text stays the same. New 4.3.3. is registration
event bullet with new lead in text: “The cdma2000 registration event shall be
used to report subject registration information.” Section 4.3.1.3 becomes
4.3.1.2. And move Registration bullet under 4.3 and 4.3.2 Comm Content
Intercept becomes 4.3.4. Section references consistent.
Page 14 of 36
AM
9-10
10
A
A
…interest to law enforcement. The section…
This section addresses interception events associated with lawful authorizations
for which only communication-identifying information is to be delivered to the
LEA (Section 4.3.1), and interception events associated with lawful
authorizations for which content is to be delivered to the LEA (Section 4.3.2).
There is a significant shortfall in delivering the CII in this manner. Law
enforcement’s requirement is for discrete LAES messages for each event and
not the receipt of all SIP signaling messages in an encapsulated form. For
example, for each event reported, the LE expects to receive important event
related information including but not limited to: identification of subject
(including more specific identification for multiple devices and sessions),
unique identification of the VoIP communications session, etc. This shortfall is
compounded by the fact that intercepted VoIP is NOT reported to LE
separately from the rest of the SIP/IMS/MMD messages. See CIU-23.
cdma2000® SIP Message Reporting is one reporting method that intercepts and
provides CII to the CF. As part of the cdma2000® SIP Message Reporting, all
SIP signaling message that the Multi-….
The section addresses interception events associated with lawful authorizations
for which only communication-identifying information is to be delivered to the
LEA (Section 4.3.1), and interception events associated with lawful
authorizations for which both communication-identifying information and
content are to be delivered to the LEA (Section 4.3.2).
“on behalf of the intercept subject. Clarify what this means. Does this imply
that all intermediate messages (from Application Server) need to be provided to
LEA. Add the following parens…on behalf of the intercept subject (e.g.,
forking). Provided a reference: TIA-873
…Multi-Media information (Voice over IP) when …
…associate, has been invited or added to the communications…
81
4
Nortel
Resol
ved
by
contr
ibutio
n
2005.
08.15
.13r1
82
CIU-40
10
25
and
28
E
83
CIU-39
10
28
T
84
Motorola 20
10
28-29
E
10
34
T
85
6
Qualcomm
4.3.2
A.
Orig
text
delete
d by
2005.
08.15
.13r1
AM;
Orig
text
delete
d by
2005.
08.15
.13r1
A;
Orig
text
delete
d by
2005.
08.15
.13r1
R
Comment #4: Provide Flexibility for Reporting the Serving System
Text in 4.3.1.2 Cdma2000® Serving System Event implies, and this has been
interpreted to mean, that the event can only be reported for roaming scenarios.
It will take more development work to disable this ‘registration’ reporting at
the home system than just reporting the event in all cases. Add a sentence, as
follows, to allow this option:
4.3.1.2 Cdma2000® Service Serving System Event
The cdma2000® PacketDataServingSystem event specified in [025-B] shall be
used to report the serving system identity currently serving the intercept subject
when that system is not the home system. The event may be optionally reported
when the subject is registering in the home network.
…Packet Data CII [025-B]…
SIP Multi-Media CII is not defined in this document. This text also implies
that ALL Packet Data CII shall be reported. Replace “SIP Multi-Media CII”
with “SIP Message Reporting (Section 4.3.1)” and add same EG as in first para
to second paragraph.
Move sentence to new second paragraph under 4.3.2 as it discusses CC.
Remember to make changed for comment 83.
Title should be “Communication Content and CII Events Intercept The group
decided that what is currently there is sufficient and changing would be too
confusing. For CC, you always get CII as well.
Page 15 of 36
86
87
7
Qualcomm
CIU-41
4.3.2
10
37
T
10
37
T
W
based
on
2005.
08.15
.13r1
AM;
resol
ved
by
confe
renci
ng is
FFS
Communication content for VoIP based on MMD is intercepted and delivered
as part of the content of the cdma2000® packet data system [025-B].
Are Mobile IP bearers used to support signaling and VoIP CC? No. PDSN
and HA tunnel. App packets flow thru tunnel. If so, how does a P-CSCF in
visited networks ever become realized or used? In this case, how is VoIP CC
handled/reported? Thru SIP signaling mechanism. If conferencing is to be
provided, how is the bearer established with the MRFC? Internal signaling
between MRFC and MRFP is not captured. P-SCSF should be able to report
all the call legs of the conference (signaling). Where is content intercepted and
delivered to the LEA? If in a conf call and the subject on hold, content still
needs to be collected. Need to verify that if subject is on hold and it it’s the
subject’s service, then all traffic goes thru subject’s PDSN.
Page 16 of 36
88
5
Nortel
AM
Comment #5: Correct the Implied Limitation on how Subject Signaling,
to be Intercepted, is Detected
There may be a need to identify signaling associated with the subject’s
communication by means other means than a SIP URI or TEL URL
(e.g., a Conference URI). The specification should not be limiting in the
means of identifying the signaling to be reported. Change the text in
4.4. General Capabilities as follows:
4.4 General Capabilities
This section describes the general capabilities that are applicable for
Multi-Media (e.g., Voice over IP) LAES for cdma2000®:
89
Motorola 17
10
40
E
A

The CSCFs shall be capable of duplicating and forwarding to the
DF all relevant SIP messages sent or received for a target
subscriber along with other information (e.g., Case Identity used
to identify the intercept subject) as required by this specification
for CII reporting. With respect to the duplication of SIP
messages, all SIP messages to or from a targeted subscriber, and
all SIP messages executed on behalf of a targeted subscriber for
Multi-Media session control are intercepted at the IAPs and sent
to the DF.

The CII should be sent with a reliable transport mechanism as
agreed to between the SP and the LEA.

Signaling associated with the subject’s communication, to be
intercepted, may be identified by SIP URI, TEL URL, or by
other means such as a Conference URI
Added definition of Conference URI to definitions; added a statement on
conferencing for mapped that states Event mapping of conferencing is
FFS..
Add “Communication Associated Information Surveillance Service Description
– Communication Identifying IAP” as Section 4.4
Page 17 of 36
90
Motorola 18
10
40
T
Add to section 4.4:
AM
Communication associated information surveillance services access information pertains to communication and service processing. This processing
may span several functional entities.
The CII-IAP provides expeditious access to the reasonably available communication-identifying information for communications made by an intercept
subject or for communications made to an intercept subject.
A communication event is a user action or signal that may cause a communication state change. These events are not intended to reflect a particular
technology, but to describe the event in general. Move this paragraph to 4.3
and clarify that CII only.
The CII-IAP shall access the communication-identifying information for the
intercept subject unobtrusively. Access to communication-identifying information shall not deny the availability of any service to either the subject or
associates
Replace the phrase “target subscriber” with the phrase “intercept subject”
Add at end of last sentence in first bullet:
“as required for CII reporting”.
The CII shall be sent with a reliable transport mechanism as agreed to between
the SP and the LEA. This negotiation may include provisions of ensuring
message integrity of intercept messages to ensure that the messages were not
altered during transmission as well as message sender authentication.
10
10
46
52
E
E
A
A
93
CIU-42
Motorola 21
CIU-43
10
53
T
R
94
CIU-44
10
55
T
95
Motorola22
11
21-25
T
Resol
ved
by
com
ment
88
W
11
23
E
A
91
92
96
8
Qualcomm
4.4.2
The identification of traffic should not be limited to SIP URI and TEL URL.
Terminal identity and subscription identity may also be used. Identification of
VoIP CC to law enforcement may be by use of IP Addresses and port numbers.
Change:
The following timing requirements from shall apply to the delivery of CII:
A call-identifying message must be sent from the carrier’s IAP to the LEA’s
Collection Function within eight seconds of receipt of that message by the IAP
at least 95% of the time, and with the call event time-stamped to an accuracy of
at least 1 second.
Replace “must” to “shall”.
Page 18 of 36
97
CIU-45
11
23-25
E
A
98
CIU-46
11
25
T
AM
99
CIU-47
11
Sectio
n
4.4.3
T
Resol
ved
by
2005.
08.15
.13r1
Resol
ved
by
2005.
08.15
.13r1
100
8a
Nortel
A communication-identifying message must be sent from the carrier's IAP to
the LEA's Collection Function within eight seconds of receipt of that message
by the IAP at least 95% of the time, and with the communication event timestamped to an accuracy of at least 200 milliseconds.
Add new text after text on CII:
The following timing requirements shall apply to the delivery of intercepted
VoIP content:
Intercepted VoIP content shall be expeditiously transmitted by the IAP towards
the DF with its interception.
Is this true for back-to-back calls when the signaling is manipulated in the
network? How is correlation done for such disjointed messages?
Comment #8: Provide the Ability to Correlate the Intercepted SIP
Signaling with its Intercepted Content and Provide the Flexibility
to Correlate the SIP CII as Necessary
a) Given a subject may have multiple, concurrent PPP connections being
intercepted, there is a need to be able to correlate the intercepted SIP signaling
with its intercepted content. b) Given that a network application served by the
S-CSCF can alter SIP signaling in such a way as to prevent external correlation
(e.g., forking) a means is needed to allow that correlation.
4.4.3
Correlation of CII-to-CC and CII-to-CII
In cases where multiple, independent subject CCs are being intercepted
(see [025-B] for CC interception), there may be a need to correlate the
intercepted CII for that CC with its CC. A correlation value is defined to
provide that capability.
101
CIU-48
11
30-34
T
Resol
ved
by
2005.
08.15
.13r1
Correlation of the SIP messages involved in a communication between the
subject and associate(s) is typically done via the information in the actual SIP
messages reported (e.g., Request-URI, To, From, Call-ID, and CSeq).
However, there may be cases which prevent this correlation externally.
A correlation value is defined to provide this capability.
What if the Call-ID is changed by the CSCF? How is correlation provided
between the CII messages?
Page 19 of 36
102
6
103
104
6
Sprint
11
31
T
Resol
ved
by
2005.
08.15
.13r1
CIU-49
11
33-34
T
Resol
ved
by
2005.
08.15
.13r1
AM
Nortel
Correlation of the SIP messages between CII and CC for a subject involved in
multiple SIP sessions is critical. A correlation parameters shall be used to
enable correlation of SIP messages containing CII with SIP messages
containing CC when delivered to the LEA. These parameters need not be the
same value between CII and CC messages, but shall provide a mechanism for
correlation of the CC and CII messages for the same session for the same
subject.
…URI, To, From, Call-ID, and CSeq).
Reason for deleting text: The correlation of CC and CII is must be within the
scope of this document as without correlation, this delivery of intercepted
communication can be rendered meaningless. See CIU-51.
Comment #6: Correct the Grammar and the Implied Limitation on How
Subject Signaling, to be Intercepted, is Detected
Under 5 Stage 2 Description: a) correct the implied restraint of identifying
subject communication signaling only via the SIP URI of the subject; b) correct
the grammar. Correct the expansion of CF (not the first instance - see 4.3.1.1).
5
Stage 2 Description: Network Perspective
This section identifies the triggering events and usage for the VoIP CII
event messages, identifies and describes the information to be reported with
each VoIP CII event message, and also describes the application level
CC delivery format and associated delivery information.
105
CIU-50
12
11
T
Resol
ved
by
2005.
08.15
.13r1
The CII-IAP shall provide to the Delivery Function (DF) the intercepted CII . The DF
shall send the intercepted CII to the CF.
Some SIP messages contain content. For CII-only orders, that content should
be removed. However, some SIP body information may be CII, such as some
information contained in the SDP (see text 39-40). This specification needs to
account for this.
Page 20 of 36
106
Motorola 22
12
12
T
W
Add 5.1 “Stage 2 Methodology”:
The methodology and organization for the development of the Stage 2 network
perspective is described. A network reference model is developed and then
information flows between functional entities over reference points are
described.
Information is described in terms of a causing event and information associated
with that event. Within each service description there is a set of events to
support the particular service.
Stage 2 for Multi-Media LAES deals with the movement of information
between the Access, Delivery, and Collection Functions. The Stage 2
description focuses on the information being transferred, rather than the transfer
mechanism.
Page 21 of 36
107
Motorola 23
12
12
T
W
Add 5.2 “Stage 2 Network Reference Model”:
The Network Reference model, as shown in Figure XX, consists of a set of
functional entities and interface reference points between some of those
functional entities. The functional entities provide the functions of the system,
and an interface reference point allows information to be exchanged between
the two functional entities connected by the interface reference point.
Telecommunication
Service Provider
Access
Function
d
a
Service Provider
Administratiion
Function
c
Delivery
Function
e
Law Enforcement
Administration
Function
Law Enforcement Agency
Page 22 of 36
b
Collection
Function
The Scope of this
Standard is limited to
the e reference point.
108
Motorola 24
12
12
E
W
Add explanation of Functional Entities:
Access Function (AF)
The Access Function, through its constituent Intercept Access Points (IAPs), is
responsible for providing access to an intercept subject’s communications,
communication identifying information, or both.
The Access Function typically includes the ability:
 to access intercept subject’s communication-identifying
information unobtrusively and make the information
available to the Delivery Function;

to access intercept subject communication content
unobtrusively and make the communication content available
to the Delivery Function; and

to protect (e.g., prevent unauthorized access, manipulation,
and disclosure) intercept controls, intercepted communication
content
and
communication-identifying
information
consistent with SP security policies and practices.
Delivery Function (DF)
The Delivery Function is responsible for delivering intercepted communications and communication-identifying information to one or more Collection
Functions.
The Delivery Function typically includes the ability:

Page 23 of 36
to accept communication content for each intercept subject
over one or more channels from the Access Function(s);
(Cont.)

to deliver communication content for each intercept subject
over one or more Communication Content links to a
Collection Function;

to accept communication -identifying or packet-mode content
information for each intercept subject over one or more
channels and deliver that information to the Collection
Function over one or more Communication-identifying
information links;

to ensure that the communication-identifying information and
communication content delivered to a Collection Function is
authorized for a particular LEA;

to duplicate and deliver authorized communicationidentifying information and content for the intercept subject
to one or more Collection Functions (up to a total of five);
and

to protect (e.g., prevent unauthorized access, manipulation,
and disclosure) intercept controls, intercepted communication
content and communication-identifying information
consistent with SP security policies and practices.
Cont.
Collection Function
The Collection Function is responsible for collecting lawfully authorized
intercepted communications (i.e., communication content) and communicationidentifying information for an LEA. The Collection Function is the
responsibility of the LEA.
The Collection Function typically includes the ability:

Page 24 of 36
to receive and process CII and CC for each intercept subject.
Cont.
Service Provider Administration Function (SPAF)
The Service Provider Administration Function is responsible for controlling
SP electronic surveillance functions.
The functions of the SPAF are beyond the scope of this Standard.
Law Enforcement Administration Function (LEAF)
The Law Enforcement Administration Function is responsible for controlling
LEA electronic surveillance functions. The Law Enforcement Administration
Function is the responsibility of the LEA.
The functions of the LEAF are beyond the scope of this Standard.
Page 25 of 36
109
Motorola 25
12
13
W
Add Interface Reference Point Information:
Reference Point a
Reference point a, or the a-interface, is the interface between the Service
Provider Administration Function and the Access Function.
Reference point a is beyond the scope of this Standard.1
Reference Point b
Reference point b, or the b-interface, is the interface between the Law
Enforcement Administration Function and the Collection Function.
Reference point b is beyond the scope of this Standard.
Reference Point c
Reference point c, or the c-interface, is the interface between the Service
Provider Administration Function and the Delivery Function.
Reference point c is beyond the scope of this Standard.1
Reference Point d
Reference point d, or the d-interface, is the interface between the Access
Function and the Delivery Function.
Reference point d is beyond the scope of this Standard.1
Reference Point e
Reference point e, or the e-interface, is the interface between the Delivery
Function and the Collection Function.
Reference point e is defined by this Standard
1
This reference point is required to protect (e.g., prevent unauthorized access, manipulation, and disclosure) 1) the privacy and security of
communications and communication-identifying information not authorized to be intercepted; and 2) information regarding the government’s
interception of communications and access to communication-identifying information.
Page 26 of 36
110
Motorola 26
12
13
T
AM;
2005.
08.15
.07
Add Message Descriptions:
The communication events described in Stage 1 convey the basic information
for reporting the disposition of a communication. This section describes those
events and supporting information.
Each message is described as consisting of a set of parameters. Each parameter
is either:
111
Motorola 27
12
15
T
W
112
CIU-51
12
26-36
T
12
12
36-37
39-40
Resol
ved
by
2005.
08.13
r1
W
W
113
114
15
16
Lucent
Lucent
5.1.1.1
5.1.1.1

mandatory (M)—required for the message,

conditional (C)—required in situations where a condition
(defined in the usage column of the table where it occurs) is
met, or

optional (O)—provided
implementation.
at
the
discretion
of
the
The information to be carried by each parameter is identified. Please note that
both optional and conditional parameters at Stage 2 are considered to be
OPTIONAL syntactically in ASN.1 Stage 3 descriptions. The Stage 2 inclusion
requirements take precedence over the Stage 3 syntax..
Add 5.1.1 “Underlying Data Transmission”:
The messages defined by this Standard are an Open System Interconnection
(OSI) Layer 7 or Application Layer protocol. The protocol for the messages is
called the lawfully Authorized Electronic Surveillance Protocol (LAESP). The
LAESP messages shall be delivered employing a standard or widely used data
communication protocol.
Law Enforcement needs to have a method to correlate all messages related to
the surveillance subject. SPs must provide a method to correlate all messages
for each communication session within their network. For example, networks
can provide anonymization, in which case, the SP needs to provide Law
Enforcement with the “tie” between the messages from the user side to those on
the network side.
Add an example of when this situation can occur..
Clarification is also needed with respect to the handling of SIP body
information other than application SIP.
Page 27 of 36
115
CIU-52
12
41-42
E
W
116
CIU-53
13
Table
1
T
117
CIU-54
13
T
118
CIU-55
13
Table
1
Table
1
AM;
resol
ved
by pheade
r
stuff
W
119
CIU-56
13
Table
1
T
T
Resol
ved
2005.
08.15
.13r1
Resol
ved
2005.
08.15
.13r1
Messages are described as consisting of a set of parameters. Each parameter is
either “mandatory” (M) meaning that it is required for the message;
“conditional” (C) meaning that it is required in situations when a condition
(defined in the usage column of the table) is met; or “optional” (O) meaning
that it is provided at the discretion of the implementation. The information to
be carried by each parameter is identified. Both optional and conditional
parameters are considered to be optional syntactically in ASN.1 Stage 3
descriptions.
Law Enforcement requires, at a minimum, location information for the intercept
subject at the beginning and end of the VoIP communication. This critical
capability is not provided in this document nor is the capability to provide
location updates. These capabilities need to be satisfied.
This document does not clearly specify where the case identity is generated.
How is correlation done between CII and CC messages? See CIU-49 and CIU51.
The table is lacking a number of parameters (e.g., subjectID, callID) which are
needed to address comment CIU-34.
Page 28 of 36
120
8b
Nortel
Resol
ved
2005.
08.15
.13r1
5.1.1.1 cdma2000 SIP Message Reporting
Table 1: CDMA2000® SIP Message Reporting Parameters
Parameter
CaseIdentity
IAPSystemIdentity
MOC
M
C
TimeStamp
M
CorrelationValues
C
SIPMessage
M
121
145
7
1
Sprint
SSG
13
5.1.1.2
8
21
T
E
Description/Conditions
Identifies the intercept subject.
Included to identify the system
containing the IAP when the
underlying data carriage does not
imply that system.
Time and date that the event was
detected.
A unique value for correlating CC
and CII when CII and CC are both
reported. May also be used for
correlating CII when necessary.
The signalling message received
from the intercept subject, sent to
the intercept subject, or sent or
received on behalf of the intercept
subject, which stimulated the
sending of the SIP Message
Reporting. Only the message is
included (i.e., without the IP and
transport headers).
Resol
ved
2005.
08.15
.13r1
Insert a parameter into the table:
A
Change “cmda2000” to “cdma2000”
Correlation Value
Page 29 of 36
C
Identifies a CC or CII
message flow for
purposes of correlation
at LEA.
122
123
Motorola 28
Motorola 29
14
14
5
5
T
T
W
W
Add Section 6.1 “Protocol Definition”:
A protocol is defined in three basic aspects:
a. Transfer Syntax,
b. Transfer Semantics, and
c. Procedures.
The transfer syntax defines the messages passed between two functional
entities. This definition may include various structures, but eventually defines
the entire message structure down to the bit level. The syntax specifies the ways
in which bits of messages are encoded for exchanging information between two
functional entities.
The transfer semantics assigns meanings to the bits, bytes and structures of the
transfer syntax. The exchanges of meanings allows the functional entities to
share information and to act upon that information.
Procedures define the behavior of the functional entities. Procedures define
which functional entities are allowed to initiate a particular transaction.
Procedures define the possible responses to a given stimulus especially when
dependent upon prior exchanges.
Add “CII Parameter Encoding Objectives”:
The following are the objectives of the parameter encoding:

Allow flexible usage of the LAESP to transport a variety
of information.
 Provide a consistent and complete syntax for transferring
information.
 Facilitate implementation of message encoding and
decoding software by using standardized techniques.
 Allow as much syntactical checking as practical to be
performed by the message parsers rather than
deferring to the application.
124
CIU-59
14
32
T
W
Allow for parameter extension and modification throughout the life of the
protocol.
Has anyone actually compiled the ASN.1 to ensure that there are no errors?=
Page 30 of 36
125
8c
Nortel
Resol
ved
by
2005.
08.15
.14
6.2
Abstract Syntax Modules
CDMA2000-sip-MessageReporting::= SEQUENCE {
caseId
[0]
CaseIdentity,
iAPSystemId
[1]
IAPSystemIdentity
timestamp
[2]
TimeStamp,
correlationValues
[3]
CorrelationValues
sipMsg
[4]
SIPMessage
}
OPTIONAL,
OPTIONAL,
-- Parameter Definitions
SIPMessage ::= OCTET STRING
CorrelationValues ::= CHOICE {
cii-cc-Correlation
[0] OCTET STRING, -- correlates CII-to-CC
cii-cii-Corrrelation
[1] OCTET STRING, -- correlates CII-to-CII
both-CorrrelationValues [2] SEQUENCE {
-- provides both CII-toCC and CII-to-CII correlation
cii-CC [0] OCTET STRING,
cii-CII [1] OCTET STRING
}
END -- of CDMA2000-SIP-CII-Module
Page 31 of 36
126
9
Nortel
Resol
ved
2005.
08.15
.13r1
Comment #9: Hard Code the Module ID in the ASN.1
6.2
Abstract Syntax Modules
CDMA2000-SIP-CII-Module
{iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) cdma2000(1) ciisip(2) version-1(0)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
IMPORTS
CaseIdentity, IAPSystemIdentity, Timestamp
FROM Laesp-j-std-025-b {iso(1) member-body(2) us(840) tia(113737) laes(2)
tr45(0) j-std-025(0) j-std-025-b(2) version-1(0)}
cdma2000-SIP-CII-Module-OID OBJECT IDENTIFIER ::= {iso(1) memberbody(2) us(840) tia(113737) laes(2) tr45(0) cdma2000(1) cii-sip(2) version1(0)}
-- OID for CDMA2000-SIP-CII-Module
CDMA2000-SIP-Protocol ::= SEQUENCE {
protocolIdentifier
OBJECT IDENTIFIER {cdma2000-SIP-CIIModule-OID},
mmdMessage
CDMA2000mmdMessage
}
127
CIU-57
14
52-56
E
Resol
ved
2005.
08.15
.14
Change the ASN.1 as follows. Simplifies construct and eliminates unused
parts:
mmdMessage CDMA2000mmdMessageCDMA2000-sip-MessageReporting
CDMA2000mmdMessage::=CHOICE {
SipMessage [0] CDMA2000-sip-MessageReporting,
}
Page 32 of 36
CIU-58
128
129
130
17
131
8
Lucent
Motorola 30
Sprint
Annex A
15
6
E
15
16
15
4
T
Resol
ved
2005.
08.15
.13r1
W
W
16
20
T
W
CDMA2000-sip-MessageReporting ::=SEQUENCE {
SIPMessage::= OCTET STRING. Limit should be specified.
Annex A:
Change from Normative to Informative as it does not add any requirements to
the standard.
This section defines a minimal list of SIP messages to be intercepted and
reported for VoIP based on MMD and the mapping of SIP messages to
surveillance messages defined in this Standard.
Page 33 of 36
132
11
Nortel
AM;
resol
ved
by
2005.
08.15
.13r1
Comment #11: Correct the Reference in Annex A and Clean up the Text
Annex A SIP CII Messages Mapping (Normative)
This annex is normative and is considered part of this Standard.
This annex provides the message and parameter mappings from SIP standard
signaling to the surveillance messages reported to the LEA by the SP for a
VoIP intercept.
When information reporting is triggered by SIP signaling as described in
4.3.1.1, SIP messages are intercepted at a CII-IAP and presented to the DF.
The DF sends the CII to the CF. The message mappings in this annex are
described from the perspective of the ‘e’ interface (the interface between the
DF and the CF).
A.1
Message Mappings
This section defines a non-exhaustive list of SIP messages to be intercepted and
reported for VoIP based on MMD and the mapping of SIP messages to CII
surveillance messages defined in this Standard.
Table A-1: SIP Message Mapping
SIP Request
Messages
INVITE
ACK
BYE
CANCEL
REGISTER
REFER
NOTIFY
133
134
9
Qualcomm
CIU-1
Annex A
16
Genera
l
11
E
T
A
Resol
ved
2005.
08.15
.13r1
SIP
Response
Messages
1xx, 2xx,
3xx, 4xx,
5xx, 6xx
CII Surveillance
Message
CDMA2000-sipMessage-Reporting
Description
CII
Surveillance
Message
Parameter
sipMsg [3]
SIPMessage
The intercepted SIP
message is stored in
parameter sipMsg [3]
of CII surveillance
message CDMA2000sip-MessageReporting.
There is no section 6.2.1.1.
There is no solution provided to address the reporting of Dialed Digits. That is
the Dialed Digit Extraction capability is not addressed by the VoIP LI solution
in the document. This is a major shortfall..
Page 34 of 36
CIU-2
135
136
7
Nortel
Genera
l
T
Resol
ved
by
com
ment
54
resol
ution
A
This document does not address the encryption/decryption and
compressions/decompression. SPs have a responsibility if they provided
encryption or compression to ensure decryption/decompression during delivery
to Law Enforcement. This omission is a shortfall. See comment 54 resolution.
Comment #7: Cdma2000 Trade Mark Question
Both cdma2000® and CDMA2000® are registered trademarks. Cdma2000 is
also used in the specification. Is Cdma2000® a registered trade mark?
137
10
Nortel
AM;
resol
ved
by
confe
rence
repor
ting
FFS.
138
1
Ericsson
W
139
2
Ericsson
W
140
141
3
4
Ericsson
Ericsson
W
W
Comment #10: Further Study is Needed on How to Report Multi-Party
Events and Subject Conference on Hold
Add the following to the end of 4.3.1.1 cdma2000® SIP Message Reporting
Event:
Reporting of Multi-Party events when using network CMS services (e.g.,
adding and removing parties to a conference call) is for further study.
Reporting of communication events and CC for subject conferences placed on
hold using network based CMS services is for further study..
1) It's technically unreasonable to do service level interception at CSCF on
SIP signalings, meaning the CSCF has to single out SIP messages for the
VoIP session.
2) It's technically unreasonable to do service level interception at PDSN on
content of communications. This means the PDSN has to extract the
packets pertaining to a VoIP conversation, from the data stream of an
established packet data session.
3) J-STD-025-B will have to be reworked as the consequence of 2).
4) cdma2000 will be deviating from WCDMA thought they're both using
the same IMS/MMD.
Page 35 of 36
142
1
Nokia
W
(1) The document seeks to provide an intercept standard specifically for
one service (VoIP) that is provided over an MMD network. It is Nokia's
opinion that an intercept specification for MMD does not need to
differentiate services in this manner - all services can be generically
intercepted at the S-CSCF. Nokia's proposal would be therefore to
replace "VoIP service based on MMD" with MMD throughout the
document.
Although we do recognize that, at present, the document does not
require service (VoIP) specific intercept, it is our opinion that this is
safeguarded only by the phrase in section 4.2.1
"Isolating and only reporting Voice over IP (VoIP) in the Multi-Media Domain
(MMD) is not a part of this
specification. "
We consider that it would be comparatively easy to remove such a small
caveat from the document at a later date. A consequence of this would
be that service based intercept would then be implied by the
specification.
See SHS liaison for resolution (to be received).
143
2
Nokia
W
(2) For this particular specification, due to the ongoing issues with the
set up of the CWG (a group within TIA distinct from the technical
working groups whose charter would be to explicitly consider CALEA
issues), at no stage has any consideration been made as to what in the
document would be needed for CALEA compliance and what would be
additional capabilities. Since CALEA gives industry the opportunity to
take the first stab at what is believe to be within or outside of CALEA,
this represents a serious omission. An example issue would be that of
timing requirments, which is such a contentious subject that it was
recently the subject of a industry JEM. The purpose of the JEM was to
determine an industry wide position on the issue of CALEA timing
requirements in packet networks. In view of this, Nokia propose that
CALEA complaince is considered before accepting this specification as
an American national standard.
144
1
Lucent
W
PN-3-0196 is not sufficient as is as a standalone document. More descriptive
text is needed, particularly to describe the underlying infrastructure on which
the MMD Services (VoIP) are supported. References are not clear enough.
Text from J-STD-025B (e.g., for call content) should be included, or very
specific references to sections of J-STD-025B.
Page 36 of 36