HT04 - Lawful Interception: Difference between revisions

From NFVwiki
(Created page with "= Description = Many regulatory authorities require operators to provide Lawful Interception capabilities. This Hot Topic aims to drive: * Understanding the impact of virtual...")
 
Line 19: Line 19:
** Security
** Security
* What other impacts may exist?
* What other impacts may exist?


==Criterion of success==
==Criterion of success==

Revision as of 14:13, 11 August 2015

Description

Many regulatory authorities require operators to provide Lawful Interception capabilities. This Hot Topic aims to drive:

  • Understanding the impact of virtualisation on the regulatory requirements of Lawful Interception
  • Exploration of architectures and designs to allow Lawful Interception capabilities to be provided in NFV deployments
  • Proofs of Concept(s) to show Lawful Interception capabilities in conjunction with NFV

HT#4 (SEC) Lawful Interception

Status

ACTIVE

What is expected to be learnt from the NFV PoCs

Points to prove/refute

  • How does virtualisation impact the requirements for Lawful Interception?
  • What impacts are there on NFV deployments in terms of:
    • Performance
    • Management
    • Security
  • What other impacts may exist?

Criterion of success

  • Presentation of architectures to provide Lawful Interception capabilities that are acceptable to Law Enforcement Agencies and deployable by operators

Technical information to be provided by the PoC Team

  • Description of how requirements in SEC009 are met
  • Overall architecture and use case descriptions
  • Specifics on the issues faced
  • Specifics on the solutions provided
  • Specifics on the lessons learnt


PoC Teams shall follow the HT#4 Feedback Template on their contributions to Hot Topic#4

Concerned WGs/WI

SEC WG: SEC004 - Lawful Interception Implications - Latest draft

SEC009 - Use cases and technical approaches for multi-layer host administration - Latest draft

Coordinator

SEc WG co-chair: Mike Bursell (Intel) mike.bursell@intel.com

Contributions (feedback) deadline

Q2 2016