Subject: RE: [MMUSIC] Protocol Action: 'Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams' to Proposed Sta ndard

From: "Drage, Keith (Keith)" <[email-masked]>
Date: Tue, 10 Jan 2006 11:40:02 -0000

Both 

http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-03.txt
http://www.ietf.org/internet-drafts/draft-ietf-xcon-bfcp-06.txt

were approved by IESG at the same time and are now in the RFC editor's queue. The only outstanding work in this area is

http://www.ietf.org/internet-drafts/draft-ietf-xcon-bfcp-connection-00.txt

which implements additional security requirements discussed in the last IETF meeting.

The relationship of BFCP with other protocols in conferencing is discussed in the two framework documents:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-conferencing-framework-05.txt
http://www.ietf.org/internet-drafts/draft-ietf-xcon-framework-02.txt

The first of these is approved by IESG and in the RFC editor's queue. The second is still under discussion in the XCON WG.

regards

Keith

Keith Drage
Lucent Technologies
[email-masked]
tel: +44 1793 776249

> -----Original Message-----
> From: [email-masked] 
> [mailto:[email-masked]]On Behalf
> Of miguel
> Sent: 09 January 2006 20:37
> To: The IESG; [email-masked]
> Subject: Re: [MMUSIC] Protocol Action: 'Session Description Protocol
> (SDP) Format for Binary Floor Control Protocol (BFCP) Streams' to
> Proposed Standard
> 
> 
> It's a very intresting draft..... but, if BFCP is only a 
> draft jet, what 
> could it be the standatr to have compilance when sharing 
> resourses with SIP?
> 
> Regards
> 
> Miguel
> 
> 
> The IESG wrote:
> 
> >The IESG has approved the following document:
> >
> >- 'Session Description Protocol (SDP) Format for Binary 
> Floor Control Protocol 
> >   (BFCP) Streams '
> >   <draft-ietf-mmusic-sdp-bfcp-03.txt> as a Proposed Standard
> >
> >This document is the product of the Multiparty Multimedia 
> Session Control 
> >Working Group. 
> >
> >The IESG contact persons are Allison Mankin and Jon Peterson.
> >
> >A URL of this Internet-Draft is:
> >http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-03.txt
> >
> >Technical Summary
> > 
> >    This document specifies how to describe Basic Floor Control
> >    Protocol (BFCP) streams in SDP session descriptions.
> >    User agents using the offer/answer model to establish
> >    BFCP streams use this format in their offers and their answers.
> >    BFCP is defined by an accompanying specification from the
> >    XCON working group.  This document also describes
> >    key management and security principles for BFCP establishment,
> >    using existing protocol capabilities available through SDP.
> > 
> >Working Group Summary
> > 
> >   There was strong working group consensus behind this draft.
> > 
> >Protocol Quality
> > 
> >  The protocol has been reviewed by the MMUSIC working group. It
> >  defines a number of new SDP parameters within the existing 
> framework. 
> >  The new parameters are not controversial.
> >
> >  Allison Mankin has acted as the Area Director for the 
> document in order
> >  to coordinate this document with the XCON BFCP document.  
> Colin Perkins is
> >  the WG Chair shepherd for this document.  The Editor, 
> Gonzalo Camarillo,
> >  took  the initiative in shepherding the Discuss comments.
> >   
> >
> >Note to RFC Editor
> > 
> > Replace Reference 3 (RFC 2234) with a reference to RFC 4234.
> >
> >
> >_______________________________________________
> >mmusic mailing list
> >[email-masked]
> >https://www1.ietf.org/mailman/listinfo/mmusic
> >
> >  
> >
> 
> 
> _______________________________________________
> mmusic mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

_______________________________________________
mmusic mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mmusic