ATIS 1000052-2012 Byte Count Reporting in an Internet Access and Services LAES Environment.pdf

《ATIS 1000052-2012 Byte Count Reporting in an Internet Access and Services LAES Environment.pdf》由会员分享，可在线阅读，更多相关《ATIS 1000052-2012 Byte Count Reporting in an Internet Access and Services LAES Environment.pdf（10页珍藏版）》请在麦多课文档分享上搜索。

1、 TECHNICAL REPORT ATIS-1000052 BYTE COUNT REPORTING IN AN INTERNET ACCESS AND SERVICES LAES ENVIRONMENT ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communica

2、tions industry. More than 200 companies actively formulate standards in ATIS Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emergi

3、ng Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for th

4、e 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Ins

5、titute (ANSI). For more information, please visit . Notice of Disclaimer & Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepte

6、d engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULA

7、TION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OFMERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, AND IN NO EVENT SHALL ATIS B

8、E LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES THAT ANY AND ALL USE OF OR RELIANCE UPON THE INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. NOTE - The users attention is called to the possibility that compliance with this standard may

9、 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 required no position is taken regarding the validity of this claim or any patent

10、rights in connection therewith. ATIS-1000052, Byte Count Reporting in an Internet Access and Services LAES Environment Is an ATIS Standard developed by the Lawfully Authorized Electronic Surveillance (LAES) Subcommittee under the ATIS Packet Technologies and Systems Committee (PTSC). Published by Al

11、liance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2012 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, with

12、out 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-1000052 ATIS Technical Report on Byte Count Reporting in an Internet Access and Services LAES Environment Alliance for Telecommunications

13、 Industry Solutions Approved May 2012 Abstract The purpose of this Technical Report is to specify a byte count reporting capability that can be used in an Internet Access and Services LAES environment. ATIS-1000052 ii Foreword The Alliance for Telecommunication Industry Solutions (ATIS) serves the p

14、ublic through improved understanding between carriers, customers, and manufacturers. The Packet Technologies and Systems Committee (PTSC) develops and recommends standards and technical reports related to services, architectures, and signaling, in addition to related subjects under consideration in

15、other North American and international standards bodies. PTSC coordinates and develops standards and technical reports relevant to telecommunications 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 o

16、rganizations, and reviews for acceptability or per contra the positions of other countries in related standards development and takes or recommends appropriate actions. Suggestions for improvement of this document are welcome. They should be sent to the Alliance for Telecommunications Industry Solut

17、ions, PTSC Secretariat, 1200 G Street NW, Suite 500, Washington, DC 20005. At the time of initiation or issuance of the letter ballot for this document, PTSC, which was responsible for its development, had the following roster: M. Dolly, PTSC Chair AT&T V. Shaikh, PTSC Vice-Chair Telcordia G. Myers,

18、 PTSC-LAES Chair Counter Link N. Rao, PTSC-LAES Vice-Chair Nokia Siemens Networks T. Jacobson, Technical Editor Alcatel-Lucent C. Underkoffler, ATIS Chief Editor The Lawfully Authorized Electronic Surveillance (LAES) Subcommittee was responsible for the development of this document. ATIS-1000052 iii

19、 Table of Contents 1 SCOPE, PURPOSE, & APPLICATION 1 1.1 SCOPE 1 1.2 PURPOSE . 1 1.3 APPLICATION . 1 2 NORMATIVE REFERENCES . 2 3 DEFINITIONS, ACRONYMS, & ABBREVIATIONS 2 3.1 DEFINITIONS 2 3.2 ACRONYMS & ABBREVIATIONS 2 4 IAS MODEL . 3 5 GENERAL SURVEILLANCE MODEL AND IAS SURVEILLANCE MODEL 3 6 BYTE

20、 COUNT REPORTING CAPABILITY . 3 6.1 PACKET DATA HEADER REPORT . 3 6.2 PACKET DATA SUMMARY REPORT 3 7 BYTE COUNT REPORTING ABSTRACT SYNTAX NOTATION 4 7.1 BYTE COUNT REPORTING ABSTRACT SYNTAX NOTATION PACKET DATA HEADER REPORT 4 7.2 TOTAL BYTE COUNT REPORTING ABSTRACT SYNTAX NOTATION PACKET DATA SUMMA

