1

SIPPING Working GroupIETF 70

Mary Barnes (WG co-chair)Gonzalo Camarillo (WG co-chair)

Oscar Novo (WG Secretary)

2

Intellectual Property● When starting a presentation you MUST say if:

There is IPR associated with your draft The restrictions listed in section 5 of RFC 3978 apply

to your draft

● When asking questions or making comments: You MUST disclose any IPR you know of relating to

the technology under discussion

● Reference: RFC 3978/3979 and “Note Well” text

3

Other Notes● Need at least two Note Takers● Jabber Transcription :

● Need a mediator for Jabber session for questions.● MP3 streaming

● Use the microphone, and state your name

● Wireless: Make sure your computer is not in adhoc mode

4

Tracking Progress● http://www.softarmor.com/sipping/process/

review_procedure.html● Tracking WG documents, including WG reviews,

assignments and status, with proposed WGLC (and IESG) dates for all WG documents.

● Updated about every 4 weeks (5 updates since IETF-69)● Important for doc editors to review deadlines and make

sure current status of docs is accurate. ● WG reviews are cached in the spreadsheet● Information is used by other SDOs to track dependencies.

● Overall progress since IETF-69 has been good: ● Some delays due to authors not generating updates in a timely

manner.● Our AD has been very busy (see next few charts)

5

RFCs Published since IETF 69

● RFC 5057: draft-ietf-sipping-dialogusage

6

RFC Editor’s Queue● draft-ietf-sipping-app-interaction-framework (PS) ● draft-ietf-sipping-transc-conf (PS)● draft-ietf-sipping-transc-framework (Info)

Added since IETF-69:● draft-ietf-sipping-gruu-reg-event (PS)● draft-ietf-sipping-v6-transition (PS)● draft-ietf-sipping-ipv6-torture-tests (Info)● draft-ietf-sipping-spam (Info)

7

IESG Processing● draft-ietf-sipping-uri-services (PS) (IETF LC ends 12/20)

● draft-ietf-sipping-rtcp-summary (PS) (IESG Eval - Revised ID)

● draft-ietf-sipping-toip (Info) (completed IETF LC)

● draft-ietf-sipping-capacity attribute (PS) (IETF LC ends 12/20)

● draft-ietf-sipping-sbc-funcs (Info) ● draft-ietf-sipping-consent-format (PS) (IETF LC ends 12/20)

● draft-ietf-sipping-pending-additions (PS) (IETF LC ends 12/20)

The following are new to this state since IETF-69:● draft-ietf-sipping-service-examples (BCP) (completed IETF

LC) ● draft-ietf-sipping-race-examples (BCP) (AD review completed

– revised ID required)

8

Awaiting Proto write-up● draft-ietf-sipping-cc-framework-08 (WGLC

completed 13 April 2007)● WGLC review Summary: Ready with nits.● Doc is ready for proto review/write-up.● Token: Gonzalo● Editor: Alan Johnston● Reviewers: AC Mahendran, John Elwell, Xavier

Marjou

9

Undergoing Final Updates prior to Proto write-up

● draft-ietf-sipping-config-framework-14 (WG re-review of -13 completed 9 November)

● -14 addresses remaining post-WGLC comments● Concerns remain over details in security section.

Once those are addressed, doc should be ready for Proto review/write-up

● Token: Editor (Sumanth Channabassappa) and design team to propose resolutions for concerns.

● Reviewers: John Elwell, Roni Even, Shida Shubert, Dave Robbins

10

Undergoing Final Updates prior to Proto write-up

● draft-ietf-sipping-sip-offeranswer-04 (post WGLC re-review ended 20 Nov)

● Propose to add some text to address SIPit identified issue, per “what answerer can send" thread

● One last concern in terms of concern over Hold and Resume inconsistency with RFC 3264:

● Text in RFC 3264 is non-normative and has been identified as a bug, thus propose to add discussion of this to section 6.

● 2 week WG re-review of -05 prior to forwarding● Token: Authors (Paul Kyzivat, Takuya Sawada)● Reviewers: Byron Campen, Jonathan Rosenberg, Rajeev Seth,

B. Nataraju

11

WGLC Completed –progression pending WG re-review/proto write-up

● draft-ietf-sipping-overload-reqs (WGLC ended on 21 May 2007)

● Updated version available on 17 November 2007.● WG re-review planned for 10– 24 December (2 weeks

post IETF-70)● Token: Reviewers (Volker Hilt, Spencer Dawkins and

Tolga Asveren) to re-review and provide feedback to WG mailing list.

12

WGLC Completed – progression pending document revisions

● The following 2 documents (coordinated with draft-ietf-sip-policy-framework):

● draft-ietf-sipping-policy-package (WGLC completed 11 Jun 2007)

● draft-ietf-sipping-media-policy-dataset (WGLC completed 11 Jun 2007)

Token: Editor (Volker Hilt) to update document(s) to address remaining outstanding issue with regards to routing streams through multiple intermediaries (currently underspecified and needs clarification). WG reviewers to review updated versions to ensure previous concerns have been addressed.

