
From tomkrist@cisco.com  Fri Jan  4 07:21:09 2013
Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEA7821F88F5 for <bfcpbis@ietfa.amsl.com>; Fri,  4 Jan 2013 07:21:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RCL+qb8FjT9k for <bfcpbis@ietfa.amsl.com>; Fri,  4 Jan 2013 07:21:08 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 96C2F21F88B9 for <bfcpbis@ietf.org>; Fri,  4 Jan 2013 07:21:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3208; q=dns/txt; s=iport; t=1357312868; x=1358522468; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=W4AjXLBry0FMYD2w9q8Id4O8bQH7A1jDMAbFeI/o9JQ=; b=Y5+7qi78HNNfjiX4c88kObjF7c0t4/mxoSuDji2+XDy9ZKwwAyLwU35L 0Cs9C1rUOVXBhjmyudccJaEpGPn2cUaqgEJWH8jvWNWkWuMmBfhzv47m8 OHPC3/mZ2q++xQx+Te1Sgbn6MvjGkNyA8FOjRNKb+qRRDfG2+R7zAuzvz g=;
X-IronPort-AV: E=Sophos;i="4.84,411,1355097600"; d="scan'208";a="10860259"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 04 Jan 2013 15:21:05 +0000
Received: from [10.55.87.60] (dhcp-10-55-87-60.cisco.com [10.55.87.60]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r04FL5DA031397; Fri, 4 Jan 2013 15:21:05 GMT
Message-ID: <50E6F361.6090809@cisco.com>
Date: Fri, 04 Jan 2013 16:21:05 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <20121219132126.31139.66098.idtracker@ietfa.amsl.com>	<50D1C4C6.7000501@cisco.com> <92B7E61ADAC1BB4F941F943788C08828046EED65@xmb-aln-x08.cisco.com> <92B7E61ADAC1BB4F941F943788C08828046F2270@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828046F2270@xmb-aln-x08.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, 'Tom Kristensen' <2mkristensen@gmail.com>
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4583bis-04.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 15:21:09 -0000

Thanks. Fixed for an upcoming version.

-- Tom

On 12/27/2012 12:16 AM, Charles Eckel (eckelcu) wrote:
> The changes look good to me. I do have the following editorial suggestions:
>
> 1) Section 3
> r/transport field explained below/transport field, as explained below
> r/of transport used/of the transport used
> r/ TCP is used as transport/ TCP is used as the transport
> r/ UDP is used as transport/ UDP is used as the transport
>
> 2 Section 7
> r/ use TCP or UDP as underlying transport/ use TCP or UDP as the underlying transport
>
> Cheers,
> Charles
>
>    
>> -----Original Message-----
>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
>> Behalf Of Charles Eckel (eckelcu)
>> Sent: Wednesday, December 19, 2012 2:08 PM
>> To: Tom Kristensen (tomkrist); bfcpbis@ietf.org
>> Cc: 'Tom Kristensen'
>> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4583bis-04.txt
>>
>> Everyone who submitted WGLC comments, please confirm this version
>> addresses all your comments satisfactorily.
>> Everyone else, please review the entire draft carefully and share any
>> comment or concerns you have.
>> Thanks to Tom for incorporating all the feedback and posting this update.
>>
>> Happy Holidays!
>> Charles
>>
>>      
>>> -----Original Message-----
>>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
>>> Behalf Of Tom Kristensen (tomkrist)
>>> Sent: Wednesday, December 19, 2012 5:45 AM
>>> To: bfcpbis@ietf.org
>>> Cc: 'Tom Kristensen'
>>> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4583bis-04.txt
>>>
>>> On 12/19/2012 02:21 PM, internet-drafts@ietf.org wrote:
>>>        
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>          
>>> directories.
>>>        
>>>>    This draft is a work item of the Binary Floor Control Protocol Bis
>>>>          
>> Working
>>      
>>> Group of the IETF.
>>>        
>>>> 	Title           : Session Description Protocol (SDP) Format for Binary
>>>>          
>>> Floor Control Protocol (BFCP) Streams
>>>        
>>>> 	Author(s)       : Gonzalo Camarillo
>>>>                             Tom Kristensen
>>>> 	Filename        : draft-ietf-bfcpbis-rfc4583bis-04.txt
>>>> 	Pages           : 15
>>>> 	Date            : 2012-12-19
>>>>
>>>>          
>>> Changes from -03:
>>> - Fixed according to Camarillo's input and comments on list 2012-10-24
>>> - Use UDP/TLS/BFCP not UDP/DTLS/BFCP in the example.
>>> - Added normative reference to RFC 5763, Section 5 also in
>>>     Section 8 Authentication.
>>> - Resolved issue with different way to pick (D)TLS initiator for TCP and
>>>     UDP, adding informational note.
>>>
>>>
>>> To my knowledge, in this draft version all the issues from WGLC and
>>> after are answered and fixed if appropriate.
>>>
>>>
>>> -- Tom
>>>
>>> _______________________________________________
>>> bfcpbis mailing list
>>> bfcpbis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/bfcpbis
>>>        
>> _______________________________________________
>> bfcpbis mailing list
>> bfcpbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/bfcpbis
>>      


