From 4bc64ff602f6f1e87daa85172f2e2a138b5f86ed Mon Sep 17 00:00:00 2001 From: Philipp Hancke Date: Sun, 15 Dec 2013 17:22:02 +0100 Subject: [PATCH] removed rfc examples (where necessary) as requested --- inbox/jingle-grouping.xml | 1 - inbox/jingle-sources.xml | 51 ++++++++++++++++++--------------------- 2 files changed, 23 insertions(+), 29 deletions(-) diff --git a/inbox/jingle-grouping.xml b/inbox/jingle-grouping.xml index e46e7def..04e0a8c8 100644 --- a/inbox/jingle-grouping.xml +++ b/inbox/jingle-grouping.xml @@ -106,7 +106,6 @@ a=group:LS voice webcam

Thanks to Emil Ivov and Lance Stout for their feedback.

The XML format for this specification originates from libjinglelibjingle is now part of the WebRTC Native Code Package available from webrtc.org..

-

The SDP syntax examples are taken from RFC 5888.

This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.

diff --git a/inbox/jingle-sources.xml b/inbox/jingle-sources.xml index 483c41e5..7bfeb944 100644 --- a/inbox/jingle-sources.xml +++ b/inbox/jingle-sources.xml @@ -79,45 +79,39 @@ a=ssrc-group:<semantics> <ssrc-id> ...

The following example is taken from RFC 5576.

-m=video 49174 RTP/AVPF 96 98 -a=rtpmap:96 H.264/90000 -a=rtpmap:98 rtx/90000 -a=fmtp:98 apt=96;rtx-time=3000 -a=ssrc-group:FID 11111 22222 -a=ssrc:11111 cname:user3@example.com -a=ssrc:22222 cname:user3@example.com -a=ssrc-group:FID 33333 44444 -a=ssrc:33333 cname:user3@example.com -a=ssrc:44444 cname:user3@example.com +m=video 1 RTP/SAVPF 100 116 117 +a=rtpmap:100 VP8/90000 +a=ssrc-group:FID 2301230316 386328120 +a=ssrc:2301230316 cname:T5qvrIZj42v//eYQ +a=ssrc:386328120 cname:uEYgNtStZyTF74sM +a=ssrc-group:FID 3139499595 2613715171 +a=ssrc:3139499595 cname:re8jhxkly9bxzuxr +a=ssrc:2613715171 cname:f83avsiw6n1m7vi

This is mapped to Jingle as follows:

- - - - - + - - + + - - + + - - + + - - + + - - + + - - + + @@ -146,9 +140,10 @@ a=ssrc:44444 cname:user3@example.com ]]>

In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.

+

This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.