[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [legalxml-intercept] Reminder for OASIS LI-XML initial telecon, 6 Jan.
The agenda will be simple. Roll call, discuss and adopt the charter, including the project description list sent out last night. --tony >Hi all, > >For those of you who want to call-in to the initial >OASIS LI-XML teleconference, the relevant information >is provided below. The Toll-Free number is useable >in North America and the UK. If you do plan to call in, >please let me know in advance. > >A summary will be provided in a liaison contribution to >TC LI. > >An agenda and material will be distributed to those >on the meeting list. > >best, >tony > > >>AUDIO ACCESS INFORMATION: >>Toll-Free Number: 888-769-8758 >>Toll Number: +1-630-395-0214 >>Passcode: 56423 >> >>MEETING INFORMATION: >>Confirmation Number: 4492161 >>Conference Date: January 6, 2003 >>Conference Time: 11.00 Eastern; 16.00 GMT; 17.00 European >>Conference Duration: 1 hour >> >>Conference Leader: Anthony Rutkowski >>Leader Day of Call Phone #: 1-703-948-4305 >>Conference Contact: Anthony Rutkowski
OASIS LegalXML Lawful Intercept (LI-XML) TC Charter
1. Name of Technical Committee
The name of the committee is the Lawful Intercept XML
(LI-XML) Technical Committee (TC) within the LegalXML Member
Section of OASIS. The Technical Committee may constitute
subcommittees or other groupings as necessary and
appropriate to carrying out the Technical Committee's
purpose.
2. Purpose of the Technical Committee
A. Mission
The LI-XML Technical Committee exists to produce a
structured, end-to-end LegalXML Lawful Interception Process
framework consisting of XML standards and authentication
mechanisms, including the development and harmonization of
identifiable related XML standards and XML translations of
ASN.1 modules, including proprietary ones made available in
accordance with IPR policies.
B. Language and Applicable Legal Domain
The scope of the LI-XML TC will be focused upon lawful
interception processes and documents worldwide. This will
include both national and local levels, although this is
dependent on the level of participation by country
practitioners. In the USA, the dual levels include federal
and state legal domains. Global LI requirements,
specifications and standards developed and maintained by the
European Telecommunications Standards Institute (ETSI) will
be considered through a liaison process with the ETSI Lawful
Intercept Technical Committee (TC LI). It is expected that
the LI-XML TC will assume English and eventually other
languages.
C. Scope
The core scope of this activity is the creation of standard
schema(s)/DTDs that can be used by parties in all stages of
the lawful interception process. See - Lawful Intercept
Process Model,
http://www.gliif.org/images/LI-XML_process.htm.
The Lawful Interception process herein described consists of
a set of interrelated actions taken by law enforcement or
national security agencies (LEAs), judicial authorities, and
telecommunication and information system providers or their
agents that result in the discovery and production of
investigative or evidentiary records associated with
network-based communications capabilities and uses to a Law
Enforcement Monitoring Facility (LEMF). The process is
effected in nearly every country pursuant to national, local
or intergovernmental law.
This investigative process typically has as many as four
iterations to obtain: a) customer and service provider
reference information; b) customer historical communications
records; c) real-time Intercept Related Information (also
called communications or call-identifying information); and
d) real-time communications content.
Each of these iterations consists of actions and objects in
as many as five stages - depending on the law of the
jurisdiction(s) involved. Usually the judicial
administrative and review process becomes more extensive as
privacy considerations come into play. Subpoenas are
generally required for customer historical records; and
judicial warrants or orders are the norm for real-time
information.
The four stages consist of 1) an initiating Law Enforcement
Agency making application to a judicial or administrative
body, which in turn 2) issues an authorizing instrument for
3) execution by the party or parties or their agents to
4) obtain the required information through some kind of a
technical or administrative mechanism, and 5) handover to a
recipient Law Enforcement Monitoring Facility.
At the entry and exit point of each stage, there is
additional set of actions that consists of the
authentication of the parties, secure transfer of the
information object with time stamps and receipts,
verification of the content, implementation processing, and
the generation of an associated a secure audit log.
If emergency or exigent conditions exist, the second stage
of the process (judicial issuance of an authorizing
instrument) can usually be altered by the LEA using another
instrument coupled with a posteriori judicial or
administrative action.
The LI-XML TC shall also consider tagged database resources
that provide for the effective authentication of all parties
in the lawful intercept process that include LEAs, judicial
or administrative authorities, communication systems
providers and their agents.
Other OASIS LegalXML activities are relevant, especially
Electronic Court Filing, eNotarization, Integrated
Justice, SAML, and WSSecurity TCs. Compatibility and use
of existing schema will be attempted where feasible.
To support this scope, the LI-XML TC shall seek to identify
and capture other XML schemas/DTDs in-use or under
development, as well as frameworks and LI-related ASN.1
modules developed by standards bodies and national
authorities. See Lawful Intercept - Existing Global Models,
http://www.gliif.org/images/LI global_models.htm. Toward
this end, introduction of this activity was favourably
discussed with the Lawful Intercept Technical Committee of
the ETSI at its recent Plenary Meeting, Dublin, 15-17 Oct
2002, and national LEA representatives present.
3. Requirements Definition
The LI-XML TC will conduct a comprehensive verification
of the following initial requirements:
XML compliant syntax used for representing the LI process
and associated documents.
W3C and OASIS specifications, as well as, ISO or other
appropriate standards shall be used except in those cases
made impossible by the legal and binding adoption of
non-standard, but legal requirements including and
especially relating to laws that protect parties to the LI
process and the public.
A set of LI-XML Components that can be used universally by
all LI Schema(s). These component specifications may include
elements and attributes (e.g. unique identifiers, creation
dates, etc.), as appropriate.
The solution will allow efficient management of the Life
Cycle of LI documents, from creation of an LI application
instrument to the archival of target records.
4. Deliverables and Schedule
4.1 Global LI-XML process framework XML Schema that can
represent all discoverable LI processes.
10 Feb 2003
4.2 Identify and provide a means of discovering on a
continuing basis, all LI related XML schemas ASN.1
modules. This will be done in collaboration with
ETSI TC LI and relevant national standards bodies
and authorities
10 Feb 2003
4.3 XML Schema(s) for LI processes specified in this
Charter and deriving from the framework. This may
be done, in part, with the LegalXML Court Filing
Integrated Justice, SAML, and WSSecurity TCs.
1 Oct 2003
4.4 Provide for a common global means of authenticating
parties, schemas, and transport security associated
with the LI process. This may be done in cooperation
with the LegalXML eNotarization TC.
1 Oct 2003
4.5 Create "data dictionaries" which provides the intended
meaning of each element, attribute or other component
of the final specification with the a means of simple
translation to languages other than English.
26 Nov 2003
4.6 Create standard XML Encoding Rules (XER) for
significant ASN.1 LI modules in coordination with the
relevant sponsoring body or company (if proprietary).
26 Nov 2003
4.7 Provide users various template style sheets to provide
them with a starting point to modify and create their
own
31 Dec 2003
4.8 Receive and publish information about interoperability
test results.
9 Jan 2004
5. Language in which the Technical Committee will conduct
business
All business will be conducted in English.
6. Working Methods
The Technical Committee will follow the operating rules of
OASIS and any operating rules adopted by the LegalXML Member
Section Steering Committee with the approval of OASIS
management and the OASIS Board of Directors. In addition,
the Technical Committee will abide by the following
practices:
1. All decisions will be made by consensus.
2. All decisions made in face-to-face meetings will be
subject to ratification or rejection by the full membership
of the Technical Committee on the list serve.
3. All email discussions concerning the technical work of
the Technical Committee and its subcommittees will take
place on OASIS supported list serves.
4. One member of the Technical Committee and of each
subcommittee will serve as ombudsman to monitor the public
list for that entity and provide input from the public list
to the committee and subcommittee discussions.
7. Intellectual Property
In no event shall this Technical Committee finalize or
approve any technical specification if it believes that the
use, distribution, or implementation of such specification
would necessarily require the unauthorized infringement of
any third party rights known to the technical committee, and
such third party has not agreed to provide necessary license
rights on perpetual, royalty-free, non-discriminatory terms.
8. Formation Information
The first meeting will be held by phone on 6 Jan 2003.
Scheduled meetings: Phone meetings at two week intervals
following formation of the LI-XML TC until cessation of its
work. Face-to-face meetings will be held quarterly.
Eligible Persons committed to the stated meeting schedule
Anthony M. Rutkowski
tony@verisign.com
VeriSign, Inc.
John Messing
jmessing@law-on-line.com
Daniel J. Greenwood
dang@mit.edu
TC chair is Anthony M. Rutkowski
Phone meeting sponsor: VeriSign, Inc.
Face-to-face meeting sponsors: VeriSign, Inc.
OASIS LI-XML Projects
Global LI Framework schema
The Framework is the principal initial core activity of
the LI-XML TC. It consists of two parts - a global
framework, and a set of individual modules. Each module
has a designated scope that includes global, regional
(i.e., groups of countries), national, agency, state/
province, or municipal variations.
1 Global Framework
The Global Framework is the generalized model capable
of encompassing all Lawful Intercept activities
worldwide, including initial information discovery,
review of communication records, and interception and
delivery of communications signalling or content,
including associated judicial or administrative orders.
1.1 LI global object dictionary
At present there are several dozen different LI
handover standards, each with dozens of different
object identifiers - many for the same objects.
Layered on top of this ensemble are a significant
number of new object identifiers that will be developed
as part of the LI-XML project or borrowed from other
LegalXML projects. This will include many national and
local variations. Building and maintaining a LI Global
Object Dictionary is key part of this activity.
1.2 Global Tag & bag meta schema
Increasingly large amounts of Intercept Related
Information and Content are being cached or archived
today. Doing so will be increasingly critical in doing
signature analysis to discover technically agile
criminals and terrorists. However, in much of the
Lawful Interception environment, IRI and CC are
captured and analyzed only as source information - in
each instance using one of the multiple insular
standards-based or proprietary specifications. The
need for a common meta information schema for tagging
this information is well appreciated within the "next
generation" LI community. This working group will
focus primarily on XML tagging of network user
information or intercept data and content; combined
with an associated "bagging" schema for global storage
and analysis.
2 LI Framework modules (tentative)
2.1 Initial information discovery
The most common and numerically frequent LI related
activity is the simple act of looking up basic
information about a communications identifier (such as
a phone number or email account), or determining all
such identifiers of a suspect. However, there is no
effective means for doing this in an authoritative,
electronic fashion except for a few proprietary national
implementations. The objective is to develop a
Global User Identifier Lookup schema.
2.2 Review of communication records
The second most common and numerically frequent LI
related activity consists of requesting the records of
a specific user from a communication services operator.
There are no means of doing this electronically. The
objective is to develop a Global Communications Record
Lookup schema.
2.3 Interception and delivery of communications signalling or content
Several dozen diverse international, national, and
industry sector standards organizations have produced
(or are producing) ASN.1 specifications for Handover
Interface ports for the interception and delivery of
communications signalling or content. No administrative
schema (HI1) exist; and many if not most of the H12
(signalling) and HI3 (content) identifiers are
non-interoperable, and a plethora of disparate
protocols exist. The objective is to identify and
provide a means of discovering on a continuing basis,
all LI related XML schemas and ASN.1 modules, translate
those modules into authoritative, interoperable XML schema,
and develop needed HI1 (administrative) XML schema.
2.4 Judicial or administrative orders
Many LI related activities require application to be
make by a Law Enforcement Agency to judicial or
administrative authorities to obtain a warrant, order,
or subpoena. This is a specialized subset of the
activity being dealt with by the LegalXML Electronic
Court Filing TC, that will be done in liaison with
them. The objective is to develop specifications for
the use of XML to create LI related documents and to
transmit those documents from an Law Enforcement Agency
to a court or LI administrative body, from the court or
administrative body to a communications provider or
agent, or to another court, and includes the handling
of highly classified court documents.
2.5 Authentication and verification schema
Many tens of thousands of parties are involved globally
in Lawful Interception process, involving an even
larger number of communications technical facilities.
This includes Law Enforcement Agencies, Law Enforcement
Monitoring Facilities, Communications Services
Providers and Agent Mediators, and Network Elements.
Yet there is no global mechanism by which these parties
and facilities are even known, much less capable of
verification or authentication. The needs are similar
to other OASIS TCs dealing with registries and
authentication. The objectives are to develop
specifications for interoperable LI Global Identifier
Registries and associated verification and
authentication schema.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC