1 / 13

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

Mary Barnes (SIPPING WG co-chair) Gonzalo Camarillo (SIPPING WG co-chair) Keith Drage (SIP WG co-chair) Dean Willis (SIP WG co-chair). SIPPING WG SIP and SIPPING work items IETF-74. Note Well.

hieu
Télécharger la présentation

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

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. Mary Barnes (SIPPING WG co-chair) Gonzalo Camarillo (SIPPING WG co-chair) Keith Drage (SIP WG co-chair) Dean Willis (SIP WG co-chair) SIPPING WG SIP and SIPPING work items IETF-74

  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 5378 and RFC 3979 (updated by RFC 4879). 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 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

  3. Logistics Need two notetakers - capture highlights and conclusion/consensus/way forward Jabber address jabber.ietf.org - room name sipping Remote audio address http://videolab.uoregon.edu/events/ietf/ When using the microphone: Speak into it, and don’t turn and face the opposite direction half way through what you need to say Speak clearly Say your name slowly and clearly before you start to speak

  4. Organisation of SIP and SIPPING sessions 3 sessions in total In session 1 we will present proposed new structure for SIP work in IETF, and in session 3 we will discuss it Session 1 contains mainly items that will in future be discussed in SIP CORE, if the proposal proceeds Session 2 contains mainly items that will in future be discussed in DISPATCH if the proposal proceeds Session 3 contains current continuing work Slides for the individual sessions (no matter which WG the draft is currently allocated to) Session 1 and session 2 will be in the SIP meeting management tool area Session 3 will be in the SIPPING meeting management tool area

  5. RFCs Published since IETF 73 RFC 5407: draft-ietf-sipping-race-examples (BCP) RFC 5390: draft-ietf-sipping-overload-reqs (Info)

  6. RFC Editor’s Queue draft-ietf-sipping-app-interaction-framework (PS) draft-ietf-sipping-gruu-reg-event (PS) draft-ietf-sipping-v6-transition (PS)

  7. IESG Processing draft-ietf-sipping-rtcp-summary (IESG Eval - Revised ID) draft-ietf-sipping-sbc-funcs draft-ietf-sipping-cc-transfer-09 (AD evaluation) draft-ietf-sipping-policy-package-04 (AD Evaluation) draft-ietf-sipping-config-framework-14 (AD evaluation: External Party) draft-ietf-sipping-sip-offeranswer-09 (Waiting AD go-ahead) draft-ietf-sipping-cc-framework (AD Evaluation) draft-ietf-sipping-service-identification-03 (Pub Request) • draft-ietf-sipping-policy-package-04 (AD Evaluation) • draft-ietf-sipping-config-framework-14 (AD evaluation: External Party) • draft-ietf-sipping-sip-offeranswer-09(AD evaluation - Back to WG for discussion) • draft-ietf-sipping-cc-framework (Pub Request) Added since IETF-72: • draft-ietf-sipping-service-identification-03 (Pub Request)

  8. WG Documents draft-ietf-sipping-media-policy-dataset: Awaiting completion of profile-datasets draft-ietf-sipping-overload-design: In Progress (On Agenda) draft-ietf-sipping-presence-scaling-requirements: Awaiting final re-review –> proto write-up draft-ietf-sipping-profile-datasets: In Progress (On Agenda) draft-ietf-sipping-nat-scenarios: Awaiting completion of TURN • draft-ietf-sipping-policy-package-04 (AD Evaluation) • draft-ietf-sipping-config-framework-14 (AD evaluation: External Party) • draft-ietf-sipping-sip-offeranswer-09(AD evaluation - Back to WG for discussion) • draft-ietf-sipping-cc-framework (Pub Request) Added since IETF-72: • draft-ietf-sipping-service-identification-03 (Pub Request)

  9. Other Documents of Interest

  10. SIP End-to-End Performance Metrics • Background • SIP service providers (SSP) and vendors are using PSTN-based metrics attempting to apply them to SIP applications • Metric definitions vary by implementation • Scope • Define a common set of SIP metrics for measuring end-to-end performance • Use metrics familiar to SSPs adapted for SIP • History • Work began in SIPPING and was eventually moved to Performance Metrics for Other Layers (PMOL) to ensure alignment with other IETF metrics work • First WGLC ended July 25, 2008 • PMOL WG consensus is that draft is ready for IESG or potentially one more short WGLC • Resources • Draft available here: draft-ietf-pmol-sip-perf-metrics-03 • IETF 74 PMOL slide presentation available here: SIP Perf Metrics • Request • SIP “experts” to review the draft for protocol reference accuracy • Any general feedback from the SIPPING working group

  11. The atypes media feature tag draft-boucadair-sipping-ipv6-atypes-01 • Motivation • Proxy Servers need a means to determine when to invoke NAT/SIP-ALG adaptation functions when UAs that support different IP versions are involved in a session • UAs that support IPv4 and IPv6 may have limitations that prevent them supporting both IPv4 and IPv6 simultaneously (e.g due to access limitations such as PDP context of single IP version, IPv6 only SIP networks or UA stack limitation) • Proposal • atypes media feature tag allows Intermediary nodes to invoke NAT/SIP-ALG adaptation functions only when required ensuring optimal media routing • atypes media feature tag indicates whether • a device supports IPv4 for both signaling and media, • IPv6 for both signaling and media, • IPv6 for signaling and IPv4 for media simultaneously, • IPv4 for signaling and IPv6 for media simultaneously

  12. SIP and XMPP Combined Usedraft-veikkolainen-sip-voip-xmpp-im Scenario An endpoint that integrates SIP User Agent and XMPP client functionality SIP is used for voice and video, XMPP for presence and IM Proposed extensions to SIP (INVITE) A header to carry endpoint’s XMPP contact URI A header to carry carry correlation info of an existing XMPP IM thread between endpoints voice, video Integrated Endpoint Integrated Endpoint SIP SIP SIP SIP Unmodified servers XMPP XMPP XMPP XMPP presence, IM

  13. Agenda Friday 9:00 – 11:30 Status and agenda bash: Chairs 5 Re-INVITE Handling in SIP & Media State under Preconditions in SIP: Gonzalo Camarillo 15 Reject-offer-in-PRACK-issue (based on ML discussion): Christer Holmberg 15 Identity: Hadriel Kaplan 25 Profile datasets: Dale Worley 15 SIP overload control: Volker Hilt 15 Event throttling: Salvatore Loreto 15 SIP change process discussion: Jon Peterson 45

More Related