From tomkrist@cisco.com  Fri Jan  4 07:59:42 2013
Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D989321F8837 for <bfcpbis@ietfa.amsl.com>; Fri,  4 Jan 2013 07:59:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlRNVxay-m0I for <bfcpbis@ietfa.amsl.com>; Fri,  4 Jan 2013 07:59:40 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 892D021F8830 for <bfcpbis@ietf.org>; Fri,  4 Jan 2013 07:59:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5308; q=dns/txt; s=iport; t=1357315179; x=1358524779; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=if/JKpl4zDPAuL9Aa4vip98cT0yChf3z6UieFeeV99U=; b=eI21sMAospB85P7+1PG2dt5Q3rnghEuhOoPZv6IXI+ypoi5UZ6OeeAwL 26XjwA33yZMgiNJKjy9voiK4/14oleQpRjufCkjwz+lLKpjZJ5aJaDgzz O1BBVur8qfT6fF2CqpPc7HXVqfZo3i5hP5c+eJ7Kml9fntOEHCQ3CGYIg c=;
X-IronPort-AV: E=Sophos;i="4.84,411,1355097600"; d="scan'208";a="79524007"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 04 Jan 2013 15:59:38 +0000
Received: from [10.55.87.60] (dhcp-10-55-87-60.cisco.com [10.55.87.60]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r04FxbMk004067; Fri, 4 Jan 2013 15:59:37 GMT
Message-ID: <50E6FC69.4060907@cisco.com>
Date: Fri, 04 Jan 2013 16:59:37 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <20121219132019.28896.3533.idtracker@ietfa.amsl.com>	<50D1C4C1.5020104@cisco.com> <92B7E61ADAC1BB4F941F943788C08828046EED5E@xmb-aln-x08.cisco.com> <92B7E61ADAC1BB4F941F943788C08828046F2256@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828046F2256@xmb-aln-x08.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, 'Tom Kristensen' <2mkristensen@gmail.com>
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 15:59:43 -0000

On 12/27/2012 12:03 AM, Charles Eckel (eckelcu) wrote:
> Hi Tom,
>    
Thanks Charles. Fixed all but the first issue in my local version of the 
draft.

> I had a close look at the changes, and overall they look okay to me.
> During my review, I did notice a few editorial things that are worth fixing:
> 1) many of the references to [16] do not work correctly, including the first reference in section 3.2, as well as those in section 6.2.
>    
What do you mean by references not working correctly?

> 2) For the note added in section 5.1, you have an extra 'a' and are missing a comma:
> r/BFCP is designed to a achieve small message size, as explained in Section 1 and BFCP entities/BFCP is designed to achieve small message size, as explained in Section 1, and BFCP entities
>    
Right. Fixed.

> 3) Section 6.2:
> r/ security considerations in Section 6 also applies/security considerations in Section 6 also apply
>    
Indeed. Fixed.

> 4) section 6.2.3:
> r/A Denial of Service (DoS) attacks/A Denial of Service (DoS) attack
>    
Yes. Fixed.

> 5) Section 8, I think we should rework the following paragraph:
>
>     When using BFCP over unreliable transport, it is also required to
>     choose values that let the receiver distinguish the reception of the
>     next message in a sequence of BFCP messages from a retransmission of
>     a previous message.  Therefore, BFCP entities using unreliable
>     transport SHOULD use monotonically increasing values for the
>     Transaction ID.
>
> To read as follows:
>
>     When using BFCP over an unreliable transport, it is important that the initiator
>     of a transaction choose a Transaction ID value that lets the receiver distinguish
>     the reception of the next message in a sequence of BFCP messages from a retransmission of
>     a previous message.  Therefore, BFCP entities using an unreliable  transport SHOULD use
>     monotonically increasing Transaction ID values.
>    
Much better. Great with input from native English speakers ;-)

> 6) Section 8,
> r/When using BFCP over unreliable transports/When using BFCP over an unreliable transport
> Note, a similar change was made in many places in order to address comments from Gonzalo; however, a global search and replace should be done to catch numerous other places in which it still occurs.
>    
Searched through and fixed. Also for "reliable transports".

-- Tom

> Cheers,
> Charles
>
>
>    
>> -----Original Message-----
>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
>> Behalf Of Charles Eckel (eckelcu)
>> Sent: Wednesday, December 19, 2012 2:08 PM
>> To: Tom Kristensen (tomkrist); bfcpbis@ietf.org
>> Cc: 'Tom Kristensen'
>> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
>>
>> Everyone who submitted WGLC comments, please confirm this version
>> addresses all your comments satisfactorily.
>> Everyone else, please review the entire draft carefully and share any
>> comment or concerns you have.
>> Thanks to Tom for incorporating all the feedback and posting this update.
>>
>> Happy Holidays!
>> Charles
>>
>>      
>>> -----Original Message-----
>>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
>>> Behalf Of Tom Kristensen (tomkrist)
>>> Sent: Wednesday, December 19, 2012 5:45 AM
>>> To: bfcpbis@ietf.org
>>> Cc: 'Tom Kristensen'
>>> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
>>>
>>> On 12/19/2012 02:20 PM, internet-drafts@ietf.org wrote:
>>>        
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>          
>>> directories.
>>>        
>>>>    This draft is a work item of the Binary Floor Control Protocol Bis
>>>>          
>> Working
>>      
>>> Group of the IETF.
>>>        
>>>> 	Title           : The Binary Floor Control Protocol (BFCP)
>>>> 	Author(s)       : Gonzalo Camarillo
>>>>                             Keith Drage
>>>>                             Tom Kristensen
>>>>                             Joerg Ott
>>>>                             Charles Eckel
>>>> 	Filename        : draft-ietf-bfcpbis-rfc4582bis-07.txt
>>>> 	Pages           : 89
>>>> 	Date            : 2012-12-19
>>>>
>>>>          
>>> Changes from -06:
>>> - Language clarification - mail on list from Charles Eckel 2012-10-13
>>> - Language clarification - use "BFCP connection" across the document,
>>>     change three occurences of "BFCP association".
>>> - Resolved a lot of issues, small and large - mail on list 2012-10-24
>>>     after WGLC from Gonzalo Camarillo. Also, later mail discussion
>>>     with regard to 5 of the issues.
>>> - Added reference to RFC 5763, Section 6.7 - mail on list from Christer
>>>     Holmberg 2012-11-28.
>>>
>>>
>>> To my knowledge, in this draft version all the issues from WGLC and
>>> after are answered and fixed if appropriate.
>>>
>>>
>>> -- Tom
>>> _______________________________________________
>>> bfcpbis mailing list
>>> bfcpbis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/bfcpbis
>>>        
>> _______________________________________________
>> bfcpbis mailing list
>> bfcpbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/bfcpbis
>>      


