1 / 10

SIPPING Working Group IETF 60

Dean Willis Gonzalo Camarillo Rohan Mahy. SIPPING Working Group IETF 60. Note Well.

clove
Télécharger la présentation

SIPPING Working Group IETF 60

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Dean Willis Gonzalo Camarillo Rohan Mahy SIPPING Working GroupIETF 60

  2. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • the IETF plenary session, • any IETF working group or portion thereof, • the IESG, or any member thereof on behalf of the IESG, • the IAB or any member thereof on behalf of the IAB, • any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, • the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details.

  3. Other Notes • Need a Note Taker • Need a scribe for Jabber session • Wireless: Make sure your computer is not in adhoc mode

  4. Agenda: Monday 1530 Call to Order and Agenda Bash — Chairs 1535 Status — Chairs 1350 App Interaction — Jonathan Rosenberg 1605 KPML — Martin Dolly / Eric Burger 1625 Dialog Package — Rohan Mahy 1635 Event Throttles — Aki Niemi 1645 SIP URI services and Consent — Gonzalo 1720 SIP URI-List Index — Tom Hiller 1730 Break

  5. Agenda: Friday 0900 Call to Order and Agenda Bash — Chairs 0905 Conferencing Design Team — Alan Johnston? 0920 Configuration — Dan Petrie 0945 Session Independent Policies — Volker Hilt 0950 Session-Specific Policies — Gonzalo Camarillo 1020 Providers Policies — Kumiko Ono 1030 End-to-Middle Security — Kumiko Ono 1040 Location Requirements — James Polk 1045 NAT Scenarios — Jonathan Rosenberg 1100 Multiple Dialog Usages — Robert Sparks 1110 Redirection Reason — John Elwell 1120 Extension to Reg Event Package — Paul Kyzivat 1130 Done

  6. Post WGLC drafts: • RFCs published since IETF 59: • RFC 3824: Using E.164 with SIP • RFC 3725: 3pcc (Third-Party Call Control) • RFC 3680: Register Event Package • In RFC Editor Queue • Message Waiting • Early Media • Early-Session Disposition • With Area Director • 3GPP R5 Requirements • QSIG to SIP • Transcoding via 3pcc

  7. Pre WGLC drafts • cc-transfer — include Petrie's issues, send to WGLC • torture tests — ready for detailed volunteer review • transcoding fw — needs author cycles • transcoding via conferencing — need author cycles • sos — pending feedback from URI list • service examples — • cc-framework — bad author. no author cookie. • reason header for preemption — waiting for RP • traitz — 

  8. Milestones Jul 04 • KPML Aug 04 • Conferencing Requirements, Framework, cc-conferencing Sep 04 • Location Reqs, E2M Reqs, Traitz Reqs Oct 04 Config List Services Requirements and FW URI List Nov 04 URI List for INVITE, SUB, MESSAGE, REFER

  9. Milestones, Cont. Dec 04 • Event Filtering • Caller Pref Usecases • Service Examples • Session Policy Requirements Jan 05 • Session Independent Policies Feb 05 • Transcoding Framework and with Conferencing Mar 05 • Session Specific Policies

  10. REFER issues • draft-olson-sipping-refer-extensions • 2 non-controversial extensions to REFER • norefersub • allow Refer-To to contain feature parameters • app interaction (discussed later) • defines a Refer-To header parameter to provide the context (call-id and tags) • same info but different syntax than KPML uses in Event header • mahy-remote-cc / sparks-multiple-dialog-usages • same idea as app interact, but suggests different syntax • What do we do with these REFER extensions?

More Related