November 2005IETF64 - SIPPING1 Service Identifiers draft-schulzrinne-sipping-service-01 Henning Schulzrinne Columbia University

Slides:

Advertisements

Similar presentations

Service URN Classification and Update Policy (for non-emergency services) Henning Schulzrinne Andrea Forte Columbia University IETF 77 - Anaheim, California.

Advertisements

The architecture diagram of our IPv6 content addressing system. In our system, the regular browser makes a HTTP request through a proxy, which translates.

XCON - IETF 62 (March 2005) - Minneapolis 1 XCON data modeling – NETCONF, RDF and others draft-schulzrinne-sipping-emergency-req-01 draft-sipping-sos Henning.

Origins of ECRIT IETF has been working on location since 2000 –Spatial BoF, eventually GEOPRIV chartered in 2001 GEOPRIV provides location information.

11 June 2015Advanced SIP applications1 Advanced SIP Applications Henning Schulzrinne.

Internet Real-Time Lab, Columbia University Next Generation Project Jong Yul Kim, Wonsang Song, and Henning Schulzrinne.

July 2006IETF66 - ECRIT1 RELO: Retrieving End System Location Information draft-schulzrinne-geopriv-relo-00 Henning Schulzrinne.

Thoughts on dividing the P2P functionality Henning Schulzrinne Columbia University

Internet Real-Time Lab, Columbia University Emergency Calling for VoIP Wonsang Song, Jong Yul Kim, and Henning Schulzrinne.

An Architecture for Location- Based Service Mobility Using the SIP Event Model Ron Shacham, Henning Schulzrinne Columbia University Wolfgang Kellerer,

