Lists Home |
Date Index |
A new OASIS technical committee is being formed under the LegalXML
member section. The OASIS Lawful Intercept Technical Committee (LI-XML
TC) has been proposed by the following members of OASIS: Anthony M.
Rutkowski, VeriSign; and the following individual members: John Messing
and Daniel J. Greenwood.
The proposal for a new TC meets the requirements of the OASIS TC Process
(see http://oasis-open.org/committees/process.shtml), and is appended to
this message. The proposal, which includes a statement of purpose, list
of deliverables, and proposed schedule, will constitute the TC's
charter. The TC Process allows these items to be clarified (revised) by
the TC members; such clarifications (revisions), as well as submissions
of technology for consideration by the TC and the beginning of technical
discussions, may occur no sooner than the TC's first meeting.
To become a member of this new TC you must 1) be an employee of an OASIS
member organization or an Individual member of OASIS; 2) notify the TC
chair, Anthony M. Rutkowski (firstname.lastname@example.org) of your intent to
participate at least 15 days prior to the first meeting; and 3) attend
the first meeting on 6 January. You should also subscribe to the TC's
mail list. Note that membership in OASIS TCs is by individual, and not
by organization. You must be eligible for participation at the time you
time you notify the chair.
The private mail list email@example.com is for
committee discussions. TC members as well as any other interested OASIS
members should subscribe to the list by going to the mail list web page
at http://lists.oasis-open.org/ob/adm.pl, or by sending a message to
firstname.lastname@example.org with the word
"subscribe" as the body of the message. (Note that subscribing to the
mail list does not make you a member of the TC; to become a member you
must contact the TC chair and attend the first meeting as described in
the preceeding paragraph.)
A public comment list will be available for the public to make comments
on the work of this TC; a message may be sent to the TC via the address
The archives of both of these mail lists are visible to the public at
Karl F. Best
Vice President, OASIS
+1 978.667.5115 x206
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
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
andlocal 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.
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,
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 SAML, WS
Security, Electronic Court Filing, eNotarization, and Integrated Justice
TCs. Compatibility and use of existing schema will be attempted where
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
theLawful Intercept Technical Committee of the ETSI at its recent
Plenary Meeting, Dublin, 15-17 Oct 2002, and national LEA
3. Requirements Definition
The LI-XML TC will conduct a comprehensive verification of the following
- XML compliant syntax used for representing the LI process and
- 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. 20 Jan 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. 20 Jan 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 and Integrated Justice TCs. Technologies from
other existing OASIS TCs such as SAML and WS Security will be used. 1
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 Aug 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.
1 Sep 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). 1 Sep 2003
4.7 Provide users various template style sheets to provide them
with a starting point to modify and create their own. 1 Nov 2003
4.8 Receive and publish information about interoperability test
results. 31 Oct 2003
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
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
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
8. Formation Information
The first meeting will be held by phone on 6 January 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, email@example.com, VeriSign, Inc.
- John Messing, firstname.lastname@example.org, individual member
- Daniel J. Greenwood, email@example.com, indivudual member
TC chair is Anthony M. Rutkowski
Phone meeting sponsor: VeriSign, Inc.
Face-to-face meeting sponsors: VeriSign, Inc.