Information Document 18-E ITU-T Study Group 2 May 2002 QUESTION:Q.1/2 SOURCE:TSB TITLE:UNIVERSAL COMMUNICATIONS IDENTIFIER (UCI) (by Mike Pluke, ETSI)

Slides:



Advertisements
Similar presentations
Authentication Authorization Accounting and Auditing
Advertisements

VON Europe /19/00 SIP and the Future of VON Protocols SIP and the Future of VON Protocols: Presence and IM Jonathan Rosenberg.
Copyright © 2007 Telcordia Technologies Challenges in Securing Converged Networks Prepared for : Telcordia Contact: John F. Kimmins Executive Director.
International Telecommunication Union ENUM Issues and Solutions Houlin Zhao Director Telecommunication Standardization Bureau International Telecommunication.
2001_03_28 SG A contribution– 1 Dept of State ITAC-T Advisory Committee SG-A Ad Hoc Meeting on ENUM March 28th & 29th, 2001 ENUM CONTRIBUTION TITLE: ENUM.
ENUM Call Flow Scenarios
Configuration management
Communication Service Identifier Requirements on SIP draft-loreto-3gpp-ics-requirements.txt
External User Security Model (EUSM) for SNMPv3 draft-kaushik-snmp-external-usm-00.txt November, 2004.
BAI613 Module 2 - Voice over IP Technology. Module Objectives 1. Describe the benefits of IP Telephony/Packet Telephony/VoIP over traditional telephone.
THIS IS THE WAY ENUM Variants Jim McEachern Carrier VoIP Standards Strategy THIS IS.
Multi-Mode Survey Management An Approach to Addressing its Challenges
ETSI Workshop on Quality Issues for IP Telephony 8-9 June 1999, Sophia Antipolis, France ETSI PROJECT TIPHON overview of QoS activities ETSI Workshop on.
Cryptography and Network Security 2 nd Edition by William Stallings Note: Lecture slides by Lawrie Brown and Henric Johnson, Modified by Andrew Yang.
Chapter 19: Network Management Business Data Communications, 5e.
Mike Pluke1 Universal Communications Identifier (UCI) and the power of profiles Mike Pluke Castle Consulting Ltd. ETSI TC HF & STF265.
Module 5: TLS and SSL 1. Overview Transport Layer Security Overview Secure Socket Layer Overview SSL Termination SSL in the Hosted Environment Load Balanced.
Identity Management Based on P3P Authors: Oliver Berthold and Marit Kohntopp P3P = Platform for Privacy Preferences Project.
TCG Confidential Copyright© 2005 Trusted Computing Group - Other names and brands are properties of their respective owners. Slide #1 TNC EAP IETF EAP.
OASIS Reference Model for Service Oriented Architecture 1.0
3GPP Presence Requirements Requirements for Presence Service based on 3GPP specifications and wireless environment characteristics draft-kiss-simple-presence-wireless-
Chapter 1 – Introduction
Chapter 19: Network Management Business Data Communications, 4e.
1 Cryptography and Network Security Third Edition by William Stallings Lecturer: Dr. Saleem Al_Zoubi.
1 IP Security Outline of the session –IP Security Overview –IP Security Architecture –Key Management Based on slides by Dr. Lawrie Brown of the Australian.
1 ITC242 – Introduction to Data Communications Week 12 Topic 18 Chapter 19 Network Management.
Semester 4 - Chapter 4 – PPP WAN connections are controlled by protocols In a LAN environment, in order to move data between any two nodes or routers two.
Protocols and the TCP/IP Suite
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Internet Telephony Helen J. Wang Network Reading Group, Jan 27, 99 Acknowledgement: Jimmy, Bhaskar.
A Use Case for SAML Extensibility Ashish Patel, France Telecom Paul Madsen, NTT.
Internal Auditing and Outsourcing
Review security basic concepts IT 352 : Lecture 2- part1 Najwa AlGhamdi, MSc – 2012 /1433.
Information Systems Today: Managing in the Digital World TB4-1 4 Technology Briefing Networking.
ENUM? “ Telephone Number Mapping (ENUM or Enum, from TElephone NUmber Mapping) is a suite of protocols to unify the telephone numbering system E.164 with.
Dineshwari Byrappa Nagraj Rashi Gupta Shreya Modi Swati Satija Magesh Panchanathan.
1 Telematica di Base Applicazioni P2P. 2 The Peer-to-Peer System Architecture  peer-to-peer is a network architecture where computer resources and services.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Protocol Security Date Submitted: December, 2007 Presented.
Eng. Wafaa Kanakri Second Semester 1435 CRYPTOGRAPHY & NETWORK SECURITY Chapter 1:Introduction Eng. Wafaa Kanakri UMM AL-QURA UNIVERSITY
1 NGN Issues - Numbering and Addressing Peter Darling ACIF NGN FOG No. 3.
22-23 June 2004TISPAN-3GPP Workshop - Sophia-Antipolis 1 Joint 3GPP & TISPAN Workshop on NGN-IMS - NGN-IMS issues handling - Alain Le Roux (France Telecom),
IEEE R lmap 23 Feb 2015.
Software Requirements Engineering CSE 305 Lecture-2.
Industry Canada 1 Bob Leafloor Colman Ho Peter Chau Industry Canada January 2003 (ENUM) T E lephone NU mber M apping.
1 Section 10.9 Internet Security Association and Key Management Protocol ISAKMP.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
© 1998 R. Gemmell IETF WG Presentation1 Robert Gemmell ROAMOPS Working Group.
User Identification Solutions in Converging Networks Mike Pluke ETSI Specialist Task Force STF 157 Leader of :
Authentication Mechanism for Port Control Protocol (PCP) draft-wasserman-pcp-authentication-01.txt Margaret Wasserman Sam Hartman Painless Security Dacheng.
User Identification Solutions in Converging Networks Mike Pluke Castle Consulting Ltd. ETSI User Group ETSI Human Factors Representing:
Use Cases Use Cases are employed to describe the functionality or behavior of a system. Each use case describes a different capability that the system.
Unified Distributed (UDub Mail) Life Cycle Objectives Sachin Pradhan Gabriel Maganis.
Document IPW-10 User Identification Solutions in Converging Networks Mike Pluke Castle Consulting Ltd. ETSI Specialist Task Force STF 157 Leader of :
Topic 1 – Introduction Huiqun Yu Information Security Principles & Applications.
Identity Proofing, Signatures, & Encryption in Direct esMD Author of Record Workgroup John Hall Coordinator, Direct Project June 13, 2012.
Systems Development Life Cycle
Patrik Fältström. ITU Tutorial Workshop on ENUM. Feb 8, 2002, Geneva Explanation of ENUM (RFC 2916) Patrik Fältström Area Director, Applications Area,
Andrew Allen Communication Service Identifier.
Jini Architecture Introduction System Overview An Example.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Enumservice VOID draft-stastny-enum-void-00 Richard Stastny Lawrence Conroy IETF60 San Diego.
DHCP Vrushali sonar. Outline DHCP DHCPv6 Comparison Security issues Summary.
IPSec is a suite of protocols defined by the Internet Engineering Task Force (IETF) to provide security services at the network layer. standard protocol.
User Identification Solutions in Converging Networks Mike Pluke ETSI STF “User Identification in Converging Networks”
K. Salah1 Security Protocols in the Internet IPSec.
IP Telephony (VoIP).
THIS IS THE WAY ENUM Variants Jim McEachern
Maryna Komarova (ENST)
3GPP and SIP-AAA requirements
System architecture, Def.
Presentation transcript:

