IETF 89 SIPREC WG

SIPREC Working GroupIETF89 - Friday, March 7th 2014, 11:50-13:20

Mailing list: https://www.ietf.org/mailman/listinfo/siprecTools site: http://tools.ietf.org/wg/siprec/

Charter: https://datatracker.ietf.org/wg/siprec/charter/

Co-Chairs:

Brian Rosen Andy Hutton br@brianrosen.net andrew.hutton@unify.com

Area Director: Gonzalo Camarillo

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. Please consult RFC 3978 (and RFC 4748) 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 be made and may be available to the public.

March 2014 SIPREC IETF89 Chair Slides 2

Logistics

• Note-takers• Jabber scribe• Jabber room: xmpp:siprec@jabber.ietf.org

• Blue sheets• Meetecho: http://www.meetecho.com/ietf89/siprec/

IETF 89 SIPREC WG

AgendaTime Length Who Topic Documents

11:50 - 11:55 5 mins Chairs AdministrativeBlue Sheets, Note takers, Jabber scribes Etc

11:55 - 12:00 5 mins Chairs WG Status Update

12:00 - 12:15 15 mins Charles Eckel SIPREC Protocolhttp://tools.ietf.org/html/draft-ietf-siprec-protocol-12

12:15 - 12:25 10 mins Paul Kyzivat Metadatahttp://tools.ietf.org/html/draft-ietf-siprec-metadata-15

12:25 - 13:05 30 mins Paul Kyzivat Conference Recording

http://tools.ietf.org/html/draft-kyzivat-siprec-conference-use-cases-01 http://tools.ietf.org/html/draft-yan-siprec-msrp-recording-00

13:05 - 13:20 15 mins Gerben Stam Lossless Recording.

 

IETF 89 SIPREC WG

Working Group Status• Use Cases and Requirements

– Done – RFC 6341

• Architecture - draft-ietf-siprec-architecture-12– RFC Editor Queue.

• Protocol - draft-ietf-siprec-protocol-12– WGLC on -010– Some updates – Charles to Present.

• Metadata - draft-ietf-siprec-metadata-15– Updated Feb.– WGLC?

• Call Flows - draft-ietf-siprec-callflows-02– Looking for real world examples – NENA ICE Interop Event – We did not get traces.

• New Work Items?– draft-kyzivat-siprec-webconf-use-case– Lossless Recording.

IETF 89 SIPREC WG

Charter UpdateSession recording is a critical requirement in many business communications environments such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons. In others, calls may be recorded for quality control, business analytics, or consumer protection. Recording is typically done by sending a copy of the media to the recording devices. The working group will determine requirements and produce a specification for a protocol that will manage delivery of media, in SIP based systems (including audio, video, MSRP instant message sessions) from an end-point that originates media, or that has access to it, to a recording device. PBX and recording vendors today implement proprietary, incompatible mechanisms to facilitate recording. A standard protocol will reduce the complexity and cost of providing such recording services.•  

IETF 89 SIPREC WG

MilestonesDONE Use Cases and Requirements to IESG as Informational RFC

MAR 2014 Submit Architecture to IESG as Informational RFC

JUN 2014 Submit protocol draft to IESG as Proposed Standard RFC

AUG 2014 Submit Metadata model and format to IESG as Proposed Standard RFC

AUG 2014 Submit SIPREC Call Flows draft to IESG as an informational RFC

??? 2014 Conference Recording Use Cases and Requirements to IESG as Informational RFC

??? 2014 Conference Recording Architecture to IESG as Informational RFC

??? 2014 Protocol and metadata for MSRP recording to IESG as Proposed Standard RFC

??? 2014 Protocol and metadata for capturing the content (RFC 4796) of the media stream. •  

7IETF 89 SIPREC WG