Reviewers: Roni Even, Jari Urpalainen, Christian Schmidt

Note: related SIP document: draft-ietf-sip-policy-framework

13

● draft-ietf-sipping-service-identification-00 ● Document completed Initial review (including RAI and APPs) on

31 October ● Token: Editor (Jonathan Rosenberg) to address comments

received during initial review. ● WGLC of 10 – 31 Jan 2008 proposed● Current reviewers: Tolga Asveren, Mahesh ● RAI reviewer: Spencer Dawkins● APPs reviewer: Claudio Allocchio

Completed Initial WG Review

14

Undergoing WGLC● None

15

● draft-ietf-sipping-nat-scenarios (WGLC 17 Dec 2007– 14 Jan 2008)

● Document updates underway to ensure alignment with completed ICE.

● Token: Doc editor (Chris Boulton) to submit a version post-IETF-70 with most recent feedback. WG to provide feedback during WGLC.

● Current reviewers: Guarav Kuhlshreshth, Vijay Gurbani, Spencer Dawkins

WGLC planned Dec 2007/Jan 2008

16

Charter Updates Proposed

● Done (Sept 2007) WGLC SIP Offer/Answer Examples ● Dec 2007 (Nov 2007) WGLC NAT scenarios ● Dec 2007 (Nov 2007) Call Control Framework to the IESG as Info ● Jan 2008 (Oct 2007) Requirements for Management of Overload in SIP

to IESG as Info ● Jan 2008 SIP Offer/Answer Examples to IESG as Info● Jan 2008 WGLC Service Identification● Feb 2008 (Oct 2007) Session Policy package to the IESG as PS ● Feb 2008 (Oct 2007) User Agent Profile for Media Policy to the IESG as

PS ● Mar 2008 (Sept 2007) SIP Call Control - Transfer to IESG as Info

(GRUU Dependency)● Mar 2008 (Feb 2008) NAT Scenarios to IESG as Info ● May 2008 Service Identification to IESG as INFO● May 2008 (Dec 2007) Revise Charter

17

Agenda

0900 – 0915 Status and Agenda Bash (Chairs) 0915 – 0925 Overload Design Team (Jonathan Rosenberg) 0925 – 0930 Service Identification (Jonathan Rosenberg) 0930 - 0955 UA Profile Datasets (Sam Ganesan) 0955 – 1010 Updates to Asserted Identity (John Elwell) 1010 – 1025 Support for Application Profile Types (Salvatore Loreto) 1025 – 1040 Scaling Requirements for Presence (Avashalom Houri) 1040 – 1055 SIP URI Service Discovery using DNS-SD (Henning

Schulzrinne) 1055 – 1105 SPAM Score (Dan Wing) 1105 – 1115 SRTP Key Disclosure (Dan Wing)

Note: for the first time in eons, there is only one SIPPING WG session.

18

Other drafts of interest● As usual, WG documents receive priority for agenda

slots ● Other documents get agenda time based on level of

mailing list discussion and issues requiring discussion

● All agenda requests, with links to docs, are logged at: http://www.softarmor.com/sipping/meets/ietf70/Agenda_request.html

● Single slide per topic always welcome for documents not receiving agenda time.

19

Basic KPML● Arguments against KPML

● Too hard for itty-bitty big gateway to dynamically generate XML

● Too hard for itty-bitty big gateway to parse and run digit map recognition engine

● Too hard for tiny applications to create KPML request document

● Basic KPML● Profile of KPML that auto-subscribes

<regex>.</regex> pattern● Fully forward-compatible with KPML

● Does anyone care, or are arguments bogus?

20

Text conversation turntaking limitationsdraft-hellstrom-text-turntaking-00.txt

● Need for gateways SIP devices <> PSTN textphones. ● For indication to SIP device user what turn-taking habits must be

applied.● For routing to the most capable device for text conversation.

● Defines a Media feature tag sip.text-turntaking to be declared by gateways

● Proposed values: no, unspecified, soft, strict● Values match different PSTN textphone types behind a PSTN/SIP gateway.● Needed to avoid confusion for SIP text users who are used to full

simultaneity of text and voice.● Same function was discussed as an SDP media-contents attribute in

mmusic, but cancelled.● Is using the SIP Media feature tag right way to go?● Is there interest in this work in the SIPPING WG?

V.18 ToIP

ToIP able SIP PhoneToIP-PSTN GWPSTN Textphone

21

Real time text gateway BCPdraft-hellstrom-txtgwy-00

● SIP devices with real-time text capability may interoperate with textphones through gateways

● This BCP describes● Routing through text capable gateways● Indicating text capabilities● Media handling between limited functionality PSTN

textphones and full functionality SIP devices● Starting text usage mid-call and alternating text-voice● SDP examples

● Builds on requirements from draft-ietf-sipping-toip ● Is there interest in this work in the SIPPING WG?

22

23

Backup

24

Important Doc Dependencies

draft-ietf-sipping-config-framework

draft-petrie-sipping-profile-dataset

draft-ietf-sipping-media-policy-dataset

draft-ietf-sipping-policy-package

draft-ietf-sip-session-policy-framework