Hi Gaurav, One of the main drivers for creating BFCP within the IETF was for content arbitration; however, there is not an RFC mandating the use of BFCP for content arbitration. Other mechanisms and conventions may be defined and used. There are industry best practices such as the IMTC's " Best Practices for Role‐Based Video Streams (RBVS) in SIP" to which you may want to refer for guidance. It is an internal IMTC document, but it has been shared with the IETF via a liaison statement (https://datatracker.ietf.org/liaison/1170/ ) through which it may be accessed by non-IMTC members.
Cheers, Charles > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Gaurav Kumar > Sent: Friday, September 28, 2012 6:22 AM > To: [email protected] > Subject: [Sip-implementors] BFCP query for content channel > > Hi All, > > I have following query on BFCP. > > > In the following SDP message from a Tandberg device, it mentions use of > BFCP for video media (label:12). Does it mean that without using BFCP, a > media session cannot be established on port: 2370 for second video > channel? Is there any means to bypass use of BFCP? > > For supporting content-arbitration or media-arbitration, Is BFCP a MUST > requirement? > > > INVITE sip:10.164.62.90 SIP/2.0 > Via: SIP/2.0/UDP > 10.164.62.69:5060;branch=z9hG4bKdec2e7fc2966051ad7d49dc54b55acc2.1;rp > ort > Call-ID: > [email protected]<mailto:[email protected]> > CSeq: 100 INVITE > Contact: <sip:10.164.62.69:5060> > From: <sip:10.164.62.69>;tag=fb65456ca9d8b501 > To: <sip:10.164.62.90> > Max-Forwards: 70 > Allow: INVITE,ACK,CANCEL,BYE,UPDATE,INFO,OPTIONS,REFER,NOTIFY > User-Agent: TANDBERG/515 (TC4.1.0.247017) > Supported: replaces,100rel,timer,gruu,path,outbound > Session-Expires: 1800 > Content-Type: application/sdp > Content-Length: 2258 > > > v=0 > o=tandberg 7 1 IN IP4 10.164.62.69 > s=- > c=IN IP4 10.164.62.69 > b=AS:768 > t=0 0 > m=audio 2366 RTP/AVP 100 101 102 103 104 9 8 0 105 > b=TIAS:64000 > a=rtpmap:100 MP4A-LATM/90000 > a=fmtp:100 profile-level-id=24;object=23;bitrate=64000 > a=rtpmap:101 MP4A-LATM/90000 > a=fmtp:101 profile-level-id=24;object=23;bitrate=56000 > a=rtpmap:102 MP4A-LATM/90000 > a=fmtp:102 profile-level-id=24;object=23;bitrate=48000 > a=rtpmap:103 G7221/16000 > a=fmtp:103 bitrate=32000 > a=rtpmap:104 G7221/16000 > a=fmtp:104 bitrate=24000 > a=rtpmap:9 G722/8000 > a=rtpmap:8 PCMA/8000 > a=rtpmap:0 PCMU/8000 > a=rtpmap:105 telephone-event/8000 > a=fmtp:105 0-15 > a=sendrecv > > m=video 2368 RTP/AVP 97 98 99 34 31 > b=TIAS:768000 > a=rtpmap:97 H264/90000 > a=fmtp:97 profile-level-id=428014;max-br=3333;max-mbps=245000;max- > fs=9000;max-smbps=245000 > a=rtpmap:98 H264/90000 > a=fmtp:98 profile-level-id=428014;max-br=3333;max-mbps=245000;max- > fs=9000;max-smbps=245000;packetization-mode=1 > a=rtpmap:99 H263-1998/90000 > a=fmtp:99 > custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1 > ;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom= > 352,240,1;qcif=1;maxbr=7680 > a=rtpmap:34 H263/90000 > a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=7680 > a=rtpmap:31 H261/90000 > a=fmtp:31 cif=1;qcif=1;maxbr=7680 > a=rtcp-fb:* nack pli > a=sendrecv > a=content:main > a=label:11 > a=answer:full > > m=application 5070 UDP/BFCP * > a=floorctrl:c-s > a=confid:1 > a=floorid:2 mstrm:12 > a=userid:7 > a=setup:passive > a=connection:new > > m=video 2370 RTP/AVP 97 98 99 34 31 > b=TIAS:768000 > a=rtpmap:97 H264/90000 > a=fmtp:97 profile-level-id=428014;max-br=3333;max-mbps=58000;max- > fs=3840;max-smbps=58000 > a=rtpmap:98 H264/90000 > a=fmtp:98 profile-level-id=428014;max-br=3333;max-mbps=58000;max- > fs=3840;max-smbps=58000;packetization-mode=1 > a=rtpmap:99 H263-1998/90000 > a=fmtp:99 > custom=1280,720,3;custom=1024,768,2;custom=1024,576,2;custom=800,600,1 > ;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom= > 352,240,1;qcif=1;maxbr=7680 > a=rtpmap:34 H263/90000 > a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=7680 > a=rtpmap:31 H261/90000 > a=fmtp:31 cif=1;qcif=1;maxbr=7680 > a=rtcp-fb:* nack pli > a=sendrecv > a=content:slides > a=label:12 > > m=application 2372 RTP/AVP 106 > a=rtpmap:106 H224/4800 > a=sendrecv > > > Sincerely, > Gaurav Kumar > > > > > This is confidential Ittiam property. > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