21、RY REPORT . 4 TECHNICAL REPORT ATIS-10052 ATIS Technical Report on Byte Count Reporting in an Internet Access and Services LAES Environment 1 1 Scope, Purpose, & Application ATIS-1000013.2007 Ref 1 and ATIS-1000013.a.2009 Ref 2 specify two methods for delivering Content Associated Communications Ide

22、ntifying Information (CACmII) to the LEA: the Packet Data Header Report and the Packet Data Summary Report. This TR specifies how byte count of IP packets is to be reported in a Packet Data Header Report and a Packet Data Summary Report (i.e., in addition to the other IP layer-3 and layer-4 informat

23、ion included in these messages) as specified in Ref 1 and Ref 2. The byte count reporting capability is not intended to be a standalone capability, but rather builds on Ref 1 and Ref 2. Events that trigger reporting of the Packet Data Header Report or the Packet Data Summary Report as specified in R

24、ef 1 and Ref 2 shall instead trigger reporting of the Packet Data Header Report or the Packet Data Summary Report as specified in this TR. Creation of this TR is premised upon the understanding that byte count in the Packet Data Header Report of Ref 1 and associated supplement(s) is not currently pa

25、rt of the safe harbor CALEA requirements. This TR makes no representation regarding byte count information being provided pursuant to a lawful authorization that does not include a full content intercept. Any requirements or standards language (i.e., “shall”, “should”) is used strictly in the contex

26、t of ensuring that this TR is inherently sound and provides appropriate guidance to voluntary implementers. 1.1 Scope This TR specifies LAES capability of reporting byte count in the Packet Data Header Report and Packet Data Summary Report messages in an IAS environment. 1.2 Purpose This TR is provi

27、ded as a specification of byte count reporting capability with minor modifications to Ref 1 and Ref 2. 1.3 Application An Internet Access or Services Provider (IASP) currently provides byte count data as part of a full content intercept. There is an LEA need to obtain byte count information associat

28、ed with an intercept subjects electronic communications, pursuant to a lawful authorization that does not include a full content intercept (e.g., a pen-register order). The subject may have engaged in many different types of packet data sessions. Byte counts, together with other Internet Protocol (I

29、P) header information such as IP addresses and port numbers could help the LEA in determining the types of sessions in which the subject was engaged to enable the LEA to focus investigations on specific sessions. Therefore, there is a need to incorporate byte count data in packet header information

30、reported to the LEA when lawfully authorized. ATIS-1000052 2 2 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this ATIS Standard. At the time of publication, the editions indicated were valid. All standards are subject

31、to revision, and parties to agreements based on this ATIS Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Ref 1 ATIS-1000013.2007 Lawfully Authorized Electronic Surveillance (LAES) for Internet Access and Services, 2007. 1

32、Ref 2 ATIS-1000013.a.2009, Supplement A to ATIS-1000013.2007, January 2009.1Ref 3 IETF RFC 791, Internet Protocol DARPA Internet Program Protocol Specification, September 1981.2Ref 4 IETF RFC 2460, Internet Protocol, Version 6 (IPv6) Specification, December 1998.23 Definitions, Acronyms, & Abbreviat

33、ions 3.1 Definitions For a list of common communications terms and definitions, please visit the ATIS Telecom Glossary, which is located at . 3.1.1 Byte count: The integer value contained in the Total Length field of the IP header if the packet is IPv4 Ref 3, or Payload Length field of the IP header

34、 if the packet is IPv6 Ref 4. 3.1.2 Total byte count: The sum of the byte counts for all packets included in the packet count for a packet data session. 3.2 Acronyms & Abbreviations ATIS Alliance for Telecommunications Industry Solutions CACmII Content Associated Communications Identifying Informati

35、on CF Collection Function CmII Communications Identifying Information IAS Internet Access and Services IASP Internet Access or Services Provider IETF Internet Engineering Task Force IP Internet Protocol LAES Lawfully Authorized Electronic Surveillance LEA Law Enforcement Agency TR Technical Report 1

36、This document is available from the Alliance for Telecommunications Industry Solutions, 1200 G Street N.W., Suite 500, Washington, DC 20005. 2This document is available from the Internet Engineering Task Force (IETF). ATIS-1000052 3 4 IAS Model The IAS model described in Clause 4.1 of Ref 1 applies.

