SIP URI Conventions for Media Servers IETF 51 8 August 2001 - - PowerPoint PPT Presentation

▶

Jul 16, 2023 318 likes •448 views

SIP URI Conventions for Media Servers IETF 51 8 August 2001 draft-burger-sipping-msuri-00.txt 1 What is This About? Standard Conventions for Accessing Media Server Resources How Does One: Play Announcements Create and

SLIDE 1

8 August 2001 draft-burger-sipping-msuri-00.txt 1

SIP URI Conventions for Media Servers

IETF 51

SLIDE 2

8 August 2001 draft-burger-sipping-msuri-00.txt 2

What is This About?

Standard Conventions for Accessing Media

Server Resources

How Does One:

– Play Announcements – Create and Control Conferences – Setup Transcoding – Perform Interactive Voice Response (IVR) – Etc.

SLIDE 3

8 August 2001 draft-burger-sipping-msuri-00.txt 3

Do We Already Have This?

RFC 3087 – Informational

– Introduces Idea of Using Request-URI for “Doing Things” – Example is an Application (Voice Mail) – Ad Hoc, Per Application LHS Definitions

draft-rosenberg-sip-vxml-00.txt

– Ad hoc Use of LHS of Request-URI to Access Media Server Functions for VoiceXML

SLIDE 4

8 August 2001 draft-burger-sipping-msuri-00.txt 4

The Point

Schema for Defining Access to Resource

Functions

– Extensible – Human and Machine Readable

Standard Mechanism for Specifying a

“Service Indicator”

SLIDE 5

8 August 2001 draft-burger-sipping-msuri-00.txt 5

Media Server URI Format

LHS of Request-URI is a Service Indicator

– Service Name (annc, conf, xcod, vxml, …) – Service Instance (conference-id, #URL)

Direct Analogue to User at User Agent

– The Service is a Thing at the Media Server That Performs Useful Work conf=conference24@ms.carrier.net

SLIDE 6

8 August 2001 draft-burger-sipping-msuri-00.txt 6

Unhappy Path

Unrecognized / Malformed Service Name

– 488 Not Acceptable Here

Unrecognized Service Instance

– 404 Not Found

Invariant for All Services

SLIDE 7

8 August 2001 draft-burger-sipping-msuri-00.txt 7

Open Issue: Dots, Dashes, Equals, or Something Else?

RFC 3087 Showed Dashes by Example

– No Distinction Between Service Name and Parameters – Examples Hard to Parse: Service Name Embedded in Request LHS

draft-rosenberg-sip-vxml-00.txt Showed Dots by

Example

– Service Name Comes First – No Distinction Between Service Name and Parameters

SLIDE 8

8 August 2001 draft-burger-sipping-msuri-00.txt 8

Propose Equals

Distinguishes Service Name from

Parameters

Obvious to Human What is Being

Requested

SIP UAS Only Needs to Understand a

Single Parser

SLIDE 9

8 August 2001 draft-burger-sipping-msuri-00.txt 9

Issue: Draft Title

It’s Not Just for Media Servers
Example: Using xcod for Human Speech-

to-Text (draft-vanwijk-sipping- deaf-req-00.txt)

SLIDE 10

8 August 2001 draft-burger-sipping-msuri-00.txt 10

Changes in –01 Planned

Drop Request-URI Password Discussion
Reference Bis Everywhere Instead of 2543

– 488 Reason Code

Tidy Abstract
Drop the X- token

SLIDE 11

8 August 2001 draft-burger-sipping-msuri-00.txt 11

Discussion on List

SIPPING Thread