From eckelcu@cisco.com  Fri Jan  4 09:43:13 2013
Return-Path: <eckelcu@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2850521F889D for <bfcpbis@ietfa.amsl.com>; Fri,  4 Jan 2013 09:43:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level: 
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qNkKVQEPNvSh for <bfcpbis@ietfa.amsl.com>; Fri,  4 Jan 2013 09:43:12 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 91C1B21F88A5 for <bfcpbis@ietf.org>; Fri,  4 Jan 2013 09:43:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6541; q=dns/txt; s=iport; t=1357321389; x=1358530989; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=mst/2Ftp+prIu66f9zl6H50654grgwB7YmkpjYaNlGk=; b=Zj/zHqRhfpoOo2Hc1OcrUiA9y083ycqg2VEnjrxHd7Ls9zJUnq3ApxoL qaM5RtbhFmd0xHfFM4jCmBSmc8QkVJOFmNNcEVYg+RLZC9tFTBAbu2CSf VJ2Ge9n7ihCq/ZKMV4UMQWWAFk7YL0x21zMvGaf9b91QV/UrHaPrxd4pn 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAGMU51CtJV2c/2dsb2JhbABFvU0Wc4IeAQEBAwEBAQE3NAsMBAIBCBEEAQEBChQJBycLFAkIAgQOBQiIBgUBDLRkjFIbg0dhA5IeOoRPjy2CdIFxNQ
X-IronPort-AV: E=Sophos;i="4.84,411,1355097600"; d="scan'208";a="158906649"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP; 04 Jan 2013 17:42:53 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r04HgrxO003567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Jan 2013 17:42:53 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.169]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Fri, 4 Jan 2013 11:42:53 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Tom Kristensen (tomkrist)" <tomkrist@cisco.com>
Thread-Topic: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
Thread-Index: AQHN3eub8/PbTNBNFU+3OIdQdkYCzZgghrKAgAAmeRCACuSB4IAOQA+A//+xUuA=
Date: Fri, 4 Jan 2013 17:42:53 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828046F4FBE@xmb-aln-x08.cisco.com>
References: <20121219132019.28896.3533.idtracker@ietfa.amsl.com> <50D1C4C1.5020104@cisco.com> <92B7E61ADAC1BB4F941F943788C08828046EED5E@xmb-aln-x08.cisco.com> <92B7E61ADAC1BB4F941F943788C08828046F2256@xmb-aln-x08.cisco.com> <50E6FC69.4060907@cisco.com>
In-Reply-To: <50E6FC69.4060907@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.68.16.69]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, 'Tom Kristensen' <2mkristensen@gmail.com>
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 17:43:13 -0000

Please see inline.

> -----Original Message-----
> From: Tom Kristensen (tomkrist)
> Sent: Friday, January 04, 2013 8:00 AM
> To: Charles Eckel (eckelcu)
> Cc: bfcpbis@ietf.org; 'Tom Kristensen'
> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
>=20
> On 12/27/2012 12:03 AM, Charles Eckel (eckelcu) wrote:
> > Hi Tom,
> >
> Thanks Charles. Fixed all but the first issue in my local version of the
> draft.
>=20
> > I had a close look at the changes, and overall they look okay to me.
> > During my review, I did notice a few editorial things that are worth fi=
xing:
> > 1) many of the references to [16] do not work correctly, including the =
first
> reference in section 3.2, as well as those in section 6.2.
> >
> What do you mean by references not working correctly?

Sorry for being so vague.=20
In the html version of the draft (http://tools.ietf.org/html/draft-ietf-bfc=
pbis-rfc4582bis-07), clicking on any of the links for "[16]" take me to sec=
tion 6.2 instead of to the appropriate reference in the references section.=
 In fact, it takes me to another occurrence of a reference to [16] that for=
 some reason is not displaying as a link.
However, if I download the xml version of the draft and run xml2rfc on it m=
yself, the resulting html version is fine. Perhaps it is a bug in the datat=
racker html file generator (e.g. it cannot handle a reference appearing at =
the start of a paragraph), and not an issue with your draft.

Cheers,
Charles

