[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: assistance in LI-XML TC
CIQ TC, FYI. I will reply to Tony. Regards, Ram -----Original Message----- From: Tony Rutkowski [mailto:trutkowski@verisign.com] Sent: Wednesday, 24 September 2003 11:21 PM To: rkumar@msi.com.au Subject: assistance in LI-XML TC Hi Ram, I'm chair of the OASIS LI-XML TC under the LegalXML umbrella. LI-XML has not been very active - largely because of the broad scope of its work and a lack of focus. Last week, at a meeting in Boston, several of the LI-XML principals decided to focus on a single deliverable that meets a significant immediate need. The attached project description provides the detail. The description also points out that your CIQ group has already provided a significant component of the work. Would you or colleagues be interested in assisting in this project? I'd also be curious if you have encountered any use of your CIQ specifications that might be related. Your advice and counsel here would be greatly appreciated - including minimally any suggestions regarding the project description. The co-chair of this effort will be Robin Gape of BT in the UK. cordially, tony rutkowski Anthony-Michael Rutkowski Vice President for NetDiscovery Development VeriSign, Inc mailto:trutkowski@verisign.com mob: +1 703.887.5196 Office: 21345 Ridgetop Circle Dulles VA 20166-6503 USA tel: +1 703.948.4305
OASIS LI-XML V0.9.2 22 Sep 2003
PROJECT DESCRIPTION
COMMUNICATION SUBSCRIBER INFORMATION ACCESS SPECIFICATIONS
1 Objective
---------
Develop a specification for the production of
structured information concerning a subscriber to
telecommunication or Internet services in response
to a structured request and authorization from a
court and/or law enforcement authority. This includes
access to communications data required pursuant to
national Codes of Practice.
2 Description
-----------
2.1 During the course of law enforcement investigations
or judicial proceedings, a critical need arises for
information concerning subscribers to telephone,
Internet or other communication services data. This
usually occurs in two stages. The first is a request
for limited information concerning a subscriber based
on a name, number, or other identifier - for which no
formal authorizing instrument is generally needed. The
second is a request for detailed information pursuant
to a subpoena or warrant, that may demand call detail
or billing records, mobile user location information,
communication or access logs, or other typically
privileged information held by the service provider.
This process can be described as two kinds of
query - response actions:
Request for > Basic Subscriber
Basic Subscriber > Information
Information >
Order for > Expanded Subscriber
Expanded Subscriber > Information
Information >
2.2 Law enforcement authorities use collection and
analysis systems that assist in the understanding of
the relationships among parties in an investigation.
To accomplish this task, these systems generate
requests for subscriber information and use the
resulting data furnished by telecommunication service
providers.
2.3 The retention and access to the subscriber data is
increasingly being mandated in conjunction with
national Codes of Practice for communication services
providers. See, e.g., United Kingdom, Home Office,
Retention Of Communications Data Under Part 11:
Anti-Terrorism, Crime & Security Act 2001, Voluntary
Code Of Practice. Rapid and efficient access to
retained data among many diverse providers is a
major emerging need.
2.4 These XML schema standards will also include legacy
transition schema such as PDF images and delimited
field flat files, as well as the legal systems of
participating country authorities and providers.
2.5 The activity will also include means for:
authenticating and acknowledging requests
authenticating and acknowledging records produced
accounting and billing
3. XML schema deliverables
-----------------------
3.1 REQUEST FOR BASIC SUBSCRIBER INFORMATION
Typically, although a request for basic subscriber
information must have an official governmental basis,
it is limited in scope, so that a judicial warrant
or subpoena is not required. This scope varies among
different national jurisdictions.
3.1.1 A request will contain one or more identifying
characteristics of the subscriber or her/his services:
subscriber name
subscriber postal address
subscriber contact telephone number
subscriber contact eMail address
subscriber contact fax
subscriber account number
subscriber national identifier (e.g., Social Security Number)
subscriber driver's license identifier
subscriber date of birth
subscriber other identifiers maintained
dealer name (where an intermediary party exists)
dealer postal address
dealer telephone number
dealer account number for subscriber
billed party name
billed party address
billing account
installation address
service account identifier
E.164 telephone number
International Mobile Equipment Identifier (IMEI)
International Mobile Subscriber Identifier (IMSI)
Urban Fleet Member Identifier (UFMI)
Internet Protocol address
Internet domain name
eMail name
Instant Messenger name
Other maintained service account identifiers
3.1.2 Requesting law enforcemant, security, intelligence,
or court official name, point of contact, address,
telephone number, fax number, eMail address, or
authenticating identifier or certificate.
3.1.3 Specification of the desired subscriber information
3.1.4 Electronic Delivery address for the produced
information
3.1.5 Request identifier, it it exists
3.1.6 Authentication and acknowledgement
3.2 ORDER FOR EXPANDED SUBSCRIBER INFORMATION
Typically, an order for expanded subscriber information
may demand any or all of the data retained or information
stored concerning a subscriber. Because of such an order
is broad and intrusive, most legal systems require a
judicial warrant or subpoena for the production of the
information.
An order for expanded subscriber information will contain
all the information in 3.1, above, plus additional fields
pertaining to the issuing authority and the basis of the
order.
3.3 PRODUCTION OF LIMITED SUBSCRIBER INFORMATION
3.3.1 Subscriber information, including contact references
subscriber name
subscriber postal address
subscriber contact telephone number
subscriber email address
subscriber contact fax
subscriber account number
subscriber national identifier such as Social Security Number
subscriber driver's license identifier
subscriber date of birth
subscriber other identifiers maintained
service account identifier
dealer name (where an intermediary party exists)
dealer postal address
dealer telephone number
dealer account number for subscriber
billed party name
billed party address
billing account
payment methods/credit card details
installation address
Identity of services subscribed to
Telephony
E.164 telephone number(s)
International Mobile Equipment Identifier (IMEI)
International Mobile Subscriber Identifier (IMSI)
Urban Fleet Member Identifier (UFMI)
Email
email address(es)
IP at registration
Instant messaging
Internet Message Handle
IP at registration
Instant messaging
Internet Message Handle
IP at registration
ISP - dial-in
Log-in
CLI at registration
ISP - always-on
Unique identifiers
MAC address
ADSL end points
IP tunnel address
3.3.2 Timestamp
3.3.3 Authentication and acknowledgement
3.3.4 Accounting and billing information
3.4. PRODUCTION OF DETAILED SUBSCRIBER INFORMATION
3.4.1 Subscriber information, including contact references
subscriber name
subscriber postal address
subscriber contact telephone number
subscriber email address
subscriber contact fax
subscriber account number
subscriber national identifier (e.g., Social Security Number)
subscriber driver's license identifier
subscriber date of birth
subscriber other identifiers maintained
service account identifier
dealer name (where an intermediary party exists)
dealer postal address
dealer telephone number
dealer account number for subscriber
billed party name
billed party address
billing account
payment methods/credit card details
installation address
Identity of services subscribed to
Telephony
E.164 telephone number(s)
International Mobile Equipment Identifier (IMEI)
International Mobile Subscriber Identifier (IMSI)
Urban Fleet Member Identifier (UFMI)
Email
email address(es), IP at registration
Instant messaging
Internet Message Handle, IP at registration
Instant messaging
Internet Message Handle
IP at registration
ISP - dial-in
Log-in
CLI at registration
ISP - always-on
Unique identifiers
MAC address
ADSL end points
IP tunnel address
3.4.2 Telephony data
All numbers (or other identifiers e.g. name@bt) associated with call
physical/presentational/network assigned Caller Line Identity (CLI)
Dialed Number Identifier (DNI)
International Mobile Subscriber Identifier (IMSI)
International Mobile Equipment Identifier (IMEI)
Urban Fleet Member Identifier (UFMI)
exchange/divert numbers
Date and time of start of call
Duration of call/date and time of end of call
Type of call
Location data at start and/or end of call (lat/long reference)
Cell site data from time cell ceases to be used
IMSI/MSISDN/IMEI mappings
For GPRS & 3G
date and time of connection
International Mobile Subscriber Identifier (IMSI)
IP address assigned
Mobile data exchanged with foreign operators
IMSI & Mobile Station Integrated Services Digital Network (MSISDN)
sets of GSM triples
sets of 3G quintuples
global titles of equipment communicating with or about the subscriber
3.4.3 Short Message Service (SMS), Enhanced Messaging Service (EMS) and
Multimedia Messaging Service (MMS) data
Calling number
Calling number IMEI
Called number
Called number IMEI
Date and time of sending
Delivery receipt
Location data when messages sent and received (lat/long reference)
3.4.4 eMail data
Log-on
authentication user name
date and time of log-in/log-off
IP address logged-in from
Sent email
authentication user name
from/to/cc email addresses
date and time sent
Received email
authentication user name
from/to email addresses
date and time received
3.4.5 ISP data
Log-on
authentication user name
date and time of log-in/log-off
IP address assigned
Dial-up
CLI
number dialled
Always-on
ADSL end point/MAC address
3.4.6 Web activity logs
Proxy server logs (date/time)
IP address used
URL's visited
services
3.4.7 Other Services
Stored message access and retreival
Instant Message Type Services (log-on/off time)
3.4.8 Collateral Data
Retention relative to data to which it is related
Data needed to interpret other communications data
for example -the mapping between cellmast identifiers and their location
translation of dialling (as supported by IN networks)
ENUM mappings
3.4.9 Timestamp
3.4.10 Authentication and acknowledgement
3.4.11 Accounting and billing information
4 Existing relevant XML specifications
------------------------------------
4.1 XML Standards for "Global" Customer Information Management
http://www.oasis-open.org/committees/ciq/ciq.html
extensible Name and Address Language (xNAL)
extensible Name Language (xNL)
extensible Address Language (xAL)
extensible Customer Information Language (xCIL)
extensible Customer Relationships Language (xCRL)
4.2 LegalXML Integrated Justice TC
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=legalxml-intjustice
5 Participants
------------
Product vendors involved: ATIS Systems GmbH, ETI*, JSI
Telecom*, Orion Scientific*, Pen-Link*, Racal,
Raytheon*, Siemens.
Service vendors involved: VeriSign*, GTEN.
Law enforcement agencies supported:
FBI Quantico, U.S. Dept of Justice, U.S. Executive Office
of US Attorneys, Administrative Office of United States
Courts , U.S. National Center for State Courts, Canada
Solicitor General, U.K. Home Office, Netherlands PIDS,
Germany RegTP.
Providers involved: British Telecom*.
* Confirmed commercial participation.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]