SIP Extensions for Caller Identity and Privacy Flemming Andreasen W. Marshall, K. K. Ramakrishnan, E. Miller, G. Russell, B. Beser,

Slides:



Advertisements
Similar presentations
SIPPING 3GPP Requirements Ad Hoc Meeting Georg Mayer IETF#53, Minneapolis.
Advertisements

July 13, 2006SIPPING WG IETF 66Slide # 1 ETSI TISPAN call completion services (draft-poetzl-sipping-call-completion-00) Roland
AVTCore IETF 82 Taipei Current Burst Gap related Drafts Jing Zhao Zhao Sunshine
STIR Secure Telephone Identity. Context and drivers STIR Working Group Charter Problem Statement Threats Status of work Related work and links Introduction.
3GPP Presence Requirements Requirements for Presence Service based on 3GPP specifications and wireless environment characteristics draft-kiss-simple-presence-wireless-
WebDAV: Agenda Find someone to record minutes Open issues in the ACL specification Reviving DASL Improved status reporting (Dusseault) Moving RFC 2518.
Requirements for Resource Priority Mechanisms for the Session Initiation Protocol draft-ietf-ieprep-sip-reqs-01 Henning Schulzrinne Columbia University.
Certificate Path Building draft-ietf-pkix-certpathbuild-01.txt Peter Hesse Matt Cooper Yuriy Dzambasow Susan Joseph Richard Nicholas.
1 SIPREC Requirements IETF #80 Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam.
Introduction to the Secure SMTP Server service. Secure SMTP server is a secure, reliable SMTP mail relay server for your outgoing mail. Secure SMTP service.
GRUU Mechanism Jonathan Rosenberg. Status Draft-rosenberg-sipping-gruu-reqs-01 defines the problem Draft-rosenberg-sip-gruu submitted with proposed solution.
1 SIP WG meeting 73rd IETF - Minneapolis, MN, USA November, 2008 Return Routability Check draft-kuthan-sip-derive-00 Jiri
Request History – Solution Mary Barnes SIP WG Meeting IETF-57 draft-ietf-sip-history-info-00.txt.
SIP Authorization Framework Use Cases Rifaat Shekh-Yusef, Jon Peterson IETF 91, SIPCore WG Honolulu, Hawaii, USA November 13,
PPSP Tracker Protocol draft-gu-ppsp-tracker-protocol PPSP WG IETF 82 Taipei Rui Cruz (presenter) Mário Nunes, Yingjie Gu, Jinwei Xia, David Bryan, João.
PSTN – User ENUM – „Infrastructure ENUM“ An ETSI View Richard Stastny IETF60 San Diego.
Ogier - 1 OSPF Database Exchange Summary List Optimization draft-ietf-ospf-dbex-opt-00.txt Richard Ogier Presented by Acee Lindem March 19, 2007 IETF 68.
Draft-rosen-ecrit-emergency- framework-00 Brian Rosen NeuStar CPa
Yang Shi (Richard), Yong Zhang IETF 74 th 26 March 2009, San Francisco CAPWAP WG MIB Drafts Report.
1 Diameter SIP application draft-ietf-aaa-diameter-sip-app-03.txt 60 th IETF meeting August 3 rd, 2004 Status.
Draft-barnes-geopriv-policy-uri. -03 (err… -02) We updated the draft (-02) in early September – … and forgot to post it We updated it again (-03) right.
Page 1IETF 65 ENUM WG IETF 65 – ENUM WG IANA Registration for an Enumservice and “tel” Parameter for Calling Name Delivery (CNAM) Information 20 March.
IETF 69 SIPPING WG Meeting Mohammad Vakil Microsoft An Extension to Session Initiation Protocol (SIP) Events for Pausing and Resuming.
SIP PUBLISH draft-ietf-simple-publish-01 Aki Niemi
IETF-90 (Toronto) DHC WG Meeting Wednesday, July 23, GMT IETF-90 DHC WG1 Last Updated: 07/21/ :10 EDT.
SIP Extensions for Network-Asserted Caller Identity and Privacy within Trusted Networks Flemming Andreasen W. Marshall, K. K. Ramakrishnan,
Interactive Connectivity Establishment : ICE
1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential Conveying Policy URI in Call-info purpose Hisham Khartabil Aki Niemi SIP WG.
Real-Time Streaming Protocol draft-ietf-mmusic-rfc2326bis-01.txt Magnus Westerlund.
SDP Simple Capability Negotiation (SDP Simcap) draft-andreasen-mmusic-sdp-simcap-reqts-00.txt draft-andreasen-mmusic-sdp-simcap-01.txt 50th IETF - March.
- 1 -P. Kyzivatdraft-sipping-gruu-reg-event-00 Reg Event Package Extensions draft-sipping-gruu-reg-event-00 IETF64 Nov-2005.
Balanced Security for IPv6 CPE draft-ietf-v6ops-balanced-ipv6-security-01 IETF89 London M. Gysi, G. Leclanche, E. Vyncke, R. Anfinsen.
March 20, 2007BLISS BOF IETF-681 Requirements and Implementation Options for the Multiple Line Appearance Feature using the Session Initiation Protocol.
IETF 70 – SIMPLE WG SIMPLE Problem Statement draft-ietf-simple-interdomain-scaling-analysis-03 Avshalom Houri – IBM Tim Rang, Sriram Parameswar - Microsoft.
Slide # 1 IETF-62 March 2005Conference Package Conference Package Status March 11 th, 2005 IETF 62, Minnesota draft-sipping-conference-package-09.
SIP Events: Changes and Open Issues IETF 50 / SIP Working Group Adam Roach
March 20th, 2001 SIP WG meeting 50th IETF SIP WG meeting Overlap signalling handling
M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:
Multiple Care-of Address Registration draft-ietf-monami6-multiplecoa-02.txt.
Stir-cnam STIR WG / IETF 95 Buenos Aires, Apr 2016 Jon.
56 th IETF Internet Fax WG Claudio Allocchio Hiroshi Tamura Mar 18 th 2003.
7-May-02SIP/SIPPING Interim Meeting1 Application Interaction Requirements Draft-culpepper-app-interact-reqs-01.txt.
SIP Working Group IETF Chairs -- Rohan MAHY Dean WILLIS.
Draft-smith-abfab- usability-ui- considerations Rhys Smith.
Session-Independent Policies draft-ietf-sipping-session-indep-policy-02 Volker Hilt Jonathan Rosenberg Gonzalo.
THIS IS THE WAY ENUM Variants Jim McEachern
RELO: Retrieving End System Location Information draft-schulzrinne-geopriv-relo-03 Henning Schulzrinne March 2007 IETF68 - GEOPRIV.
E.212 ENUMService Type Definition E.212 Parameters for the "tel" URI
Request-URI Param Delivery
Agenda and Status SIP Working Group
Requirements and Implementation Options for the Multiple Line Appearance Feature using the Session Initiation Protocol (SIP) draft-johnston-bliss-mla-req-00.
draft-ietf-geopriv-lbyr-requirements-02 status update
OpenID Enhanced Authentication Profile (EAP) Working Group
Configuration Framework draft-ietf-sipping-config-framework-06
Jean-François Mulé CableLabs
OpenID Enhanced Authentication Profile (EAP) Working Group
Flemming Andreasen SIP Extensions for Caller Identity and Privacy Flemming Andreasen
RFC PASSporT Construction 6.2 Verifier Behavior
draft-ipdvb-sec-01.txt ULE Security Requirements
SIP RPH and TN Signing Cross Relationship
draft-rocky-sipping-calling-party-category-01 Report
RELO: Retrieving End System Location Information draft-schulzrinne-geopriv-relo-03 Henning Schulzrinne March 2007 IETF68 - GEOPRIV.
INSIPID Session Initiation Protocol (SIP) Extension for logging and debugging (draft-kaithal-dispatch-sip-log-information-00 ) March 26th 2012 IETF -83.
call completion services
Change Proposals for SHAKEN Documents
SIP RPH Signing Use Cases
RFC Verifier Behavior Step 4: Check the Freshness of Date
OpenID Enhanced Authentication Profile (EAP) Working Group
OpenID Enhanced Authentication Profile (EAP) Working Group
OpenID Enhanced Authentication Profile (EAP) Working Group
Presentation transcript:

