proposal for new TC: LegalXML SDHI

MHonArc v2.5.0b2 -->
















legalxml-sc message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: proposal for new TC: LegalXML SDHI




From: "Karl F. Best" <>
To: 
Date: Fri, 05 Mar 2004 10:52:28 -0500






LegalXML Steering Committee:

I have received a proposal to form a LegalXML SDHI TC as part of the 
member section. Please send to me any comments by the end of next week 
so that I can follow up with the proposers before the CfP goes out.

-Karl

============================================

Name of the Proposed TC:

OASIS LegalXML Subscriber Data Handover Interface (SDHI) TC

Statement of Purpose:

During the course of law enforcement investigations or judicial
proceedings, emergency situations, or other government mandated
conditions, a critical need arises for information concerning
subscribers to telephone, Internet or other communication services at a
well-defined interface. Law enforcement authorities may also use
collection and analysis systems that assist in understanding the
relationships among parties in an investigation. To accomplish this
task, these systems may generate requests for subscriber information and
use the resulting data furnished by telecommunication or other service
providers.

The Technical Committee, part of the OASIS LegalXML Member Section, will
develop a specification for the production at a consistent Subscriber
Data Handover Interface (SDHI), by telecommunication or Internet service
providers, of XML structured information concerning a subscriber or
communications identifier (e.g., a telephone number) in response to an
XML structured request which includes, when necessary, authorization
from a judicial, public safety, or law enforcement authority.

There are generally two request variations. The first is a request for
basic information concerning a subscriber based on a name, number, or
other identifier - for which no formal authorizing instrument is usually
needed. The second is a request for expanded information pursuant to a
subpoena or warrant or other lawful order, which 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 specification will include required access to provider records
pursuant to national Codes of Practice for data retention, emergency
response, or investigatory requests, although in most cases, the
information is kept by communication services providers as part of
normal commercial business practice for accounting, billing, fraud
prevention, and marketing purposes.  See, e.g., United Kingdom,
Regulation of Investigatory Powers Act 2000, 2000 chap. 23, part 1
chapter II, and the disclosure of communications data (sections 21-25
inclusive); and France, Loi no. 2003-239 du 18 mars 2003, Loi pour la
securite interieure. Rapid and efficient access to retained data among
many diverse providers is a major emerging need.  The specification is
intended only to facilitate access and production of information that
may already exist, and has no prescriptive implication or intent.

This process can be described as a simple “query > authorization >
response action”

Scope:

The work of the SDHI TC will be limited to the following:

* SDHI Requirements Specification
* SDHI Request, Authorization and Response Schema

The identification or development of such additional schema as may be
necessary to implement the SDHI Interface.  These may include:

* XML mechanisms for the queries, including if necessary the “envelope”
for the authentication and secure transfer of the information, to be
imported from other TC work.  These capabilities could rely in part on
the Legal XML Court Filing Blue Envelope specification.
* Localization. These Subscriber Data Handover Interface standards must
include a localization mechanism to accommodate the diverse legal
systems of country authorities and providers, as well as legacy
transition schema such as PDF images and delimited field flat files
* prioritizing requests
* accounting and billing
* accommodating number and identifier portability

List of Deliverables:

* SDHI Requirements Specification, version 0.1.0 posted at the first meeting
* SDHI Requirements Specification finalized; two months after first meeting
* Begin work on the SDHI request and response schemas; two months after
first meeting
* SDHI request and response schemas approved; five months after first
meeting
* Produce additional identified deliverables or revisions to the SDHI
request and response schemas; eight months after first meeting
* Terminate SDHI Technical Committee; eight months after first meeting

Anticipated Audience:

The anticipated audience and users include law enforcement and public
safety officials, judicial and administrative bodies, national
regulatory agencies, communication service providers, lawful access
service bureaus, and vendors of network equipment, subscriber accounting
systems, and collection system analysis tools.

Language:

English.

------------------
The following is informational only for the purposes of starting the TC,
and will not be part of the TC's charter:

Similar Work:

* OASIS Customer Information Quality TC, XML Standards for "Global"
Customer Information Management;
http://www.oasis-open.org/committees/ciq (including the extensible Name
and Address Language (xNAL); extensible Name Language (xNL); extensible
Address Language (xAL); extensible Customer Information Language (xCIL);
and extensible Customer Relationships Language (xCRL))
* OASIS Digital Signature TC; http://www.oasis-open.org/committees/dss,
including the Digital Signature Service Core Protocols and Elements (DSS)
* OASIS LegalXML Integrated Justice TC;
http://www.oasis-open.org/committees/legalxml-intjustice
* OASIS e-Government TC; http://www.oasis-open.org/committees/egov
* OASIS Election Services TC; http://www.oasis-open.org/committees/election
* IETF Cross Registry Information Service Protocol (crisp) TC; http://
www.ietf.org/html.charters/crisp-charter.html

List of Contributions:

* Requirements Specification, Subscriber Data Handover Interface (SDHI)
Version 0.1.0

Date of first meeting:

15 April 2004
Time: 11:00 hrs EST; 16hrs GMT
Type of meeting: teleconference
Sponsor: BTplc

On-going Meeting Schedule:

Phone meetings at two week intervals following formation of the SDHI TC
until cessation of its work.  Face-to-face meetings will be held quarterly

Ongoing meeting sponsor: BTplc (phone meetings); VeriSign and BTplc
(face-to-face)

Proposers:

Anthony M Rutkowski, Verisign, 
Robin Gape, BTplc, 
John M. Greacen Individual member, 

TC Convener

Anthony M Rutkowski

Proposed TC Co-chairs: Anthony M Rutkowski and Robin Gape










-- 
=================================================================
Karl F. Best
Vice President, OASIS
office  +1 978.667.5115 x206     mobile +1 978.761.1648
      http://www.oasis-open.org