1 / 14

SIPPING Working Group IETF 63

This is a note for the SIPPING Working Group at IETF 63, outlining the rules and guidelines for contributions and statements made during the session.

samuelcarroll
Télécharger la présentation

SIPPING Working Group IETF 63

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 63

  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 3978 and RFC 3979. 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 3978 for details.

  3. Other Notes • Need a Note Taker • Need a scribe for Jabber session • MP3 streaming • Use the microphone, and state your name • TISPAN Ad-Hoc Yesterday • P2P SIP Ad-Hoc Today in the Morning • Supplemental web page: • http://www.softarmor.com/sipping • Wireless: Make sure your computer is not in adhoc mode

  4. Agenda: Wednesday 1030 Status and Agenda Bash - Chairs 1045 Data Sets - Dan Petrie 1110 Session Policies - Volker Hilt 1140 Consent Framework - Gonzalo Camarillo 1210 Unfriendly Functions - Jani Hautakorpi 1220 Event Throttles – Aki Niemi

  5. Agenda: Thursday 1030 Agenda Bash - Chairs 1035 ToIP - Arnoud van Wijk 1045 Config -- Dan Petrie 1115 HERFP – Rohan Mahy 1125 TISPAN - Roland Jesske 1150 P-Answer-State – Andrew Allen 1205 Implicit Subscriptions – Jonathan Rosenberg 1215 Media Privacy - Henning Schulzrinne 1220 SIP User Identifiers - Henning Schulzrinne

  6. Post Publication Requested Drafts • RFCs published since IETF 60: • RFC 3824:Using E.164 numbers with SIP • RFC 4083: Input 3GPP R5 Requirements on SIP • RFC 4117:Transcoding Services Invocation in SIP 3pcc • In RFC Editor Queue • Conferencing for UAs • Conferencing Requirements • Dialog Package • E2M Security Requirements • KPML

  7. Post Publication Requested Drafts • With Area Director or IESG • Conferencing Framework (approved) • Conferencing Package (approved) • QSIG to SIP (waiting for publication writeup) • Torture Test (S/MIME issue) • Reason Header for Preemption • Application Interaction • Caller Preferences Use Cases • Configuration Framework

  8. Post WGLC Drafts • URI-list Services Drafts • waiting for consent framework • RTCP Summary • Submission problem • Trait-based Authorization • Few comments during WGLC. Is it really ready? • PoC Settings Event Package (expert review)

  9. Ongoing WGLCs • Call Control Transfer

  10. Open Issue • Multiple-recipient MESSAGE • Done, waiting for consent • Inconsistent with SIP guidelines for extensions and NIT actions. • Do we need it? Rohan doesn’t think so… • Is using message sessions an alternative?

  11. Some Individual Submissions • draft-sohel-sipping-s-bc-concept-arch-00.txt • Chairs think this is probably out of scope • draft-elwell-sipping-redirection-reason-02.txt • Focuses on PSTN interworking, not on the 302 Ambiguity Problem • May be needed for TISPAN • draft-levin-simple-interdomain-reqs-02.txt • What do we do with this? • draft-ma-h323-sip-conf-requirement-00.txt • Chairs think this is probably out of scope • draft-hasebe-sipping-exceptional-procedure-example-01.txt • Useful work, should we adopt it or support it as individual?

  12. Motivation • Clarifying exceptional procedures • They are specified by RFCs, but It may be difficult to interpret how a terminal actually operates.(of course, although it is possible) • Contents of exceptional procedures 1.sip-implementors mailing list logs 2.The transition of dialog state

  13. Milestones Aug 05 Requirements on Trait-Based Authorization to IESG as Info Sep 05 Requirements for Consent-based Communications in SIP to IESG as Info Sep 05 Service Quality Reporting to IESG as PS Sep 05 Revise Charter Nov 05 Transcoding with Conf Bridge to IESG as Info Nov 05 Transcoding Framework to IESG as Info Nov 05 Session Policy Requirements to IESG as Info Nov 05 Framework for Consent-based Communications in SIP to IESG Nov 05 Submit URI List Transport Mechanism to the IESG as PS Nov 05 Submit I-D on Ad-Hoc Conferencing using URI lists to the IESG as PS Nov 05 Submit I-D on Multiple REFER to the IESG as PS Nov 05 Submit I-D on Subscriptions to Ad-Hoc Resource Lists to the IESG as PS Jan 06 Session Independent Policy Mechanism to the IESG as PS Jan 06 Session Specific Policy Mechanism to the IESG as PS Feb 06 SIP Service Examples to IESG as Info Feb 06 IPv6 Transition in SIP to the IESG as Info

  14. Milestones Delete Event Filtering Requirements to the IESG as Info Delete Location Requirements to IESG as Info Done KPML to IESG as PS Done End-to-Middle Security Requirements to IESG as Info Done Conferencing Requirements to IESG as Info Done Conferencing Framework to IESG as Info Done Conferencing Call Control-Conferencing to IESG as BCP Done Caller Preferences Use Cases to IESG as Info Done Configuration Framework to the IESG as a PS

More Related