SIP Extensions for Caller Identity and Privacy Flemming Andreasen W. Marshall, K. K. Ramakrishnan, E. Miller, G. Russell, B. Beser, M. Mannette, K. Steinbrenner, D. Oran, F. Andreasen, J. Pickens, P. Lalwaney, J. Fellows, D. Evans, K. Kelly, M. Watson IETF - March 2001

I-D Status At the last IETF: –To date, very few comments received –No known issues –But “hum” did not reach consensus for WG Last Call Since last IETF –Got one set of comments from Mark Watson –List discussion followed by list consensus on next steps –I-D updated accordingly

The Comments Generalize Remote-Party-ID –Make usable for any type of identity information –Define basic ones and incl. extension mechanism Suggested five specific enhancements: –Requlatory Requirements –Types of Party –Types of Identity –Handling of Privacy Requirements –Location Information

The Comments, cont. Requlatory requirements –Both user and “network” must be able to request privacy. Types of Party –Calling, called, connected, etc. Types of Identity –Subscriber, user, terminal, etc. Handling of privacy requirements –Each type may have its own requirement.

The Comments, cont. Location Information –Physical location of party, e.g. for E911 Fair amount of list discussion led to consensus on: –Generalize Remote-Party-ID as suggested. –Include support for first four enhancements: Requlatory requirements Types of Party Types of Identity Handling of Privacy Requirements

The Comments, cont. Location Information was controversial though. However –Location information not required for all applications. –A URL-based location information scheme could be supported as an extension. Consensus on leaving out the specifics of location information from the draft.

Spec Changes Rpi-token (in Remote-Party-ID) –Removed rpi-type –Added rpi-pty-type, rpi-id-type, and rpi-privacy Anonymity –Removed “full”, “uri”, and “name” Updated processing rules incl. default handling of unknown Remote-Party-ID’s: –Must be marked as “non-screened” –Privacy must be afforded if requested.

Resulting Header Definitions Remote-Party-ID = "Remote-Party-ID" ":" [display-name] " " *(";" rpi-token) rpi-token = rpi-screen |rpi-pty-type | rpi-id-type | rpi-privacy | other-rpi-token rpi-screen = "screen" "=" ("no" | "yes" ) rpi-pty-type = "party" "=" ( "calling" | "called" | token ) rpi-id-type = "id-type" "=" ( "subscriber" | "user" |"alias" | "return" | "term" | token ) rpi-privacy = "privacy" "=" 1#(("full" | "name" | "uri" | "off" | token ) [ "-" ( "network" | token ) ] ) other-rpi-token = token ["=" (token | quoted-string)] Anonymity = "Anonymity" ":" 1#privacy-tag privacy-tag = "ipaddr" | "off" | token