Information Document 18-E ITU-T Study Group 2 May 2002 QUESTION:Q.1/2 SOURCE:TSB TITLE:UNIVERSAL COMMUNICATIONS IDENTIFIER (UCI) (by Mike Pluke, ETSI) The purpose of this document is to provide background information on the Universal Communication Identifier code.

ETSI Universal Communications Identifier (UCI) Mike Pluke Castle Consulting Ltd. Leader of ETSI Specialist Task Forces 180 & 200

The Universal Communications Identifier (UCI) the rationale for an identifier such as the UCI; the key drivers that have shaped the UCI and its support environment; an explanation of the framework that supports UCI; a brief comparison with other similar initiatives of interest to ITU-T SG2; an overview of the development of the UCI within ETSI; the ITU-T SG2 issues? I will cover:

Todays identifier complexities Which of these is Mike Miles?

Some important user requirements ( I ) have a single communication identifier for every significant life role; check the authenticity of the description of the people you communicate with (or see when they use aliases); keep your identifier when adding services or changing suppliers; have control over the release of your own information. You should be able to:

should be associated with you (or your role) - not hardware, services, 3rd parties, or service suppliers; should provide a meaningful description of you (in a way you wish to be described); can be added to communications networks and services with the very minimum amount of re- engineering. A UCI: Some important user requirements ( II )

