1、 ATIS-1000022 WIRELINE SERVICE PROVIDER JOB AID FOR VOP AND IAS LAES STANDARDS TECHNICAL REPORT The Alliance for Telecommunication Industry Solutions (ATIS) is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations s
2、tandards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry committees and its Incubator Solutions Program. NOTE - The users a
3、ttention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to whether use of an invention covered by patent rights will be required, and if any such use is requi
4、red no position is taken regarding the validity of this claim or any patent rights in connection therewith. ATIS-1000022, Wireline Service Provider Job Aid for VoP and IAS LAES Standards Is an ATIS Standard developed by the Lawfully Authorized Electronic Surveillance (LAES) Subcommittee under the AT
5、IS Packet Technologies and Systems Committee (PTSC). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2007 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduc
6、ed in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS-1000022 Technical Report on WIRELINE SERVICE PROVIDER JOB AID FOR VOP
7、 AND IAS LAES STANDARDS Secretariat Alliance for Telecommunications Industry Solutions Approved September 2007 Abstract This document provides guidance designed to assist VoP and IAS providers in utilizing available industry standards (ATIS-1000678.2006 and ATIS-1000013.2007) to address lawful inter
8、cept requests from law enforcement. ATIS-1000022 ii FOREWORD The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved understanding between carriers, customers, and manufacturers. The Packet Technologies and Systems Committee (PTSC) - formerly T1S1 - develops a
9、nd recommends standards and technical reports related to services, architectures, and signaling, in addition to related subjects under consideration in other North American and international standards bodies. PTSC coordinates and develops standards and technical reports relevant to telecommunication
10、s networks in the U.S., reviews and prepares contributions on such matters for submission to U.S. ITU-T and U.S. ITU-R Study Groups or other standards organizations, and reviews for acceptability or per contra the positions of other countries in related standards development and takes or recommends
11、appropriate actions. Suggestions for improvement of this document are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, PTSC Secretariat, 1200 G Street NW, Suite 500, Washington, DC 20005. At the time it approved this document, PTSC, which is responsible for the
12、 development of this Technical Report, had the following members: B. Hall, PTSC Chair J. Zebarth, PTSC Vice-Chair C. Underkoffler, ATIS Chief Editor R. McNealy, PTSC Technical Editor Organization Represented Name of Representative AcmePacket Kevin Klett Alcatel-Lucent Stuart Goldman AT or 2) Content
13、 Associated Communications Identifying Information (CACmII) - see 6.1.2. CmII is “reasonably available” to an IASP if it is present at an intercept access point and can be made available without the provider being unduly burdened with network modifications. CmII is delivered by the set of messages d
14、efined in ATIS-1000013.2007 and the set of mandatory and conditional parameters contained therein. 6.1.1 Access Associated CmII (AACmII) Access Associated Communications Identifying Information (AACmII) is information associated with communication between the subscriber and the IAS network for the p
15、urposes of login, logout, access authorization, access authentication, or resource allocation caused by the use of, or attempted use of, the IAS network by the subscriber. 6.1.2 Content Associated CmII (CACmII) Content Associated Communications Identifying Information (CACmII) is information associa
16、ted with the delivery and routing of the subscriber packets in the network (e.g., the headers of the IP packets). 6.2 Communication Content (CmC) Communication Content (CmC) is the full IP packet stream to and from the subject. 7 LAES SIGNALING AND CONTENT AVAILABILITY AND CORRELATION 7.1 Availabili
17、ty The availability of signaling information (CII or CmII) and content (CC or CmC) for a specific court order depends upon the specific service provider scenario. The tables in Clause 8 provide details as to when the signaling information and content are available for delivery to an LEA. 7.2 Correla
18、tion LAES data correlation refers to the linking of signaling messages with content messages. It is the responsibility of the SP to provide signaling messages and content messages to Law Enforcement with ATIS-1000022 the proper identifying header information on all messages delivered to Law Enforcem
19、ent. Where a single SP delivers both the signaling messages and content messages, the SP populates correlation parameters to allow Law Enforcement to determine the association between the signaling and content. It is Law Enforcements responsibility to associate the appropriate signaling and content
20、messages with a given Lawful Intercept activity. Due to the distributed nature of IP based services (e.g., access, ISP, and VoP may be provided by three separate service providers), there are cases in which the service providers are not aware of any correlation between signaling and content and the
21、messages delivered to an LEA will not contain correlation parameters. Correlation across separate networks is the responsibility of the LEA. For example, in situations where signaling messages are delivered to the LEA by the VoP service provider (e.g., a Pen Register order served on a VoP TN) and co
22、ntent is delivered to the LEA by the IP network access provider (e.g., a Title III order served on a broadband access line), it is the LEAs responsibility to perform the task of data correlation. 8 APPLICABILITY OF WIRELINE VOP AND IAS LAES STANDARDS This clause addresses the use of LAES standards t
23、o provide surveillance information to an LEA in common SP scenarios. Figure 3 provides a high level depiction of the SP functionality involved in providing Internet Access and VoP and the LAES support that they provide. Any or all of the service providers may be requested, through a lawfully authori
24、zed electronic surveillance court order, to deliver various types of surveillance information to an LEA collection site. The particular messages to be generated and their source will depend on the SP scenario, the type of court order served (e.g., pen register, trap and trace, Title III) and the fac
25、ility or subject upon which the court order is served (e.g., a DSL line2, a user name, a VoP TN or URI). Figure 3 - SP Scenarios 2Identification of the DSL line varies by network implementation (e.g., MAC address, ATM VPI/VCI, telephone number, subscription identity). 7 ATIS-1000022 8 The following
26、sections address various service provider scenarios and indicate, for a type of court order and type of subject, what LAES information needs to be delivered, and what standards document applies. 8.1 Service Provider Scenario 1 In this scenario, all three services (Access, ISP, and VoP) are provided
27、by the same SP. Table 1 - Service Provider Scenario 1 Target of Court Order Type of Court Order Service Provider Implementing Court Order LAES Information Delivered to LI VoP party (e.g., TN or URI) PR/TT Access/ISP/VoP CII per ATIS-1000678.2006. VoP party (e.g., TN or URI) Title III Access/ISP/VoP
28、CII and CC per ATIS-1000678.2006. Access ID (e.g., DSL) PR/TT Access/ISP/VoP CmII per ATIS-1000013.2007. Access ID (e.g., DSL) Title III Access/ISP/VoP CmII and CmC per ATIS-1000013.2007. ISP User Account (e.g., ) PR/TT Access/ISP/VoP CmII per ATIS-1000013.2007. ISP User Account (e.g., ) Title III A
29、ccess/ISP/VoP CmII and CmC per ATIS-1000013.2007. ATIS-1000022 9 8.2 Service Provider Scenario 2 In this scenario, Access and ISP services are provided by one SP, while the VoP service is provided by a different SP. Table 2 - Service Provider Scenario 2 Target of Court Order Type of Court Order Serv
30、ice Provider Implementing Court Order LAES Information Delivered to LI VoP party (e.g., TN or URI) PR/TT Access/ISP CII for this court order is not reasonably available to this carrier. Access/ISP should refer LEA to the VoP provider, if it is known. VoP party (e.g., TN or URI) PR/TT VoP CII per ATI
31、S-1000678.2006. VoP party (e.g., TN or URI) Title III Access/ISP CII and CC for this court order are not reasonably available to this carrier. Access/ISP should refer LEA to the VoP provider, if it is known. VoP party (e.g., TN or URI) Title III VoP CII and CC per ATIS-1000678.2006. Access ID (e.g.,
32、 DSL) PR/TT Access/ISP CmII per ATIS-1000013.2007. Access ID (e.g., DSL) PR/TT VoP CmII for this court order is not reasonably available to this carrier. VoP provider should refer LEA to the Access/ISP, if it is known. Access ID (e.g., DSL) Title III Access/ISP CmII and CmC per ATIS-1000013.2007. Ac
33、cess ID (e.g., DSL) Title III VoP CmII and CmC for this court order are not reasonably available to this carrier. VoP provider should refer LEA to the Access/ISP, if it is known. ISP User Account (e.g., ) PR/TT Access/ISP CmII per ATIS-1000013.2007. ISP User Account (e.g., ) PR/TT VoP CmII for this
34、court order is not reasonably available to this carrier. VoP provider should refer LEA to the Access/ISP, if it is known. ISP User Account (e.g., ) Title III Access/ISP CmII and CmC per ATIS-1000013.2007. ISP User Account (e.g., ) Title III VoP CmII and CmC for this court order are not reasonably av
35、ailable to this carrier. VoP provider should refer LEA to the Access/ISP, if it is known. ATIS-1000022 10 8.3 Service Provider Scenario 3 In this scenario, the Access service is provided by one SP, while the ISP and VoP services are provided by a different SP. Table 3 - Service Provider Scenario 3 T
36、arget of Court Order Type of Court Order Service Provider Implementing Court Order LAES Information Delivered to LI VoP party (e.g., TN or URI) PR/TT Access CII for this court order is not reasonably available to this carrier. Access provider should refer LEA to the VoP provider, if it is known. VoP
37、 party (e.g., TN or URI) PR/TT ISP/VoP CII per ATIS-1000678.2006. VoP party (e.g., TN or URI) Title III Access CII and CC for this court order are not reasonably available to this carrier. Access provider should refer LEA to the VoP provider, if it is known. VoP party (e.g., TN or URI) Title III ISP
38、/VoP CII and CC per ATIS-1000678.2006. Access ID (e.g., DSL) PR/TT Access CmII per ATIS-1000013.2007. Access ID (e.g., DSL) PR/TT ISP/VoP CmII for this court order is not reasonably available to this carrier. ISP/VoP provider should refer LEA to the Access provider, if it is known. Access ID (e.g.,
39、DSL) Title III Access CmII and CmC per ATIS-1000013.2007. Access ID (e.g., DSL) Title III ISP/VoP CmII and CmC for this court order are not reasonably available to this carrier. ISP/VoP provider should refer LEA to the Access provider, if it is known. ISP User Account (e.g., ) PR/TT Access AACmII ma
40、y be available to the Access Provider if it performs the Reg-F, otherwise, CmII for this court order is not reasonably available to this carrier. Access provider should refer LEA to the ISP, if it is known. ISP User Account (e.g., ) PR/TT ISP/VoP CmII per ATIS-1000013.2007. ISP User Account (e.g., )
41、 Title III Access AACmII may be available to the Access Provider if it performs the Reg-F, otherwise, CmII and CmC for this court order are not reasonably available to this carrier. Access provider should refer LEA to the ISP, if it is known. ISP User Account (e.g., ) Title III ISP/VoP CmII and CmC
42、per ATIS-1000013.2007. ATIS-1000022 11 8.4 Service Provider Scenario 4 In this scenario, the Access and VoP services are provided by one SP, while the ISP service is provided by a different SP. Table 4 - Service Provider Scenario 4 Target of Court Order Type of Court Order Service Provider Implement
43、ing Court Order LAES Information Delivered to LI VoP party (e.g., TN or URI) PR/TT Access/VoP CII per ATIS-1000678.2006. VoP party (e.g., TN or URI) PR/TT ISP CII for this court order is not reasonably available to this carrier. ISP should refer LEA to the VoP provider, if it is known. VoP party (e.
44、g., TN or URI) Title III Access/VoP CII and CC per ATIS-1000678.2006. VoP party (e.g., TN or URI) Title III ISP CII and CC for this court order are not reasonably available to this carrier. ISP should refer LEA to the VoP provider, if it is known. Access ID (e.g., DSL) PR/TT Access/VoP CmII per ATIS
45、-1000013.2007. Access ID (e.g., DSL) PR/TT ISP CmII for this court order is not reasonably available to this carrier. ISP should refer LEA to the Access provider, if it is known. Access ID (e.g., DSL) Title III Access/VoP CmII and CmC per ATIS-1000013.2007. Access ID (e.g., DSL) Title III ISP CmII a
46、nd CmC for this court order are not reasonably available to this carrier. ISP should refer LEA to the Access provider, if it is known. ISP User Account (e.g., ) PR/TT Access/VoP AACmII may be available to the Access Provider if it performs the Reg-F, otherwise, CmII for this court order is not reaso
47、nably available to this carrier. Access/VoP provider should refer LEA to the ISP, if it is known. ISP User Account (e.g., ) PR/TT ISP CmII per ATIS-1000013.2007. ISP User Account (e.g., ) Title III Access/VoP AACmII may be available to the Access Provider if it performs the Reg-F, otherwise, CmII an
48、d CmC for this court order are not reasonably available to this carrier. Access/VoP provider should refer LEA to the ISP, if it is known. ISP User Account (e.g., ) Title III ISP CmII and CmC per ATIS-1000013.2007. ATIS-1000022 12 8.5 Service Provider Scenario 5 In this scenario, the Access, ISP, and
49、 VoP services are provided by three separate SPs. Table 5 - Service Provider Scenario 5 Target of Court Order Type of Court Order Service Provider Implementing Court Order LAES Information Delivered to LI VoP party (e.g., TN or URI) PR/TT Access CII for this court order is not reasonably available to this carrier. Access provider should refer LEA to the VoP provider, if it is known. VoP party (e.g., TN or URI) PR/