> > 2) For the note added in section 5.1, you have an extra 'a' and are mis=
sing a
> comma:
> > r/BFCP is designed to a achieve small message size, as explained in
> Section 1 and BFCP entities/BFCP is designed to achieve small message siz=
e,
> as explained in Section 1, and BFCP entities
> >
> Right. Fixed.
>=20
> > 3) Section 6.2:
> > r/ security considerations in Section 6 also applies/security considera=
tions
> in Section 6 also apply
> >
> Indeed. Fixed.
>=20
> > 4) section 6.2.3:
> > r/A Denial of Service (DoS) attacks/A Denial of Service (DoS) attack
> >
> Yes. Fixed.
>=20
> > 5) Section 8, I think we should rework the following paragraph:
> >
> >     When using BFCP over unreliable transport, it is also required to
> >     choose values that let the receiver distinguish the reception of th=
e
> >     next message in a sequence of BFCP messages from a retransmission o=
f
> >     a previous message.  Therefore, BFCP entities using unreliable
> >     transport SHOULD use monotonically increasing values for the
> >     Transaction ID.
> >
> > To read as follows:
> >
> >     When using BFCP over an unreliable transport, it is important that =
the
> initiator
> >     of a transaction choose a Transaction ID value that lets the receiv=
er
> distinguish
> >     the reception of the next message in a sequence of BFCP messages fr=
om
> a retransmission of
> >     a previous message.  Therefore, BFCP entities using an unreliable
> transport SHOULD use
> >     monotonically increasing Transaction ID values.
> >
> Much better. Great with input from native English speakers ;-)
>=20
> > 6) Section 8,
> > r/When using BFCP over unreliable transports/When using BFCP over an
> unreliable transport
> > Note, a similar change was made in many places in order to address
> comments from Gonzalo; however, a global search and replace should be
> done to catch numerous other places in which it still occurs.
> >
> Searched through and fixed. Also for "reliable transports".
>=20
> -- Tom
>=20
> > Cheers,
> > Charles
> >
> >
> >
> >> -----Original Message-----
> >> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
> >> Behalf Of Charles Eckel (eckelcu)
> >> Sent: Wednesday, December 19, 2012 2:08 PM
> >> To: Tom Kristensen (tomkrist); bfcpbis@ietf.org
> >> Cc: 'Tom Kristensen'
> >> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.tx=
t
> >>
> >> Everyone who submitted WGLC comments, please confirm this version
> >> addresses all your comments satisfactorily.
> >> Everyone else, please review the entire draft carefully and share any
> >> comment or concerns you have.
> >> Thanks to Tom for incorporating all the feedback and posting this upda=
te.
> >>
> >> Happy Holidays!
> >> Charles
> >>
> >>
> >>> -----Original Message-----
> >>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
> >>> Behalf Of Tom Kristensen (tomkrist)
> >>> Sent: Wednesday, December 19, 2012 5:45 AM
> >>> To: bfcpbis@ietf.org
> >>> Cc: 'Tom Kristensen'
> >>> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.t=
xt
> >>>
> >>> On 12/19/2012 02:20 PM, internet-drafts@ietf.org wrote:
> >>>
> >>>> A New Internet-Draft is available from the on-line Internet-Drafts
> >>>>
> >>> directories.
> >>>
> >>>>    This draft is a work item of the Binary Floor Control Protocol Bi=
s
> >>>>
> >> Working
> >>
> >>> Group of the IETF.
> >>>
> >>>> 	Title           : The Binary Floor Control Protocol (BFCP)
> >>>> 	Author(s)       : Gonzalo Camarillo
> >>>>                             Keith Drage
> >>>>                             Tom Kristensen
> >>>>                             Joerg Ott
> >>>>                             Charles Eckel
> >>>> 	Filename        : draft-ietf-bfcpbis-rfc4582bis-07.txt
> >>>> 	Pages           : 89
> >>>> 	Date            : 2012-12-19
> >>>>
> >>>>
> >>> Changes from -06:
> >>> - Language clarification - mail on list from Charles Eckel 2012-10-13
> >>> - Language clarification - use "BFCP connection" across the document,
> >>>     change three occurences of "BFCP association".
> >>> - Resolved a lot of issues, small and large - mail on list 2012-10-24
> >>>     after WGLC from Gonzalo Camarillo. Also, later mail discussion
> >>>     with regard to 5 of the issues.
> >>> - Added reference to RFC 5763, Section 6.7 - mail on list from Christ=
er
> >>>     Holmberg 2012-11-28.
> >>>
> >>>
> >>> To my knowledge, in this draft version all the issues from WGLC and
> >>> after are answered and fixed if appropriate.
> >>>
> >>>
> >>> -- Tom
> >>> _______________________________________________
> >>> bfcpbis mailing list
> >>> bfcpbis@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/bfcpbis
> >>>
> >> _______________________________________________
> >> bfcpbis mailing list
> >> bfcpbis@ietf.org
> >> https://www.ietf.org/mailman/listinfo/bfcpbis
> >>


