1

draft-manyfolks-sip-resource-01draft-manyfolks-sip-resource-01W. Marshall, K. K. Ramakrishnan, E. Miller, G. Russell, B. Beser, M. Mannette, K. Steinbrenner, D. Oran,

F. Andreasen, M. Ramalho, W. Guckel, J. Pickens, P. Lalwaney, J. Fellows, D. Evans, K. Kelly, A. Roach, J. Rosenberg, H.Schulzrinne, S. Donovan, D. Willis

draft-dcsgroup-sip-privacy-02draft-dcsgroup-sip-privacy-02draft-dcsgroup-sip-state-02draft-dcsgroup-sip-state-02

draft-dcsgroup-sip-call-auth-02draft-dcsgroup-sip-call-auth-02draft-dcsgroup-sip-arch-02draft-dcsgroup-sip-arch-02

draft-dcsgroup-sip-proxy-proxy-02draft-dcsgroup-sip-proxy-proxy-02W. 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

AT&T, CableLabs, 3Com, Cisco, Columbia University, Com21, dynamicsoft, Ericsson, Motorola, NetSpeak, Nokia, Secure Cable Solutions

July 2000

IETF Presentation

“manyfolks” and “dcsgroup” drafts

2

Changes in current versionsChanges in current versions

RFC2026 compliance

minor technical changes many editorial changes

3

Draft-manyfolks-sip-resource-01Draft-manyfolks-sip-resource-01

RFC2026 compliant

Handles UAS desiring preconditions when UAC didn’t specify any

4

Draft-dcsgroup-sip-privacy-02Draft-dcsgroup-sip-privacy-02

RFC2026 compliant

Proxy-Require: privacy

Removed authentication from this header– authentication to be included in a general SIP authentication/security

mechanism

Removed OSPS

Document restructured to conform to guidelines for SIP extensions

5

Draft-dcsgroup-sip-state-02Draft-dcsgroup-sip-state-02

RFC2026 compliant

Require: State Supported: State

Handles interaction between State header and Via encryption– need for “Proxy-Require: state” to ensure proper handling

Open issue of Record-Route/Route encryption Pending update: change of “host” to “hostport” in syntax

Document restructured to conform to guidelines for SIP extensions

6

Draft-dcsgroup-sip-call-auth-02Draft-dcsgroup-sip-call-auth-02

RFC2026 compliant

minor editorial changes only, no technical changes

7

Draft-dcsgroup-sip-arch-02Draft-dcsgroup-sip-arch-02

RFC2026 compliant

Added call flow diagrams and detailed message flows

Targeted as Informational RFC

8

Draft-dcsgroup-sip-proxy-proxy-02Draft-dcsgroup-sip-proxy-proxy-02

RFC2026 compliant

Full description of DCS-specific extensions– Dcs-Trace-Party-ID tracing of obscene/harassing calls

– Dcs-Gate resource coordination

– Dcs-Also, Dcs-Replace call transfer and three-way-calling

– Dcs-OSPS busy-line verification and emergency int

– Dcs-Billing-ID, Dcs-Billing-Info coordination of billing information

– Dcs-LAES, Dcs-Redirect CALEA obligations

Require: Dcs Targeted as informational RFC

– Reference document for IANA registration of header names

9

Next StepsNext Steps

DCS System design complete, specification available on web– http://www.softarmor.com/sipwg/drafts/dcsdraft2.pdf

– ftp://ftp.cablelabs.com/pub/ietfdocs/dcsdraft2.pdf

Progress as informational RFC– draft-dcsgroup-sip-arch-02

– draft-dcsgroup-sip-proxy-proxy-02

Progress as SIP extensions as part of Working Group items– draft-manyfolks-sip-resource-01

– draft-dcsgroup-sip-privacy-02

– draft-dcsgroup-sip-state-02

– draft-dcsgroup-sip-call-auth-02