Where should services reside in Internet Telephony Systems? Xiaotao Wu, Henning Schulzrinne {xiaotaow, Department of Computer Science,

Requirements for Resource Priority Mechanisms for the Session Initiation Protocol draft-ietf-ieprep-sip-reqs-01 Henning Schulzrinne Columbia University.

CS 603 Naming in Distributed Systems January 28, 2002.

NG911 project status Henning Schulzrinne (with Jong Yul Kim, Wonsang Song, Anshuman Rawat, Matthew Mintz-Habib, Amrita Rajagopal and Xiaotao Wu) Dept.

IETF Session Initiation Protocol Henning Schulzrinne Columbia University New York, NY.

SDO Emergency Services Coordination Workshop (ESW06) 1 Emergency Service Identifiers Presented by Henning Schulzrinne Columbia University

March 2006IETF65 - ECRIT1 Emergency Service Identifiers draft-ietf-ecrit-service-urn-01 Henning Schulzrinne Columbia University

1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Emergency calls related work done in IETF Gabor Bajko May 22, 2006.

9.1. The Internet Domain Names and IP addresses. Aims Be able to compare terms such as Domain names and IP addresses URL,URI and URN Internet Registries.

Copyright © 2004, Epok, Inc. Extensible Resource Identifiers (XRIs) XDI Face to Face 28 April 2004.

SDO Emergency Services Coordination Workshop (ESW06) 1 A Location-to-Service Translation Protocol (LoST) & Mapping Protocol Architecture Ted Hardie Andrew.

ECRIT: Emergency Calling Henning Schulzrinne (with Jong Yul Kim, Wonsang Song, Anshuman Rawat, Matthew Mintz-Habib, Amrita Rajagopal and Xiaotao Wu) Dept.

Draft-rosen-ecrit-emergency- framework-00 Brian Rosen NeuStar CPa

1 Location Hiding Henning Schulzrinne Laura Liess Hannes Tschofenig.

August 2005IETF63 - SIPPING1 Recommended Relationships between Different Types of Identifiers draft-schulzrinne-sipping-id-relationships-00 Henning Schulzrinne.

November 2005IETF64 - ECRIT1 Emergency Service Identifiers draft-ietf-sipping-sos-01 draft-schulzrinne-sipping-service-01 Henning Schulzrinne Columbia.

PSAP Callback draft-ietf-ecrit-psap-callback Phone BCP Status Usage Scenarios.

AAA and Mobile IPv6 Franck Le AAA WG - IETF55. Why Diameter support for Mobile IPv6? Mobile IPv6 is a routing protocol and does not deal with issues related.

November 2006IETF67 - GEOPRIV1 A Location Reference Event Package for the Session Initiation Protocol (SIP) draft-schulzrinne-geopriv-locationref-00 Henning.

July 2006IETF66 - ECRIT1 LoST: A Location-to-Service Translation Protocol draft-ietf-ecrit-lost-00 Ted Hardie Andrew Newton Henning Schulzrinne Hannes.

1 Ubiquitous Computing in Home Networks Henning Schulzrinne, Columbia University Stefan Berger, IBM Research IEEE Communication Magazine 2003.

BRIAN ROSEN HANNES TSCHOFENIG HENNING SCHULZRINNE draft-rosen-ecrit-data-only-ea.

Core VoIP and 911 issues and alternatives Henning Schulzrinne Columbia University August 2003.

August 2005IETF 63 - SIPPING Specifying Media Privacy Requirements in SIP Ron Shacham Henning Schulzrinne Dept. of Computer.

1 911 Background  Traditional 911 ~6,000 PSAPs in the US Selective routers route calls to correct PSAP –Operated by carriers –Relies on DB of fixed subscriber.

March 2004GEOPRIV - IETF 59 (Seoul)1 GEOPRIV Policy draft-ietf-geopriv-policy draft-ietf-geopriv-common-policy Henning Schulzrinne Columbia University.

December 2007IETF 70 (Vancouver)1 Applications and Media Information (AMI) Extension to the Presence Information Data Format draft-schulzrinne-simple-ami-00.

Protecting First-Level Responder Resources in an IP-based Emergency Services Architecture 13 th April 2007, THE FIRST INTERNATIONAL WORKSHOP ON RESEARCH.

August 2005IETF63 - SIMPLE1 Solving the identity crisis draft-ietf-geopriv-common-policy-05 Henning Schulzrinne Aki Niemi Hannes Tschofennig Jonathan Rosenberg.

NetCri'07 LoST: A Protocol for Mapping Geographic Locations to Public Safety Answering Points Henning Schulzrinne, Hannes Tschofenig, Andrew Newton, Ted.

Emergency Text Messaging using SIP MESSAGE draft-kim-ecrit-text-00

Emergency Context Resolution with Internet Technologies (ecrit) Hannes Tschofenig, Marc Linsner IETF 65.

Extensions to the Emergency Services Architecture for dealing with Unauthenticated and Unauthorized Devices draft-ietf-ecrit-unauthenticated-access-03.txt.

© 2015 Airbus DS Communications, Inc. All rights reserved. Lights, Camera, NG9-1-1 Diana Gijselaers/ Solutions Engineer – NG9-1-1 GIS and Core Services.

WREC Working Group IETF 49, San Diego Co-Chairs: Mark Nottingham Ian Cooper WREC Working Group.

Emergency Context Resolution with Internet Technologies (ecrit) Hannes Tschofenig, Marc Linsner IETF 66, Montreal, June 2006.

Postech DP&NM Lab Session Initiation Protocol (SIP) Date: Seongcheol Hong DP&NM Lab., Dept. of CSE, POSTECH Date: Seongcheol.

ECRIT - IETF 62 (March 2005) - Minneapolis 1 Requirements for Emergency Calling draft-schulzrinne-sipping-emergency-req-01 draft-ietf-sipping-sos-01 Henning.

August 2005IETF63 - ECRIT1 Service URN draft-schulzrinne-sipping-service-00 Henning Schulzrinne Dept. of Computer Science Columbia University

RELO: Retrieving End System Location Information draft-schulzrinne-geopriv-relo-03 Henning Schulzrinne March 2007 IETF68 - GEOPRIV.

Transcoding Framework

Henning Schulzrinne Dept. of Computer Science Columbia University

Emergency Service Identifiers draft-ietf-ecrit-service-urn-01

Jong Yul Kim, Wonsang Song, and Henning Schulzrinne

Thoughts on VoIP and Emergency Calling

Emergency Calling Architecture

Next Generation Project

Transcoding Framework

Recommended Relationships between Different Types of Identifiers draft-schulzrinne-sipping-id-relationships-00 Henning Schulzrinne (Columbia U.) Eunsoo.

Service URN draft-schulzrinne-sipping-service-00

RELO: Retrieving End System Location Information draft-schulzrinne-geopriv-relo-03 Henning Schulzrinne March 2007 IETF68 - GEOPRIV.

Change Proposals for SHAKEN Documents

Ted Hardie Andrew Newton Henning Schulzrinne Hannes Tschofenig

LbyR discussion Henning Schulzrinne Hannes Tschofenig Richard Barnes

Dept. of Computer Science

Solving the identity crisis draft-ietf-geopriv-common-policy-05

IETF 55 (November 2002, Atlanta)

BINDing URIs to SIP AORs

Active RTP liveness discovery

Presentation transcript:

November 2005IETF64 - SIPPING1 Service Identifiers draft-schulzrinne-sipping-service-01 Henning Schulzrinne Columbia University

November 2005IETF64 - SIPPING2 Motivation Need means to designate a logical service Domain providing service is not known Examples: –emergency services –“411” (directory assistance), repair, operator, … –800# services equivalent Context-dependent resolution –may depend on provider, location, …

November 2005IETF64 - SIPPING3 URN structure urn:service:sname.subsname… urn:service:sname reaches any service of type ‘sname’ Examples: –urn:service:sos –urn:service:sos.fire –urn:service:sos.police –urn:service:sos.marine –urn:service:sos.mountain –urn:service:sos.rescue –urn:service:sos.poison –urn:service:sos.suicide –urn:service:sos.mental-health

November 2005IETF64 - SIPPING4 Why a URN? Identifies a generic service, not a specific resource Uses mapping protocol: –{identifier, location & context}  URL(s) Can be used anywhere a URN/URL is allowed, e.g.: –web pages –result returned by mapping protocol –request and To URI in SIP

November 2005IETF64 - SIPPING5 Suggested behavior Based on today’s list discussion METHOD urn:service:service To: urn:service:service Proxy then converts to METHOD urn:service:service To: urn:service:service Route:

November 2005IETF64 - SIPPING6 Open issues Will get URN list input on syntax Will addressing mechanism work? How generic should this be? Work item?