37、 5 General Surveillance Model and IAS Surveillance Model The general surveillance model described in Clause 4.2 and the IAS surveillance model described in clause 4.3 of Ref 1 apply. 6 Byte Count Reporting Capability The byte count reporting capability is not intended to be a standalone capability,

38、but rather builds on Ref 1 and Ref 2. When this capability is utilized, Clause 5.2.11, Packet Data Header Report, and Clause 5.2.12, Packet Data Summary Report, of Ref 1 and including their revision in Ref 2 and the corresponding functionality as included in any future revision shall apply. Events t

39、hat trigger reporting of the Packet Data Header Report as specified in Ref 1 (currently in Clause 5.2.11) and as modified in any supplements to Ref 1 as well as any successor standards, shall trigger reporting of the Packet Data Header Report with the inclusion of an additional parameter as specifie

40、d in Clause 6.1 below. Events that trigger reporting of the Packet Data Summary Report as specified in Ref 1 (currently in Clause 5.2.12) and as modified in any supplements to Ref 1 as well as any successor standards shall trigger reporting of the Packet Data Summary Report with the inclusion of an

41、additional parameter as specified in Clause 6.2 below. 6.1 Packet Data Header Report The Packet Data Header Report provides the CACmII on a per packet basis. The Packet Data Header Report is triggered by each packet of a packet stream sent or received by the intercept subject. The Header Set paramet

42、er in the Packet Data Header Report message as specified in Ref 1 Clause 6.2.11 and as modified in supplements to Ref 1 (e.g., Ref 2) as well as any successor standard shall include the number of bytes (byte count) that are transferred in each packet. The byte count reported is the number contained

43、in the Total Length field of the packet header if the packet is IPv4 Ref 3, or Payload Length field of the packet header if the packet is IPv6 Ref 4. The byte count is in addition to all the information that is reported in the Packet Data Header Report. 6.2 Packet Data Summary Report The Packet Data

44、 Summary Report provides CACmII in a summarized format. The Stream Set parameter in the Packet Data Summary Report message as specified in Ref 1 Clause 6.2.12 and as modified in supplements to Ref 1 (e.g., Ref 2) as well as any successor standard, shall include the total byte count for a packet data

45、 session. Total byte count is the sum of the byte counts for all packets included in the packet count for a packet data session. The total byte count is in addition to all the information that is reported in the Packet Data Summary Report. ATIS-1000052 4 7 Byte Count Reporting Abstract Syntax Notati

46、on 7.1 Byte Count Reporting Abstract Syntax Notation - Packet Data Header Report In conjunction with the Packet Data Header Report, the “byteCount” shall be inserted into the HeaderSet parameter as a new last entry. byteCount 30 INTEGER OPTIONAL The following shows how the “byteCount” is inserted in

47、to the HeaderSet parameter of Ref 2. HeaderSet := SEQUENCE packetDataSessionID 0 PacketDataSessionID, sourceIPaddress 1 IpAddress, destinationIPaddress 2 IpAddress, protocol 3 INTEGER, sourcePortNumber 4 INTEGER OPTIONAL, destinationPortNumber 5 INTEGER OPTIONAL, iPv6FlowLabel 6 INTEGER OPTIONAL, by

48、teCount 30 INTEGER OPTIONAL The following shows how the “byteCount” is inserted into the HeaderSet parameter of Ref 1. HeaderSet := SEQUENCE streamID 0 Value, sourceIPaddress 1 IpAddress, destinationIPaddress 2 IpAddress, sourcePortNumber 3 PortNumber OPTIONAL, destinationPortNumber 4 PortNumber OPT

49、IONAL, byteCount 30 INTEGER OPTIONAL 7.2 Total Byte Count Reporting Abstract Syntax Notation - Packet Data Summary Report In conjunction with Packet Data Summary Header Report, the “totalByteCount” shall be inserted into the StreamSet parameter as a new last entry. totalByteCount 30 INTEGER OPTIONAL The following shows how the “totalByteCount” is inserted into the StreamSet parameter of Ref 2. StreamSet := SET OF SE