From tomkrist@cisco.com  Mon Jan  7 00:18:45 2013
Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1FFB21F8526 for <bfcpbis@ietfa.amsl.com>; Mon,  7 Jan 2013 00:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f16Em3YtVas0 for <bfcpbis@ietfa.amsl.com>; Mon,  7 Jan 2013 00:18:45 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id CC9FB21F8506 for <bfcpbis@ietf.org>; Mon,  7 Jan 2013 00:18:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=955; q=dns/txt; s=iport; t=1357546725; x=1358756325; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=0TcY0B20Sr1ojy2FZQ2nSjUfu/ranTpm2KeJz5brBgQ=; b=Qs94pC5pQmgpUzH5k5ip8mPvp7fWAIvGzGLd9oY401Uh8BIqNVjzVfzI w/QlPQmbgw3uWkQsQudVCPXIB695iy4LzM4gIo11S3WPBfYYDc9q5dmfs Uu8m6C3ddtaaDAWXDNussihGRmCHZaE0fd3rloItQYQtvvMHQvgtGvAWk g=;
X-IronPort-AV: E=Sophos;i="4.84,422,1355097600"; d="scan'208";a="149095707"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 07 Jan 2013 08:18:42 +0000
Received: from [10.47.38.250] ([10.47.38.250]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r078IgFh022290; Mon, 7 Jan 2013 08:18:42 GMT
Message-ID: <50EA84E1.8070809@cisco.com>
Date: Mon, 07 Jan 2013 09:18:41 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <20121219132019.28896.3533.idtracker@ietfa.amsl.com>	<50D1C4C1.5020104@cisco.com> <92B7E61ADAC1BB4F941F943788C08828046EED5E@xmb-aln-x08.cisco.com> <92B7E61ADAC1BB4F941F943788C08828046F2256@xmb-aln-x08.cisco.com> <50E6FC69.4060907@cisco.com> <92B7E61ADAC1BB4F941F943788C08828046F4FBE@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828046F4FBE@xmb-aln-x08.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, 'Tom Kristensen' <2mkristensen@gmail.com>
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 08:18:45 -0000

On 01/04/2013 06:42 PM, Charles Eckel (eckelcu) wrote:

[...]
>> What do you mean by references not working correctly?
>>      
> Sorry for being so vague.
> In the html version of the draft (http://tools.ietf.org/html/draft-ietf-bfcpbis-rfc4582bis-07), clicking on any of the links for "[16]" take me to section 6.2 instead of to the appropriate reference in the references section. In fact, it takes me to another occurrence of a reference to [16] that for some reason is not displaying as a link.
> However, if I download the xml version of the draft and run xml2rfc on it myself, the resulting html version is fine. Perhaps it is a bug in the datatracker html file generator (e.g. it cannot handle a reference appearing at the start of a paragraph), and not an issue with your draft.
Adding "RFC 5018" in front of the reference, so that the reference 
doesn't appear at the start of this paragraph. Will hopefully fix it!

-- Tom

[...]



From internet-drafts@ietf.org  Wed Jan  9 06:47:06 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447B721F84DC; Wed,  9 Jan 2013 06:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZP-WX+hDPjI; Wed,  9 Jan 2013 06:47:05 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C482421F8488; Wed,  9 Jan 2013 06:47:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130109144705.12172.41929.idtracker@ietfa.amsl.com>
Date: Wed, 09 Jan 2013 06:47:05 -0800
Cc: bfcpbis@ietf.org
Subject: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-08.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 14:47:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Binary Floor Control Protocol Bis  Workin=
g Group of the IETF.

	Title           : The Binary Floor Control Protocol (BFCP)
	Author(s)       : Gonzalo Camarillo
                          Keith Drage
                          Tom Kristensen
                          Joerg Ott
                          Charles Eckel
	Filename        : draft-ietf-bfcpbis-rfc4582bis-08.txt
	Pages           : 89
	Date            : 2013-01-09

Abstract:
   Floor control is a means to manage joint or exclusive access to
   shared resources in a (multiparty) conferencing environment.
   Thereby, floor control complements other functions -- such as
   conference and media session setup, conference policy manipulation,
   and media control -- that are realized by other protocols.

   This document specifies the Binary Floor Control Protocol (BFCP).
   BFCP is used between floor participants and floor control servers,
   and between floor chairs (i.e., moderators) and floor control
   servers.

   This document obsoletes RFC 4582.  Changes from RFC 4582 are
   summarized in Section 16.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfcpbis-rfc4582bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-bfcpbis-rfc4582bis-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bfcpbis-rfc4582bis-08


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From internet-drafts@ietf.org  Wed Jan  9 06:47:25 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1E921F8607; Wed,  9 Jan 2013 06:47:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMvCKZPghqEk; Wed,  9 Jan 2013 06:47:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4794C21F85AF; Wed,  9 Jan 2013 06:47:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130109144725.17196.1155.idtracker@ietfa.amsl.com>
Date: Wed, 09 Jan 2013 06:47:25 -0800
Cc: bfcpbis@ietf.org
Subject: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4583bis-05.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 14:47:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Binary Floor Control Protocol Bis  Workin=
g Group of the IETF.

	Title           : Session Description Protocol (SDP) Format for Binary Flo=
or Control Protocol (BFCP) Streams
	Author(s)       : Gonzalo Camarillo
                          Tom Kristensen
	Filename        : draft-ietf-bfcpbis-rfc4583bis-05.txt
	Pages           : 15
	Date            : 2013-01-09

Abstract:
   This document specifies how to describe Binary Floor Control Protocol
   (BFCP) streams in Session Description Protocol (SDP) descriptions.
   User agents using the offer/answer model to establish BFCP streams
   use this format in their offers and answers.

   This document obsoletes RFC 4583.  Changes from RFC 4583 are
   summarized in Section 12.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfcpbis-rfc4583bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-bfcpbis-rfc4583bis-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bfcpbis-rfc4583bis-05


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From tomkrist@cisco.com  Wed Jan  9 06:51:44 2013
Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9131421F8596 for <bfcpbis@ietfa.amsl.com>; Wed,  9 Jan 2013 06:51:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTXmyXskytWF for <bfcpbis@ietfa.amsl.com>; Wed,  9 Jan 2013 06:51:44 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id B28F621F8488 for <bfcpbis@ietf.org>; Wed,  9 Jan 2013 06:51:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1534; q=dns/txt; s=iport; t=1357743103; x=1358952703; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=XCtplPiYZbohXJ7ThwWLNdku6qzNPJKgWiEAeoJ29Rg=; b=E5pXShqtU/kSRrJU6T8hnhfCAIx5csXfUcnrtM3hQxsHv1GOxs1Rsvm6 /2k9iOlXw/VhVUrmgm105++vswNxRLJwhc1AeZAzmK+RbbdUqUxZtIGo1 gpmaqCs+5qQOzoQGeAvPVLNW2auT++Ufu4r8P1mDEKhNfW5qbbAxL09Na A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlsIAEaD7VCQ/khL/2dsb2JhbABEg0e6CxZzgh4BAQEEODAQEQsYCRYPCQMCAQIBRRMGAgEBiBO2IIxof4MpA5YMhWuKXoJ1gXA
X-IronPort-AV: E=Sophos;i="4.84,438,1355097600"; d="scan'208";a="10967751"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 09 Jan 2013 14:51:42 +0000
Received: from [10.61.89.109] (ams3-vpn-dhcp6510.cisco.com [10.61.89.109]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r09EpgCu013325 for <bfcpbis@ietf.org>; Wed, 9 Jan 2013 14:51:42 GMT
Message-ID: <50ED83FE.5050005@cisco.com>
Date: Wed, 09 Jan 2013 15:51:42 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: bfcpbis@ietf.org
References: <20130109144705.12172.41929.idtracker@ietfa.amsl.com>
In-Reply-To: <20130109144705.12172.41929.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-08.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 14:51:44 -0000

On 01/09/2013 03:47 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Binary Floor Control Protocol Bis  Working Group of the IETF.
>
> 	Title           : The Binary Floor Control Protocol (BFCP)
> 	Author(s)       : Gonzalo Camarillo
>                            Keith Drage
>                            Tom Kristensen
>                            Joerg Ott
>                            Charles Eckel
> 	Filename        : draft-ietf-bfcpbis-rfc4582bis-08.txt
> 	Pages           : 89
> 	Date            : 2013-01-09
>
> Abstract:
>     Floor control is a means to manage joint or exclusive access to
>     shared resources in a (multiparty) conferencing environment.
>     Thereby, floor control complements other functions -- such as
>     conference and media session setup, conference policy manipulation,
>     and media control -- that are realized by other protocols.
>
>     This document specifies the Binary Floor Control Protocol (BFCP).
>     BFCP is used between floor participants and floor control servers,
>     and between floor chairs (i.e., moderators) and floor control
>     servers.
>
>     This document obsoletes RFC 4582.  Changes from RFC 4582 are
>     summarized in Section 16.
>    

Resolved Charles Eckel's editorial issues, sent to list 2012-12-27 and 
elaborated/discussed in the mail thread.

The draft is hopefully ready for a next step in the process,
-- Tom


From tomkrist@cisco.com  Wed Jan  9 06:52:48 2013
Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57EA221F85CB for <bfcpbis@ietfa.amsl.com>; Wed,  9 Jan 2013 06:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id otBkcmM+PjnN for <bfcpbis@ietfa.amsl.com>; Wed,  9 Jan 2013 06:52:46 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id F19D321F85C2 for <bfcpbis@ietf.org>; Wed,  9 Jan 2013 06:52:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1149; q=dns/txt; s=iport; t=1357743165; x=1358952765; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=aVvJH2+v7c4+aDvEifWW7rvuleWk0e2+2nfF9Wyayek=; b=hHMySyQA/K+oWQ/IZlZIHP07AGsarbmzev9hlwfDDaCUHkFzmcAvEDGZ ovarWBWHb4isPl1PPtOF6cMRlgavBZrOk+QW2rNfGWrp8gIyaIW3jwbiO 6lyoy6Qa33WUkQdWk4FSeE7VVnliEtNt4MkzqnBPiW6IFLPKzZvkLZXc4 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlkIALmD7VCQ/khL/2dsb2JhbABEg0e6CxZzgh4BAQEEOFELGAklDwJGEwYCAQGIE7YjjGh/gykDlgyFa4pegnWBcA
X-IronPort-AV: E=Sophos;i="4.84,438,1355097600"; d="scan'208";a="10979987"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 09 Jan 2013 14:52:44 +0000
Received: from [10.61.89.109] (ams3-vpn-dhcp6510.cisco.com [10.61.89.109]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r09EqhWl013506 for <bfcpbis@ietf.org>; Wed, 9 Jan 2013 14:52:44 GMT
Message-ID: <50ED843B.90003@cisco.com>
Date: Wed, 09 Jan 2013 15:52:43 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: bfcpbis@ietf.org
References: <20130109144725.17196.1155.idtracker@ietfa.amsl.com>
In-Reply-To: <20130109144725.17196.1155.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4583bis-05.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 14:52:49 -0000

On 01/09/2013 03:47 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Binary Floor Control Protocol Bis  Working Group of the IETF.
>
> 	Title           : Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
> 	Author(s)       : Gonzalo Camarillo
>                            Tom Kristensen
> 	Filename        : draft-ietf-bfcpbis-rfc4583bis-05.txt
> 	Pages           : 15
> 	Date            : 2013-01-09
>
> Abstract:
>     This document specifies how to describe Binary Floor Control Protocol
>     (BFCP) streams in Session Description Protocol (SDP) descriptions.
>     User agents using the offer/answer model to establish BFCP streams
>     use this format in their offers and answers.
>
>     This document obsoletes RFC 4583.  Changes from RFC 4583 are
>     summarized in Section 12.
>    
Resolved Charles Eckel's editorial issues, sent to list 2012-12-27 and 
elaborated/discussed in the mail thread.

The draft is hopefully ready for a next step in the process,
-- Tom



From eckelcu@cisco.com  Fri Jan 11 10:25:59 2013
Return-Path: <eckelcu@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0429021F895F for <bfcpbis@ietfa.amsl.com>; Fri, 11 Jan 2013 10:25:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.497
X-Spam-Level: 
X-Spam-Status: No, score=-8.497 tagged_above=-999 required=5 tests=[AWL=2.103,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMl8DvkSpu5G for <bfcpbis@ietfa.amsl.com>; Fri, 11 Jan 2013 10:25:57 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 46CFB21F8919 for <bfcpbis@ietf.org>; Fri, 11 Jan 2013 10:25:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=320; q=dns/txt; s=iport; t=1357928753; x=1359138353; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=aHBf431/2LRBUA2/KXSpCSS0WpAOU2hVnMj4A75Duus=; b=ZRM3sfNktvxZy5I8g3vuFDKBbwPRM0MO2m85yueSreuzt5AujL40tHeT J3U1sbm2+8ddWPIbCENYa72uI6Wn+DXRyRjeVKU/E4glka+5Pq3yoDEHk En7GZWM2RsAhIqTuk3OfDPzi6kQbgzdYXRbYHlI3h4Y05xXvwnOaAOPVf U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EABNY8FCtJV2Y/2dsb2JhbABEvX4Wc4IgAQQ6UQEqFEImAQQbiBABlxefG4x+g0dhA6ZUgnWBbzU
X-IronPort-AV: E=Sophos;i="4.84,453,1355097600"; d="scan'208";a="161520445"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 11 Jan 2013 18:25:49 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r0BIPnSI003408 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <bfcpbis@ietf.org>; Fri, 11 Jan 2013 18:25:49 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.224]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Fri, 11 Jan 2013 12:25:49 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: not requesting a meeting slot at IETF 86
Thread-Index: Ac3wKRLr+AOtPdnPQDadvLJhgS3JYw==
Date: Fri, 11 Jan 2013 18:25:48 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C0882804728FD5@xmb-aln-x08.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.68.16.69]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [bfcpbis] not requesting a meeting slot at IETF 86
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 18:25:59 -0000

This e-mail is to inform the working group that we are not planning to requ=
est a meeting slot for BFCPBIS at IETF 86.
If anyone thinks there is a good reason to do otherwise, please let the cha=
irs know asap as the deadline to request a session is Monday, Jan 14.

Cheers,
Charles and Keith, BFCPBIS co-chairs

From keith.drage@alcatel-lucent.com  Sun Jan 13 14:47:38 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3BCA21F8545 for <bfcpbis@ietfa.amsl.com>; Sun, 13 Jan 2013 14:47:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.524
X-Spam-Level: 
X-Spam-Status: No, score=-108.524 tagged_above=-999 required=5 tests=[AWL=1.725, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id id5-h4onuJDM for <bfcpbis@ietfa.amsl.com>; Sun, 13 Jan 2013 14:47:37 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id E4B4921F852C for <bfcpbis@ietf.org>; Sun, 13 Jan 2013 14:47:36 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r0DMlUd2015524 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 13 Jan 2013 23:47:30 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Sun, 13 Jan 2013 23:47:30 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Date: Sun, 13 Jan 2013 23:47:30 +0100
Thread-Topic: not requesting a meeting slot at IETF 86
Thread-Index: Ac3wKRLr+AOtPdnPQDadvLJhgS3JYwBtMzSw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20D745EF092@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <92B7E61ADAC1BB4F941F943788C0882804728FD5@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C0882804728FD5@xmb-aln-x08.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Subject: Re: [bfcpbis] not requesting a meeting slot at IETF 86
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 22:47:38 -0000

Note that we are starting the writeup for the publication request for both =
drafts. This could may well result in a number of editorial and other minor=
 changes.=20

If you spot anything that is still worthy of comment, now would be a good t=
ime to make that comment.

Keith

> -----Original Message-----
> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On Behal=
f
> Of Charles Eckel (eckelcu)
> Sent: 11 January 2013 18:26
> To: bfcpbis@ietf.org
> Subject: [bfcpbis] not requesting a meeting slot at IETF 86
>=20
> This e-mail is to inform the working group that we are not planning to
> request a meeting slot for BFCPBIS at IETF 86.
> If anyone thinks there is a good reason to do otherwise, please let the
> chairs know asap as the deadline to request a session is Monday, Jan 14.
>=20
> Cheers,
> Charles and Keith, BFCPBIS co-chairs
> _______________________________________________
> bfcpbis mailing list
> bfcpbis@ietf.org
> https://www.ietf.org/mailman/listinfo/bfcpbis

From aeh@db.org  Sun Jan 20 10:08:39 2013
Return-Path: <aeh@db.org>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 557BB21F8555 for <bfcpbis@ietfa.amsl.com>; Sun, 20 Jan 2013 10:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbQRDbOVJXPb for <bfcpbis@ietfa.amsl.com>; Sun, 20 Jan 2013 10:08:38 -0800 (PST)
Received: from mailstore06.sysedata.no (b.mail.tornado.no [195.159.29.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB7E21F857E for <bfcpbis@ietf.org>; Sun, 20 Jan 2013 10:08:37 -0800 (PST)
Received: from [84.209.197.2] (helo=alfred-heggestads-macbook-pro.local) by mailstore06.sysedata.no with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from <aeh@db.org>) id 1TwzJr-00039C-IA for bfcpbis@ietf.org; Sun, 20 Jan 2013 19:08:35 +0100
Message-ID: <50FC32A3.4020908@db.org>
Date: Sun, 20 Jan 2013 19:08:35 +0100
From: "Alfred E. Heggestad" <aeh@db.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [bfcpbis] RFC4583bis examples
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jan 2013 18:08:39 -0000

hi,


I have some comments to the Example section in:

   http://tools.ietf.org/id/draft-ietf-bfcpbis-rfc4583bis-05.txt



    m=application 50000 UDP/TLS/BFCP *
    a=setup:actpass
    a=fingerprint:SHA-1 \
         4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
    a=floorctrl:c-only, s-only
    a=confid:4321
    a=userid:1234
    a=floorid:1 mstrm:10
    a=floorid:2 mstrm:11
    m=audio 50002 RTP/AVP 0
    a=label:10
    m=video 50004 RTP/AVP 31
    a=label:11

    The following is the answer returned by the server.

    m=application 9 UDP/TLS/BFCP *
    a=setup:active
    a=fingerprint:SHA-1 \
         3D:B4:7B:E3:CC:FC:0D:1B:5D:31:33:9E:48:9B:67:FE:68:40:E8:21
    a=floorctrl:s-only
    a=confid:4321
    a=userid:1234
    a=floorid:1 mstrm:10
    a=floorid:2 mstrm:11
    m=audio 55000 RTP/AVP 0
    m=video 55002 RTP/AVP 31



1. can the "floorctrl" attribute have several values, and are they
    separated by COMMA or SPACE ?


2. is it normal to use port 9 for UDP sockets ...? perhaps it is better
    to use a port number from the example range (1024-65535) ?






/alfred

From tomkrist@cisco.com  Mon Jan 21 01:58:05 2013
Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57B1A21F86CE for <bfcpbis@ietfa.amsl.com>; Mon, 21 Jan 2013 01:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bugDbt0rghD for <bfcpbis@ietfa.amsl.com>; Mon, 21 Jan 2013 01:58:04 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 714BA21F86C9 for <bfcpbis@ietf.org>; Mon, 21 Jan 2013 01:58:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=686; q=dns/txt; s=iport; t=1358762284; x=1359971884; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Zd4XZ8wm/g+Q6iGEYdwvX38nor9pfhcsD4to1iTnDk8=; b=Xi62I9qbBXoIigzS3VW/zbjlaZxcz/q1khb1KzaMykQKFl+PzEcK7g2h s3FuqtP7XP8dPdnTp4HO1PtECBeQKjS/gUV8WjBw7KUZXmt35D/ncDuMD 7KRROc2Etcf9Fr5b8lnopdyqqTm0QI9kgq6kjzHZlOu0lWzgrFOa+AFXh 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAPMO/VCQ/khR/2dsb2JhbABEgzi3HINZFnOCHgEBAQMBOEABBQsLGAkWDwkDAgECAUUGDQEHAQGIDwa7EJE5A5YMhWuKXoJ2
X-IronPort-AV: E=Sophos;i="4.84,505,1355097600"; d="scan'208";a="149590458"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 21 Jan 2013 09:58:03 +0000
Received: from [10.47.38.211] ([10.47.38.211]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r0L9w2eA026546; Mon, 21 Jan 2013 09:58:03 GMT
Message-ID: <50FD112A.8010004@cisco.com>
Date: Mon, 21 Jan 2013 10:58:02 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: "Alfred E. Heggestad" <aeh@db.org>
References: <50FC32A3.4020908@db.org>
In-Reply-To: <50FC32A3.4020908@db.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Subject: Re: [bfcpbis] RFC4583bis examples
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2013 09:58:05 -0000

On 01/20/2013 07:08 PM, Alfred E. Heggestad wrote:
> hi,

[...]

> 1. can the "floorctrl" attribute have several values, and are they
>    separated by COMMA or SPACE ?
Yes, several values allowed separated by SP:

---

    floor-control-attribute  = "a=floorctrl:" role *(SP role)
    role                     = "c-only" / "s-only" / "c-s"

---

> 2. is it normal to use port 9 for UDP sockets ...? perhaps it is better
>    to use a port number from the example range (1024-65535) ?

Nope. Discard port only applicable for a TCP connection. For UDP we have 
to use the port the BFCP messages shall be sent to.

Thanks, Alfred! This needs to be fixed.

-- Tom

From tomkrist@cisco.com  Mon Jan 21 02:12:48 2013
Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86D7B21F85B4 for <bfcpbis@ietfa.amsl.com>; Mon, 21 Jan 2013 02:12:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DG8j+bxWWojl for <bfcpbis@ietfa.amsl.com>; Mon, 21 Jan 2013 02:12:47 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id EC42C21F84E0 for <bfcpbis@ietf.org>; Mon, 21 Jan 2013 02:12:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1862; q=dns/txt; s=iport; t=1358763167; x=1359972767; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=BBrhzUzaTZFiv9mYei63zjF0Y2D3B6MbySLNVLHmcmk=; b=bV85VHPLpl4Gev8u/wftr3mmABOebxrJmopItdMxlHu+Jxdy4za7jLaj F//hd2bzfpNgqv0LR7xJXG0P0TLP6VFDGfPJu734oiy8v2RSSK2ippO5l eheXUAYFXIRQv8IBY6CkAdARApQOseKVDtIhU0cnsr8utBSHSBshcVs/1 w=;
X-Files: aeh-example-fix-2013-01-21.diff : 1287
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFANAT/VCQ/khM/2dsb2JhbABCAoM4iGmyDBZzgh8BAQR4ARALIQ0JDwkDAgECAUUGDQEHAQGIFbsKjgwLgyIDjwiHBIVril6CdoFu
X-IronPort-AV: E=Sophos;i="4.84,505,1355097600";  d="diff'?scan'208";a="11218543"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 21 Jan 2013 10:12:44 +0000
Received: from [10.47.38.211] ([10.47.38.211]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r0LACi5u023894; Mon, 21 Jan 2013 10:12:44 GMT
Message-ID: <50FD149C.4050008@cisco.com>
Date: Mon, 21 Jan 2013 11:12:44 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: "Alfred E. Heggestad" <aeh@db.org>
References: <50FC32A3.4020908@db.org> <50FD112A.8010004@cisco.com>
In-Reply-To: <50FD112A.8010004@cisco.com>
Content-Type: multipart/mixed; boundary="------------030702080709090201010902"
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Subject: Re: [bfcpbis] RFC4583bis examples
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2013 10:12:48 -0000

This is a multi-part message in MIME format.
--------------030702080709090201010902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Fixed for upcoming version.

XML diff enclosed, if any interest ;-)

-- Tom

--------------030702080709090201010902
Content-Type: text/x-patch;
 name="aeh-example-fix-2013-01-21.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="aeh-example-fix-2013-01-21.diff"

Index: draft-ietf-bfcpbis-rfc4583bis.xml
===================================================================
--- draft-ietf-bfcpbis-rfc4583bis.xml	(revision 1677)
+++ draft-ietf-bfcpbis-rfc4583bis.xml	(working copy)
@@ -4,7 +4,7 @@
 
 <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
 
-<rfc category="std" ipr="trust200902" docName="draft-ietf-bfcpbis-rfc4583bis-05" obsoletes="4583">
+<rfc category="std" ipr="trust200902" docName="draft-ietf-bfcpbis-rfc4583bis-06" obsoletes="4583">
 
 <?rfc strict="yes"?>
 <?rfc toc="yes"?>
@@ -232,7 +232,7 @@
 a=setup:actpass
 a=fingerprint:SHA-1 \
      4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
-a=floorctrl:c-only, s-only
+a=floorctrl:c-only s-only
 a=confid:4321
 a=userid:1234	
 a=floorid:1 mstrm:10
@@ -246,7 +246,7 @@
     <t>The following is the answer returned by the server.</t>
     <figure>
       <artwork>
-m=application 9 UDP/TLS/BFCP *
+m=application 55000 UDP/TLS/BFCP *
 a=setup:active
 a=fingerprint:SHA-1 \
      3D:B4:7B:E3:CC:FC:0D:1B:5D:31:33:9E:48:9B:67:FE:68:40:E8:21
@@ -255,8 +255,8 @@
 a=userid:1234	
 a=floorid:1 mstrm:10
 a=floorid:2 mstrm:11
-m=audio 55000 RTP/AVP 0
-m=video 55002 RTP/AVP 31
+m=audio 55002 RTP/AVP 0
+m=video 55004 RTP/AVP 31
       </artwork>
     </figure>
   </section>

--------------030702080709090201010902--

From keith.drage@alcatel-lucent.com  Mon Jan 21 09:57:58 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E8A21F8620 for <bfcpbis@ietfa.amsl.com>; Mon, 21 Jan 2013 09:57:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.249
X-Spam-Level: 
X-Spam-Status: No, score=-108.249 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxbB8HlkZRMe for <bfcpbis@ietfa.amsl.com>; Mon, 21 Jan 2013 09:57:58 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [62.23.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id B912821F85B3 for <bfcpbis@ietf.org>; Mon, 21 Jan 2013 09:57:57 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r0LHvp55021420 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <bfcpbis@ietf.org>; Mon, 21 Jan 2013 18:57:55 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 21 Jan 2013 18:57:49 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Date: Mon, 21 Jan 2013 18:57:45 +0100
Thread-Topic: Implementation status of the drafts
Thread-Index: Ac34ANE8S0iCTAbiSmmgZzXRaygF5A==
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20D7468B0DC@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Subject: [bfcpbis] Implementation status of the drafts
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2013 17:57:58 -0000

(As WG cochairs)

For the publication request, we are asked to give an indication of the impl=
ementation status of the drafts, so that the IESG can identify whether the =
protocol as described actually works in practice.

We have been told that there have been some working implementations in the =
past, but it would be useful to get an update.

Could I ask people therefore to reply to the list, or if you prefer, direct=
ly to the WG chairs, identifying what if anything has been implemented from=
 the two bfcpbis drafts (and at what version).

As this is a replacement of the original BFCP documents RFC 4582 and RFC 45=
83, it would also be useful to have indications of the implementation of th=
ose documents.

Regards

Keith