Nothing currently fits the specification Current identifiers were judged against the user requirements developed by ETSI Specialist Task Force STF157 None of todays identifiers (e.g. phone numbers, addresses, IM addresses) meet these requirements Other identifier proposals (e.g. IETF URNs) also fail to meet the requirements It was concluded that a new identifier would be needed

Support for a new identifier A new identification scheme with new capabilities needs a new support environment The new support environment should not mean large changes to existing systems The identifier support environment must be considered as an overlay to existing communications systems

Existing support environment Support for communications largely comes from the networks, protocols and applications associated with individual communication types (e.g. telephony networks, SMTP mail protocols) Users can control their telephone communications using supplementary services Users can control their communications using mail redirection and filtering in clients Instant messaging systems allow control by manual selection of availability settings and with buddy lists The types of controls and the range of different control mechanisms are as varied as the different types of communication Users cannot cope well with such a range of controls

The UCI support environment the identity (UCI) of people attempting to communicate with the user; the date and time when communication is attempted; the urgency of the communication; whether the originator of a communication has a work or a personal status; the users preferences for how they wish to be reached (which services and which terminals). The UCI support environment allows the control of communications based upon at least the following:

The UCI Is a 3-part data structure A unique role identifier (unroid) – numeric – E essential to establish communication A persona element (persel) – not unique – alphanumeric description of UCI owner - most useful for the end-user A status element (statel) – multiple status indications giving key details about the UCI and its owner – helps the user decide the most appropriate way to communicate Only the unroid is required in all signalling flows

UCI elements The Personal User Agent (PUA) – this acts on the users behalf in controlling communication set-up The PUA contains the users preferences and rules The PUA only talks to its owner, other PUAs and SAs The Service Agent (SA) – this is the interface to existing networks and services The SA only talks to PUAs and its own network/service Terminals, identification mechanisms, etc.

Relationship between UCI elements

Simplified UCI operation = registration association

Simplified UCI operation X X

Simplified UCI operation Jane selects Dans UCI and sends it

Simplified UCI operation

Initiatives similar to UCI ( I ) - UPT Like UCI, UPT does: have a single identifier for a range of services; assume a common interface for controlling a range of services, but, UPT does not: have any concept of identifying the true name of the UPT subscriber; allow the authenticity of any association between a personal name and a UPT identifier to be verified; integrate non-telephony services such as very effectively.

Initiatives similar to UCI ( II ) - ENUM Like UCI, ENUM does: have a single E.164 number associated with a range of services; have a global scope. but ENUM does not have any concept of identifying the true name of the ENUM subscriber; allow the authenticity of any association between a personal name and an ENUM identifier to be verified; allow individual communications identifiers to be hidden (as the NAPTR record is public) – a spammers charter!; provide inherent protection from distributed denial of service (DDoS) attacks (as the NAPTR record is public). Intercommunication in UCI is strictly controlled between Users, their PUAs and SAs – this should help eliminate threats such as DDoS

UCI work in ETSI STF157: Looked at user requirements, the definition of a UCI, and a first look at a UCI architecture; STF180: Is defining the UCI architecture in more detail, is specifying usage scenarios and is examining security issues from the end-users perspective STF199: Is looking at implementation issues across communications platforms and security from the service provider perspective STF200: Is looking at the usability issues of end-user control of their communications environment

Issues for ITU-T SG2 Allocation of identifiers – in particular the globally unique E.164 unroid element of the UCI Service aspects of UCI – it is multi-service, it is global …

Thank you Contact: