
From duddy@avaya.com  Tue Jun  1 08:32:09 2010
Return-Path: <duddy@avaya.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 344283A6A46 for <xcon@core3.amsl.com>; Tue,  1 Jun 2010 08:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[AWL=-0.001,  BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-g5M68EVpaw for <xcon@core3.amsl.com>; Tue,  1 Jun 2010 08:32:05 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 5E0673A6A57 for <xcon@ietf.org>; Tue,  1 Jun 2010 08:31:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,340,1272859200"; d="scan'208,217";a="18556492"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 01 Jun 2010 11:31:05 -0400
X-IronPort-AV: E=Sophos;i="4.53,340,1272859200";  d="scan'208,217";a="479901736"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.153]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Jun 2010 11:31:04 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB019F.70C4C073"
Date: Tue, 1 Jun 2010 16:31:01 +0100
Message-ID: <4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON]  I-D Action:draft-ietf-xcon-ccmp-07.txt
Thread-Index: Acrla81R5loMyOpgQ+mWBS732veu/gAg/tigBrfkryAAM/dHwA==
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com> <20100426201045.8x0hgw8rkkw488cs@webmail.unina.it> 
From: "Duddy, Sean (Sean)" <duddy@avaya.com>
To: <xcon@ietf.org>
Subject: [XCON]   I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jun 2010 15:32:09 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB019F.70C4C073
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Simon,
        Some of the changes I *think* we agreed on didn't make it in to
this draft. I have highlighed these in red below :-

  <xs:complexType name=3D"ccmp-blueprints-request-message-type">
       <xs:complexContent>
           <xs:extension base=3D"tns:ccmp-request-message-type">
               <xs:sequence>
                   <xs:element ref=3D"blueprintsRequest" minOccurs=3D"0" =
/>
               </xs:sequence>
           </xs:extension>
       </xs:complexContent>
   </xs:complexType>

 <xs:complexType name=3D"ccmp-confs-request-message-type">
       <xs:complexContent>
           <xs:extension base=3D"tns:ccmp-request-message-type">
               <xs:sequence>

                   <xs:element ref=3D"confsRequest" minOccurs=3D"0"/>
               </xs:sequence>
           </xs:extension>
       </xs:complexContent>
   </xs:complexType>

 <xs:complexType name=3D"ccmp-sidebarsByVal-request-message-type">
       <xs:complexContent>
           <xs:extension base=3D"tns:ccmp-request-message-type">
               <xs:sequence>
                   <xs:element ref=3D"sidebarsByValRequest"
minOccurs=3D"0"/>
                </xs:sequence>
           </xs:extension>
       </xs:complexContent>
   </xs:complexType>

 <xs:complexType name=3D"ccmp-sidebarsByRef-request-message-type">
        <xs:complexContent>
            <xs:extension base=3D"tns:ccmp-request-message-type">
                <xs:sequence>
                    <xs:element ref=3D"sidebarsByRefRequest" =
minOccurs=3D"0"
/>
                </xs:sequence>
            </xs:extension>
        </xs:complexContent>
    </xs:complexType>


------_=_NextPart_001_01CB019F.70C4C073
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3676" name=3DGENERATOR></HEAD>
<BODY><!-- Converted from text/plain format -->
<P>Hi Simon,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Some of the =
changes I=20
*think* we agreed on didn&#8217;t make it in to this draft. I have =
highlighed these in=20
red below :-<BR><BR>&nbsp; &lt;xs:complexType=20
name=3D"ccmp-blueprints-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
&lt;xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
&lt;xs:extension=20
base=3D"tns:ccmp-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:element ref=3D"blueprintsRequest" <FONT =
color=3D#ff0000>minOccurs=3D"0"</FONT>=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
&lt;/xs:extension&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:complexContent&gt;<BR>&nbsp;&nbsp; &lt;/xs:complexType&gt;</P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>&nbsp;&lt;xs:complexType=20
name=3D"ccmp-confs-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
&lt;xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
&lt;xs:extension=20
base=3D"tns:ccmp-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:sequence&gt;</FONT></P>
<P><FONT face=3DArial color=3D#0000ff=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:element ref=3D"confsRequest" <FONT=20
color=3D#ff0000>minOccurs=3D"0"</FONT>/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
&lt;/xs:extension&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:complexContent&gt;<BR>&nbsp;&nbsp; =
&lt;/xs:complexType&gt;</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>&nbsp;&lt;xs:complexType=20
name=3D"ccmp-sidebarsByVal-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
&lt;xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
&lt;xs:extension=20
base=3D"tns:ccmp-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:element ref=3D"sidebarsByValRequest" <FONT=20
color=3D#ff0000>minOccurs=3D"0"</FONT>/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
&lt;/xs:extension&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:complexContent&gt;<BR>&nbsp;&nbsp; =
&lt;/xs:complexType&gt;</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>&nbsp;&lt;xs:complexType=20
name=3D"ccmp-sidebarsByRef-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:extension=20
base=3D"tns:ccmp-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:element ref=3D"sidebarsByRefRequest" <FONT=20
color=3D#ff0000>minOccurs=3D"0"</FONT>=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
&lt;/xs:extension&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;=20
&lt;/xs:complexType&gt;</FONT></P></BODY></HTML>

------_=_NextPart_001_01CB019F.70C4C073--

From duddy@avaya.com  Tue Jun  1 08:38:29 2010
Return-Path: <duddy@avaya.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D094C3A6A4A for <xcon@core3.amsl.com>; Tue,  1 Jun 2010 08:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.069
X-Spam-Level: 
X-Spam-Status: No, score=-0.069 tagged_above=-999 required=5 tests=[AWL=-0.671, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_210=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pbj+tZL-lB+d for <xcon@core3.amsl.com>; Tue,  1 Jun 2010 08:38:26 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 0B0CE3A68A4 for <xcon@ietf.org>; Tue,  1 Jun 2010 08:38:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,341,1272859200";  d="scan'208,217";a="220857202"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 01 Jun 2010 11:38:13 -0400
X-IronPort-AV: E=Sophos;i="4.53,341,1272859200";  d="scan'208,217";a="479905397"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.153]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Jun 2010 11:38:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB01A0.65B011D7"
Date: Tue, 1 Jun 2010 16:37:52 +0100
Message-ID: <4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON]   I-D Action:draft-ietf-xcon-ccmp-07.txt
Thread-Index: Acrla81R5loMyOpgQ+mWBS732veu/gAg/tigBrfkryAAM/dHwAAAa+tg
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com><20100426201045.8x0hgw8rkkw488cs@webmail.unina.it> <4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com>
From: "Duddy, Sean (Sean)" <duddy@avaya.com>
To: <xcon@ietf.org>
Subject: [XCON]    I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jun 2010 15:38:29 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB01A0.65B011D7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Simon,
    xsd namepsace is not defined , you need to change to xs istead
xs:simpleType name=3D"response-codeType">
         <xsd:restriction base=3D"xsd:positiveInteger">
                 <xsd:pattern value=3D"[0-9][0-9][0-9]" />
         </xsd:restriction>



Barnes, et al.          Expires October 28, 2010               [Page 80]

  <outbind://57/#page-81>=20
Internet-Draft                    CCMP                        April 2010


    </xs:simpleType>


------_=_NextPart_001_01CB01A0.65B011D7
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3676" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D275314115-01062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Simon,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D275314115-01062010>&nbsp;&nbsp;&nbsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>xsd namepsace is not defined , you =
need to=20
change to xs istead</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><PRE class=3Dnewpage><FONT size=3D3>xs:simpleType =
name=3D"response-codeType"&gt;
         &lt;<FONT color=3D#ff0000>xsd</FONT>:restriction base=3D"<FONT =
color=3D#ff0000>xsd</FONT>:positiveInteger"&gt;
                 &lt;<FONT color=3D#ff0000>xsd</FONT>:pattern =
value=3D"[0-9][0-9][0-9]" /&gt;
         &lt;/<FONT color=3D#ff0000>xsd</FONT>:restriction&gt;



<SPAN class=3Dgrey>Barnes, et al.          Expires October 28, 2010      =
         [Page 80]</SPAN>
</FONT></PRE><PRE class=3Dnewpage><A class=3Dinvisible id=3Dpage-81 =
href=3D"outbind://57/#page-81" name=3Dpage-81><FONT size=3D3> =
</FONT></A>
<FONT size=3D3><SPAN class=3Dgrey>Internet-Draft                    CCMP =
                       April 2010</SPAN>


    &lt;/xs:simpleType&gt;
</FONT></PRE></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01CB01A0.65B011D7--

From duddy@avaya.com  Tue Jun  1 08:51:47 2010
Return-Path: <duddy@avaya.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10A4C28C0E9 for <xcon@core3.amsl.com>; Tue,  1 Jun 2010 08:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.516
X-Spam-Level: 
X-Spam-Status: No, score=-0.516 tagged_above=-999 required=5 tests=[AWL=0.223,  BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRFWf7d5VB7e for <xcon@core3.amsl.com>; Tue,  1 Jun 2010 08:51:46 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id C05083A6A33 for <xcon@ietf.org>; Tue,  1 Jun 2010 08:51:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,341,1272859200";  d="scan'208,217";a="220859604"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 01 Jun 2010 11:51:33 -0400
X-IronPort-AV: E=Sophos;i="4.53,341,1272859200";  d="scan'208,217";a="468268916"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.153]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 01 Jun 2010 11:51:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB01A2.20D20389"
Date: Tue, 1 Jun 2010 16:50:15 +0100
Message-ID: <4408C6EC74CC3D42824FD68FDA8E8F710125F7F2@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-ietf-xcon-ccmp-07.txt
Thread-Index: Acrla81R5loMyOpgQ+mWBS732veu/gAg/tigBrfkryAAM/dHwAAAa+tgAABgE8A=
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com><20100426201045.8x0hgw8rkkw488cs@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com> <4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com>
From: "Duddy, Sean (Sean)" <duddy@avaya.com>
To: <xcon@ietf.org>
Subject: [XCON] I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jun 2010 15:51:47 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB01A2.20D20389
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Simon,
    The ccmp request extensions(see below) are generating a Unique
Particle Attribution violation. This is happening because
ccmp-request-message-type has an any also...
Maybe these extensions need a defined element which basically holds an
any...
=20
=20
 <!-- CCMP request extensions... -->
        <xs:complexType name=3D"ccmp-extended-request-message-type">
          <xs:complexContent>
                <xs:extension base=3D"tns:ccmp-request-message-type">
                  <xs:sequence>
                        <xs:any namespace=3D"##other"
processContents=3D"lax" minOccurs=3D"0"
                          maxOccurs=3D"unbounded" />
                  </xs:sequence>
                </xs:extension>
          </xs:complexContent>
        </xs:complexType>
=20
  <!-- CCMP response extensions... -->
        <xs:complexType name=3D"ccmp-extended-response-message-type">
          <xs:complexContent>
                <xs:extension base=3D"tns:ccmp-response-message-type">
                  <xs:sequence>
                        <xs:any namespace=3D"##other"
processContents=3D"lax" minOccurs=3D"0"
                          maxOccurs=3D"unbounded" />
                  </xs:sequence>
                </xs:extension>
          </xs:complexContent>
        </xs:complexType>

------_=_NextPart_001_01CB01A2.20D20389
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3676" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D007165215-01062010><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>H<SPAN class=3D007165215-01062010>i=20
Simon,</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D007165215-01062010><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN =
class=3D007165215-01062010>&nbsp;&nbsp;&nbsp; The=20
ccmp request extensions(see below)&nbsp;are generating a Unique Particle =

Attribution violation. This is happening because =
ccmp-request-message-type has=20
an any also...</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D007165215-01062010><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D007165215-01062010>Maybe =
these extensions=20
need a defined element which basically holds an=20
any...</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D007165215-01062010><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D007165215-01062010></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D007165215-01062010><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D007165215-01062010></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D007165215-01062010><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN =
class=3D007165215-01062010>&nbsp;&lt;!-- CCMP=20
request extensions... =
--&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:complexType=20
name=3D"ccmp-extended-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:extension=20
base=3D"tns:ccmp-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
&lt;xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
&lt;xs:any namespace=3D"##other" processContents=3D"lax"=20
minOccurs=3D"0"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
maxOccurs=3D"unbounded"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:extension&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
&lt;/xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

&lt;/xs:complexType&gt;</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D007165215-01062010><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D007165215-01062010>&nbsp; =
&lt;!-- CCMP=20
response extensions... =
--&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:complexType=20
name=3D"ccmp-extended-response-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:extension=20
base=3D"tns:ccmp-response-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
&lt;xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
&lt;xs:any namespace=3D"##other" processContents=3D"lax"=20
minOccurs=3D"0"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
maxOccurs=3D"unbounded"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:extension&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
&lt;/xs:complexContent&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

&lt;/xs:complexType&gt;</SPAN></FONT></FONT></FONT></SPAN></DIV></BODY></=
HTML>

------_=_NextPart_001_01CB01A2.20D20389--

From duddy@avaya.com  Wed Jun  2 06:20:53 2010
Return-Path: <duddy@avaya.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6B043A68F8 for <xcon@core3.amsl.com>; Wed,  2 Jun 2010 06:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.201
X-Spam-Level: 
X-Spam-Status: No, score=-0.201 tagged_above=-999 required=5 tests=[AWL=-0.203, BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zt7v15rJ5vas for <xcon@core3.amsl.com>; Wed,  2 Jun 2010 06:20:52 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 3218F3A683D for <xcon@ietf.org>; Wed,  2 Jun 2010 06:20:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,347,1272859200"; d="scan'208,217";a="18700273"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 02 Jun 2010 07:52:13 -0400
X-IronPort-AV: E=Sophos;i="4.53,347,1272859200";  d="scan'208,217";a="480184556"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.153]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Jun 2010 07:52:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB024A.00D580D5"
Date: Wed, 2 Jun 2010 12:51:57 +0100
Message-ID: <4408C6EC74CC3D42824FD68FDA8E8F710125F8A8@306900ANEX2.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-ietf-xcon-ccmp-07.txt
Thread-Index: Acrla81R5loMyOpgQ+mWBS732veu/gAg/tigBrfkryAAM/dHwAAAa+tgAABgE8AAKehZwA==
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com><20100426201045.8x0hgw8rkkw488cs@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com> <4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com>
From: "Duddy, Sean (Sean)" <duddy@avaya.com>
To: <xcon@ietf.org>
Subject: [XCON] I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jun 2010 13:20:54 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB024A.00D580D5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Simon,
    I am wondering what is the most appropriate error code when a user
cannot be authenticated by the ccmp server? i.e. invalid user name or
password.
=20
Around this area, we have the following error code defined:-
424 Authentication Required: User's authentication information missing
in a request to perform the requested operation. "subject" parameter
needed in the request.=20
=20
So we need another code like 'INVALID AUTHENTICATION' or we simply
change 424 to something like:-
=20
424 Invalid Authentication : User's authentication information is
missing or invalid.
=20
I prefer just having the one code i.e. renaming 424.
=20
Regards
Sean

------_=_NextPart_001_01CB024A.00D580D5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3676" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =
size=3D2>Hi=20
Simon,</FONT></SPAN></DIV>
<DIV><SPAN class=3D740125211-02062010>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial><FONT=20
color=3D#0000ff size=3D2>I am wondering what is the most appropriate =
error code when=20
a user cannot be authenticated by the ccmp server? i.e. invalid user =
name or=20
password.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =
size=3D2>Around=20
this area, we have the following error code =
defined:-</FONT></SPAN></DIV>
<DIV><SPAN class=3D740125211-02062010>424 Authentication Required: =
User's=20
authentication information missing in a request to perform the requested =

operation. "subject" parameter needed in the request. </SPAN></DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =
size=3D2>So we=20
need another code like 'INVALID AUTHENTICATION' or we simply change 424 =
to=20
something like:-</FONT></SPAN></DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D740125211-02062010>
<DIV><SPAN class=3D740125211-02062010>424 Invalid Authentication : =
User's=20
authentication information is missing or invalid.</SPAN></DIV>
<DIV><SPAN class=3D740125211-02062010></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
prefer just having the one code i.e. renaming 424.</FONT></SPAN></DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =

size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D740125211-02062010><FONT face=3DArial color=3D#0000ff =

size=3D2>Sean</FONT></SPAN></DIV></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01CB024A.00D580D5--

From duddy@avaya.com  Wed Jun  2 09:40:24 2010
Return-Path: <duddy@avaya.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1DCD3A68C4 for <xcon@core3.amsl.com>; Wed,  2 Jun 2010 09:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.16
X-Spam-Level: 
X-Spam-Status: No, score=-0.16 tagged_above=-999 required=5 tests=[AWL=-0.162,  BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T04Pj0RTG2lP for <xcon@core3.amsl.com>; Wed,  2 Jun 2010 09:40:22 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 910173A6872 for <xcon@ietf.org>; Wed,  2 Jun 2010 09:40:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,348,1272859200";  d="scan'208,217";a="221075373"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 02 Jun 2010 12:40:08 -0400
X-IronPort-AV: E=Sophos;i="4.53,348,1272859200";  d="scan'208,217";a="468682964"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.153]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 02 Jun 2010 12:40:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB0272.3AD88E03"
Date: Wed, 2 Jun 2010 17:39:54 +0100
Message-ID: <4408C6EC74CC3D42824FD68FDA8E8F710125F94B@306900ANEX2.global.avaya.com>
In-Reply-To: <209F0863F938D249AFDC024EC4C9E3E20C077CC2EA@ESESSCMS0353.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-xcon-common-data-model-19
Thread-Index: AcqfSij3aQa6iQTxQq+jLBhs8rRvvgFciftgF23MgPA=
References: <4408C6EC74CC3D42824FD68FDA8E8F71010D14E6@306900ANEX2.global.avaya.com> <209F0863F938D249AFDC024EC4C9E3E20C077CC2EA@ESESSCMS0353.eemea.ericsson.se>
From: "Duddy, Sean (Sean)" <duddy@avaya.com>
To: <xcon@ietf.org>
Subject: Re: [XCON] draft-ietf-xcon-common-data-model-19
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jun 2010 16:40:24 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB0272.3AD88E03
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,
    The latest version of the data model defines the conference-password
as single string. In version 17 it was changed to be a list.
Why was this change reverted?
=20
Sean

________________________________

From: Oscar Novo [mailto:oscar.novo@ericsson.com]=20
Sent: 03 February 2010 15:11
To: Duddy, Sean (Sean); xcon@ietf.org
Subject: RE: draft-ietf-xcon-common-data-model-14


Hi Sean,
=20
True, the field should be defined as multiple password. I'll change that
in the following version of the draft.
The propose to have different passwords in the flexibility to have
different set of users with different credentials. So, the conference
server can restrict access to a set of users by just removing the
credentials from the server.
=20
I think the extension of the <conf-uris> element is not really needed
since the limitations of the credentials can be done using the same
roles (you might want to restrict access to the group of participants A
but not the group of participants B).
=20
Regards,
=20
Oscar

________________________________

From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
Duddy, Sean (Sean)
Sent: 27. tammikuuta 2010 14:14
To: xcon@ietf.org
Subject: [XCON] draft-ietf-xcon-common-data-model-14


Hi all,
    The new password field in  draft-ietf-xcon-common-data-model-14 is
defined as follows:-
=20
    <xs:element name=3D"conference-password" type=3D"xs:string"/>

=20
In section 4.2.10, it states that this field contain password(s). What
would be the usecase for multiple passcodes on the same URI?
If it is a valid use case then the xsd type for this should xs::list.
=20
Does the purpose field defined in rfc4575 need to be extended to
indicate the type of URI i.e. moderator,particpant etc?
Or how would a client that just created a conference distinguish between
the URIs?
=20
Regards
Sean

------_=_NextPart_001_01CB0272.3AD88E03
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3676" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi All,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D094054916-02062010>&nbsp;&nbsp;&nbsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>The latest version of the data =
model defines the=20
conference-password as single string. In version 17 it was changed to be =
a=20
list.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Why was this change =
reverted?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sean</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Oscar Novo=20
[mailto:oscar.novo@ericsson.com] <BR><B>Sent:</B> 03 February 2010=20
15:11<BR><B>To:</B> Duddy, Sean (Sean); xcon@ietf.org<BR><B>Subject:</B> =
RE:=20
draft-ietf-xcon-common-data-model-14<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Sean,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>True, the field should be defined as multiple =
password.=20
I'll change that in the following version of the =
draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The propose to have different passwords in the =
flexibility=20
to have different set of users with different credentials. So, the =
conference=20
server can restrict&nbsp;access to a set of users by just removing the=20
credentials from the server.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D144253310-03022010></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I think the extension of the &lt;conf-uris&gt; =
element is=20
not really needed since the limitations of the credentials can be done =
using the=20
same roles (you might want to restrict access to the group of =
participants A but=20
not the group of participants B).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Oscar</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> xcon-bounces@ietf.org=20
[mailto:xcon-bounces@ietf.org] <B>On Behalf Of </B>Duddy, Sean=20
(Sean)<BR><B>Sent:</B> 27. tammikuuta 2010 14:14<BR><B>To:</B>=20
xcon@ietf.org<BR><B>Subject:</B> [XCON]=20
draft-ietf-xcon-common-data-model-14<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Hi=20
all,</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;=20
The new password field&nbsp;in =
&nbsp;draft-ietf-xcon-common-data-model-14 is=20
defined as follows:-</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010>&nbsp;&nbsp;&nbsp; &lt;xs:element=20
name=3D"conference-password" type=3D"xs:string"/&gt;<BR></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>In =
section 4.2.10,=20
it states that this field contain password(s). What would be the usecase =
for=20
multiple passcodes on the same URI?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>If it =
is a valid use=20
case then the xsd type for this should xs::list.</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Does =
the purpose=20
field defined in rfc4575 need to be extended to indicate the type of URI =
i.e.=20
moderator,particpant etc?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Or how =
would a=20
client that just created a conference distinguish between the=20
URIs?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2>Sean</FONT></DIV></SPAN></BODY></HTML>

------_=_NextPart_001_01CB0272.3AD88E03--

From oscar.novo@ericsson.com  Thu Jun  3 00:17:12 2010
Return-Path: <oscar.novo@ericsson.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E8223A68D8 for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 00:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.998
X-Spam-Level: 
X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nY9WxKAunTaD for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 00:17:08 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 5C8853A681C for <xcon@ietf.org>; Thu,  3 Jun 2010 00:17:08 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b13ae0000071b2-59-4c0756e5fd80
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 53.83.29106.5E6570C4; Thu,  3 Jun 2010 09:16:53 +0200 (CEST)
Received: from ESESSCMS0353.eemea.ericsson.se ([169.254.2.40]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Thu, 3 Jun 2010 09:16:53 +0200
From: Oscar Novo <oscar.novo@ericsson.com>
To: "Duddy, Sean (Sean)" <duddy@avaya.com>, "xcon@ietf.org" <xcon@ietf.org>
Date: Thu, 3 Jun 2010 09:16:50 +0200
Thread-Topic: draft-ietf-xcon-common-data-model-19
Thread-Index: AcqfSij3aQa6iQTxQq+jLBhs8rRvvgFciftgF23MgPAAHigsgA==
Message-ID: <209F0863F938D249AFDC024EC4C9E3E21116FE3EB4@ESESSCMS0353.eemea.ericsson.se>
References: <4408C6EC74CC3D42824FD68FDA8E8F71010D14E6@306900ANEX2.global.avaya.com> <209F0863F938D249AFDC024EC4C9E3E20C077CC2EA@ESESSCMS0353.eemea.ericsson.se> <4408C6EC74CC3D42824FD68FDA8E8F710125F94B@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125F94B@306900ANEX2.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_209F0863F938D249AFDC024EC4C9E3E21116FE3EB4ESESSCMS0353e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [XCON] draft-ietf-xcon-common-data-model-19
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 07:17:12 -0000

--_000_209F0863F938D249AFDC024EC4C9E3E21116FE3EB4ESESSCMS0353e_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

Conference-password still is a list of password (check the rnc/rng schema a=
nd the text). In the w3c schema the conference-password is a string of mult=
iple passwords.
It was changed because the w3c schema was wrong before.

Cheers,

Oscar
________________________________
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of Dud=
dy, Sean (Sean)
Sent: 2. kes=E4kuuta 2010 19:40
To: xcon@ietf.org
Subject: Re: [XCON] draft-ietf-xcon-common-data-model-19

Hi All,
    The latest version of the data model defines the conference-password as=
 single string. In version 17 it was changed to be a list.
Why was this change reverted?

Sean

________________________________
From: Oscar Novo [mailto:oscar.novo@ericsson.com]
Sent: 03 February 2010 15:11
To: Duddy, Sean (Sean); xcon@ietf.org
Subject: RE: draft-ietf-xcon-common-data-model-14

Hi Sean,

True, the field should be defined as multiple password. I'll change that in=
 the following version of the draft.
The propose to have different passwords in the flexibility to have differen=
t set of users with different credentials. So, the conference server can re=
strict access to a set of users by just removing the credentials from the s=
erver.

I think the extension of the <conf-uris> element is not really needed since=
 the limitations of the credentials can be done using the same roles (you m=
ight want to restrict access to the group of participants A but not the gro=
up of participants B).

Regards,

Oscar

________________________________
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of Dud=
dy, Sean (Sean)
Sent: 27. tammikuuta 2010 14:14
To: xcon@ietf.org
Subject: [XCON] draft-ietf-xcon-common-data-model-14

Hi all,
    The new password field in  draft-ietf-xcon-common-data-model-14 is defi=
ned as follows:-

    <xs:element name=3D"conference-password" type=3D"xs:string"/>

In section 4.2.10, it states that this field contain password(s). What woul=
d be the usecase for multiple passcodes on the same URI?
If it is a valid use case then the xsd type for this should xs::list.

Does the purpose field defined in rfc4575 need to be extended to indicate t=
he type of URI i.e. moderator,particpant etc?
Or how would a client that just created a conference distinguish between th=
e URIs?

Regards
Sean

--_000_209F0863F938D249AFDC024EC4C9E3E21116FE3EB4ESESSCMS0353e_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.6001.18444" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hello,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Conference-password still is a list of password (c=
heck the=20
rnc/rng schema and the text). In the w3c schema the conference-password is =
a=20
string of multiple passwords.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010></SPAN><SPAN=20
class=3D278341207-03062010><FONT face=3DArial color=3D#0000ff size=3D2>It w=
as changed=20
because the w3c schema was wrong before. </FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D278341207-03062010><FONT face=3DArial color=3D#0000ff=20
size=3D2>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=3D278341207-03062010></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D278341207-03062010></SPAN><FONT face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>O<SPAN=20
class=3D278341207-03062010>scar</SPAN></FONT></FONT></FONT><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> xcon-bounces@ietf.org=20
[mailto:xcon-bounces@ietf.org] <B>On Behalf Of </B>Duddy, Sean=20
(Sean)<BR><B>Sent:</B> 2. kes=E4kuuta 2010 19:40<BR><B>To:</B>=20
xcon@ietf.org<BR><B>Subject:</B> Re: [XCON]=20
draft-ietf-xcon-common-data-model-19<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi All,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010>&nbsp;&nbsp;&n=
bsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>The latest version of the data model =
defines the=20
conference-password as single string. In version 17 it was changed to be a=
=20
list.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Why was this change reverted?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Sean</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Oscar Novo=20
[mailto:oscar.novo@ericsson.com] <BR><B>Sent:</B> 03 February 2010=20
15:11<BR><B>To:</B> Duddy, Sean (Sean); xcon@ietf.org<BR><B>Subject:</B> RE=
:=20
draft-ietf-xcon-common-data-model-14<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Sean,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>True, the field should be defined as multiple pass=
word.=20
I'll change that in the following version of the draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The propose to have different passwords in the fle=
xibility=20
to have different set of users with different credentials. So, the conferen=
ce=20
server can restrict&nbsp;access to a set of users by just removing the=20
credentials from the server.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I think the extension of the &lt;conf-uris&gt; ele=
ment is=20
not really needed since the limitations of the credentials can be done usin=
g the=20
same roles (you might want to restrict access to the group of participants =
A but=20
not the group of participants B).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Oscar</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> xcon-bounces@ietf.org=20
[mailto:xcon-bounces@ietf.org] <B>On Behalf Of </B>Duddy, Sean=20
(Sean)<BR><B>Sent:</B> 27. tammikuuta 2010 14:14<BR><B>To:</B>=20
xcon@ietf.org<BR><B>Subject:</B> [XCON]=20
draft-ietf-xcon-common-data-model-14<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Hi=20
all,</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>&nbsp;&nb=
sp;&nbsp;=20
The new password field&nbsp;in &nbsp;draft-ietf-xcon-common-data-model-14 i=
s=20
defined as follows:-</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010>&nbsp;&nbsp;&nbsp; &lt;xs:element=20
name=3D"conference-password" type=3D"xs:string"/&gt;<BR></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>In sectio=
n 4.2.10,=20
it states that this field contain password(s). What would be the usecase fo=
r=20
multiple passcodes on the same URI?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>If it is =
a valid use=20
case then the xsd type for this should xs::list.</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Does the =
purpose=20
field defined in rfc4575 need to be extended to indicate the type of URI i.=
e.=20
moderator,particpant etc?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Or how wo=
uld a=20
client that just created a conference distinguish between the=20
URIs?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2>Sean</FONT></DIV></SPAN></BODY></HTML>

--_000_209F0863F938D249AFDC024EC4C9E3E21116FE3EB4ESESSCMS0353e_--

From duddy@avaya.com  Thu Jun  3 02:50:46 2010
Return-Path: <duddy@avaya.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3E433A684B for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 02:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.167
X-Spam-Level: 
X-Spam-Status: No, score=0.167 tagged_above=-999 required=5 tests=[AWL=-0.435,  BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_26=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9a8-fQjKgEh4 for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 02:50:45 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 014803A697F for <xcon@ietf.org>; Thu,  3 Jun 2010 02:50:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,353,1272859200";  d="scan'208,217";a="191713811"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 03 Jun 2010 05:50:30 -0400
X-IronPort-AV: E=Sophos;i="4.53,353,1272859200";  d="scan'208,217";a="468895437"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.153]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 03 Jun 2010 05:50:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB0302.261D15CF"
Date: Thu, 3 Jun 2010 10:53:21 +0100
Message-ID: <4408C6EC74CC3D42824FD68FDA8E8F710125F9EA@306900ANEX2.global.avaya.com>
In-Reply-To: <209F0863F938D249AFDC024EC4C9E3E21116FE3EB4@ESESSCMS0353.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-xcon-common-data-model-19
Thread-Index: AcqfSij3aQa6iQTxQq+jLBhs8rRvvgFciftgF23MgPAAHigsgAAFfWcw
References: <4408C6EC74CC3D42824FD68FDA8E8F71010D14E6@306900ANEX2.global.avaya.com><209F0863F938D249AFDC024EC4C9E3E20C077CC2EA@ESESSCMS0353.eemea.ericsson.se> <4408C6EC74CC3D42824FD68FDA8E8F710125F94B@306900ANEX2.global.avaya.com> <209F0863F938D249AFDC024EC4C9E3E21116FE3EB4@ESESSCMS0353.eemea.ericsson.se>
From: "Duddy, Sean (Sean)" <duddy@avaya.com>
To: "Oscar Novo" <oscar.novo@ericsson.com>, <xcon@ietf.org>
Subject: Re: [XCON] draft-ietf-xcon-common-data-model-19
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 09:50:46 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB0302.261D15CF
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Oscar,
=20
Ok before it was of type <xs:list itemType=3D"xs:string"/> now it is of =
type xs:string.
=20
So what is the delimiting character(s) that seperate each password in =
the string?
=20
I would have thought a list is more appropriate...

________________________________

From: Oscar Novo [mailto:oscar.novo@ericsson.com]=20
Sent: 03 June 2010 08:17
To: Duddy, Sean (Sean); xcon@ietf.org
Subject: RE: draft-ietf-xcon-common-data-model-19


Hello,
=20
Conference-password still is a list of password (check the rnc/rng =
schema and the text). In the w3c schema the conference-password is a =
string of multiple passwords.
It was changed because the w3c schema was wrong before.=20
=20
Cheers,
=20
Oscar

________________________________

From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of =
Duddy, Sean (Sean)
Sent: 2. kes=E4kuuta 2010 19:40
To: xcon@ietf.org
Subject: Re: [XCON] draft-ietf-xcon-common-data-model-19


Hi All,
    The latest version of the data model defines the conference-password =
as single string. In version 17 it was changed to be a list.
Why was this change reverted?
=20
Sean

________________________________

From: Oscar Novo [mailto:oscar.novo@ericsson.com]=20
Sent: 03 February 2010 15:11
To: Duddy, Sean (Sean); xcon@ietf.org
Subject: RE: draft-ietf-xcon-common-data-model-14


Hi Sean,
=20
True, the field should be defined as multiple password. I'll change that =
in the following version of the draft.
The propose to have different passwords in the flexibility to have =
different set of users with different credentials. So, the conference =
server can restrict access to a set of users by just removing the =
credentials from the server.
=20
I think the extension of the <conf-uris> element is not really needed =
since the limitations of the credentials can be done using the same =
roles (you might want to restrict access to the group of participants A =
but not the group of participants B).
=20
Regards,
=20
Oscar

________________________________

From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of =
Duddy, Sean (Sean)
Sent: 27. tammikuuta 2010 14:14
To: xcon@ietf.org
Subject: [XCON] draft-ietf-xcon-common-data-model-14


Hi all,
    The new password field in  draft-ietf-xcon-common-data-model-14 is =
defined as follows:-
=20
    <xs:element name=3D"conference-password" type=3D"xs:string"/>

=20
In section 4.2.10, it states that this field contain password(s). What =
would be the usecase for multiple passcodes on the same URI?
If it is a valid use case then the xsd type for this should xs::list.
=20
Does the purpose field defined in rfc4575 need to be extended to =
indicate the type of URI i.e. moderator,particpant etc?
Or how would a client that just created a conference distinguish between =
the URIs?
=20
Regards
Sean

------_=_NextPart_001_01CB0302.261D15CF
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3676" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Oscar,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D787454909-03062010></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Ok before it was of type &lt;xs:list=20
itemType=3D"xs:string"/&gt; now it is of type =
xs:string.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>So what is the delimiting character(s) that =
seperate each=20
password in the string?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I would have thought a list is more=20
appropriate...</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Oscar Novo=20
[mailto:oscar.novo@ericsson.com] <BR><B>Sent:</B> 03 June 2010=20
08:17<BR><B>To:</B> Duddy, Sean (Sean); xcon@ietf.org<BR><B>Subject:</B> =
RE:=20
draft-ietf-xcon-common-data-model-19<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hello,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Conference-password still is a list of password =
(check the=20
rnc/rng schema and the text). In the w3c schema the conference-password =
is a=20
string of multiple passwords.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D278341207-03062010></SPAN><SPAN=20
class=3D278341207-03062010><FONT face=3DArial color=3D#0000ff =
size=3D2>It was changed=20
because the w3c schema was wrong before. </FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D278341207-03062010><FONT face=3DArial color=3D#0000ff =

size=3D2>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=3D278341207-03062010></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D278341207-03062010></SPAN><FONT face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>O<SPAN=20
class=3D278341207-03062010>scar</SPAN></FONT></FONT></FONT><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> xcon-bounces@ietf.org=20
[mailto:xcon-bounces@ietf.org] <B>On Behalf Of </B>Duddy, Sean=20
(Sean)<BR><B>Sent:</B> 2. kes=E4kuuta 2010 19:40<BR><B>To:</B>=20
xcon@ietf.org<BR><B>Subject:</B> Re: [XCON]=20
draft-ietf-xcon-common-data-model-19<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi All,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D094054916-02062010>&nbsp;&nbsp;&nbsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>The latest version of the data =
model defines the=20
conference-password as single string. In version 17 it was changed to be =
a=20
list.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Why was this change =
reverted?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sean</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Oscar Novo=20
[mailto:oscar.novo@ericsson.com] <BR><B>Sent:</B> 03 February 2010=20
15:11<BR><B>To:</B> Duddy, Sean (Sean); xcon@ietf.org<BR><B>Subject:</B> =
RE:=20
draft-ietf-xcon-common-data-model-14<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Sean,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>True, the field should be defined as multiple =
password.=20
I'll change that in the following version of the =
draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The propose to have different passwords in the =
flexibility=20
to have different set of users with different credentials. So, the =
conference=20
server can restrict&nbsp;access to a set of users by just removing the=20
credentials from the server.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D144253310-03022010></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I think the extension of the &lt;conf-uris&gt; =
element is=20
not really needed since the limitations of the credentials can be done =
using the=20
same roles (you might want to restrict access to the group of =
participants A but=20
not the group of participants B).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Oscar</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> xcon-bounces@ietf.org=20
[mailto:xcon-bounces@ietf.org] <B>On Behalf Of </B>Duddy, Sean=20
(Sean)<BR><B>Sent:</B> 27. tammikuuta 2010 14:14<BR><B>To:</B>=20
xcon@ietf.org<BR><B>Subject:</B> [XCON]=20
draft-ietf-xcon-common-data-model-14<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Hi=20
all,</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;=20
The new password field&nbsp;in =
&nbsp;draft-ietf-xcon-common-data-model-14 is=20
defined as follows:-</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010>&nbsp;&nbsp;&nbsp; &lt;xs:element=20
name=3D"conference-password" type=3D"xs:string"/&gt;<BR></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>In =
section 4.2.10,=20
it states that this field contain password(s). What would be the usecase =
for=20
multiple passcodes on the same URI?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>If it =
is a valid use=20
case then the xsd type for this should xs::list.</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Does =
the purpose=20
field defined in rfc4575 need to be extended to indicate the type of URI =
i.e.=20
moderator,particpant etc?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Or how =
would a=20
client that just created a conference distinguish between the=20
URIs?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2>Sean</FONT></DIV></SPAN></BODY></HTML>

------_=_NextPart_001_01CB0302.261D15CF--

From oscar.novo@ericsson.com  Thu Jun  3 04:45:55 2010
Return-Path: <oscar.novo@ericsson.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F21028C152 for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 04:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.791
X-Spam-Level: 
X-Spam-Status: No, score=-3.791 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_40=-0.185, HTML_MESSAGE=0.001, J_CHICKENPOX_26=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zHw2Qs9p583V for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 04:45:53 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 2B1603A69EF for <xcon@ietf.org>; Thu,  3 Jun 2010 04:45:52 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b13ae0000071b2-6d-4c0795e2b72c
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 02.8A.29106.2E5970C4; Thu,  3 Jun 2010 13:45:39 +0200 (CEST)
Received: from ESESSCMS0353.eemea.ericsson.se ([169.254.2.40]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Thu, 3 Jun 2010 13:45:38 +0200
From: Oscar Novo <oscar.novo@ericsson.com>
To: "Duddy, Sean (Sean)" <duddy@avaya.com>, "xcon@ietf.org" <xcon@ietf.org>
Date: Thu, 3 Jun 2010 13:45:37 +0200
Thread-Topic: draft-ietf-xcon-common-data-model-19
Thread-Index: AcqfSij3aQa6iQTxQq+jLBhs8rRvvgFciftgF23MgPAAHigsgAAFfWcwAAOujSA=
Message-ID: <209F0863F938D249AFDC024EC4C9E3E21116FE4126@ESESSCMS0353.eemea.ericsson.se>
References: <4408C6EC74CC3D42824FD68FDA8E8F71010D14E6@306900ANEX2.global.avaya.com><209F0863F938D249AFDC024EC4C9E3E20C077CC2EA@ESESSCMS0353.eemea.ericsson.se> <4408C6EC74CC3D42824FD68FDA8E8F710125F94B@306900ANEX2.global.avaya.com> <209F0863F938D249AFDC024EC4C9E3E21116FE3EB4@ESESSCMS0353.eemea.ericsson.se> <4408C6EC74CC3D42824FD68FDA8E8F710125F9EA@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125F9EA@306900ANEX2.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_209F0863F938D249AFDC024EC4C9E3E21116FE4126ESESSCMS0353e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [XCON] draft-ietf-xcon-common-data-model-19
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 11:45:55 -0000

--_000_209F0863F938D249AFDC024EC4C9E3E21116FE4126ESESSCMS0353e_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

I really recommend you to look at the rng/rnc schema, not at the w3c schema=
. RELAX NG schema is the 'oficial' schema of the data model. The w3c schema=
 is just an informative schemas and w3c schemas have limitations such as th=
e case you asked me.

Regarding your question, it's up to the implementor but it could be whitesp=
aces if we think that, normally,  a password with whitespaces is not valid.

Cheers,

Oscar

________________________________
From: Duddy, Sean (Sean) [mailto:duddy@avaya.com]
Sent: 3. kes=E4kuuta 2010 12:53
To: Oscar Novo; xcon@ietf.org
Subject: RE: draft-ietf-xcon-common-data-model-19

Hi Oscar,

Ok before it was of type <xs:list itemType=3D"xs:string"/> now it is of typ=
e xs:string.

So what is the delimiting character(s) that seperate each password in the s=
tring?

I would have thought a list is more appropriate...

________________________________
From: Oscar Novo [mailto:oscar.novo@ericsson.com]
Sent: 03 June 2010 08:17
To: Duddy, Sean (Sean); xcon@ietf.org
Subject: RE: draft-ietf-xcon-common-data-model-19

Hello,

Conference-password still is a list of password (check the rnc/rng schema a=
nd the text). In the w3c schema the conference-password is a string of mult=
iple passwords.
It was changed because the w3c schema was wrong before.

Cheers,

Oscar
________________________________
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of Dud=
dy, Sean (Sean)
Sent: 2. kes=E4kuuta 2010 19:40
To: xcon@ietf.org
Subject: Re: [XCON] draft-ietf-xcon-common-data-model-19

Hi All,
    The latest version of the data model defines the conference-password as=
 single string. In version 17 it was changed to be a list.
Why was this change reverted?

Sean

________________________________
From: Oscar Novo [mailto:oscar.novo@ericsson.com]
Sent: 03 February 2010 15:11
To: Duddy, Sean (Sean); xcon@ietf.org
Subject: RE: draft-ietf-xcon-common-data-model-14

Hi Sean,

True, the field should be defined as multiple password. I'll change that in=
 the following version of the draft.
The propose to have different passwords in the flexibility to have differen=
t set of users with different credentials. So, the conference server can re=
strict access to a set of users by just removing the credentials from the s=
erver.

I think the extension of the <conf-uris> element is not really needed since=
 the limitations of the credentials can be done using the same roles (you m=
ight want to restrict access to the group of participants A but not the gro=
up of participants B).

Regards,

Oscar

________________________________
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of Dud=
dy, Sean (Sean)
Sent: 27. tammikuuta 2010 14:14
To: xcon@ietf.org
Subject: [XCON] draft-ietf-xcon-common-data-model-14

Hi all,
    The new password field in  draft-ietf-xcon-common-data-model-14 is defi=
ned as follows:-

    <xs:element name=3D"conference-password" type=3D"xs:string"/>

In section 4.2.10, it states that this field contain password(s). What woul=
d be the usecase for multiple passcodes on the same URI?
If it is a valid use case then the xsd type for this should xs::list.

Does the purpose field defined in rfc4575 need to be extended to indicate t=
he type of URI i.e. moderator,particpant etc?
Or how would a client that just created a conference distinguish between th=
e URIs?

Regards
Sean

--_000_209F0863F938D249AFDC024EC4C9E3E21116FE4126ESESSCMS0353e_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.6001.18444" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D122113511-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hello,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D122113511-03062010><SPAN lang=3DF=
I>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D122113511-03062010>I really recommend you to look at the </SPAN>rng=
/rnc=20
schema<SPAN class=3D122113511-03062010>, not at the w3c schema. RELAX NG sc=
hema is=20
the 'oficial' schema of the data model. The w3c schema is just an informati=
ve=20
schemas and w3c schemas have limitations such as the case you asked me.=20
</SPAN></FONT></FONT></FONT></P></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D122113511-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Regarding your question, it's up to the implemento=
r but it=20
could be whitespaces if we think that,&nbsp;normally,&nbsp; a password with=
=20
whitespaces is not valid.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D122113511-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D122113511-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D122113511-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D122113511-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Oscar</FONT>&nbsp;</SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Duddy, Sean (Sean)=20
[mailto:duddy@avaya.com] <BR><B>Sent:</B> 3. kes=E4kuuta 2010 12:53<BR><B>T=
o:</B>=20
Oscar Novo; xcon@ietf.org<BR><B>Subject:</B> RE:=20
draft-ietf-xcon-common-data-model-19<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Oscar,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Ok before it was of type &lt;xs:list=20
itemType=3D"xs:string"/&gt; now it is of type xs:string.</FONT></SPAN></DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>So what is the delimiting character(s) that sepera=
te each=20
password in the string?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D787454909-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I would have thought a list is more=20
appropriate...</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Oscar Novo=20
[mailto:oscar.novo@ericsson.com] <BR><B>Sent:</B> 03 June 2010=20
08:17<BR><B>To:</B> Duddy, Sean (Sean); xcon@ietf.org<BR><B>Subject:</B> RE=
:=20
draft-ietf-xcon-common-data-model-19<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hello,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Conference-password still is a list of password (c=
heck the=20
rnc/rng schema and the text). In the w3c schema the conference-password is =
a=20
string of multiple passwords.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D278341207-03062010></SPAN><SPAN=20
class=3D278341207-03062010><FONT face=3DArial color=3D#0000ff size=3D2>It w=
as changed=20
because the w3c schema was wrong before. </FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D278341207-03062010><FONT face=3DArial color=3D#0000ff=20
size=3D2>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=3D278341207-03062010></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D278341207-03062010></SPAN><FONT face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>O<SPAN=20
class=3D278341207-03062010>scar</SPAN></FONT></FONT></FONT><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> xcon-bounces@ietf.org=20
[mailto:xcon-bounces@ietf.org] <B>On Behalf Of </B>Duddy, Sean=20
(Sean)<BR><B>Sent:</B> 2. kes=E4kuuta 2010 19:40<BR><B>To:</B>=20
xcon@ietf.org<BR><B>Subject:</B> Re: [XCON]=20
draft-ietf-xcon-common-data-model-19<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi All,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010>&nbsp;&nbsp;&n=
bsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>The latest version of the data model =
defines the=20
conference-password as single string. In version 17 it was changed to be a=
=20
list.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Why was this change reverted?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D094054916-02062010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Sean</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Oscar Novo=20
[mailto:oscar.novo@ericsson.com] <BR><B>Sent:</B> 03 February 2010=20
15:11<BR><B>To:</B> Duddy, Sean (Sean); xcon@ietf.org<BR><B>Subject:</B> RE=
:=20
draft-ietf-xcon-common-data-model-14<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Sean,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>True, the field should be defined as multiple pass=
word.=20
I'll change that in the following version of the draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The propose to have different passwords in the fle=
xibility=20
to have different set of users with different credentials. So, the conferen=
ce=20
server can restrict&nbsp;access to a set of users by just removing the=20
credentials from the server.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I think the extension of the &lt;conf-uris&gt; ele=
ment is=20
not really needed since the limitations of the credentials can be done usin=
g the=20
same roles (you might want to restrict access to the group of participants =
A but=20
not the group of participants B).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D144253310-03022010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Oscar</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> xcon-bounces@ietf.org=20
[mailto:xcon-bounces@ietf.org] <B>On Behalf Of </B>Duddy, Sean=20
(Sean)<BR><B>Sent:</B> 27. tammikuuta 2010 14:14<BR><B>To:</B>=20
xcon@ietf.org<BR><B>Subject:</B> [XCON]=20
draft-ietf-xcon-common-data-model-14<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Hi=20
all,</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>&nbsp;&nb=
sp;&nbsp;=20
The new password field&nbsp;in &nbsp;draft-ietf-xcon-common-data-model-14 i=
s=20
defined as follows:-</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010>&nbsp;&nbsp;&nbsp; &lt;xs:element=20
name=3D"conference-password" type=3D"xs:string"/&gt;<BR></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>In sectio=
n 4.2.10,=20
it states that this field contain password(s). What would be the usecase fo=
r=20
multiple passcodes on the same URI?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>If it is =
a valid use=20
case then the xsd type for this should xs::list.</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Does the =
purpose=20
field defined in rfc4575 need to be extended to indicate the type of URI i.=
e.=20
moderator,particpant etc?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial size=3D2>Or how wo=
uld a=20
client that just created a conference distinguish between the=20
URIs?</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D640255611-27012010><FONT face=3DArial=20
size=3D2>Sean</FONT></DIV></SPAN></BODY></HTML>

--_000_209F0863F938D249AFDC024EC4C9E3E21116FE4126ESESSCMS0353e_--

From spromano@unina.it  Thu Jun  3 08:24:34 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 461D23A69D4 for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 08:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.482
X-Spam-Level: **
X-Spam-Status: No, score=2.482 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, J_CHICKENPOX_210=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pgg6kraB8VwG for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 08:24:33 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by core3.amsl.com (Postfix) with ESMTP id E260A3A68BF for <xcon@ietf.org>; Thu,  3 Jun 2010 08:24:31 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp1.unina.it (8.14.0/8.14.0) with ESMTP id o53FOC0r016529 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 3 Jun 2010 17:24:13 +0200
Message-ID: <4C07C91C.7020504@unina.it>
Date: Thu, 03 Jun 2010 17:24:12 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Duddy, Sean (Sean)" <duddy@avaya.com>
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com><20100426201045.8x0hgw8rkkw488cs@webmail.unina.it>	<4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com> <4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com>
Content-Type: multipart/alternative; boundary="------------090109060002050200020808"
Cc: xcon@ietf.org
Subject: Re: [XCON] I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 15:24:34 -0000

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

Hi Sean,

right! This is the first of a series of minor errors we had already 
discovered and fixed in the upcoming version of the draft, which will be 
uploaded shortly. Thank you for mentioning it...I really appreciate the 
fact that someone else is playing with the specs ;-).

Cheers,

Simon

Il 01/06/2010 17.37, Duddy, Sean (Sean) ha scritto:
> Hi Simon,
> xsd namepsace is not defined , you need to change to xs istead
> xs:simpleType name="response-codeType">
>           <xsd:restriction base="xsd:positiveInteger">
>                   <xsd:pattern value="[0-9][0-9][0-9]" />
>           </xsd:restriction>
>
>
>
> Barnes, et al.          Expires October 28, 2010               [Page 80]
>     <outbind://57/#page-81>
> Internet-Draft                    CCMP                        April 2010
>
>
>      </xs:simpleType>
>
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>    

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



--------------090109060002050200020808
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Sean,<br>
<br>
right! This is the first of a series of minor errors we had already
discovered and fixed in the upcoming version of the draft, which will
be uploaded shortly. Thank you for mentioning it...I really appreciate
the fact that someone else is playing with the specs ;-).<br>
<br>
Cheers,<br>
<br>
Simon<br>
<br>
Il 01/06/2010 17.37, Duddy, Sean (Sean) ha scritto:
<blockquote
 cite="mid:4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com"
 type="cite">
  <title></title>
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta content="MSHTML 6.00.2900.3676" name="GENERATOR">
  <div dir="ltr" align="left"><span class="275314115-01062010"><font
 color="#0000ff" face="Arial" size="2">Hi Simon,</font></span></div>
  <div dir="ltr" align="left"><span class="275314115-01062010">&nbsp;&nbsp;&nbsp; <font
 color="#0000ff" face="Arial" size="2">xsd namepsace is not defined ,
you need to change to xs istead</font></span></div>
  <div dir="ltr" align="left"><font color="#0000ff" face="Arial"
 size="2">
  <pre class="newpage"><font size="3">xs:simpleType name="response-codeType"&gt;
         &lt;<font color="#ff0000">xsd</font>:restriction base="<font
 color="#ff0000">xsd</font>:positiveInteger"&gt;
                 &lt;<font color="#ff0000">xsd</font>:pattern value="[0-9][0-9][0-9]" /&gt;
         &lt;/<font color="#ff0000">xsd</font>:restriction&gt;



<span class="grey">Barnes, et al.          Expires October 28, 2010               [Page 80]</span>
</font></pre>
  <pre class="newpage"><a moz-do-not-send="true" class="invisible"
 id="page-81" href="outbind://57/#page-81" name="page-81"><font size="3"> </font></a>
<font size="3"><span class="grey">Internet-Draft                    CCMP                        April 2010</span>


    &lt;/xs:simpleType&gt;
</font></pre>
  </font></div>
  <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
XCON mailing list
<a class="moz-txt-link-abbreviated" href="mailto:XCON@ietf.org">XCON@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/xcon">https://www.ietf.org/mailman/listinfo/xcon</a>
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
                            _\\|//_
                            ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    Simon Pietro Romano
              Universita' di Napoli Federico II
                 Computer Science Department 
        Phone: +39 081 7683823 -- Fax: +39 081 7684219
                e-mail: <a class="moz-txt-link-abbreviated" href="mailto:spromano@unina.it">spromano@unina.it</a>
          <a class="moz-txt-link-freetext" href="http://www.comics.unina.it/simonpietro.romano">http://www.comics.unina.it/simonpietro.romano</a>

    &lt;&lt;Molti mi dicono che lo scoraggiamento &egrave; l'alibi degli 
   idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. Magritte.
                         oooO
   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                          \ (    (   )
                           \_)    ) /
                                 (_/

</pre>
</body>
</html>

--------------090109060002050200020808--

From spromano@unina.it  Thu Jun  3 08:33:19 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 983E428C0F9 for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 08:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.182
X-Spam-Level: **
X-Spam-Status: No, score=2.182 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2F-Gc8F+FQG2 for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 08:33:00 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by core3.amsl.com (Postfix) with ESMTP id D50303A69A4 for <xcon@ietf.org>; Thu,  3 Jun 2010 08:32:55 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp1.unina.it (8.14.0/8.14.0) with ESMTP id o53FVwof016839 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 3 Jun 2010 17:31:58 +0200
Message-ID: <4C07CAED.5040306@unina.it>
Date: Thu, 03 Jun 2010 17:31:57 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Duddy, Sean (Sean)" <duddy@avaya.com>
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com><20100426201045.8x0hgw8rkkw488cs@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com>	<4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com> <4408C6EC74CC3D42824FD68FDA8E8F710125F7F2@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125F7F2@306900ANEX2.global.avaya.com>
Content-Type: multipart/alternative; boundary="------------090207090603030402060609"
Cc: xcon@ietf.org
Subject: Re: [XCON] I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 15:33:20 -0000

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

Exactly. I modified the schema like we did for all other messages, 
namely the type "extended-request-message-type" extends the type 
"request-message-type" and contains the "extended-request", which is in 
turn of type "extended-request-type". Furthermore, inside the 
definitions of  both "extended-request-type" and 
"extended-response-type" we put an (optional) element called 
"extensionName". The modified schema now looks like the following:

*********************************************************************
<!-- CCMP request extensions -->
<xs:complexType name="ccmp-extended-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
<xs:sequence>
<xs:element ref="extendedRequest"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>

<xs:element name="extendedRequest" type="extendedRequestType"/>

<xs:complexType name="extendedRequestType">
<xs:sequence>
<xs:element name="extensionName" type="xs:string" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"
                            maxOccurs="unbounded" />
</xs:sequence>
</xs:complexType>
*********************************************************************

Cheers,

Simon


Il 01/06/2010 17.50, Duddy, Sean (Sean) ha scritto:
> Hi Simon,
>     The ccmp request extensions(see below) are generating a Unique 
> Particle Attribution violation. This is happening because 
> ccmp-request-message-type has an any also...
> Maybe these extensions need a defined element which basically holds an 
> any...
> <!-- CCMP request extensions... -->
> <xs:complexType name="ccmp-extended-request-message-type">
> <xs:complexContent>
> <xs:extension base="tns:ccmp-request-message-type">
> <xs:sequence>
> <xs:any namespace="##other" processContents="lax" minOccurs="0"
>                           maxOccurs="unbounded" />
> </xs:sequence>
> </xs:extension>
> </xs:complexContent>
> </xs:complexType>
> <!-- CCMP response extensions... -->
> <xs:complexType name="ccmp-extended-response-message-type">
> <xs:complexContent>
> <xs:extension base="tns:ccmp-response-message-type">
> <xs:sequence>
> <xs:any namespace="##other" processContents="lax" minOccurs="0"
>                           maxOccurs="unbounded" />
> </xs:sequence>
> </xs:extension>
> </xs:complexContent>
> </xs:complexType>
>
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>    

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



--------------090207090603030402060609
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Exactly. I modified the schema like we did for all other messages,
namely the type "extended-request-message-type" extends the type
"request-message-type" and contains the "extended-request", which is in
turn of type "extended-request-type". Furthermore, inside the
definitions of&nbsp; both "extended-request-type" and
"extended-response-type" we put an (optional) element called
"extensionName". The modified schema now looks like the following:<br>
<br>
*********************************************************************<br>
&lt;!-- CCMP request extensions --&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xs:complexType name="ccmp-extended-request-message-type"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:complexContent&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:extension
base="tns:ccmp-request-message-type"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&lt;xs:element
ref="extendedRequest"/&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;/xs:extension&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:complexContent&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;/xs:complexType&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;xs:element
name="extendedRequest" type="extendedRequestType"/&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;xs:complexType
name="extendedRequestType"&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;xs:element name="extensionName"
type="xs:string" minOccurs="0"/&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
&lt;xs:any namespace="##other" processContents="lax"
minOccurs="0"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
maxOccurs="unbounded" /&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;/xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;/xs:complexType&gt; <br>
*********************************************************************<br>
<br>
Cheers,<br>
<br>
Simon<br>
<br>
<br>
Il 01/06/2010 17.50, Duddy, Sean (Sean) ha scritto:
<blockquote
 cite="mid:4408C6EC74CC3D42824FD68FDA8E8F710125F7F2@306900ANEX2.global.avaya.com"
 type="cite">
  <title></title>
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta content="MSHTML 6.00.2900.3676" name="GENERATOR">
  <div dir="ltr" align="left"><span class="007165215-01062010"><font
 face="Arial"><font color="#0000ff"><font size="2">H<span
 class="007165215-01062010">i Simon,</span></font></font></font></span></div>
  <div dir="ltr" align="left"><span class="007165215-01062010"><font
 face="Arial"><font color="#0000ff"><font size="2"><span
 class="007165215-01062010">&nbsp;&nbsp;&nbsp; The ccmp request extensions(see
below)&nbsp;are generating a Unique Particle Attribution violation. This is
happening because ccmp-request-message-type has an any also...</span></font></font></font></span></div>
  <div dir="ltr" align="left"><span class="007165215-01062010"><font
 face="Arial"><font color="#0000ff"><font size="2"><span
 class="007165215-01062010">Maybe these extensions need a defined
element which basically holds an any...</span></font></font></font></span></div>
  <div dir="ltr" align="left"><span class="007165215-01062010"><font
 face="Arial"><font color="#0000ff"><font size="2"><span
 class="007165215-01062010"></span></font></font></font></span>&nbsp;</div>
  <div dir="ltr" align="left"><span class="007165215-01062010"><font
 face="Arial"><font color="#0000ff"><font size="2"><span
 class="007165215-01062010"></span></font></font></font></span>&nbsp;</div>
  <div dir="ltr" align="left"><span class="007165215-01062010"><font
 face="Arial"><font color="#0000ff"><font size="2"><span
 class="007165215-01062010">&nbsp;&lt;!-- CCMP request extensions... --&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:complexType name="ccmp-extended-request-message-type"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:complexContent&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:extension
base="tns:ccmp-request-message-type"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:any namespace="##other"
processContents="lax" minOccurs="0"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; maxOccurs="unbounded" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:extension&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:complexContent&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:complexType&gt;</span></font></font></font></span></div>
  <div>&nbsp;</div>
  <div dir="ltr" align="left"><span class="007165215-01062010"><font
 face="Arial"><font color="#0000ff"><font size="2"><span
 class="007165215-01062010">&nbsp; &lt;!-- CCMP response extensions... --&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:complexType
name="ccmp-extended-response-message-type"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:complexContent&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:extension
base="tns:ccmp-response-message-type"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:any namespace="##other"
processContents="lax" minOccurs="0"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; maxOccurs="unbounded" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:extension&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:complexContent&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:complexType&gt;</span></font></font></font></span></div>
  <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
XCON mailing list
<a class="moz-txt-link-abbreviated" href="mailto:XCON@ietf.org">XCON@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/xcon">https://www.ietf.org/mailman/listinfo/xcon</a>
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
                            _\\|//_
                            ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    Simon Pietro Romano
              Universita' di Napoli Federico II
                 Computer Science Department 
        Phone: +39 081 7683823 -- Fax: +39 081 7684219
                e-mail: <a class="moz-txt-link-abbreviated" href="mailto:spromano@unina.it">spromano@unina.it</a>
          <a class="moz-txt-link-freetext" href="http://www.comics.unina.it/simonpietro.romano">http://www.comics.unina.it/simonpietro.romano</a>

    &lt;&lt;Molti mi dicono che lo scoraggiamento &egrave; l'alibi degli 
   idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. Magritte.
                         oooO
   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                          \ (    (   )
                           \_)    ) /
                                 (_/

</pre>
</body>
</html>

--------------090207090603030402060609--

From spromano@unina.it  Thu Jun  3 08:35:55 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4A5B28C148 for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 08:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.032
X-Spam-Level: **
X-Spam-Status: No, score=2.032 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mrlq8eoIJiIy for <xcon@core3.amsl.com>; Thu,  3 Jun 2010 08:35:50 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id 75BC33A69D6 for <xcon@ietf.org>; Thu,  3 Jun 2010 08:35:42 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.0/8.14.0) with ESMTP id o53FYPiB025678 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 3 Jun 2010 17:34:26 +0200
Message-ID: <4C07CB81.9090502@unina.it>
Date: Thu, 03 Jun 2010 17:34:25 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Duddy, Sean (Sean)" <duddy@avaya.com>
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com><20100426201045.8x0hgw8rkkw488cs@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com>	<4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com> <4408C6EC74CC3D42824FD68FDA8E8F710125F8A8@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125F8A8@306900ANEX2.global.avaya.com>
Content-Type: multipart/alternative; boundary="------------060008070206000405030103"
Cc: xcon@ietf.org
Subject: Re: [XCON] I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 15:35:55 -0000
X-List-Received-Date: Thu, 03 Jun 2010 15:35:55 -0000

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

Hi again,

> Hi Simon,
> I am wondering what is the most appropriate error code when a user 
> cannot be authenticated by the ccmp server? i.e. invalid user name or 
> password.
> Around this area, we have the following error code defined:-
> 424 Authentication Required: User's authentication information missing 
> in a request to perform the requested operation. "subject" parameter 
> needed in the request.
> So we need another code like 'INVALID AUTHENTICATION' or we simply 
> change 424 to something like:-
> 424 Invalid Authentication : User's authentication information is 
> missing or invalid.
> I prefer just having the one code i.e. renaming 424.

I totally agree. If no one else objects, I'll go for the "just one code" 
option and change the specs accordingly.

Simon


-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



--------------060008070206000405030103
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi again,<br>
<br>
<blockquote
 cite="mid:4408C6EC74CC3D42824FD68FDA8E8F710125F8A8@306900ANEX2.global.avaya.com"
 type="cite">
  <title></title>
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta content="MSHTML 6.00.2900.3676" name="GENERATOR">
  <div><span class="740125211-02062010"><font color="#0000ff"
 face="Arial" size="2">Hi Simon,</font></span></div>
  <div><span class="740125211-02062010">&nbsp;&nbsp;&nbsp; <font face="Arial"><font
 color="#0000ff" size="2">I am wondering what is the most appropriate
error code when a user cannot be authenticated by the ccmp server? i.e.
invalid user name or password.</font></font></span></div>
  <div><span class="740125211-02062010"></span>&nbsp;</div>
  <div><span class="740125211-02062010"><font color="#0000ff"
 face="Arial" size="2">Around this area, we have the following error
code defined:-</font></span></div>
  <div><span class="740125211-02062010">424 Authentication Required:
User's authentication information missing in a request to perform the
requested operation. "subject" parameter needed in the request. </span></div>
  <div><span class="740125211-02062010"></span>&nbsp;</div>
  <div><span class="740125211-02062010"><font color="#0000ff"
 face="Arial" size="2">So we need another code like 'INVALID
AUTHENTICATION' or we simply change 424 to something like:-</font></span></div>
  <div><span class="740125211-02062010"></span>&nbsp;</div>
  <div><span class="740125211-02062010">
  <div><span class="740125211-02062010">424 Invalid Authentication :
User's authentication information is missing or invalid.</span></div>
  <div><span class="740125211-02062010"></span>&nbsp;</div>
  <div><span class="740125211-02062010"><font color="#0000ff"
 face="Arial" size="2">I prefer just having the one code i.e. renaming
424.</font></span></div>
  </span></div>
</blockquote>
<br>
I totally agree. If no one else objects, I'll go for the "just one
code" option and change the specs accordingly.<br>
<br>
Simon<br>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
                            _\\|//_
                            ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    Simon Pietro Romano
              Universita' di Napoli Federico II
                 Computer Science Department 
        Phone: +39 081 7683823 -- Fax: +39 081 7684219
                e-mail: <a class="moz-txt-link-abbreviated" href="mailto:spromano@unina.it">spromano@unina.it</a>
          <a class="moz-txt-link-freetext" href="http://www.comics.unina.it/simonpietro.romano">http://www.comics.unina.it/simonpietro.romano</a>

    &lt;&lt;Molti mi dicono che lo scoraggiamento &egrave; l'alibi degli 
   idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. Magritte.
                         oooO
   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                          \ (    (   )
                           \_)    ) /
                                 (_/

</pre>
</body>
</html>

--------------060008070206000405030103--

From duddy@avaya.com  Fri Jun  4 07:21:13 2010
Return-Path: <duddy@avaya.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCF023A699A for <xcon@core3.amsl.com>; Fri,  4 Jun 2010 07:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.164
X-Spam-Level: 
X-Spam-Status: No, score=-0.164 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5yvVvLj+X2Im for <xcon@core3.amsl.com>; Fri,  4 Jun 2010 07:21:09 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 3513D3A6829 for <xcon@ietf.org>; Fri,  4 Jun 2010 07:21:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,361,1272859200";  d="scan'208,217";a="191921542"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 Jun 2010 10:20:51 -0400
X-IronPort-AV: E=Sophos;i="4.53,361,1272859200";  d="scan'208,217";a="480874149"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.153]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Jun 2010 10:20:49 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB03F1.1447C553"
Date: Fri, 4 Jun 2010 15:20:27 +0100
Message-ID: <4408C6EC74CC3D42824FD68FDA8E8F710125FC0A@306900ANEX2.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-ietf-xcon-ccmp-07.txt
Thread-Index: Acrla81R5loMyOpgQ+mWBS732veu/gAg/tigBrfkryAAM/dHwAAAa+tgAABgE8AAKehZwABpydQQ
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com><20100426201045.8x0hgw8rkkw488cs@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com> <4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com>
From: "Duddy, Sean (Sean)" <duddy@avaya.com>
To: <xcon@ietf.org>
Subject: [XCON] I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jun 2010 14:21:13 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB03F1.1447C553
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
    I see there is a inconsistency between the constraints on the
request and response, see the highlighted item below:-
Is there a use case where a request would not have a confUserID?
=20
=20
   <xs:complexType abstract=3D"true"
                  name=3D"ccmp-request-message-type">
      <xs:sequence>
          <xs:element name=3D"subject" type=3D"subject-type"
                      minOccurs=3D"0" maxOccurs=3D"1" />
          <xs:element name=3D"confUserID" type=3D"xs:string"
                      minOccurs=3D"0" maxOccurs=3D"1" />
          <xs:element name=3D"confObjID" type=3D"xs:string"
                      minOccurs=3D"0" maxOccurs=3D"1" />
          <xs:element name=3D"operation" type=3D"operationType"
                      minOccurs=3D"0" maxOccurs=3D"1" />
          <xs:element name=3D"conference-password" type=3D"xs:string"
                      minOccurs=3D"0" maxOccurs=3D"1" />
         <xs:any namespace=3D"##other" processContents=3D"lax"
                 minOccurs=3D"0" maxOccurs=3D"unbounded"/>
     </xs:sequence>
     <xs:anyAttribute namespace=3D"##any" processContents=3D"lax"/>
</xs:complexType>=20
=20
=20
<xs:complexType abstract=3D"true" name=3D"ccmp-response-message-type">
      <xs:sequence>
          <xs:element name=3D"confUserID" type=3D"xs:string"
                      minOccurs=3D"1" maxOccurs=3D"1" />
          <xs:element name=3D"confObjID" type=3D"xs:string"
                      minOccurs=3D"0" maxOccurs=3D"1" />
          <xs:element name=3D"operation" minOccurs=3D"0"
                      maxOccurs=3D"1" />
          <xs:element ref=3D"response-code" minOccurs=3D"1"
                      maxOccurs=3D"1" />
          <xs:element name=3D"response-string" type=3D"xs:string"
                      minOccurs=3D"0" maxOccurs=3D"1" />
          <xs:element name=3D"version" type=3D"xs:positiveInteger"
                      minOccurs=3D"0" maxOccurs=3D"1" />
          <xs:any namespace=3D"##other" processContents=3D"lax"
                      minOccurs=3D"0" maxOccurs=3D"unbounded"/>
      </xs:sequence>
      <xs:anyAttribute namespace=3D"##any" processContents=3D"lax"/>
  </xs:complexType>=20

------_=_NextPart_001_01CB03F1.1447C553
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3676" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010>Hi,</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010>&nbsp;&nbsp;&nbsp;&nbsp;I see there is a =
inconsistency=20
between the constraints on the request and response, see the <FONT=20
color=3D#ff0000>highlighted</FONT> item =
below:-</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010>Is there a use case where a request would not =
have a=20
confUserID?</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010>&nbsp;</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010>&nbsp;</SPAN>&nbsp; &lt;xs:complexType=20
abstract=3D"true"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
name=3D"ccmp-request-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

&lt;xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
&lt;xs:element name=3D"subject"=20
type=3D"subject-type"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
minOccurs=3D"0" maxOccurs=3D"1"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT=20
color=3D#ff0000>&lt;xs:element name=3D"confUserID"=20
type=3D"xs:string"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
minOccurs=3D"0" maxOccurs=3D"1"=20
/&gt;<BR></FONT>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:element name=3D"confObjID"=20
type=3D"xs:string"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
minOccurs=3D"0" maxOccurs=3D"1"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element=20
name=3D"operation"=20
type=3D"operationType"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
minOccurs=3D"0" maxOccurs=3D"1"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element=20
name=3D"conference-password"=20
type=3D"xs:string"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
minOccurs=3D"0" maxOccurs=3D"1"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:any=20
namespace=3D"##other"=20
processContents=3D"lax"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
minOccurs=3D"0" maxOccurs=3D"unbounded"/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp; =

&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:anyAttribute=20
namespace=3D"##any" =
processContents=3D"lax"/&gt;<BR>&lt;/xs:complexType&gt;<SPAN=20
class=3D814152114-04062010>&nbsp;</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D814152114-04062010>&lt;xs:complexType abstract=3D"true"=20
name=3D"ccmp-response-message-type"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
&lt;xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
&lt;xs:element name=3D"confUserID"=20
type=3D"xs:string"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
minOccurs=3D"1" maxOccurs=3D"1"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element=20
name=3D"confObjID"=20
type=3D"xs:string"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
minOccurs=3D"0" maxOccurs=3D"1"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element=20
name=3D"operation"=20
minOccurs=3D"0"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

maxOccurs=3D"1" =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:element ref=3D"response-code"=20
minOccurs=3D"1"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

maxOccurs=3D"1" =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;xs:element name=3D"response-string"=20
type=3D"xs:string"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
minOccurs=3D"0" maxOccurs=3D"1"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:element=20
name=3D"version"=20
type=3D"xs:positiveInteger"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
minOccurs=3D"0" maxOccurs=3D"1"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:any=20
namespace=3D"##other"=20
processContents=3D"lax"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
minOccurs=3D"0" =
maxOccurs=3D"unbounded"/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/xs:sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;xs:anyAttribute=20
namespace=3D"##any" processContents=3D"lax"/&gt;<BR>&nbsp;=20
&lt;/xs:complexType&gt;&nbsp;</SPAN></FONT></FONT></FONT></DIV></BODY></H=
TML>

------_=_NextPart_001_01CB03F1.1447C553--

From tom.kristensen@tandberg.com  Mon Jun  7 09:38:01 2010
Return-Path: <tom.kristensen@tandberg.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52B7328C62E for <xcon@core3.amsl.com>; Mon,  7 Jun 2010 09:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDEVp90q2RxW for <xcon@core3.amsl.com>; Mon,  7 Jun 2010 09:38:00 -0700 (PDT)
Received: from mail204.messagelabs.com (mail204.messagelabs.com [194.106.221.19]) by core3.amsl.com (Postfix) with SMTP id 895B13A7F06 for <xcon@ietf.org>; Mon,  7 Jun 2010 06:22:42 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tom.kristensen@tandberg.com
X-Msg-Ref: server-15.tower-204.messagelabs.com!1275916949!16427294!2
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [62.70.2.252]
Received: (qmail 17450 invoked from network); 7 Jun 2010 13:22:40 -0000
Received: from unknown (HELO OSLEXCP11.eu.tandberg.int) (62.70.2.252) by server-15.tower-204.messagelabs.com with SMTP; 7 Jun 2010 13:22:40 -0000
Received: from oslexcp2.eu.tandberg.int ([10.47.136.30]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Jun 2010 15:22:38 +0200
Received: from 10.47.13.171 ([10.47.13.171]) by oslexcp2.eu.tandberg.int ([10.47.136.30]) with Microsoft Exchange Server HTTP-DAV ;  Mon,  7 Jun 2010 13:22:38 +0000
Received: from TKristensenT500 by oslexcp2.eu.tandberg.int; 07 Jun 2010 15:22:38 +0200
From: Tom Kristensen <tom.kristensen@tandberg.com>
To: xcon@ietf.org
In-Reply-To: <1273653780.2694.11.camel@localhost>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Organization: TANDBERG R&D
Date: Mon, 07 Jun 2010 15:22:38 +0200
Message-ID: <1275916958.17477.9.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) 
X-OriginalArrivalTime: 07 Jun 2010 13:22:38.0950 (UTC) FILETIME=[80415860:01CB0644]
Cc: Alan Johnston <alan.b.johnston@gmail.com>, Mark Thompson <mark.thompson@tandberg.com>, xcon-chairs@tools.ietf.org
Subject: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2010 16:38:01 -0000

The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted early in
March. No comments received since.

We'd like guidance on the next steps. First we ask for adoption as WG
item. Next step would include the merging process with bis versions of
RFC 4582 and RFC 4583.=20

We'd like to point out that interested parties for this work indeed
exist.

(For the record: Questions was sent to XCON chairs in April and May. See
below. No response given. Therefore, this request on the list.)

-- Tom

On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> Chairs,
>=20
> Any thoughts or decision on this matter?
>=20
> Cheers,
> -- Tom
>=20
> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > XCON chairs,
> >=20
> > We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March - well in
> > advance of IETF-77.=20
> >    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> >=20
> > No comments received. Neither on XCON WG list, nor directly to the
> > authors. Therefore, we ask for adoption of this draft as an XCON WG
> > item.
> >=20
> > -- Tom
>=20


From alan.b.johnston@gmail.com  Tue Jun  8 09:43:42 2010
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19CF13A679F for <xcon@core3.amsl.com>; Tue,  8 Jun 2010 09:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 93Y10r5nitZn for <xcon@core3.amsl.com>; Tue,  8 Jun 2010 09:43:41 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id EB4ED3A69DB for <xcon@ietf.org>; Tue,  8 Jun 2010 09:43:39 -0700 (PDT)
Received: by pvf33 with SMTP id 33so2342625pvf.31 for <xcon@ietf.org>; Tue, 08 Jun 2010 09:43:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=MvM4MZPGuv66T9aAzYh8m0dP7eXovsC7Q19GuoygKHM=; b=pDLCvdahJROn8rsjvji+AA78hQ3KvKC4bkw4Vx9T3roQEqdoc3TGrgJiftkcv2AlDp Tto3N0aKU9Adlyo5pTh+MrnljrN6cvg1T8KklVIbsmd2E3iy5VQyaTTLU/vrqq2q0Ojk /bQ4JgbxFbcNxW46X6CJCHveLeRpDW0npWzIQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=M0KwUhcCuOQkXPyYnEkFUVxHuaaHUdt894pc2uv2c/z1N1oSUf/A1R8LuHJHpqKRmC HhucI2/QoKYgMExGI4hJAXuuImGbQVyLrpuIxvMS1rGXJyXmrp8bitc4QjY8fG4OwwiE a1UsY/a1B9lIAqZ978S2UoJcy685BREFWcd68=
Received: by 10.224.64.227 with SMTP id f35mr1369180qai.310.1276015417860; Tue, 08 Jun 2010 09:43:37 -0700 (PDT)
Received: from AlanLaptop.sipserver.homeip.net (24-107-197-239.dhcp.stls.mo.charter.com [24.107.197.239]) by mx.google.com with ESMTPS id v37sm4888168qce.0.2010.06.08.09.43.35 (version=SSLv3 cipher=RC4-MD5); Tue, 08 Jun 2010 09:43:36 -0700 (PDT)
Message-ID: <4C0E7332.6080402@gmail.com>
Date: Tue, 08 Jun 2010 11:43:30 -0500
From: Alan Johnston <alan.b.johnston@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Tom Kristensen <tom.kristensen@tandberg.com>
References: <1271757479.26184.8.camel@localhost>	 <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost>
In-Reply-To: <1275916958.17477.9.camel@localhost>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Mark Thompson <mark.thompson@tandberg.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 16:43:42 -0000

Tom,

Apologies for the delay in replying.  As you know, the working group is
in the process of completing its final milestones.  Publication requests
will be issued in the next few days for the data model, CCMP, and the
Examples drafts.

Taking on any new milestones for the working group would require:
1. Strong support and interest from working group participants
2. Approval of our ADs.

I haven't seen evidence of either of these at this stage.

A possible option is to take this work to DISPATCH, get an indication of
interests, and get feedback on the best way to move this work forward.

- Alan -
co-chair XCON


On 6/7/10 8:22 AM, Tom Kristensen wrote:
> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted early in
> March. No comments received since.
> 
> We'd like guidance on the next steps. First we ask for adoption as WG
> item. Next step would include the merging process with bis versions of
> RFC 4582 and RFC 4583. 
> 
> We'd like to point out that interested parties for this work indeed
> exist.
> 
> (For the record: Questions was sent to XCON chairs in April and May. See
> below. No response given. Therefore, this request on the list.)
> 
> -- Tom
> 
> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>> Chairs,
>>
>> Any thoughts or decision on this matter?
>>
>> Cheers,
>> -- Tom
>>
>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>> XCON chairs,
>>>
>>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March - well in
>>> advance of IETF-77. 
>>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
>>>
>>> No comments received. Neither on XCON WG list, nor directly to the
>>> authors. Therefore, we ask for adoption of this draft as an XCON WG
>>> item.
>>>
>>> -- Tom
>>
> 
> 

From ron.even.tlv@gmail.com  Tue Jun  8 11:37:33 2010
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7A6F3A67C1 for <xcon@core3.amsl.com>; Tue,  8 Jun 2010 11:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upvAQ4w1L2gi for <xcon@core3.amsl.com>; Tue,  8 Jun 2010 11:37:32 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 5FB623A68F3 for <xcon@ietf.org>; Tue,  8 Jun 2010 11:37:32 -0700 (PDT)
Received: by wwc33 with SMTP id 33so829868wwc.31 for <xcon@ietf.org>; Tue, 08 Jun 2010 11:37:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=ednh2T2jDGYCowMLxD/9bBu79nqwIfZdeZVtiMNntJ4=; b=DgM+UyPoqnKwvgA5rdT6XHwq7LPn4cYb5WXsZDqAecswtzq8Qp8ft00r+UpqcB1YWE fURKhYlcwCMCDBJGgjm4z/Gibzce1zLwQxpoZDGoem7oSP8SEoHQOOmyyD2i3EuMqBug EbO5rqDparU7j+YukSEr/seRVG0rACjsO5tZI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=XIsEV/45+QTh0IaHPA1KH5kyxoYj5Uhi3w9Q5z7hLTozuomluATYdmiOnutEO1ZkOu afPVCUTiMXjUurMeBU7Pk1VIaS2gJl6sgJb5WkMeiST1xrFtfJl/K1z7tUGYfSwwUtA0 Ir5rb21D7bQcCrw9D1mUlNZm7w9j6FCU582Ew=
Received: by 10.227.134.84 with SMTP id i20mr243437wbt.52.1276022247406; Tue, 08 Jun 2010 11:37:27 -0700 (PDT)
Received: from windows8d787f9 ([109.65.51.207]) by mx.google.com with ESMTPS id y31sm48837792wby.4.2010.06.08.11.37.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 08 Jun 2010 11:37:26 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Alan Johnston'" <alan.b.johnston@gmail.com>, "'Tom Kristensen'" <tom.kristensen@tandberg.com>
References: <1271757479.26184.8.camel@localhost>		<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com>
In-Reply-To: <4C0E7332.6080402@gmail.com>
Date: Tue, 8 Jun 2010 21:35:05 +0300
Message-ID: <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsHKcuJcQZj32/pSbi+rrpFcwLuPQADqyTw
Content-Language: en-us
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 18:37:33 -0000

Hi Alan,
I support this work and think it is urgent to finish it.
I think that updating BFCP with UDP support is very important. I would like
to mention that BFCP is being used in video conferencing application and
since the implementers encountered problems with TCP they use a fall back to
UDP.
We discussed this work in previous IETF meeting and Gonzalo as far as I
remember suggested to add it to a BFCP bis draft.

Thanks
Roni Even

> -----Original Message-----
> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
> Alan Johnston
> Sent: Tuesday, June 08, 2010 7:44 PM
> To: Tom Kristensen
> Cc: Mark Thompson; xcon@ietf.org
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> 
> Tom,
> 
> Apologies for the delay in replying.  As you know, the working group is
> in the process of completing its final milestones.  Publication
> requests
> will be issued in the next few days for the data model, CCMP, and the
> Examples drafts.
> 
> Taking on any new milestones for the working group would require:
> 1. Strong support and interest from working group participants
> 2. Approval of our ADs.
> 
> I haven't seen evidence of either of these at this stage.
> 
> A possible option is to take this work to DISPATCH, get an indication
> of
> interests, and get feedback on the best way to move this work forward.
> 
> - Alan -
> co-chair XCON
> 
> 
> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted early in
> > March. No comments received since.
> >
> > We'd like guidance on the next steps. First we ask for adoption as WG
> > item. Next step would include the merging process with bis versions
> of
> > RFC 4582 and RFC 4583.
> >
> > We'd like to point out that interested parties for this work indeed
> > exist.
> >
> > (For the record: Questions was sent to XCON chairs in April and May.
> See
> > below. No response given. Therefore, this request on the list.)
> >
> > -- Tom
> >
> > On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> >> Chairs,
> >>
> >> Any thoughts or decision on this matter?
> >>
> >> Cheers,
> >> -- Tom
> >>
> >> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> >>> XCON chairs,
> >>>
> >>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March -
> well in
> >>> advance of IETF-77.
> >>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> >>>
> >>> No comments received. Neither on XCON WG list, nor directly to the
> >>> authors. Therefore, we ask for adoption of this draft as an XCON WG
> >>> item.
> >>>
> >>> -- Tom
> >>
> >
> >
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From patrick.luthi@tandberg.com  Wed Jun  9 00:11:15 2010
Return-Path: <patrick.luthi@tandberg.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B4C33A68EB for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 00:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.74
X-Spam-Level: 
X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id olrWym5Zor7f for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 00:11:14 -0700 (PDT)
Received: from mail205.messagelabs.com (mail205.messagelabs.com [85.158.140.179]) by core3.amsl.com (Postfix) with SMTP id 08C073A67DB for <xcon@ietf.org>; Wed,  9 Jun 2010 00:11:13 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: patrick.luthi@tandberg.com
X-Msg-Ref: server-11.tower-205.messagelabs.com!1276067474!7871716!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [62.70.2.252]
Received: (qmail 8380 invoked from network); 9 Jun 2010 07:11:14 -0000
Received: from unknown (HELO OSLEXCP11.eu.tandberg.int) (62.70.2.252) by server-11.tower-205.messagelabs.com with SMTP; 9 Jun 2010 07:11:14 -0000
Received: from oslexcp2.eu.tandberg.int ([10.47.136.30]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Wed, 9 Jun 2010 09:11:14 +0200
Received: from suisse127.tandberg.com ([10.0.6.167]) by oslexcp2.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 9 Jun 2010 09:11:13 +0200
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 09 Jun 2010 09:06:50 +0200
To: "Roni Even" <ron.even.tlv@gmail.com>, "'Alan Johnston'" <alan.b.johnston@gmail.com>, "'Tom Kristensen'" <tom.kristensen@tandberg.com>
From: Patrick Luthi <patrick.luthi@tandberg.com>
In-Reply-To: <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <OSLEXCP2SZ3Zs3Mpw6y00000702@oslexcp2.eu.tandberg.int>
X-OriginalArrivalTime: 09 Jun 2010 07:11:13.0735 (UTC) FILETIME=[F20EE570:01CB07A2]
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 07:11:15 -0000

Hi Alan,

I support this work too. Videotelephony and videoconferencing 
manufacturers quickly need the solution that this draft is addressing!

I was in the room the last time we discussed this in XCON and my 
understanding was that there was support for the work to move 
forward. I also remember Gonzalo suggesting the addition to a BFCP-bis draft.

Regards,

Patrick

At 20:35 08/06/2010, Roni Even wrote:
>Hi Alan,
>I support this work and think it is urgent to finish it.
>I think that updating BFCP with UDP support is very important. I would like
>to mention that BFCP is being used in video conferencing application and
>since the implementers encountered problems with TCP they use a fall back to
>UDP.
>We discussed this work in previous IETF meeting and Gonzalo as far as I
>remember suggested to add it to a BFCP bis draft.
>
>Thanks
>Roni Even
>
> > -----Original Message-----
> > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
> > Alan Johnston
> > Sent: Tuesday, June 08, 2010 7:44 PM
> > To: Tom Kristensen
> > Cc: Mark Thompson; xcon@ietf.org
> > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >
> > Tom,
> >
> > Apologies for the delay in replying.  As you know, the working group is
> > in the process of completing its final milestones.  Publication
> > requests
> > will be issued in the next few days for the data model, CCMP, and the
> > Examples drafts.
> >
> > Taking on any new milestones for the working group would require:
> > 1. Strong support and interest from working group participants
> > 2. Approval of our ADs.
> >
> > I haven't seen evidence of either of these at this stage.
> >
> > A possible option is to take this work to DISPATCH, get an indication
> > of
> > interests, and get feedback on the best way to move this work forward.
> >
> > - Alan -
> > co-chair XCON
> >
> >
> > On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > > The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted early in
> > > March. No comments received since.
> > >
> > > We'd like guidance on the next steps. First we ask for adoption as WG
> > > item. Next step would include the merging process with bis versions
> > of
> > > RFC 4582 and RFC 4583.
> > >
> > > We'd like to point out that interested parties for this work indeed
> > > exist.
> > >
> > > (For the record: Questions was sent to XCON chairs in April and May.
> > See
> > > below. No response given. Therefore, this request on the list.)
> > >
> > > -- Tom
> > >
> > > On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > >> Chairs,
> > >>
> > >> Any thoughts or decision on this matter?
> > >>
> > >> Cheers,
> > >> -- Tom
> > >>
> > >> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > >>> XCON chairs,
> > >>>
> > >>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March -
> > well in
> > >>> advance of IETF-77.
> > >>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> > >>>
> > >>> No comments received. Neither on XCON WG list, nor directly to the
> > >>> authors. Therefore, we ask for adoption of this draft as an XCON WG
> > >>> item.
> > >>>
> > >>> -- Tom
> > >>
> > >
> > >
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
>
>_______________________________________________
>XCON mailing list
>XCON@ietf.org
>https://www.ietf.org/mailman/listinfo/xcon



From keith.drage@alcatel-lucent.com  Wed Jun  9 04:21:02 2010
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4813328C0D0 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 04:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rAkN455Tcdtt for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 04:21:01 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id ED51E3A68E7 for <xcon@ietf.org>; Wed,  9 Jun 2010 04:21:00 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o59BK9tA021868 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 9 Jun 2010 13:20:56 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 9 Jun 2010 13:20:39 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Roni Even <ron.even.tlv@gmail.com>, "'Alan Johnston'" <alan.b.johnston@gmail.com>, "'Tom Kristensen'" <tom.kristensen@tandberg.com>
Date: Wed, 9 Jun 2010 13:20:39 +0200
Thread-Topic: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
Thread-Index: AcsHKcuJcQZj32/pSbi+rrpFcwLuPQADqyTwACKbIsA=
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>
In-Reply-To: <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.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.64 on 155.132.188.83
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 11:21:02 -0000

We made an explicit decision in the original draft that UDP was not require=
d, not that we would do it later. That as far as I am concerned represents =
the current status of consensus.

This was done on the basis that we had all seen how UDP support had complic=
ated SIP, and we did not want to repeat that issue.

So this is not continuing the work. The status is an author draft which goe=
s against a WG consensus position.

I believe Georg Ott also expressed some concerns which I did not see answer=
ed on list at all.

regards

Keith=20

> -----Original Message-----
> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On=20
> Behalf Of Roni Even
> Sent: Tuesday, June 08, 2010 7:35 PM
> To: 'Alan Johnston'; 'Tom Kristensen'
> Cc: 'Mark Thompson'; xcon@ietf.org
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>=20
> Hi Alan,
> I support this work and think it is urgent to finish it.
> I think that updating BFCP with UDP support is very=20
> important. I would like to mention that BFCP is being used in=20
> video conferencing application and since the implementers=20
> encountered problems with TCP they use a fall back to UDP.
> We discussed this work in previous IETF meeting and Gonzalo=20
> as far as I remember suggested to add it to a BFCP bis draft.
>=20
> Thanks
> Roni Even
>=20
> > -----Original Message-----
> > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]=20
> On Behalf=20
> > Of Alan Johnston
> > Sent: Tuesday, June 08, 2010 7:44 PM
> > To: Tom Kristensen
> > Cc: Mark Thompson; xcon@ietf.org
> > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >=20
> > Tom,
> >=20
> > Apologies for the delay in replying.  As you know, the=20
> working group=20
> > is in the process of completing its final milestones.  Publication=20
> > requests will be issued in the next few days for the data=20
> model, CCMP,=20
> > and the Examples drafts.
> >=20
> > Taking on any new milestones for the working group would require:
> > 1. Strong support and interest from working group participants 2.=20
> > Approval of our ADs.
> >=20
> > I haven't seen evidence of either of these at this stage.
> >=20
> > A possible option is to take this work to DISPATCH, get an=20
> indication=20
> > of interests, and get feedback on the best way to move this work=20
> > forward.
> >=20
> > - Alan -
> > co-chair XCON
> >=20
> >=20
> > On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > > The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted=20
> early in=20
> > > March. No comments received since.
> > >
> > > We'd like guidance on the next steps. First we ask for=20
> adoption as=20
> > > WG item. Next step would include the merging process with bis=20
> > > versions
> > of
> > > RFC 4582 and RFC 4583.
> > >
> > > We'd like to point out that interested parties for this=20
> work indeed=20
> > > exist.
> > >
> > > (For the record: Questions was sent to XCON chairs in=20
> April and May.
> > See
> > > below. No response given. Therefore, this request on the list.)
> > >
> > > -- Tom
> > >
> > > On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > >> Chairs,
> > >>
> > >> Any thoughts or decision on this matter?
> > >>
> > >> Cheers,
> > >> -- Tom
> > >>
> > >> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > >>> XCON chairs,
> > >>>
> > >>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March -
> > well in
> > >>> advance of IETF-77.
> > >>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> > >>>
> > >>> No comments received. Neither on XCON WG list, nor=20
> directly to the=20
> > >>> authors. Therefore, we ask for adoption of this draft=20
> as an XCON=20
> > >>> WG item.
> > >>>
> > >>> -- Tom
> > >>
> > >
> > >
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
>=20
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
> =

From 2mkristensen@gmail.com  Wed Jun  9 04:38:01 2010
Return-Path: <2mkristensen@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A22E63A696E for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 04:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rt5dE6gLfQrN for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 04:37:59 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 1B0B228C0E6 for <xcon@ietf.org>; Wed,  9 Jun 2010 04:37:58 -0700 (PDT)
Received: by fxm13 with SMTP id 13so1413474fxm.31 for <xcon@ietf.org>; Wed, 09 Jun 2010 04:37:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bvlAMIN+2ZaEjb4RdScRfA3dZwsVOd+i+u7u8fKfZnU=; b=t/YqXmP8k+kYqwAyM1v2V0qmwwe7jsggnC4j2ENiXB+7tYVT1zE9MbO4bbDx8JAIsz pEkIOJ4T1MZboIHocRpfK93IA4DC7LB6xN7bQvS+bt6PAkvabidMLw68xdMO26Y6co34 WZTtuNg+oOgPUDisXkuurSIvpeuyzywrZcfE4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=V35auZfMK/S9fOMNCMqExnNmEs0pyjNdZMG8vW5eyA7p1HUtTpuHgkLeVaWUjQEemn Z4tPkJY6mLCHg4IowAlWgn5prT4TQm26VD7XhnDFkZcAtaYKH2d3vSn7LVJhd7R77o5C Mc7qlP7Qi9MDn4iP6nMJW9/IA6U9/YoQI700k=
MIME-Version: 1.0
Received: by 10.223.24.133 with SMTP id v5mr1176380fab.46.1276083476190; Wed,  09 Jun 2010 04:37:56 -0700 (PDT)
Received: by 10.223.119.205 with HTTP; Wed, 9 Jun 2010 04:37:56 -0700 (PDT)
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Wed, 9 Jun 2010 13:37:56 +0200
Message-ID: <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>
From: Tom Kristensen <2mkristensen@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Alan Johnston <alan.b.johnston@gmail.com>, Mark Thompson <mark.thompson@tandberg.com>, Tom Kristensen <tom.kristensen@tandberg.com>, "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 11:38:01 -0000

The UDP/BFCP draft has been presented and discussed in two or three
IETF XCON sessions. No objection to the work being carried on, just
that adoption as WG item was postponed until the draft was more
complete. (This has been delayed of various reasons, but the authors
believe the -02 version in question here should be ready for
adoption).

The "current status of consensus" might be valid for some, but
participants in the XCON sessions and the minutes of meeting show
progress away from that initial consensus.

I believe Ott's concerns are either dealt with or at least mentioned
in the draft. Arrest me if I'm wrong.

-- Tom

On 9 June 2010 13:20, DRAGE, Keith (Keith)
<keith.drage@alcatel-lucent.com> wrote:
> We made an explicit decision in the original draft that UDP was not requi=
red, not that we would do it later. That as far as I am concerned represent=
s the current status of consensus.
>
> This was done on the basis that we had all seen how UDP support had compl=
icated SIP, and we did not want to repeat that issue.
>
> So this is not continuing the work. The status is an author draft which g=
oes against a WG consensus position.
>
> I believe Georg Ott also expressed some concerns which I did not see answ=
ered on list at all.
>
> regards
>
> Keith
>
>> -----Original Message-----
>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
>> Behalf Of Roni Even
>> Sent: Tuesday, June 08, 2010 7:35 PM
>> To: 'Alan Johnston'; 'Tom Kristensen'
>> Cc: 'Mark Thompson'; xcon@ietf.org
>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>
>> Hi Alan,
>> I support this work and think it is urgent to finish it.
>> I think that updating BFCP with UDP support is very
>> important. I would like to mention that BFCP is being used in
>> video conferencing application and since the implementers
>> encountered problems with TCP they use a fall back to UDP.
>> We discussed this work in previous IETF meeting and Gonzalo
>> as far as I remember suggested to add it to a BFCP bis draft.
>>
>> Thanks
>> Roni Even
>>
>> > -----Original Message-----
>> > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>> On Behalf
>> > Of Alan Johnston
>> > Sent: Tuesday, June 08, 2010 7:44 PM
>> > To: Tom Kristensen
>> > Cc: Mark Thompson; xcon@ietf.org
>> > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>> >
>> > Tom,
>> >
>> > Apologies for the delay in replying. =A0As you know, the
>> working group
>> > is in the process of completing its final milestones. =A0Publication
>> > requests will be issued in the next few days for the data
>> model, CCMP,
>> > and the Examples drafts.
>> >
>> > Taking on any new milestones for the working group would require:
>> > 1. Strong support and interest from working group participants 2.
>> > Approval of our ADs.
>> >
>> > I haven't seen evidence of either of these at this stage.
>> >
>> > A possible option is to take this work to DISPATCH, get an
>> indication
>> > of interests, and get feedback on the best way to move this work
>> > forward.
>> >
>> > - Alan -
>> > co-chair XCON
>> >
>> >
>> > On 6/7/10 8:22 AM, Tom Kristensen wrote:
>> > > The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>> early in
>> > > March. No comments received since.
>> > >
>> > > We'd like guidance on the next steps. First we ask for
>> adoption as
>> > > WG item. Next step would include the merging process with bis
>> > > versions
>> > of
>> > > RFC 4582 and RFC 4583.
>> > >
>> > > We'd like to point out that interested parties for this
>> work indeed
>> > > exist.
>> > >
>> > > (For the record: Questions was sent to XCON chairs in
>> April and May.
>> > See
>> > > below. No response given. Therefore, this request on the list.)
>> > >
>> > > -- Tom
>> > >
>> > > On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>> > >> Chairs,
>> > >>
>> > >> Any thoughts or decision on this matter?
>> > >>
>> > >> Cheers,
>> > >> -- Tom
>> > >>
>> > >> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>> > >>> XCON chairs,
>> > >>>
>> > >>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March -
>> > well in
>> > >>> advance of IETF-77.
>> > >>> =A0 =A0http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
>> > >>>
>> > >>> No comments received. Neither on XCON WG list, nor
>> directly to the
>> > >>> authors. Therefore, we ask for adoption of this draft
>> as an XCON
>> > >>> WG item.
>> > >>>
>> > >>> -- Tom
>> > >>
>> > >
>> > >
>> > _______________________________________________
>> > XCON mailing list
>> > XCON@ietf.org
>> > https://www.ietf.org/mailman/listinfo/xcon
>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>



--=20
# TANDBERG R&D
## http://www.tandberg.com
### http://folk.uio.no/tomkri/

From aeh@db.org  Wed Jun  9 04:38:32 2010
Return-Path: <aeh@db.org>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CB6028C0F6 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 04:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aiyk2K0vBXl2 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 04:38:31 -0700 (PDT)
Received: from submit-tmp.sysedata.no (submit-tmp.sysedata.no [195.159.29.133]) by core3.amsl.com (Postfix) with ESMTP id 44C7C28C0F0 for <xcon@ietf.org>; Wed,  9 Jun 2010 04:38:31 -0700 (PDT)
Received: from [85.119.140.4] (helo=alfred-heggestads-macbook-pro.local) by submit-tmp.sysedata.no with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <aeh@db.org>) id 1OMJc6-0006s1-8P; Wed, 09 Jun 2010 13:38:30 +0200
Message-ID: <4C0F7D35.3070302@db.org>
Date: Wed, 09 Jun 2010 13:38:29 +0200
From: "Alfred E. Heggestad" <aeh@db.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Tom Kristensen <tom.kristensen@tandberg.com>
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost>
In-Reply-To: <1275916958.17477.9.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Alan Johnston <alan.b.johnston@gmail.com>, Mark Thompson <mark.thompson@tandberg.com>, xcon@ietf.org, xcon-chairs@tools.ietf.org
Subject: Re: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 11:38:32 -0000

Hi

I support this draft, and would like to see support for BFCP over UDP




Best regards,

Alfred E. Heggestad
Telio Telecom AS


On 6/7/10 3:22 PM, Tom Kristensen wrote:
> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted early in
> March. No comments received since.
>
> We'd like guidance on the next steps. First we ask for adoption as WG
> item. Next step would include the merging process with bis versions of
> RFC 4582 and RFC 4583.
>
> We'd like to point out that interested parties for this work indeed
> exist.
>
> (For the record: Questions was sent to XCON chairs in April and May. See
> below. No response given. Therefore, this request on the list.)
>
> -- Tom
>
> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>> Chairs,
>>
>> Any thoughts or decision on this matter?
>>
>> Cheers,
>> -- Tom
>>
>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>> XCON chairs,
>>>
>>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March - well in
>>> advance of IETF-77.
>>>     http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
>>>
>>> No comments received. Neither on XCON WG list, nor directly to the
>>> authors. Therefore, we ask for adoption of this draft as an XCON WG
>>> item.
>>>
>>> -- Tom
>>
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From rbarnes@bbn.com  Wed Jun  9 05:36:00 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A1C328C10E for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 05:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4nbb9YXb1tQN for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 05:35:58 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 7C4F928C10D for <xcon@ietf.org>; Wed,  9 Jun 2010 05:34:20 -0700 (PDT)
Received: from [192.1.255.204] (port=55782 helo=col-dhcp-192-1-255-204.bbn.com) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OMKU6-000JtG-Ay; Wed, 09 Jun 2010 08:34:18 -0400
Message-Id: <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: Tom Kristensen <2mkristensen@gmail.com>
In-Reply-To: <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 9 Jun 2010 08:34:16 -0400
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: Mark Thompson <mark.thompson@tandberg.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, Alan Johnston <alan.b.johnston@gmail.com>, Tom Kristensen <tom.kristensen@tandberg.com>, "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 12:36:00 -0000

Tom and others who are interested in this draft:

For those who are relatively new here: Could you summarize why you  
think this draft is needed?  What requirement does it meet that BFCP  
doesn't right now?

Thanks,
--Richard




On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:

> The UDP/BFCP draft has been presented and discussed in two or three
> IETF XCON sessions. No objection to the work being carried on, just
> that adoption as WG item was postponed until the draft was more
> complete. (This has been delayed of various reasons, but the authors
> believe the -02 version in question here should be ready for
> adoption).
>
> The "current status of consensus" might be valid for some, but
> participants in the XCON sessions and the minutes of meeting show
> progress away from that initial consensus.
>
> I believe Ott's concerns are either dealt with or at least mentioned
> in the draft. Arrest me if I'm wrong.
>
> -- Tom
>
> On 9 June 2010 13:20, DRAGE, Keith (Keith)
> <keith.drage@alcatel-lucent.com> wrote:
>> We made an explicit decision in the original draft that UDP was not  
>> required, not that we would do it later. That as far as I am  
>> concerned represents the current status of consensus.
>>
>> This was done on the basis that we had all seen how UDP support had  
>> complicated SIP, and we did not want to repeat that issue.
>>
>> So this is not continuing the work. The status is an author draft  
>> which goes against a WG consensus position.
>>
>> I believe Georg Ott also expressed some concerns which I did not  
>> see answered on list at all.
>>
>> regards
>>
>> Keith
>>
>>> -----Original Message-----
>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
>>> Behalf Of Roni Even
>>> Sent: Tuesday, June 08, 2010 7:35 PM
>>> To: 'Alan Johnston'; 'Tom Kristensen'
>>> Cc: 'Mark Thompson'; xcon@ietf.org
>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>
>>> Hi Alan,
>>> I support this work and think it is urgent to finish it.
>>> I think that updating BFCP with UDP support is very
>>> important. I would like to mention that BFCP is being used in
>>> video conferencing application and since the implementers
>>> encountered problems with TCP they use a fall back to UDP.
>>> We discussed this work in previous IETF meeting and Gonzalo
>>> as far as I remember suggested to add it to a BFCP bis draft.
>>>
>>> Thanks
>>> Roni Even
>>>
>>>> -----Original Message-----
>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>> On Behalf
>>>> Of Alan Johnston
>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>>>> To: Tom Kristensen
>>>> Cc: Mark Thompson; xcon@ietf.org
>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>
>>>> Tom,
>>>>
>>>> Apologies for the delay in replying.  As you know, the
>>> working group
>>>> is in the process of completing its final milestones.  Publication
>>>> requests will be issued in the next few days for the data
>>> model, CCMP,
>>>> and the Examples drafts.
>>>>
>>>> Taking on any new milestones for the working group would require:
>>>> 1. Strong support and interest from working group participants 2.
>>>> Approval of our ADs.
>>>>
>>>> I haven't seen evidence of either of these at this stage.
>>>>
>>>> A possible option is to take this work to DISPATCH, get an
>>> indication
>>>> of interests, and get feedback on the best way to move this work
>>>> forward.
>>>>
>>>> - Alan -
>>>> co-chair XCON
>>>>
>>>>
>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>>> early in
>>>>> March. No comments received since.
>>>>>
>>>>> We'd like guidance on the next steps. First we ask for
>>> adoption as
>>>>> WG item. Next step would include the merging process with bis
>>>>> versions
>>>> of
>>>>> RFC 4582 and RFC 4583.
>>>>>
>>>>> We'd like to point out that interested parties for this
>>> work indeed
>>>>> exist.
>>>>>
>>>>> (For the record: Questions was sent to XCON chairs in
>>> April and May.
>>>> See
>>>>> below. No response given. Therefore, this request on the list.)
>>>>>
>>>>> -- Tom
>>>>>
>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>>>>>> Chairs,
>>>>>>
>>>>>> Any thoughts or decision on this matter?
>>>>>>
>>>>>> Cheers,
>>>>>> -- Tom
>>>>>>
>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>>>>>> XCON chairs,
>>>>>>>
>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March -
>>>> well in
>>>>>>> advance of IETF-77.
>>>>>>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
>>>>>>>
>>>>>>> No comments received. Neither on XCON WG list, nor
>>> directly to the
>>>>>>> authors. Therefore, we ask for adoption of this draft
>>> as an XCON
>>>>>>> WG item.
>>>>>>>
>>>>>>> -- Tom
>>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> XCON mailing list
>>>> XCON@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>
>>> _______________________________________________
>>> XCON mailing list
>>> XCON@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xcon
>>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>>
>
>
>
> -- 
> # TANDBERG R&D
> ## http://www.tandberg.com
> ### http://folk.uio.no/tomkri/
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From ron.even.tlv@gmail.com  Wed Jun  9 05:42:00 2010
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 501EF28C0F8 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 05:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lTZ+5q7EnFve for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 05:41:58 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 75D9D3A685A for <xcon@ietf.org>; Wed,  9 Jun 2010 05:41:58 -0700 (PDT)
Received: by wyb32 with SMTP id 32so1603900wyb.31 for <xcon@ietf.org>; Wed, 09 Jun 2010 05:41:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=IlFbQalrQSV2dWYEC9doDxOWCWfCF/itrev++kcU1go=; b=hoZF/YZB/ocq5TIblPbCmQAXMM/MlNds9mt8gl/GNzHtDvIQ7L7c2KjPZcor87Xiqj DUXm3HmQwWzuY5ZMeHPdgSphzpB3N5g9w5RQWxn09Gi36kaqRsSY2xUFxO4/m55UPUnJ zHw43CE6ZU6/4NVSQaVs16uGiJyYZ4TLsn+iE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=R2vNPvJVD8rbMh3WOFH5S7a4V0rP025EliW2xGhVjMY78JbGwenR6vkNlXGcLjfFqk zIV/VMKu8zj2ncYFGCn3Zo4T3O/nltlx+rMck1hA71ss6fBuKGSo5dI/sXW+7qb1a029 A3OQmkPSmfdDBHFAK+ipPkHyMtiuIErvbXGq0=
Received: by 10.227.128.213 with SMTP id l21mr5630572wbs.133.1276087311940; Wed, 09 Jun 2010 05:41:51 -0700 (PDT)
Received: from windows8d787f9 (bzq-109-65-51-207.red.bezeqint.net [109.65.51.207]) by mx.google.com with ESMTPS id w27sm144218weq.22.2010.06.09.05.41.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 09 Jun 2010 05:41:51 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Richard L. Barnes'" <rbarnes@bbn.com>, "'Tom Kristensen'" <2mkristensen@gmail.com>
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>
In-Reply-To: <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>
Date: Wed, 9 Jun 2010 15:39:40 +0300
Message-ID: <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsH0Gk34nEfgBH9TEaUEMNu/gfFxAAACy+w
Content-Language: en-us
Cc: 'Tom Kristensen' <tom.kristensen@tandberg.com>, 'Mark Thompson' <mark.thompson@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>, "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 12:42:00 -0000

Richard,
The BFCP I used as a presentation token for video conferencing. What the
implementers found out that TCP does not work in real networks due to
Session border controllers not supporting TCP as used in BFCP. 
This is why in products they try to establish TCP connection and if fails
tries UDP.
The video conferencing vendors participating in the IMTC sip parity activity
group defined an interoperability profile that references this option
Roni Even 

> -----Original Message-----
> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
> Richard L. Barnes
> Sent: Wednesday, June 09, 2010 3:34 PM
> To: Tom Kristensen
> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom Kristensen;
> xcon@ietf.org
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> 
> Tom and others who are interested in this draft:
> 
> For those who are relatively new here: Could you summarize why you
> think this draft is needed?  What requirement does it meet that BFCP
> doesn't right now?
> 
> Thanks,
> --Richard
> 
> 
> 
> 
> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> 
> > The UDP/BFCP draft has been presented and discussed in two or three
> > IETF XCON sessions. No objection to the work being carried on, just
> > that adoption as WG item was postponed until the draft was more
> > complete. (This has been delayed of various reasons, but the authors
> > believe the -02 version in question here should be ready for
> > adoption).
> >
> > The "current status of consensus" might be valid for some, but
> > participants in the XCON sessions and the minutes of meeting show
> > progress away from that initial consensus.
> >
> > I believe Ott's concerns are either dealt with or at least mentioned
> > in the draft. Arrest me if I'm wrong.
> >
> > -- Tom
> >
> > On 9 June 2010 13:20, DRAGE, Keith (Keith)
> > <keith.drage@alcatel-lucent.com> wrote:
> >> We made an explicit decision in the original draft that UDP was not
> >> required, not that we would do it later. That as far as I am
> >> concerned represents the current status of consensus.
> >>
> >> This was done on the basis that we had all seen how UDP support had
> >> complicated SIP, and we did not want to repeat that issue.
> >>
> >> So this is not continuing the work. The status is an author draft
> >> which goes against a WG consensus position.
> >>
> >> I believe Georg Ott also expressed some concerns which I did not
> >> see answered on list at all.
> >>
> >> regards
> >>
> >> Keith
> >>
> >>> -----Original Message-----
> >>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
> >>> Behalf Of Roni Even
> >>> Sent: Tuesday, June 08, 2010 7:35 PM
> >>> To: 'Alan Johnston'; 'Tom Kristensen'
> >>> Cc: 'Mark Thompson'; xcon@ietf.org
> >>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >>>
> >>> Hi Alan,
> >>> I support this work and think it is urgent to finish it.
> >>> I think that updating BFCP with UDP support is very
> >>> important. I would like to mention that BFCP is being used in
> >>> video conferencing application and since the implementers
> >>> encountered problems with TCP they use a fall back to UDP.
> >>> We discussed this work in previous IETF meeting and Gonzalo
> >>> as far as I remember suggested to add it to a BFCP bis draft.
> >>>
> >>> Thanks
> >>> Roni Even
> >>>
> >>>> -----Original Message-----
> >>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >>> On Behalf
> >>>> Of Alan Johnston
> >>>> Sent: Tuesday, June 08, 2010 7:44 PM
> >>>> To: Tom Kristensen
> >>>> Cc: Mark Thompson; xcon@ietf.org
> >>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >>>>
> >>>> Tom,
> >>>>
> >>>> Apologies for the delay in replying.  As you know, the
> >>> working group
> >>>> is in the process of completing its final milestones.  Publication
> >>>> requests will be issued in the next few days for the data
> >>> model, CCMP,
> >>>> and the Examples drafts.
> >>>>
> >>>> Taking on any new milestones for the working group would require:
> >>>> 1. Strong support and interest from working group participants 2.
> >>>> Approval of our ADs.
> >>>>
> >>>> I haven't seen evidence of either of these at this stage.
> >>>>
> >>>> A possible option is to take this work to DISPATCH, get an
> >>> indication
> >>>> of interests, and get feedback on the best way to move this work
> >>>> forward.
> >>>>
> >>>> - Alan -
> >>>> co-chair XCON
> >>>>
> >>>>
> >>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> >>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> >>> early in
> >>>>> March. No comments received since.
> >>>>>
> >>>>> We'd like guidance on the next steps. First we ask for
> >>> adoption as
> >>>>> WG item. Next step would include the merging process with bis
> >>>>> versions
> >>>> of
> >>>>> RFC 4582 and RFC 4583.
> >>>>>
> >>>>> We'd like to point out that interested parties for this
> >>> work indeed
> >>>>> exist.
> >>>>>
> >>>>> (For the record: Questions was sent to XCON chairs in
> >>> April and May.
> >>>> See
> >>>>> below. No response given. Therefore, this request on the list.)
> >>>>>
> >>>>> -- Tom
> >>>>>
> >>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> >>>>>> Chairs,
> >>>>>>
> >>>>>> Any thoughts or decision on this matter?
> >>>>>>
> >>>>>> Cheers,
> >>>>>> -- Tom
> >>>>>>
> >>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> >>>>>>> XCON chairs,
> >>>>>>>
> >>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March -
> >>>> well in
> >>>>>>> advance of IETF-77.
> >>>>>>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> >>>>>>>
> >>>>>>> No comments received. Neither on XCON WG list, nor
> >>> directly to the
> >>>>>>> authors. Therefore, we ask for adoption of this draft
> >>> as an XCON
> >>>>>>> WG item.
> >>>>>>>
> >>>>>>> -- Tom
> >>>>>>
> >>>>>
> >>>>>
> >>>> _______________________________________________
> >>>> XCON mailing list
> >>>> XCON@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>
> >>> _______________________________________________
> >>> XCON mailing list
> >>> XCON@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/xcon
> >>>
> >> _______________________________________________
> >> XCON mailing list
> >> XCON@ietf.org
> >> https://www.ietf.org/mailman/listinfo/xcon
> >>
> >
> >
> >
> > --
> > # TANDBERG R&D
> > ## http://www.tandberg.com
> > ### http://folk.uio.no/tomkri/
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
> 
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From rbarnes@bbn.com  Wed Jun  9 05:51:34 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6177728C111 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 05:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id syk18igTjzsr for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 05:51:33 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id EC5233A68B9 for <xcon@ietf.org>; Wed,  9 Jun 2010 05:51:32 -0700 (PDT)
Received: from [192.1.255.204] (port=55981 helo=col-dhcp-192-1-255-204.bbn.com) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OMKkl-000K8Q-97; Wed, 09 Jun 2010 08:51:31 -0400
Message-Id: <40418C09-CBE0-4546-A07D-5331E40BFDA6@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: "Roni Even" <ron.even.tlv@gmail.com>
In-Reply-To: <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 9 Jun 2010 08:51:30 -0400
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>
X-Mailer: Apple Mail (2.936)
Cc: 'Tom Kristensen' <tom.kristensen@tandberg.com>, "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, xcon@ietf.org, 'Mark Thompson' <mark.thompson@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 12:51:34 -0000

Thanks for the quick reply, Roni.

What do you mean by "TCP as used in BFCP"?  Is the issue:
-- SBCs don't let any TCP through at all?
-- SBCs don't support the SDP options for BFCP? (thus don't open ports?)
-- SBCs are doing DPI and don't let through TCP traffic containing BFCP?
-- Something else?



On Jun 9, 2010, at 8:39 AM, Roni Even wrote:

> Richard,
> The BFCP I used as a presentation token for video conferencing. What  
> the
> implementers found out that TCP does not work in real networks due to
> Session border controllers not supporting TCP as used in BFCP.
> This is why in products they try to establish TCP connection and if  
> fails
> tries UDP.
> The video conferencing vendors participating in the IMTC sip parity  
> activity
> group defined an interoperability profile that references this option
> Roni Even
>
>> -----Original Message-----
>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On  
>> Behalf Of
>> Richard L. Barnes
>> Sent: Wednesday, June 09, 2010 3:34 PM
>> To: Tom Kristensen
>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom  
>> Kristensen;
>> xcon@ietf.org
>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>
>> Tom and others who are interested in this draft:
>>
>> For those who are relatively new here: Could you summarize why you
>> think this draft is needed?  What requirement does it meet that BFCP
>> doesn't right now?
>>
>> Thanks,
>> --Richard
>>
>>
>>
>>
>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
>>
>>> The UDP/BFCP draft has been presented and discussed in two or three
>>> IETF XCON sessions. No objection to the work being carried on, just
>>> that adoption as WG item was postponed until the draft was more
>>> complete. (This has been delayed of various reasons, but the authors
>>> believe the -02 version in question here should be ready for
>>> adoption).
>>>
>>> The "current status of consensus" might be valid for some, but
>>> participants in the XCON sessions and the minutes of meeting show
>>> progress away from that initial consensus.
>>>
>>> I believe Ott's concerns are either dealt with or at least mentioned
>>> in the draft. Arrest me if I'm wrong.
>>>
>>> -- Tom
>>>
>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
>>> <keith.drage@alcatel-lucent.com> wrote:
>>>> We made an explicit decision in the original draft that UDP was not
>>>> required, not that we would do it later. That as far as I am
>>>> concerned represents the current status of consensus.
>>>>
>>>> This was done on the basis that we had all seen how UDP support had
>>>> complicated SIP, and we did not want to repeat that issue.
>>>>
>>>> So this is not continuing the work. The status is an author draft
>>>> which goes against a WG consensus position.
>>>>
>>>> I believe Georg Ott also expressed some concerns which I did not
>>>> see answered on list at all.
>>>>
>>>> regards
>>>>
>>>> Keith
>>>>
>>>>> -----Original Message-----
>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
>>>>> Behalf Of Roni Even
>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>>
>>>>> Hi Alan,
>>>>> I support this work and think it is urgent to finish it.
>>>>> I think that updating BFCP with UDP support is very
>>>>> important. I would like to mention that BFCP is being used in
>>>>> video conferencing application and since the implementers
>>>>> encountered problems with TCP they use a fall back to UDP.
>>>>> We discussed this work in previous IETF meeting and Gonzalo
>>>>> as far as I remember suggested to add it to a BFCP bis draft.
>>>>>
>>>>> Thanks
>>>>> Roni Even
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>> On Behalf
>>>>>> Of Alan Johnston
>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>>>>>> To: Tom Kristensen
>>>>>> Cc: Mark Thompson; xcon@ietf.org
>>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp- 
>>>>>> udp-02
>>>>>>
>>>>>> Tom,
>>>>>>
>>>>>> Apologies for the delay in replying.  As you know, the
>>>>> working group
>>>>>> is in the process of completing its final milestones.   
>>>>>> Publication
>>>>>> requests will be issued in the next few days for the data
>>>>> model, CCMP,
>>>>>> and the Examples drafts.
>>>>>>
>>>>>> Taking on any new milestones for the working group would require:
>>>>>> 1. Strong support and interest from working group participants 2.
>>>>>> Approval of our ADs.
>>>>>>
>>>>>> I haven't seen evidence of either of these at this stage.
>>>>>>
>>>>>> A possible option is to take this work to DISPATCH, get an
>>>>> indication
>>>>>> of interests, and get feedback on the best way to move this work
>>>>>> forward.
>>>>>>
>>>>>> - Alan -
>>>>>> co-chair XCON
>>>>>>
>>>>>>
>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>>>>> early in
>>>>>>> March. No comments received since.
>>>>>>>
>>>>>>> We'd like guidance on the next steps. First we ask for
>>>>> adoption as
>>>>>>> WG item. Next step would include the merging process with bis
>>>>>>> versions
>>>>>> of
>>>>>>> RFC 4582 and RFC 4583.
>>>>>>>
>>>>>>> We'd like to point out that interested parties for this
>>>>> work indeed
>>>>>>> exist.
>>>>>>>
>>>>>>> (For the record: Questions was sent to XCON chairs in
>>>>> April and May.
>>>>>> See
>>>>>>> below. No response given. Therefore, this request on the list.)
>>>>>>>
>>>>>>> -- Tom
>>>>>>>
>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>>>>>>>> Chairs,
>>>>>>>>
>>>>>>>> Any thoughts or decision on this matter?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> -- Tom
>>>>>>>>
>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>>>>>>>> XCON chairs,
>>>>>>>>>
>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in  
>>>>>>>>> March -
>>>>>> well in
>>>>>>>>> advance of IETF-77.
>>>>>>>>>   http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
>>>>>>>>>
>>>>>>>>> No comments received. Neither on XCON WG list, nor
>>>>> directly to the
>>>>>>>>> authors. Therefore, we ask for adoption of this draft
>>>>> as an XCON
>>>>>>>>> WG item.
>>>>>>>>>
>>>>>>>>> -- Tom
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>> XCON mailing list
>>>>>> XCON@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>
>>>>> _______________________________________________
>>>>> XCON mailing list
>>>>> XCON@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>
>>>> _______________________________________________
>>>> XCON mailing list
>>>> XCON@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>
>>>
>>>
>>>
>>> --
>>> # TANDBERG R&D
>>> ## http://www.tandberg.com
>>> ### http://folk.uio.no/tomkri/
>>> _______________________________________________
>>> XCON mailing list
>>> XCON@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xcon
>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>


From keith.drage@alcatel-lucent.com  Wed Jun  9 15:54:17 2010
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F7393A67B3 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 15:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level: 
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[AWL=2.300,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mEl+SOcQRbIQ for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 15:54:15 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 962E63A68C3 for <xcon@ietf.org>; Wed,  9 Jun 2010 15:54:14 -0700 (PDT)
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 o59Ms7DE010295 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 10 Jun 2010 00:54:08 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Thu, 10 Jun 2010 00:54:07 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Roni Even <ron.even.tlv@gmail.com>, "'Richard L. Barnes'" <rbarnes@bbn.com>, "'Tom Kristensen'" <2mkristensen@gmail.com>
Date: Thu, 10 Jun 2010 00:54:02 +0200
Thread-Topic: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
Thread-Index: AcsH0Gk34nEfgBH9TEaUEMNu/gfFxAAACy+wABUA11A=
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>
In-Reply-To: <4c0f8c0f.9becd80a.55da.0fe2@mx.google.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.64 on 155.132.188.13
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>, 'Tom Kristensen' <tom.kristensen@tandberg.com>, "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 22:54:17 -0000

What you are essentially saying is that all protocols in the future that ne=
ed reliable transport, as BFCP does, have to design in their own reliable t=
ransport element so they can use UDP. This is not a BFCP specific issue.

I find that an unacceptable direction for IETF to be heading in.=20

I would also note that you are also asking for adoption of a document that =
cannot in its current form meet the security requirements of the original R=
FC.

regards

Keith



=20

> -----Original Message-----
> From: Roni Even [mailto:ron.even.tlv@gmail.com]=20
> Sent: Wednesday, June 09, 2010 1:40 PM
> To: 'Richard L. Barnes'; 'Tom Kristensen'
> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';=20
> 'Tom Kristensen'; xcon@ietf.org
> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>=20
> Richard,
> The BFCP I used as a presentation token for video=20
> conferencing. What the implementers found out that TCP does=20
> not work in real networks due to Session border controllers=20
> not supporting TCP as used in BFCP.=20
> This is why in products they try to establish TCP connection=20
> and if fails tries UDP.
> The video conferencing vendors participating in the IMTC sip=20
> parity activity group defined an interoperability profile=20
> that references this option Roni Even=20
>=20
> > -----Original Message-----
> > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]=20
> On Behalf=20
> > Of Richard L. Barnes
> > Sent: Wednesday, June 09, 2010 3:34 PM
> > To: Tom Kristensen
> > Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom=20
> > Kristensen; xcon@ietf.org
> > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >=20
> > Tom and others who are interested in this draft:
> >=20
> > For those who are relatively new here: Could you summarize why you=20
> > think this draft is needed?  What requirement does it meet=20
> that BFCP=20
> > doesn't right now?
> >=20
> > Thanks,
> > --Richard
> >=20
> >=20
> >=20
> >=20
> > On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> >=20
> > > The UDP/BFCP draft has been presented and discussed in=20
> two or three=20
> > > IETF XCON sessions. No objection to the work being=20
> carried on, just=20
> > > that adoption as WG item was postponed until the draft was more=20
> > > complete. (This has been delayed of various reasons, but=20
> the authors=20
> > > believe the -02 version in question here should be ready for=20
> > > adoption).
> > >
> > > The "current status of consensus" might be valid for some, but=20
> > > participants in the XCON sessions and the minutes of meeting show=20
> > > progress away from that initial consensus.
> > >
> > > I believe Ott's concerns are either dealt with or at=20
> least mentioned=20
> > > in the draft. Arrest me if I'm wrong.
> > >
> > > -- Tom
> > >
> > > On 9 June 2010 13:20, DRAGE, Keith (Keith)=20
> > > <keith.drage@alcatel-lucent.com> wrote:
> > >> We made an explicit decision in the original draft that=20
> UDP was not=20
> > >> required, not that we would do it later. That as far as I am=20
> > >> concerned represents the current status of consensus.
> > >>
> > >> This was done on the basis that we had all seen how UDP=20
> support had=20
> > >> complicated SIP, and we did not want to repeat that issue.
> > >>
> > >> So this is not continuing the work. The status is an=20
> author draft=20
> > >> which goes against a WG consensus position.
> > >>
> > >> I believe Georg Ott also expressed some concerns which I did not=20
> > >> see answered on list at all.
> > >>
> > >> regards
> > >>
> > >> Keith
> > >>
> > >>> -----Original Message-----
> > >>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On=20
> > >>> Behalf Of Roni Even
> > >>> Sent: Tuesday, June 08, 2010 7:35 PM
> > >>> To: 'Alan Johnston'; 'Tom Kristensen'
> > >>> Cc: 'Mark Thompson'; xcon@ietf.org
> > >>> Subject: Re: [XCON] WG Adoption?=20
> draft-sandbakken-xcon-bfcp-udp-02
> > >>>
> > >>> Hi Alan,
> > >>> I support this work and think it is urgent to finish it.
> > >>> I think that updating BFCP with UDP support is very=20
> important. I=20
> > >>> would like to mention that BFCP is being used in video=20
> > >>> conferencing application and since the implementers encountered=20
> > >>> problems with TCP they use a fall back to UDP.
> > >>> We discussed this work in previous IETF meeting and=20
> Gonzalo as far=20
> > >>> as I remember suggested to add it to a BFCP bis draft.
> > >>>
> > >>> Thanks
> > >>> Roni Even
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > >>> On Behalf
> > >>>> Of Alan Johnston
> > >>>> Sent: Tuesday, June 08, 2010 7:44 PM
> > >>>> To: Tom Kristensen
> > >>>> Cc: Mark Thompson; xcon@ietf.org
> > >>>> Subject: Re: [XCON] WG Adoption?=20
> > >>>> draft-sandbakken-xcon-bfcp-udp-02
> > >>>>
> > >>>> Tom,
> > >>>>
> > >>>> Apologies for the delay in replying.  As you know, the
> > >>> working group
> > >>>> is in the process of completing its final milestones. =20
> > >>>> Publication requests will be issued in the next few=20
> days for the=20
> > >>>> data
> > >>> model, CCMP,
> > >>>> and the Examples drafts.
> > >>>>
> > >>>> Taking on any new milestones for the working group=20
> would require:
> > >>>> 1. Strong support and interest from working group=20
> participants 2.
> > >>>> Approval of our ADs.
> > >>>>
> > >>>> I haven't seen evidence of either of these at this stage.
> > >>>>
> > >>>> A possible option is to take this work to DISPATCH, get an
> > >>> indication
> > >>>> of interests, and get feedback on the best way to move=20
> this work=20
> > >>>> forward.
> > >>>>
> > >>>> - Alan -
> > >>>> co-chair XCON
> > >>>>
> > >>>>
> > >>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > >>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> > >>> early in
> > >>>>> March. No comments received since.
> > >>>>>
> > >>>>> We'd like guidance on the next steps. First we ask for
> > >>> adoption as
> > >>>>> WG item. Next step would include the merging process with bis=20
> > >>>>> versions
> > >>>> of
> > >>>>> RFC 4582 and RFC 4583.
> > >>>>>
> > >>>>> We'd like to point out that interested parties for this
> > >>> work indeed
> > >>>>> exist.
> > >>>>>
> > >>>>> (For the record: Questions was sent to XCON chairs in
> > >>> April and May.
> > >>>> See
> > >>>>> below. No response given. Therefore, this request on=20
> the list.)
> > >>>>>
> > >>>>> -- Tom
> > >>>>>
> > >>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > >>>>>> Chairs,
> > >>>>>>
> > >>>>>> Any thoughts or decision on this matter?
> > >>>>>>
> > >>>>>> Cheers,
> > >>>>>> -- Tom
> > >>>>>>
> > >>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > >>>>>>> XCON chairs,
> > >>>>>>>
> > >>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02=20
> early in March=20
> > >>>>>>> -
> > >>>> well in
> > >>>>>>> advance of IETF-77.
> > >>>>>>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> > >>>>>>>
> > >>>>>>> No comments received. Neither on XCON WG list, nor
> > >>> directly to the
> > >>>>>>> authors. Therefore, we ask for adoption of this draft
> > >>> as an XCON
> > >>>>>>> WG item.
> > >>>>>>>
> > >>>>>>> -- Tom
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>> _______________________________________________
> > >>>> XCON mailing list
> > >>>> XCON@ietf.org
> > >>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>
> > >>> _______________________________________________
> > >>> XCON mailing list
> > >>> XCON@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>
> > >> _______________________________________________
> > >> XCON mailing list
> > >> XCON@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/xcon
> > >>
> > >
> > >
> > >
> > > --
> > > # TANDBERG R&D
> > > ## http://www.tandberg.com
> > > ### http://folk.uio.no/tomkri/
> > > _______________________________________________
> > > XCON mailing list
> > > XCON@ietf.org
> > > https://www.ietf.org/mailman/listinfo/xcon
> >=20
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
>=20
> =

From keith.drage@alcatel-lucent.com  Wed Jun  9 16:03:08 2010
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACAC43A6893 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 16:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.716
X-Spam-Level: 
X-Spam-Status: No, score=-2.716 tagged_above=-999 required=5 tests=[AWL=-0.467, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNESrdMU3E5O for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 16:03:07 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 165693A67D7 for <xcon@ietf.org>; Wed,  9 Jun 2010 16:03:06 -0700 (PDT)
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 o59N35EI015954 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 10 Jun 2010 01:03:05 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Thu, 10 Jun 2010 01:03:04 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Tom Kristensen <2mkristensen@gmail.com>
Date: Thu, 10 Jun 2010 01:03:00 +0200
Thread-Topic: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
Thread-Index: AcsHyELSm/jacSuwTp6IHjSnJmu4wQAXrvCw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE213E49BEA@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>
In-Reply-To: <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
Cc: Alan Johnston <alan.b.johnston@gmail.com>, Mark Thompson <mark.thompson@tandberg.com>, Tom Kristensen <tom.kristensen@tandberg.com>, "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 23:03:08 -0000

You say:

> The UDP/BFCP draft has been presented and discussed in two or=20
> three IETF XCON sessions. No objection to the work being=20
> carried on, just that adoption as WG item was postponed until=20
> the draft was more complete. (This has been delayed of=20
> various reasons, but the authors believe the -02 version in=20
> question here should be ready for adoption).
>=20

Aside from this being at total variance to my understanding of WG adoption =
this is the previous history according to the minutes.

IETF #77

XCON did not meet.

IETF #76

3. BFCP over UDP
  draft-sandbakken-xcon-bfcp-udp
Alan Johnston presented an update on this document on behalf of Tom Kristen=
sen.  Several commenters pointed out that the current draft still has many =
problems that had been called out at previous meetings, The draft will not =
be taken up by the WG at this time.

IETF#75

No discussion in meeting

IETF#74

4. Geir Arne Sandbakken: BFCP over UDP
-- Trouble getting BFCP/TCP through RTP relays for NAT traversal
   =3D> Translated BFCP to UDP
-- Now works with ICE, IMTC considering adopting BFCP
-- Open issues: Dynamic message sizes, security considerations
-- Adam: Not going to ask for adoption now, but wanted to present it
   -- People please read through this
-- Roni: Work is going on in IMTC because companies are meeting and working=
.  This work is important.
-- Elwell: This is important, especially since TURN-TCP isn't done
-- Cullen: If we limited message sizes, would it still be useful?
   -- If so, then that would be much easier than fragmenting
   -- Geir Arne: Biggest packets seem to be 40bytes
   -- Gonzalo: BFCP messages can get big, I will help with this doc
-- Lorenzo: There are packet size limitations in TCP too
-- Lorenzo: Have you considered UDP/TCP gateways?
-- Gonzalo: You would have problems with that.
-- Gonzalo: There's a scope question; do we want to do BFCP bugfixes too?

IETF#73

No discussion in meeting

IETF#72

No discussion in meeting

IETF#71

No discussion in meeting

regards

Keith

> -----Original Message-----
> From: Tom Kristensen [mailto:2mkristensen@gmail.com]=20
> Sent: Wednesday, June 09, 2010 12:38 PM
> To: DRAGE, Keith (Keith)
> Cc: Roni Even; Alan Johnston; Tom Kristensen; Mark Thompson;=20
> xcon@ietf.org
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>=20
> The UDP/BFCP draft has been presented and discussed in two or=20
> three IETF XCON sessions. No objection to the work being=20
> carried on, just that adoption as WG item was postponed until=20
> the draft was more complete. (This has been delayed of=20
> various reasons, but the authors believe the -02 version in=20
> question here should be ready for adoption).
>=20
> The "current status of consensus" might be valid for some,=20
> but participants in the XCON sessions and the minutes of=20
> meeting show progress away from that initial consensus.
>=20
> I believe Ott's concerns are either dealt with or at least=20
> mentioned in the draft. Arrest me if I'm wrong.
>=20
> -- Tom
>=20
> On 9 June 2010 13:20, DRAGE, Keith (Keith)=20
> <keith.drage@alcatel-lucent.com> wrote:
> > We made an explicit decision in the original draft that UDP=20
> was not required, not that we would do it later. That as far=20
> as I am concerned represents the current status of consensus.
> >
> > This was done on the basis that we had all seen how UDP=20
> support had complicated SIP, and we did not want to repeat that issue.
> >
> > So this is not continuing the work. The status is an author=20
> draft which goes against a WG consensus position.
> >
> > I believe Georg Ott also expressed some concerns which I=20
> did not see answered on list at all.
> >
> > regards
> >
> > Keith
> >
> >> -----Original Message-----
> >> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]=20
> On Behalf=20
> >> Of Roni Even
> >> Sent: Tuesday, June 08, 2010 7:35 PM
> >> To: 'Alan Johnston'; 'Tom Kristensen'
> >> Cc: 'Mark Thompson'; xcon@ietf.org
> >> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >>
> >> Hi Alan,
> >> I support this work and think it is urgent to finish it.
> >> I think that updating BFCP with UDP support is very important. I=20
> >> would like to mention that BFCP is being used in video=20
> conferencing=20
> >> application and since the implementers encountered=20
> problems with TCP=20
> >> they use a fall back to UDP.
> >> We discussed this work in previous IETF meeting and=20
> Gonzalo as far as=20
> >> I remember suggested to add it to a BFCP bis draft.
> >>
> >> Thanks
> >> Roni Even
> >>
> >> > -----Original Message-----
> >> > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >> On Behalf
> >> > Of Alan Johnston
> >> > Sent: Tuesday, June 08, 2010 7:44 PM
> >> > To: Tom Kristensen
> >> > Cc: Mark Thompson; xcon@ietf.org
> >> > Subject: Re: [XCON] WG Adoption?=20
> draft-sandbakken-xcon-bfcp-udp-02
> >> >
> >> > Tom,
> >> >
> >> > Apologies for the delay in replying. =A0As you know, the
> >> working group
> >> > is in the process of completing its final milestones. =A0
> Publication=20
> >> > requests will be issued in the next few days for the data
> >> model, CCMP,
> >> > and the Examples drafts.
> >> >
> >> > Taking on any new milestones for the working group would require:
> >> > 1. Strong support and interest from working group participants 2.
> >> > Approval of our ADs.
> >> >
> >> > I haven't seen evidence of either of these at this stage.
> >> >
> >> > A possible option is to take this work to DISPATCH, get an
> >> indication
> >> > of interests, and get feedback on the best way to move this work=20
> >> > forward.
> >> >
> >> > - Alan -
> >> > co-chair XCON
> >> >
> >> >
> >> > On 6/7/10 8:22 AM, Tom Kristensen wrote:
> >> > > The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> >> early in
> >> > > March. No comments received since.
> >> > >
> >> > > We'd like guidance on the next steps. First we ask for
> >> adoption as
> >> > > WG item. Next step would include the merging process with bis=20
> >> > > versions
> >> > of
> >> > > RFC 4582 and RFC 4583.
> >> > >
> >> > > We'd like to point out that interested parties for this
> >> work indeed
> >> > > exist.
> >> > >
> >> > > (For the record: Questions was sent to XCON chairs in
> >> April and May.
> >> > See
> >> > > below. No response given. Therefore, this request on the list.)
> >> > >
> >> > > -- Tom
> >> > >
> >> > > On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> >> > >> Chairs,
> >> > >>
> >> > >> Any thoughts or decision on this matter?
> >> > >>
> >> > >> Cheers,
> >> > >> -- Tom
> >> > >>
> >> > >> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> >> > >>> XCON chairs,
> >> > >>>
> >> > >>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early=20
> in March -
> >> > well in
> >> > >>> advance of IETF-77.
> >> > >>> =A0 =A0http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> >> > >>>
> >> > >>> No comments received. Neither on XCON WG list, nor
> >> directly to the
> >> > >>> authors. Therefore, we ask for adoption of this draft
> >> as an XCON
> >> > >>> WG item.
> >> > >>>
> >> > >>> -- Tom
> >> > >>
> >> > >
> >> > >
> >> > _______________________________________________
> >> > XCON mailing list
> >> > XCON@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/xcon
> >>
> >> _______________________________________________
> >> XCON mailing list
> >> XCON@ietf.org
> >> https://www.ietf.org/mailman/listinfo/xcon
> >>
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
> >
>=20
>=20
>=20
> --
> # TANDBERG R&D
> ## http://www.tandberg.com
> ### http://folk.uio.no/tomkri/
> =

From pkyzivat@cisco.com  Wed Jun  9 16:12:19 2010
Return-Path: <pkyzivat@cisco.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CEB473A6953 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 16:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.013
X-Spam-Level: 
X-Spam-Status: No, score=-10.013 tagged_above=-999 required=5 tests=[AWL=0.586, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dY-WKzSxbGS3 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 16:12:17 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 65E033A68FA for <xcon@ietf.org>; Wed,  9 Jun 2010 16:12:17 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJ68D0xAZnwN/2dsb2JhbACeXHGlE5oVgk0YgjMEkEA
X-IronPort-AV: E=Sophos;i="4.53,394,1272844800"; d="scan'208";a="119795219"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 09 Jun 2010 23:12:18 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o59NCItW015618; Wed, 9 Jun 2010 23:12:18 GMT
Message-ID: <4C101FD2.1050704@cisco.com>
Date: Wed, 09 Jun 2010 19:12:18 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost>	<4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>	<59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>	<4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, "xcon@ietf.org" <xcon@ietf.org>, 'Tom Kristensen' <tom.kristensen@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 23:12:20 -0000

DRAGE, Keith (Keith) wrote:
> What you are essentially saying is that all protocols in the future that need reliable transport, as BFCP does, have to design in their own reliable transport element so they can use UDP. This is not a BFCP specific issue.
> 
> I find that an unacceptable direction for IETF to be heading in. 

I just came across this discussion, and am not entirely briefed on all 
its history.

Nevertheless I'm inclined to agree with Keith on this.
In fact I think the argument being raised in support of this direction 
is an even broader one: that no new feature can be added to sip if it 
doesn't work through currently deployed SBCs. I really hope we have not 
reached that state of affairs.

	Thanks,
	Paul

> I would also note that you are also asking for adoption of a document that cannot in its current form meet the security requirements of the original RFC.
> 
> regards
> 
> Keith
> 
> 
> 
>  
> 
>> -----Original Message-----
>> From: Roni Even [mailto:ron.even.tlv@gmail.com] 
>> Sent: Wednesday, June 09, 2010 1:40 PM
>> To: 'Richard L. Barnes'; 'Tom Kristensen'
>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston'; 
>> 'Tom Kristensen'; xcon@ietf.org
>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>
>> Richard,
>> The BFCP I used as a presentation token for video 
>> conferencing. What the implementers found out that TCP does 
>> not work in real networks due to Session border controllers 
>> not supporting TCP as used in BFCP. 
>> This is why in products they try to establish TCP connection 
>> and if fails tries UDP.
>> The video conferencing vendors participating in the IMTC sip 
>> parity activity group defined an interoperability profile 
>> that references this option Roni Even 
>>
>>> -----Original Message-----
>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] 
>> On Behalf 
>>> Of Richard L. Barnes
>>> Sent: Wednesday, June 09, 2010 3:34 PM
>>> To: Tom Kristensen
>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom 
>>> Kristensen; xcon@ietf.org
>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>
>>> Tom and others who are interested in this draft:
>>>
>>> For those who are relatively new here: Could you summarize why you 
>>> think this draft is needed?  What requirement does it meet 
>> that BFCP 
>>> doesn't right now?
>>>
>>> Thanks,
>>> --Richard
>>>
>>>
>>>
>>>
>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
>>>
>>>> The UDP/BFCP draft has been presented and discussed in 
>> two or three 
>>>> IETF XCON sessions. No objection to the work being 
>> carried on, just 
>>>> that adoption as WG item was postponed until the draft was more 
>>>> complete. (This has been delayed of various reasons, but 
>> the authors 
>>>> believe the -02 version in question here should be ready for 
>>>> adoption).
>>>>
>>>> The "current status of consensus" might be valid for some, but 
>>>> participants in the XCON sessions and the minutes of meeting show 
>>>> progress away from that initial consensus.
>>>>
>>>> I believe Ott's concerns are either dealt with or at 
>> least mentioned 
>>>> in the draft. Arrest me if I'm wrong.
>>>>
>>>> -- Tom
>>>>
>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith) 
>>>> <keith.drage@alcatel-lucent.com> wrote:
>>>>> We made an explicit decision in the original draft that 
>> UDP was not 
>>>>> required, not that we would do it later. That as far as I am 
>>>>> concerned represents the current status of consensus.
>>>>>
>>>>> This was done on the basis that we had all seen how UDP 
>> support had 
>>>>> complicated SIP, and we did not want to repeat that issue.
>>>>>
>>>>> So this is not continuing the work. The status is an 
>> author draft 
>>>>> which goes against a WG consensus position.
>>>>>
>>>>> I believe Georg Ott also expressed some concerns which I did not 
>>>>> see answered on list at all.
>>>>>
>>>>> regards
>>>>>
>>>>> Keith
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On 
>>>>>> Behalf Of Roni Even
>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
>>>>>> Subject: Re: [XCON] WG Adoption? 
>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>> Hi Alan,
>>>>>> I support this work and think it is urgent to finish it.
>>>>>> I think that updating BFCP with UDP support is very 
>> important. I 
>>>>>> would like to mention that BFCP is being used in video 
>>>>>> conferencing application and since the implementers encountered 
>>>>>> problems with TCP they use a fall back to UDP.
>>>>>> We discussed this work in previous IETF meeting and 
>> Gonzalo as far 
>>>>>> as I remember suggested to add it to a BFCP bis draft.
>>>>>>
>>>>>> Thanks
>>>>>> Roni Even
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>> On Behalf
>>>>>>> Of Alan Johnston
>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>>>>>>> To: Tom Kristensen
>>>>>>> Cc: Mark Thompson; xcon@ietf.org
>>>>>>> Subject: Re: [XCON] WG Adoption? 
>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>
>>>>>>> Tom,
>>>>>>>
>>>>>>> Apologies for the delay in replying.  As you know, the
>>>>>> working group
>>>>>>> is in the process of completing its final milestones.  
>>>>>>> Publication requests will be issued in the next few 
>> days for the 
>>>>>>> data
>>>>>> model, CCMP,
>>>>>>> and the Examples drafts.
>>>>>>>
>>>>>>> Taking on any new milestones for the working group 
>> would require:
>>>>>>> 1. Strong support and interest from working group 
>> participants 2.
>>>>>>> Approval of our ADs.
>>>>>>>
>>>>>>> I haven't seen evidence of either of these at this stage.
>>>>>>>
>>>>>>> A possible option is to take this work to DISPATCH, get an
>>>>>> indication
>>>>>>> of interests, and get feedback on the best way to move 
>> this work 
>>>>>>> forward.
>>>>>>>
>>>>>>> - Alan -
>>>>>>> co-chair XCON
>>>>>>>
>>>>>>>
>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>>>>>> early in
>>>>>>>> March. No comments received since.
>>>>>>>>
>>>>>>>> We'd like guidance on the next steps. First we ask for
>>>>>> adoption as
>>>>>>>> WG item. Next step would include the merging process with bis 
>>>>>>>> versions
>>>>>>> of
>>>>>>>> RFC 4582 and RFC 4583.
>>>>>>>>
>>>>>>>> We'd like to point out that interested parties for this
>>>>>> work indeed
>>>>>>>> exist.
>>>>>>>>
>>>>>>>> (For the record: Questions was sent to XCON chairs in
>>>>>> April and May.
>>>>>>> See
>>>>>>>> below. No response given. Therefore, this request on 
>> the list.)
>>>>>>>> -- Tom
>>>>>>>>
>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>>>>>>>>> Chairs,
>>>>>>>>>
>>>>>>>>> Any thoughts or decision on this matter?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> -- Tom
>>>>>>>>>
>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>>>>>>>>> XCON chairs,
>>>>>>>>>>
>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02 
>> early in March 
>>>>>>>>>> -
>>>>>>> well in
>>>>>>>>>> advance of IETF-77.
>>>>>>>>>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
>>>>>>>>>>
>>>>>>>>>> No comments received. Neither on XCON WG list, nor
>>>>>> directly to the
>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
>>>>>> as an XCON
>>>>>>>>>> WG item.
>>>>>>>>>>
>>>>>>>>>> -- Tom
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> XCON mailing list
>>>>>>> XCON@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>> _______________________________________________
>>>>>> XCON mailing list
>>>>>> XCON@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>
>>>>> _______________________________________________
>>>>> XCON mailing list
>>>>> XCON@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>
>>>>
>>>>
>>>> --
>>>> # TANDBERG R&D
>>>> ## http://www.tandberg.com
>>>> ### http://folk.uio.no/tomkri/
>>>> _______________________________________________
>>>> XCON mailing list
>>>> XCON@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/xcon
>>> _______________________________________________
>>> XCON mailing list
>>> XCON@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xcon
>>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
> 

From ron.even.tlv@gmail.com  Wed Jun  9 22:25:12 2010
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 026EF3A6403 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 22:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FYOB0Jgs-1z5 for <xcon@core3.amsl.com>; Wed,  9 Jun 2010 22:25:10 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 885973A68CF for <xcon@ietf.org>; Wed,  9 Jun 2010 22:25:09 -0700 (PDT)
Received: by wya21 with SMTP id 21so376474wya.31 for <xcon@ietf.org>; Wed, 09 Jun 2010 22:25:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=NvwpKRHtBgnB2RSx/dDVjG++FnHCSzBZ0l9+9WaQOPQ=; b=Ej3mbRS5RmDTvVeMJYIHvEmlP7kUzpeK8tjGv9ewcZYbWrtxaYNrHDWrOfHpUiGQqo fUV7FfeX1CyY+u+/1feXYRuoFR9ibxJGyW4rlBqnSRiFWlSJjc5Sa9Zkeub5lSz80cgp z4muD7r4qcBXXvP7bgjFYRrR8pv7z0wijGdns=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=Os6OStSblMoJmGOx3RNxwO0tPcPZWTWpMyAWRZSaNcGTcg74Job0eWp7gwOAi9u8OG pZlWJh3X4DEKGOBfMZy/dgSjNeFxmUfVYL73stKCcKbaE3Td+LVjEUh31OI5Id7HuIDD 6IX+xDp1tmpTkIbJrHj8CtxP5nfeHmzhjZSDU=
Received: by 10.227.157.134 with SMTP id b6mr4131878wbx.12.1276147508450; Wed, 09 Jun 2010 22:25:08 -0700 (PDT)
Received: from windows8d787f9 ([109.65.51.207]) by mx.google.com with ESMTPS id y31sm61957446wby.16.2010.06.09.22.25.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 09 Jun 2010 22:25:07 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, "'Richard L. Barnes'" <rbarnes@bbn.com>, "'Tom Kristensen'" <2mkristensen@gmail.com>
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Thu, 10 Jun 2010 08:22:55 +0300
Message-ID: <4c107733.df0ce30a.21ca.15cc@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsH0Gk34nEfgBH9TEaUEMNu/gfFxAAACy+wABUA11AADSt3IA==
Content-Language: en-us
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>, 'Tom Kristensen' <tom.kristensen@tandberg.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 05:25:12 -0000

Hi  Keith,

I think that the IETF is trying to design protocols that will work over the
Internet and also to enable interoperability between independent
implementations. 
 
In the BFCP case the shipping implementations support TCP as the transport
protocol but they encountered issues when running over the Internet due to
devices like SBCs and due to lack of support for TCP media relay or ICE-TCP
[I-D.ietf-mmusic-ice-tcp].  
When implementations looked at how to address the issue, the
interoperability went away since there is no fall back solution for this
real life case. Some did a fall back to HTTP and some did to UDP but not in
an interoperable way.

In order to achieve interoperability, this draft is trying to extend the
current BFCP. It is not suggesting to replace TCP but to keep TCP as the
mandatory transport and use UDP as fallback if unable to establish TCP
connection. 

As for security, if the topic will be adopted the solution will be updated
to use DTLS as the transport for BFCP.

I hope that people will read the draft and look at the objectives and the
proposed solution.


BTW: This is a problem for client to client media connections over TCP and
my understanding is that RTSP offers to use both TCP and UDP since both are
specified. Since BFCP is not a payload but is running in parallel to the RTP
payload (for the point to point calls or MCU based multipoint) it needs
similar transport options.

Thanks
Roni Even




> -----Original Message-----
> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
> Sent: Thursday, June 10, 2010 1:54 AM
> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen'; xcon@ietf.org
> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> 
> What you are essentially saying is that all protocols in the future
> that need reliable transport, as BFCP does, have to design in their own
> reliable transport element so they can use UDP. This is not a BFCP
> specific issue.
> 
> I find that an unacceptable direction for IETF to be heading in.
> 
> I would also note that you are also asking for adoption of a document
> that cannot in its current form meet the security requirements of the
> original RFC.
> 
> regards
> 
> Keith
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > Sent: Wednesday, June 09, 2010 1:40 PM
> > To: 'Richard L. Barnes'; 'Tom Kristensen'
> > Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> > 'Tom Kristensen'; xcon@ietf.org
> > Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >
> > Richard,
> > The BFCP I used as a presentation token for video
> > conferencing. What the implementers found out that TCP does
> > not work in real networks due to Session border controllers
> > not supporting TCP as used in BFCP.
> > This is why in products they try to establish TCP connection
> > and if fails tries UDP.
> > The video conferencing vendors participating in the IMTC sip
> > parity activity group defined an interoperability profile
> > that references this option Roni Even
> >
> > > -----Original Message-----
> > > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > On Behalf
> > > Of Richard L. Barnes
> > > Sent: Wednesday, June 09, 2010 3:34 PM
> > > To: Tom Kristensen
> > > Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> > > Kristensen; xcon@ietf.org
> > > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > >
> > > Tom and others who are interested in this draft:
> > >
> > > For those who are relatively new here: Could you summarize why you
> > > think this draft is needed?  What requirement does it meet
> > that BFCP
> > > doesn't right now?
> > >
> > > Thanks,
> > > --Richard
> > >
> > >
> > >
> > >
> > > On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> > >
> > > > The UDP/BFCP draft has been presented and discussed in
> > two or three
> > > > IETF XCON sessions. No objection to the work being
> > carried on, just
> > > > that adoption as WG item was postponed until the draft was more
> > > > complete. (This has been delayed of various reasons, but
> > the authors
> > > > believe the -02 version in question here should be ready for
> > > > adoption).
> > > >
> > > > The "current status of consensus" might be valid for some, but
> > > > participants in the XCON sessions and the minutes of meeting show
> > > > progress away from that initial consensus.
> > > >
> > > > I believe Ott's concerns are either dealt with or at
> > least mentioned
> > > > in the draft. Arrest me if I'm wrong.
> > > >
> > > > -- Tom
> > > >
> > > > On 9 June 2010 13:20, DRAGE, Keith (Keith)
> > > > <keith.drage@alcatel-lucent.com> wrote:
> > > >> We made an explicit decision in the original draft that
> > UDP was not
> > > >> required, not that we would do it later. That as far as I am
> > > >> concerned represents the current status of consensus.
> > > >>
> > > >> This was done on the basis that we had all seen how UDP
> > support had
> > > >> complicated SIP, and we did not want to repeat that issue.
> > > >>
> > > >> So this is not continuing the work. The status is an
> > author draft
> > > >> which goes against a WG consensus position.
> > > >>
> > > >> I believe Georg Ott also expressed some concerns which I did not
> > > >> see answered on list at all.
> > > >>
> > > >> regards
> > > >>
> > > >> Keith
> > > >>
> > > >>> -----Original Message-----
> > > >>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
> > > >>> Behalf Of Roni Even
> > > >>> Sent: Tuesday, June 08, 2010 7:35 PM
> > > >>> To: 'Alan Johnston'; 'Tom Kristensen'
> > > >>> Cc: 'Mark Thompson'; xcon@ietf.org
> > > >>> Subject: Re: [XCON] WG Adoption?
> > draft-sandbakken-xcon-bfcp-udp-02
> > > >>>
> > > >>> Hi Alan,
> > > >>> I support this work and think it is urgent to finish it.
> > > >>> I think that updating BFCP with UDP support is very
> > important. I
> > > >>> would like to mention that BFCP is being used in video
> > > >>> conferencing application and since the implementers encountered
> > > >>> problems with TCP they use a fall back to UDP.
> > > >>> We discussed this work in previous IETF meeting and
> > Gonzalo as far
> > > >>> as I remember suggested to add it to a BFCP bis draft.
> > > >>>
> > > >>> Thanks
> > > >>> Roni Even
> > > >>>
> > > >>>> -----Original Message-----
> > > >>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > > >>> On Behalf
> > > >>>> Of Alan Johnston
> > > >>>> Sent: Tuesday, June 08, 2010 7:44 PM
> > > >>>> To: Tom Kristensen
> > > >>>> Cc: Mark Thompson; xcon@ietf.org
> > > >>>> Subject: Re: [XCON] WG Adoption?
> > > >>>> draft-sandbakken-xcon-bfcp-udp-02
> > > >>>>
> > > >>>> Tom,
> > > >>>>
> > > >>>> Apologies for the delay in replying.  As you know, the
> > > >>> working group
> > > >>>> is in the process of completing its final milestones.
> > > >>>> Publication requests will be issued in the next few
> > days for the
> > > >>>> data
> > > >>> model, CCMP,
> > > >>>> and the Examples drafts.
> > > >>>>
> > > >>>> Taking on any new milestones for the working group
> > would require:
> > > >>>> 1. Strong support and interest from working group
> > participants 2.
> > > >>>> Approval of our ADs.
> > > >>>>
> > > >>>> I haven't seen evidence of either of these at this stage.
> > > >>>>
> > > >>>> A possible option is to take this work to DISPATCH, get an
> > > >>> indication
> > > >>>> of interests, and get feedback on the best way to move
> > this work
> > > >>>> forward.
> > > >>>>
> > > >>>> - Alan -
> > > >>>> co-chair XCON
> > > >>>>
> > > >>>>
> > > >>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > > >>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> > > >>> early in
> > > >>>>> March. No comments received since.
> > > >>>>>
> > > >>>>> We'd like guidance on the next steps. First we ask for
> > > >>> adoption as
> > > >>>>> WG item. Next step would include the merging process with bis
> > > >>>>> versions
> > > >>>> of
> > > >>>>> RFC 4582 and RFC 4583.
> > > >>>>>
> > > >>>>> We'd like to point out that interested parties for this
> > > >>> work indeed
> > > >>>>> exist.
> > > >>>>>
> > > >>>>> (For the record: Questions was sent to XCON chairs in
> > > >>> April and May.
> > > >>>> See
> > > >>>>> below. No response given. Therefore, this request on
> > the list.)
> > > >>>>>
> > > >>>>> -- Tom
> > > >>>>>
> > > >>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > > >>>>>> Chairs,
> > > >>>>>>
> > > >>>>>> Any thoughts or decision on this matter?
> > > >>>>>>
> > > >>>>>> Cheers,
> > > >>>>>> -- Tom
> > > >>>>>>
> > > >>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > > >>>>>>> XCON chairs,
> > > >>>>>>>
> > > >>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> > early in March
> > > >>>>>>> -
> > > >>>> well in
> > > >>>>>>> advance of IETF-77.
> > > >>>>>>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
> udp
> > > >>>>>>>
> > > >>>>>>> No comments received. Neither on XCON WG list, nor
> > > >>> directly to the
> > > >>>>>>> authors. Therefore, we ask for adoption of this draft
> > > >>> as an XCON
> > > >>>>>>> WG item.
> > > >>>>>>>
> > > >>>>>>> -- Tom
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>> _______________________________________________
> > > >>>> XCON mailing list
> > > >>>> XCON@ietf.org
> > > >>>> https://www.ietf.org/mailman/listinfo/xcon
> > > >>>
> > > >>> _______________________________________________
> > > >>> XCON mailing list
> > > >>> XCON@ietf.org
> > > >>> https://www.ietf.org/mailman/listinfo/xcon
> > > >>>
> > > >> _______________________________________________
> > > >> XCON mailing list
> > > >> XCON@ietf.org
> > > >> https://www.ietf.org/mailman/listinfo/xcon
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > # TANDBERG R&D
> > > > ## http://www.tandberg.com
> > > > ### http://folk.uio.no/tomkri/
> > > > _______________________________________________
> > > > XCON mailing list
> > > > XCON@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/xcon
> > >
> > > _______________________________________________
> > > XCON mailing list
> > > XCON@ietf.org
> > > https://www.ietf.org/mailman/listinfo/xcon
> >
> > =


From keith.drage@alcatel-lucent.com  Thu Jun 10 02:24:14 2010
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF1403A63CA for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 02:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.929
X-Spam-Level: 
X-Spam-Status: No, score=-2.929 tagged_above=-999 required=5 tests=[AWL=-0.680, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id go4y1qvmEVsX for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 02:24:13 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 1FBC43A6903 for <xcon@ietf.org>; Thu, 10 Jun 2010 02:24:12 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o5A9O5vb001668 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 10 Jun 2010 11:24:06 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Thu, 10 Jun 2010 11:23:24 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Gonzalo Camarillo <gcamaril@gmail.com>, "Richard L. Barnes" <rbarnes@bbn.com>
Date: Thu, 10 Jun 2010 11:23:18 +0200
Thread-Topic: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
Thread-Index: AcsIffB1sWeapY6dR7uAOR+ZJK1yzwAAG6ww
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE213E49C62@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <40418C09-CBE0-4546-A07D-5331E40BFDA6@bbn.com> <4C10ADEF.6030107@gmail.com>
In-Reply-To: <4C10ADEF.6030107@gmail.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
Cc: 'Tom Kristensen' <tom.kristensen@tandberg.com>, 'Mark Thompson' <mark.thompson@tandberg.com>, "xcon@ietf.org" <xcon@ietf.org>, 'Alan Johnston' <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 09:24:14 -0000

Gonzalo, thanks for the input.=20

Yes, I believe this discussion is exactly the discussion we should be havin=
g, rather than the blind adoption of a draft.

I believe in the past we also informally asked for IAB input on this issue.=
 Did we ever get any viewpoint from that body.

regards

Keith

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]=20
> Sent: Thursday, June 10, 2010 10:19 AM
> To: Richard L. Barnes
> Cc: Roni Even; 'Tom Kristensen'; DRAGE, Keith (Keith);=20
> xcon@ietf.org; 'Mark Thompson'; 'Alan Johnston'
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>=20
> Hi,
>=20
> a bit of background on this draft. When writing the BFCP=20
> spec, I included a DNS-based mechanism to choose which=20
> transport protocol to use. However, the WG decided to specify=20
> a single transport protocol
> (TCP) instead. At that point, using UDP instead of TCP was=20
> seen as an unnecessary optimization because the may reason=20
> for using UDP was to save a RTT (i.e., by avoiding the TCP=20
> three-way handshake) in certain circumstances. Nobody seems=20
> to be keep on using SCTP either.
>=20
> The typical use case for BFCP consisted of a client talking=20
> to a floor control server with a public IP address. In that=20
> type of scenario, TCP works well even when the client is behind a NAT.
>=20
> However, there are deployments where BFCP is used between two=20
> endpoints (one of them acts as the floor control server),=20
> none of which have a public IP address. Given the problems=20
> ICE TCP currently has, implementers have (understandably)=20
> started using UDP. Using UDP allows endpoints to use ICE or=20
> any other NAT traversal technique for UDP flows.
>=20
> With this background in mind, there are different things the=20
> WG may choose to do. We could follow the approach in this=20
> draft and specify a UDP transport for BFCP, we could specify=20
> how to encapsulate BFCP over TCP over UDP, we could progress=20
> ICE TCP to completion, ...
>=20
> Cheers,
>=20
> Gonzalo
>=20
>=20
>=20
> On 09/06/2010 3:51 PM, Richard L. Barnes wrote:
> > Thanks for the quick reply, Roni.
> >=20
> > What do you mean by "TCP as used in BFCP"?  Is the issue:
> > -- SBCs don't let any TCP through at all?
> > -- SBCs don't support the SDP options for BFCP? (thus don't open=20
> > ports?)
> > -- SBCs are doing DPI and don't let through TCP traffic=20
> containing BFCP?
> > -- Something else?
> >=20
> >=20
> >=20
> > On Jun 9, 2010, at 8:39 AM, Roni Even wrote:
> >=20
> >> Richard,
> >> The BFCP I used as a presentation token for video=20
> conferencing. What=20
> >> the implementers found out that TCP does not work in real networks=20
> >> due to Session border controllers not supporting TCP as=20
> used in BFCP.
> >> This is why in products they try to establish TCP=20
> connection and if=20
> >> fails tries UDP.
> >> The video conferencing vendors participating in the IMTC=20
> sip parity=20
> >> activity group defined an interoperability profile that references=20
> >> this option Roni Even
> >>
> >>> -----Original Message-----
> >>> From: xcon-bounces@ietf.org=20
> [mailto:xcon-bounces@ietf.org] On Behalf=20
> >>> Of Richard L. Barnes
> >>> Sent: Wednesday, June 09, 2010 3:34 PM
> >>> To: Tom Kristensen
> >>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom=20
> >>> Kristensen; xcon@ietf.org
> >>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >>>
> >>> Tom and others who are interested in this draft:
> >>>
> >>> For those who are relatively new here: Could you=20
> summarize why you=20
> >>> think this draft is needed?  What requirement does it=20
> meet that BFCP=20
> >>> doesn't right now?
> >>>
> >>> Thanks,
> >>> --Richard
> >>>
> >>>
> >>>
> >>>
> >>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> >>>
> >>>> The UDP/BFCP draft has been presented and discussed in=20
> two or three=20
> >>>> IETF XCON sessions. No objection to the work being=20
> carried on, just=20
> >>>> that adoption as WG item was postponed until the draft was more=20
> >>>> complete. (This has been delayed of various reasons, but the=20
> >>>> authors believe the -02 version in question here should be ready=20
> >>>> for adoption).
> >>>>
> >>>> The "current status of consensus" might be valid for some, but=20
> >>>> participants in the XCON sessions and the minutes of=20
> meeting show=20
> >>>> progress away from that initial consensus.
> >>>>
> >>>> I believe Ott's concerns are either dealt with or at least=20
> >>>> mentioned in the draft. Arrest me if I'm wrong.
> >>>>
> >>>> -- Tom
> >>>>
> >>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)=20
> >>>> <keith.drage@alcatel-lucent.com> wrote:
> >>>>> We made an explicit decision in the original draft that UDP was=20
> >>>>> not required, not that we would do it later. That as=20
> far as I am=20
> >>>>> concerned represents the current status of consensus.
> >>>>>
> >>>>> This was done on the basis that we had all seen how UDP support=20
> >>>>> had complicated SIP, and we did not want to repeat that issue.
> >>>>>
> >>>>> So this is not continuing the work. The status is an=20
> author draft=20
> >>>>> which goes against a WG consensus position.
> >>>>>
> >>>>> I believe Georg Ott also expressed some concerns which=20
> I did not=20
> >>>>> see answered on list at all.
> >>>>>
> >>>>> regards
> >>>>>
> >>>>> Keith
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On=20
> >>>>>> Behalf Of Roni Even
> >>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
> >>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
> >>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
> >>>>>> Subject: Re: [XCON] WG Adoption?=20
> >>>>>> draft-sandbakken-xcon-bfcp-udp-02
> >>>>>>
> >>>>>> Hi Alan,
> >>>>>> I support this work and think it is urgent to finish it.
> >>>>>> I think that updating BFCP with UDP support is very=20
> important. I=20
> >>>>>> would like to mention that BFCP is being used in video=20
> >>>>>> conferencing application and since the implementers=20
> encountered=20
> >>>>>> problems with TCP they use a fall back to UDP.
> >>>>>> We discussed this work in previous IETF meeting and Gonzalo as=20
> >>>>>> far as I remember suggested to add it to a BFCP bis draft.
> >>>>>>
> >>>>>> Thanks
> >>>>>> Roni Even
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >>>>>> On Behalf
> >>>>>>> Of Alan Johnston
> >>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
> >>>>>>> To: Tom Kristensen
> >>>>>>> Cc: Mark Thompson; xcon@ietf.org
> >>>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-
> >>>>>>> udp-02
> >>>>>>>
> >>>>>>> Tom,
> >>>>>>>
> >>>>>>> Apologies for the delay in replying.  As you know, the
> >>>>>> working group
> >>>>>>> is in the process of completing its final milestones.  =20
> >>>>>>> Publication
> >>>>>>> requests will be issued in the next few days for the data
> >>>>>> model, CCMP,
> >>>>>>> and the Examples drafts.
> >>>>>>>
> >>>>>>> Taking on any new milestones for the working group=20
> would require:
> >>>>>>> 1. Strong support and interest from working group=20
> participants 2.
> >>>>>>> Approval of our ADs.
> >>>>>>>
> >>>>>>> I haven't seen evidence of either of these at this stage.
> >>>>>>>
> >>>>>>> A possible option is to take this work to DISPATCH, get an
> >>>>>> indication
> >>>>>>> of interests, and get feedback on the best way to=20
> move this work=20
> >>>>>>> forward.
> >>>>>>>
> >>>>>>> - Alan -
> >>>>>>> co-chair XCON
> >>>>>>>
> >>>>>>>
> >>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> >>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> >>>>>> early in
> >>>>>>>> March. No comments received since.
> >>>>>>>>
> >>>>>>>> We'd like guidance on the next steps. First we ask for
> >>>>>> adoption as
> >>>>>>>> WG item. Next step would include the merging process=20
> with bis=20
> >>>>>>>> versions
> >>>>>>> of
> >>>>>>>> RFC 4582 and RFC 4583.
> >>>>>>>>
> >>>>>>>> We'd like to point out that interested parties for this
> >>>>>> work indeed
> >>>>>>>> exist.
> >>>>>>>>
> >>>>>>>> (For the record: Questions was sent to XCON chairs in
> >>>>>> April and May.
> >>>>>>> See
> >>>>>>>> below. No response given. Therefore, this request on=20
> the list.)
> >>>>>>>>
> >>>>>>>> -- Tom
> >>>>>>>>
> >>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> >>>>>>>>> Chairs,
> >>>>>>>>>
> >>>>>>>>> Any thoughts or decision on this matter?
> >>>>>>>>>
> >>>>>>>>> Cheers,
> >>>>>>>>> -- Tom
> >>>>>>>>>
> >>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> >>>>>>>>>> XCON chairs,
> >>>>>>>>>>
> >>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02=20
> early in March=20
> >>>>>>>>>> -
> >>>>>>> well in
> >>>>>>>>>> advance of IETF-77.
> >>>>>>>>>>   http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> >>>>>>>>>>
> >>>>>>>>>> No comments received. Neither on XCON WG list, nor
> >>>>>> directly to the
> >>>>>>>>>> authors. Therefore, we ask for adoption of this draft
> >>>>>> as an XCON
> >>>>>>>>>> WG item.
> >>>>>>>>>>
> >>>>>>>>>> -- Tom
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> XCON mailing list
> >>>>>>> XCON@ietf.org
> >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> XCON mailing list
> >>>>>> XCON@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>
> >>>>> _______________________________________________
> >>>>> XCON mailing list
> >>>>> XCON@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> # TANDBERG R&D
> >>>> ## http://www.tandberg.com
> >>>> ### http://folk.uio.no/tomkri/
> >>>> _______________________________________________
> >>>> XCON mailing list
> >>>> XCON@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>
> >>> _______________________________________________
> >>> XCON mailing list
> >>> XCON@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/xcon
> >>
> >=20
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
> >=20
> =

From tom.kristensen@tandberg.com  Thu Jun 10 02:52:59 2010
Return-Path: <tom.kristensen@tandberg.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7549B3A6914 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 02:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iB+5kxfxNcL1 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 02:52:58 -0700 (PDT)
Received: from mail188.messagelabs.com (mail188.messagelabs.com [85.158.139.163]) by core3.amsl.com (Postfix) with SMTP id C5BF23A67DB for <xcon@ietf.org>; Thu, 10 Jun 2010 02:52:57 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tom.kristensen@tandberg.com
X-Msg-Ref: server-4.tower-188.messagelabs.com!1276163560!26019610!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [62.70.2.252]
Received: (qmail 32678 invoked from network); 10 Jun 2010 09:52:40 -0000
Received: from unknown (HELO OSLEXCP11.eu.tandberg.int) (62.70.2.252) by server-4.tower-188.messagelabs.com with SMTP; 10 Jun 2010 09:52:40 -0000
Received: from oslexcp2.eu.tandberg.int ([10.47.136.30]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Thu, 10 Jun 2010 11:52:30 +0200
Received: from 10.47.13.249 ([10.47.13.249]) by oslexcp2.eu.tandberg.int ([10.47.136.30]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 10 Jun 2010 09:52:29 +0000
Received: from TKristensenT500 by oslexcp2.eu.tandberg.int; 10 Jun 2010 11:52:29 +0200
From: Tom Kristensen <tom.kristensen@tandberg.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <4C101FD2.1050704@cisco.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4C101FD2.1050704@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Organization: TANDBERG R&D
Date: Thu, 10 Jun 2010 11:52:29 +0200
Message-ID: <1276163549.2832.9.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) 
X-OriginalArrivalTime: 10 Jun 2010 09:52:30.0096 (UTC) FILETIME=[A4082900:01CB0882]
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "xcon@ietf.org" <xcon@ietf.org>, 'Alan Johnston' <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 09:52:59 -0000

On Wed, 2010-06-09 at 19:12 -0400, Paul Kyzivat wrote:
>=20
> DRAGE, Keith (Keith) wrote:
> > What you are essentially saying is that all protocols in the future tha=
t need reliable transport, as BFCP does, have to design in their own reliab=
le transport element so they can use UDP. This is not a BFCP specific issue=
.
> >=20
> > I find that an unacceptable direction for IETF to be heading in.=20
>=20
> I just came across this discussion, and am not entirely briefed on all=20
> its history.
>=20
> Nevertheless I'm inclined to agree with Keith on this.
> In fact I think the argument being raised in support of this direction=20
> is an even broader one: that no new feature can be added to sip if it=20
> doesn't work through currently deployed SBCs. I really hope we have not=20
> reached that state of affairs.

I like this kind of argumentation when looking at the problem at hand
from an ideal point of view. However, we also have to be pragmatic to
some degree and make useful protocols that works in the actual networks
existing out there.

Camarillo pointed out a path for discussion in a recent message in this
thread - and we have had parts of it already in the WG and elsewhere.
Some of the alternatives are mentioned in the draft (versions -01 and
-02).

-- Tom

From ron.even.tlv@gmail.com  Thu Jun 10 03:06:54 2010
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CEC73A6944 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 03:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5Zpz6bzbLqM for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 03:06:52 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id D34F83A689A for <xcon@ietf.org>; Thu, 10 Jun 2010 03:06:51 -0700 (PDT)
Received: by wya21 with SMTP id 21so523046wya.31 for <xcon@ietf.org>; Thu, 10 Jun 2010 03:06:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=SlGySkfnMn9pzyRFdiRfrya1gUFzsHTkVvvekJ9n46Q=; b=FNplYGJUnQG1bc+Klpe5+a6z3XVFkIOpVHz09mq0B4HO9Y7k5uWmDXfDSHtDGD6MeY nCpx0R2OgK633yHQpFsCbrkFjYpuXTEq3G5rVNAWQPsfVtd5ewMR4zszmLN+smp3VPHT q2SW5wqBgpu5eD2FglUawYlaN9KgDLV7u811Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=V7A0Uev39e8zl6E2lnYFyVY9cAhlQ5+PzrOfH96JBcIsd7swX22ndRW10tLAFfQTUr kl/1bu+mJ8HVyIGh4GuNP/BcIg5Dy00jeOdS+forvohYLXWaSYehq9uVmJan5fYDMyWF AXwy5NHqP5wMk3Vd8zYYePSc9UHONBmA6FIQc=
Received: by 10.227.68.202 with SMTP id w10mr2990989wbi.209.1276164410008; Thu, 10 Jun 2010 03:06:50 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-176-22-234.red.bezeqint.net [79.176.22.234]) by mx.google.com with ESMTPS id n31sm32984381wba.21.2010.06.10.03.06.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Jun 2010 03:06:49 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Gonzalo Camarillo'" <gcamaril@gmail.com>, "'Richard L. Barnes'" <rbarnes@bbn.com>
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost>	<4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>	<59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>	<4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <40418C09-CBE0-4546-A07D-5331E40BFDA6@bbn.com> <4C10ADEF.6030107@gmail.com>
In-Reply-To: <4C10ADEF.6030107@gmail.com>
Date: Thu, 10 Jun 2010 13:04:39 +0300
Message-ID: <4c10b939.5f10e30a.0d5a.2c56@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsIfesx8akgq2sVSQOpU7z5w7nqtQABXhLQ
Content-Language: en-us
Cc: 'Alan Johnston' <alan.b.johnston@gmail.com>, 'Tom Kristensen' <tom.kristensen@tandberg.com>, 'Mark Thompson' <mark.thompson@tandberg.com>, "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 10:06:54 -0000

Hi Gonzalo,
I think that the important input is
" However, there are deployments where BFCP is used between two endpoints
(one of them acts as the floor control server), none of which have a public
IP address. Given the problems ICE TCP currently has, implementers have
(understandably) started using UDP. Using UDP allows endpoints to use ICE or
any other NAT traversal technique for UDP flows."

I think that even though the suggestions " we could specify how to
encapsulate BFCP over TCP over UDP, we could progress ICE TCP to completion,
..." are interesting they do not solve the issue raised in the previous
paragraph since this discussion about TCP has been going forever and is not
progressing. Nobody shows interest which means that people are either using
HTTP or UDP when they encounter the problem. 
If there are cases where TCP does not work I do not see any reason not to
use UDP / DTLS as a fallback mechanism as this draft suggests.



Roni Even

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]
> Sent: Thursday, June 10, 2010 12:19 PM
> To: Richard L. Barnes
> Cc: Roni Even; 'Tom Kristensen'; 'DRAGE, Keith (Keith)'; xcon@ietf.org;
> 'Mark Thompson'; 'Alan Johnston'
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> 
> Hi,
> 
> a bit of background on this draft. When writing the BFCP spec, I
> included a DNS-based mechanism to choose which transport protocol to
> use. However, the WG decided to specify a single transport protocol
> (TCP) instead. At that point, using UDP instead of TCP was seen as an
> unnecessary optimization because the may reason for using UDP was to
> save a RTT (i.e., by avoiding the TCP three-way handshake) in certain
> circumstances. Nobody seems to be keep on using SCTP either.
> 
> The typical use case for BFCP consisted of a client talking to a floor
> control server with a public IP address. In that type of scenario, TCP
> works well even when the client is behind a NAT.
> 
> However, there are deployments where BFCP is used between two endpoints
> (one of them acts as the floor control server), none of which have a
> public IP address. Given the problems ICE TCP currently has,
> implementers have (understandably) started using UDP. Using UDP allows
> endpoints to use ICE or any other NAT traversal technique for UDP
> flows.
> 
> With this background in mind, there are different things the WG may
> choose to do. We could follow the approach in this draft and specify a
> UDP transport for BFCP, we could specify how to encapsulate BFCP over
> TCP over UDP, we could progress ICE TCP to completion, ...
> 
> Cheers,
> 
> Gonzalo
> 
> 
> 
> On 09/06/2010 3:51 PM, Richard L. Barnes wrote:
> > Thanks for the quick reply, Roni.
> >
> > What do you mean by "TCP as used in BFCP"?  Is the issue:
> > -- SBCs don't let any TCP through at all?
> > -- SBCs don't support the SDP options for BFCP? (thus don't open
> ports?)
> > -- SBCs are doing DPI and don't let through TCP traffic containing
> BFCP?
> > -- Something else?
> >
> >
> >
> > On Jun 9, 2010, at 8:39 AM, Roni Even wrote:
> >
> >> Richard,
> >> The BFCP I used as a presentation token for video conferencing. What
> >> the
> >> implementers found out that TCP does not work in real networks due
> to
> >> Session border controllers not supporting TCP as used in BFCP.
> >> This is why in products they try to establish TCP connection and if
> >> fails
> >> tries UDP.
> >> The video conferencing vendors participating in the IMTC sip parity
> >> activity
> >> group defined an interoperability profile that references this
> option
> >> Roni Even
> >>
> >>> -----Original Message-----
> >>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
> >>> Behalf Of
> >>> Richard L. Barnes
> >>> Sent: Wednesday, June 09, 2010 3:34 PM
> >>> To: Tom Kristensen
> >>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> >>> Kristensen;
> >>> xcon@ietf.org
> >>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >>>
> >>> Tom and others who are interested in this draft:
> >>>
> >>> For those who are relatively new here: Could you summarize why you
> >>> think this draft is needed?  What requirement does it meet that
> BFCP
> >>> doesn't right now?
> >>>
> >>> Thanks,
> >>> --Richard
> >>>
> >>>
> >>>
> >>>
> >>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> >>>
> >>>> The UDP/BFCP draft has been presented and discussed in two or
> three
> >>>> IETF XCON sessions. No objection to the work being carried on,
> just
> >>>> that adoption as WG item was postponed until the draft was more
> >>>> complete. (This has been delayed of various reasons, but the
> authors
> >>>> believe the -02 version in question here should be ready for
> >>>> adoption).
> >>>>
> >>>> The "current status of consensus" might be valid for some, but
> >>>> participants in the XCON sessions and the minutes of meeting show
> >>>> progress away from that initial consensus.
> >>>>
> >>>> I believe Ott's concerns are either dealt with or at least
> mentioned
> >>>> in the draft. Arrest me if I'm wrong.
> >>>>
> >>>> -- Tom
> >>>>
> >>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
> >>>> <keith.drage@alcatel-lucent.com> wrote:
> >>>>> We made an explicit decision in the original draft that UDP was
> not
> >>>>> required, not that we would do it later. That as far as I am
> >>>>> concerned represents the current status of consensus.
> >>>>>
> >>>>> This was done on the basis that we had all seen how UDP support
> had
> >>>>> complicated SIP, and we did not want to repeat that issue.
> >>>>>
> >>>>> So this is not continuing the work. The status is an author draft
> >>>>> which goes against a WG consensus position.
> >>>>>
> >>>>> I believe Georg Ott also expressed some concerns which I did not
> >>>>> see answered on list at all.
> >>>>>
> >>>>> regards
> >>>>>
> >>>>> Keith
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
> >>>>>> Behalf Of Roni Even
> >>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
> >>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
> >>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
> >>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> 02
> >>>>>>
> >>>>>> Hi Alan,
> >>>>>> I support this work and think it is urgent to finish it.
> >>>>>> I think that updating BFCP with UDP support is very
> >>>>>> important. I would like to mention that BFCP is being used in
> >>>>>> video conferencing application and since the implementers
> >>>>>> encountered problems with TCP they use a fall back to UDP.
> >>>>>> We discussed this work in previous IETF meeting and Gonzalo
> >>>>>> as far as I remember suggested to add it to a BFCP bis draft.
> >>>>>>
> >>>>>> Thanks
> >>>>>> Roni Even
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >>>>>> On Behalf
> >>>>>>> Of Alan Johnston
> >>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
> >>>>>>> To: Tom Kristensen
> >>>>>>> Cc: Mark Thompson; xcon@ietf.org
> >>>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-
> >>>>>>> udp-02
> >>>>>>>
> >>>>>>> Tom,
> >>>>>>>
> >>>>>>> Apologies for the delay in replying.  As you know, the
> >>>>>> working group
> >>>>>>> is in the process of completing its final milestones.
> >>>>>>> Publication
> >>>>>>> requests will be issued in the next few days for the data
> >>>>>> model, CCMP,
> >>>>>>> and the Examples drafts.
> >>>>>>>
> >>>>>>> Taking on any new milestones for the working group would
> require:
> >>>>>>> 1. Strong support and interest from working group participants
> 2.
> >>>>>>> Approval of our ADs.
> >>>>>>>
> >>>>>>> I haven't seen evidence of either of these at this stage.
> >>>>>>>
> >>>>>>> A possible option is to take this work to DISPATCH, get an
> >>>>>> indication
> >>>>>>> of interests, and get feedback on the best way to move this
> work
> >>>>>>> forward.
> >>>>>>>
> >>>>>>> - Alan -
> >>>>>>> co-chair XCON
> >>>>>>>
> >>>>>>>
> >>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> >>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> >>>>>> early in
> >>>>>>>> March. No comments received since.
> >>>>>>>>
> >>>>>>>> We'd like guidance on the next steps. First we ask for
> >>>>>> adoption as
> >>>>>>>> WG item. Next step would include the merging process with bis
> >>>>>>>> versions
> >>>>>>> of
> >>>>>>>> RFC 4582 and RFC 4583.
> >>>>>>>>
> >>>>>>>> We'd like to point out that interested parties for this
> >>>>>> work indeed
> >>>>>>>> exist.
> >>>>>>>>
> >>>>>>>> (For the record: Questions was sent to XCON chairs in
> >>>>>> April and May.
> >>>>>>> See
> >>>>>>>> below. No response given. Therefore, this request on the
> list.)
> >>>>>>>>
> >>>>>>>> -- Tom
> >>>>>>>>
> >>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> >>>>>>>>> Chairs,
> >>>>>>>>>
> >>>>>>>>> Any thoughts or decision on this matter?
> >>>>>>>>>
> >>>>>>>>> Cheers,
> >>>>>>>>> -- Tom
> >>>>>>>>>
> >>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> >>>>>>>>>> XCON chairs,
> >>>>>>>>>>
> >>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02 early in
> >>>>>>>>>> March -
> >>>>>>> well in
> >>>>>>>>>> advance of IETF-77.
> >>>>>>>>>>   http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> >>>>>>>>>>
> >>>>>>>>>> No comments received. Neither on XCON WG list, nor
> >>>>>> directly to the
> >>>>>>>>>> authors. Therefore, we ask for adoption of this draft
> >>>>>> as an XCON
> >>>>>>>>>> WG item.
> >>>>>>>>>>
> >>>>>>>>>> -- Tom
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> XCON mailing list
> >>>>>>> XCON@ietf.org
> >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> XCON mailing list
> >>>>>> XCON@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>
> >>>>> _______________________________________________
> >>>>> XCON mailing list
> >>>>> XCON@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> # TANDBERG R&D
> >>>> ## http://www.tandberg.com
> >>>> ### http://folk.uio.no/tomkri/
> >>>> _______________________________________________
> >>>> XCON mailing list
> >>>> XCON@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>
> >>> _______________________________________________
> >>> XCON mailing list
> >>> XCON@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/xcon
> >>
> >
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
> >


From lorenzo@meetecho.com  Thu Jun 10 04:02:29 2010
Return-Path: <lorenzo@meetecho.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F51A3A6A04 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 04:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.581
X-Spam-Level: 
X-Spam-Status: No, score=0.581 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GGH4oFlochV4 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 04:02:27 -0700 (PDT)
Received: from smtplq03.aruba.it (smtplq-out18.aruba.it [62.149.158.38]) by core3.amsl.com (Postfix) with SMTP id 91B8B3A69BF for <xcon@ietf.org>; Thu, 10 Jun 2010 04:02:26 -0700 (PDT)
Received: (qmail 22799 invoked by uid 89); 10 Jun 2010 11:02:08 -0000
Received: from unknown (HELO smtp3.aruba.it) (62.149.128.201) by smtplq03.aruba.it with SMTP; 10 Jun 2010 11:02:08 -0000
Received: (qmail 14746 invoked by uid 89); 10 Jun 2010 11:02:08 -0000
Received: from unknown (HELO lminiero-acer) (lorenzo@meetecho.com@143.225.229.188) by smtp3.ad.aruba.it with SMTP; 10 Jun 2010 11:02:08 -0000
Date: Thu, 10 Jun 2010 13:00:09 +0200
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: "Roni Even" <ron.even.tlv@gmail.com>
Message-Id: <20100610130009.1f1fbb03.lorenzo@meetecho.com>
In-Reply-To: <4c107733.df0ce30a.21ca.15cc@mx.google.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4c107733.df0ce30a.21ca.15cc@mx.google.com>
Organization: Meetecho
X-Mailer: Sylpheed 2.6.0 (GTK+ 2.16.6; i586-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtp3.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq03.aruba.it 1.6.2 0/1000/N
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, xcon@ietf.org, 'Tom Kristensen' <tom.kristensen@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 11:02:29 -0000

Hi all,

with respect to this topic, I think there are many issues implementers
have to face when bringing IETF solutions to the real world. We found
ourselves many times in a situation in which some kind of work-around
had to be devised in order to let things work properly. Just to cite a
couple of examples, with BFCP we had to find a way to let it work in a
distributed conferencing scenario (which is far from easy, given the
intrinsic centralized model behind such protocol). In such case, we
decided to encapsulate BFCP messages in the body of XMPP
server-to-server packets (see the XCON-DCON Synchronization Protocol in
draft-romano-dcon-xdsp-reqs-06 for the details) and then even devised
a BFCP-XMPP gateway for such a purpose. With respect to the NAT
traversal issue, we also implemented an HTTP encapsulation. Moving
further we even conceived a DTMF-based frontend to BFCP ;) and also
almost thought about a BFCP-over-RTP approach.

That said, I nevertheless agree with Keith on the discussion. Those
problems may be common to other TCP-based protocols as well, and as such
a generic solution (generic TCP over UDP, for instance, or anything
else) may be a much better approach than doing a protocol specific
patch. Besides, whatever the solution, it should also take care of how
the negotiation of such channels would be affected (as is the
case of RFC4583 for BFCP, which the proposed draft actually does).

As Keith already suggested, DISPATCH may be a much better place to
discuss this issue: DISPATCH is where we'll also propose the above
mentioned DCON work.

Lorenzo



On Thu, 10 Jun 2010 08:22:55 +0300
"Roni Even" <ron.even.tlv@gmail.com> wrote:

> Hi  Keith,
> 
> I think that the IETF is trying to design protocols that will work over the
> Internet and also to enable interoperability between independent
> implementations. 
>  
> In the BFCP case the shipping implementations support TCP as the transport
> protocol but they encountered issues when running over the Internet due to
> devices like SBCs and due to lack of support for TCP media relay or ICE-TCP
> [I-D.ietf-mmusic-ice-tcp].  
> When implementations looked at how to address the issue, the
> interoperability went away since there is no fall back solution for this
> real life case. Some did a fall back to HTTP and some did to UDP but not in
> an interoperable way.
> 
> In order to achieve interoperability, this draft is trying to extend the
> current BFCP. It is not suggesting to replace TCP but to keep TCP as the
> mandatory transport and use UDP as fallback if unable to establish TCP
> connection. 
> 
> As for security, if the topic will be adopted the solution will be updated
> to use DTLS as the transport for BFCP.
> 
> I hope that people will read the draft and look at the objectives and the
> proposed solution.
> 
> 
> BTW: This is a problem for client to client media connections over TCP and
> my understanding is that RTSP offers to use both TCP and UDP since both are
> specified. Since BFCP is not a payload but is running in parallel to the RTP
> payload (for the point to point calls or MCU based multipoint) it needs
> similar transport options.
> 
> Thanks
> Roni Even
> 
> 
> 
> 
> > -----Original Message-----
> > From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
> > Sent: Thursday, June 10, 2010 1:54 AM
> > To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> > Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen'; xcon@ietf.org
> > Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > 
> > What you are essentially saying is that all protocols in the future
> > that need reliable transport, as BFCP does, have to design in their own
> > reliable transport element so they can use UDP. This is not a BFCP
> > specific issue.
> > 
> > I find that an unacceptable direction for IETF to be heading in.
> > 
> > I would also note that you are also asking for adoption of a document
> > that cannot in its current form meet the security requirements of the
> > original RFC.
> > 
> > regards
> > 
> > Keith
> > 
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > Sent: Wednesday, June 09, 2010 1:40 PM
> > > To: 'Richard L. Barnes'; 'Tom Kristensen'
> > > Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> > > 'Tom Kristensen'; xcon@ietf.org
> > > Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > >
> > > Richard,
> > > The BFCP I used as a presentation token for video
> > > conferencing. What the implementers found out that TCP does
> > > not work in real networks due to Session border controllers
> > > not supporting TCP as used in BFCP.
> > > This is why in products they try to establish TCP connection
> > > and if fails tries UDP.
> > > The video conferencing vendors participating in the IMTC sip
> > > parity activity group defined an interoperability profile
> > > that references this option Roni Even
> > >
> > > > -----Original Message-----
> > > > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > > On Behalf
> > > > Of Richard L. Barnes
> > > > Sent: Wednesday, June 09, 2010 3:34 PM
> > > > To: Tom Kristensen
> > > > Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> > > > Kristensen; xcon@ietf.org
> > > > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > > >
> > > > Tom and others who are interested in this draft:
> > > >
> > > > For those who are relatively new here: Could you summarize why you
> > > > think this draft is needed?  What requirement does it meet
> > > that BFCP
> > > > doesn't right now?
> > > >
> > > > Thanks,
> > > > --Richard
> > > >
> > > >
> > > >
> > > >
> > > > On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> > > >
> > > > > The UDP/BFCP draft has been presented and discussed in
> > > two or three
> > > > > IETF XCON sessions. No objection to the work being
> > > carried on, just
> > > > > that adoption as WG item was postponed until the draft was more
> > > > > complete. (This has been delayed of various reasons, but
> > > the authors
> > > > > believe the -02 version in question here should be ready for
> > > > > adoption).
> > > > >
> > > > > The "current status of consensus" might be valid for some, but
> > > > > participants in the XCON sessions and the minutes of meeting show
> > > > > progress away from that initial consensus.
> > > > >
> > > > > I believe Ott's concerns are either dealt with or at
> > > least mentioned
> > > > > in the draft. Arrest me if I'm wrong.
> > > > >
> > > > > -- Tom
> > > > >
> > > > > On 9 June 2010 13:20, DRAGE, Keith (Keith)
> > > > > <keith.drage@alcatel-lucent.com> wrote:
> > > > >> We made an explicit decision in the original draft that
> > > UDP was not
> > > > >> required, not that we would do it later. That as far as I am
> > > > >> concerned represents the current status of consensus.
> > > > >>
> > > > >> This was done on the basis that we had all seen how UDP
> > > support had
> > > > >> complicated SIP, and we did not want to repeat that issue.
> > > > >>
> > > > >> So this is not continuing the work. The status is an
> > > author draft
> > > > >> which goes against a WG consensus position.
> > > > >>
> > > > >> I believe Georg Ott also expressed some concerns which I did not
> > > > >> see answered on list at all.
> > > > >>
> > > > >> regards
> > > > >>
> > > > >> Keith
> > > > >>
> > > > >>> -----Original Message-----
> > > > >>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
> > > > >>> Behalf Of Roni Even
> > > > >>> Sent: Tuesday, June 08, 2010 7:35 PM
> > > > >>> To: 'Alan Johnston'; 'Tom Kristensen'
> > > > >>> Cc: 'Mark Thompson'; xcon@ietf.org
> > > > >>> Subject: Re: [XCON] WG Adoption?
> > > draft-sandbakken-xcon-bfcp-udp-02
> > > > >>>
> > > > >>> Hi Alan,
> > > > >>> I support this work and think it is urgent to finish it.
> > > > >>> I think that updating BFCP with UDP support is very
> > > important. I
> > > > >>> would like to mention that BFCP is being used in video
> > > > >>> conferencing application and since the implementers encountered
> > > > >>> problems with TCP they use a fall back to UDP.
> > > > >>> We discussed this work in previous IETF meeting and
> > > Gonzalo as far
> > > > >>> as I remember suggested to add it to a BFCP bis draft.
> > > > >>>
> > > > >>> Thanks
> > > > >>> Roni Even
> > > > >>>
> > > > >>>> -----Original Message-----
> > > > >>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > > > >>> On Behalf
> > > > >>>> Of Alan Johnston
> > > > >>>> Sent: Tuesday, June 08, 2010 7:44 PM
> > > > >>>> To: Tom Kristensen
> > > > >>>> Cc: Mark Thompson; xcon@ietf.org
> > > > >>>> Subject: Re: [XCON] WG Adoption?
> > > > >>>> draft-sandbakken-xcon-bfcp-udp-02
> > > > >>>>
> > > > >>>> Tom,
> > > > >>>>
> > > > >>>> Apologies for the delay in replying.  As you know, the
> > > > >>> working group
> > > > >>>> is in the process of completing its final milestones.
> > > > >>>> Publication requests will be issued in the next few
> > > days for the
> > > > >>>> data
> > > > >>> model, CCMP,
> > > > >>>> and the Examples drafts.
> > > > >>>>
> > > > >>>> Taking on any new milestones for the working group
> > > would require:
> > > > >>>> 1. Strong support and interest from working group
> > > participants 2.
> > > > >>>> Approval of our ADs.
> > > > >>>>
> > > > >>>> I haven't seen evidence of either of these at this stage.
> > > > >>>>
> > > > >>>> A possible option is to take this work to DISPATCH, get an
> > > > >>> indication
> > > > >>>> of interests, and get feedback on the best way to move
> > > this work
> > > > >>>> forward.
> > > > >>>>
> > > > >>>> - Alan -
> > > > >>>> co-chair XCON
> > > > >>>>
> > > > >>>>
> > > > >>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > > > >>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> > > > >>> early in
> > > > >>>>> March. No comments received since.
> > > > >>>>>
> > > > >>>>> We'd like guidance on the next steps. First we ask for
> > > > >>> adoption as
> > > > >>>>> WG item. Next step would include the merging process with bis
> > > > >>>>> versions
> > > > >>>> of
> > > > >>>>> RFC 4582 and RFC 4583.
> > > > >>>>>
> > > > >>>>> We'd like to point out that interested parties for this
> > > > >>> work indeed
> > > > >>>>> exist.
> > > > >>>>>
> > > > >>>>> (For the record: Questions was sent to XCON chairs in
> > > > >>> April and May.
> > > > >>>> See
> > > > >>>>> below. No response given. Therefore, this request on
> > > the list.)
> > > > >>>>>
> > > > >>>>> -- Tom
> > > > >>>>>
> > > > >>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > > > >>>>>> Chairs,
> > > > >>>>>>
> > > > >>>>>> Any thoughts or decision on this matter?
> > > > >>>>>>
> > > > >>>>>> Cheers,
> > > > >>>>>> -- Tom
> > > > >>>>>>
> > > > >>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > > > >>>>>>> XCON chairs,
> > > > >>>>>>>
> > > > >>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> > > early in March
> > > > >>>>>>> -
> > > > >>>> well in
> > > > >>>>>>> advance of IETF-77.
> > > > >>>>>>>    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
> > udp
> > > > >>>>>>>
> > > > >>>>>>> No comments received. Neither on XCON WG list, nor
> > > > >>> directly to the
> > > > >>>>>>> authors. Therefore, we ask for adoption of this draft
> > > > >>> as an XCON
> > > > >>>>>>> WG item.
> > > > >>>>>>>
> > > > >>>>>>> -- Tom
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>> _______________________________________________
> > > > >>>> XCON mailing list
> > > > >>>> XCON@ietf.org
> > > > >>>> https://www.ietf.org/mailman/listinfo/xcon
> > > > >>>
> > > > >>> _______________________________________________
> > > > >>> XCON mailing list
> > > > >>> XCON@ietf.org
> > > > >>> https://www.ietf.org/mailman/listinfo/xcon
> > > > >>>
> > > > >> _______________________________________________
> > > > >> XCON mailing list
> > > > >> XCON@ietf.org
> > > > >> https://www.ietf.org/mailman/listinfo/xcon
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > # TANDBERG R&D
> > > > > ## http://www.tandberg.com
> > > > > ### http://folk.uio.no/tomkri/
> > > > > _______________________________________________
> > > > > XCON mailing list
> > > > > XCON@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/xcon
> > > >
> > > > _______________________________________________
> > > > XCON mailing list
> > > > XCON@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/xcon
> > >
> > > =
> 
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
> 


-- 
Lorenzo Miniero
Meetecho s.r.l.
http://www.meetecho.com/

From rbarnes@bbn.com  Thu Jun 10 06:18:41 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D42F43A6936 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 06:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s74ruTHYTQ09 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 06:18:25 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id AB94F3A6999 for <xcon@ietf.org>; Thu, 10 Jun 2010 06:18:21 -0700 (PDT)
Received: from dhcp89-089-146.bbn.com ([128.89.89.146]:61934) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OMheF-000Hlj-FZ; Thu, 10 Jun 2010 09:18:19 -0400
Message-Id: <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: Lorenzo Miniero <lorenzo@meetecho.com>
In-Reply-To: <20100610130009.1f1fbb03.lorenzo@meetecho.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 10 Jun 2010 09:18:12 -0400
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4c107733.df0ce30a.21ca.15cc@mx.google.com> <20100610130009.1f1fbb03.lorenzo@meetecho.com>
X-Mailer: Apple Mail (2.936)
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, xcon@ietf.org, 'Tom Kristensen' <tom.kristensen@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 13:18:42 -0000

<hat type="individual"/>

I tend to agree with Lorenzo that DISPATCH would be a better place to  
have these discussions, especially given that, as far as I can tell  
from this thread, the problem seems to be a general one of NAT  
traversal for TCP.



On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:

> Hi all,
>
> with respect to this topic, I think there are many issues implementers
> have to face when bringing IETF solutions to the real world. We found
> ourselves many times in a situation in which some kind of work-around
> had to be devised in order to let things work properly. Just to cite a
> couple of examples, with BFCP we had to find a way to let it work in a
> distributed conferencing scenario (which is far from easy, given the
> intrinsic centralized model behind such protocol). In such case, we
> decided to encapsulate BFCP messages in the body of XMPP
> server-to-server packets (see the XCON-DCON Synchronization Protocol  
> in
> draft-romano-dcon-xdsp-reqs-06 for the details) and then even devised
> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
> traversal issue, we also implemented an HTTP encapsulation. Moving
> further we even conceived a DTMF-based frontend to BFCP ;) and also
> almost thought about a BFCP-over-RTP approach.
>
> That said, I nevertheless agree with Keith on the discussion. Those
> problems may be common to other TCP-based protocols as well, and as  
> such
> a generic solution (generic TCP over UDP, for instance, or anything
> else) may be a much better approach than doing a protocol specific
> patch. Besides, whatever the solution, it should also take care of how
> the negotiation of such channels would be affected (as is the
> case of RFC4583 for BFCP, which the proposed draft actually does).
>
> As Keith already suggested, DISPATCH may be a much better place to
> discuss this issue: DISPATCH is where we'll also propose the above
> mentioned DCON work.
>
> Lorenzo
>
>
>
> On Thu, 10 Jun 2010 08:22:55 +0300
> "Roni Even" <ron.even.tlv@gmail.com> wrote:
>
>> Hi  Keith,
>>
>> I think that the IETF is trying to design protocols that will work  
>> over the
>> Internet and also to enable interoperability between independent
>> implementations.
>>
>> In the BFCP case the shipping implementations support TCP as the  
>> transport
>> protocol but they encountered issues when running over the Internet  
>> due to
>> devices like SBCs and due to lack of support for TCP media relay or  
>> ICE-TCP
>> [I-D.ietf-mmusic-ice-tcp].
>> When implementations looked at how to address the issue, the
>> interoperability went away since there is no fall back solution for  
>> this
>> real life case. Some did a fall back to HTTP and some did to UDP  
>> but not in
>> an interoperable way.
>>
>> In order to achieve interoperability, this draft is trying to  
>> extend the
>> current BFCP. It is not suggesting to replace TCP but to keep TCP  
>> as the
>> mandatory transport and use UDP as fallback if unable to establish  
>> TCP
>> connection.
>>
>> As for security, if the topic will be adopted the solution will be  
>> updated
>> to use DTLS as the transport for BFCP.
>>
>> I hope that people will read the draft and look at the objectives  
>> and the
>> proposed solution.
>>
>>
>> BTW: This is a problem for client to client media connections over  
>> TCP and
>> my understanding is that RTSP offers to use both TCP and UDP since  
>> both are
>> specified. Since BFCP is not a payload but is running in parallel  
>> to the RTP
>> payload (for the point to point calls or MCU based multipoint) it  
>> needs
>> similar transport options.
>>
>> Thanks
>> Roni Even
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
>>> Sent: Thursday, June 10, 2010 1:54 AM
>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';  
>>> xcon@ietf.org
>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>
>>> What you are essentially saying is that all protocols in the future
>>> that need reliable transport, as BFCP does, have to design in  
>>> their own
>>> reliable transport element so they can use UDP. This is not a BFCP
>>> specific issue.
>>>
>>> I find that an unacceptable direction for IETF to be heading in.
>>>
>>> I would also note that you are also asking for adoption of a  
>>> document
>>> that cannot in its current form meet the security requirements of  
>>> the
>>> original RFC.
>>>
>>> regards
>>>
>>> Keith
>>>
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>>> Sent: Wednesday, June 09, 2010 1:40 PM
>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
>>>> 'Tom Kristensen'; xcon@ietf.org
>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>
>>>> Richard,
>>>> The BFCP I used as a presentation token for video
>>>> conferencing. What the implementers found out that TCP does
>>>> not work in real networks due to Session border controllers
>>>> not supporting TCP as used in BFCP.
>>>> This is why in products they try to establish TCP connection
>>>> and if fails tries UDP.
>>>> The video conferencing vendors participating in the IMTC sip
>>>> parity activity group defined an interoperability profile
>>>> that references this option Roni Even
>>>>
>>>>> -----Original Message-----
>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>> On Behalf
>>>>> Of Richard L. Barnes
>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
>>>>> To: Tom Kristensen
>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
>>>>> Kristensen; xcon@ietf.org
>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>>
>>>>> Tom and others who are interested in this draft:
>>>>>
>>>>> For those who are relatively new here: Could you summarize why you
>>>>> think this draft is needed?  What requirement does it meet
>>>> that BFCP
>>>>> doesn't right now?
>>>>>
>>>>> Thanks,
>>>>> --Richard
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
>>>>>
>>>>>> The UDP/BFCP draft has been presented and discussed in
>>>> two or three
>>>>>> IETF XCON sessions. No objection to the work being
>>>> carried on, just
>>>>>> that adoption as WG item was postponed until the draft was more
>>>>>> complete. (This has been delayed of various reasons, but
>>>> the authors
>>>>>> believe the -02 version in question here should be ready for
>>>>>> adoption).
>>>>>>
>>>>>> The "current status of consensus" might be valid for some, but
>>>>>> participants in the XCON sessions and the minutes of meeting show
>>>>>> progress away from that initial consensus.
>>>>>>
>>>>>> I believe Ott's concerns are either dealt with or at
>>>> least mentioned
>>>>>> in the draft. Arrest me if I'm wrong.
>>>>>>
>>>>>> -- Tom
>>>>>>
>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
>>>>>> <keith.drage@alcatel-lucent.com> wrote:
>>>>>>> We made an explicit decision in the original draft that
>>>> UDP was not
>>>>>>> required, not that we would do it later. That as far as I am
>>>>>>> concerned represents the current status of consensus.
>>>>>>>
>>>>>>> This was done on the basis that we had all seen how UDP
>>>> support had
>>>>>>> complicated SIP, and we did not want to repeat that issue.
>>>>>>>
>>>>>>> So this is not continuing the work. The status is an
>>>> author draft
>>>>>>> which goes against a WG consensus position.
>>>>>>>
>>>>>>> I believe Georg Ott also expressed some concerns which I did not
>>>>>>> see answered on list at all.
>>>>>>>
>>>>>>> regards
>>>>>>>
>>>>>>> Keith
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
>>>>>>>> Behalf Of Roni Even
>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>
>>>>>>>> Hi Alan,
>>>>>>>> I support this work and think it is urgent to finish it.
>>>>>>>> I think that updating BFCP with UDP support is very
>>>> important. I
>>>>>>>> would like to mention that BFCP is being used in video
>>>>>>>> conferencing application and since the implementers encountered
>>>>>>>> problems with TCP they use a fall back to UDP.
>>>>>>>> We discussed this work in previous IETF meeting and
>>>> Gonzalo as far
>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Roni Even
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>>>> On Behalf
>>>>>>>>> Of Alan Johnston
>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>>>>>>>>> To: Tom Kristensen
>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>
>>>>>>>>> Tom,
>>>>>>>>>
>>>>>>>>> Apologies for the delay in replying.  As you know, the
>>>>>>>> working group
>>>>>>>>> is in the process of completing its final milestones.
>>>>>>>>> Publication requests will be issued in the next few
>>>> days for the
>>>>>>>>> data
>>>>>>>> model, CCMP,
>>>>>>>>> and the Examples drafts.
>>>>>>>>>
>>>>>>>>> Taking on any new milestones for the working group
>>>> would require:
>>>>>>>>> 1. Strong support and interest from working group
>>>> participants 2.
>>>>>>>>> Approval of our ADs.
>>>>>>>>>
>>>>>>>>> I haven't seen evidence of either of these at this stage.
>>>>>>>>>
>>>>>>>>> A possible option is to take this work to DISPATCH, get an
>>>>>>>> indication
>>>>>>>>> of interests, and get feedback on the best way to move
>>>> this work
>>>>>>>>> forward.
>>>>>>>>>
>>>>>>>>> - Alan -
>>>>>>>>> co-chair XCON
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>>>>>>>> early in
>>>>>>>>>> March. No comments received since.
>>>>>>>>>>
>>>>>>>>>> We'd like guidance on the next steps. First we ask for
>>>>>>>> adoption as
>>>>>>>>>> WG item. Next step would include the merging process with bis
>>>>>>>>>> versions
>>>>>>>>> of
>>>>>>>>>> RFC 4582 and RFC 4583.
>>>>>>>>>>
>>>>>>>>>> We'd like to point out that interested parties for this
>>>>>>>> work indeed
>>>>>>>>>> exist.
>>>>>>>>>>
>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
>>>>>>>> April and May.
>>>>>>>>> See
>>>>>>>>>> below. No response given. Therefore, this request on
>>>> the list.)
>>>>>>>>>>
>>>>>>>>>> -- Tom
>>>>>>>>>>
>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>>>>>>>>>>> Chairs,
>>>>>>>>>>>
>>>>>>>>>>> Any thoughts or decision on this matter?
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>> -- Tom
>>>>>>>>>>>
>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>>>>>>>>>>> XCON chairs,
>>>>>>>>>>>>
>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
>>>> early in March
>>>>>>>>>>>> -
>>>>>>>>> well in
>>>>>>>>>>>> advance of IETF-77.
>>>>>>>>>>>>   http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
>>> udp
>>>>>>>>>>>>
>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
>>>>>>>> directly to the
>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
>>>>>>>> as an XCON
>>>>>>>>>>>> WG item.
>>>>>>>>>>>>
>>>>>>>>>>>> -- Tom
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> XCON mailing list
>>>>>>>>> XCON@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> XCON mailing list
>>>>>>>> XCON@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> XCON mailing list
>>>>>>> XCON@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> # TANDBERG R&D
>>>>>> ## http://www.tandberg.com
>>>>>> ### http://folk.uio.no/tomkri/
>>>>>> _______________________________________________
>>>>>> XCON mailing list
>>>>>> XCON@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>
>>>>> _______________________________________________
>>>>> XCON mailing list
>>>>> XCON@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>
>>>> =
>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>>
>
>
> -- 
> Lorenzo Miniero
> Meetecho s.r.l.
> http://www.meetecho.com/


From ron.even.tlv@gmail.com  Thu Jun 10 06:52:44 2010
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F261128C0EF for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 06:52:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkoUVjUY0GPT for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 06:52:41 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 1377528C0EA for <xcon@ietf.org>; Thu, 10 Jun 2010 06:52:40 -0700 (PDT)
Received: by wya21 with SMTP id 21so672439wya.31 for <xcon@ietf.org>; Thu, 10 Jun 2010 06:52:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=C+ewtc08g/xng4t2ZTxbE9jRRJyAWN/A6TkymH1MCug=; b=qPk2E21tL9nQmFmX3NFVeCL0MieeKnTT3M/qHdEcsQCdpAW92lEnS/tfIif54ac/Af dxkWM6hVwY6XKUXGkD4aJ+9Vc9jMhV4zGy0YKvl6w7f2CrcY7evjpbmHfP+WYo6ffxUO ZpY9G1+uzjY0AcJG6dfZpCvrQ1ufKoV/rUw9U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=c3WyWV5bFEMQfgi45auLPgII2TA/oBqNz4YwxZ7OxpTe+gBHqBDUMv58pA2jsDnMwK Rer4Dk/NpNAbBa15jiLB6T6+TV8anpAHhp1nu6yCnP2HT6cg/bblGWxIb5e8gDQaBHX1 UKV0W0aSaDgEMGFBPl5DRUTnnMdX9R6NuOIg0=
Received: by 10.227.146.210 with SMTP id i18mr246990wbv.41.1276176589168; Thu, 10 Jun 2010 06:29:49 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-176-22-234.red.bezeqint.net [79.176.22.234]) by mx.google.com with ESMTPS id t15sm61305wbc.5.2010.06.10.06.29.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Jun 2010 06:29:47 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Lorenzo Miniero'" <lorenzo@meetecho.com>
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost>	<4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>	<59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>	<4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<4c107733.df0ce30a.21ca.15cc@mx.google.com> <20100610130009.1f1fbb03.lorenzo@meetecho.com>
In-Reply-To: <20100610130009.1f1fbb03.lorenzo@meetecho.com>
Date: Thu, 10 Jun 2010 16:27:31 +0300
Message-ID: <4c10e8cb.4f1ee30a.2e30.00b0@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsIjGAL63LBz8XXSm2Ca/dlrfw91QAEs84Q
Content-Language: en-us
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, xcon@ietf.org, 'Tom Kristensen' <tom.kristensen@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 13:52:44 -0000

Lorenzo,
Your email emphasis the urgency of a solution, you mention that you
encapsulate BFCP in HTTP for NAT traversal. In your own solution it works.
The problem is with interoperability between different implementations and
the current state is that for the same application people choose different
approaches for fall back if TCP fail.

Again this may look like a general problem but the so far there are no
solutions if though it is being discussed. We can go on discussing ICE TCP
and TCP relays other directions but this should not stop us from solving
current problems.

Part of the UDP fall back is also to address the reliability of the protocol
this requires specific solution per protocol. I think that this work is
within the scope of XCON since the BFCP protocol design in the WG is not
finished (Gonzalo agrees that the use case where the BFCP server is not in
the public Internet was not considered when designing the protocol) so we
should finish BFCP in XCON
Roni Even 

> -----Original Message-----
> From: Lorenzo Miniero [mailto:lorenzo@meetecho.com]
> Sent: Thursday, June 10, 2010 2:00 PM
> To: Roni Even
> Cc: 'DRAGE, Keith (Keith)'; 'Richard L. Barnes'; 'Tom Kristensen';
> 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen'; xcon@ietf.org
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> 
> Hi all,
> 
> with respect to this topic, I think there are many issues implementers
> have to face when bringing IETF solutions to the real world. We found
> ourselves many times in a situation in which some kind of work-around
> had to be devised in order to let things work properly. Just to cite a
> couple of examples, with BFCP we had to find a way to let it work in a
> distributed conferencing scenario (which is far from easy, given the
> intrinsic centralized model behind such protocol). In such case, we
> decided to encapsulate BFCP messages in the body of XMPP
> server-to-server packets (see the XCON-DCON Synchronization Protocol in
> draft-romano-dcon-xdsp-reqs-06 for the details) and then even devised
> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
> traversal issue, we also implemented an HTTP encapsulation. Moving
> further we even conceived a DTMF-based frontend to BFCP ;) and also
> almost thought about a BFCP-over-RTP approach.
> 
> That said, I nevertheless agree with Keith on the discussion. Those
> problems may be common to other TCP-based protocols as well, and as
> such
> a generic solution (generic TCP over UDP, for instance, or anything
> else) may be a much better approach than doing a protocol specific
> patch. Besides, whatever the solution, it should also take care of how
> the negotiation of such channels would be affected (as is the
> case of RFC4583 for BFCP, which the proposed draft actually does).
> 
> As Keith already suggested, DISPATCH may be a much better place to
> discuss this issue: DISPATCH is where we'll also propose the above
> mentioned DCON work.
> 
> Lorenzo
> 
> 
> 
> On Thu, 10 Jun 2010 08:22:55 +0300
> "Roni Even" <ron.even.tlv@gmail.com> wrote:
> 
> > Hi  Keith,
> >
> > I think that the IETF is trying to design protocols that will work
> over the
> > Internet and also to enable interoperability between independent
> > implementations.
> >
> > In the BFCP case the shipping implementations support TCP as the
> transport
> > protocol but they encountered issues when running over the Internet
> due to
> > devices like SBCs and due to lack of support for TCP media relay or
> ICE-TCP
> > [I-D.ietf-mmusic-ice-tcp].
> > When implementations looked at how to address the issue, the
> > interoperability went away since there is no fall back solution for
> this
> > real life case. Some did a fall back to HTTP and some did to UDP but
> not in
> > an interoperable way.
> >
> > In order to achieve interoperability, this draft is trying to extend
> the
> > current BFCP. It is not suggesting to replace TCP but to keep TCP as
> the
> > mandatory transport and use UDP as fallback if unable to establish
> TCP
> > connection.
> >
> > As for security, if the topic will be adopted the solution will be
> updated
> > to use DTLS as the transport for BFCP.
> >
> > I hope that people will read the draft and look at the objectives and
> the
> > proposed solution.
> >
> >
> > BTW: This is a problem for client to client media connections over
> TCP and
> > my understanding is that RTSP offers to use both TCP and UDP since
> both are
> > specified. Since BFCP is not a payload but is running in parallel to
> the RTP
> > payload (for the point to point calls or MCU based multipoint) it
> needs
> > similar transport options.
> >
> > Thanks
> > Roni Even
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
> > > Sent: Thursday, June 10, 2010 1:54 AM
> > > To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> > > Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
> xcon@ietf.org
> > > Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > >
> > > What you are essentially saying is that all protocols in the future
> > > that need reliable transport, as BFCP does, have to design in their
> own
> > > reliable transport element so they can use UDP. This is not a BFCP
> > > specific issue.
> > >
> > > I find that an unacceptable direction for IETF to be heading in.
> > >
> > > I would also note that you are also asking for adoption of a
> document
> > > that cannot in its current form meet the security requirements of
> the
> > > original RFC.
> > >
> > > regards
> > >
> > > Keith
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > Sent: Wednesday, June 09, 2010 1:40 PM
> > > > To: 'Richard L. Barnes'; 'Tom Kristensen'
> > > > Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> > > > 'Tom Kristensen'; xcon@ietf.org
> > > > Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> 02
> > > >
> > > > Richard,
> > > > The BFCP I used as a presentation token for video
> > > > conferencing. What the implementers found out that TCP does
> > > > not work in real networks due to Session border controllers
> > > > not supporting TCP as used in BFCP.
> > > > This is why in products they try to establish TCP connection
> > > > and if fails tries UDP.
> > > > The video conferencing vendors participating in the IMTC sip
> > > > parity activity group defined an interoperability profile
> > > > that references this option Roni Even
> > > >
> > > > > -----Original Message-----
> > > > > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > > > On Behalf
> > > > > Of Richard L. Barnes
> > > > > Sent: Wednesday, June 09, 2010 3:34 PM
> > > > > To: Tom Kristensen
> > > > > Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> > > > > Kristensen; xcon@ietf.org
> > > > > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-
> udp-02
> > > > >
> > > > > Tom and others who are interested in this draft:
> > > > >
> > > > > For those who are relatively new here: Could you summarize why
> you
> > > > > think this draft is needed?  What requirement does it meet
> > > > that BFCP
> > > > > doesn't right now?
> > > > >
> > > > > Thanks,
> > > > > --Richard
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> > > > >
> > > > > > The UDP/BFCP draft has been presented and discussed in
> > > > two or three
> > > > > > IETF XCON sessions. No objection to the work being
> > > > carried on, just
> > > > > > that adoption as WG item was postponed until the draft was
> more
> > > > > > complete. (This has been delayed of various reasons, but
> > > > the authors
> > > > > > believe the -02 version in question here should be ready for
> > > > > > adoption).
> > > > > >
> > > > > > The "current status of consensus" might be valid for some,
> but
> > > > > > participants in the XCON sessions and the minutes of meeting
> show
> > > > > > progress away from that initial consensus.
> > > > > >
> > > > > > I believe Ott's concerns are either dealt with or at
> > > > least mentioned
> > > > > > in the draft. Arrest me if I'm wrong.
> > > > > >
> > > > > > -- Tom
> > > > > >
> > > > > > On 9 June 2010 13:20, DRAGE, Keith (Keith)
> > > > > > <keith.drage@alcatel-lucent.com> wrote:
> > > > > >> We made an explicit decision in the original draft that
> > > > UDP was not
> > > > > >> required, not that we would do it later. That as far as I am
> > > > > >> concerned represents the current status of consensus.
> > > > > >>
> > > > > >> This was done on the basis that we had all seen how UDP
> > > > support had
> > > > > >> complicated SIP, and we did not want to repeat that issue.
> > > > > >>
> > > > > >> So this is not continuing the work. The status is an
> > > > author draft
> > > > > >> which goes against a WG consensus position.
> > > > > >>
> > > > > >> I believe Georg Ott also expressed some concerns which I did
> not
> > > > > >> see answered on list at all.
> > > > > >>
> > > > > >> regards
> > > > > >>
> > > > > >> Keith
> > > > > >>
> > > > > >>> -----Original Message-----
> > > > > >>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> On
> > > > > >>> Behalf Of Roni Even
> > > > > >>> Sent: Tuesday, June 08, 2010 7:35 PM
> > > > > >>> To: 'Alan Johnston'; 'Tom Kristensen'
> > > > > >>> Cc: 'Mark Thompson'; xcon@ietf.org
> > > > > >>> Subject: Re: [XCON] WG Adoption?
> > > > draft-sandbakken-xcon-bfcp-udp-02
> > > > > >>>
> > > > > >>> Hi Alan,
> > > > > >>> I support this work and think it is urgent to finish it.
> > > > > >>> I think that updating BFCP with UDP support is very
> > > > important. I
> > > > > >>> would like to mention that BFCP is being used in video
> > > > > >>> conferencing application and since the implementers
> encountered
> > > > > >>> problems with TCP they use a fall back to UDP.
> > > > > >>> We discussed this work in previous IETF meeting and
> > > > Gonzalo as far
> > > > > >>> as I remember suggested to add it to a BFCP bis draft.
> > > > > >>>
> > > > > >>> Thanks
> > > > > >>> Roni Even
> > > > > >>>
> > > > > >>>> -----Original Message-----
> > > > > >>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > > > > >>> On Behalf
> > > > > >>>> Of Alan Johnston
> > > > > >>>> Sent: Tuesday, June 08, 2010 7:44 PM
> > > > > >>>> To: Tom Kristensen
> > > > > >>>> Cc: Mark Thompson; xcon@ietf.org
> > > > > >>>> Subject: Re: [XCON] WG Adoption?
> > > > > >>>> draft-sandbakken-xcon-bfcp-udp-02
> > > > > >>>>
> > > > > >>>> Tom,
> > > > > >>>>
> > > > > >>>> Apologies for the delay in replying.  As you know, the
> > > > > >>> working group
> > > > > >>>> is in the process of completing its final milestones.
> > > > > >>>> Publication requests will be issued in the next few
> > > > days for the
> > > > > >>>> data
> > > > > >>> model, CCMP,
> > > > > >>>> and the Examples drafts.
> > > > > >>>>
> > > > > >>>> Taking on any new milestones for the working group
> > > > would require:
> > > > > >>>> 1. Strong support and interest from working group
> > > > participants 2.
> > > > > >>>> Approval of our ADs.
> > > > > >>>>
> > > > > >>>> I haven't seen evidence of either of these at this stage.
> > > > > >>>>
> > > > > >>>> A possible option is to take this work to DISPATCH, get an
> > > > > >>> indication
> > > > > >>>> of interests, and get feedback on the best way to move
> > > > this work
> > > > > >>>> forward.
> > > > > >>>>
> > > > > >>>> - Alan -
> > > > > >>>> co-chair XCON
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > > > > >>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> > > > > >>> early in
> > > > > >>>>> March. No comments received since.
> > > > > >>>>>
> > > > > >>>>> We'd like guidance on the next steps. First we ask for
> > > > > >>> adoption as
> > > > > >>>>> WG item. Next step would include the merging process with
> bis
> > > > > >>>>> versions
> > > > > >>>> of
> > > > > >>>>> RFC 4582 and RFC 4583.
> > > > > >>>>>
> > > > > >>>>> We'd like to point out that interested parties for this
> > > > > >>> work indeed
> > > > > >>>>> exist.
> > > > > >>>>>
> > > > > >>>>> (For the record: Questions was sent to XCON chairs in
> > > > > >>> April and May.
> > > > > >>>> See
> > > > > >>>>> below. No response given. Therefore, this request on
> > > > the list.)
> > > > > >>>>>
> > > > > >>>>> -- Tom
> > > > > >>>>>
> > > > > >>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > > > > >>>>>> Chairs,
> > > > > >>>>>>
> > > > > >>>>>> Any thoughts or decision on this matter?
> > > > > >>>>>>
> > > > > >>>>>> Cheers,
> > > > > >>>>>> -- Tom
> > > > > >>>>>>
> > > > > >>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > > > > >>>>>>> XCON chairs,
> > > > > >>>>>>>
> > > > > >>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> > > > early in March
> > > > > >>>>>>> -
> > > > > >>>> well in
> > > > > >>>>>>> advance of IETF-77.
> > > > > >>>>>>>    http://tools.ietf.org/html/draft-sandbakken-xcon-
> bfcp-
> > > udp
> > > > > >>>>>>>
> > > > > >>>>>>> No comments received. Neither on XCON WG list, nor
> > > > > >>> directly to the
> > > > > >>>>>>> authors. Therefore, we ask for adoption of this draft
> > > > > >>> as an XCON
> > > > > >>>>>>> WG item.
> > > > > >>>>>>>
> > > > > >>>>>>> -- Tom
> > > > > >>>>>>
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>> _______________________________________________
> > > > > >>>> XCON mailing list
> > > > > >>>> XCON@ietf.org
> > > > > >>>> https://www.ietf.org/mailman/listinfo/xcon
> > > > > >>>
> > > > > >>> _______________________________________________
> > > > > >>> XCON mailing list
> > > > > >>> XCON@ietf.org
> > > > > >>> https://www.ietf.org/mailman/listinfo/xcon
> > > > > >>>
> > > > > >> _______________________________________________
> > > > > >> XCON mailing list
> > > > > >> XCON@ietf.org
> > > > > >> https://www.ietf.org/mailman/listinfo/xcon
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > # TANDBERG R&D
> > > > > > ## http://www.tandberg.com
> > > > > > ### http://folk.uio.no/tomkri/
> > > > > > _______________________________________________
> > > > > > XCON mailing list
> > > > > > XCON@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/xcon
> > > > >
> > > > > _______________________________________________
> > > > > XCON mailing list
> > > > > XCON@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/xcon
> > > >
> > > > =
> >
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
> >
> 
> 
> --
> Lorenzo Miniero
> Meetecho s.r.l.
> http://www.meetecho.com/


From spromano@unina.it  Thu Jun 10 07:00:00 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BFB43A6A21 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.882
X-Spam-Level: *
X-Spam-Status: No, score=1.882 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rpp4zRNi9JOT for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 06:59:58 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id 49F9F3A6A0C for <xcon@ietf.org>; Thu, 10 Jun 2010 06:59:58 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.0/8.14.0) with ESMTP id o5ADxs7l023932 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 15:59:54 +0200
Message-ID: <4C10EFDA.8050601@unina.it>
Date: Thu, 10 Jun 2010 15:59:54 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Duddy, Sean (Sean)" <duddy@avaya.com>
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com><20100426201045.8x0hgw8rkkw488cs@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F710125F7E5@306900ANEX2.global.avaya.com>	<4408C6EC74CC3D42824FD68FDA8E8F710125F7EB@306900ANEX2.global.avaya.com> <4408C6EC74CC3D42824FD68FDA8E8F710125FC0A@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125FC0A@306900ANEX2.global.avaya.com>
Content-Type: multipart/alternative; boundary="------------060507010305000600030407"
Cc: xcon@ietf.org
Subject: Re: [XCON] I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 14:00:00 -0000

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

Hi Sean,

the use case you are referring to is explained in the draft. See 
sections 3.2 and 5.3.6 in draft-ietf-xcon-ccmp-07.

Do you agree this is a potential use case?

Simon



Il 04/06/2010 16.20, Duddy, Sean (Sean) ha scritto:
> Hi,
>     I see there is a inconsistency between the constraints on the 
> request and response, see the highlighted item below:-
> Is there a use case where a request would not have a confUserID?
> <xs:complexType abstract="true"
>                   name="ccmp-request-message-type">
> <xs:sequence>
> <xs:element name="subject" type="subject-type"
>                       minOccurs="0" maxOccurs="1" />
> <xs:element name="confUserID" type="xs:string"
>                       minOccurs="0" maxOccurs="1" />
> <xs:element name="confObjID" type="xs:string"
>                       minOccurs="0" maxOccurs="1" />
> <xs:element name="operation" type="operationType"
>                       minOccurs="0" maxOccurs="1" />
> <xs:element name="conference-password" type="xs:string"
>                       minOccurs="0" maxOccurs="1" />
> <xs:any namespace="##other" processContents="lax"
>                  minOccurs="0" maxOccurs="unbounded"/>
> </xs:sequence>
> <xs:anyAttribute namespace="##any" processContents="lax"/>
> </xs:complexType>
> <xs:complexType abstract="true" name="ccmp-response-message-type">
> <xs:sequence>
> <xs:element name="confUserID" type="xs:string"
>                       minOccurs="1" maxOccurs="1" />
> <xs:element name="confObjID" type="xs:string"
>                       minOccurs="0" maxOccurs="1" />
> <xs:element name="operation" minOccurs="0"
>                       maxOccurs="1" />
> <xs:element ref="response-code" minOccurs="1"
>                       maxOccurs="1" />
> <xs:element name="response-string" type="xs:string"
>                       minOccurs="0" maxOccurs="1" />
> <xs:element name="version" type="xs:positiveInteger"
>                       minOccurs="0" maxOccurs="1" />
> <xs:any namespace="##other" processContents="lax"
>                       minOccurs="0" maxOccurs="unbounded"/>
> </xs:sequence>
> <xs:anyAttribute namespace="##any" processContents="lax"/>
> </xs:complexType>
>
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>    

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



--------------060507010305000600030407
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Sean,<br>
<br>
the use case you are referring to is explained in the draft. See
sections 3.2 and 5.3.6 in draft-ietf-xcon-ccmp-07.<br>
<br>
Do you agree this is a potential use case?<br>
<br>
Simon<br>
<br>
<br>
<br>
Il 04/06/2010 16.20, Duddy, Sean (Sean) ha scritto:
<blockquote
 cite="mid:4408C6EC74CC3D42824FD68FDA8E8F710125FC0A@306900ANEX2.global.avaya.com"
 type="cite">
  <title></title>
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta content="MSHTML 6.00.2900.3676" name="GENERATOR">
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010">Hi,</span></font></font></font></div>
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010">&nbsp;&nbsp;&nbsp;&nbsp;I see there is a inconsistency between
the constraints on the request and response, see the <font
 color="#ff0000">highlighted</font> item below:-</span></font></font></font></div>
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010">Is there a use case where a request would
not have a confUserID?</span></font></font></font></div>
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010">&nbsp;</span></font></font></font></div>
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010"></span></font></font></font>&nbsp;</div>
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010">&nbsp;</span>&nbsp; &lt;xs:complexType abstract="true"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; name="ccmp-request-message-type"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="subject" type="subject-type"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font color="#ff0000">&lt;xs:element name="confUserID"
type="xs:string"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="1" /&gt;<br>
  </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="confObjID" type="xs:string"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="operation" type="operationType"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="conference-password" type="xs:string"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:any namespace="##other" processContents="lax"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="unbounded"/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:anyAttribute namespace="##any" processContents="lax"/&gt;<br>
&lt;/xs:complexType&gt;<span class="814152114-04062010">&nbsp;</span></font></font></font></div>
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010"></span></font></font></font>&nbsp;</div>
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010"></span></font></font></font>&nbsp;</div>
  <div><font face="Arial"><font color="#0000ff"><font size="2"><span
 class="814152114-04062010">&lt;xs:complexType abstract="true"
name="ccmp-response-message-type"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="confUserID" type="xs:string"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="1" maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="confObjID" type="xs:string"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="operation" minOccurs="0"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element ref="response-code" minOccurs="1"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="response-string" type="xs:string"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:element name="version" type="xs:positiveInteger"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="1" /&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:any namespace="##other" processContents="lax"<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; minOccurs="0" maxOccurs="unbounded"/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xs:sequence&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xs:anyAttribute namespace="##any" processContents="lax"/&gt;<br>
&nbsp; &lt;/xs:complexType&gt;&nbsp;</span></font></font></font></div>
  <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
XCON mailing list
<a class="moz-txt-link-abbreviated" href="mailto:XCON@ietf.org">XCON@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/xcon">https://www.ietf.org/mailman/listinfo/xcon</a>
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
                            _\\|//_
                            ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    Simon Pietro Romano
              Universita' di Napoli Federico II
                 Computer Science Department 
        Phone: +39 081 7683823 -- Fax: +39 081 7684219
                e-mail: <a class="moz-txt-link-abbreviated" href="mailto:spromano@unina.it">spromano@unina.it</a>
          <a class="moz-txt-link-freetext" href="http://www.comics.unina.it/simonpietro.romano">http://www.comics.unina.it/simonpietro.romano</a>

    &lt;&lt;Molti mi dicono che lo scoraggiamento &egrave; l'alibi degli 
   idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. Magritte.
                         oooO
   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                          \ (    (   )
                           \_)    ) /
                                 (_/

</pre>
</body>
</html>

--------------060507010305000600030407--

From spromano@unina.it  Thu Jun 10 07:02:05 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 257D428C0EF for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.581
X-Spam-Level: 
X-Spam-Status: No, score=0.581 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1esvg4N6kSOy for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:02:04 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by core3.amsl.com (Postfix) with ESMTP id D9A3928C101 for <xcon@ietf.org>; Thu, 10 Jun 2010 07:02:03 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp1.unina.it (8.14.0/8.14.0) with ESMTP id o5AE20SR015078 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 16:02:01 +0200
Message-ID: <4C10F058.1010906@unina.it>
Date: Thu, 10 Jun 2010 16:02:00 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Duddy, Sean (Sean)" <duddy@avaya.com>
References: <4408C6EC74CC3D42824FD68FDA8E8F710115C2D0@306900ANEX2.global.avaya.com><20100426115834.lhvudl29s4kk8w40@webmail.unina.it><4408C6EC74CC3D42824FD68FDA8E8F71011BB4B8@306900ANEX2.global.avaya.com> <20100426201045.8x0hgw8rkkw488cs@webmail.unina.it> <4408C6EC74CC3D42824FD68FDA8E8F710125F6B1@306900ANEX2.global.avaya.com>
In-Reply-To: <4408C6EC74CC3D42824FD68FDA8E8F710125F6B1@306900ANEX2.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: xcon@ietf.org
Subject: Re: [XCON] I-D Action:draft-ietf-xcon-ccmp-07.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 14:02:05 -0000

Sean,

I would say it should have a minOccurs=0 (e.g. in retrieve messages...), 
but a maxOccurs=1, as you are suggesting.

What do you think?

Simon

Il 31/05/2010 16.47, Duddy, Sean (Sean) ha scritto:
> Hi Simon,
> 	Should the userInfo element of
>
>   <xs:complexType name="userRequestType">
>         <xs:sequence>
>             <xs:element name="userInfo"
>                         type="info:user-type" minOccurs="0" />
>             <xs:any namespace="##other" processContents="lax"
>                     minOccurs="0" maxOccurs="unbounded"/>
>         </xs:sequence>
>         <xs:anyAttribute namespace="##any" processContents="lax"/>
>     </xs:complexType>
>
> have a minOccurs of 1 and a maxOccurs of 1? Is there an example of why
> it can be restricted to 1?
>
> Sean
>    

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From pkyzivat@cisco.com  Thu Jun 10 07:52:51 2010
Return-Path: <pkyzivat@cisco.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 85E913A6A39 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.131
X-Spam-Level: 
X-Spam-Status: No, score=-10.131 tagged_above=-999 required=5 tests=[AWL=0.468, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GrmtK3CWKBfS for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:52:50 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 801703A696E for <xcon@ietf.org>; Thu, 10 Jun 2010 07:52:50 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAO+YEExAZnwN/2dsb2JhbACDHps/caRAiR2RAoEmgwNvBA
X-IronPort-AV: E=Sophos;i="4.53,398,1272844800"; d="scan'208";a="120071501"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 10 Jun 2010 14:52:52 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o5AEqppK004276; Thu, 10 Jun 2010 14:52:51 GMT
Message-ID: <4C10FC3F.6020205@cisco.com>
Date: Thu, 10 Jun 2010 10:52:47 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Tom Kristensen <tom.kristensen@tandberg.com>
References: <1271757479.26184.8.camel@localhost>	 <1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost>	 <4C0E7332.6080402@gmail.com>	 <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	 <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	 <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>	 <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>	 <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>	 <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	 <4C101FD2.1050704@cisco.com> <1276163549.2832.9.camel@localhost>
In-Reply-To: <1276163549.2832.9.camel@localhost>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "xcon@ietf.org" <xcon@ietf.org>, 'Alan Johnston' <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 14:52:51 -0000

Tom Kristensen wrote:
> On Wed, 2010-06-09 at 19:12 -0400, Paul Kyzivat wrote:
>> DRAGE, Keith (Keith) wrote:
>>> What you are essentially saying is that all protocols in the future that need reliable transport, as BFCP does, have to design in their own reliable transport element so they can use UDP. This is not a BFCP specific issue.
>>>
>>> I find that an unacceptable direction for IETF to be heading in. 
>> I just came across this discussion, and am not entirely briefed on all 
>> its history.
>>
>> Nevertheless I'm inclined to agree with Keith on this.
>> In fact I think the argument being raised in support of this direction 
>> is an even broader one: that no new feature can be added to sip if it 
>> doesn't work through currently deployed SBCs. I really hope we have not 
>> reached that state of affairs.
> 
> I like this kind of argumentation when looking at the problem at hand
> from an ideal point of view. However, we also have to be pragmatic to
> some degree and make useful protocols that works in the actual networks
> existing out there.

Yes, I understand. At some point we must work with what exists.

In the case of SBCs this is a constant problem because they are not an 
entity with well defined behavior. Most of them are configurable to a 
large degree. I don't know if the problems you had were because of lack 
of configurability in the SBCs, or because of some more major lack, such 
as ICE-TCP.

At the least, I don't want "we did *this* because *that* didn't work" to 
be sufficient justification.

For instance, I believe there is very close analogy here to MSRP. Should 
the same concerns cause us to define MSRP-over-UDP?

> Camarillo pointed out a path for discussion in a recent message in this
> thread - and we have had parts of it already in the WG and elsewhere.

I hunted for a message by Gonzalo on this topic without success.

> Some of the alternatives are mentioned in the draft (versions -01 and
> -02).

What section? I couldn't find those either, in -02.

	Thanks,
	Paul

From pkyzivat@cisco.com  Thu Jun 10 07:57:44 2010
Return-Path: <pkyzivat@cisco.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C9303A69F7 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.19
X-Spam-Level: 
X-Spam-Status: No, score=-10.19 tagged_above=-999 required=5 tests=[AWL=0.409,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oChVlODwyQYg for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:57:43 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 713303A6978 for <xcon@ietf.org>; Thu, 10 Jun 2010 07:57:43 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJOaEExAZnwN/2dsb2JhbACeXXGkPZohhRgE
X-IronPort-AV: E=Sophos;i="4.53,398,1272844800"; d="scan'208";a="120209964"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 10 Jun 2010 14:57:45 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o5AEvibn006334; Thu, 10 Jun 2010 14:57:44 GMT
Message-ID: <4C10FD63.6020701@cisco.com>
Date: Thu, 10 Jun 2010 10:57:39 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Tom Kristensen <tom.kristensen@tandberg.com>
References: <1271757479.26184.8.camel@localhost>		<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost>		<4C0E7332.6080402@gmail.com>		<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>		<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>		<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>		<59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>		<4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>		<EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>		<4C101FD2.1050704@cisco.com> <1276163549.2832.9.camel@localhost> <4C10FC3F.6020205@cisco.com>
In-Reply-To: <4C10FC3F.6020205@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 14:57:44 -0000

Paul Kyzivat wrote:

>> Camarillo pointed out a path for discussion in a recent message in this
>> thread - and we have had parts of it already in the WG and elsewhere.
> 
> I hunted for a message by Gonzalo on this topic without success.

Hmm. I now found a message in reply to Gonzalo's, so I know what he 
said, though I still don't have his original message. Odd.

In any case, his comments do provide some insight.
I agree it is worth having a discussion of the use cases where 
bfcp-over-tcp fails, and what the options are for solving those.

	Thanks,
	Paul

From liebowitz@mitre.org  Thu Jun 10 07:59:42 2010
Return-Path: <liebowitz@mitre.org>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 774BA3A69E8 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.998
X-Spam-Level: 
X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3fFpnpH1gL2 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 07:59:41 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id A1EE33A6978 for <XCON@ietf.org>; Thu, 10 Jun 2010 07:59:38 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o5AExeoV004905 for <XCON@ietf.org>; Thu, 10 Jun 2010 10:59:40 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o5AExeKl004902 for <XCON@ietf.org>; Thu, 10 Jun 2010 10:59:40 -0400
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Thu, 10 Jun 2010 10:59:40 -0400
From: "Liebowitz, Burt H" <liebowitz@mitre.org>
To: "XCON@ietf.org" <XCON@ietf.org>
Date: Thu, 10 Jun 2010 10:59:38 -0400
Thread-Topic: please take me off the list
Thread-Index: AcsIrYwX7jjP+wApQ0CM2+yC3EYQyQ==
Message-ID: <34F02F03E4C0744888D194585BBB0D78040F13B81D@IMCMBX2.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_34F02F03E4C0744888D194585BBB0D78040F13B81DIMCMBX2MITREO_"
MIME-Version: 1.0
Subject: [XCON] please take me off the list
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 14:59:42 -0000

--_000_34F02F03E4C0744888D194585BBB0D78040F13B81DIMCMBX2MITREO_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please take me off the list

Thanks

Burt Liebowitz

--_000_34F02F03E4C0744888D194585BBB0D78040F13B81DIMCMBX2MITREO_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Please take me off the list<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Thanks<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Burt Liebowitz<o:p></o:p></p>

</div>

</body>

</html>

--_000_34F02F03E4C0744888D194585BBB0D78040F13B81DIMCMBX2MITREO_--

From allyn@cisco.com  Thu Jun 10 14:02:46 2010
Return-Path: <allyn@cisco.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA7393A6784 for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 14:02:46 -0700 (PDT)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qIEO1Wy-fHAW for <xcon@core3.amsl.com>; Thu, 10 Jun 2010 14:02:46 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id E02DF3A659A for <xcon@ietf.org>; Thu, 10 Jun 2010 14:02:45 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAB/wEEyrR7Hu/2dsb2JhbACeaXGjaZoPhRgEg0s
X-IronPort-AV: E=Sophos;i="4.53,400,1272844800"; d="scan'208";a="542991530"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-6.cisco.com with ESMTP; 10 Jun 2010 21:02:33 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o5AL2XpW006744; Thu, 10 Jun 2010 21:02:33 GMT
Received: from xmb-sjc-221.amer.cisco.com ([128.107.191.80]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 10 Jun 2010 14:02:32 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 Jun 2010 14:02:31 -0700
Message-ID: <9AC2C4348FD86B4BB1F8FA9C5E3A5EDC018C5297@xmb-sjc-221.amer.cisco.com>
In-Reply-To: <1275916958.17477.9.camel@localhost>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
Thread-Index: AcsGX85ByrG9ZbdVQaCyaUUmalqErwCgFFKw
References: <1271757479.26184.8.camel@localhost><1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost>
From: "Allyn Romanow (allyn)" <allyn@cisco.com>
To: "Tom Kristensen" <tom.kristensen@tandberg.com>, <xcon@ietf.org>, "Geir Arne Sandbakken" <geir.sandbakken@tandberg.com>
X-OriginalArrivalTime: 10 Jun 2010 21:02:32.0905 (UTC) FILETIME=[3EC5FB90:01CB08E0]
Cc: Alan Johnston <alan.b.johnston@gmail.com>, Mark Thompson <mark.thompson@tandberg.com>, xcon-chairs@tools.ietf.org
Subject: Re: [XCON] WG Adoption?  draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2010 21:02:47 -0000

Extremely interested in moving this forward.

Thanks,
Allyn

-----Original Message-----
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
Tom Kristensen
Sent: Monday, June 07, 2010 6:23 AM
To: xcon@ietf.org
Cc: Alan Johnston; Mark Thompson; xcon-chairs@tools.ietf.org
Subject: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02

The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted early in
March. No comments received since.

We'd like guidance on the next steps. First we ask for adoption as WG
item. Next step would include the merging process with bis versions of
RFC 4582 and RFC 4583.=20

We'd like to point out that interested parties for this work indeed
exist.

(For the record: Questions was sent to XCON chairs in April and May. See
below. No response given. Therefore, this request on the list.)

-- Tom

On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> Chairs,
>=20
> Any thoughts or decision on this matter?
>=20
> Cheers,
> -- Tom
>=20
> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > XCON chairs,
> >=20
> > We submitted draft-sandbakken-xcon-bfcp-udp-02 early in March - well
in
> > advance of IETF-77.=20
> >    http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-udp
> >=20
> > No comments received. Neither on XCON WG list, nor directly to the
> > authors. Therefore, we ask for adoption of this draft as an XCON WG
> > item.
> >=20
> > -- Tom
>=20

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www.ietf.org/mailman/listinfo/xcon

From spromano@unina.it  Tue Jun 15 09:28:37 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D07653A69BE for <xcon@core3.amsl.com>; Tue, 15 Jun 2010 09:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.231
X-Spam-Level: *
X-Spam-Status: No, score=1.231 tagged_above=-999 required=5 tests=[AWL=-0.650,  BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85Jaf+SvZSHA for <xcon@core3.amsl.com>; Tue, 15 Jun 2010 09:28:36 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id 570C43A69D7 for <xcon@ietf.org>; Tue, 15 Jun 2010 09:28:35 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.0/8.14.0) with ESMTP id o5FGSap5003716 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 15 Jun 2010 18:28:36 +0200
Message-ID: <4C17AA2B.40107@unina.it>
Date: Tue, 15 Jun 2010 18:28:27 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Oscar Novo <oscar.novo@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Cc: xcon@ietf.org
Subject: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jun 2010 16:28:37 -0000

Dear Oscar and all,

while playing with the data model, we found out that, in some cases, a 
more fine-grained control over the conference media would be desirable. 
To better explain this point, I will herein recall the current structure 
of the data model, which envisages the presence of a <controls> element:

******************* BEGIN excerpt from draft 
*********************************

<xs:complexType name="controls-type">
<xs:sequence>
         <xs:element name="mute" type="xs:boolean" minOccurs="0"/>
	<xs:element name="pause-video" type="xs:boolean" minOccurs="0"/>
	<xs:element name="gain" type="gain-type" minOccurs="0"/>
         <xs:element name="video-layout" type="video-layout-type" default="single-view" minOccurs="0"/>
	<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
*********************  END excerpt from draft ****************************

The above element is used, e.g., in the following data model hierarchy, in order to define controls on the
overall conference mix (on a per-medium basis):

<endpoint entity="xxx">

<media id="audio_id">
     <from-mixer name="AudioOut">
       <controls>
       <!-- controls on the mixed audio stream -->
	<gain>50<gain>
	...
       </controls>
     </from-mixer>
   </media>
</endpoint>

Indeed, we believe that the<controls>  element might also be used to arrive at a more fine-grained
(i.e. per-user and per-medium) level of control over the media involved in an XCON conference.
It would be nice to have something like the following:

<endpoint entity="xxx">

<media id="audio_id">
     <from-mixer name="AudioOut">
       <controls>
       <!-- controls on the mixed audio stream -->
	<gain>50</gain>
	...
       </controls>
     <!-- ****** BEGIN: New stuff proposed ****** -->	
       <mix-preferences>
       <include-users-list>
	<source entity="xcon-userid:alice@example.com">
	<!-- controls associated with user xcon-userid:alice@example.com -->
	<controls>
	<gain>5</gain>
	...
           </controls>
	</source>
	<source entity="xcon-userid:carol@example.com">
	<!-- controls associated with user xcon-userid:carol@example.com -->
	<controls>	
	<gain>10</gain>
	...
           </controls>
	</source>
       </include-users-list>
       <exclude-users-list>
         <source entity="xcon-userid:bob@example.com"/>
         <source entity="xcon-userid:pippozzo@example.com"/>
       </exclude-users-list>
       </mix-preferences>
     <!-- ****** END: New stuff proposed ****** -->	

     </from-mixer>
   </media>
</endpoint>

In the example above, we introduce the possibility to manage the single contributions coming from
users participating in a conference, by re-using the same<controls>  element adopted for the overall
conference mix. By the way, we envisaged the presence of both an<include-users-list>  element and an
<exclude-users-list>, even though the latter might be equivalent to the former, with a "<mute>true</mute>"
sub-element (in the<controls>  element of the specific<source>). As you can see, this modification would require
the definition of some new elements, namely:
1.<mix-preferences>
2.<include-users-list>
3.<exclude-users-list>
4.<source>

For the sake of completeness, it stands clear that the mentioned modifications might already be applied, given
the extensibility of the current data model definition (which envisages the presence of<any>  sub-elements in the
<from-mixer>  element); nonetheless, we think it might be worth defining such new elements in an explicit fashion.

What is your feeling about this?

Cheers,

Simon


-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From rbarnes@bbn.com  Tue Jun 15 10:26:07 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44F6E3A6887 for <xcon@core3.amsl.com>; Tue, 15 Jun 2010 10:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V51ASqyhDZlX for <xcon@core3.amsl.com>; Tue, 15 Jun 2010 10:26:05 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 905B53A687C for <xcon@ietf.org>; Tue, 15 Jun 2010 10:26:05 -0700 (PDT)
Received: from [128.89.254.74] (port=54537 helo=[192.168.1.43]) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OOZto-000N4p-AO; Tue, 15 Jun 2010 13:26:08 -0400
Message-Id: <01A49760-50A7-4846-BAF9-4717EB617525@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <4C17AA2B.40107@unina.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 15 Jun 2010 13:26:05 -0400
References: <4C17AA2B.40107@unina.it>
X-Mailer: Apple Mail (2.936)
Cc: xcon@ietf.org
Subject: Re: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jun 2010 17:26:07 -0000

Hey Simon,

Is there an especial reason to handle these modifications in the base =20=

spec, instead of as an extension?

Thanks,
--Richard



On Jun 15, 2010, at 12:28 PM, Simon Pietro Romano wrote:

> Dear Oscar and all,
>
> while playing with the data model, we found out that, in some cases, =20=

> a more fine-grained control over the conference media would be =20
> desirable. To better explain this point, I will herein recall the =20
> current structure of the data model, which envisages the presence of =20=

> a <controls> element:
>
> ******************* BEGIN excerpt from draft =20
> *********************************
>
> <xs:complexType name=3D"controls-type">
> <xs:sequence>
>        <xs:element name=3D"mute" type=3D"xs:boolean" minOccurs=3D"0"/>
> 	<xs:element name=3D"pause-video" type=3D"xs:boolean" =
minOccurs=3D"0"/>
> 	<xs:element name=3D"gain" type=3D"gain-type" minOccurs=3D"0"/>
>        <xs:element name=3D"video-layout" type=3D"video-layout-type" =20=

> default=3D"single-view" minOccurs=3D"0"/>
> 	<xs:any namespace=3D"##other" processContents=3D"lax" =
minOccurs=3D"0" =20
> maxOccurs=3D"unbounded"/>
> </xs:sequence>
> <xs:anyAttribute namespace=3D"##any" processContents=3D"lax"/>
> </xs:complexType>
> *********************  END excerpt from draft =20
> ****************************
>
> The above element is used, e.g., in the following data model =20
> hierarchy, in order to define controls on the
> overall conference mix (on a per-medium basis):
>
> <endpoint entity=3D"xxx">
>
> <media id=3D"audio_id">
>    <from-mixer name=3D"AudioOut">
>      <controls>
>      <!-- controls on the mixed audio stream -->
> 	<gain>50<gain>
> 	...
>      </controls>
>    </from-mixer>
>  </media>
> </endpoint>
>
> Indeed, we believe that the<controls>  element might also be used to =20=

> arrive at a more fine-grained
> (i.e. per-user and per-medium) level of control over the media =20
> involved in an XCON conference.
> It would be nice to have something like the following:
>
> <endpoint entity=3D"xxx">
>
> <media id=3D"audio_id">
>    <from-mixer name=3D"AudioOut">
>      <controls>
>      <!-- controls on the mixed audio stream -->
> 	<gain>50</gain>
> 	...
>      </controls>
>    <!-- ****** BEGIN: New stuff proposed ****** -->=09
>      <mix-preferences>
>      <include-users-list>
> 	<source entity=3D"xcon-userid:alice@example.com">
> 	<!-- controls associated with user xcon-userid:alice@example.com =
-->
> 	<controls>
> 	<gain>5</gain>
> 	...
>          </controls>
> 	</source>
> 	<source entity=3D"xcon-userid:carol@example.com">
> 	<!-- controls associated with user xcon-userid:carol@example.com =
-->
> 	<controls>=09
> 	<gain>10</gain>
> 	...
>          </controls>
> 	</source>
>      </include-users-list>
>      <exclude-users-list>
>        <source entity=3D"xcon-userid:bob@example.com"/>
>        <source entity=3D"xcon-userid:pippozzo@example.com"/>
>      </exclude-users-list>
>      </mix-preferences>
>    <!-- ****** END: New stuff proposed ****** -->=09
>
>    </from-mixer>
>  </media>
> </endpoint>
>
> In the example above, we introduce the possibility to manage the =20
> single contributions coming from
> users participating in a conference, by re-using the same<controls>  =20=

> element adopted for the overall
> conference mix. By the way, we envisaged the presence of both =20
> an<include-users-list>  element and an
> <exclude-users-list>, even though the latter might be equivalent to =20=

> the former, with a "<mute>true</mute>"
> sub-element (in the<controls>  element of the specific<source>). As =20=

> you can see, this modification would require
> the definition of some new elements, namely:
> 1.<mix-preferences>
> 2.<include-users-list>
> 3.<exclude-users-list>
> 4.<source>
>
> For the sake of completeness, it stands clear that the mentioned =20
> modifications might already be applied, given
> the extensibility of the current data model definition (which =20
> envisages the presence of<any>  sub-elements in the
> <from-mixer>  element); nonetheless, we think it might be worth =20
> defining such new elements in an explicit fashion.
>
> What is your feeling about this?
>
> Cheers,
>
> Simon
>
>
> --=20
>                            _\\|//_
>                            ( O-O )
>   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>                    Simon Pietro Romano
>              Universita' di Napoli Federico II
>                 Computer Science Department
>        Phone: +39 081 7683823 -- Fax: +39 081 7684219
>                e-mail: spromano@unina.it
>          http://www.comics.unina.it/simonpietro.romano
>
>    <<Molti mi dicono che lo scoraggiamento =E8 l'alibi degli
>   idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>                         oooO
>   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>                          \ (    (   )
>                           \_)    ) /
>                                 (_/
>
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From spromano@unina.it  Tue Jun 15 10:28:50 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AED83A69D5 for <xcon@core3.amsl.com>; Tue, 15 Jun 2010 10:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.355
X-Spam-Level: *
X-Spam-Status: No, score=1.355 tagged_above=-999 required=5 tests=[AWL=-0.340,  BAYES_40=-0.185, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pwkYlZ0NOMWD for <xcon@core3.amsl.com>; Tue, 15 Jun 2010 10:28:49 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id CAC733A69DD for <xcon@ietf.org>; Tue, 15 Jun 2010 10:28:48 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.0/8.14.0) with ESMTP id o5FHSpGA006476 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <xcon@ietf.org>; Tue, 15 Jun 2010 19:28:51 +0200
Message-ID: <4C17B84A.6060905@unina.it>
Date: Tue, 15 Jun 2010 19:28:42 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: xcon@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [XCON] New "options" message in CCMP?
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jun 2010 17:28:50 -0000

Dear all,

we are refining the CCMP schema based both on our experience and on 
feedbacks received on the list. Apart from fixing some minor
nits which came out during the revision process, we thought that it 
might be useful to add to the set of protocol messages a new "options"
request which can be sent from a CCMP client to a CCMP server in order 
to retrieve general information about its capabilities (specifically
in terms of standard CCMP messages supported, plus potential extension 
messages understood by the server).
A potential (easy, yet long ;-)) extension to the current schema follows:

********************* BEGIN Options request message definition 
*************************
<xs:complexType name="ccmp-options-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
</xs:extension>
</xs:complexContent>
</xs:complexType>

   ********************** END options request definition ******************

********************* BEGIN options response message definition 
*************************
<xs:complexType name="ccmp-options-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="optionsResponse"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>


<xs:element name="optionsResponse"
                 type="optionsResponseType" />

<xs:complexType name="optionsResponseType">
<xs:sequence>
<xs:element name="options"
                         type="options-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>


<xs:complexType name="options-type">
<xs:sequence>
<xs:element name="standard-message-list" 
type="standard-message-list-type" minOccurs="1"/>
<xs:element name="extended-message-list" 
type="extended-message-list-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>

<xs:complexType name="standard-message-list-type">
<xs:sequence>
<xs:element name="standard-message" type="standard-message-type" 
minOccurs="1" maxOccurs="10"/>
<xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>

<xs:complexType name="standard-message-type">
<xs:sequence>
<xs:element name="name" type="standard-message-name-type" minOccurs="1"/>
<xs:element name="schema-def" type="xs:string" />
<xs:element name="description" type="xs:string" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>

<xs:simpleType name="standard-message-name-type">
<xs:restriction base="xs:token">
<xs:enumeration value="confsRequest"/>
<xs:enumeration value="confRequest"/>
<xs:enumeration value="blueprintsRequest"/>
<xs:enumeration value="blueprintRequest"/>
<xs:enumeration value="usersRequest"/>
<xs:enumeration value="userRequest"/>
<xs:enumeration value="sidebarsByValRequest"/>
<xs:enumeration value="sidebarByValRequest"/>
<xs:enumeration value="sidebarsByRefRequest"/>
<xs:enumeration value="sidebarByRefRequest"/>
</xs:restriction>
</xs:simpleType>

<xs:complexType name="extended-message-list-type">
<xs:sequence>
<xs:element name="extended-message" type="extended-message-type" 
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>

<xs:complexType name="extended-message-type">
<xs:sequence>
<xs:element name="name" type="xs:string" />
<xs:element name="schema-def" type="xs:string" />
<xs:element name="description" type="xs:string" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>

********************* END Options response message definition 
*************************

As it comes out from the above schema, an "options"  request message is 
a basic CCMP message. Coming to the response,
it can contain information about both standard (i.e. IETF-defined) CCMP 
messages and extension messages supported by the server.
In both cases, the response carries back a list of names of the 
supported (standard and extended) messages. Since all CCMP messages
can potentially contain XML elements not envisioned in the CCMP schema 
(due to the presence of <any> elements and attributes), a reference
to a proper schema definition specifying such new elements/attributes 
can also be sent back to the clients (in the <schema-ref> element).

What do you guys think of this further capability? Shall we add it to 
the new draft version? [Editor's note] We definitely find it useful ;-)!

Thanks for your feedback,

Simon

-- 

                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From spromano@unina.it  Tue Jun 15 10:34:50 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 271E33A68B8 for <xcon@core3.amsl.com>; Tue, 15 Jun 2010 10:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.233
X-Spam-Level: 
X-Spam-Status: No, score=0.233 tagged_above=-999 required=5 tests=[AWL=0.952,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ppZAMXuqLQp for <xcon@core3.amsl.com>; Tue, 15 Jun 2010 10:34:49 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id 9C2DB3A6821 for <xcon@ietf.org>; Tue, 15 Jun 2010 10:34:48 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.0/8.14.0) with ESMTP id o5FHYjEx006775 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 15 Jun 2010 19:34:46 +0200
Message-ID: <4C17B9AD.8060806@unina.it>
Date: Tue, 15 Jun 2010 19:34:37 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Richard L. Barnes" <rbarnes@bbn.com>
References: <4C17AA2B.40107@unina.it> <01A49760-50A7-4846-BAF9-4717EB617525@bbn.com>
In-Reply-To: <01A49760-50A7-4846-BAF9-4717EB617525@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: xcon@ietf.org
Subject: Re: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jun 2010 17:34:50 -0000

It is just for the sake of completeness. We thought we were still in 
time for this, since the data model is (almost...) ready for publication.
We ended up with this idea when impementing a number of real-world use 
cases involving the use of the CCMP, which is one of the
candidate protocols for manipulating data model fields.
Just as an exmple, if I want to filter out some users' media 
contributions from the video mix I am receiving from an XCON-compliant
conference server, I cannot currently do this, unless I fall back to 
using some kind of dirty hack.

Simon

Il 15/06/2010 19.26, Richard L. Barnes ha scritto:
> Hey Simon,
>
> Is there an especial reason to handle these modifications in the base 
> spec, instead of as an extension?
>
> Thanks,
> --Richard
>
>
>
> On Jun 15, 2010, at 12:28 PM, Simon Pietro Romano wrote:
>
>> Dear Oscar and all,
>>
>> while playing with the data model, we found out that, in some cases, 
>> a more fine-grained control over the conference media would be 
>> desirable. To better explain this point, I will herein recall the 
>> current structure of the data model, which envisages the presence of 
>> a <controls> element:
>>
>> ******************* BEGIN excerpt from draft 
>> *********************************
>>
>> <xs:complexType name="controls-type">
>> <xs:sequence>
>> <xs:element name="mute" type="xs:boolean" minOccurs="0"/>
>> <xs:element name="pause-video" type="xs:boolean" minOccurs="0"/>
>> <xs:element name="gain" type="gain-type" minOccurs="0"/>
>> <xs:element name="video-layout" type="video-layout-type" 
>> default="single-view" minOccurs="0"/>
>> <xs:any namespace="##other" processContents="lax" minOccurs="0" 
>> maxOccurs="unbounded"/>
>> </xs:sequence>
>> <xs:anyAttribute namespace="##any" processContents="lax"/>
>> </xs:complexType>
>> *********************  END excerpt from draft 
>> ****************************
>>
>> The above element is used, e.g., in the following data model 
>> hierarchy, in order to define controls on the
>> overall conference mix (on a per-medium basis):
>>
>> <endpoint entity="xxx">
>>
>> <media id="audio_id">
>> <from-mixer name="AudioOut">
>> <controls>
>> <!-- controls on the mixed audio stream -->
>> <gain>50<gain>
>>     ...
>> </controls>
>> </from-mixer>
>> </media>
>> </endpoint>
>>
>> Indeed, we believe that the<controls>  element might also be used to 
>> arrive at a more fine-grained
>> (i.e. per-user and per-medium) level of control over the media 
>> involved in an XCON conference.
>> It would be nice to have something like the following:
>>
>> <endpoint entity="xxx">
>>
>> <media id="audio_id">
>> <from-mixer name="AudioOut">
>> <controls>
>> <!-- controls on the mixed audio stream -->
>> <gain>50</gain>
>>     ...
>> </controls>
>> <!-- ****** BEGIN: New stuff proposed ****** -->
>> <mix-preferences>
>> <include-users-list>
>> <source entity="xcon-userid:alice@example.com">
>> <!-- controls associated with user xcon-userid:alice@example.com -->
>> <controls>
>> <gain>5</gain>
>>     ...
>> </controls>
>> </source>
>> <source entity="xcon-userid:carol@example.com">
>> <!-- controls associated with user xcon-userid:carol@example.com -->
>> <controls>
>> <gain>10</gain>
>>     ...
>> </controls>
>> </source>
>> </include-users-list>
>> <exclude-users-list>
>> <source entity="xcon-userid:bob@example.com"/>
>> <source entity="xcon-userid:pippozzo@example.com"/>
>> </exclude-users-list>
>> </mix-preferences>
>> <!-- ****** END: New stuff proposed ****** -->
>>
>> </from-mixer>
>> </media>
>> </endpoint>
>>
>> In the example above, we introduce the possibility to manage the 
>> single contributions coming from
>> users participating in a conference, by re-using the same<controls>  
>> element adopted for the overall
>> conference mix. By the way, we envisaged the presence of both 
>> an<include-users-list>  element and an
>> <exclude-users-list>, even though the latter might be equivalent to 
>> the former, with a "<mute>true</mute>"
>> sub-element (in the<controls>  element of the specific<source>). As 
>> you can see, this modification would require
>> the definition of some new elements, namely:
>> 1.<mix-preferences>
>> 2.<include-users-list>
>> 3.<exclude-users-list>
>> 4.<source>
>>
>> For the sake of completeness, it stands clear that the mentioned 
>> modifications might already be applied, given
>> the extensibility of the current data model definition (which 
>> envisages the presence of<any>  sub-elements in the
>> <from-mixer>  element); nonetheless, we think it might be worth 
>> defining such new elements in an explicit fashion.
>>
>> What is your feeling about this?
>>
>> Cheers,
>>
>> Simon
>>
>>
>> -- 
>>                            _\\|//_
>>                            ( O-O )
>>   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>>                    Simon Pietro Romano
>>              Universita' di Napoli Federico II
>>                 Computer Science Department
>>        Phone: +39 081 7683823 -- Fax: +39 081 7684219
>>                e-mail: spromano@unina.it
>>          http://www.comics.unina.it/simonpietro.romano
>>
>> <<Molti mi dicono che lo scoraggiamento è l'alibi degli
>>   idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>>                         oooO
>>   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>>                          \ (    (   )
>>                           \_)    ) /
>>                                 (_/
>>
>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From oscar.novo@ericsson.com  Thu Jun 17 06:07:35 2010
Return-Path: <oscar.novo@ericsson.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 998E73A6AB6 for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 06:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9qCwTXeuQTun for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 06:07:34 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 029183A69D3 for <xcon@ietf.org>; Thu, 17 Jun 2010 06:07:33 -0700 (PDT)
X-AuditID: c1b4fb39-b7b80ae000001aa1-76-4c1a1e1987bd
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id F8.CD.06817.91E1A1C4; Thu, 17 Jun 2010 15:07:37 +0200 (CEST)
Received: from ESESSCMS0353.eemea.ericsson.se ([169.254.2.40]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Thu, 17 Jun 2010 15:07:37 +0200
From: Oscar Novo <oscar.novo@ericsson.com>
To: Simon Pietro Romano <spromano@unina.it>
Date: Thu, 17 Jun 2010 15:07:36 +0200
Thread-Topic: Controls in the XCON data model
Thread-Index: AcsMp86z7t8mI+JETpyf0NaQaP3ZTwBdg+jg
Message-ID: <209F0863F938D249AFDC024EC4C9E3E21117371B47@ESESSCMS0353.eemea.ericsson.se>
References: <4C17AA2B.40107@unina.it>
In-Reply-To: <4C17AA2B.40107@unina.it>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2010 13:07:35 -0000

Hi Simon,

The document is already in publication request:

https://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/

Cheers,

Oscar=20

-----Original Message-----
From: Simon Pietro Romano [mailto:spromano@unina.it]=20
Sent: 15. kes=E4kuuta 2010 19:28
To: Oscar Novo
Cc: xcon@ietf.org
Subject: Controls in the XCON data model

Dear Oscar and all,

while playing with the data model, we found out that, in some cases, a more=
 fine-grained control over the conference media would be desirable.=20
To better explain this point, I will herein recall the current structure of=
 the data model, which envisages the presence of a <controls> element:

******************* BEGIN excerpt from draft
*********************************

<xs:complexType name=3D"controls-type">
<xs:sequence>
         <xs:element name=3D"mute" type=3D"xs:boolean" minOccurs=3D"0"/>
	<xs:element name=3D"pause-video" type=3D"xs:boolean" minOccurs=3D"0"/>
	<xs:element name=3D"gain" type=3D"gain-type" minOccurs=3D"0"/>
         <xs:element name=3D"video-layout" type=3D"video-layout-type" defau=
lt=3D"single-view" minOccurs=3D"0"/>
	<xs:any namespace=3D"##other" processContents=3D"lax" minOccurs=3D"0" maxO=
ccurs=3D"unbounded"/> </xs:sequence> <xs:anyAttribute namespace=3D"##any" p=
rocessContents=3D"lax"/> </xs:complexType>
*********************  END excerpt from draft ****************************

The above element is used, e.g., in the following data model hierarchy, in =
order to define controls on the overall conference mix (on a per-medium bas=
is):

<endpoint entity=3D"xxx">

<media id=3D"audio_id">
     <from-mixer name=3D"AudioOut">
       <controls>
       <!-- controls on the mixed audio stream -->
	<gain>50<gain>
	...
       </controls>
     </from-mixer>
   </media>
</endpoint>

Indeed, we believe that the<controls>  element might also be used to arrive=
 at a more fine-grained (i.e. per-user and per-medium) level of control ove=
r the media involved in an XCON conference.
It would be nice to have something like the following:

<endpoint entity=3D"xxx">

<media id=3D"audio_id">
     <from-mixer name=3D"AudioOut">
       <controls>
       <!-- controls on the mixed audio stream -->
	<gain>50</gain>
	...
       </controls>
     <!-- ****** BEGIN: New stuff proposed ****** -->=09
       <mix-preferences>
       <include-users-list>
	<source entity=3D"xcon-userid:alice@example.com">
	<!-- controls associated with user xcon-userid:alice@example.com -->
	<controls>
	<gain>5</gain>
	...
           </controls>
	</source>
	<source entity=3D"xcon-userid:carol@example.com">
	<!-- controls associated with user xcon-userid:carol@example.com -->
	<controls>=09
	<gain>10</gain>
	...
           </controls>
	</source>
       </include-users-list>
       <exclude-users-list>
         <source entity=3D"xcon-userid:bob@example.com"/>
         <source entity=3D"xcon-userid:pippozzo@example.com"/>
       </exclude-users-list>
       </mix-preferences>
     <!-- ****** END: New stuff proposed ****** -->=09

     </from-mixer>
   </media>
</endpoint>

In the example above, we introduce the possibility to manage the single con=
tributions coming from users participating in a conference, by re-using the=
 same<controls>  element adopted for the overall conference mix. By the way=
, we envisaged the presence of both an<include-users-list>  element and an =
<exclude-users-list>, even though the latter might be equivalent to the for=
mer, with a "<mute>true</mute>"
sub-element (in the<controls>  element of the specific<source>). As you can=
 see, this modification would require the definition of some new elements, =
namely:
1.<mix-preferences>
2.<include-users-list>
3.<exclude-users-list>
4.<source>

For the sake of completeness, it stands clear that the mentioned modificati=
ons might already be applied, given the extensibility of the current data m=
odel definition (which envisages the presence of<any>  sub-elements in the =
<from-mixer>  element); nonetheless, we think it might be worth defining su=
ch new elements in an explicit fashion.

What is your feeling about this?

Cheers,

Simon


--=20
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento =E8 l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From spromano@unina.it  Thu Jun 17 07:57:05 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31CC93A6882 for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 07:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOKIdzRVL4J3 for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 07:57:04 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by core3.amsl.com (Postfix) with ESMTP id DF4783A6855 for <xcon@ietf.org>; Thu, 17 Jun 2010 07:57:02 -0700 (PDT)
Received: from [1.100.251.104] ([94.164.117.217]) (authenticated bits=0) by smtp1.unina.it (8.14.0/8.14.0) with ESMTP id o5HEuw9G026914 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Jun 2010 16:57:02 +0200
References: <4C17AA2B.40107@unina.it> <209F0863F938D249AFDC024EC4C9E3E21117371B47@ESESSCMS0353.eemea.ericsson.se>
Message-Id: <630C331E-E69D-4BE2-B575-6E72462C3CE3@unina.it>
From: Simon Pietro Romano <spromano@unina.it>
To: Oscar Novo <oscar.novo@ericsson.com>
In-Reply-To: <209F0863F938D249AFDC024EC4C9E3E21117371B47@ESESSCMS0353.eemea.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPhone Mail 7C144)
Date: Thu, 17 Jun 2010 16:55:15 +0200
X-Mailer: iPhone Mail (7C144)
Cc: "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2010 14:57:05 -0000

Hi,

should this stop any further discussion about the data model, so?

Simon

Il giorno 17/giu/2010, alle ore 15.07, Oscar Novo =
<oscar.novo@ericsson.com=20
 > ha scritto:

> Hi Simon,
>
> The document is already in publication request:
>
> https://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/
>
> Cheers,
>
> Oscar
>
> -----Original Message-----
> From: Simon Pietro Romano [mailto:spromano@unina.it]
> Sent: 15. kes=C3=A4kuuta 2010 19:28
> To: Oscar Novo
> Cc: xcon@ietf.org
> Subject: Controls in the XCON data model
>
> Dear Oscar and all,
>
> while playing with the data model, we found out that, in some cases, =20=

> a more fine-grained control over the conference media would be =20
> desirable.
> To better explain this point, I will herein recall the current =20
> structure of the data model, which envisages the presence of a =20
> <controls> element:
>
> ******************* BEGIN excerpt from draft
> *********************************
>
> <xs:complexType name=3D"controls-type">
> <xs:sequence>
>         <xs:element name=3D"mute" type=3D"xs:boolean" minOccurs=3D"0"/>
>    <xs:element name=3D"pause-video" type=3D"xs:boolean" =
minOccurs=3D"0"/>
>    <xs:element name=3D"gain" type=3D"gain-type" minOccurs=3D"0"/>
>         <xs:element name=3D"video-layout" type=3D"video-layout-type" =20=

> default=3D"single-view" minOccurs=3D"0"/>
>    <xs:any namespace=3D"##other" processContents=3D"lax" minOccurs=3D"0"=
 =20
> maxOccurs=3D"unbounded"/> </xs:sequence> <xs:anyAttribute =20
> namespace=3D"##any" processContents=3D"lax"/> </xs:complexType>
> *********************  END excerpt from draft =20
> ****************************
>
> The above element is used, e.g., in the following data model =20
> hierarchy, in order to define controls on the overall conference mix =20=

> (on a per-medium basis):
>
> <endpoint entity=3D"xxx">
>
> <media id=3D"audio_id">
>     <from-mixer name=3D"AudioOut">
>       <controls>
>       <!-- controls on the mixed audio stream -->
>    <gain>50<gain>
>    ...
>       </controls>
>     </from-mixer>
>   </media>
> </endpoint>
>
> Indeed, we believe that the<controls>  element might also be used to =20=

> arrive at a more fine-grained (i.e. per-user and per-medium) level =20
> of control over the media involved in an XCON conference.
> It would be nice to have something like the following:
>
> <endpoint entity=3D"xxx">
>
> <media id=3D"audio_id">
>     <from-mixer name=3D"AudioOut">
>       <controls>
>       <!-- controls on the mixed audio stream -->
>    <gain>50</gain>
>    ...
>       </controls>
>     <!-- ****** BEGIN: New stuff proposed ****** -->
>       <mix-preferences>
>       <include-users-list>
>    <source entity=3D"xcon-userid:alice@example.com">
>    <!-- controls associated with user xcon-userid:alice@example.com =20=

> -->
>    <controls>
>    <gain>5</gain>
>    ...
>           </controls>
>    </source>
>    <source entity=3D"xcon-userid:carol@example.com">
>    <!-- controls associated with user xcon-userid:carol@example.com =20=

> -->
>    <controls>
>    <gain>10</gain>
>    ...
>           </controls>
>    </source>
>       </include-users-list>
>       <exclude-users-list>
>         <source entity=3D"xcon-userid:bob@example.com"/>
>         <source entity=3D"xcon-userid:pippozzo@example.com"/>
>       </exclude-users-list>
>       </mix-preferences>
>     <!-- ****** END: New stuff proposed ****** -->
>
>     </from-mixer>
>   </media>
> </endpoint>
>
> In the example above, we introduce the possibility to manage the =20
> single contributions coming from users participating in a =20
> conference, by re-using the same<controls>  element adopted for the =20=

> overall conference mix. By the way, we envisaged the presence of =20
> both an<include-users-list>  element and an <exclude-users-list>, =20
> even though the latter might be equivalent to the former, with a =20
> "<mute>true</mute>"
> sub-element (in the<controls>  element of the specific<source>). As =20=

> you can see, this modification would require the definition of some =20=

> new elements, namely:
> 1.<mix-preferences>
> 2.<include-users-list>
> 3.<exclude-users-list>
> 4.<source>
>
> For the sake of completeness, it stands clear that the mentioned =20
> modifications might already be applied, given the extensibility of =20
> the current data model definition (which envisages the presence =20
> of<any>  sub-elements in the <from-mixer>  element); nonetheless, we =20=

> think it might be worth defining such new elements in an explicit =20
> fashion.
>
> What is your feeling about this?
>
> Cheers,
>
> Simon
>
>
> --=20
>                             _\\|//_
>                             ( O-O )
>    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>                     Simon Pietro Romano
>               Universita' di Napoli Federico II
>                  Computer Science Department
>         Phone: +39 081 7683823 -- Fax: +39 081 7684219
>                 e-mail: spromano@unina.it
>           http://www.comics.unina.it/simonpietro.romano
>
>     <<Molti mi dicono che lo scoraggiamento =C3=A8 l'alibi degli
>    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>                          oooO
>    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>                           \ (    (   )
>                            \_)    ) /
>                                  (_/
>
>

From rbarnes@bbn.com  Thu Jun 17 08:02:57 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DAB728C0E7 for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 08:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWBe4YsIpjMO for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 08:02:56 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id EFCC03A690D for <xcon@ietf.org>; Thu, 17 Jun 2010 08:02:55 -0700 (PDT)
Received: from [128.89.254.129] (port=51155 helo=[192.168.1.43]) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OPGcN-000J4C-TH; Thu, 17 Jun 2010 11:03:00 -0400
Message-Id: <2431DCBE-E573-413D-8376-B37520943A13@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <630C331E-E69D-4BE2-B575-6E72462C3CE3@unina.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 17 Jun 2010 11:02:56 -0400
References: <4C17AA2B.40107@unina.it> <209F0863F938D249AFDC024EC4C9E3E21117371B47@ESESSCMS0353.eemea.ericsson.se> <630C331E-E69D-4BE2-B575-6E72462C3CE3@unina.it>
X-Mailer: Apple Mail (2.936)
Cc: "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2010 15:02:57 -0000

Well, it has passed Working Group *Last* Call.  So formally, the last =20=

chance for comments is the IETF LC, which I don't think has opened =20
yet.  So everyone please get your comments on the data model in during =20=

IETF LC.

Thanks,
--Richard


On Jun 17, 2010, at 10:55 AM, Simon Pietro Romano wrote:

> Hi,
>
> should this stop any further discussion about the data model, so?
>
> Simon
>
> Il giorno 17/giu/2010, alle ore 15.07, Oscar Novo =
<oscar.novo@ericsson.com=20
> > ha scritto:
>
>> Hi Simon,
>>
>> The document is already in publication request:
>>
>> https://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/
>>
>> Cheers,
>>
>> Oscar
>>
>> -----Original Message-----
>> From: Simon Pietro Romano [mailto:spromano@unina.it]
>> Sent: 15. kes=E4kuuta 2010 19:28
>> To: Oscar Novo
>> Cc: xcon@ietf.org
>> Subject: Controls in the XCON data model
>>
>> Dear Oscar and all,
>>
>> while playing with the data model, we found out that, in some =20
>> cases, a more fine-grained control over the conference media would =20=

>> be desirable.
>> To better explain this point, I will herein recall the current =20
>> structure of the data model, which envisages the presence of a =20
>> <controls> element:
>>
>> ******************* BEGIN excerpt from draft
>> *********************************
>>
>> <xs:complexType name=3D"controls-type">
>> <xs:sequence>
>>        <xs:element name=3D"mute" type=3D"xs:boolean" minOccurs=3D"0"/>
>>   <xs:element name=3D"pause-video" type=3D"xs:boolean" =
minOccurs=3D"0"/>
>>   <xs:element name=3D"gain" type=3D"gain-type" minOccurs=3D"0"/>
>>        <xs:element name=3D"video-layout" type=3D"video-layout-type" =20=

>> default=3D"single-view" minOccurs=3D"0"/>
>>   <xs:any namespace=3D"##other" processContents=3D"lax" minOccurs=3D"0"=
 =20
>> maxOccurs=3D"unbounded"/> </xs:sequence> <xs:anyAttribute =20
>> namespace=3D"##any" processContents=3D"lax"/> </xs:complexType>
>> *********************  END excerpt from draft =20
>> ****************************
>>
>> The above element is used, e.g., in the following data model =20
>> hierarchy, in order to define controls on the overall conference =20
>> mix (on a per-medium basis):
>>
>> <endpoint entity=3D"xxx">
>>
>> <media id=3D"audio_id">
>>    <from-mixer name=3D"AudioOut">
>>      <controls>
>>      <!-- controls on the mixed audio stream -->
>>   <gain>50<gain>
>>   ...
>>      </controls>
>>    </from-mixer>
>>  </media>
>> </endpoint>
>>
>> Indeed, we believe that the<controls>  element might also be used =20
>> to arrive at a more fine-grained (i.e. per-user and per-medium) =20
>> level of control over the media involved in an XCON conference.
>> It would be nice to have something like the following:
>>
>> <endpoint entity=3D"xxx">
>>
>> <media id=3D"audio_id">
>>    <from-mixer name=3D"AudioOut">
>>      <controls>
>>      <!-- controls on the mixed audio stream -->
>>   <gain>50</gain>
>>   ...
>>      </controls>
>>    <!-- ****** BEGIN: New stuff proposed ****** -->
>>      <mix-preferences>
>>      <include-users-list>
>>   <source entity=3D"xcon-userid:alice@example.com">
>>   <!-- controls associated with user xcon-userid:alice@example.com =20=

>> -->
>>   <controls>
>>   <gain>5</gain>
>>   ...
>>          </controls>
>>   </source>
>>   <source entity=3D"xcon-userid:carol@example.com">
>>   <!-- controls associated with user xcon-userid:carol@example.com =20=

>> -->
>>   <controls>
>>   <gain>10</gain>
>>   ...
>>          </controls>
>>   </source>
>>      </include-users-list>
>>      <exclude-users-list>
>>        <source entity=3D"xcon-userid:bob@example.com"/>
>>        <source entity=3D"xcon-userid:pippozzo@example.com"/>
>>      </exclude-users-list>
>>      </mix-preferences>
>>    <!-- ****** END: New stuff proposed ****** -->
>>
>>    </from-mixer>
>>  </media>
>> </endpoint>
>>
>> In the example above, we introduce the possibility to manage the =20
>> single contributions coming from users participating in a =20
>> conference, by re-using the same<controls>  element adopted for the =20=

>> overall conference mix. By the way, we envisaged the presence of =20
>> both an<include-users-list>  element and an <exclude-users-list>, =20
>> even though the latter might be equivalent to the former, with a =20
>> "<mute>true</mute>"
>> sub-element (in the<controls>  element of the specific<source>). As =20=

>> you can see, this modification would require the definition of some =20=

>> new elements, namely:
>> 1.<mix-preferences>
>> 2.<include-users-list>
>> 3.<exclude-users-list>
>> 4.<source>
>>
>> For the sake of completeness, it stands clear that the mentioned =20
>> modifications might already be applied, given the extensibility of =20=

>> the current data model definition (which envisages the presence =20
>> of<any>  sub-elements in the <from-mixer>  element); nonetheless, =20
>> we think it might be worth defining such new elements in an =20
>> explicit fashion.
>>
>> What is your feeling about this?
>>
>> Cheers,
>>
>> Simon
>>
>>
>> --=20
>>                            _\\|//_
>>                            ( O-O )
>>   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>>                    Simon Pietro Romano
>>              Universita' di Napoli Federico II
>>                 Computer Science Department
>>        Phone: +39 081 7683823 -- Fax: +39 081 7684219
>>                e-mail: spromano@unina.it
>>          http://www.comics.unina.it/simonpietro.romano
>>
>>    <<Molti mi dicono che lo scoraggiamento =E8 l'alibi degli
>>   idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>>                         oooO
>>   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>>                          \ (    (   )
>>                           \_)    ) /
>>                                 (_/
>>
>>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From mary.ietf.barnes@gmail.com  Thu Jun 17 08:36:01 2010
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D70173A68B6 for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 08:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6IX3NKjDT5Y for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 08:36:00 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 4AC523A6801 for <xcon@ietf.org>; Thu, 17 Jun 2010 08:36:00 -0700 (PDT)
Received: by iwn2 with SMTP id 2so689945iwn.31 for <xcon@ietf.org>; Thu, 17 Jun 2010 08:36:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ctiS0Nq8vYBX/ViKKJXaHf7h//ShYtvYjbN9DOLZJns=; b=GLvq8sLR+fRlzGtRNhgaVAYYGfzXhVUouUUQdkZ/hQBHbNhmEZvmE92B8SDe8dgMds Oje6xw8ZRMDxQQmTa9ZBq3zzV3v3Dt44QW9QQ9qMJFv1UEHNdfGU3er4ScM58fsn4zqZ pbTbTczJKTrvhU0kGU+gCfgfJJ3LmFcQXH3/g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mLWuefLqr+YV8oAU6y4fdzU7OeneZvcM543VlayRUjlfwEm/HuGurfq0fovj2S8LC1 fDDxlV1d+G256I2zCqElNqGQnwRG9lpWHfRV4iBVwh/HeXQBzHjpkZ1arQ8hgFDXc8p0 Q2eS5OMlB3Bwl2kAyGxE3EDBh0zumOuNlKTaE=
MIME-Version: 1.0
Received: by 10.231.150.2 with SMTP id w2mr11997626ibv.37.1276788962081; Thu,  17 Jun 2010 08:36:02 -0700 (PDT)
Received: by 10.231.145.146 with HTTP; Thu, 17 Jun 2010 08:35:44 -0700 (PDT)
In-Reply-To: <2431DCBE-E573-413D-8376-B37520943A13@bbn.com>
References: <4C17AA2B.40107@unina.it> <209F0863F938D249AFDC024EC4C9E3E21117371B47@ESESSCMS0353.eemea.ericsson.se> <630C331E-E69D-4BE2-B575-6E72462C3CE3@unina.it> <2431DCBE-E573-413D-8376-B37520943A13@bbn.com>
Date: Thu, 17 Jun 2010 10:35:44 -0500
Message-ID: <AANLkTinUImijEs8IiEZWaojRiUBnJriB5JDe_2kYKuXq@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2010 15:36:02 -0000

Since the document has only just entered the Publication Requested
state,  I would think there's still a window for making changes if
folks agree (i.e. there's at least one more state change required
before this goes into IETF LC).

I had  also thought this document was not going to go through IETF LC
until the CCMP documents were ready since it is important that they
are aligned.

Thanks,
Mary.

On Thu, Jun 17, 2010 at 10:02 AM, Richard L. Barnes <rbarnes@bbn.com> wrote=
:
> Well, it has passed Working Group *Last* Call. =A0So formally, the last c=
hance
> for comments is the IETF LC, which I don't think has opened yet. =A0So
> everyone please get your comments on the data model in during IETF LC.
>
> Thanks,
> --Richard
>
>
> On Jun 17, 2010, at 10:55 AM, Simon Pietro Romano wrote:
>
>> Hi,
>>
>> should this stop any further discussion about the data model, so?
>>
>> Simon
>>
>> Il giorno 17/giu/2010, alle ore 15.07, Oscar Novo
>> <oscar.novo@ericsson.com> ha scritto:
>>
>>> Hi Simon,
>>>
>>> The document is already in publication request:
>>>
>>> https://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/
>>>
>>> Cheers,
>>>
>>> Oscar
>>>
>>> -----Original Message-----
>>> From: Simon Pietro Romano [mailto:spromano@unina.it]
>>> Sent: 15. kes=E4kuuta 2010 19:28
>>> To: Oscar Novo
>>> Cc: xcon@ietf.org
>>> Subject: Controls in the XCON data model
>>>
>>> Dear Oscar and all,
>>>
>>> while playing with the data model, we found out that, in some cases, a
>>> more fine-grained control over the conference media would be desirable.
>>> To better explain this point, I will herein recall the current structur=
e
>>> of the data model, which envisages the presence of a <controls> element=
:
>>>
>>> ******************* BEGIN excerpt from draft
>>> *********************************
>>>
>>> <xs:complexType name=3D"controls-type">
>>> <xs:sequence>
>>> =A0 =A0 =A0 <xs:element name=3D"mute" type=3D"xs:boolean" minOccurs=3D"=
0"/>
>>> =A0<xs:element name=3D"pause-video" type=3D"xs:boolean" minOccurs=3D"0"=
/>
>>> =A0<xs:element name=3D"gain" type=3D"gain-type" minOccurs=3D"0"/>
>>> =A0 =A0 =A0 <xs:element name=3D"video-layout" type=3D"video-layout-type=
"
>>> default=3D"single-view" minOccurs=3D"0"/>
>>> =A0<xs:any namespace=3D"##other" processContents=3D"lax" minOccurs=3D"0=
"
>>> maxOccurs=3D"unbounded"/> </xs:sequence> <xs:anyAttribute namespace=3D"=
##any"
>>> processContents=3D"lax"/> </xs:complexType>
>>> ********************* =A0END excerpt from draft
>>> ****************************
>>>
>>> The above element is used, e.g., in the following data model hierarchy,
>>> in order to define controls on the overall conference mix (on a per-med=
ium
>>> basis):
>>>
>>> <endpoint entity=3D"xxx">
>>>
>>> <media id=3D"audio_id">
>>> =A0 <from-mixer name=3D"AudioOut">
>>> =A0 =A0 <controls>
>>> =A0 =A0 <!-- controls on the mixed audio stream -->
>>> =A0<gain>50<gain>
>>> =A0...
>>> =A0 =A0 </controls>
>>> =A0 </from-mixer>
>>> =A0</media>
>>> </endpoint>
>>>
>>> Indeed, we believe that the<controls> =A0element might also be used to
>>> arrive at a more fine-grained (i.e. per-user and per-medium) level of
>>> control over the media involved in an XCON conference.
>>> It would be nice to have something like the following:
>>>
>>> <endpoint entity=3D"xxx">
>>>
>>> <media id=3D"audio_id">
>>> =A0 <from-mixer name=3D"AudioOut">
>>> =A0 =A0 <controls>
>>> =A0 =A0 <!-- controls on the mixed audio stream -->
>>> =A0<gain>50</gain>
>>> =A0...
>>> =A0 =A0 </controls>
>>> =A0 <!-- ****** BEGIN: New stuff proposed ****** -->
>>> =A0 =A0 <mix-preferences>
>>> =A0 =A0 <include-users-list>
>>> =A0<source entity=3D"xcon-userid:alice@example.com">
>>> =A0<!-- controls associated with user xcon-userid:alice@example.com -->
>>> =A0<controls>
>>> =A0<gain>5</gain>
>>> =A0...
>>> =A0 =A0 =A0 =A0 </controls>
>>> =A0</source>
>>> =A0<source entity=3D"xcon-userid:carol@example.com">
>>> =A0<!-- controls associated with user xcon-userid:carol@example.com -->
>>> =A0<controls>
>>> =A0<gain>10</gain>
>>> =A0...
>>> =A0 =A0 =A0 =A0 </controls>
>>> =A0</source>
>>> =A0 =A0 </include-users-list>
>>> =A0 =A0 <exclude-users-list>
>>> =A0 =A0 =A0 <source entity=3D"xcon-userid:bob@example.com"/>
>>> =A0 =A0 =A0 <source entity=3D"xcon-userid:pippozzo@example.com"/>
>>> =A0 =A0 </exclude-users-list>
>>> =A0 =A0 </mix-preferences>
>>> =A0 <!-- ****** END: New stuff proposed ****** -->
>>>
>>> =A0 </from-mixer>
>>> =A0</media>
>>> </endpoint>
>>>
>>> In the example above, we introduce the possibility to manage the single
>>> contributions coming from users participating in a conference, by re-us=
ing
>>> the same<controls> =A0element adopted for the overall conference mix. B=
y the
>>> way, we envisaged the presence of both an<include-users-list> =A0elemen=
t and
>>> an <exclude-users-list>, even though the latter might be equivalent to =
the
>>> former, with a "<mute>true</mute>"
>>> sub-element (in the<controls> =A0element of the specific<source>). As y=
ou
>>> can see, this modification would require the definition of some new
>>> elements, namely:
>>> 1.<mix-preferences>
>>> 2.<include-users-list>
>>> 3.<exclude-users-list>
>>> 4.<source>
>>>
>>> For the sake of completeness, it stands clear that the mentioned
>>> modifications might already be applied, given the extensibility of the
>>> current data model definition (which envisages the presence of<any>
>>> =A0sub-elements in the <from-mixer> =A0element); nonetheless, we think =
it might
>>> be worth defining such new elements in an explicit fashion.
>>>
>>> What is your feeling about this?
>>>
>>> Cheers,
>>>
>>> Simon
>>>
>>>
>>> --
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _\\|//_
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ( O-O )
>>> =A0~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Simon Pietro Romano
>>> =A0 =A0 =A0 =A0 =A0 =A0 Universita' di Napoli Federico II
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Computer Science Department
>>> =A0 =A0 =A0 Phone: +39 081 7683823 -- Fax: +39 081 7684219
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 e-mail: spromano@unina.it
>>> =A0 =A0 =A0 =A0 http://www.comics.unina.it/simonpietro.romano
>>>
>>> =A0 <<Molti mi dicono che lo scoraggiamento =E8 l'alibi degli
>>> =A0idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0oooO
>>> =A0~~~~~~~~~~~~~~~~~~~~~~( =A0 )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 \ ( =A0 =A0( =A0 )
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0\_) =A0 =A0) /
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(_/
>>>
>>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>

From alan.b.johnston@gmail.com  Thu Jun 17 08:45:37 2010
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C6243A69B3 for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 08:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmJgUNGrHKlM for <xcon@core3.amsl.com>; Thu, 17 Jun 2010 08:45:35 -0700 (PDT)
Received: from mail-yw0-f194.google.com (mail-yw0-f194.google.com [209.85.211.194]) by core3.amsl.com (Postfix) with ESMTP id 70E063A696C for <xcon@ietf.org>; Thu, 17 Jun 2010 08:45:35 -0700 (PDT)
Received: by ywh32 with SMTP id 32so57273ywh.5 for <xcon@ietf.org>; Thu, 17 Jun 2010 08:45:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:in-reply-to:x-mailer :subject:references:message-id:content-type :content-transfer-encoding:mime-version:date:cc; bh=hIqqZFWU0S911OtqIgLvvEagxrdMMR7LA/7CHNbXY04=; b=FYUYMUSa/F9KlUmzTNp4X0NtCtF3tSS8B438PAztU16HrvtCb8PISeOr6SKT17sc4E 3wRde+jNGUvJ78HCCn1mdpUjjfMuN3Ldmqlj9t1/xXvpTmXuXWlDWETgPUZhY6wEhHe9 0Ic+5iZwM4jXPnOQKKzq3UMZ7Qijj3GpRkfmI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:in-reply-to:x-mailer:subject:references:message-id :content-type:content-transfer-encoding:mime-version:date:cc; b=npm9GYkmSoeroGA3wE6W92lqgWCdPTZhjsleL7xdlNQcqu73IV5e5Vu1STzvIxtxGy /665BchMervwrDR8vK29vooBlhr0oHjeuJTCc2XRH7WXWQsvUjZ9+Bb0tyUuisvYbCWM G2sYE04xkAUMcibIAa46AUzJ6B0APQxswPpII=
Received: by 10.224.73.79 with SMTP id p15mr5668079qaj.21.1276789537722; Thu, 17 Jun 2010 08:45:37 -0700 (PDT)
Received: from [10.62.150.45] (mobile-166-137-142-120.mycingular.net [166.137.142.120]) by mx.google.com with ESMTPS id w29sm8857418vcr.2.2010.06.17.08.45.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Jun 2010 08:45:36 -0700 (PDT)
From: Alan Johnston <alan.b.johnston@gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
In-Reply-To: <AANLkTinUImijEs8IiEZWaojRiUBnJriB5JDe_2kYKuXq@mail.gmail.com>
X-Mailer: iPhone Mail (7E18)
References: <4C17AA2B.40107@unina.it> <209F0863F938D249AFDC024EC4C9E3E21117371B47@ESESSCMS0353.eemea.ericsson.se> <630C331E-E69D-4BE2-B575-6E72462C3CE3@unina.it> <2431DCBE-E573-413D-8376-B37520943A13@bbn.com> <AANLkTinUImijEs8IiEZWaojRiUBnJriB5JDe_2kYKuXq@mail.gmail.com>
Message-Id: <ECAFBBEA-0947-4B4F-8BC7-DB2F8B11EB9F@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPhone Mail 7E18)
Date: Thu, 17 Jun 2010 10:45:24 -0500
Cc: "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2010 15:45:37 -0000

The plan is to IETF LC all three of them together, so we need to =20
finish up CCMP and the Examples draft ASAP.

  - Alan -


On Jun 17, 2010, at 10:35 AM, Mary Barnes <mary.ietf.barnes@gmail.com> =20=

wrote:

> Since the document has only just entered the Publication Requested
> state,  I would think there's still a window for making changes if
> folks agree (i.e. there's at least one more state change required
> before this goes into IETF LC).
>
> I had  also thought this document was not going to go through IETF LC
> until the CCMP documents were ready since it is important that they
> are aligned.
>
> Thanks,
> Mary.
>
> On Thu, Jun 17, 2010 at 10:02 AM, Richard L. Barnes =20
> <rbarnes@bbn.com> wrote:
>> Well, it has passed Working Group *Last* Call.  So formally, the =20
>> last chance
>> for comments is the IETF LC, which I don't think has opened yet.  So
>> everyone please get your comments on the data model in during IETF =20=

>> LC.
>>
>> Thanks,
>> --Richard
>>
>>
>> On Jun 17, 2010, at 10:55 AM, Simon Pietro Romano wrote:
>>
>>> Hi,
>>>
>>> should this stop any further discussion about the data model, so?
>>>
>>> Simon
>>>
>>> Il giorno 17/giu/2010, alle ore 15.07, Oscar Novo
>>> <oscar.novo@ericsson.com> ha scritto:
>>>
>>>> Hi Simon,
>>>>
>>>> The document is already in publication request:
>>>>
>>>> https://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/
>>>>
>>>> Cheers,
>>>>
>>>> Oscar
>>>>
>>>> -----Original Message-----
>>>> From: Simon Pietro Romano [mailto:spromano@unina.it]
>>>> Sent: 15. kes=C3=A4kuuta 2010 19:28
>>>> To: Oscar Novo
>>>> Cc: xcon@ietf.org
>>>> Subject: Controls in the XCON data model
>>>>
>>>> Dear Oscar and all,
>>>>
>>>> while playing with the data model, we found out that, in some =20
>>>> cases, a
>>>> more fine-grained control over the conference media would be =20
>>>> desirable.
>>>> To better explain this point, I will herein recall the current =20
>>>> structure
>>>> of the data model, which envisages the presence of a <controls> =20
>>>> element:
>>>>
>>>> ******************* BEGIN excerpt from draft
>>>> *********************************
>>>>
>>>> <xs:complexType name=3D"controls-type">
>>>> <xs:sequence>
>>>>       <xs:element name=3D"mute" type=3D"xs:boolean" minOccurs=3D"0"/>=

>>>>  <xs:element name=3D"pause-video" type=3D"xs:boolean" =
minOccurs=3D"0"/>
>>>>  <xs:element name=3D"gain" type=3D"gain-type" minOccurs=3D"0"/>
>>>>       <xs:element name=3D"video-layout" type=3D"video-layout-type"
>>>> default=3D"single-view" minOccurs=3D"0"/>
>>>>  <xs:any namespace=3D"##other" processContents=3D"lax" =
minOccurs=3D"0"
>>>> maxOccurs=3D"unbounded"/> </xs:sequence> <xs:anyAttribute =20
>>>> namespace=3D"##any"
>>>> processContents=3D"lax"/> </xs:complexType>
>>>> *********************  END excerpt from draft
>>>> ****************************
>>>>
>>>> The above element is used, e.g., in the following data model =20
>>>> hierarchy,
>>>> in order to define controls on the overall conference mix (on a =20
>>>> per-medium
>>>> basis):
>>>>
>>>> <endpoint entity=3D"xxx">
>>>>
>>>> <media id=3D"audio_id">
>>>>   <from-mixer name=3D"AudioOut">
>>>>     <controls>
>>>>     <!-- controls on the mixed audio stream -->
>>>>  <gain>50<gain>
>>>>  ...
>>>>     </controls>
>>>>   </from-mixer>
>>>>  </media>
>>>> </endpoint>
>>>>
>>>> Indeed, we believe that the<controls>  element might also be used =20=

>>>> to
>>>> arrive at a more fine-grained (i.e. per-user and per-medium) =20
>>>> level of
>>>> control over the media involved in an XCON conference.
>>>> It would be nice to have something like the following:
>>>>
>>>> <endpoint entity=3D"xxx">
>>>>
>>>> <media id=3D"audio_id">
>>>>   <from-mixer name=3D"AudioOut">
>>>>     <controls>
>>>>     <!-- controls on the mixed audio stream -->
>>>>  <gain>50</gain>
>>>>  ...
>>>>     </controls>
>>>>   <!-- ****** BEGIN: New stuff proposed ****** -->
>>>>     <mix-preferences>
>>>>     <include-users-list>
>>>>  <source entity=3D"xcon-userid:alice@example.com">
>>>>  <!-- controls associated with user xcon-userid:alice@example.com =20=

>>>> -->
>>>>  <controls>
>>>>  <gain>5</gain>
>>>>  ...
>>>>         </controls>
>>>>  </source>
>>>>  <source entity=3D"xcon-userid:carol@example.com">
>>>>  <!-- controls associated with user xcon-userid:carol@example.com =20=

>>>> -->
>>>>  <controls>
>>>>  <gain>10</gain>
>>>>  ...
>>>>         </controls>
>>>>  </source>
>>>>     </include-users-list>
>>>>     <exclude-users-list>
>>>>       <source entity=3D"xcon-userid:bob@example.com"/>
>>>>       <source entity=3D"xcon-userid:pippozzo@example.com"/>
>>>>     </exclude-users-list>
>>>>     </mix-preferences>
>>>>   <!-- ****** END: New stuff proposed ****** -->
>>>>
>>>>   </from-mixer>
>>>>  </media>
>>>> </endpoint>
>>>>
>>>> In the example above, we introduce the possibility to manage the =20=

>>>> single
>>>> contributions coming from users participating in a conference, by =20=

>>>> re-using
>>>> the same<controls>  element adopted for the overall conference =20
>>>> mix. By the
>>>> way, we envisaged the presence of both an<include-users-list>  =20
>>>> element and
>>>> an <exclude-users-list>, even though the latter might be =20
>>>> equivalent to the
>>>> former, with a "<mute>true</mute>"
>>>> sub-element (in the<controls>  element of the specific<source>). =20=

>>>> As you
>>>> can see, this modification would require the definition of some new
>>>> elements, namely:
>>>> 1.<mix-preferences>
>>>> 2.<include-users-list>
>>>> 3.<exclude-users-list>
>>>> 4.<source>
>>>>
>>>> For the sake of completeness, it stands clear that the mentioned
>>>> modifications might already be applied, given the extensibility =20
>>>> of the
>>>> current data model definition (which envisages the presence of<any>
>>>>  sub-elements in the <from-mixer>  element); nonetheless, we =20
>>>> think it might
>>>> be worth defining such new elements in an explicit fashion.
>>>>
>>>> What is your feeling about this?
>>>>
>>>> Cheers,
>>>>
>>>> Simon
>>>>
>>>>
>>>> --
>>>>                           _\\|//_
>>>>                           ( O-O )
>>>>  ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>>>>                   Simon Pietro Romano
>>>>             Universita' di Napoli Federico II
>>>>                Computer Science Department
>>>>       Phone: +39 081 7683823 -- Fax: +39 081 7684219
>>>>               e-mail: spromano@unina.it
>>>>         http://www.comics.unina.it/simonpietro.romano
>>>>
>>>>   <<Molti mi dicono che lo scoraggiamento =C3=A8 l'alibi degli
>>>>  idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>>>>                        oooO
>>>>  ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>                         \ (    (   )
>>>>                          \_)    ) /
>>>>                                (_/
>>>>
>>>>
>>> _______________________________________________
>>> XCON mailing list
>>> XCON@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xcon
>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon

From oscar.novo@ericsson.com  Fri Jun 18 03:14:26 2010
Return-Path: <oscar.novo@ericsson.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C28D3A6A04 for <xcon@core3.amsl.com>; Fri, 18 Jun 2010 03:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level: 
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MwxpAXbn0JNb for <xcon@core3.amsl.com>; Fri, 18 Jun 2010 03:14:23 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 84A0B3A687B for <xcon@ietf.org>; Fri, 18 Jun 2010 03:14:22 -0700 (PDT)
X-AuditID: c1b4fb39-b7b80ae000001aa1-7b-4c1b47027301
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id A1.2B.06817.2074B1C4; Fri, 18 Jun 2010 12:14:26 +0200 (CEST)
Received: from ESESSCMS0353.eemea.ericsson.se ([169.254.2.40]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Fri, 18 Jun 2010 12:14:25 +0200
From: Oscar Novo <oscar.novo@ericsson.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>, Simon Pietro Romano <spromano@unina.it>
Date: Fri, 18 Jun 2010 12:14:22 +0200
Thread-Topic: [XCON] Controls in the XCON data model
Thread-Index: AcsOLjTrXfe+zJj5RomzApVsKRaB6gAkGYwQ
Message-ID: <209F0863F938D249AFDC024EC4C9E3E21117371F92@ESESSCMS0353.eemea.ericsson.se>
References: <4C17AA2B.40107@unina.it> <209F0863F938D249AFDC024EC4C9E3E21117371B47@ESESSCMS0353.eemea.ericsson.se> <630C331E-E69D-4BE2-B575-6E72462C3CE3@unina.it> <2431DCBE-E573-413D-8376-B37520943A13@bbn.com>
In-Reply-To: <2431DCBE-E573-413D-8376-B37520943A13@bbn.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "xcon@ietf.org" <xcon@ietf.org>
Subject: Re: [XCON] Controls in the XCON data model
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2010 10:14:26 -0000

Hi,

Yes, I'll try to collect all the comments in the IETF LC. =20

Cheers,

Oscar

-----Original Message-----
From: Richard L. Barnes [mailto:rbarnes@bbn.com]=20
Sent: 17. kes=E4kuuta 2010 18:03
To: Simon Pietro Romano
Cc: Oscar Novo; xcon@ietf.org
Subject: Re: [XCON] Controls in the XCON data model

Well, it has passed Working Group *Last* Call.  So formally, the last chanc=
e for comments is the IETF LC, which I don't think has opened yet.  So ever=
yone please get your comments on the data model in during IETF LC.

Thanks,
--Richard


On Jun 17, 2010, at 10:55 AM, Simon Pietro Romano wrote:

> Hi,
>
> should this stop any further discussion about the data model, so?
>
> Simon
>
> Il giorno 17/giu/2010, alle ore 15.07, Oscar Novo=20
> <oscar.novo@ericsson.com
> > ha scritto:
>
>> Hi Simon,
>>
>> The document is already in publication request:
>>
>> https://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/
>>
>> Cheers,
>>
>> Oscar
>>
>> -----Original Message-----
>> From: Simon Pietro Romano [mailto:spromano@unina.it]
>> Sent: 15. kes=E4kuuta 2010 19:28
>> To: Oscar Novo
>> Cc: xcon@ietf.org
>> Subject: Controls in the XCON data model
>>
>> Dear Oscar and all,
>>
>> while playing with the data model, we found out that, in some cases,=20
>> a more fine-grained control over the conference media would be=20
>> desirable.
>> To better explain this point, I will herein recall the current=20
>> structure of the data model, which envisages the presence of a=20
>> <controls> element:
>>
>> ******************* BEGIN excerpt from draft
>> *********************************
>>
>> <xs:complexType name=3D"controls-type"> <xs:sequence>
>>        <xs:element name=3D"mute" type=3D"xs:boolean" minOccurs=3D"0"/>
>>   <xs:element name=3D"pause-video" type=3D"xs:boolean" minOccurs=3D"0"/>
>>   <xs:element name=3D"gain" type=3D"gain-type" minOccurs=3D"0"/>
>>        <xs:element name=3D"video-layout" type=3D"video-layout-type" =20
>> default=3D"single-view" minOccurs=3D"0"/>
>>   <xs:any namespace=3D"##other" processContents=3D"lax" minOccurs=3D"0" =
=20
>> maxOccurs=3D"unbounded"/> </xs:sequence> <xs:anyAttribute=20
>> namespace=3D"##any" processContents=3D"lax"/> </xs:complexType>
>> *********************  END excerpt from draft
>> ****************************
>>
>> The above element is used, e.g., in the following data model=20
>> hierarchy, in order to define controls on the overall conference mix=20
>> (on a per-medium basis):
>>
>> <endpoint entity=3D"xxx">
>>
>> <media id=3D"audio_id">
>>    <from-mixer name=3D"AudioOut">
>>      <controls>
>>      <!-- controls on the mixed audio stream -->
>>   <gain>50<gain>
>>   ...
>>      </controls>
>>    </from-mixer>
>>  </media>
>> </endpoint>
>>
>> Indeed, we believe that the<controls>  element might also be used to=20
>> arrive at a more fine-grained (i.e. per-user and per-medium) level of=20
>> control over the media involved in an XCON conference.
>> It would be nice to have something like the following:
>>
>> <endpoint entity=3D"xxx">
>>
>> <media id=3D"audio_id">
>>    <from-mixer name=3D"AudioOut">
>>      <controls>
>>      <!-- controls on the mixed audio stream -->
>>   <gain>50</gain>
>>   ...
>>      </controls>
>>    <!-- ****** BEGIN: New stuff proposed ****** -->
>>      <mix-preferences>
>>      <include-users-list>
>>   <source entity=3D"xcon-userid:alice@example.com">
>>   <!-- controls associated with user xcon-userid:alice@example.com
>> -->
>>   <controls>
>>   <gain>5</gain>
>>   ...
>>          </controls>
>>   </source>
>>   <source entity=3D"xcon-userid:carol@example.com">
>>   <!-- controls associated with user xcon-userid:carol@example.com
>> -->
>>   <controls>
>>   <gain>10</gain>
>>   ...
>>          </controls>
>>   </source>
>>      </include-users-list>
>>      <exclude-users-list>
>>        <source entity=3D"xcon-userid:bob@example.com"/>
>>        <source entity=3D"xcon-userid:pippozzo@example.com"/>
>>      </exclude-users-list>
>>      </mix-preferences>
>>    <!-- ****** END: New stuff proposed ****** -->
>>
>>    </from-mixer>
>>  </media>
>> </endpoint>
>>
>> In the example above, we introduce the possibility to manage the=20
>> single contributions coming from users participating in a conference,=20
>> by re-using the same<controls>  element adopted for the overall=20
>> conference mix. By the way, we envisaged the presence of both=20
>> an<include-users-list>  element and an <exclude-users-list>, even=20
>> though the latter might be equivalent to the former, with a=20
>> "<mute>true</mute>"
>> sub-element (in the<controls>  element of the specific<source>). As=20
>> you can see, this modification would require the definition of some=20
>> new elements, namely:
>> 1.<mix-preferences>
>> 2.<include-users-list>
>> 3.<exclude-users-list>
>> 4.<source>
>>
>> For the sake of completeness, it stands clear that the mentioned=20
>> modifications might already be applied, given the extensibility of=20
>> the current data model definition (which envisages the presence=20
>> of<any>  sub-elements in the <from-mixer>  element); nonetheless, we=20
>> think it might be worth defining such new elements in an explicit=20
>> fashion.
>>
>> What is your feeling about this?
>>
>> Cheers,
>>
>> Simon
>>
>>
>> --=20
>>                            _\\|//_
>>                            ( O-O )
>>   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>>                    Simon Pietro Romano
>>              Universita' di Napoli Federico II
>>                 Computer Science Department
>>        Phone: +39 081 7683823 -- Fax: +39 081 7684219
>>                e-mail: spromano@unina.it
>>          http://www.comics.unina.it/simonpietro.romano
>>
>>    <<Molti mi dicono che lo scoraggiamento =E8 l'alibi degli
>>   idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>>                         oooO
>>   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>>                          \ (    (   )
>>                           \_)    ) /
>>                                 (_/
>>
>>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From rbarnes@bbn.com  Fri Jun 18 05:40:26 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC98E3A68C6 for <xcon@core3.amsl.com>; Fri, 18 Jun 2010 05:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.79
X-Spam-Level: 
X-Spam-Status: No, score=-0.79 tagged_above=-999 required=5 tests=[AWL=-0.605,  BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFxLjEJRH1IP for <xcon@core3.amsl.com>; Fri, 18 Jun 2010 05:40:17 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id D7A413A6A16 for <xcon@ietf.org>; Fri, 18 Jun 2010 05:40:06 -0700 (PDT)
Received: from [192.1.255.188] (port=55149 helo=col-dhcp-192-1-255-188.bbn.com) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OParj-0009Z1-AR for xcon@ietf.org; Fri, 18 Jun 2010 08:40:11 -0400
Message-Id: <992CB57C-1AE3-44C5-BD3D-83FFDD79DDC5@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: xcon@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 18 Jun 2010 08:40:10 -0400
X-Mailer: Apple Mail (2.936)
Subject: [XCON] re-WGLC on CCMP and Examples
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2010 12:40:26 -0000

All,

This is to announce an abbreviated re-Working Group Last Call on the  
following documents:

   draft-ietf-xcon-ccmp-05
   draft-ietf-xcon-examples-02

We had a WGLC for these drafts back in January, but there's been a  
trickle of comments coming in since then.  Please have any last  
comments to the list by Friday, 25 June 2010.

Thanks,
--Richard

From root@core3.amsl.com  Fri Jun 18 07:00:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: xcon@ietf.org
Delivered-To: xcon@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 505913A6A84; Fri, 18 Jun 2010 07:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100618140002.505913A6A84@core3.amsl.com>
Date: Fri, 18 Jun 2010 07:00:02 -0700 (PDT)
Cc: xcon@ietf.org
Subject: [XCON] I-D Action:draft-ietf-xcon-ccmp-08.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2010 14:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Centralized Conferencing Working Group of the IETF.


	Title           : Centralized Conferencing Manipulation Protocol
	Author(s)       : M. Barnes, et al.
	Filename        : draft-ietf-xcon-ccmp-08.txt
	Pages           : 99
	Date            : 2010-06-18

The Centralized Conferencing Manipulation Protocol (CCMP) allows an
XCON conferencing system client to create, retrieve, change, and
delete objects that describe a centralized conference.  CCMP is a
means to control basic and advanced conference features such as
conference state and capabilities, participants, relative roles, and
details.  CCMP is a state-less, XML-based, client server protocol
that carries, in its request and response messages, conference
information in the form of XML documents and fragments conforming to
the centralized conferencing data model schema.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xcon-ccmp-08.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-xcon-ccmp-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-06-18065717.I-D@ietf.org>


--NextPart--

From spromano@unina.it  Fri Jun 18 07:00:29 2010
Return-Path: <spromano@unina.it>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33E1528C0D8 for <xcon@core3.amsl.com>; Fri, 18 Jun 2010 07:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.042
X-Spam-Level: 
X-Spam-Status: No, score=0.042 tagged_above=-999 required=5 tests=[AWL=0.761,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsgnMRuL-56S for <xcon@core3.amsl.com>; Fri, 18 Jun 2010 07:00:23 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by core3.amsl.com (Postfix) with ESMTP id 91FC828C0DD for <xcon@ietf.org>; Fri, 18 Jun 2010 07:00:22 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp1.unina.it (8.14.0/8.14.0) with ESMTP id o5IE0LrH007865 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 18 Jun 2010 16:00:22 +0200
Message-ID: <4C1B7BE7.9020202@unina.it>
Date: Fri, 18 Jun 2010 16:00:07 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Richard L. Barnes" <rbarnes@bbn.com>
References: <992CB57C-1AE3-44C5-BD3D-83FFDD79DDC5@bbn.com>
In-Reply-To: <992CB57C-1AE3-44C5-BD3D-83FFDD79DDC5@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: xcon@ietf.org
Subject: Re: [XCON] re-WGLC on CCMP and Examples
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2010 14:00:29 -0000

Hi all,

I just submitted the latest version of the CCMP draft, which contains 
all modifications indicated by the two reviewers we have had to date 
(Sean Duddy and Gonzalo Camarillo), plus the newly introduced
optionsRequest and optionsResponse messages (as per my previous e-mail 
on the list). Please, work on them if you want to provide us with 
feedbacks/comments.

Cheers,

Simon

Il 18/06/2010 14.40, Richard L. Barnes ha scritto:
> All,
>
> This is to announce an abbreviated re-Working Group Last Call on the 
> following documents:
>
>   draft-ietf-xcon-ccmp-05
>   draft-ietf-xcon-examples-02
>
> We had a WGLC for these drafts back in January, but there's been a 
> trickle of comments coming in since then.  Please have any last 
> comments to the list by Friday, 25 June 2010.
>
> Thanks,
> --Richard
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From ron.even.tlv@gmail.com  Tue Jun 22 22:08:52 2010
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 105353A6936 for <xcon@core3.amsl.com>; Tue, 22 Jun 2010 22:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kO-nAHhcv-c8 for <xcon@core3.amsl.com>; Tue, 22 Jun 2010 22:08:49 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id F236B3A6853 for <xcon@ietf.org>; Tue, 22 Jun 2010 22:08:46 -0700 (PDT)
Received: by wwi17 with SMTP id 17so220757wwi.31 for <xcon@ietf.org>; Tue, 22 Jun 2010 22:08:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=Ur1w9mI0eJkyGA4cdcPQR5KBm3tXdJmQKiREEOEZ2Kg=; b=WPJ9xsceIfrBcDpLl37TZspiLoJxCi7WmD2fHB2VHEv9X2uvKuqMh1b8iNXxvWRG39 U8IAJ4fdERIaYjSV4+XQGf51rcf5wYgYGWtyG7RDgM8H6ISUBxhqZ8+wDMmQxG03R3LU YBOccJYGNETUByZ9KQDPSaPOH10gdZd8tnwJs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=el1BfEC5k46sazQ0qFr/LXMBXQS1a6NVjMb5EvmR+ugtKSo3/hPRUDca5FEP9BSbzN UkHWu2rak6kEVL2DkhSqfl5lOiPKvRmq5aoUsCqLc7I/fnjiy29FtaCA5Nn3sIlOHoO1 seEvH8H82yOfIRFzAL5N5mwGjKRppnXQCSziU=
Received: by 10.227.146.3 with SMTP id f3mr7120343wbv.211.1277269728478; Tue, 22 Jun 2010 22:08:48 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-5-86.red.bezeqint.net [79.179.5.86]) by mx.google.com with ESMTPS id t15sm58802267wbc.5.2010.06.22.22.08.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Jun 2010 22:08:47 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Richard L. Barnes'" <rbarnes@bbn.com>, <xcon@ietf.org>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4c107733.df0ce30a.21ca.15cc@mx.google.com> <20100610130009.1f1fbb03.lorenzo@meetecho.com> <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com>
In-Reply-To: <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com>
Date: Wed, 23 Jun 2010 08:05:55 +0300
Message-ID: <4c2196df.4f1ee30a.7753.ffffe8b2@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsIn2W+70DTVUtwReeaBNMobX/PYwJ8ZlTQ
Content-Language: en-us
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>, 'Tom Kristensen' <tom.kristensen@tandberg.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 05:08:52 -0000

Hi,
The XCON charter includes:

  - A mechanism for notification of conference related events/changes
    (for example a floor change)
  - A basic floor control protocol

This document is an update to the floor control protocol. You need a working
floor control protocol for centralized conferences and the current solution
has implementation problem. This is why I think that this work is within the
charter of XCON who is still an open WG. 
This proposal is in XCON for a while and there were requests to address some
issues in the proposal but there was never a question if this is within the
scope of XCON.
Roni Even

> -----Original Message-----
> From: Richard L. Barnes [mailto:rbarnes@bbn.com]
> Sent: Thursday, June 10, 2010 4:18 PM
> To: Lorenzo Miniero
> Cc: Roni Even; 'DRAGE, Keith (Keith)'; 'Tom Kristensen'; 'Mark
> Thompson'; 'Alan Johnston'; 'Tom Kristensen'; xcon@ietf.org
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> 
> <hat type="individual"/>
> 
> I tend to agree with Lorenzo that DISPATCH would be a better place to
> have these discussions, especially given that, as far as I can tell
> from this thread, the problem seems to be a general one of NAT
> traversal for TCP.
> 
> 
> 
> On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
> 
> > Hi all,
> >
> > with respect to this topic, I think there are many issues
> implementers
> > have to face when bringing IETF solutions to the real world. We found
> > ourselves many times in a situation in which some kind of work-around
> > had to be devised in order to let things work properly. Just to cite
> a
> > couple of examples, with BFCP we had to find a way to let it work in
> a
> > distributed conferencing scenario (which is far from easy, given the
> > intrinsic centralized model behind such protocol). In such case, we
> > decided to encapsulate BFCP messages in the body of XMPP
> > server-to-server packets (see the XCON-DCON Synchronization Protocol
> > in
> > draft-romano-dcon-xdsp-reqs-06 for the details) and then even devised
> > a BFCP-XMPP gateway for such a purpose. With respect to the NAT
> > traversal issue, we also implemented an HTTP encapsulation. Moving
> > further we even conceived a DTMF-based frontend to BFCP ;) and also
> > almost thought about a BFCP-over-RTP approach.
> >
> > That said, I nevertheless agree with Keith on the discussion. Those
> > problems may be common to other TCP-based protocols as well, and as
> > such
> > a generic solution (generic TCP over UDP, for instance, or anything
> > else) may be a much better approach than doing a protocol specific
> > patch. Besides, whatever the solution, it should also take care of
> how
> > the negotiation of such channels would be affected (as is the
> > case of RFC4583 for BFCP, which the proposed draft actually does).
> >
> > As Keith already suggested, DISPATCH may be a much better place to
> > discuss this issue: DISPATCH is where we'll also propose the above
> > mentioned DCON work.
> >
> > Lorenzo
> >
> >
> >
> > On Thu, 10 Jun 2010 08:22:55 +0300
> > "Roni Even" <ron.even.tlv@gmail.com> wrote:
> >
> >> Hi  Keith,
> >>
> >> I think that the IETF is trying to design protocols that will work
> >> over the
> >> Internet and also to enable interoperability between independent
> >> implementations.
> >>
> >> In the BFCP case the shipping implementations support TCP as the
> >> transport
> >> protocol but they encountered issues when running over the Internet
> >> due to
> >> devices like SBCs and due to lack of support for TCP media relay or
> >> ICE-TCP
> >> [I-D.ietf-mmusic-ice-tcp].
> >> When implementations looked at how to address the issue, the
> >> interoperability went away since there is no fall back solution for
> >> this
> >> real life case. Some did a fall back to HTTP and some did to UDP
> >> but not in
> >> an interoperable way.
> >>
> >> In order to achieve interoperability, this draft is trying to
> >> extend the
> >> current BFCP. It is not suggesting to replace TCP but to keep TCP
> >> as the
> >> mandatory transport and use UDP as fallback if unable to establish
> >> TCP
> >> connection.
> >>
> >> As for security, if the topic will be adopted the solution will be
> >> updated
> >> to use DTLS as the transport for BFCP.
> >>
> >> I hope that people will read the draft and look at the objectives
> >> and the
> >> proposed solution.
> >>
> >>
> >> BTW: This is a problem for client to client media connections over
> >> TCP and
> >> my understanding is that RTSP offers to use both TCP and UDP since
> >> both are
> >> specified. Since BFCP is not a payload but is running in parallel
> >> to the RTP
> >> payload (for the point to point calls or MCU based multipoint) it
> >> needs
> >> similar transport options.
> >>
> >> Thanks
> >> Roni Even
> >>
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
> >>> Sent: Thursday, June 10, 2010 1:54 AM
> >>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> >>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
> >>> xcon@ietf.org
> >>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >>>
> >>> What you are essentially saying is that all protocols in the future
> >>> that need reliable transport, as BFCP does, have to design in
> >>> their own
> >>> reliable transport element so they can use UDP. This is not a BFCP
> >>> specific issue.
> >>>
> >>> I find that an unacceptable direction for IETF to be heading in.
> >>>
> >>> I would also note that you are also asking for adoption of a
> >>> document
> >>> that cannot in its current form meet the security requirements of
> >>> the
> >>> original RFC.
> >>>
> >>> regards
> >>>
> >>> Keith
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> >>>> Sent: Wednesday, June 09, 2010 1:40 PM
> >>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
> >>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> >>>> 'Tom Kristensen'; xcon@ietf.org
> >>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >>>>
> >>>> Richard,
> >>>> The BFCP I used as a presentation token for video
> >>>> conferencing. What the implementers found out that TCP does
> >>>> not work in real networks due to Session border controllers
> >>>> not supporting TCP as used in BFCP.
> >>>> This is why in products they try to establish TCP connection
> >>>> and if fails tries UDP.
> >>>> The video conferencing vendors participating in the IMTC sip
> >>>> parity activity group defined an interoperability profile
> >>>> that references this option Roni Even
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >>>> On Behalf
> >>>>> Of Richard L. Barnes
> >>>>> Sent: Wednesday, June 09, 2010 3:34 PM
> >>>>> To: Tom Kristensen
> >>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> >>>>> Kristensen; xcon@ietf.org
> >>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> 02
> >>>>>
> >>>>> Tom and others who are interested in this draft:
> >>>>>
> >>>>> For those who are relatively new here: Could you summarize why
> you
> >>>>> think this draft is needed?  What requirement does it meet
> >>>> that BFCP
> >>>>> doesn't right now?
> >>>>>
> >>>>> Thanks,
> >>>>> --Richard
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> >>>>>
> >>>>>> The UDP/BFCP draft has been presented and discussed in
> >>>> two or three
> >>>>>> IETF XCON sessions. No objection to the work being
> >>>> carried on, just
> >>>>>> that adoption as WG item was postponed until the draft was more
> >>>>>> complete. (This has been delayed of various reasons, but
> >>>> the authors
> >>>>>> believe the -02 version in question here should be ready for
> >>>>>> adoption).
> >>>>>>
> >>>>>> The "current status of consensus" might be valid for some, but
> >>>>>> participants in the XCON sessions and the minutes of meeting
> show
> >>>>>> progress away from that initial consensus.
> >>>>>>
> >>>>>> I believe Ott's concerns are either dealt with or at
> >>>> least mentioned
> >>>>>> in the draft. Arrest me if I'm wrong.
> >>>>>>
> >>>>>> -- Tom
> >>>>>>
> >>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
> >>>>>> <keith.drage@alcatel-lucent.com> wrote:
> >>>>>>> We made an explicit decision in the original draft that
> >>>> UDP was not
> >>>>>>> required, not that we would do it later. That as far as I am
> >>>>>>> concerned represents the current status of consensus.
> >>>>>>>
> >>>>>>> This was done on the basis that we had all seen how UDP
> >>>> support had
> >>>>>>> complicated SIP, and we did not want to repeat that issue.
> >>>>>>>
> >>>>>>> So this is not continuing the work. The status is an
> >>>> author draft
> >>>>>>> which goes against a WG consensus position.
> >>>>>>>
> >>>>>>> I believe Georg Ott also expressed some concerns which I did
> not
> >>>>>>> see answered on list at all.
> >>>>>>>
> >>>>>>> regards
> >>>>>>>
> >>>>>>> Keith
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
> >>>>>>>> Behalf Of Roni Even
> >>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
> >>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
> >>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
> >>>>>>>> Subject: Re: [XCON] WG Adoption?
> >>>> draft-sandbakken-xcon-bfcp-udp-02
> >>>>>>>>
> >>>>>>>> Hi Alan,
> >>>>>>>> I support this work and think it is urgent to finish it.
> >>>>>>>> I think that updating BFCP with UDP support is very
> >>>> important. I
> >>>>>>>> would like to mention that BFCP is being used in video
> >>>>>>>> conferencing application and since the implementers
> encountered
> >>>>>>>> problems with TCP they use a fall back to UDP.
> >>>>>>>> We discussed this work in previous IETF meeting and
> >>>> Gonzalo as far
> >>>>>>>> as I remember suggested to add it to a BFCP bis draft.
> >>>>>>>>
> >>>>>>>> Thanks
> >>>>>>>> Roni Even
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >>>>>>>> On Behalf
> >>>>>>>>> Of Alan Johnston
> >>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
> >>>>>>>>> To: Tom Kristensen
> >>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
> >>>>>>>>> Subject: Re: [XCON] WG Adoption?
> >>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
> >>>>>>>>>
> >>>>>>>>> Tom,
> >>>>>>>>>
> >>>>>>>>> Apologies for the delay in replying.  As you know, the
> >>>>>>>> working group
> >>>>>>>>> is in the process of completing its final milestones.
> >>>>>>>>> Publication requests will be issued in the next few
> >>>> days for the
> >>>>>>>>> data
> >>>>>>>> model, CCMP,
> >>>>>>>>> and the Examples drafts.
> >>>>>>>>>
> >>>>>>>>> Taking on any new milestones for the working group
> >>>> would require:
> >>>>>>>>> 1. Strong support and interest from working group
> >>>> participants 2.
> >>>>>>>>> Approval of our ADs.
> >>>>>>>>>
> >>>>>>>>> I haven't seen evidence of either of these at this stage.
> >>>>>>>>>
> >>>>>>>>> A possible option is to take this work to DISPATCH, get an
> >>>>>>>> indication
> >>>>>>>>> of interests, and get feedback on the best way to move
> >>>> this work
> >>>>>>>>> forward.
> >>>>>>>>>
> >>>>>>>>> - Alan -
> >>>>>>>>> co-chair XCON
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> >>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> >>>>>>>> early in
> >>>>>>>>>> March. No comments received since.
> >>>>>>>>>>
> >>>>>>>>>> We'd like guidance on the next steps. First we ask for
> >>>>>>>> adoption as
> >>>>>>>>>> WG item. Next step would include the merging process with
> bis
> >>>>>>>>>> versions
> >>>>>>>>> of
> >>>>>>>>>> RFC 4582 and RFC 4583.
> >>>>>>>>>>
> >>>>>>>>>> We'd like to point out that interested parties for this
> >>>>>>>> work indeed
> >>>>>>>>>> exist.
> >>>>>>>>>>
> >>>>>>>>>> (For the record: Questions was sent to XCON chairs in
> >>>>>>>> April and May.
> >>>>>>>>> See
> >>>>>>>>>> below. No response given. Therefore, this request on
> >>>> the list.)
> >>>>>>>>>>
> >>>>>>>>>> -- Tom
> >>>>>>>>>>
> >>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> >>>>>>>>>>> Chairs,
> >>>>>>>>>>>
> >>>>>>>>>>> Any thoughts or decision on this matter?
> >>>>>>>>>>>
> >>>>>>>>>>> Cheers,
> >>>>>>>>>>> -- Tom
> >>>>>>>>>>>
> >>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> >>>>>>>>>>>> XCON chairs,
> >>>>>>>>>>>>
> >>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> >>>> early in March
> >>>>>>>>>>>> -
> >>>>>>>>> well in
> >>>>>>>>>>>> advance of IETF-77.
> >>>>>>>>>>>>   http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
> >>> udp
> >>>>>>>>>>>>
> >>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
> >>>>>>>> directly to the
> >>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
> >>>>>>>> as an XCON
> >>>>>>>>>>>> WG item.
> >>>>>>>>>>>>
> >>>>>>>>>>>> -- Tom
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> XCON mailing list
> >>>>>>>>> XCON@ietf.org
> >>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> XCON mailing list
> >>>>>>>> XCON@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> XCON mailing list
> >>>>>>> XCON@ietf.org
> >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> # TANDBERG R&D
> >>>>>> ## http://www.tandberg.com
> >>>>>> ### http://folk.uio.no/tomkri/
> >>>>>> _______________________________________________
> >>>>>> XCON mailing list
> >>>>>> XCON@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>
> >>>>> _______________________________________________
> >>>>> XCON mailing list
> >>>>> XCON@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>
> >>>> =
> >>
> >> _______________________________________________
> >> XCON mailing list
> >> XCON@ietf.org
> >> https://www.ietf.org/mailman/listinfo/xcon
> >>
> >
> >
> > --
> > Lorenzo Miniero
> > Meetecho s.r.l.
> > http://www.meetecho.com/


From patrick.luthi@tandberg.com  Wed Jun 23 08:20:27 2010
Return-Path: <patrick.luthi@tandberg.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBE343A6A97 for <xcon@core3.amsl.com>; Wed, 23 Jun 2010 08:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AR4IPDrYT0YA for <xcon@core3.amsl.com>; Wed, 23 Jun 2010 08:20:24 -0700 (PDT)
Received: from mail206.messagelabs.com (mail206.messagelabs.com [85.158.139.211]) by core3.amsl.com (Postfix) with SMTP id E661F3A6A8B for <xcon@ietf.org>; Wed, 23 Jun 2010 08:20:22 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: patrick.luthi@tandberg.com
X-Msg-Ref: server-6.tower-206.messagelabs.com!1277306429!5554238!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [62.70.2.252]
Received: (qmail 5911 invoked from network); 23 Jun 2010 15:20:30 -0000
Received: from unknown (HELO OSLEXCP11.eu.tandberg.int) (62.70.2.252) by server-6.tower-206.messagelabs.com with SMTP; 23 Jun 2010 15:20:30 -0000
Received: from oslexcp2.eu.tandberg.int ([10.47.136.30]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Wed, 23 Jun 2010 17:20:29 +0200
Received: from suisse127.tandberg.com ([10.0.6.160]) by oslexcp2.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 23 Jun 2010 17:20:28 +0200
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 23 Jun 2010 17:12:16 +0200
To: "Roni Even" <ron.even.tlv@gmail.com>, "'Richard L. Barnes'" <rbarnes@bbn.com>,<xcon@ietf.org>
From: Patrick Luthi <patrick.luthi@tandberg.com>
In-Reply-To: <4c2196df.4f1ee30a.7753.ffffe8b2@mx.google.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4c107733.df0ce30a.21ca.15cc@mx.google.com> <20100610130009.1f1fbb03.lorenzo@meetecho.com> <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com> <4c2196df.4f1ee30a.7753.ffffe8b2@mx.google.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <OSLEXCP2D3JkUwWpSWe000007c7@oslexcp2.eu.tandberg.int>
X-OriginalArrivalTime: 23 Jun 2010 15:20:28.0885 (UTC) FILETIME=[9CDFD050:01CB12E7]
Cc: 'Mark Thompson' <mark.thompson@tandberg.com>, 'Alan Johnston' <alan.b.johnston@gmail.com>, 'Tom Kristensen' <tom.kristensen@tandberg.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 15:20:27 -0000

I am with Roni on this one! BFCP is in the scope of XCON and there 
shouldn't be a problem extending it to include UDP as a fallback.

Videoconferencing manufacturers have a problem with TCP as discussed 
earlier and they need a solution now!

XCON Chairs, could you please consider this work to move forward?

Regards,

Patrick

At 07:05 23/06/2010, Roni Even wrote:
>Hi,
>The XCON charter includes:
>
>   - A mechanism for notification of conference related events/changes
>     (for example a floor change)
>   - A basic floor control protocol
>
>This document is an update to the floor control protocol. You need a working
>floor control protocol for centralized conferences and the current solution
>has implementation problem. This is why I think that this work is within the
>charter of XCON who is still an open WG.
>This proposal is in XCON for a while and there were requests to address some
>issues in the proposal but there was never a question if this is within the
>scope of XCON.
>Roni Even
>
> > -----Original Message-----
> > From: Richard L. Barnes [mailto:rbarnes@bbn.com]
> > Sent: Thursday, June 10, 2010 4:18 PM
> > To: Lorenzo Miniero
> > Cc: Roni Even; 'DRAGE, Keith (Keith)'; 'Tom Kristensen'; 'Mark
> > Thompson'; 'Alan Johnston'; 'Tom Kristensen'; xcon@ietf.org
> > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >
> > <hat type="individual"/>
> >
> > I tend to agree with Lorenzo that DISPATCH would be a better place to
> > have these discussions, especially given that, as far as I can tell
> > from this thread, the problem seems to be a general one of NAT
> > traversal for TCP.
> >
> >
> >
> > On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
> >
> > > Hi all,
> > >
> > > with respect to this topic, I think there are many issues
> > implementers
> > > have to face when bringing IETF solutions to the real world. We found
> > > ourselves many times in a situation in which some kind of work-around
> > > had to be devised in order to let things work properly. Just to cite
> > a
> > > couple of examples, with BFCP we had to find a way to let it work in
> > a
> > > distributed conferencing scenario (which is far from easy, given the
> > > intrinsic centralized model behind such protocol). In such case, we
> > > decided to encapsulate BFCP messages in the body of XMPP
> > > server-to-server packets (see the XCON-DCON Synchronization Protocol
> > > in
> > > draft-romano-dcon-xdsp-reqs-06 for the details) and then even devised
> > > a BFCP-XMPP gateway for such a purpose. With respect to the NAT
> > > traversal issue, we also implemented an HTTP encapsulation. Moving
> > > further we even conceived a DTMF-based frontend to BFCP ;) and also
> > > almost thought about a BFCP-over-RTP approach.
> > >
> > > That said, I nevertheless agree with Keith on the discussion. Those
> > > problems may be common to other TCP-based protocols as well, and as
> > > such
> > > a generic solution (generic TCP over UDP, for instance, or anything
> > > else) may be a much better approach than doing a protocol specific
> > > patch. Besides, whatever the solution, it should also take care of
> > how
> > > the negotiation of such channels would be affected (as is the
> > > case of RFC4583 for BFCP, which the proposed draft actually does).
> > >
> > > As Keith already suggested, DISPATCH may be a much better place to
> > > discuss this issue: DISPATCH is where we'll also propose the above
> > > mentioned DCON work.
> > >
> > > Lorenzo
> > >
> > >
> > >
> > > On Thu, 10 Jun 2010 08:22:55 +0300
> > > "Roni Even" <ron.even.tlv@gmail.com> wrote:
> > >
> > >> Hi  Keith,
> > >>
> > >> I think that the IETF is trying to design protocols that will work
> > >> over the
> > >> Internet and also to enable interoperability between independent
> > >> implementations.
> > >>
> > >> In the BFCP case the shipping implementations support TCP as the
> > >> transport
> > >> protocol but they encountered issues when running over the Internet
> > >> due to
> > >> devices like SBCs and due to lack of support for TCP media relay or
> > >> ICE-TCP
> > >> [I-D.ietf-mmusic-ice-tcp].
> > >> When implementations looked at how to address the issue, the
> > >> interoperability went away since there is no fall back solution for
> > >> this
> > >> real life case. Some did a fall back to HTTP and some did to UDP
> > >> but not in
> > >> an interoperable way.
> > >>
> > >> In order to achieve interoperability, this draft is trying to
> > >> extend the
> > >> current BFCP. It is not suggesting to replace TCP but to keep TCP
> > >> as the
> > >> mandatory transport and use UDP as fallback if unable to establish
> > >> TCP
> > >> connection.
> > >>
> > >> As for security, if the topic will be adopted the solution will be
> > >> updated
> > >> to use DTLS as the transport for BFCP.
> > >>
> > >> I hope that people will read the draft and look at the objectives
> > >> and the
> > >> proposed solution.
> > >>
> > >>
> > >> BTW: This is a problem for client to client media connections over
> > >> TCP and
> > >> my understanding is that RTSP offers to use both TCP and UDP since
> > >> both are
> > >> specified. Since BFCP is not a payload but is running in parallel
> > >> to the RTP
> > >> payload (for the point to point calls or MCU based multipoint) it
> > >> needs
> > >> similar transport options.
> > >>
> > >> Thanks
> > >> Roni Even
> > >>
> > >>
> > >>
> > >>
> > >>> -----Original Message-----
> > >>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
> > >>> Sent: Thursday, June 10, 2010 1:54 AM
> > >>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> > >>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
> > >>> xcon@ietf.org
> > >>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > >>>
> > >>> What you are essentially saying is that all protocols in the future
> > >>> that need reliable transport, as BFCP does, have to design in
> > >>> their own
> > >>> reliable transport element so they can use UDP. This is not a BFCP
> > >>> specific issue.
> > >>>
> > >>> I find that an unacceptable direction for IETF to be heading in.
> > >>>
> > >>> I would also note that you are also asking for adoption of a
> > >>> document
> > >>> that cannot in its current form meet the security requirements of
> > >>> the
> > >>> original RFC.
> > >>>
> > >>> regards
> > >>>
> > >>> Keith
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > >>>> Sent: Wednesday, June 09, 2010 1:40 PM
> > >>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
> > >>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> > >>>> 'Tom Kristensen'; xcon@ietf.org
> > >>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > >>>>
> > >>>> Richard,
> > >>>> The BFCP I used as a presentation token for video
> > >>>> conferencing. What the implementers found out that TCP does
> > >>>> not work in real networks due to Session border controllers
> > >>>> not supporting TCP as used in BFCP.
> > >>>> This is why in products they try to establish TCP connection
> > >>>> and if fails tries UDP.
> > >>>> The video conferencing vendors participating in the IMTC sip
> > >>>> parity activity group defined an interoperability profile
> > >>>> that references this option Roni Even
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > >>>> On Behalf
> > >>>>> Of Richard L. Barnes
> > >>>>> Sent: Wednesday, June 09, 2010 3:34 PM
> > >>>>> To: Tom Kristensen
> > >>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> > >>>>> Kristensen; xcon@ietf.org
> > >>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> > 02
> > >>>>>
> > >>>>> Tom and others who are interested in this draft:
> > >>>>>
> > >>>>> For those who are relatively new here: Could you summarize why
> > you
> > >>>>> think this draft is needed?  What requirement does it meet
> > >>>> that BFCP
> > >>>>> doesn't right now?
> > >>>>>
> > >>>>> Thanks,
> > >>>>> --Richard
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> > >>>>>
> > >>>>>> The UDP/BFCP draft has been presented and discussed in
> > >>>> two or three
> > >>>>>> IETF XCON sessions. No objection to the work being
> > >>>> carried on, just
> > >>>>>> that adoption as WG item was postponed until the draft was more
> > >>>>>> complete. (This has been delayed of various reasons, but
> > >>>> the authors
> > >>>>>> believe the -02 version in question here should be ready for
> > >>>>>> adoption).
> > >>>>>>
> > >>>>>> The "current status of consensus" might be valid for some, but
> > >>>>>> participants in the XCON sessions and the minutes of meeting
> > show
> > >>>>>> progress away from that initial consensus.
> > >>>>>>
> > >>>>>> I believe Ott's concerns are either dealt with or at
> > >>>> least mentioned
> > >>>>>> in the draft. Arrest me if I'm wrong.
> > >>>>>>
> > >>>>>> -- Tom
> > >>>>>>
> > >>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
> > >>>>>> <keith.drage@alcatel-lucent.com> wrote:
> > >>>>>>> We made an explicit decision in the original draft that
> > >>>> UDP was not
> > >>>>>>> required, not that we would do it later. That as far as I am
> > >>>>>>> concerned represents the current status of consensus.
> > >>>>>>>
> > >>>>>>> This was done on the basis that we had all seen how UDP
> > >>>> support had
> > >>>>>>> complicated SIP, and we did not want to repeat that issue.
> > >>>>>>>
> > >>>>>>> So this is not continuing the work. The status is an
> > >>>> author draft
> > >>>>>>> which goes against a WG consensus position.
> > >>>>>>>
> > >>>>>>> I believe Georg Ott also expressed some concerns which I did
> > not
> > >>>>>>> see answered on list at all.
> > >>>>>>>
> > >>>>>>> regards
> > >>>>>>>
> > >>>>>>> Keith
> > >>>>>>>
> > >>>>>>>> -----Original Message-----
> > >>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
> > >>>>>>>> Behalf Of Roni Even
> > >>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
> > >>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
> > >>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
> > >>>>>>>> Subject: Re: [XCON] WG Adoption?
> > >>>> draft-sandbakken-xcon-bfcp-udp-02
> > >>>>>>>>
> > >>>>>>>> Hi Alan,
> > >>>>>>>> I support this work and think it is urgent to finish it.
> > >>>>>>>> I think that updating BFCP with UDP support is very
> > >>>> important. I
> > >>>>>>>> would like to mention that BFCP is being used in video
> > >>>>>>>> conferencing application and since the implementers
> > encountered
> > >>>>>>>> problems with TCP they use a fall back to UDP.
> > >>>>>>>> We discussed this work in previous IETF meeting and
> > >>>> Gonzalo as far
> > >>>>>>>> as I remember suggested to add it to a BFCP bis draft.
> > >>>>>>>>
> > >>>>>>>> Thanks
> > >>>>>>>> Roni Even
> > >>>>>>>>
> > >>>>>>>>> -----Original Message-----
> > >>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > >>>>>>>> On Behalf
> > >>>>>>>>> Of Alan Johnston
> > >>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
> > >>>>>>>>> To: Tom Kristensen
> > >>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
> > >>>>>>>>> Subject: Re: [XCON] WG Adoption?
> > >>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
> > >>>>>>>>>
> > >>>>>>>>> Tom,
> > >>>>>>>>>
> > >>>>>>>>> Apologies for the delay in replying.  As you know, the
> > >>>>>>>> working group
> > >>>>>>>>> is in the process of completing its final milestones.
> > >>>>>>>>> Publication requests will be issued in the next few
> > >>>> days for the
> > >>>>>>>>> data
> > >>>>>>>> model, CCMP,
> > >>>>>>>>> and the Examples drafts.
> > >>>>>>>>>
> > >>>>>>>>> Taking on any new milestones for the working group
> > >>>> would require:
> > >>>>>>>>> 1. Strong support and interest from working group
> > >>>> participants 2.
> > >>>>>>>>> Approval of our ADs.
> > >>>>>>>>>
> > >>>>>>>>> I haven't seen evidence of either of these at this stage.
> > >>>>>>>>>
> > >>>>>>>>> A possible option is to take this work to DISPATCH, get an
> > >>>>>>>> indication
> > >>>>>>>>> of interests, and get feedback on the best way to move
> > >>>> this work
> > >>>>>>>>> forward.
> > >>>>>>>>>
> > >>>>>>>>> - Alan -
> > >>>>>>>>> co-chair XCON
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > >>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> > >>>>>>>> early in
> > >>>>>>>>>> March. No comments received since.
> > >>>>>>>>>>
> > >>>>>>>>>> We'd like guidance on the next steps. First we ask for
> > >>>>>>>> adoption as
> > >>>>>>>>>> WG item. Next step would include the merging process with
> > bis
> > >>>>>>>>>> versions
> > >>>>>>>>> of
> > >>>>>>>>>> RFC 4582 and RFC 4583.
> > >>>>>>>>>>
> > >>>>>>>>>> We'd like to point out that interested parties for this
> > >>>>>>>> work indeed
> > >>>>>>>>>> exist.
> > >>>>>>>>>>
> > >>>>>>>>>> (For the record: Questions was sent to XCON chairs in
> > >>>>>>>> April and May.
> > >>>>>>>>> See
> > >>>>>>>>>> below. No response given. Therefore, this request on
> > >>>> the list.)
> > >>>>>>>>>>
> > >>>>>>>>>> -- Tom
> > >>>>>>>>>>
> > >>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > >>>>>>>>>>> Chairs,
> > >>>>>>>>>>>
> > >>>>>>>>>>> Any thoughts or decision on this matter?
> > >>>>>>>>>>>
> > >>>>>>>>>>> Cheers,
> > >>>>>>>>>>> -- Tom
> > >>>>>>>>>>>
> > >>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > >>>>>>>>>>>> XCON chairs,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> > >>>> early in March
> > >>>>>>>>>>>> -
> > >>>>>>>>> well in
> > >>>>>>>>>>>> advance of IETF-77.
> > >>>>>>>>>>>>   http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
> > >>> udp
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
> > >>>>>>>> directly to the
> > >>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
> > >>>>>>>> as an XCON
> > >>>>>>>>>>>> WG item.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> -- Tom
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>> _______________________________________________
> > >>>>>>>>> XCON mailing list
> > >>>>>>>>> XCON@ietf.org
> > >>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>>
> > >>>>>>>> _______________________________________________
> > >>>>>>>> XCON mailing list
> > >>>>>>>> XCON@ietf.org
> > >>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>>
> > >>>>>>> _______________________________________________
> > >>>>>>> XCON mailing list
> > >>>>>>> XCON@ietf.org
> > >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> # TANDBERG R&D
> > >>>>>> ## http://www.tandberg.com
> > >>>>>> ### http://folk.uio.no/tomkri/
> > >>>>>> _______________________________________________
> > >>>>>> XCON mailing list
> > >>>>>> XCON@ietf.org
> > >>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> XCON mailing list
> > >>>>> XCON@ietf.org
> > >>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>
> > >>>> =
> > >>
> > >> _______________________________________________
> > >> XCON mailing list
> > >> XCON@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/xcon
> > >>
> > >
> > >
> > > --
> > > Lorenzo Miniero
> > > Meetecho s.r.l.
> > > http://www.meetecho.com/
>
>_______________________________________________
>XCON mailing list
>XCON@ietf.org
>https://www.ietf.org/mailman/listinfo/xcon



From mary.ietf.barnes@gmail.com  Wed Jun 23 09:25:33 2010
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A89828C117 for <xcon@core3.amsl.com>; Wed, 23 Jun 2010 09:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.27
X-Spam-Level: 
X-Spam-Status: No, score=-2.27 tagged_above=-999 required=5 tests=[AWL=0.329,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id clbehmsuU9w1 for <xcon@core3.amsl.com>; Wed, 23 Jun 2010 09:25:31 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 261FA3A6973 for <xcon@ietf.org>; Wed, 23 Jun 2010 09:25:31 -0700 (PDT)
Received: by iwn40 with SMTP id 40so474664iwn.31 for <xcon@ietf.org>; Wed, 23 Jun 2010 09:25:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=S5/s0i2aI8Ejlj80LQZ2l3KZQyNdck7/qHCUTyMvs6w=; b=WoOXTNjz0A7SPS2DdrTVmUa0Yy5meF51AtUslJuOF8Mi+yn9Su2ZeCd+y1pazIn6bf dAohM9p36LPQp3qYBMddcedUulY5V3LSBq4M0rDLTM8GX0Kts/gOh2QF1Mb832IAh1KZ A5gDfK5fqnRHccd16kVtB3F7NIMpaPigIwfeE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xJUok1YwF9Wf5FB9wbhKM1Nnm34NoWHIyaSCwtAO0WEaYJoN4VwzLvWCAFWELqSZUs 5IAqFlnYTDeZyII5LrPxZXmNCJKc/T/HmoiGq4ZCPaxnmGuMNF/QABw7SN8el71U7Rse 0Gu4bXAb7NzFCst5o0Rc+B3MAAX6lhpXv/3aM=
MIME-Version: 1.0
Received: by 10.231.145.79 with SMTP id c15mr9341879ibv.102.1277310334755;  Wed, 23 Jun 2010 09:25:34 -0700 (PDT)
Received: by 10.231.146.206 with HTTP; Wed, 23 Jun 2010 09:25:34 -0700 (PDT)
In-Reply-To: <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4c107733.df0ce30a.21ca.15cc@mx.google.com> <20100610130009.1f1fbb03.lorenzo@meetecho.com> <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com>
Date: Wed, 23 Jun 2010 11:25:34 -0500
Message-ID: <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Tom Kristensen <tom.kristensen@tandberg.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, xcon@ietf.org, Mark Thompson <mark.thompson@tandberg.com>, Alan Johnston <alan.b.johnston@gmail.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 16:25:33 -0000

I have reviewed the draft in question and while I agree that this
could be viewed as a workaround for some more general problems that
need to be solved, there is a current industry need for the solution
in this draft.   If the general problems described go to DISPATCH
(which is the appropriate thing to do rather than bringing this
specific document), the timeframe for getting agreement on the problem
to be solved and for the solutions to be agreed would be far longer
IMHO than if this document were progressed. If XCON would prefer to
close the WG without progressing this document (in this form or as a
-bis to RFC  4582), my suggestion would be to do as was done for the
remaining SIP and SIPPING documents and progress this item as an
individual AD sponsored.

Mary.

On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes <rbarnes@bbn.com> wrote:
> <hat type=3D"individual"/>
>
> I tend to agree with Lorenzo that DISPATCH would be a better place to hav=
e
> these discussions, especially given that, as far as I can tell from this
> thread, the problem seems to be a general one of NAT traversal for TCP.
>
>
>
> On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
>
>> Hi all,
>>
>> with respect to this topic, I think there are many issues implementers
>> have to face when bringing IETF solutions to the real world. We found
>> ourselves many times in a situation in which some kind of work-around
>> had to be devised in order to let things work properly. Just to cite a
>> couple of examples, with BFCP we had to find a way to let it work in a
>> distributed conferencing scenario (which is far from easy, given the
>> intrinsic centralized model behind such protocol). In such case, we
>> decided to encapsulate BFCP messages in the body of XMPP
>> server-to-server packets (see the XCON-DCON Synchronization Protocol in
>> draft-romano-dcon-xdsp-reqs-06 for the details) and then even devised
>> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
>> traversal issue, we also implemented an HTTP encapsulation. Moving
>> further we even conceived a DTMF-based frontend to BFCP ;) and also
>> almost thought about a BFCP-over-RTP approach.
>>
>> That said, I nevertheless agree with Keith on the discussion. Those
>> problems may be common to other TCP-based protocols as well, and as such
>> a generic solution (generic TCP over UDP, for instance, or anything
>> else) may be a much better approach than doing a protocol specific
>> patch. Besides, whatever the solution, it should also take care of how
>> the negotiation of such channels would be affected (as is the
>> case of RFC4583 for BFCP, which the proposed draft actually does).
>>
>> As Keith already suggested, DISPATCH may be a much better place to
>> discuss this issue: DISPATCH is where we'll also propose the above
>> mentioned DCON work.
>>
>> Lorenzo
>>
>>
>>
>> On Thu, 10 Jun 2010 08:22:55 +0300
>> "Roni Even" <ron.even.tlv@gmail.com> wrote:
>>
>>> Hi =A0Keith,
>>>
>>> I think that the IETF is trying to design protocols that will work over
>>> the
>>> Internet and also to enable interoperability between independent
>>> implementations.
>>>
>>> In the BFCP case the shipping implementations support TCP as the
>>> transport
>>> protocol but they encountered issues when running over the Internet due
>>> to
>>> devices like SBCs and due to lack of support for TCP media relay or
>>> ICE-TCP
>>> [I-D.ietf-mmusic-ice-tcp].
>>> When implementations looked at how to address the issue, the
>>> interoperability went away since there is no fall back solution for thi=
s
>>> real life case. Some did a fall back to HTTP and some did to UDP but no=
t
>>> in
>>> an interoperable way.
>>>
>>> In order to achieve interoperability, this draft is trying to extend th=
e
>>> current BFCP. It is not suggesting to replace TCP but to keep TCP as th=
e
>>> mandatory transport and use UDP as fallback if unable to establish TCP
>>> connection.
>>>
>>> As for security, if the topic will be adopted the solution will be
>>> updated
>>> to use DTLS as the transport for BFCP.
>>>
>>> I hope that people will read the draft and look at the objectives and t=
he
>>> proposed solution.
>>>
>>>
>>> BTW: This is a problem for client to client media connections over TCP
>>> and
>>> my understanding is that RTSP offers to use both TCP and UDP since both
>>> are
>>> specified. Since BFCP is not a payload but is running in parallel to th=
e
>>> RTP
>>> payload (for the point to point calls or MCU based multipoint) it needs
>>> similar transport options.
>>>
>>> Thanks
>>> Roni Even
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
>>>> Sent: Thursday, June 10, 2010 1:54 AM
>>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
>>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen'; xcon@ietf.org
>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>
>>>> What you are essentially saying is that all protocols in the future
>>>> that need reliable transport, as BFCP does, have to design in their ow=
n
>>>> reliable transport element so they can use UDP. This is not a BFCP
>>>> specific issue.
>>>>
>>>> I find that an unacceptable direction for IETF to be heading in.
>>>>
>>>> I would also note that you are also asking for adoption of a document
>>>> that cannot in its current form meet the security requirements of the
>>>> original RFC.
>>>>
>>>> regards
>>>>
>>>> Keith
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>>>> Sent: Wednesday, June 09, 2010 1:40 PM
>>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
>>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
>>>>> 'Tom Kristensen'; xcon@ietf.org
>>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>>
>>>>> Richard,
>>>>> The BFCP I used as a presentation token for video
>>>>> conferencing. What the implementers found out that TCP does
>>>>> not work in real networks due to Session border controllers
>>>>> not supporting TCP as used in BFCP.
>>>>> This is why in products they try to establish TCP connection
>>>>> and if fails tries UDP.
>>>>> The video conferencing vendors participating in the IMTC sip
>>>>> parity activity group defined an interoperability profile
>>>>> that references this option Roni Even
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>
>>>>> On Behalf
>>>>>>
>>>>>> Of Richard L. Barnes
>>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
>>>>>> To: Tom Kristensen
>>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
>>>>>> Kristensen; xcon@ietf.org
>>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>>>
>>>>>> Tom and others who are interested in this draft:
>>>>>>
>>>>>> For those who are relatively new here: Could you summarize why you
>>>>>> think this draft is needed? =A0What requirement does it meet
>>>>>
>>>>> that BFCP
>>>>>>
>>>>>> doesn't right now?
>>>>>>
>>>>>> Thanks,
>>>>>> --Richard
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
>>>>>>
>>>>>>> The UDP/BFCP draft has been presented and discussed in
>>>>>
>>>>> two or three
>>>>>>>
>>>>>>> IETF XCON sessions. No objection to the work being
>>>>>
>>>>> carried on, just
>>>>>>>
>>>>>>> that adoption as WG item was postponed until the draft was more
>>>>>>> complete. (This has been delayed of various reasons, but
>>>>>
>>>>> the authors
>>>>>>>
>>>>>>> believe the -02 version in question here should be ready for
>>>>>>> adoption).
>>>>>>>
>>>>>>> The "current status of consensus" might be valid for some, but
>>>>>>> participants in the XCON sessions and the minutes of meeting show
>>>>>>> progress away from that initial consensus.
>>>>>>>
>>>>>>> I believe Ott's concerns are either dealt with or at
>>>>>
>>>>> least mentioned
>>>>>>>
>>>>>>> in the draft. Arrest me if I'm wrong.
>>>>>>>
>>>>>>> -- Tom
>>>>>>>
>>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
>>>>>>> <keith.drage@alcatel-lucent.com> wrote:
>>>>>>>>
>>>>>>>> We made an explicit decision in the original draft that
>>>>>
>>>>> UDP was not
>>>>>>>>
>>>>>>>> required, not that we would do it later. That as far as I am
>>>>>>>> concerned represents the current status of consensus.
>>>>>>>>
>>>>>>>> This was done on the basis that we had all seen how UDP
>>>>>
>>>>> support had
>>>>>>>>
>>>>>>>> complicated SIP, and we did not want to repeat that issue.
>>>>>>>>
>>>>>>>> So this is not continuing the work. The status is an
>>>>>
>>>>> author draft
>>>>>>>>
>>>>>>>> which goes against a WG consensus position.
>>>>>>>>
>>>>>>>> I believe Georg Ott also expressed some concerns which I did not
>>>>>>>> see answered on list at all.
>>>>>>>>
>>>>>>>> regards
>>>>>>>>
>>>>>>>> Keith
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
>>>>>>>>> Behalf Of Roni Even
>>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
>>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
>>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>
>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>
>>>>>>>>> Hi Alan,
>>>>>>>>> I support this work and think it is urgent to finish it.
>>>>>>>>> I think that updating BFCP with UDP support is very
>>>>>
>>>>> important. I
>>>>>>>>>
>>>>>>>>> would like to mention that BFCP is being used in video
>>>>>>>>> conferencing application and since the implementers encountered
>>>>>>>>> problems with TCP they use a fall back to UDP.
>>>>>>>>> We discussed this work in previous IETF meeting and
>>>>>
>>>>> Gonzalo as far
>>>>>>>>>
>>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Roni Even
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>>>>>
>>>>>>>>> On Behalf
>>>>>>>>>>
>>>>>>>>>> Of Alan Johnston
>>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>>>>>>>>>> To: Tom Kristensen
>>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
>>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>>
>>>>>>>>>> Tom,
>>>>>>>>>>
>>>>>>>>>> Apologies for the delay in replying. =A0As you know, the
>>>>>>>>>
>>>>>>>>> working group
>>>>>>>>>>
>>>>>>>>>> is in the process of completing its final milestones.
>>>>>>>>>> Publication requests will be issued in the next few
>>>>>
>>>>> days for the
>>>>>>>>>>
>>>>>>>>>> data
>>>>>>>>>
>>>>>>>>> model, CCMP,
>>>>>>>>>>
>>>>>>>>>> and the Examples drafts.
>>>>>>>>>>
>>>>>>>>>> Taking on any new milestones for the working group
>>>>>
>>>>> would require:
>>>>>>>>>>
>>>>>>>>>> 1. Strong support and interest from working group
>>>>>
>>>>> participants 2.
>>>>>>>>>>
>>>>>>>>>> Approval of our ADs.
>>>>>>>>>>
>>>>>>>>>> I haven't seen evidence of either of these at this stage.
>>>>>>>>>>
>>>>>>>>>> A possible option is to take this work to DISPATCH, get an
>>>>>>>>>
>>>>>>>>> indication
>>>>>>>>>>
>>>>>>>>>> of interests, and get feedback on the best way to move
>>>>>
>>>>> this work
>>>>>>>>>>
>>>>>>>>>> forward.
>>>>>>>>>>
>>>>>>>>>> - Alan -
>>>>>>>>>> co-chair XCON
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>>>>>>>>>>>
>>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>>>>>>>>>
>>>>>>>>> early in
>>>>>>>>>>>
>>>>>>>>>>> March. No comments received since.
>>>>>>>>>>>
>>>>>>>>>>> We'd like guidance on the next steps. First we ask for
>>>>>>>>>
>>>>>>>>> adoption as
>>>>>>>>>>>
>>>>>>>>>>> WG item. Next step would include the merging process with bis
>>>>>>>>>>> versions
>>>>>>>>>>
>>>>>>>>>> of
>>>>>>>>>>>
>>>>>>>>>>> RFC 4582 and RFC 4583.
>>>>>>>>>>>
>>>>>>>>>>> We'd like to point out that interested parties for this
>>>>>>>>>
>>>>>>>>> work indeed
>>>>>>>>>>>
>>>>>>>>>>> exist.
>>>>>>>>>>>
>>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
>>>>>>>>>
>>>>>>>>> April and May.
>>>>>>>>>>
>>>>>>>>>> See
>>>>>>>>>>>
>>>>>>>>>>> below. No response given. Therefore, this request on
>>>>>
>>>>> the list.)
>>>>>>>>>>>
>>>>>>>>>>> -- Tom
>>>>>>>>>>>
>>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Chairs,
>>>>>>>>>>>>
>>>>>>>>>>>> Any thoughts or decision on this matter?
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> XCON chairs,
>>>>>>>>>>>>>
>>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
>>>>>
>>>>> early in March
>>>>>>>>>>>>>
>>>>>>>>>>>>> -
>>>>>>>>>>
>>>>>>>>>> well in
>>>>>>>>>>>>>
>>>>>>>>>>>>> advance of IETF-77.
>>>>>>>>>>>>> =A0http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
>>>>
>>>> udp
>>>>>>>>>>>>>
>>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
>>>>>>>>>
>>>>>>>>> directly to the
>>>>>>>>>>>>>
>>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
>>>>>>>>>
>>>>>>>>> as an XCON
>>>>>>>>>>>>>
>>>>>>>>>>>>> WG item.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> XCON mailing list
>>>>>>>>>> XCON@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> XCON mailing list
>>>>>>>>> XCON@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> XCON mailing list
>>>>>>>> XCON@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> # TANDBERG R&D
>>>>>>> ## http://www.tandberg.com
>>>>>>> ### http://folk.uio.no/tomkri/
>>>>>>> _______________________________________________
>>>>>>> XCON mailing list
>>>>>>> XCON@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>
>>>>>> _______________________________________________
>>>>>> XCON mailing list
>>>>>> XCON@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>
>>>>> =3D
>>>
>>> _______________________________________________
>>> XCON mailing list
>>> XCON@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xcon
>>>
>>
>>
>> --
>> Lorenzo Miniero
>> Meetecho s.r.l.
>> http://www.meetecho.com/
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>

From ron.even.tlv@gmail.com  Thu Jun 24 07:40:35 2010
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 383B53A6802 for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 07:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=1.207,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R7XF0BfTMfpU for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 07:40:31 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id ED4C03A67F9 for <xcon@ietf.org>; Thu, 24 Jun 2010 07:40:29 -0700 (PDT)
Received: by wwb22 with SMTP id 22so627551wwb.31 for <xcon@ietf.org>; Thu, 24 Jun 2010 07:40:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=boytaCYXF0KuEFqUhi9HT1Jr21akF3rocitZzXhZvHQ=; b=Nr64mpi7sguAJA0qz2ZgpQQYd9fpAgACxtQLQnDOzMdCCBNQt7Ndwf8XbmJP4sF/B9 ewnolnn26gOKJZULbfh5R7yRoN6hCqcHZyhD4QcGqbogRZwq9QquwkoiwoPO98VN5g7+ 3FuEr1oCsvMbhCwO9IgBuBswAkS2fIPIhozLw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=XYvTpRvkpFoovdA8nLvWypOKct38cbigR61uGOQEtn4bI6wirWdlKaK6o8CyuYzNj3 TrF3hJxn6nzh4NRzbkbduGmbxxjeyTKZ1xmgKd7R15c0ptj2gVRNXqlXvpbTufi9w1Bj Umt8Ux04N/oexASKhMLBbk23vYS7hfXzoWgbw=
Received: by 10.216.85.211 with SMTP id u61mr3903953wee.103.1277390434714; Thu, 24 Jun 2010 07:40:34 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-38-248.red.bezeqint.net [79.179.38.248]) by mx.google.com with ESMTPS id n29sm1598980wej.17.2010.06.24.07.40.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 24 Jun 2010 07:40:32 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Mary Barnes'" <mary.ietf.barnes@gmail.com>, "'Richard L. Barnes'" <rbarnes@bbn.com>
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>	<59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>	<4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<4c107733.df0ce30a.21ca.15cc@mx.google.com>	<20100610130009.1f1fbb03.lorenzo@meetecho.com>	<0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com> <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com>
In-Reply-To: <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com>
Date: Thu, 24 Jun 2010 17:40:25 +0300
Message-ID: <4c236e60.9d90d80a.1d25.6b10@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsS8L6juex13K82S6GqiItBFE9dVQAujJeQ
Content-Language: en-us
Cc: 'Alan Johnston' <alan.b.johnston@gmail.com>, 'Tom Kristensen' <tom.kristensen@tandberg.com>, 'Mark Thompson' <mark.thompson@tandberg.com>, "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 14:40:35 -0000

Mary,
I think that in the discussion in the past, Gonzalo suggested to do a =
bis
draft to RFC 4582. I think he mentioned other issues he wanted to =
update.
Roni Even

> -----Original Message-----
> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf =
Of
> Mary Barnes
> Sent: Wednesday, June 23, 2010 7:26 PM
> To: Richard L. Barnes
> Cc: Tom Kristensen; DRAGE, Keith (Keith); xcon@ietf.org; Mark =
Thompson;
> Alan Johnston
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>=20
> I have reviewed the draft in question and while I agree that this
> could be viewed as a workaround for some more general problems that
> need to be solved, there is a current industry need for the solution
> in this draft.   If the general problems described go to DISPATCH
> (which is the appropriate thing to do rather than bringing this
> specific document), the timeframe for getting agreement on the problem
> to be solved and for the solutions to be agreed would be far longer
> IMHO than if this document were progressed. If XCON would prefer to
> close the WG without progressing this document (in this form or as a
> -bis to RFC  4582), my suggestion would be to do as was done for the
> remaining SIP and SIPPING documents and progress this item as an
> individual AD sponsored.
>=20
> Mary.
>=20
> On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes <rbarnes@bbn.com>
> wrote:
> > <hat type=3D"individual"/>
> >
> > I tend to agree with Lorenzo that DISPATCH would be a better place =
to
> have
> > these discussions, especially given that, as far as I can tell from
> this
> > thread, the problem seems to be a general one of NAT traversal for
> TCP.
> >
> >
> >
> > On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
> >
> >> Hi all,
> >>
> >> with respect to this topic, I think there are many issues
> implementers
> >> have to face when bringing IETF solutions to the real world. We
> found
> >> ourselves many times in a situation in which some kind of work-
> around
> >> had to be devised in order to let things work properly. Just to =
cite
> a
> >> couple of examples, with BFCP we had to find a way to let it work =
in
> a
> >> distributed conferencing scenario (which is far from easy, given =
the
> >> intrinsic centralized model behind such protocol). In such case, we
> >> decided to encapsulate BFCP messages in the body of XMPP
> >> server-to-server packets (see the XCON-DCON Synchronization =
Protocol
> in
> >> draft-romano-dcon-xdsp-reqs-06 for the details) and then even
> devised
> >> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
> >> traversal issue, we also implemented an HTTP encapsulation. Moving
> >> further we even conceived a DTMF-based frontend to BFCP ;) and also
> >> almost thought about a BFCP-over-RTP approach.
> >>
> >> That said, I nevertheless agree with Keith on the discussion. Those
> >> problems may be common to other TCP-based protocols as well, and as
> such
> >> a generic solution (generic TCP over UDP, for instance, or anything
> >> else) may be a much better approach than doing a protocol specific
> >> patch. Besides, whatever the solution, it should also take care of
> how
> >> the negotiation of such channels would be affected (as is the
> >> case of RFC4583 for BFCP, which the proposed draft actually does).
> >>
> >> As Keith already suggested, DISPATCH may be a much better place to
> >> discuss this issue: DISPATCH is where we'll also propose the above
> >> mentioned DCON work.
> >>
> >> Lorenzo
> >>
> >>
> >>
> >> On Thu, 10 Jun 2010 08:22:55 +0300
> >> "Roni Even" <ron.even.tlv@gmail.com> wrote:
> >>
> >>> Hi =A0Keith,
> >>>
> >>> I think that the IETF is trying to design protocols that will work
> over
> >>> the
> >>> Internet and also to enable interoperability between independent
> >>> implementations.
> >>>
> >>> In the BFCP case the shipping implementations support TCP as the
> >>> transport
> >>> protocol but they encountered issues when running over the =
Internet
> due
> >>> to
> >>> devices like SBCs and due to lack of support for TCP media relay =
or
> >>> ICE-TCP
> >>> [I-D.ietf-mmusic-ice-tcp].
> >>> When implementations looked at how to address the issue, the
> >>> interoperability went away since there is no fall back solution =
for
> this
> >>> real life case. Some did a fall back to HTTP and some did to UDP
> but not
> >>> in
> >>> an interoperable way.
> >>>
> >>> In order to achieve interoperability, this draft is trying to
> extend the
> >>> current BFCP. It is not suggesting to replace TCP but to keep TCP
> as the
> >>> mandatory transport and use UDP as fallback if unable to establish
> TCP
> >>> connection.
> >>>
> >>> As for security, if the topic will be adopted the solution will be
> >>> updated
> >>> to use DTLS as the transport for BFCP.
> >>>
> >>> I hope that people will read the draft and look at the objectives
> and the
> >>> proposed solution.
> >>>
> >>>
> >>> BTW: This is a problem for client to client media connections over
> TCP
> >>> and
> >>> my understanding is that RTSP offers to use both TCP and UDP since
> both
> >>> are
> >>> specified. Since BFCP is not a payload but is running in parallel
> to the
> >>> RTP
> >>> payload (for the point to point calls or MCU based multipoint) it
> needs
> >>> similar transport options.
> >>>
> >>> Thanks
> >>> Roni Even
> >>>
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: DRAGE, Keith (Keith) =
[mailto:keith.drage@alcatel-lucent.com]
> >>>> Sent: Thursday, June 10, 2010 1:54 AM
> >>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> >>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
> xcon@ietf.org
> >>>> Subject: RE: [XCON] WG Adoption? =
draft-sandbakken-xcon-bfcp-udp-02
> >>>>
> >>>> What you are essentially saying is that all protocols in the
> future
> >>>> that need reliable transport, as BFCP does, have to design in
> their own
> >>>> reliable transport element so they can use UDP. This is not a =
BFCP
> >>>> specific issue.
> >>>>
> >>>> I find that an unacceptable direction for IETF to be heading in.
> >>>>
> >>>> I would also note that you are also asking for adoption of a
> document
> >>>> that cannot in its current form meet the security requirements of
> the
> >>>> original RFC.
> >>>>
> >>>> regards
> >>>>
> >>>> Keith
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> >>>>> Sent: Wednesday, June 09, 2010 1:40 PM
> >>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
> >>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> >>>>> 'Tom Kristensen'; xcon@ietf.org
> >>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> 02
> >>>>>
> >>>>> Richard,
> >>>>> The BFCP I used as a presentation token for video
> >>>>> conferencing. What the implementers found out that TCP does
> >>>>> not work in real networks due to Session border controllers
> >>>>> not supporting TCP as used in BFCP.
> >>>>> This is why in products they try to establish TCP connection
> >>>>> and if fails tries UDP.
> >>>>> The video conferencing vendors participating in the IMTC sip
> >>>>> parity activity group defined an interoperability profile
> >>>>> that references this option Roni Even
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >>>>>
> >>>>> On Behalf
> >>>>>>
> >>>>>> Of Richard L. Barnes
> >>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
> >>>>>> To: Tom Kristensen
> >>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> >>>>>> Kristensen; xcon@ietf.org
> >>>>>> Subject: Re: [XCON] WG Adoption? =
draft-sandbakken-xcon-bfcp-udp-
> 02
> >>>>>>
> >>>>>> Tom and others who are interested in this draft:
> >>>>>>
> >>>>>> For those who are relatively new here: Could you summarize why
> you
> >>>>>> think this draft is needed? =A0What requirement does it meet
> >>>>>
> >>>>> that BFCP
> >>>>>>
> >>>>>> doesn't right now?
> >>>>>>
> >>>>>> Thanks,
> >>>>>> --Richard
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> >>>>>>
> >>>>>>> The UDP/BFCP draft has been presented and discussed in
> >>>>>
> >>>>> two or three
> >>>>>>>
> >>>>>>> IETF XCON sessions. No objection to the work being
> >>>>>
> >>>>> carried on, just
> >>>>>>>
> >>>>>>> that adoption as WG item was postponed until the draft was =
more
> >>>>>>> complete. (This has been delayed of various reasons, but
> >>>>>
> >>>>> the authors
> >>>>>>>
> >>>>>>> believe the -02 version in question here should be ready for
> >>>>>>> adoption).
> >>>>>>>
> >>>>>>> The "current status of consensus" might be valid for some, but
> >>>>>>> participants in the XCON sessions and the minutes of meeting
> show
> >>>>>>> progress away from that initial consensus.
> >>>>>>>
> >>>>>>> I believe Ott's concerns are either dealt with or at
> >>>>>
> >>>>> least mentioned
> >>>>>>>
> >>>>>>> in the draft. Arrest me if I'm wrong.
> >>>>>>>
> >>>>>>> -- Tom
> >>>>>>>
> >>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
> >>>>>>> <keith.drage@alcatel-lucent.com> wrote:
> >>>>>>>>
> >>>>>>>> We made an explicit decision in the original draft that
> >>>>>
> >>>>> UDP was not
> >>>>>>>>
> >>>>>>>> required, not that we would do it later. That as far as I am
> >>>>>>>> concerned represents the current status of consensus.
> >>>>>>>>
> >>>>>>>> This was done on the basis that we had all seen how UDP
> >>>>>
> >>>>> support had
> >>>>>>>>
> >>>>>>>> complicated SIP, and we did not want to repeat that issue.
> >>>>>>>>
> >>>>>>>> So this is not continuing the work. The status is an
> >>>>>
> >>>>> author draft
> >>>>>>>>
> >>>>>>>> which goes against a WG consensus position.
> >>>>>>>>
> >>>>>>>> I believe Georg Ott also expressed some concerns which I did
> not
> >>>>>>>> see answered on list at all.
> >>>>>>>>
> >>>>>>>> regards
> >>>>>>>>
> >>>>>>>> Keith
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] =
On
> >>>>>>>>> Behalf Of Roni Even
> >>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
> >>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
> >>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
> >>>>>>>>> Subject: Re: [XCON] WG Adoption?
> >>>>>
> >>>>> draft-sandbakken-xcon-bfcp-udp-02
> >>>>>>>>>
> >>>>>>>>> Hi Alan,
> >>>>>>>>> I support this work and think it is urgent to finish it.
> >>>>>>>>> I think that updating BFCP with UDP support is very
> >>>>>
> >>>>> important. I
> >>>>>>>>>
> >>>>>>>>> would like to mention that BFCP is being used in video
> >>>>>>>>> conferencing application and since the implementers
> encountered
> >>>>>>>>> problems with TCP they use a fall back to UDP.
> >>>>>>>>> We discussed this work in previous IETF meeting and
> >>>>>
> >>>>> Gonzalo as far
> >>>>>>>>>
> >>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
> >>>>>>>>>
> >>>>>>>>> Thanks
> >>>>>>>>> Roni Even
> >>>>>>>>>
> >>>>>>>>>> -----Original Message-----
> >>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >>>>>>>>>
> >>>>>>>>> On Behalf
> >>>>>>>>>>
> >>>>>>>>>> Of Alan Johnston
> >>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
> >>>>>>>>>> To: Tom Kristensen
> >>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
> >>>>>>>>>> Subject: Re: [XCON] WG Adoption?
> >>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
> >>>>>>>>>>
> >>>>>>>>>> Tom,
> >>>>>>>>>>
> >>>>>>>>>> Apologies for the delay in replying. =A0As you know, the
> >>>>>>>>>
> >>>>>>>>> working group
> >>>>>>>>>>
> >>>>>>>>>> is in the process of completing its final milestones.
> >>>>>>>>>> Publication requests will be issued in the next few
> >>>>>
> >>>>> days for the
> >>>>>>>>>>
> >>>>>>>>>> data
> >>>>>>>>>
> >>>>>>>>> model, CCMP,
> >>>>>>>>>>
> >>>>>>>>>> and the Examples drafts.
> >>>>>>>>>>
> >>>>>>>>>> Taking on any new milestones for the working group
> >>>>>
> >>>>> would require:
> >>>>>>>>>>
> >>>>>>>>>> 1. Strong support and interest from working group
> >>>>>
> >>>>> participants 2.
> >>>>>>>>>>
> >>>>>>>>>> Approval of our ADs.
> >>>>>>>>>>
> >>>>>>>>>> I haven't seen evidence of either of these at this stage.
> >>>>>>>>>>
> >>>>>>>>>> A possible option is to take this work to DISPATCH, get an
> >>>>>>>>>
> >>>>>>>>> indication
> >>>>>>>>>>
> >>>>>>>>>> of interests, and get feedback on the best way to move
> >>>>>
> >>>>> this work
> >>>>>>>>>>
> >>>>>>>>>> forward.
> >>>>>>>>>>
> >>>>>>>>>> - Alan -
> >>>>>>>>>> co-chair XCON
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> >>>>>>>>>
> >>>>>>>>> early in
> >>>>>>>>>>>
> >>>>>>>>>>> March. No comments received since.
> >>>>>>>>>>>
> >>>>>>>>>>> We'd like guidance on the next steps. First we ask for
> >>>>>>>>>
> >>>>>>>>> adoption as
> >>>>>>>>>>>
> >>>>>>>>>>> WG item. Next step would include the merging process with
> bis
> >>>>>>>>>>> versions
> >>>>>>>>>>
> >>>>>>>>>> of
> >>>>>>>>>>>
> >>>>>>>>>>> RFC 4582 and RFC 4583.
> >>>>>>>>>>>
> >>>>>>>>>>> We'd like to point out that interested parties for this
> >>>>>>>>>
> >>>>>>>>> work indeed
> >>>>>>>>>>>
> >>>>>>>>>>> exist.
> >>>>>>>>>>>
> >>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
> >>>>>>>>>
> >>>>>>>>> April and May.
> >>>>>>>>>>
> >>>>>>>>>> See
> >>>>>>>>>>>
> >>>>>>>>>>> below. No response given. Therefore, this request on
> >>>>>
> >>>>> the list.)
> >>>>>>>>>>>
> >>>>>>>>>>> -- Tom
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Chairs,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Any thoughts or decision on this matter?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Cheers,
> >>>>>>>>>>>> -- Tom
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> XCON chairs,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> >>>>>
> >>>>> early in March
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> -
> >>>>>>>>>>
> >>>>>>>>>> well in
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> advance of IETF-77.
> >>>>>>>>>>>>> =
=A0http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
> >>>>
> >>>> udp
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
> >>>>>>>>>
> >>>>>>>>> directly to the
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
> >>>>>>>>>
> >>>>>>>>> as an XCON
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> WG item.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> -- Tom
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> XCON mailing list
> >>>>>>>>>> XCON@ietf.org
> >>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> XCON mailing list
> >>>>>>>>> XCON@ietf.org
> >>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> XCON mailing list
> >>>>>>>> XCON@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> # TANDBERG R&D
> >>>>>>> ## http://www.tandberg.com
> >>>>>>> ### http://folk.uio.no/tomkri/
> >>>>>>> _______________________________________________
> >>>>>>> XCON mailing list
> >>>>>>> XCON@ietf.org
> >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> XCON mailing list
> >>>>>> XCON@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >>>>>
> >>>>> =3D
> >>>
> >>> _______________________________________________
> >>> XCON mailing list
> >>> XCON@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/xcon
> >>>
> >>
> >>
> >> --
> >> Lorenzo Miniero
> >> Meetecho s.r.l.
> >> http://www.meetecho.com/
> >
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
> >
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From 2mkristensen@gmail.com  Thu Jun 24 07:50:35 2010
Return-Path: <2mkristensen@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9C393A6A26 for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 07:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=1.207,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLMy6zf3EKMb for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 07:50:31 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 917223A69F5 for <xcon@ietf.org>; Thu, 24 Jun 2010 07:50:00 -0700 (PDT)
Received: by fxm20 with SMTP id 20so1296832fxm.31 for <xcon@ietf.org>; Thu, 24 Jun 2010 07:50:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+TEirHIKutsoyj3XDEk5+ToM90sLLIlmho91vrZ4jao=; b=D3/edZX/DYVBHdak44I+JcDc2dPHCNZxXTP3X2sVCBZSDHkRPsdvwGxBDdpGCirwHB PRjWx/rf3l/WRXDKvXfd9Sbdx6DL2H0aDw6B2cZa1TWeRIcyg3M+/kFaEgJOAm9dQqTq A2n1Cbjj3y2oyehawlYRtWK8pJszlpG+xdMNA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=vjUjw4RT/qKPbVoATZ4qxrdZ33L1MzA+0lW7hPBxqHPzVmLosbCtaD+kbB7q/Kf+Nz 6an7Glm3aOsUBlMDrtFzBSkAeMDMw8Vn89usF5z0seNm4XqkM7d22WB4C7g0UtKMtzPw cr2FCOH1FaveX9F5orl/yChj5os4S7F3bzwME=
MIME-Version: 1.0
Received: by 10.223.103.202 with SMTP id l10mr210405fao.33.1277391005465; Thu,  24 Jun 2010 07:50:05 -0700 (PDT)
Received: by 10.223.125.209 with HTTP; Thu, 24 Jun 2010 07:50:05 -0700 (PDT)
In-Reply-To: <4c236e60.9d90d80a.1d25.6b10@mx.google.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4c107733.df0ce30a.21ca.15cc@mx.google.com> <20100610130009.1f1fbb03.lorenzo@meetecho.com> <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com> <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com> <4c236e60.9d90d80a.1d25.6b10@mx.google.com>
Date: Thu, 24 Jun 2010 16:50:05 +0200
Message-ID: <AANLkTimUQ6pGeRyRbGd68dyu9Y2EitVhWl8ANU-DuauK@mail.gmail.com>
From: Tom Kristensen <2mkristensen@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Mark Thompson <mark.thompson@tandberg.com>, Alan Johnston <alan.b.johnston@gmail.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, xcon@ietf.org, Tom Kristensen <tom.kristensen@tandberg.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 14:50:35 -0000

That's correct, Roni.

The thread starting with a list of issues in addition to the UDP/BFCP
extension is available in the list archives here:
http://www.ietf.org/mail-archive/web/xcon/current/msg02231.html

-- Tom


2010/6/24 Roni Even <ron.even.tlv@gmail.com>:
> Mary,
> I think that in the discussion in the past, Gonzalo suggested to do a bis
> draft to RFC 4582. I think he mentioned other issues he wanted to update.
> Roni Even
>
>> -----Original Message-----
>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
>> Mary Barnes
>> Sent: Wednesday, June 23, 2010 7:26 PM
>> To: Richard L. Barnes
>> Cc: Tom Kristensen; DRAGE, Keith (Keith); xcon@ietf.org; Mark Thompson;
>> Alan Johnston
>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>
>> I have reviewed the draft in question and while I agree that this
>> could be viewed as a workaround for some more general problems that
>> need to be solved, there is a current industry need for the solution
>> in this draft. =A0 If the general problems described go to DISPATCH
>> (which is the appropriate thing to do rather than bringing this
>> specific document), the timeframe for getting agreement on the problem
>> to be solved and for the solutions to be agreed would be far longer
>> IMHO than if this document were progressed. If XCON would prefer to
>> close the WG without progressing this document (in this form or as a
>> -bis to RFC =A04582), my suggestion would be to do as was done for the
>> remaining SIP and SIPPING documents and progress this item as an
>> individual AD sponsored.
>>
>> Mary.
>>
>> On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes <rbarnes@bbn.com>
>> wrote:
>> > <hat type=3D"individual"/>
>> >
>> > I tend to agree with Lorenzo that DISPATCH would be a better place to
>> have
>> > these discussions, especially given that, as far as I can tell from
>> this
>> > thread, the problem seems to be a general one of NAT traversal for
>> TCP.
>> >
>> >
>> >
>> > On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
>> >
>> >> Hi all,
>> >>
>> >> with respect to this topic, I think there are many issues
>> implementers
>> >> have to face when bringing IETF solutions to the real world. We
>> found
>> >> ourselves many times in a situation in which some kind of work-
>> around
>> >> had to be devised in order to let things work properly. Just to cite
>> a
>> >> couple of examples, with BFCP we had to find a way to let it work in
>> a
>> >> distributed conferencing scenario (which is far from easy, given the
>> >> intrinsic centralized model behind such protocol). In such case, we
>> >> decided to encapsulate BFCP messages in the body of XMPP
>> >> server-to-server packets (see the XCON-DCON Synchronization Protocol
>> in
>> >> draft-romano-dcon-xdsp-reqs-06 for the details) and then even
>> devised
>> >> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
>> >> traversal issue, we also implemented an HTTP encapsulation. Moving
>> >> further we even conceived a DTMF-based frontend to BFCP ;) and also
>> >> almost thought about a BFCP-over-RTP approach.
>> >>
>> >> That said, I nevertheless agree with Keith on the discussion. Those
>> >> problems may be common to other TCP-based protocols as well, and as
>> such
>> >> a generic solution (generic TCP over UDP, for instance, or anything
>> >> else) may be a much better approach than doing a protocol specific
>> >> patch. Besides, whatever the solution, it should also take care of
>> how
>> >> the negotiation of such channels would be affected (as is the
>> >> case of RFC4583 for BFCP, which the proposed draft actually does).
>> >>
>> >> As Keith already suggested, DISPATCH may be a much better place to
>> >> discuss this issue: DISPATCH is where we'll also propose the above
>> >> mentioned DCON work.
>> >>
>> >> Lorenzo
>> >>
>> >>
>> >>
>> >> On Thu, 10 Jun 2010 08:22:55 +0300
>> >> "Roni Even" <ron.even.tlv@gmail.com> wrote:
>> >>
>> >>> Hi =A0Keith,
>> >>>
>> >>> I think that the IETF is trying to design protocols that will work
>> over
>> >>> the
>> >>> Internet and also to enable interoperability between independent
>> >>> implementations.
>> >>>
>> >>> In the BFCP case the shipping implementations support TCP as the
>> >>> transport
>> >>> protocol but they encountered issues when running over the Internet
>> due
>> >>> to
>> >>> devices like SBCs and due to lack of support for TCP media relay or
>> >>> ICE-TCP
>> >>> [I-D.ietf-mmusic-ice-tcp].
>> >>> When implementations looked at how to address the issue, the
>> >>> interoperability went away since there is no fall back solution for
>> this
>> >>> real life case. Some did a fall back to HTTP and some did to UDP
>> but not
>> >>> in
>> >>> an interoperable way.
>> >>>
>> >>> In order to achieve interoperability, this draft is trying to
>> extend the
>> >>> current BFCP. It is not suggesting to replace TCP but to keep TCP
>> as the
>> >>> mandatory transport and use UDP as fallback if unable to establish
>> TCP
>> >>> connection.
>> >>>
>> >>> As for security, if the topic will be adopted the solution will be
>> >>> updated
>> >>> to use DTLS as the transport for BFCP.
>> >>>
>> >>> I hope that people will read the draft and look at the objectives
>> and the
>> >>> proposed solution.
>> >>>
>> >>>
>> >>> BTW: This is a problem for client to client media connections over
>> TCP
>> >>> and
>> >>> my understanding is that RTSP offers to use both TCP and UDP since
>> both
>> >>> are
>> >>> specified. Since BFCP is not a payload but is running in parallel
>> to the
>> >>> RTP
>> >>> payload (for the point to point calls or MCU based multipoint) it
>> needs
>> >>> similar transport options.
>> >>>
>> >>> Thanks
>> >>> Roni Even
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>> -----Original Message-----
>> >>>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
>> >>>> Sent: Thursday, June 10, 2010 1:54 AM
>> >>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
>> >>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
>> xcon@ietf.org
>> >>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>> >>>>
>> >>>> What you are essentially saying is that all protocols in the
>> future
>> >>>> that need reliable transport, as BFCP does, have to design in
>> their own
>> >>>> reliable transport element so they can use UDP. This is not a BFCP
>> >>>> specific issue.
>> >>>>
>> >>>> I find that an unacceptable direction for IETF to be heading in.
>> >>>>
>> >>>> I would also note that you are also asking for adoption of a
>> document
>> >>>> that cannot in its current form meet the security requirements of
>> the
>> >>>> original RFC.
>> >>>>
>> >>>> regards
>> >>>>
>> >>>> Keith
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>> -----Original Message-----
>> >>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>> >>>>> Sent: Wednesday, June 09, 2010 1:40 PM
>> >>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
>> >>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
>> >>>>> 'Tom Kristensen'; xcon@ietf.org
>> >>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
>> 02
>> >>>>>
>> >>>>> Richard,
>> >>>>> The BFCP I used as a presentation token for video
>> >>>>> conferencing. What the implementers found out that TCP does
>> >>>>> not work in real networks due to Session border controllers
>> >>>>> not supporting TCP as used in BFCP.
>> >>>>> This is why in products they try to establish TCP connection
>> >>>>> and if fails tries UDP.
>> >>>>> The video conferencing vendors participating in the IMTC sip
>> >>>>> parity activity group defined an interoperability profile
>> >>>>> that references this option Roni Even
>> >>>>>
>> >>>>>> -----Original Message-----
>> >>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>> >>>>>
>> >>>>> On Behalf
>> >>>>>>
>> >>>>>> Of Richard L. Barnes
>> >>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
>> >>>>>> To: Tom Kristensen
>> >>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
>> >>>>>> Kristensen; xcon@ietf.org
>> >>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
>> 02
>> >>>>>>
>> >>>>>> Tom and others who are interested in this draft:
>> >>>>>>
>> >>>>>> For those who are relatively new here: Could you summarize why
>> you
>> >>>>>> think this draft is needed? =A0What requirement does it meet
>> >>>>>
>> >>>>> that BFCP
>> >>>>>>
>> >>>>>> doesn't right now?
>> >>>>>>
>> >>>>>> Thanks,
>> >>>>>> --Richard
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
>> >>>>>>
>> >>>>>>> The UDP/BFCP draft has been presented and discussed in
>> >>>>>
>> >>>>> two or three
>> >>>>>>>
>> >>>>>>> IETF XCON sessions. No objection to the work being
>> >>>>>
>> >>>>> carried on, just
>> >>>>>>>
>> >>>>>>> that adoption as WG item was postponed until the draft was more
>> >>>>>>> complete. (This has been delayed of various reasons, but
>> >>>>>
>> >>>>> the authors
>> >>>>>>>
>> >>>>>>> believe the -02 version in question here should be ready for
>> >>>>>>> adoption).
>> >>>>>>>
>> >>>>>>> The "current status of consensus" might be valid for some, but
>> >>>>>>> participants in the XCON sessions and the minutes of meeting
>> show
>> >>>>>>> progress away from that initial consensus.
>> >>>>>>>
>> >>>>>>> I believe Ott's concerns are either dealt with or at
>> >>>>>
>> >>>>> least mentioned
>> >>>>>>>
>> >>>>>>> in the draft. Arrest me if I'm wrong.
>> >>>>>>>
>> >>>>>>> -- Tom
>> >>>>>>>
>> >>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
>> >>>>>>> <keith.drage@alcatel-lucent.com> wrote:
>> >>>>>>>>
>> >>>>>>>> We made an explicit decision in the original draft that
>> >>>>>
>> >>>>> UDP was not
>> >>>>>>>>
>> >>>>>>>> required, not that we would do it later. That as far as I am
>> >>>>>>>> concerned represents the current status of consensus.
>> >>>>>>>>
>> >>>>>>>> This was done on the basis that we had all seen how UDP
>> >>>>>
>> >>>>> support had
>> >>>>>>>>
>> >>>>>>>> complicated SIP, and we did not want to repeat that issue.
>> >>>>>>>>
>> >>>>>>>> So this is not continuing the work. The status is an
>> >>>>>
>> >>>>> author draft
>> >>>>>>>>
>> >>>>>>>> which goes against a WG consensus position.
>> >>>>>>>>
>> >>>>>>>> I believe Georg Ott also expressed some concerns which I did
>> not
>> >>>>>>>> see answered on list at all.
>> >>>>>>>>
>> >>>>>>>> regards
>> >>>>>>>>
>> >>>>>>>> Keith
>> >>>>>>>>
>> >>>>>>>>> -----Original Message-----
>> >>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
>> >>>>>>>>> Behalf Of Roni Even
>> >>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
>> >>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
>> >>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
>> >>>>>>>>> Subject: Re: [XCON] WG Adoption?
>> >>>>>
>> >>>>> draft-sandbakken-xcon-bfcp-udp-02
>> >>>>>>>>>
>> >>>>>>>>> Hi Alan,
>> >>>>>>>>> I support this work and think it is urgent to finish it.
>> >>>>>>>>> I think that updating BFCP with UDP support is very
>> >>>>>
>> >>>>> important. I
>> >>>>>>>>>
>> >>>>>>>>> would like to mention that BFCP is being used in video
>> >>>>>>>>> conferencing application and since the implementers
>> encountered
>> >>>>>>>>> problems with TCP they use a fall back to UDP.
>> >>>>>>>>> We discussed this work in previous IETF meeting and
>> >>>>>
>> >>>>> Gonzalo as far
>> >>>>>>>>>
>> >>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
>> >>>>>>>>>
>> >>>>>>>>> Thanks
>> >>>>>>>>> Roni Even
>> >>>>>>>>>
>> >>>>>>>>>> -----Original Message-----
>> >>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>> >>>>>>>>>
>> >>>>>>>>> On Behalf
>> >>>>>>>>>>
>> >>>>>>>>>> Of Alan Johnston
>> >>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>> >>>>>>>>>> To: Tom Kristensen
>> >>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
>> >>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>> >>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>> >>>>>>>>>>
>> >>>>>>>>>> Tom,
>> >>>>>>>>>>
>> >>>>>>>>>> Apologies for the delay in replying. =A0As you know, the
>> >>>>>>>>>
>> >>>>>>>>> working group
>> >>>>>>>>>>
>> >>>>>>>>>> is in the process of completing its final milestones.
>> >>>>>>>>>> Publication requests will be issued in the next few
>> >>>>>
>> >>>>> days for the
>> >>>>>>>>>>
>> >>>>>>>>>> data
>> >>>>>>>>>
>> >>>>>>>>> model, CCMP,
>> >>>>>>>>>>
>> >>>>>>>>>> and the Examples drafts.
>> >>>>>>>>>>
>> >>>>>>>>>> Taking on any new milestones for the working group
>> >>>>>
>> >>>>> would require:
>> >>>>>>>>>>
>> >>>>>>>>>> 1. Strong support and interest from working group
>> >>>>>
>> >>>>> participants 2.
>> >>>>>>>>>>
>> >>>>>>>>>> Approval of our ADs.
>> >>>>>>>>>>
>> >>>>>>>>>> I haven't seen evidence of either of these at this stage.
>> >>>>>>>>>>
>> >>>>>>>>>> A possible option is to take this work to DISPATCH, get an
>> >>>>>>>>>
>> >>>>>>>>> indication
>> >>>>>>>>>>
>> >>>>>>>>>> of interests, and get feedback on the best way to move
>> >>>>>
>> >>>>> this work
>> >>>>>>>>>>
>> >>>>>>>>>> forward.
>> >>>>>>>>>>
>> >>>>>>>>>> - Alan -
>> >>>>>>>>>> co-chair XCON
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>> >>>>>>>>>
>> >>>>>>>>> early in
>> >>>>>>>>>>>
>> >>>>>>>>>>> March. No comments received since.
>> >>>>>>>>>>>
>> >>>>>>>>>>> We'd like guidance on the next steps. First we ask for
>> >>>>>>>>>
>> >>>>>>>>> adoption as
>> >>>>>>>>>>>
>> >>>>>>>>>>> WG item. Next step would include the merging process with
>> bis
>> >>>>>>>>>>> versions
>> >>>>>>>>>>
>> >>>>>>>>>> of
>> >>>>>>>>>>>
>> >>>>>>>>>>> RFC 4582 and RFC 4583.
>> >>>>>>>>>>>
>> >>>>>>>>>>> We'd like to point out that interested parties for this
>> >>>>>>>>>
>> >>>>>>>>> work indeed
>> >>>>>>>>>>>
>> >>>>>>>>>>> exist.
>> >>>>>>>>>>>
>> >>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
>> >>>>>>>>>
>> >>>>>>>>> April and May.
>> >>>>>>>>>>
>> >>>>>>>>>> See
>> >>>>>>>>>>>
>> >>>>>>>>>>> below. No response given. Therefore, this request on
>> >>>>>
>> >>>>> the list.)
>> >>>>>>>>>>>
>> >>>>>>>>>>> -- Tom
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Chairs,
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Any thoughts or decision on this matter?
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Cheers,
>> >>>>>>>>>>>> -- Tom
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> XCON chairs,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
>> >>>>>
>> >>>>> early in March
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> -
>> >>>>>>>>>>
>> >>>>>>>>>> well in
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> advance of IETF-77.
>> >>>>>>>>>>>>> =A0http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
>> >>>>
>> >>>> udp
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
>> >>>>>>>>>
>> >>>>>>>>> directly to the
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
>> >>>>>>>>>
>> >>>>>>>>> as an XCON
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> WG item.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> -- Tom
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>> _______________________________________________
>> >>>>>>>>>> XCON mailing list
>> >>>>>>>>>> XCON@ietf.org
>> >>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>> >>>>>>>>>
>> >>>>>>>>> _______________________________________________
>> >>>>>>>>> XCON mailing list
>> >>>>>>>>> XCON@ietf.org
>> >>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>> >>>>>>>>>
>> >>>>>>>> _______________________________________________
>> >>>>>>>> XCON mailing list
>> >>>>>>>> XCON@ietf.org
>> >>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> # TANDBERG R&D
>> >>>>>>> ## http://www.tandberg.com
>> >>>>>>> ### http://folk.uio.no/tomkri/
>> >>>>>>> _______________________________________________
>> >>>>>>> XCON mailing list
>> >>>>>>> XCON@ietf.org
>> >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>> >>>>>>
>> >>>>>> _______________________________________________
>> >>>>>> XCON mailing list
>> >>>>>> XCON@ietf.org
>> >>>>>> https://www.ietf.org/mailman/listinfo/xcon
>> >>>>>
>> >>>>> =3D
>> >>>
>> >>> _______________________________________________
>> >>> XCON mailing list
>> >>> XCON@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/xcon
>> >>>
>> >>
>> >>
>> >> --
>> >> Lorenzo Miniero
>> >> Meetecho s.r.l.
>> >> http://www.meetecho.com/
>> >
>> > _______________________________________________
>> > XCON mailing list
>> > XCON@ietf.org
>> > https://www.ietf.org/mailman/listinfo/xcon
>> >
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>



--=20
# TANDBERG R&D
## http://www.tandberg.com
### http://folk.uio.no/tomkri/

From stephen.botzko@gmail.com  Thu Jun 24 08:29:39 2010
Return-Path: <stephen.botzko@gmail.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 005243A69E0 for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 08:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qR-+tv+vZq5l for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 08:29:34 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id D57BC3A69EC for <xcon@ietf.org>; Thu, 24 Jun 2010 08:29:22 -0700 (PDT)
Received: by wwb22 with SMTP id 22so673099wwb.31 for <xcon@ietf.org>; Thu, 24 Jun 2010 08:29:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=p7KGIz99/5A0jF1EszHa82B8Vx2fmKz96t+WaaWwppo=; b=GdWXaQvBOwwi7ENNuiUB+ZIIQ2h+Z8R+WXR8kMpLB1fT/a2SbfJut9TWUdwHfdNk6l cgiBv5Tx2RGlnljLag+FEYnXj6R9MR/QFWWpH8O8wbaSTFgkel/q/KuBzu2VgJihX1sL X/HCsEyimPwmGtY/Ml/XtBEhCkBERjADWpdWo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ZdqStsALWCjTgO2eVfOy8KWWHfosekfKZDZmzxtN3Rcjc6xprISTr+YBevYjvZNTQ1 v6gVmggLeLYSkoVSkwejWe+gOjx2QmqPlINdEuwW/efh4xLfwFjWGHJesdVRXGoL7IE7 CGWRzeqLeVOwpKYl/h0nDTmsiBrntM7biFSVE=
MIME-Version: 1.0
Received: by 10.216.88.6 with SMTP id z6mr7492453wee.79.1277393367309; Thu, 24  Jun 2010 08:29:27 -0700 (PDT)
Received: by 10.216.11.132 with HTTP; Thu, 24 Jun 2010 08:29:27 -0700 (PDT)
In-Reply-To: <4c236e60.9d90d80a.1d25.6b10@mx.google.com>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4c107733.df0ce30a.21ca.15cc@mx.google.com> <20100610130009.1f1fbb03.lorenzo@meetecho.com> <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com> <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com> <4c236e60.9d90d80a.1d25.6b10@mx.google.com>
Date: Thu, 24 Jun 2010 11:29:27 -0400
Message-ID: <AANLkTinzNkKCmheW9CM85ppzBlhL3tM0eh87iKM-29A_@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6d9746ee59eba0489c8518b
Cc: Mark Thompson <mark.thompson@tandberg.com>, Alan Johnston <alan.b.johnston@gmail.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, xcon@ietf.org, Tom Kristensen <tom.kristensen@tandberg.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 15:29:39 -0000

--0016e6d9746ee59eba0489c8518b
Content-Type: text/plain; charset=ISO-8859-1

BFCP is an important component in our application (videoconferencing).  The
inability to use BFCP when TCP cannot be used is a huge problem for us
today.

So I would like to see this document progressed.

If for some reason XCON doesn't finish it before the WG is closed, I think
Mary's suggestion of progressing it under individual AD sponsorship is good.

Stephen Botzko



2010/6/24 Roni Even <ron.even.tlv@gmail.com>

> Mary,
> I think that in the discussion in the past, Gonzalo suggested to do a bis
> draft to RFC 4582. I think he mentioned other issues he wanted to update.
> Roni Even
>
> > -----Original Message-----
> > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
> > Mary Barnes
> > Sent: Wednesday, June 23, 2010 7:26 PM
> > To: Richard L. Barnes
> > Cc: Tom Kristensen; DRAGE, Keith (Keith); xcon@ietf.org; Mark Thompson;
> > Alan Johnston
> > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >
> > I have reviewed the draft in question and while I agree that this
> > could be viewed as a workaround for some more general problems that
> > need to be solved, there is a current industry need for the solution
> > in this draft.   If the general problems described go to DISPATCH
> > (which is the appropriate thing to do rather than bringing this
> > specific document), the timeframe for getting agreement on the problem
> > to be solved and for the solutions to be agreed would be far longer
> > IMHO than if this document were progressed. If XCON would prefer to
> > close the WG without progressing this document (in this form or as a
> > -bis to RFC  4582), my suggestion would be to do as was done for the
> > remaining SIP and SIPPING documents and progress this item as an
> > individual AD sponsored.
> >
> > Mary.
> >
> > On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes <rbarnes@bbn.com>
> > wrote:
> > > <hat type="individual"/>
> > >
> > > I tend to agree with Lorenzo that DISPATCH would be a better place to
> > have
> > > these discussions, especially given that, as far as I can tell from
> > this
> > > thread, the problem seems to be a general one of NAT traversal for
> > TCP.
> > >
> > >
> > >
> > > On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
> > >
> > >> Hi all,
> > >>
> > >> with respect to this topic, I think there are many issues
> > implementers
> > >> have to face when bringing IETF solutions to the real world. We
> > found
> > >> ourselves many times in a situation in which some kind of work-
> > around
> > >> had to be devised in order to let things work properly. Just to cite
> > a
> > >> couple of examples, with BFCP we had to find a way to let it work in
> > a
> > >> distributed conferencing scenario (which is far from easy, given the
> > >> intrinsic centralized model behind such protocol). In such case, we
> > >> decided to encapsulate BFCP messages in the body of XMPP
> > >> server-to-server packets (see the XCON-DCON Synchronization Protocol
> > in
> > >> draft-romano-dcon-xdsp-reqs-06 for the details) and then even
> > devised
> > >> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
> > >> traversal issue, we also implemented an HTTP encapsulation. Moving
> > >> further we even conceived a DTMF-based frontend to BFCP ;) and also
> > >> almost thought about a BFCP-over-RTP approach.
> > >>
> > >> That said, I nevertheless agree with Keith on the discussion. Those
> > >> problems may be common to other TCP-based protocols as well, and as
> > such
> > >> a generic solution (generic TCP over UDP, for instance, or anything
> > >> else) may be a much better approach than doing a protocol specific
> > >> patch. Besides, whatever the solution, it should also take care of
> > how
> > >> the negotiation of such channels would be affected (as is the
> > >> case of RFC4583 for BFCP, which the proposed draft actually does).
> > >>
> > >> As Keith already suggested, DISPATCH may be a much better place to
> > >> discuss this issue: DISPATCH is where we'll also propose the above
> > >> mentioned DCON work.
> > >>
> > >> Lorenzo
> > >>
> > >>
> > >>
> > >> On Thu, 10 Jun 2010 08:22:55 +0300
> > >> "Roni Even" <ron.even.tlv@gmail.com> wrote:
> > >>
> > >>> Hi  Keith,
> > >>>
> > >>> I think that the IETF is trying to design protocols that will work
> > over
> > >>> the
> > >>> Internet and also to enable interoperability between independent
> > >>> implementations.
> > >>>
> > >>> In the BFCP case the shipping implementations support TCP as the
> > >>> transport
> > >>> protocol but they encountered issues when running over the Internet
> > due
> > >>> to
> > >>> devices like SBCs and due to lack of support for TCP media relay or
> > >>> ICE-TCP
> > >>> [I-D.ietf-mmusic-ice-tcp].
> > >>> When implementations looked at how to address the issue, the
> > >>> interoperability went away since there is no fall back solution for
> > this
> > >>> real life case. Some did a fall back to HTTP and some did to UDP
> > but not
> > >>> in
> > >>> an interoperable way.
> > >>>
> > >>> In order to achieve interoperability, this draft is trying to
> > extend the
> > >>> current BFCP. It is not suggesting to replace TCP but to keep TCP
> > as the
> > >>> mandatory transport and use UDP as fallback if unable to establish
> > TCP
> > >>> connection.
> > >>>
> > >>> As for security, if the topic will be adopted the solution will be
> > >>> updated
> > >>> to use DTLS as the transport for BFCP.
> > >>>
> > >>> I hope that people will read the draft and look at the objectives
> > and the
> > >>> proposed solution.
> > >>>
> > >>>
> > >>> BTW: This is a problem for client to client media connections over
> > TCP
> > >>> and
> > >>> my understanding is that RTSP offers to use both TCP and UDP since
> > both
> > >>> are
> > >>> specified. Since BFCP is not a payload but is running in parallel
> > to the
> > >>> RTP
> > >>> payload (for the point to point calls or MCU based multipoint) it
> > needs
> > >>> similar transport options.
> > >>>
> > >>> Thanks
> > >>> Roni Even
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
> > >>>> Sent: Thursday, June 10, 2010 1:54 AM
> > >>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> > >>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
> > xcon@ietf.org
> > >>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > >>>>
> > >>>> What you are essentially saying is that all protocols in the
> > future
> > >>>> that need reliable transport, as BFCP does, have to design in
> > their own
> > >>>> reliable transport element so they can use UDP. This is not a BFCP
> > >>>> specific issue.
> > >>>>
> > >>>> I find that an unacceptable direction for IETF to be heading in.
> > >>>>
> > >>>> I would also note that you are also asking for adoption of a
> > document
> > >>>> that cannot in its current form meet the security requirements of
> > the
> > >>>> original RFC.
> > >>>>
> > >>>> regards
> > >>>>
> > >>>> Keith
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > >>>>> Sent: Wednesday, June 09, 2010 1:40 PM
> > >>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
> > >>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> > >>>>> 'Tom Kristensen'; xcon@ietf.org
> > >>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> > 02
> > >>>>>
> > >>>>> Richard,
> > >>>>> The BFCP I used as a presentation token for video
> > >>>>> conferencing. What the implementers found out that TCP does
> > >>>>> not work in real networks due to Session border controllers
> > >>>>> not supporting TCP as used in BFCP.
> > >>>>> This is why in products they try to establish TCP connection
> > >>>>> and if fails tries UDP.
> > >>>>> The video conferencing vendors participating in the IMTC sip
> > >>>>> parity activity group defined an interoperability profile
> > >>>>> that references this option Roni Even
> > >>>>>
> > >>>>>> -----Original Message-----
> > >>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > >>>>>
> > >>>>> On Behalf
> > >>>>>>
> > >>>>>> Of Richard L. Barnes
> > >>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
> > >>>>>> To: Tom Kristensen
> > >>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> > >>>>>> Kristensen; xcon@ietf.org
> > >>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> > 02
> > >>>>>>
> > >>>>>> Tom and others who are interested in this draft:
> > >>>>>>
> > >>>>>> For those who are relatively new here: Could you summarize why
> > you
> > >>>>>> think this draft is needed?  What requirement does it meet
> > >>>>>
> > >>>>> that BFCP
> > >>>>>>
> > >>>>>> doesn't right now?
> > >>>>>>
> > >>>>>> Thanks,
> > >>>>>> --Richard
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> > >>>>>>
> > >>>>>>> The UDP/BFCP draft has been presented and discussed in
> > >>>>>
> > >>>>> two or three
> > >>>>>>>
> > >>>>>>> IETF XCON sessions. No objection to the work being
> > >>>>>
> > >>>>> carried on, just
> > >>>>>>>
> > >>>>>>> that adoption as WG item was postponed until the draft was more
> > >>>>>>> complete. (This has been delayed of various reasons, but
> > >>>>>
> > >>>>> the authors
> > >>>>>>>
> > >>>>>>> believe the -02 version in question here should be ready for
> > >>>>>>> adoption).
> > >>>>>>>
> > >>>>>>> The "current status of consensus" might be valid for some, but
> > >>>>>>> participants in the XCON sessions and the minutes of meeting
> > show
> > >>>>>>> progress away from that initial consensus.
> > >>>>>>>
> > >>>>>>> I believe Ott's concerns are either dealt with or at
> > >>>>>
> > >>>>> least mentioned
> > >>>>>>>
> > >>>>>>> in the draft. Arrest me if I'm wrong.
> > >>>>>>>
> > >>>>>>> -- Tom
> > >>>>>>>
> > >>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
> > >>>>>>> <keith.drage@alcatel-lucent.com> wrote:
> > >>>>>>>>
> > >>>>>>>> We made an explicit decision in the original draft that
> > >>>>>
> > >>>>> UDP was not
> > >>>>>>>>
> > >>>>>>>> required, not that we would do it later. That as far as I am
> > >>>>>>>> concerned represents the current status of consensus.
> > >>>>>>>>
> > >>>>>>>> This was done on the basis that we had all seen how UDP
> > >>>>>
> > >>>>> support had
> > >>>>>>>>
> > >>>>>>>> complicated SIP, and we did not want to repeat that issue.
> > >>>>>>>>
> > >>>>>>>> So this is not continuing the work. The status is an
> > >>>>>
> > >>>>> author draft
> > >>>>>>>>
> > >>>>>>>> which goes against a WG consensus position.
> > >>>>>>>>
> > >>>>>>>> I believe Georg Ott also expressed some concerns which I did
> > not
> > >>>>>>>> see answered on list at all.
> > >>>>>>>>
> > >>>>>>>> regards
> > >>>>>>>>
> > >>>>>>>> Keith
> > >>>>>>>>
> > >>>>>>>>> -----Original Message-----
> > >>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
> > >>>>>>>>> Behalf Of Roni Even
> > >>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
> > >>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
> > >>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
> > >>>>>>>>> Subject: Re: [XCON] WG Adoption?
> > >>>>>
> > >>>>> draft-sandbakken-xcon-bfcp-udp-02
> > >>>>>>>>>
> > >>>>>>>>> Hi Alan,
> > >>>>>>>>> I support this work and think it is urgent to finish it.
> > >>>>>>>>> I think that updating BFCP with UDP support is very
> > >>>>>
> > >>>>> important. I
> > >>>>>>>>>
> > >>>>>>>>> would like to mention that BFCP is being used in video
> > >>>>>>>>> conferencing application and since the implementers
> > encountered
> > >>>>>>>>> problems with TCP they use a fall back to UDP.
> > >>>>>>>>> We discussed this work in previous IETF meeting and
> > >>>>>
> > >>>>> Gonzalo as far
> > >>>>>>>>>
> > >>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
> > >>>>>>>>>
> > >>>>>>>>> Thanks
> > >>>>>>>>> Roni Even
> > >>>>>>>>>
> > >>>>>>>>>> -----Original Message-----
> > >>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> > >>>>>>>>>
> > >>>>>>>>> On Behalf
> > >>>>>>>>>>
> > >>>>>>>>>> Of Alan Johnston
> > >>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
> > >>>>>>>>>> To: Tom Kristensen
> > >>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
> > >>>>>>>>>> Subject: Re: [XCON] WG Adoption?
> > >>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
> > >>>>>>>>>>
> > >>>>>>>>>> Tom,
> > >>>>>>>>>>
> > >>>>>>>>>> Apologies for the delay in replying.  As you know, the
> > >>>>>>>>>
> > >>>>>>>>> working group
> > >>>>>>>>>>
> > >>>>>>>>>> is in the process of completing its final milestones.
> > >>>>>>>>>> Publication requests will be issued in the next few
> > >>>>>
> > >>>>> days for the
> > >>>>>>>>>>
> > >>>>>>>>>> data
> > >>>>>>>>>
> > >>>>>>>>> model, CCMP,
> > >>>>>>>>>>
> > >>>>>>>>>> and the Examples drafts.
> > >>>>>>>>>>
> > >>>>>>>>>> Taking on any new milestones for the working group
> > >>>>>
> > >>>>> would require:
> > >>>>>>>>>>
> > >>>>>>>>>> 1. Strong support and interest from working group
> > >>>>>
> > >>>>> participants 2.
> > >>>>>>>>>>
> > >>>>>>>>>> Approval of our ADs.
> > >>>>>>>>>>
> > >>>>>>>>>> I haven't seen evidence of either of these at this stage.
> > >>>>>>>>>>
> > >>>>>>>>>> A possible option is to take this work to DISPATCH, get an
> > >>>>>>>>>
> > >>>>>>>>> indication
> > >>>>>>>>>>
> > >>>>>>>>>> of interests, and get feedback on the best way to move
> > >>>>>
> > >>>>> this work
> > >>>>>>>>>>
> > >>>>>>>>>> forward.
> > >>>>>>>>>>
> > >>>>>>>>>> - Alan -
> > >>>>>>>>>> co-chair XCON
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> > >>>>>>>>>
> > >>>>>>>>> early in
> > >>>>>>>>>>>
> > >>>>>>>>>>> March. No comments received since.
> > >>>>>>>>>>>
> > >>>>>>>>>>> We'd like guidance on the next steps. First we ask for
> > >>>>>>>>>
> > >>>>>>>>> adoption as
> > >>>>>>>>>>>
> > >>>>>>>>>>> WG item. Next step would include the merging process with
> > bis
> > >>>>>>>>>>> versions
> > >>>>>>>>>>
> > >>>>>>>>>> of
> > >>>>>>>>>>>
> > >>>>>>>>>>> RFC 4582 and RFC 4583.
> > >>>>>>>>>>>
> > >>>>>>>>>>> We'd like to point out that interested parties for this
> > >>>>>>>>>
> > >>>>>>>>> work indeed
> > >>>>>>>>>>>
> > >>>>>>>>>>> exist.
> > >>>>>>>>>>>
> > >>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
> > >>>>>>>>>
> > >>>>>>>>> April and May.
> > >>>>>>>>>>
> > >>>>>>>>>> See
> > >>>>>>>>>>>
> > >>>>>>>>>>> below. No response given. Therefore, this request on
> > >>>>>
> > >>>>> the list.)
> > >>>>>>>>>>>
> > >>>>>>>>>>> -- Tom
> > >>>>>>>>>>>
> > >>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Chairs,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Any thoughts or decision on this matter?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Cheers,
> > >>>>>>>>>>>> -- Tom
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> XCON chairs,
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> > >>>>>
> > >>>>> early in March
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> -
> > >>>>>>>>>>
> > >>>>>>>>>> well in
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> advance of IETF-77.
> > >>>>>>>>>>>>>  http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
> > >>>>
> > >>>> udp
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
> > >>>>>>>>>
> > >>>>>>>>> directly to the
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
> > >>>>>>>>>
> > >>>>>>>>> as an XCON
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> WG item.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> -- Tom
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>> _______________________________________________
> > >>>>>>>>>> XCON mailing list
> > >>>>>>>>>> XCON@ietf.org
> > >>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>>>
> > >>>>>>>>> _______________________________________________
> > >>>>>>>>> XCON mailing list
> > >>>>>>>>> XCON@ietf.org
> > >>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>>>
> > >>>>>>>> _______________________________________________
> > >>>>>>>> XCON mailing list
> > >>>>>>>> XCON@ietf.org
> > >>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> # TANDBERG R&D
> > >>>>>>> ## http://www.tandberg.com
> > >>>>>>> ### http://folk.uio.no/tomkri/
> > >>>>>>> _______________________________________________
> > >>>>>>> XCON mailing list
> > >>>>>>> XCON@ietf.org
> > >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>> XCON mailing list
> > >>>>>> XCON@ietf.org
> > >>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>
> > >>>>> =
> > >>>
> > >>> _______________________________________________
> > >>> XCON mailing list
> > >>> XCON@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>
> > >>
> > >>
> > >> --
> > >> Lorenzo Miniero
> > >> Meetecho s.r.l.
> > >> http://www.meetecho.com/
> > >
> > > _______________________________________________
> > > XCON mailing list
> > > XCON@ietf.org
> > > https://www.ietf.org/mailman/listinfo/xcon
> > >
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>

--0016e6d9746ee59eba0489c8518b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

BFCP is an important component in our application (videoconferencing).=A0 T=
he inability to use BFCP when TCP cannot be used is a huge problem for us t=
oday.<br><br>So I would like to see this document progressed.=A0 <br><br>If=
 for some reason XCON doesn&#39;t finish it before the WG is closed, I thin=
k Mary&#39;s suggestion of progressing it under individual AD sponsorship i=
s good.<br>
<br>Stephen Botzko<br><br><br><br><div class=3D"gmail_quote">2010/6/24 Roni=
 Even <span dir=3D"ltr">&lt;<a href=3D"mailto:ron.even.tlv@gmail.com">ron.e=
ven.tlv@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=
=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); p=
adding-left: 1ex;">
Mary,<br>
I think that in the discussion in the past, Gonzalo suggested to do a bis<b=
r>
draft to RFC 4582. I think he mentioned other issues he wanted to update.<b=
r>
Roni Even<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:xcon-bounces@ietf.org">xcon-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:xcon-bounces@ietf.org">xcon-bounces@ietf.org</=
a>] On Behalf Of<br>
&gt; Mary Barnes<br>
&gt; Sent: Wednesday, June 23, 2010 7:26 PM<br>
&gt; To: Richard L. Barnes<br>
&gt; Cc: Tom Kristensen; DRAGE, Keith (Keith); <a href=3D"mailto:xcon@ietf.=
org">xcon@ietf.org</a>; Mark Thompson;<br>
&gt; Alan Johnston<br>
&gt; Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02<br>
&gt;<br>
&gt; I have reviewed the draft in question and while I agree that this<br>
&gt; could be viewed as a workaround for some more general problems that<br=
>
&gt; need to be solved, there is a current industry need for the solution<b=
r>
&gt; in this draft. =A0 If the general problems described go to DISPATCH<br=
>
&gt; (which is the appropriate thing to do rather than bringing this<br>
&gt; specific document), the timeframe for getting agreement on the problem=
<br>
&gt; to be solved and for the solutions to be agreed would be far longer<br=
>
&gt; IMHO than if this document were progressed. If XCON would prefer to<br=
>
&gt; close the WG without progressing this document (in this form or as a<b=
r>
&gt; -bis to RFC =A04582), my suggestion would be to do as was done for the=
<br>
&gt; remaining SIP and SIPPING documents and progress this item as an<br>
&gt; individual AD sponsored.<br>
&gt;<br>
&gt; Mary.<br>
&gt;<br>
&gt; On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes &lt;<a href=3D"mail=
to:rbarnes@bbn.com">rbarnes@bbn.com</a>&gt;<br>
&gt; wrote:<br>
&gt; &gt; &lt;hat type=3D&quot;individual&quot;/&gt;<br>
&gt; &gt;<br>
&gt; &gt; I tend to agree with Lorenzo that DISPATCH would be a better plac=
e to<br>
&gt; have<br>
&gt; &gt; these discussions, especially given that, as far as I can tell fr=
om<br>
&gt; this<br>
&gt; &gt; thread, the problem seems to be a general one of NAT traversal fo=
r<br>
&gt; TCP.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; Hi all,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; with respect to this topic, I think there are many issues<br>
&gt; implementers<br>
&gt; &gt;&gt; have to face when bringing IETF solutions to the real world. =
We<br>
&gt; found<br>
&gt; &gt;&gt; ourselves many times in a situation in which some kind of wor=
k-<br>
&gt; around<br>
&gt; &gt;&gt; had to be devised in order to let things work properly. Just =
to cite<br>
&gt; a<br>
&gt; &gt;&gt; couple of examples, with BFCP we had to find a way to let it =
work in<br>
&gt; a<br>
&gt; &gt;&gt; distributed conferencing scenario (which is far from easy, gi=
ven the<br>
&gt; &gt;&gt; intrinsic centralized model behind such protocol). In such ca=
se, we<br>
&gt; &gt;&gt; decided to encapsulate BFCP messages in the body of XMPP<br>
&gt; &gt;&gt; server-to-server packets (see the XCON-DCON Synchronization P=
rotocol<br>
&gt; in<br>
&gt; &gt;&gt; draft-romano-dcon-xdsp-reqs-06 for the details) and then even=
<br>
&gt; devised<br>
&gt; &gt;&gt; a BFCP-XMPP gateway for such a purpose. With respect to the N=
AT<br>
&gt; &gt;&gt; traversal issue, we also implemented an HTTP encapsulation. M=
oving<br>
&gt; &gt;&gt; further we even conceived a DTMF-based frontend to BFCP ;) an=
d also<br>
&gt; &gt;&gt; almost thought about a BFCP-over-RTP approach.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; That said, I nevertheless agree with Keith on the discussion.=
 Those<br>
&gt; &gt;&gt; problems may be common to other TCP-based protocols as well, =
and as<br>
&gt; such<br>
&gt; &gt;&gt; a generic solution (generic TCP over UDP, for instance, or an=
ything<br>
&gt; &gt;&gt; else) may be a much better approach than doing a protocol spe=
cific<br>
&gt; &gt;&gt; patch. Besides, whatever the solution, it should also take ca=
re of<br>
&gt; how<br>
&gt; &gt;&gt; the negotiation of such channels would be affected (as is the=
<br>
&gt; &gt;&gt; case of RFC4583 for BFCP, which the proposed draft actually d=
oes).<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; As Keith already suggested, DISPATCH may be a much better pla=
ce to<br>
&gt; &gt;&gt; discuss this issue: DISPATCH is where we&#39;ll also propose =
the above<br>
&gt; &gt;&gt; mentioned DCON work.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Lorenzo<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On Thu, 10 Jun 2010 08:22:55 +0300<br>
&gt; &gt;&gt; &quot;Roni Even&quot; &lt;<a href=3D"mailto:ron.even.tlv@gmai=
l.com">ron.even.tlv@gmail.com</a>&gt; wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; Hi =A0Keith,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; I think that the IETF is trying to design protocols that =
will work<br>
&gt; over<br>
&gt; &gt;&gt;&gt; the<br>
&gt; &gt;&gt;&gt; Internet and also to enable interoperability between inde=
pendent<br>
&gt; &gt;&gt;&gt; implementations.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; In the BFCP case the shipping implementations support TCP=
 as the<br>
&gt; &gt;&gt;&gt; transport<br>
&gt; &gt;&gt;&gt; protocol but they encountered issues when running over th=
e Internet<br>
&gt; due<br>
&gt; &gt;&gt;&gt; to<br>
&gt; &gt;&gt;&gt; devices like SBCs and due to lack of support for TCP medi=
a relay or<br>
&gt; &gt;&gt;&gt; ICE-TCP<br>
&gt; &gt;&gt;&gt; [I-D.ietf-mmusic-ice-tcp].<br>
&gt; &gt;&gt;&gt; When implementations looked at how to address the issue, =
the<br>
&gt; &gt;&gt;&gt; interoperability went away since there is no fall back so=
lution for<br>
&gt; this<br>
&gt; &gt;&gt;&gt; real life case. Some did a fall back to HTTP and some did=
 to UDP<br>
&gt; but not<br>
&gt; &gt;&gt;&gt; in<br>
&gt; &gt;&gt;&gt; an interoperable way.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; In order to achieve interoperability, this draft is tryin=
g to<br>
&gt; extend the<br>
&gt; &gt;&gt;&gt; current BFCP. It is not suggesting to replace TCP but to =
keep TCP<br>
&gt; as the<br>
&gt; &gt;&gt;&gt; mandatory transport and use UDP as fallback if unable to =
establish<br>
&gt; TCP<br>
&gt; &gt;&gt;&gt; connection.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; As for security, if the topic will be adopted the solutio=
n will be<br>
&gt; &gt;&gt;&gt; updated<br>
&gt; &gt;&gt;&gt; to use DTLS as the transport for BFCP.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; I hope that people will read the draft and look at the ob=
jectives<br>
&gt; and the<br>
&gt; &gt;&gt;&gt; proposed solution.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; BTW: This is a problem for client to client media connect=
ions over<br>
&gt; TCP<br>
&gt; &gt;&gt;&gt; and<br>
&gt; &gt;&gt;&gt; my understanding is that RTSP offers to use both TCP and =
UDP since<br>
&gt; both<br>
&gt; &gt;&gt;&gt; are<br>
&gt; &gt;&gt;&gt; specified. Since BFCP is not a payload but is running in =
parallel<br>
&gt; to the<br>
&gt; &gt;&gt;&gt; RTP<br>
&gt; &gt;&gt;&gt; payload (for the point to point calls or MCU based multip=
oint) it<br>
&gt; needs<br>
&gt; &gt;&gt;&gt; similar transport options.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Thanks<br>
&gt; &gt;&gt;&gt; Roni Even<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt; From: DRAGE, Keith (Keith) [mailto:<a href=3D"mailto:=
keith.drage@alcatel-lucent.com">keith.drage@alcatel-lucent.com</a>]<br>
&gt; &gt;&gt;&gt;&gt; Sent: Thursday, June 10, 2010 1:54 AM<br>
&gt; &gt;&gt;&gt;&gt; To: Roni Even; &#39;Richard L. Barnes&#39;; &#39;Tom =
Kristensen&#39;<br>
&gt; &gt;&gt;&gt;&gt; Cc: &#39;Mark Thompson&#39;; &#39;Alan Johnston&#39;;=
 &#39;Tom Kristensen&#39;;<br>
&gt; <a href=3D"mailto:xcon@ietf.org">xcon@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt; Subject: RE: [XCON] WG Adoption? draft-sandbakken-xco=
n-bfcp-udp-02<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; What you are essentially saying is that all protocols=
 in the<br>
&gt; future<br>
&gt; &gt;&gt;&gt;&gt; that need reliable transport, as BFCP does, have to d=
esign in<br>
&gt; their own<br>
&gt; &gt;&gt;&gt;&gt; reliable transport element so they can use UDP. This =
is not a BFCP<br>
&gt; &gt;&gt;&gt;&gt; specific issue.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; I find that an unacceptable direction for IETF to be =
heading in.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; I would also note that you are also asking for adopti=
on of a<br>
&gt; document<br>
&gt; &gt;&gt;&gt;&gt; that cannot in its current form meet the security req=
uirements of<br>
&gt; the<br>
&gt; &gt;&gt;&gt;&gt; original RFC.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; regards<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Keith<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt; From: Roni Even [mailto:<a href=3D"mailto:ron.eve=
n.tlv@gmail.com">ron.even.tlv@gmail.com</a>]<br>
&gt; &gt;&gt;&gt;&gt;&gt; Sent: Wednesday, June 09, 2010 1:40 PM<br>
&gt; &gt;&gt;&gt;&gt;&gt; To: &#39;Richard L. Barnes&#39;; &#39;Tom Kristen=
sen&#39;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Cc: &#39;Mark Thompson&#39;; DRAGE, Keith (Keith)=
; &#39;Alan Johnston&#39;;<br>
&gt; &gt;&gt;&gt;&gt;&gt; &#39;Tom Kristensen&#39;; <a href=3D"mailto:xcon@=
ietf.org">xcon@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Subject: RE: [XCON] WG Adoption? draft-sandbakken=
-xcon-bfcp-udp-<br>
&gt; 02<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Richard,<br>
&gt; &gt;&gt;&gt;&gt;&gt; The BFCP I used as a presentation token for video=
<br>
&gt; &gt;&gt;&gt;&gt;&gt; conferencing. What the implementers found out tha=
t TCP does<br>
&gt; &gt;&gt;&gt;&gt;&gt; not work in real networks due to Session border c=
ontrollers<br>
&gt; &gt;&gt;&gt;&gt;&gt; not supporting TCP as used in BFCP.<br>
&gt; &gt;&gt;&gt;&gt;&gt; This is why in products they try to establish TCP=
 connection<br>
&gt; &gt;&gt;&gt;&gt;&gt; and if fails tries UDP.<br>
&gt; &gt;&gt;&gt;&gt;&gt; The video conferencing vendors participating in t=
he IMTC sip<br>
&gt; &gt;&gt;&gt;&gt;&gt; parity activity group defined an interoperability=
 profile<br>
&gt; &gt;&gt;&gt;&gt;&gt; that references this option Roni Even<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; From: <a href=3D"mailto:xcon-bounces@ietf.org=
">xcon-bounces@ietf.org</a> [mailto:<a href=3D"mailto:xcon-bounces@ietf.org=
">xcon-bounces@ietf.org</a>]<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; On Behalf<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Of Richard L. Barnes<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Sent: Wednesday, June 09, 2010 3:34 PM<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; To: Tom Kristensen<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Cc: Mark Thompson; DRAGE, Keith (Keith); Alan=
 Johnston; Tom<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Kristensen; <a href=3D"mailto:xcon@ietf.org">=
xcon@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [XCON] WG Adoption? draft-sandba=
kken-xcon-bfcp-udp-<br>
&gt; 02<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Tom and others who are interested in this dra=
ft:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; For those who are relatively new here: Could =
you summarize why<br>
&gt; you<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; think this draft is needed? =A0What requireme=
nt does it meet<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; that BFCP<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; doesn&#39;t right now?<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; --Richard<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; On Jun 9, 2010, at 7:37 AM, Tom Kristensen wr=
ote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The UDP/BFCP draft has been presented and=
 discussed in<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; two or three<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; IETF XCON sessions. No objection to the w=
ork being<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; carried on, just<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; that adoption as WG item was postponed un=
til the draft was more<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; complete. (This has been delayed of vario=
us reasons, but<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; the authors<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; believe the -02 version in question here =
should be ready for<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; adoption).<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The &quot;current status of consensus&quo=
t; might be valid for some, but<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; participants in the XCON sessions and the=
 minutes of meeting<br>
&gt; show<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; progress away from that initial consensus=
.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; I believe Ott&#39;s concerns are either d=
ealt with or at<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; least mentioned<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; in the draft. Arrest me if I&#39;m wrong.=
<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; -- Tom<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; On 9 June 2010 13:20, DRAGE, Keith (Keith=
)<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:keith.drage@alcatel=
-lucent.com">keith.drage@alcatel-lucent.com</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We made an explicit decision in the o=
riginal draft that<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; UDP was not<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; required, not that we would do it lat=
er. That as far as I am<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; concerned represents the current stat=
us of consensus.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; This was done on the basis that we ha=
d all seen how UDP<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; support had<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; complicated SIP, and we did not want =
to repeat that issue.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; So this is not continuing the work. T=
he status is an<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; author draft<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; which goes against a WG consensus pos=
ition.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I believe Georg Ott also expressed so=
me concerns which I did<br>
&gt; not<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; see answered on list at all.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; regards<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Keith<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: <a href=3D"mailto:xcon-boun=
ces@ietf.org">xcon-bounces@ietf.org</a> [mailto:<a href=3D"mailto:xcon-boun=
ces@ietf.org">xcon-bounces@ietf.org</a>] On<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Behalf Of Roni Even<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, June 08, 2010 7:35=
 PM<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: &#39;Alan Johnston&#39;; &#39=
;Tom Kristensen&#39;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: &#39;Mark Thompson&#39;; <a h=
ref=3D"mailto:xcon@ietf.org">xcon@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [XCON] WG Adoption?<=
br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; draft-sandbakken-xcon-bfcp-udp-02<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Alan,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I support this work and think it =
is urgent to finish it.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I think that updating BFCP with U=
DP support is very<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; important. I<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; would like to mention that BFCP i=
s being used in video<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; conferencing application and sinc=
e the implementers<br>
&gt; encountered<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; problems with TCP they use a fall=
 back to UDP.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We discussed this work in previou=
s IETF meeting and<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Gonzalo as far<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; as I remember suggested to add it=
 to a BFCP bis draft.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Roni Even<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br=
>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: <a href=3D"mailto:xcon-=
bounces@ietf.org">xcon-bounces@ietf.org</a> [mailto:<a href=3D"mailto:xcon-=
bounces@ietf.org">xcon-bounces@ietf.org</a>]<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Behalf<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Of Alan Johnston<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, June 08, 2010 =
7:44 PM<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Tom Kristensen<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: Mark Thompson; <a href=3D=
"mailto:xcon@ietf.org">xcon@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [XCON] WG Adopti=
on?<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-sandbakken-xcon-bfcp-ud=
p-02<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tom,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Apologies for the delay in re=
plying. =A0As you know, the<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; working group<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; is in the process of completi=
ng its final milestones.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Publication requests will be =
issued in the next few<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; days for the<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; data<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; model, CCMP,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; and the Examples drafts.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Taking on any new milestones =
for the working group<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; would require:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. Strong support and interes=
t from working group<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; participants 2.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Approval of our ADs.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I haven&#39;t seen evidence o=
f either of these at this stage.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; A possible option is to take =
this work to DISPATCH, get an<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; indication<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; of interests, and get feedbac=
k on the best way to move<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; this work<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; forward.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; - Alan -<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; co-chair XCON<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On 6/7/10 8:22 AM, Tom Kriste=
nsen wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; The draft draft-sandbakke=
n-xcon-bfcp-udp-02 was submitted<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; early in<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; March. No comments receiv=
ed since.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We&#39;d like guidance on=
 the next steps. First we ask for<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; adoption as<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; WG item. Next step would =
include the merging process with<br>
&gt; bis<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; versions<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; of<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; RFC 4582 and RFC 4583.<br=
>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We&#39;d like to point ou=
t that interested parties for this<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; work indeed<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exist.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; (For the record: Question=
s was sent to XCON chairs in<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; April and May.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; See<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; below. No response given.=
 Therefore, this request on<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; the list.)<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -- Tom<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Wed, 2010-05-12 at 10:=
43 +0200, Tom Kristensen wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Chairs,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Any thoughts or decis=
ion on this matter?<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cheers,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -- Tom<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Tue, 2010-04-20 at=
 11:58 +0200, Tom Kristensen wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON chairs,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We submitted draf=
t-sandbakken-xcon-bfcp-udp-02<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; early in March<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; well in<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; advance of IETF-7=
7.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =A0<a href=3D"htt=
p://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-" target=3D"_blank">http=
://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-</a><br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; udp<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; No comments recei=
ved. Neither on XCON WG list, nor<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; directly to the<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; authors. Therefor=
e, we ask for adoption of this draft<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; as an XCON<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; WG item.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -- Tom<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _____________________________=
__________________<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:XCON@ietf.o=
rg">XCON@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.o=
rg/mailman/listinfo/xcon" target=3D"_blank">https://www.ietf.org/mailman/li=
stinfo/xcon</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _________________________________=
______________<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:XCON@ietf.org">=
XCON@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/m=
ailman/listinfo/xcon" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/xcon</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _____________________________________=
__________<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:XCON@ietf.org">XCON=
@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailm=
an/listinfo/xcon" target=3D"_blank">https://www.ietf.org/mailman/listinfo/x=
con</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; --<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; # TANDBERG R&amp;D<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; ## <a href=3D"http://www.tandberg.com" ta=
rget=3D"_blank">http://www.tandberg.com</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; ### <a href=3D"http://folk.uio.no/tomkri/=
" target=3D"_blank">http://folk.uio.no/tomkri/</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; _________________________________________=
______<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:XCON@ietf.org">XCON@iet=
f.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/l=
istinfo/xcon" target=3D"_blank">https://www.ietf.org/mailman/listinfo/xcon<=
/a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; _____________________________________________=
__<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:XCON@ietf.org">XCON@ietf.or=
g</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listi=
nfo/xcon" target=3D"_blank">https://www.ietf.org/mailman/listinfo/xcon</a><=
br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =3D<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt; XCON mailing list<br>
&gt; &gt;&gt;&gt; <a href=3D"mailto:XCON@ietf.org">XCON@ietf.org</a><br>
&gt; &gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/xcon" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/xcon</a><br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; --<br>
&gt; &gt;&gt; Lorenzo Miniero<br>
&gt; &gt;&gt; Meetecho s.r.l.<br>
&gt; &gt;&gt; <a href=3D"http://www.meetecho.com/" target=3D"_blank">http:/=
/www.meetecho.com/</a><br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; XCON mailing list<br>
&gt; &gt; <a href=3D"mailto:XCON@ietf.org">XCON@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/xcon" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/xcon</a><br>
&gt; &gt;<br>
&gt; _______________________________________________<br>
&gt; XCON mailing list<br>
&gt; <a href=3D"mailto:XCON@ietf.org">XCON@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/xcon" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/xcon</a><br>
<br>
_______________________________________________<br>
XCON mailing list<br>
<a href=3D"mailto:XCON@ietf.org">XCON@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xcon" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/xcon</a><br>
</blockquote></div><br>

--0016e6d9746ee59eba0489c8518b--

From eckelcu@cisco.com  Thu Jun 24 08:53:21 2010
Return-Path: <eckelcu@cisco.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83D3B28C0FE for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 08:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.37
X-Spam-Level: 
X-Spam-Status: No, score=-9.37 tagged_above=-999 required=5 tests=[AWL=0.630,  BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8c4Mrz17FZWd for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 08:53:15 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 77DF33A68AE for <xcon@ietf.org>; Thu, 24 Jun 2010 08:53:14 -0700 (PDT)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMMbI0yrRN+J/2dsb2JhbACfN3GnRJpfglIXgjgEg16NSg
X-IronPort-AV: E=Sophos;i="4.53,475,1272844800"; d="scan'208";a="228016332"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-3.cisco.com with ESMTP; 24 Jun 2010 15:53:22 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o5OFrMuw026378; Thu, 24 Jun 2010 15:53:22 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 24 Jun 2010 08:53:22 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
x-cr-hashedpuzzle: CVCK L6Hy a+It bz4f cPeC fRAU k8wN n4az r8YV vl6N xh46 yBmf yjvv 2eBf 7br5 8DUx; 7; MgBtAGsAcgBpAHMAdABlAG4AcwBlAG4AQABnAG0AYQBpAGwALgBjAG8AbQA7AGEAbABhAG4ALgBiAC4AagBvAGgAbgBzAHQAbwBuAEAAZwBtAGEAaQBsAC4AYwBvAG0AOwBrAGUAaQB0AGgALgBkAHIAYQBnAGUAQABhAGwAYwBhAHQAZQBsAC0AbAB1AGMAZQBuAHQALgBjAG8AbQA7AG0AYQByAGsALgB0AGgAbwBtAHAAcwBvAG4AQAB0AGEAbgBkAGIAZQByAGcALgBjAG8AbQA7AHIAbwBuAC4AZQB2AGUAbgAuAHQAbAB2AEAAZwBtAGEAaQBsAC4AYwBvAG0AOwB0AG8AbQAuAGsAcgBpAHMAdABlAG4AcwBlAG4AQAB0AGEAbgBkAGIAZQByAGcALgBjAG8AbQA7AHgAYwBvAG4AQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {5D97BAB7-ECEE-4462-8A32-DFF20FBD9D53}; ZQBjAGsAZQBsAGMAdQBAAGMAaQBzAGMAbwAuAGMAbwBtAA==; Thu, 24 Jun 2010 15:53:10 GMT; UgBFADoAIABbAFgAQwBPAE4AXQAgAFcARwAgAEEAZABvAHAAdABpAG8AbgA/ACAAZAByAGEAZgB0AC0AcwBhAG4AZABiAGEAawBrAGUAbgAtAHgAYwBvAG4ALQBiAGYAYwBwAC0AdQBkAHAALQAwADIA
x-cr-puzzleid: {5D97BAB7-ECEE-4462-8A32-DFF20FBD9D53}
Content-class: urn:content-classes:message
Date: Thu, 24 Jun 2010 08:53:10 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C0151F424@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <AANLkTimUQ6pGeRyRbGd68dyu9Y2EitVhWl8ANU-DuauK@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
Thread-Index: AcsTrLLQZc5QxF6iTVuPed6tp7relgABvxtw
References: <1271757479.26184.8.camel@localhost><1273653780.2694.11.camel@localhost><1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com><4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com><EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com><59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com><4c0f8c0f.9becd80a.55da.0fe2@mx.google.com><EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><4c107733.df0ce30a.21ca.15cc@mx.google.com><20100610130009.1f1fbb03.lorenzo@meetecho.com><0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com><AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com><4c236e60.9d90d80a.1d25.6b10@mx.google.com> <AANLkTimUQ6pGeRyRbGd68dyu9Y2EitVhWl8ANU-DuauK@mail.gmail.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Tom Kristensen" <2mkristensen@gmail.com>, "Roni Even" <ron.even.tlv@gmail.com>
X-OriginalArrivalTime: 24 Jun 2010 15:53:22.0658 (UTC) FILETIME=[5FBF6C20:01CB13B5]
Cc: Tom Kristensen <tom.kristensen@tandberg.com>, Mark Thompson <mark.thompson@tandberg.com>, Alan Johnston <alan.b.johnston@gmail.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 15:53:21 -0000

I am very interested in seeing draft-sandbakken-xcon-bfcp-udp move =
forward as I see it as a very useful and straightforward extension of =
RFC 4582 that solves a real world problem in an way that makes use of =
many existing mechanisms already standardized within the IETF. With the =
IMTC, we are already recommending support for =
draft-sandbakken-xcon-bfcp-udp in addition to RFC 4582 as there are =
cases in which BFCP via TCP is not possible and BFCP via UDP offers a =
very workable solution. The draft already has wide support with the IMTC =
member companies, most of which are quite active within the IETF as =
well, so I feel there is sufficient support to move this draft forward.
As for the best path to achieve this, XCON seems the most logical choice =
to me, but I only recently started following the group's work and defer =
to others on the best way forward in terms or timing and procedure. My =
main concern is that the path taken is one that leads to standardize the =
addition of BFCP via UDP sooner rather than later.

Thanks,
Charles=20

> -----Original Message-----
> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf =
Of Tom Kristensen
> Sent: Thursday, June 24, 2010 7:50 AM
> To: Roni Even
> Cc: Mark Thompson; Alan Johnston; DRAGE,Keith (Keith); xcon@ietf.org; =
Tom Kristensen
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>=20
> That's correct, Roni.
>=20
> The thread starting with a list of issues in addition to the UDP/BFCP
> extension is available in the list archives here:
> http://www.ietf.org/mail-archive/web/xcon/current/msg02231.html
>=20
> -- Tom
>=20
>=20
> 2010/6/24 Roni Even <ron.even.tlv@gmail.com>:
> > Mary,
> > I think that in the discussion in the past, Gonzalo suggested to do =
a bis
> > draft to RFC 4582. I think he mentioned other issues he wanted to =
update.
> > Roni Even
> >
> >> -----Original Message-----
> >> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On =
Behalf Of
> >> Mary Barnes
> >> Sent: Wednesday, June 23, 2010 7:26 PM
> >> To: Richard L. Barnes
> >> Cc: Tom Kristensen; DRAGE, Keith (Keith); xcon@ietf.org; Mark =
Thompson;
> >> Alan Johnston
> >> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >>
> >> I have reviewed the draft in question and while I agree that this
> >> could be viewed as a workaround for some more general problems that
> >> need to be solved, there is a current industry need for the =
solution
> >> in this draft. =A0 If the general problems described go to DISPATCH
> >> (which is the appropriate thing to do rather than bringing this
> >> specific document), the timeframe for getting agreement on the =
problem
> >> to be solved and for the solutions to be agreed would be far longer
> >> IMHO than if this document were progressed. If XCON would prefer to
> >> close the WG without progressing this document (in this form or as =
a
> >> -bis to RFC =A04582), my suggestion would be to do as was done for =
the
> >> remaining SIP and SIPPING documents and progress this item as an
> >> individual AD sponsored.
> >>
> >> Mary.
> >>
> >> On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes =
<rbarnes@bbn.com>
> >> wrote:
> >> > <hat type=3D"individual"/>
> >> >
> >> > I tend to agree with Lorenzo that DISPATCH would be a better =
place to
> >> have
> >> > these discussions, especially given that, as far as I can tell =
from
> >> this
> >> > thread, the problem seems to be a general one of NAT traversal =
for
> >> TCP.
> >> >
> >> >
> >> >
> >> > On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
> >> >
> >> >> Hi all,
> >> >>
> >> >> with respect to this topic, I think there are many issues
> >> implementers
> >> >> have to face when bringing IETF solutions to the real world. We
> >> found
> >> >> ourselves many times in a situation in which some kind of work-
> >> around
> >> >> had to be devised in order to let things work properly. Just to =
cite
> >> a
> >> >> couple of examples, with BFCP we had to find a way to let it =
work in
> >> a
> >> >> distributed conferencing scenario (which is far from easy, given =
the
> >> >> intrinsic centralized model behind such protocol). In such case, =
we
> >> >> decided to encapsulate BFCP messages in the body of XMPP
> >> >> server-to-server packets (see the XCON-DCON Synchronization =
Protocol
> >> in
> >> >> draft-romano-dcon-xdsp-reqs-06 for the details) and then even
> >> devised
> >> >> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
> >> >> traversal issue, we also implemented an HTTP encapsulation. =
Moving
> >> >> further we even conceived a DTMF-based frontend to BFCP ;) and =
also
> >> >> almost thought about a BFCP-over-RTP approach.
> >> >>
> >> >> That said, I nevertheless agree with Keith on the discussion. =
Those
> >> >> problems may be common to other TCP-based protocols as well, and =
as
> >> such
> >> >> a generic solution (generic TCP over UDP, for instance, or =
anything
> >> >> else) may be a much better approach than doing a protocol =
specific
> >> >> patch. Besides, whatever the solution, it should also take care =
of
> >> how
> >> >> the negotiation of such channels would be affected (as is the
> >> >> case of RFC4583 for BFCP, which the proposed draft actually =
does).
> >> >>
> >> >> As Keith already suggested, DISPATCH may be a much better place =
to
> >> >> discuss this issue: DISPATCH is where we'll also propose the =
above
> >> >> mentioned DCON work.
> >> >>
> >> >> Lorenzo
> >> >>
> >> >>
> >> >>
> >> >> On Thu, 10 Jun 2010 08:22:55 +0300
> >> >> "Roni Even" <ron.even.tlv@gmail.com> wrote:
> >> >>
> >> >>> Hi =A0Keith,
> >> >>>
> >> >>> I think that the IETF is trying to design protocols that will =
work
> >> over
> >> >>> the
> >> >>> Internet and also to enable interoperability between =
independent
> >> >>> implementations.
> >> >>>
> >> >>> In the BFCP case the shipping implementations support TCP as =
the
> >> >>> transport
> >> >>> protocol but they encountered issues when running over the =
Internet
> >> due
> >> >>> to
> >> >>> devices like SBCs and due to lack of support for TCP media =
relay or
> >> >>> ICE-TCP
> >> >>> [I-D.ietf-mmusic-ice-tcp].
> >> >>> When implementations looked at how to address the issue, the
> >> >>> interoperability went away since there is no fall back solution =
for
> >> this
> >> >>> real life case. Some did a fall back to HTTP and some did to =
UDP
> >> but not
> >> >>> in
> >> >>> an interoperable way.
> >> >>>
> >> >>> In order to achieve interoperability, this draft is trying to
> >> extend the
> >> >>> current BFCP. It is not suggesting to replace TCP but to keep =
TCP
> >> as the
> >> >>> mandatory transport and use UDP as fallback if unable to =
establish
> >> TCP
> >> >>> connection.
> >> >>>
> >> >>> As for security, if the topic will be adopted the solution will =
be
> >> >>> updated
> >> >>> to use DTLS as the transport for BFCP.
> >> >>>
> >> >>> I hope that people will read the draft and look at the =
objectives
> >> and the
> >> >>> proposed solution.
> >> >>>
> >> >>>
> >> >>> BTW: This is a problem for client to client media connections =
over
> >> TCP
> >> >>> and
> >> >>> my understanding is that RTSP offers to use both TCP and UDP =
since
> >> both
> >> >>> are
> >> >>> specified. Since BFCP is not a payload but is running in =
parallel
> >> to the
> >> >>> RTP
> >> >>> payload (for the point to point calls or MCU based multipoint) =
it
> >> needs
> >> >>> similar transport options.
> >> >>>
> >> >>> Thanks
> >> >>> Roni Even
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>> -----Original Message-----
> >> >>>> From: DRAGE, Keith (Keith) =
[mailto:keith.drage@alcatel-lucent.com]
> >> >>>> Sent: Thursday, June 10, 2010 1:54 AM
> >> >>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> >> >>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
> >> xcon@ietf.org
> >> >>>> Subject: RE: [XCON] WG Adoption? =
draft-sandbakken-xcon-bfcp-udp-02
> >> >>>>
> >> >>>> What you are essentially saying is that all protocols in the
> >> future
> >> >>>> that need reliable transport, as BFCP does, have to design in
> >> their own
> >> >>>> reliable transport element so they can use UDP. This is not a =
BFCP
> >> >>>> specific issue.
> >> >>>>
> >> >>>> I find that an unacceptable direction for IETF to be heading =
in.
> >> >>>>
> >> >>>> I would also note that you are also asking for adoption of a
> >> document
> >> >>>> that cannot in its current form meet the security requirements =
of
> >> the
> >> >>>> original RFC.
> >> >>>>
> >> >>>> regards
> >> >>>>
> >> >>>> Keith
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>> -----Original Message-----
> >> >>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> >> >>>>> Sent: Wednesday, June 09, 2010 1:40 PM
> >> >>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
> >> >>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> >> >>>>> 'Tom Kristensen'; xcon@ietf.org
> >> >>>>> Subject: RE: [XCON] WG Adoption? =
draft-sandbakken-xcon-bfcp-udp-
> >> 02
> >> >>>>>
> >> >>>>> Richard,
> >> >>>>> The BFCP I used as a presentation token for video
> >> >>>>> conferencing. What the implementers found out that TCP does
> >> >>>>> not work in real networks due to Session border controllers
> >> >>>>> not supporting TCP as used in BFCP.
> >> >>>>> This is why in products they try to establish TCP connection
> >> >>>>> and if fails tries UDP.
> >> >>>>> The video conferencing vendors participating in the IMTC sip
> >> >>>>> parity activity group defined an interoperability profile
> >> >>>>> that references this option Roni Even
> >> >>>>>
> >> >>>>>> -----Original Message-----
> >> >>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
> >> >>>>>
> >> >>>>> On Behalf
> >> >>>>>>
> >> >>>>>> Of Richard L. Barnes
> >> >>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
> >> >>>>>> To: Tom Kristensen
> >> >>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> >> >>>>>> Kristensen; xcon@ietf.org
> >> >>>>>> Subject: Re: [XCON] WG Adoption? =
draft-sandbakken-xcon-bfcp-udp-
> >> 02
> >> >>>>>>
> >> >>>>>> Tom and others who are interested in this draft:
> >> >>>>>>
> >> >>>>>> For those who are relatively new here: Could you summarize =
why
> >> you
> >> >>>>>> think this draft is needed? =A0What requirement does it meet
> >> >>>>>
> >> >>>>> that BFCP
> >> >>>>>>
> >> >>>>>> doesn't right now?
> >> >>>>>>
> >> >>>>>> Thanks,
> >> >>>>>> --Richard
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> >> >>>>>>
> >> >>>>>>> The UDP/BFCP draft has been presented and discussed in
> >> >>>>>
> >> >>>>> two or three
> >> >>>>>>>
> >> >>>>>>> IETF XCON sessions. No objection to the work being
> >> >>>>>
> >> >>>>> carried on, just
> >> >>>>>>>
> >> >>>>>>> that adoption as WG item was postponed until the draft was =
more
> >> >>>>>>> complete. (This has been delayed of various reasons, but
> >> >>>>>
> >> >>>>> the authors
> >> >>>>>>>
> >> >>>>>>> believe the -02 version in question here should be ready =
for
> >> >>>>>>> adoption).
> >> >>>>>>>
> >> >>>>>>> The "current status of consensus" might be valid for some, =
but
> >> >>>>>>> participants in the XCON sessions and the minutes of =
meeting
> >> show
> >> >>>>>>> progress away from that initial consensus.
> >> >>>>>>>
> >> >>>>>>> I believe Ott's concerns are either dealt with or at
> >> >>>>>
> >> >>>>> least mentioned
> >> >>>>>>>
> >> >>>>>>> in the draft. Arrest me if I'm wrong.
> >> >>>>>>>
> >> >>>>>>> -- Tom
> >> >>>>>>>
> >> >>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
> >> >>>>>>> <keith.drage@alcatel-lucent.com> wrote:
> >> >>>>>>>>
> >> >>>>>>>> We made an explicit decision in the original draft that
> >> >>>>>
> >> >>>>> UDP was not
> >> >>>>>>>>
> >> >>>>>>>> required, not that we would do it later. That as far as I =
am
> >> >>>>>>>> concerned represents the current status of consensus.
> >> >>>>>>>>
> >> >>>>>>>> This was done on the basis that we had all seen how UDP
> >> >>>>>
> >> >>>>> support had
> >> >>>>>>>>
> >> >>>>>>>> complicated SIP, and we did not want to repeat that issue.
> >> >>>>>>>>
> >> >>>>>>>> So this is not continuing the work. The status is an
> >> >>>>>
> >> >>>>> author draft
> >> >>>>>>>>
> >> >>>>>>>> which goes against a WG consensus position.
> >> >>>>>>>>
> >> >>>>>>>> I believe Georg Ott also expressed some concerns which I =
did
> >> not
> >> >>>>>>>> see answered on list at all.
> >> >>>>>>>>
> >> >>>>>>>> regards
> >> >>>>>>>>
> >> >>>>>>>> Keith
> >> >>>>>>>>
> >> >>>>>>>>> -----Original Message-----
> >> >>>>>>>>> From: xcon-bounces@ietf.org =
[mailto:xcon-bounces@ietf.org] On
> >> >>>>>>>>> Behalf Of Roni Even
> >> >>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
> >> >>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
> >> >>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
> >> >>>>>>>>> Subject: Re: [XCON] WG Adoption?
> >> >>>>>
> >> >>>>> draft-sandbakken-xcon-bfcp-udp-02
> >> >>>>>>>>>
> >> >>>>>>>>> Hi Alan,
> >> >>>>>>>>> I support this work and think it is urgent to finish it.
> >> >>>>>>>>> I think that updating BFCP with UDP support is very
> >> >>>>>
> >> >>>>> important. I
> >> >>>>>>>>>
> >> >>>>>>>>> would like to mention that BFCP is being used in video
> >> >>>>>>>>> conferencing application and since the implementers
> >> encountered
> >> >>>>>>>>> problems with TCP they use a fall back to UDP.
> >> >>>>>>>>> We discussed this work in previous IETF meeting and
> >> >>>>>
> >> >>>>> Gonzalo as far
> >> >>>>>>>>>
> >> >>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
> >> >>>>>>>>>
> >> >>>>>>>>> Thanks
> >> >>>>>>>>> Roni Even
> >> >>>>>>>>>
> >> >>>>>>>>>> -----Original Message-----
> >> >>>>>>>>>> From: xcon-bounces@ietf.org =
[mailto:xcon-bounces@ietf.org]
> >> >>>>>>>>>
> >> >>>>>>>>> On Behalf
> >> >>>>>>>>>>
> >> >>>>>>>>>> Of Alan Johnston
> >> >>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
> >> >>>>>>>>>> To: Tom Kristensen
> >> >>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
> >> >>>>>>>>>> Subject: Re: [XCON] WG Adoption?
> >> >>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
> >> >>>>>>>>>>
> >> >>>>>>>>>> Tom,
> >> >>>>>>>>>>
> >> >>>>>>>>>> Apologies for the delay in replying. =A0As you know, the
> >> >>>>>>>>>
> >> >>>>>>>>> working group
> >> >>>>>>>>>>
> >> >>>>>>>>>> is in the process of completing its final milestones.
> >> >>>>>>>>>> Publication requests will be issued in the next few
> >> >>>>>
> >> >>>>> days for the
> >> >>>>>>>>>>
> >> >>>>>>>>>> data
> >> >>>>>>>>>
> >> >>>>>>>>> model, CCMP,
> >> >>>>>>>>>>
> >> >>>>>>>>>> and the Examples drafts.
> >> >>>>>>>>>>
> >> >>>>>>>>>> Taking on any new milestones for the working group
> >> >>>>>
> >> >>>>> would require:
> >> >>>>>>>>>>
> >> >>>>>>>>>> 1. Strong support and interest from working group
> >> >>>>>
> >> >>>>> participants 2.
> >> >>>>>>>>>>
> >> >>>>>>>>>> Approval of our ADs.
> >> >>>>>>>>>>
> >> >>>>>>>>>> I haven't seen evidence of either of these at this =
stage.
> >> >>>>>>>>>>
> >> >>>>>>>>>> A possible option is to take this work to DISPATCH, get =
an
> >> >>>>>>>>>
> >> >>>>>>>>> indication
> >> >>>>>>>>>>
> >> >>>>>>>>>> of interests, and get feedback on the best way to move
> >> >>>>>
> >> >>>>> this work
> >> >>>>>>>>>>
> >> >>>>>>>>>> forward.
> >> >>>>>>>>>>
> >> >>>>>>>>>> - Alan -
> >> >>>>>>>>>> co-chair XCON
> >> >>>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was =
submitted
> >> >>>>>>>>>
> >> >>>>>>>>> early in
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> March. No comments received since.
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> We'd like guidance on the next steps. First we ask for
> >> >>>>>>>>>
> >> >>>>>>>>> adoption as
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> WG item. Next step would include the merging process =
with
> >> bis
> >> >>>>>>>>>>> versions
> >> >>>>>>>>>>
> >> >>>>>>>>>> of
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> RFC 4582 and RFC 4583.
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> We'd like to point out that interested parties for this
> >> >>>>>>>>>
> >> >>>>>>>>> work indeed
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> exist.
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
> >> >>>>>>>>>
> >> >>>>>>>>> April and May.
> >> >>>>>>>>>>
> >> >>>>>>>>>> See
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> below. No response given. Therefore, this request on
> >> >>>>>
> >> >>>>> the list.)
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> -- Tom
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen =
wrote:
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> Chairs,
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> Any thoughts or decision on this matter?
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> Cheers,
> >> >>>>>>>>>>>> -- Tom
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen =
wrote:
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> XCON chairs,
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> >> >>>>>
> >> >>>>> early in March
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> -
> >> >>>>>>>>>>
> >> >>>>>>>>>> well in
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> advance of IETF-77.
> >> >>>>>>>>>>>>> =
=A0http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
> >> >>>>
> >> >>>> udp
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
> >> >>>>>>>>>
> >> >>>>>>>>> directly to the
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
> >> >>>>>>>>>
> >> >>>>>>>>> as an XCON
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> WG item.
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> -- Tom
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>> _______________________________________________
> >> >>>>>>>>>> XCON mailing list
> >> >>>>>>>>>> XCON@ietf.org
> >> >>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >> >>>>>>>>>
> >> >>>>>>>>> _______________________________________________
> >> >>>>>>>>> XCON mailing list
> >> >>>>>>>>> XCON@ietf.org
> >> >>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >> >>>>>>>>>
> >> >>>>>>>> _______________________________________________
> >> >>>>>>>> XCON mailing list
> >> >>>>>>>> XCON@ietf.org
> >> >>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>> --
> >> >>>>>>> # TANDBERG R&D
> >> >>>>>>> ## http://www.tandberg.com
> >> >>>>>>> ### http://folk.uio.no/tomkri/
> >> >>>>>>> _______________________________________________
> >> >>>>>>> XCON mailing list
> >> >>>>>>> XCON@ietf.org
> >> >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >> >>>>>>
> >> >>>>>> _______________________________________________
> >> >>>>>> XCON mailing list
> >> >>>>>> XCON@ietf.org
> >> >>>>>> https://www.ietf.org/mailman/listinfo/xcon
> >> >>>>>
> >> >>>>> =3D
> >> >>>
> >> >>> _______________________________________________
> >> >>> XCON mailing list
> >> >>> XCON@ietf.org
> >> >>> https://www.ietf.org/mailman/listinfo/xcon
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >> Lorenzo Miniero
> >> >> Meetecho s.r.l.
> >> >> http://www.meetecho.com/
> >> >
> >> > _______________________________________________
> >> > XCON mailing list
> >> > XCON@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/xcon
> >> >
> >> _______________________________________________
> >> XCON mailing list
> >> XCON@ietf.org
> >> https://www.ietf.org/mailman/listinfo/xcon
> >
> > _______________________________________________
> > XCON mailing list
> > XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
> >
>=20
>=20
>=20
> --
> # TANDBERG R&D
> ## http://www.tandberg.com
> ### http://folk.uio.no/tomkri/
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon

From allyn@cisco.com  Thu Jun 24 11:29:34 2010
Return-Path: <allyn@cisco.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2594E3A6912 for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 11:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dGb+IrNeBazV for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 11:29:32 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 1D62E3A6407 for <xcon@ietf.org>; Thu, 24 Jun 2010 11:29:32 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAI5AI0yrR7Hu/2dsb2JhbACfOXGnaJpZglIXgjgEg16NSg
X-IronPort-AV: E=Sophos;i="4.53,475,1272844800"; d="scan'208";a="217241522"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 24 Jun 2010 18:29:40 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o5OITeCK003142; Thu, 24 Jun 2010 18:29:40 GMT
Received: from xmb-sjc-221.amer.cisco.com ([128.107.191.80]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 24 Jun 2010 11:29:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
x-cr-hashedpuzzle: DYDz EMxN O7Vj WTfm aRVR igBd ioPD mBvb tRgJ uZP5 0lgv 5RaN 87ZJ AAzqTg== ACJuBw== AEP+7A==; 7; YQBsAGEAbgAuAGIALgBqAG8AaABuAHMAdABvAG4AQABnAG0AYQBpAGwALgBjAG8AbQA7AGsAZQBpAHQAaAAuAGQAcgBhAGcAZQBAAGEAbABjAGEAdABlAGwALQBsAHUAYwBlAG4AdAAuAGMAbwBtADsAbQBhAHIAawAuAHQAaABvAG0AcABzAG8AbgBAAHQAYQBuAGQAYgBlAHIAZwAuAGMAbwBtADsAbQBhAHIAeQAuAGkAZQB0AGYALgBiAGEAcgBuAGUAcwBAAGcAbQBhAGkAbAAuAGMAbwBtADsAcgBiAGEAcgBuAGUAcwBAAGIAYgBuAC4AYwBvAG0AOwB0AG8AbQAuAGsAcgBpAHMAdABlAG4AcwBlAG4AQAB0AGEAbgBkAGIAZQByAGcALgBjAG8AbQA7AHgAYwBvAG4AQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {AB8115A1-B7BB-46C8-8BCB-C81033A3791B}; YQBsAGwAeQBuAEAAYwBpAHMAYwBvAC4AYwBvAG0A; Thu, 24 Jun 2010 18:29:21 GMT; UgBFADoAIABbAFgAQwBPAE4AXQAgAFcARwAgAEEAZABvAHAAdABpAG8AbgA/ACAAZAByAGEAZgB0AC0AcwBhAG4AZABiAGEAawBrAGUAbgAtAHgAYwBvAG4ALQBiAGYAYwBwAC0AdQBkAHAALQAwADIA
x-cr-puzzleid: {AB8115A1-B7BB-46C8-8BCB-C81033A3791B}
Content-class: urn:content-classes:message
Date: Thu, 24 Jun 2010 11:29:21 -0700
Message-ID: <9AC2C4348FD86B4BB1F8FA9C5E3A5EDC01AE3EB5@xmb-sjc-221.amer.cisco.com>
In-Reply-To: <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
Thread-Index: AcsS8MDZr3NCNB3STCKsU9inEBoTSQA2OkSw
References: <1271757479.26184.8.camel@localhost><1273653780.2694.11.camel@localhost><1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com><4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com><EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com><59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com><4c0f8c0f.9becd80a.55da.0fe2@mx.google.com><EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><4c107733.df0ce30a.21ca.15cc@mx.google.com><20100610130009.1f1fbb03.lorenzo@meetecho.com><0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com> <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com>
From: "Allyn Romanow (allyn)" <allyn@cisco.com>
To: "Mary Barnes" <mary.ietf.barnes@gmail.com>, "Richard L. Barnes" <rbarnes@bbn.com>
X-OriginalArrivalTime: 24 Jun 2010 18:29:40.0108 (UTC) FILETIME=[3524BCC0:01CB13CB]
Cc: Alan Johnston <alan.b.johnston@gmail.com>, Tom Kristensen <tom.kristensen@tandberg.com>, Mark Thompson <mark.thompson@tandberg.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 18:29:34 -0000

Although a general solution for TCP based media would be a very good =
thing to be worked on, we also are in the position of needing an =
immediate solution, and BFCP over UDP fills that bill. So, I'm also in =
favor of working further on the draft and moving forward with it, in =
whichever venue people find convenient.

Allyn

-----Original Message-----
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of =
Mary Barnes
Sent: Wednesday, June 23, 2010 9:26 AM
To: Richard L. Barnes
Cc: Tom Kristensen; DRAGE,Keith (Keith); xcon@ietf.org; Mark Thompson; =
Alan Johnston
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02

I have reviewed the draft in question and while I agree that this
could be viewed as a workaround for some more general problems that
need to be solved, there is a current industry need for the solution
in this draft.   If the general problems described go to DISPATCH
(which is the appropriate thing to do rather than bringing this
specific document), the timeframe for getting agreement on the problem
to be solved and for the solutions to be agreed would be far longer
IMHO than if this document were progressed. If XCON would prefer to
close the WG without progressing this document (in this form or as a
-bis to RFC  4582), my suggestion would be to do as was done for the
remaining SIP and SIPPING documents and progress this item as an
individual AD sponsored.

Mary.

On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes <rbarnes@bbn.com> =
wrote:
> <hat type=3D"individual"/>
>
> I tend to agree with Lorenzo that DISPATCH would be a better place to =
have
> these discussions, especially given that, as far as I can tell from =
this
> thread, the problem seems to be a general one of NAT traversal for =
TCP.
>
>
>
> On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
>
>> Hi all,
>>
>> with respect to this topic, I think there are many issues =
implementers
>> have to face when bringing IETF solutions to the real world. We found
>> ourselves many times in a situation in which some kind of work-around
>> had to be devised in order to let things work properly. Just to cite =
a
>> couple of examples, with BFCP we had to find a way to let it work in =
a
>> distributed conferencing scenario (which is far from easy, given the
>> intrinsic centralized model behind such protocol). In such case, we
>> decided to encapsulate BFCP messages in the body of XMPP
>> server-to-server packets (see the XCON-DCON Synchronization Protocol =
in
>> draft-romano-dcon-xdsp-reqs-06 for the details) and then even devised
>> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
>> traversal issue, we also implemented an HTTP encapsulation. Moving
>> further we even conceived a DTMF-based frontend to BFCP ;) and also
>> almost thought about a BFCP-over-RTP approach.
>>
>> That said, I nevertheless agree with Keith on the discussion. Those
>> problems may be common to other TCP-based protocols as well, and as =
such
>> a generic solution (generic TCP over UDP, for instance, or anything
>> else) may be a much better approach than doing a protocol specific
>> patch. Besides, whatever the solution, it should also take care of =
how
>> the negotiation of such channels would be affected (as is the
>> case of RFC4583 for BFCP, which the proposed draft actually does).
>>
>> As Keith already suggested, DISPATCH may be a much better place to
>> discuss this issue: DISPATCH is where we'll also propose the above
>> mentioned DCON work.
>>
>> Lorenzo
>>
>>
>>
>> On Thu, 10 Jun 2010 08:22:55 +0300
>> "Roni Even" <ron.even.tlv@gmail.com> wrote:
>>
>>> Hi =A0Keith,
>>>
>>> I think that the IETF is trying to design protocols that will work =
over
>>> the
>>> Internet and also to enable interoperability between independent
>>> implementations.
>>>
>>> In the BFCP case the shipping implementations support TCP as the
>>> transport
>>> protocol but they encountered issues when running over the Internet =
due
>>> to
>>> devices like SBCs and due to lack of support for TCP media relay or
>>> ICE-TCP
>>> [I-D.ietf-mmusic-ice-tcp].
>>> When implementations looked at how to address the issue, the
>>> interoperability went away since there is no fall back solution for =
this
>>> real life case. Some did a fall back to HTTP and some did to UDP but =
not
>>> in
>>> an interoperable way.
>>>
>>> In order to achieve interoperability, this draft is trying to extend =
the
>>> current BFCP. It is not suggesting to replace TCP but to keep TCP as =
the
>>> mandatory transport and use UDP as fallback if unable to establish =
TCP
>>> connection.
>>>
>>> As for security, if the topic will be adopted the solution will be
>>> updated
>>> to use DTLS as the transport for BFCP.
>>>
>>> I hope that people will read the draft and look at the objectives =
and the
>>> proposed solution.
>>>
>>>
>>> BTW: This is a problem for client to client media connections over =
TCP
>>> and
>>> my understanding is that RTSP offers to use both TCP and UDP since =
both
>>> are
>>> specified. Since BFCP is not a payload but is running in parallel to =
the
>>> RTP
>>> payload (for the point to point calls or MCU based multipoint) it =
needs
>>> similar transport options.
>>>
>>> Thanks
>>> Roni Even
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
>>>> Sent: Thursday, June 10, 2010 1:54 AM
>>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
>>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen'; =
xcon@ietf.org
>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>
>>>> What you are essentially saying is that all protocols in the future
>>>> that need reliable transport, as BFCP does, have to design in their =
own
>>>> reliable transport element so they can use UDP. This is not a BFCP
>>>> specific issue.
>>>>
>>>> I find that an unacceptable direction for IETF to be heading in.
>>>>
>>>> I would also note that you are also asking for adoption of a =
document
>>>> that cannot in its current form meet the security requirements of =
the
>>>> original RFC.
>>>>
>>>> regards
>>>>
>>>> Keith
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>>>> Sent: Wednesday, June 09, 2010 1:40 PM
>>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
>>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
>>>>> 'Tom Kristensen'; xcon@ietf.org
>>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>>
>>>>> Richard,
>>>>> The BFCP I used as a presentation token for video
>>>>> conferencing. What the implementers found out that TCP does
>>>>> not work in real networks due to Session border controllers
>>>>> not supporting TCP as used in BFCP.
>>>>> This is why in products they try to establish TCP connection
>>>>> and if fails tries UDP.
>>>>> The video conferencing vendors participating in the IMTC sip
>>>>> parity activity group defined an interoperability profile
>>>>> that references this option Roni Even
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>
>>>>> On Behalf
>>>>>>
>>>>>> Of Richard L. Barnes
>>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
>>>>>> To: Tom Kristensen
>>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
>>>>>> Kristensen; xcon@ietf.org
>>>>>> Subject: Re: [XCON] WG Adoption? =
draft-sandbakken-xcon-bfcp-udp-02
>>>>>>
>>>>>> Tom and others who are interested in this draft:
>>>>>>
>>>>>> For those who are relatively new here: Could you summarize why =
you
>>>>>> think this draft is needed? =A0What requirement does it meet
>>>>>
>>>>> that BFCP
>>>>>>
>>>>>> doesn't right now?
>>>>>>
>>>>>> Thanks,
>>>>>> --Richard
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
>>>>>>
>>>>>>> The UDP/BFCP draft has been presented and discussed in
>>>>>
>>>>> two or three
>>>>>>>
>>>>>>> IETF XCON sessions. No objection to the work being
>>>>>
>>>>> carried on, just
>>>>>>>
>>>>>>> that adoption as WG item was postponed until the draft was more
>>>>>>> complete. (This has been delayed of various reasons, but
>>>>>
>>>>> the authors
>>>>>>>
>>>>>>> believe the -02 version in question here should be ready for
>>>>>>> adoption).
>>>>>>>
>>>>>>> The "current status of consensus" might be valid for some, but
>>>>>>> participants in the XCON sessions and the minutes of meeting =
show
>>>>>>> progress away from that initial consensus.
>>>>>>>
>>>>>>> I believe Ott's concerns are either dealt with or at
>>>>>
>>>>> least mentioned
>>>>>>>
>>>>>>> in the draft. Arrest me if I'm wrong.
>>>>>>>
>>>>>>> -- Tom
>>>>>>>
>>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
>>>>>>> <keith.drage@alcatel-lucent.com> wrote:
>>>>>>>>
>>>>>>>> We made an explicit decision in the original draft that
>>>>>
>>>>> UDP was not
>>>>>>>>
>>>>>>>> required, not that we would do it later. That as far as I am
>>>>>>>> concerned represents the current status of consensus.
>>>>>>>>
>>>>>>>> This was done on the basis that we had all seen how UDP
>>>>>
>>>>> support had
>>>>>>>>
>>>>>>>> complicated SIP, and we did not want to repeat that issue.
>>>>>>>>
>>>>>>>> So this is not continuing the work. The status is an
>>>>>
>>>>> author draft
>>>>>>>>
>>>>>>>> which goes against a WG consensus position.
>>>>>>>>
>>>>>>>> I believe Georg Ott also expressed some concerns which I did =
not
>>>>>>>> see answered on list at all.
>>>>>>>>
>>>>>>>> regards
>>>>>>>>
>>>>>>>> Keith
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
>>>>>>>>> Behalf Of Roni Even
>>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
>>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
>>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>
>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>
>>>>>>>>> Hi Alan,
>>>>>>>>> I support this work and think it is urgent to finish it.
>>>>>>>>> I think that updating BFCP with UDP support is very
>>>>>
>>>>> important. I
>>>>>>>>>
>>>>>>>>> would like to mention that BFCP is being used in video
>>>>>>>>> conferencing application and since the implementers =
encountered
>>>>>>>>> problems with TCP they use a fall back to UDP.
>>>>>>>>> We discussed this work in previous IETF meeting and
>>>>>
>>>>> Gonzalo as far
>>>>>>>>>
>>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Roni Even
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>>>>>
>>>>>>>>> On Behalf
>>>>>>>>>>
>>>>>>>>>> Of Alan Johnston
>>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>>>>>>>>>> To: Tom Kristensen
>>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
>>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>>
>>>>>>>>>> Tom,
>>>>>>>>>>
>>>>>>>>>> Apologies for the delay in replying. =A0As you know, the
>>>>>>>>>
>>>>>>>>> working group
>>>>>>>>>>
>>>>>>>>>> is in the process of completing its final milestones.
>>>>>>>>>> Publication requests will be issued in the next few
>>>>>
>>>>> days for the
>>>>>>>>>>
>>>>>>>>>> data
>>>>>>>>>
>>>>>>>>> model, CCMP,
>>>>>>>>>>
>>>>>>>>>> and the Examples drafts.
>>>>>>>>>>
>>>>>>>>>> Taking on any new milestones for the working group
>>>>>
>>>>> would require:
>>>>>>>>>>
>>>>>>>>>> 1. Strong support and interest from working group
>>>>>
>>>>> participants 2.
>>>>>>>>>>
>>>>>>>>>> Approval of our ADs.
>>>>>>>>>>
>>>>>>>>>> I haven't seen evidence of either of these at this stage.
>>>>>>>>>>
>>>>>>>>>> A possible option is to take this work to DISPATCH, get an
>>>>>>>>>
>>>>>>>>> indication
>>>>>>>>>>
>>>>>>>>>> of interests, and get feedback on the best way to move
>>>>>
>>>>> this work
>>>>>>>>>>
>>>>>>>>>> forward.
>>>>>>>>>>
>>>>>>>>>> - Alan -
>>>>>>>>>> co-chair XCON
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>>>>>>>>>>>
>>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>>>>>>>>>
>>>>>>>>> early in
>>>>>>>>>>>
>>>>>>>>>>> March. No comments received since.
>>>>>>>>>>>
>>>>>>>>>>> We'd like guidance on the next steps. First we ask for
>>>>>>>>>
>>>>>>>>> adoption as
>>>>>>>>>>>
>>>>>>>>>>> WG item. Next step would include the merging process with =
bis
>>>>>>>>>>> versions
>>>>>>>>>>
>>>>>>>>>> of
>>>>>>>>>>>
>>>>>>>>>>> RFC 4582 and RFC 4583.
>>>>>>>>>>>
>>>>>>>>>>> We'd like to point out that interested parties for this
>>>>>>>>>
>>>>>>>>> work indeed
>>>>>>>>>>>
>>>>>>>>>>> exist.
>>>>>>>>>>>
>>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
>>>>>>>>>
>>>>>>>>> April and May.
>>>>>>>>>>
>>>>>>>>>> See
>>>>>>>>>>>
>>>>>>>>>>> below. No response given. Therefore, this request on
>>>>>
>>>>> the list.)
>>>>>>>>>>>
>>>>>>>>>>> -- Tom
>>>>>>>>>>>
>>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Chairs,
>>>>>>>>>>>>
>>>>>>>>>>>> Any thoughts or decision on this matter?
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> XCON chairs,
>>>>>>>>>>>>>
>>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
>>>>>
>>>>> early in March
>>>>>>>>>>>>>
>>>>>>>>>>>>> -
>>>>>>>>>>
>>>>>>>>>> well in
>>>>>>>>>>>>>
>>>>>>>>>>>>> advance of IETF-77.
>>>>>>>>>>>>> =A0http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
>>>>
>>>> udp
>>>>>>>>>>>>>
>>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
>>>>>>>>>
>>>>>>>>> directly to the
>>>>>>>>>>>>>
>>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
>>>>>>>>>
>>>>>>>>> as an XCON
>>>>>>>>>>>>>
>>>>>>>>>>>>> WG item.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> XCON mailing list
>>>>>>>>>> XCON@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> XCON mailing list
>>>>>>>>> XCON@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> XCON mailing list
>>>>>>>> XCON@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> # TANDBERG R&D
>>>>>>> ## http://www.tandberg.com
>>>>>>> ### http://folk.uio.no/tomkri/
>>>>>>> _______________________________________________
>>>>>>> XCON mailing list
>>>>>>> XCON@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>
>>>>>> _______________________________________________
>>>>>> XCON mailing list
>>>>>> XCON@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>
>>>>> =3D
>>>
>>> _______________________________________________
>>> XCON mailing list
>>> XCON@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xcon
>>>
>>
>>
>> --
>> Lorenzo Miniero
>> Meetecho s.r.l.
>> http://www.meetecho.com/
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>
_______________________________________________
XCON mailing list
XCON@ietf.org
https://www.ietf.org/mailman/listinfo/xcon

From patrick.luthi@tandberg.com  Thu Jun 24 12:20:42 2010
Return-Path: <patrick.luthi@tandberg.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC3183A6837 for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 12:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.134
X-Spam-Level: 
X-Spam-Status: No, score=-6.134 tagged_above=-999 required=5 tests=[AWL=0.464,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+qkgLS+Jqnh for <xcon@core3.amsl.com>; Thu, 24 Jun 2010 12:20:35 -0700 (PDT)
Received: from mail195.messagelabs.com (mail195.messagelabs.com [85.158.138.147]) by core3.amsl.com (Postfix) with SMTP id 3B9A03A6A5C for <xcon@ietf.org>; Thu, 24 Jun 2010 12:20:32 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: patrick.luthi@tandberg.com
X-Msg-Ref: server-14.tower-195.messagelabs.com!1277407234!37025615!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [62.70.2.252]
Received: (qmail 25310 invoked from network); 24 Jun 2010 19:20:34 -0000
Received: from unknown (HELO OSLEXCP11.eu.tandberg.int) (62.70.2.252) by server-14.tower-195.messagelabs.com with SMTP; 24 Jun 2010 19:20:34 -0000
Received: from oslexcp2.eu.tandberg.int ([10.47.136.30]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Thu, 24 Jun 2010 21:20:34 +0200
Received: from suisse127.tandberg.com ([10.0.6.163]) by oslexcp2.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 24 Jun 2010 21:19:57 +0200
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 24 Jun 2010 21:19:20 +0200
To: stephen botzko <stephen.botzko@gmail.com>, Roni Even <ron.even.tlv@gmail.com>
From: Patrick Luthi <patrick.luthi@tandberg.com>
In-Reply-To: <AANLkTinzNkKCmheW9CM85ppzBlhL3tM0eh87iKM-29A_@mail.gmail.c om>
References: <1271757479.26184.8.camel@localhost> <1273653780.2694.11.camel@localhost> <1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com> <4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com> <59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com> <4c0f8c0f.9becd80a.55da.0fe2@mx.google.com> <EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4c107733.df0ce30a.21ca.15cc@mx.google.com> <20100610130009.1f1fbb03.lorenzo@meetecho.com> <0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com> <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com> <4c236e60.9d90d80a.1d25.6b10@mx.google.com> <AANLkTinzNkKCmheW9CM85ppzBlhL3tM0eh87iKM-29A_@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_115125953==.ALT"
Message-ID: <OSLEXCP2OyDc41W2ufy000007db@oslexcp2.eu.tandberg.int>
X-OriginalArrivalTime: 24 Jun 2010 19:19:57.0373 (UTC) FILETIME=[3B92D6D0:01CB13D2]
Cc: Tom Kristensen <tom.kristensen@tandberg.com>, Mark Thompson <mark.thompson@tandberg.com>, Alan Johnston <alan.b.johnston@gmail.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 19:20:42 -0000

--=====================_115125953==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Great to hear that since I was making that point about the problem 
with TCP for videoconferencing in a previous post!

XCON seems to be the right place for this work, but if the WG closes, 
then Mary's suggestion is perfectly good. The key is to have a solution soon!

Regards,

Patrick

At 17:29 24/06/2010, stephen botzko wrote:
>BFCP is an important component in our application 
>(videoconferencing).  The inability to use BFCP when TCP cannot be 
>used is a huge problem for us today.
>
>So I would like to see this document progressed.
>
>If for some reason XCON doesn't finish it before the WG is closed, I 
>think Mary's suggestion of progressing it under individual AD 
>sponsorship is good.
>
>Stephen Botzko
>
>
>
>2010/6/24 Roni Even <<mailto:ron.even.tlv@gmail.com>ron.even.tlv@gmail.com>
>Mary,
>I think that in the discussion in the past, Gonzalo suggested to do a bis
>draft to RFC 4582. I think he mentioned other issues he wanted to update.
>Roni Even
>
> > -----Original Message-----
> > From: <mailto:xcon-bounces@ietf.org>xcon-bounces@ietf.org 
> [mailto:xcon-bounces@ietf.org] On Behalf Of
> > Mary Barnes
> > Sent: Wednesday, June 23, 2010 7:26 PM
> > To: Richard L. Barnes
> > Cc: Tom Kristensen; DRAGE, Keith (Keith); 
> <mailto:xcon@ietf.org>xcon@ietf.org; Mark Thompson;
> > Alan Johnston
> > Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> >
> > I have reviewed the draft in question and while I agree that this
> > could be viewed as a workaround for some more general problems that
> > need to be solved, there is a current industry need for the solution
> > in this draft.   If the general problems described go to DISPATCH
> > (which is the appropriate thing to do rather than bringing this
> > specific document), the timeframe for getting agreement on the problem
> > to be solved and for the solutions to be agreed would be far longer
> > IMHO than if this document were progressed. If XCON would prefer to
> > close the WG without progressing this document (in this form or as a
> > -bis to RFC  4582), my suggestion would be to do as was done for the
> > remaining SIP and SIPPING documents and progress this item as an
> > individual AD sponsored.
> >
> > Mary.
> >
> > On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes 
> <<mailto:rbarnes@bbn.com>rbarnes@bbn.com>
> > wrote:
> > > <hat type="individual"/>
> > >
> > > I tend to agree with Lorenzo that DISPATCH would be a better place to
> > have
> > > these discussions, especially given that, as far as I can tell from
> > this
> > > thread, the problem seems to be a general one of NAT traversal for
> > TCP.
> > >
> > >
> > >
> > > On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
> > >
> > >> Hi all,
> > >>
> > >> with respect to this topic, I think there are many issues
> > implementers
> > >> have to face when bringing IETF solutions to the real world. We
> > found
> > >> ourselves many times in a situation in which some kind of work-
> > around
> > >> had to be devised in order to let things work properly. Just to cite
> > a
> > >> couple of examples, with BFCP we had to find a way to let it work in
> > a
> > >> distributed conferencing scenario (which is far from easy, given the
> > >> intrinsic centralized model behind such protocol). In such case, we
> > >> decided to encapsulate BFCP messages in the body of XMPP
> > >> server-to-server packets (see the XCON-DCON Synchronization Protocol
> > in
> > >> draft-romano-dcon-xdsp-reqs-06 for the details) and then even
> > devised
> > >> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
> > >> traversal issue, we also implemented an HTTP encapsulation. Moving
> > >> further we even conceived a DTMF-based frontend to BFCP ;) and also
> > >> almost thought about a BFCP-over-RTP approach.
> > >>
> > >> That said, I nevertheless agree with Keith on the discussion. Those
> > >> problems may be common to other TCP-based protocols as well, and as
> > such
> > >> a generic solution (generic TCP over UDP, for instance, or anything
> > >> else) may be a much better approach than doing a protocol specific
> > >> patch. Besides, whatever the solution, it should also take care of
> > how
> > >> the negotiation of such channels would be affected (as is the
> > >> case of RFC4583 for BFCP, which the proposed draft actually does).
> > >>
> > >> As Keith already suggested, DISPATCH may be a much better place to
> > >> discuss this issue: DISPATCH is where we'll also propose the above
> > >> mentioned DCON work.
> > >>
> > >> Lorenzo
> > >>
> > >>
> > >>
> > >> On Thu, 10 Jun 2010 08:22:55 +0300
> > >> "Roni Even" 
> <<mailto:ron.even.tlv@gmail.com>ron.even.tlv@gmail.com> wrote:
> > >>
> > >>> Hi  Keith,
> > >>>
> > >>> I think that the IETF is trying to design protocols that will work
> > over
> > >>> the
> > >>> Internet and also to enable interoperability between independent
> > >>> implementations.
> > >>>
> > >>> In the BFCP case the shipping implementations support TCP as the
> > >>> transport
> > >>> protocol but they encountered issues when running over the Internet
> > due
> > >>> to
> > >>> devices like SBCs and due to lack of support for TCP media relay or
> > >>> ICE-TCP
> > >>> [I-D.ietf-mmusic-ice-tcp].
> > >>> When implementations looked at how to address the issue, the
> > >>> interoperability went away since there is no fall back solution for
> > this
> > >>> real life case. Some did a fall back to HTTP and some did to UDP
> > but not
> > >>> in
> > >>> an interoperable way.
> > >>>
> > >>> In order to achieve interoperability, this draft is trying to
> > extend the
> > >>> current BFCP. It is not suggesting to replace TCP but to keep TCP
> > as the
> > >>> mandatory transport and use UDP as fallback if unable to establish
> > TCP
> > >>> connection.
> > >>>
> > >>> As for security, if the topic will be adopted the solution will be
> > >>> updated
> > >>> to use DTLS as the transport for BFCP.
> > >>>
> > >>> I hope that people will read the draft and look at the objectives
> > and the
> > >>> proposed solution.
> > >>>
> > >>>
> > >>> BTW: This is a problem for client to client media connections over
> > TCP
> > >>> and
> > >>> my understanding is that RTSP offers to use both TCP and UDP since
> > both
> > >>> are
> > >>> specified. Since BFCP is not a payload but is running in parallel
> > to the
> > >>> RTP
> > >>> payload (for the point to point calls or MCU based multipoint) it
> > needs
> > >>> similar transport options.
> > >>>
> > >>> Thanks
> > >>> Roni Even
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
> > >>>> Sent: Thursday, June 10, 2010 1:54 AM
> > >>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
> > >>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
> > <mailto:xcon@ietf.org>xcon@ietf.org
> > >>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
> > >>>>
> > >>>> What you are essentially saying is that all protocols in the
> > future
> > >>>> that need reliable transport, as BFCP does, have to design in
> > their own
> > >>>> reliable transport element so they can use UDP. This is not a BFCP
> > >>>> specific issue.
> > >>>>
> > >>>> I find that an unacceptable direction for IETF to be heading in.
> > >>>>
> > >>>> I would also note that you are also asking for adoption of a
> > document
> > >>>> that cannot in its current form meet the security requirements of
> > the
> > >>>> original RFC.
> > >>>>
> > >>>> regards
> > >>>>
> > >>>> Keith
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > >>>>> Sent: Wednesday, June 09, 2010 1:40 PM
> > >>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
> > >>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
> > >>>>> 'Tom Kristensen'; <mailto:xcon@ietf.org>xcon@ietf.org
> > >>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> > 02
> > >>>>>
> > >>>>> Richard,
> > >>>>> The BFCP I used as a presentation token for video
> > >>>>> conferencing. What the implementers found out that TCP does
> > >>>>> not work in real networks due to Session border controllers
> > >>>>> not supporting TCP as used in BFCP.
> > >>>>> This is why in products they try to establish TCP connection
> > >>>>> and if fails tries UDP.
> > >>>>> The video conferencing vendors participating in the IMTC sip
> > >>>>> parity activity group defined an interoperability profile
> > >>>>> that references this option Roni Even
> > >>>>>
> > >>>>>> -----Original Message-----
> > >>>>>> From: <mailto:xcon-bounces@ietf.org>xcon-bounces@ietf.org 
> [mailto:xcon-bounces@ietf.org]
> > >>>>>
> > >>>>> On Behalf
> > >>>>>>
> > >>>>>> Of Richard L. Barnes
> > >>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
> > >>>>>> To: Tom Kristensen
> > >>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
> > >>>>>> Kristensen; <mailto:xcon@ietf.org>xcon@ietf.org
> > >>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
> > 02
> > >>>>>>
> > >>>>>> Tom and others who are interested in this draft:
> > >>>>>>
> > >>>>>> For those who are relatively new here: Could you summarize why
> > you
> > >>>>>> think this draft is needed?  What requirement does it meet
> > >>>>>
> > >>>>> that BFCP
> > >>>>>>
> > >>>>>> doesn't right now?
> > >>>>>>
> > >>>>>> Thanks,
> > >>>>>> --Richard
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
> > >>>>>>
> > >>>>>>> The UDP/BFCP draft has been presented and discussed in
> > >>>>>
> > >>>>> two or three
> > >>>>>>>
> > >>>>>>> IETF XCON sessions. No objection to the work being
> > >>>>>
> > >>>>> carried on, just
> > >>>>>>>
> > >>>>>>> that adoption as WG item was postponed until the draft was more
> > >>>>>>> complete. (This has been delayed of various reasons, but
> > >>>>>
> > >>>>> the authors
> > >>>>>>>
> > >>>>>>> believe the -02 version in question here should be ready for
> > >>>>>>> adoption).
> > >>>>>>>
> > >>>>>>> The "current status of consensus" might be valid for some, but
> > >>>>>>> participants in the XCON sessions and the minutes of meeting
> > show
> > >>>>>>> progress away from that initial consensus.
> > >>>>>>>
> > >>>>>>> I believe Ott's concerns are either dealt with or at
> > >>>>>
> > >>>>> least mentioned
> > >>>>>>>
> > >>>>>>> in the draft. Arrest me if I'm wrong.
> > >>>>>>>
> > >>>>>>> -- Tom
> > >>>>>>>
> > >>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
> > >>>>>>> 
> <<mailto:keith.drage@alcatel-lucent.com>keith.drage@alcatel-lucent.com> wrote:
> > >>>>>>>>
> > >>>>>>>> We made an explicit decision in the original draft that
> > >>>>>
> > >>>>> UDP was not
> > >>>>>>>>
> > >>>>>>>> required, not that we would do it later. That as far as I am
> > >>>>>>>> concerned represents the current status of consensus.
> > >>>>>>>>
> > >>>>>>>> This was done on the basis that we had all seen how UDP
> > >>>>>
> > >>>>> support had
> > >>>>>>>>
> > >>>>>>>> complicated SIP, and we did not want to repeat that issue.
> > >>>>>>>>
> > >>>>>>>> So this is not continuing the work. The status is an
> > >>>>>
> > >>>>> author draft
> > >>>>>>>>
> > >>>>>>>> which goes against a WG consensus position.
> > >>>>>>>>
> > >>>>>>>> I believe Georg Ott also expressed some concerns which I did
> > not
> > >>>>>>>> see answered on list at all.
> > >>>>>>>>
> > >>>>>>>> regards
> > >>>>>>>>
> > >>>>>>>> Keith
> > >>>>>>>>
> > >>>>>>>>> -----Original Message-----
> > >>>>>>>>> From: 
> <mailto:xcon-bounces@ietf.org>xcon-bounces@ietf.org 
> [mailto:xcon-bounces@ietf.org] On
> > >>>>>>>>> Behalf Of Roni Even
> > >>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
> > >>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
> > >>>>>>>>> Cc: 'Mark Thompson'; <mailto:xcon@ietf.org>xcon@ietf.org
> > >>>>>>>>> Subject: Re: [XCON] WG Adoption?
> > >>>>>
> > >>>>> draft-sandbakken-xcon-bfcp-udp-02
> > >>>>>>>>>
> > >>>>>>>>> Hi Alan,
> > >>>>>>>>> I support this work and think it is urgent to finish it.
> > >>>>>>>>> I think that updating BFCP with UDP support is very
> > >>>>>
> > >>>>> important. I
> > >>>>>>>>>
> > >>>>>>>>> would like to mention that BFCP is being used in video
> > >>>>>>>>> conferencing application and since the implementers
> > encountered
> > >>>>>>>>> problems with TCP they use a fall back to UDP.
> > >>>>>>>>> We discussed this work in previous IETF meeting and
> > >>>>>
> > >>>>> Gonzalo as far
> > >>>>>>>>>
> > >>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
> > >>>>>>>>>
> > >>>>>>>>> Thanks
> > >>>>>>>>> Roni Even
> > >>>>>>>>>
> > >>>>>>>>>> -----Original Message-----
> > >>>>>>>>>> From: 
> <mailto:xcon-bounces@ietf.org>xcon-bounces@ietf.org 
> [mailto:xcon-bounces@ietf.org]
> > >>>>>>>>>
> > >>>>>>>>> On Behalf
> > >>>>>>>>>>
> > >>>>>>>>>> Of Alan Johnston
> > >>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
> > >>>>>>>>>> To: Tom Kristensen
> > >>>>>>>>>> Cc: Mark Thompson; <mailto:xcon@ietf.org>xcon@ietf.org
> > >>>>>>>>>> Subject: Re: [XCON] WG Adoption?
> > >>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
> > >>>>>>>>>>
> > >>>>>>>>>> Tom,
> > >>>>>>>>>>
> > >>>>>>>>>> Apologies for the delay in replying.  As you know, the
> > >>>>>>>>>
> > >>>>>>>>> working group
> > >>>>>>>>>>
> > >>>>>>>>>> is in the process of completing its final milestones.
> > >>>>>>>>>> Publication requests will be issued in the next few
> > >>>>>
> > >>>>> days for the
> > >>>>>>>>>>
> > >>>>>>>>>> data
> > >>>>>>>>>
> > >>>>>>>>> model, CCMP,
> > >>>>>>>>>>
> > >>>>>>>>>> and the Examples drafts.
> > >>>>>>>>>>
> > >>>>>>>>>> Taking on any new milestones for the working group
> > >>>>>
> > >>>>> would require:
> > >>>>>>>>>>
> > >>>>>>>>>> 1. Strong support and interest from working group
> > >>>>>
> > >>>>> participants 2.
> > >>>>>>>>>>
> > >>>>>>>>>> Approval of our ADs.
> > >>>>>>>>>>
> > >>>>>>>>>> I haven't seen evidence of either of these at this stage.
> > >>>>>>>>>>
> > >>>>>>>>>> A possible option is to take this work to DISPATCH, get an
> > >>>>>>>>>
> > >>>>>>>>> indication
> > >>>>>>>>>>
> > >>>>>>>>>> of interests, and get feedback on the best way to move
> > >>>>>
> > >>>>> this work
> > >>>>>>>>>>
> > >>>>>>>>>> forward.
> > >>>>>>>>>>
> > >>>>>>>>>> - Alan -
> > >>>>>>>>>> co-chair XCON
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
> > >>>>>>>>>
> > >>>>>>>>> early in
> > >>>>>>>>>>>
> > >>>>>>>>>>> March. No comments received since.
> > >>>>>>>>>>>
> > >>>>>>>>>>> We'd like guidance on the next steps. First we ask for
> > >>>>>>>>>
> > >>>>>>>>> adoption as
> > >>>>>>>>>>>
> > >>>>>>>>>>> WG item. Next step would include the merging process with
> > bis
> > >>>>>>>>>>> versions
> > >>>>>>>>>>
> > >>>>>>>>>> of
> > >>>>>>>>>>>
> > >>>>>>>>>>> RFC 4582 and RFC 4583.
> > >>>>>>>>>>>
> > >>>>>>>>>>> We'd like to point out that interested parties for this
> > >>>>>>>>>
> > >>>>>>>>> work indeed
> > >>>>>>>>>>>
> > >>>>>>>>>>> exist.
> > >>>>>>>>>>>
> > >>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
> > >>>>>>>>>
> > >>>>>>>>> April and May.
> > >>>>>>>>>>
> > >>>>>>>>>> See
> > >>>>>>>>>>>
> > >>>>>>>>>>> below. No response given. Therefore, this request on
> > >>>>>
> > >>>>> the list.)
> > >>>>>>>>>>>
> > >>>>>>>>>>> -- Tom
> > >>>>>>>>>>>
> > >>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Chairs,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Any thoughts or decision on this matter?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Cheers,
> > >>>>>>>>>>>> -- Tom
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> XCON chairs,
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
> > >>>>>
> > >>>>> early in March
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> -
> > >>>>>>>>>>
> > >>>>>>>>>> well in
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> advance of IETF-77.
> > >>>>>>>>>>>>> 
> <http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp->http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
> > >>>>
> > >>>> udp
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
> > >>>>>>>>>
> > >>>>>>>>> directly to the
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
> > >>>>>>>>>
> > >>>>>>>>> as an XCON
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> WG item.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> -- Tom
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>> _______________________________________________
> > >>>>>>>>>> XCON mailing list
> > >>>>>>>>>> <mailto:XCON@ietf.org>XCON@ietf.org
> > >>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>>>
> > >>>>>>>>> _______________________________________________
> > >>>>>>>>> XCON mailing list
> > >>>>>>>>> <mailto:XCON@ietf.org>XCON@ietf.org
> > >>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>>>
> > >>>>>>>> _______________________________________________
> > >>>>>>>> XCON mailing list
> > >>>>>>>> <mailto:XCON@ietf.org>XCON@ietf.org
> > >>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> # TANDBERG R&D
> > >>>>>>> ## <http://www.tandberg.com>http://www.tandberg.com
> > >>>>>>> ### http://folk.uio.no/tomkri/
> > >>>>>>> _______________________________________________
> > >>>>>>> XCON mailing list
> > >>>>>>> <mailto:XCON@ietf.org>XCON@ietf.org
> > >>>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>> XCON mailing list
> > >>>>>> <mailto:XCON@ietf.org>XCON@ietf.org
> > >>>>>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>>>
> > >>>>> =
> > >>>
> > >>> _______________________________________________
> > >>> XCON mailing list
> > >>> <mailto:XCON@ietf.org>XCON@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/xcon
> > >>>
> > >>
> > >>
> > >> --
> > >> Lorenzo Miniero
> > >> Meetecho s.r.l.
> > >> <http://www.meetecho.com/>http://www.meetecho.com/
> > >
> > > _______________________________________________
> > > XCON mailing list
> > > <mailto:XCON@ietf.org>XCON@ietf.org
> > > https://www.ietf.org/mailman/listinfo/xcon
> > >
> > _______________________________________________
> > XCON mailing list
> > <mailto:XCON@ietf.org>XCON@ietf.org
> > https://www.ietf.org/mailman/listinfo/xcon
>
>_______________________________________________
>XCON mailing list
><mailto:XCON@ietf.org>XCON@ietf.org
>https://www.ietf.org/mailman/listinfo/xcon
>
>
>_______________________________________________
>XCON mailing list
>XCON@ietf.org
>https://www.ietf.org/mailman/listinfo/xcon

--=====================_115125953==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Great to hear that since I was making that point about the problem with
TCP for videoconferencing in a previous post!<br><br>
XCON seems to be the right place for this work, but if the WG closes,
then Mary's suggestion is perfectly good. The key is to have a solution
soon!<br><br>
Regards,<br><br>
Patrick<br><br>
At 17:29 24/06/2010, stephen botzko wrote:<br>
<blockquote type=cite class=cite cite="">BFCP is an important component
in our application (videoconferencing).&nbsp; The inability to use BFCP
when TCP cannot be used is a huge problem for us today.<br><br>
So I would like to see this document progressed.&nbsp; <br><br>
If for some reason XCON doesn't finish it before the WG is closed, I
think Mary's suggestion of progressing it under individual AD sponsorship
is good.<br><br>
Stephen Botzko<br><br>
<br><br>
2010/6/24 Roni Even
&lt;<a href="mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>
&gt;<br>

<dl>
<dd>Mary,<br>

<dd>I think that in the discussion in the past, Gonzalo suggested to do a
bis<br>

<dd>draft to RFC 4582. I think he mentioned other issues he wanted to
update.<br>

<dd>Roni Even<br><br>

<dd>&gt; -----Original Message-----<br>

<dd>&gt; From:
<a href="mailto:xcon-bounces@ietf.org">xcon-bounces@ietf.org</a>
[<a href="mailto:xcon-bounces@ietf.org" eudora="autourl">
mailto:xcon-bounces@ietf.org</a>] On Behalf Of<br>

<dd>&gt; Mary Barnes<br>

<dd>&gt; Sent: Wednesday, June 23, 2010 7:26 PM<br>

<dd>&gt; To: Richard L. Barnes<br>

<dd>&gt; Cc: Tom Kristensen; DRAGE, Keith (Keith);
<a href="mailto:xcon@ietf.org">xcon@ietf.org</a>; Mark Thompson;<br>

<dd>&gt; Alan Johnston<br>

<dd>&gt; Subject: Re: [XCON] WG Adoption?
draft-sandbakken-xcon-bfcp-udp-02<br>

<dd>&gt;<br>

<dd>&gt; I have reviewed the draft in question and while I agree that
this<br>

<dd>&gt; could be viewed as a workaround for some more general problems
that<br>

<dd>&gt; need to be solved, there is a current industry need for the
solution<br>

<dd>&gt; in this draft.&nbsp;&nbsp; If the general problems described go
to DISPATCH<br>

<dd>&gt; (which is the appropriate thing to do rather than bringing
this<br>

<dd>&gt; specific document), the timeframe for getting agreement on the
problem<br>

<dd>&gt; to be solved and for the solutions to be agreed would be far
longer<br>

<dd>&gt; IMHO than if this document were progressed. If XCON would prefer
to<br>

<dd>&gt; close the WG without progressing this document (in this form or
as a<br>

<dd>&gt; -bis to RFC&nbsp; 4582), my suggestion would be to do as was
done for the<br>

<dd>&gt; remaining SIP and SIPPING documents and progress this item as
an<br>

<dd>&gt; individual AD sponsored.<br>

<dd>&gt;<br>

<dd>&gt; Mary.<br>

<dd>&gt;<br>

<dd>&gt; On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes
&lt;<a href="mailto:rbarnes@bbn.com">rbarnes@bbn.com</a>&gt;<br>

<dd>&gt; wrote:<br>

<dd>&gt; &gt; &lt;hat type=&quot;individual&quot;/&gt;<br>

<dd>&gt; &gt;<br>

<dd>&gt; &gt; I tend to agree with Lorenzo that DISPATCH would be a
better place to<br>

<dd>&gt; have<br>

<dd>&gt; &gt; these discussions, especially given that, as far as I can
tell from<br>

<dd>&gt; this<br>

<dd>&gt; &gt; thread, the problem seems to be a general one of NAT
traversal for<br>

<dd>&gt; TCP.<br>

<dd>&gt; &gt;<br>

<dd>&gt; &gt;<br>

<dd>&gt; &gt;<br>

<dd>&gt; &gt; On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:<br>

<dd>&gt; &gt;<br>

<dd>&gt; &gt;&gt; Hi all,<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt; with respect to this topic, I think there are many
issues<br>

<dd>&gt; implementers<br>

<dd>&gt; &gt;&gt; have to face when bringing IETF solutions to the real
world. We<br>

<dd>&gt; found<br>

<dd>&gt; &gt;&gt; ourselves many times in a situation in which some kind
of work-<br>

<dd>&gt; around<br>

<dd>&gt; &gt;&gt; had to be devised in order to let things work properly.
Just to cite<br>

<dd>&gt; a<br>

<dd>&gt; &gt;&gt; couple of examples, with BFCP we had to find a way to
let it work in<br>

<dd>&gt; a<br>

<dd>&gt; &gt;&gt; distributed conferencing scenario (which is far from
easy, given the<br>

<dd>&gt; &gt;&gt; intrinsic centralized model behind such protocol). In
such case, we<br>

<dd>&gt; &gt;&gt; decided to encapsulate BFCP messages in the body of
XMPP<br>

<dd>&gt; &gt;&gt; server-to-server packets (see the XCON-DCON
Synchronization Protocol<br>

<dd>&gt; in<br>

<dd>&gt; &gt;&gt; draft-romano-dcon-xdsp-reqs-06 for the details) and
then even<br>

<dd>&gt; devised<br>

<dd>&gt; &gt;&gt; a BFCP-XMPP gateway for such a purpose. With respect to
the NAT<br>

<dd>&gt; &gt;&gt; traversal issue, we also implemented an HTTP
encapsulation. Moving<br>

<dd>&gt; &gt;&gt; further we even conceived a DTMF-based frontend to BFCP
;) and also<br>

<dd>&gt; &gt;&gt; almost thought about a BFCP-over-RTP approach.<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt; That said, I nevertheless agree with Keith on the
discussion. Those<br>

<dd>&gt; &gt;&gt; problems may be common to other TCP-based protocols as
well, and as<br>

<dd>&gt; such<br>

<dd>&gt; &gt;&gt; a generic solution (generic TCP over UDP, for instance,
or anything<br>

<dd>&gt; &gt;&gt; else) may be a much better approach than doing a
protocol specific<br>

<dd>&gt; &gt;&gt; patch. Besides, whatever the solution, it should also
take care of<br>

<dd>&gt; how<br>

<dd>&gt; &gt;&gt; the negotiation of such channels would be affected (as
is the<br>

<dd>&gt; &gt;&gt; case of RFC4583 for BFCP, which the proposed draft
actually does).<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt; As Keith already suggested, DISPATCH may be a much
better place to<br>

<dd>&gt; &gt;&gt; discuss this issue: DISPATCH is where we'll also
propose the above<br>

<dd>&gt; &gt;&gt; mentioned DCON work.<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt; Lorenzo<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt; On Thu, 10 Jun 2010 08:22:55 +0300<br>

<dd>&gt; &gt;&gt; &quot;Roni Even&quot;
&lt;<a href="mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>
&gt; wrote:<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt; Hi&nbsp; Keith,<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt; I think that the IETF is trying to design protocols
that will work<br>

<dd>&gt; over<br>

<dd>&gt; &gt;&gt;&gt; the<br>

<dd>&gt; &gt;&gt;&gt; Internet and also to enable interoperability
between independent<br>

<dd>&gt; &gt;&gt;&gt; implementations.<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt; In the BFCP case the shipping implementations
support TCP as the<br>

<dd>&gt; &gt;&gt;&gt; transport<br>

<dd>&gt; &gt;&gt;&gt; protocol but they encountered issues when running
over the Internet<br>

<dd>&gt; due<br>

<dd>&gt; &gt;&gt;&gt; to<br>

<dd>&gt; &gt;&gt;&gt; devices like SBCs and due to lack of support for
TCP media relay or<br>

<dd>&gt; &gt;&gt;&gt; ICE-TCP<br>

<dd>&gt; &gt;&gt;&gt; [I-D.ietf-mmusic-ice-tcp].<br>

<dd>&gt; &gt;&gt;&gt; When implementations looked at how to address the
issue, the<br>

<dd>&gt; &gt;&gt;&gt; interoperability went away since there is no fall
back solution for<br>

<dd>&gt; this<br>

<dd>&gt; &gt;&gt;&gt; real life case. Some did a fall back to HTTP and
some did to UDP<br>

<dd>&gt; but not<br>

<dd>&gt; &gt;&gt;&gt; in<br>

<dd>&gt; &gt;&gt;&gt; an interoperable way.<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt; In order to achieve interoperability, this draft is
trying to<br>

<dd>&gt; extend the<br>

<dd>&gt; &gt;&gt;&gt; current BFCP. It is not suggesting to replace TCP
but to keep TCP<br>

<dd>&gt; as the<br>

<dd>&gt; &gt;&gt;&gt; mandatory transport and use UDP as fallback if
unable to establish<br>

<dd>&gt; TCP<br>

<dd>&gt; &gt;&gt;&gt; connection.<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt; As for security, if the topic will be adopted the
solution will be<br>

<dd>&gt; &gt;&gt;&gt; updated<br>

<dd>&gt; &gt;&gt;&gt; to use DTLS as the transport for BFCP.<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt; I hope that people will read the draft and look at
the objectives<br>

<dd>&gt; and the<br>

<dd>&gt; &gt;&gt;&gt; proposed solution.<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt; BTW: This is a problem for client to client media
connections over<br>

<dd>&gt; TCP<br>

<dd>&gt; &gt;&gt;&gt; and<br>

<dd>&gt; &gt;&gt;&gt; my understanding is that RTSP offers to use both
TCP and UDP since<br>

<dd>&gt; both<br>

<dd>&gt; &gt;&gt;&gt; are<br>

<dd>&gt; &gt;&gt;&gt; specified. Since BFCP is not a payload but is
running in parallel<br>

<dd>&gt; to the<br>

<dd>&gt; &gt;&gt;&gt; RTP<br>

<dd>&gt; &gt;&gt;&gt; payload (for the point to point calls or MCU based
multipoint) it<br>

<dd>&gt; needs<br>

<dd>&gt; &gt;&gt;&gt; similar transport options.<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt; Thanks<br>

<dd>&gt; &gt;&gt;&gt; Roni Even<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt; -----Original Message-----<br>

<dd>&gt; &gt;&gt;&gt;&gt; From: DRAGE, Keith (Keith)
[<a href="mailto:keith.drage@alcatel-lucent.com" eudora="autourl">
mailto:keith.drage@alcatel-lucent.com</a>]<br>

<dd>&gt; &gt;&gt;&gt;&gt; Sent: Thursday, June 10, 2010 1:54 AM<br>

<dd>&gt; &gt;&gt;&gt;&gt; To: Roni Even; 'Richard L. Barnes'; 'Tom
Kristensen'<br>

<dd>&gt; &gt;&gt;&gt;&gt; Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom
Kristensen';<br>

<dd>&gt; <a href="mailto:xcon@ietf.org">xcon@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt; Subject: RE: [XCON] WG Adoption?
draft-sandbakken-xcon-bfcp-udp-02<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt; What you are essentially saying is that all
protocols in the<br>

<dd>&gt; future<br>

<dd>&gt; &gt;&gt;&gt;&gt; that need reliable transport, as BFCP does,
have to design in<br>

<dd>&gt; their own<br>

<dd>&gt; &gt;&gt;&gt;&gt; reliable transport element so they can use UDP.
This is not a BFCP<br>

<dd>&gt; &gt;&gt;&gt;&gt; specific issue.<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt; I find that an unacceptable direction for IETF
to be heading in.<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt; I would also note that you are also asking for
adoption of a<br>

<dd>&gt; document<br>

<dd>&gt; &gt;&gt;&gt;&gt; that cannot in its current form meet the
security requirements of<br>

<dd>&gt; the<br>

<dd>&gt; &gt;&gt;&gt;&gt; original RFC.<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt; regards<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt; Keith<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; From: Roni Even
[<a href="mailto:ron.even.tlv@gmail.com" eudora="autourl">
mailto:ron.even.tlv@gmail.com</a>]<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; Sent: Wednesday, June 09, 2010 1:40 PM<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; To: 'Richard L. Barnes'; 'Tom
Kristensen'<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; Cc: 'Mark Thompson'; DRAGE, Keith (Keith);
'Alan Johnston';<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; 'Tom Kristensen';
<a href="mailto:xcon@ietf.org">xcon@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; Subject: RE: [XCON] WG Adoption?
draft-sandbakken-xcon-bfcp-udp-<br>

<dd>&gt; 02<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; Richard,<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; The BFCP I used as a presentation token for
video<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; conferencing. What the implementers found
out that TCP does<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; not work in real networks due to Session
border controllers<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; not supporting TCP as used in BFCP.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; This is why in products they try to
establish TCP connection<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; and if fails tries UDP.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; The video conferencing vendors
participating in the IMTC sip<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; parity activity group defined an
interoperability profile<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; that references this option Roni Even<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; From:
<a href="mailto:xcon-bounces@ietf.org">xcon-bounces@ietf.org</a>
[<a href="mailto:xcon-bounces@ietf.org" eudora="autourl">
mailto:xcon-bounces@ietf.org</a>]<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; On Behalf<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; Of Richard L. Barnes<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; Sent: Wednesday, June 09, 2010 3:34
PM<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; To: Tom Kristensen<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; Cc: Mark Thompson; DRAGE, Keith
(Keith); Alan Johnston; Tom<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; Kristensen;
<a href="mailto:xcon@ietf.org">xcon@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [XCON] WG Adoption?
draft-sandbakken-xcon-bfcp-udp-<br>

<dd>&gt; 02<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; Tom and others who are interested in
this draft:<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; For those who are relatively new here:
Could you summarize why<br>

<dd>&gt; you<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; think this draft is needed?&nbsp; What
requirement does it meet<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; that BFCP<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; doesn't right now?<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; --Richard<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; On Jun 9, 2010, at 7:37 AM, Tom
Kristensen wrote:<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The UDP/BFCP draft has been
presented and discussed in<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; two or three<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; IETF XCON sessions. No objection to
the work being<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; carried on, just<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; that adoption as WG item was
postponed until the draft was more<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; complete. (This has been delayed of
various reasons, but<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; the authors<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; believe the -02 version in question
here should be ready for<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; adoption).<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The &quot;current status of
consensus&quot; might be valid for some, but<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; participants in the XCON sessions
and the minutes of meeting<br>

<dd>&gt; show<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; progress away from that initial
consensus.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; I believe Ott's concerns are either
dealt with or at<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; least mentioned<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; in the draft. Arrest me if I'm
wrong.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; -- Tom<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; On 9 June 2010 13:20, DRAGE, Keith
(Keith)<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;
&lt;<a href="mailto:keith.drage@alcatel-lucent.com">
keith.drage@alcatel-lucent.com</a>&gt; wrote:<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We made an explicit decision in
the original draft that<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; UDP was not<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; required, not that we would do
it later. That as far as I am<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; concerned represents the
current status of consensus.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; This was done on the basis that
we had all seen how UDP<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; support had<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; complicated SIP, and we did not
want to repeat that issue.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; So this is not continuing the
work. The status is an<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; author draft<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; which goes against a WG
consensus position.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I believe Georg Ott also
expressed some concerns which I did<br>

<dd>&gt; not<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; see answered on list at
all.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; regards<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Keith<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original
Message-----<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From:
<a href="mailto:xcon-bounces@ietf.org">xcon-bounces@ietf.org</a>
[<a href="mailto:xcon-bounces@ietf.org" eudora="autourl">
mailto:xcon-bounces@ietf.org</a>] On<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Behalf Of Roni Even<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, June 08,
2010 7:35 PM<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: 'Alan Johnston'; 'Tom
Kristensen'<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: 'Mark Thompson';
<a href="mailto:xcon@ietf.org">xcon@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [XCON] WG
Adoption?<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; draft-sandbakken-xcon-bfcp-udp-02<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Alan,<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I support this work and
think it is urgent to finish it.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I think that updating BFCP
with UDP support is very<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; important. I<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; would like to mention that
BFCP is being used in video<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; conferencing application
and since the implementers<br>

<dd>&gt; encountered<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; problems with TCP they use
a fall back to UDP.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We discussed this work in
previous IETF meeting and<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; Gonzalo as far<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; as I remember suggested to
add it to a BFCP bis draft.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Roni Even<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original
Message-----<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From:
<a href="mailto:xcon-bounces@ietf.org">xcon-bounces@ietf.org</a>
[<a href="mailto:xcon-bounces@ietf.org" eudora="autourl">
mailto:xcon-bounces@ietf.org</a>]<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Behalf<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Of Alan Johnston<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, June 08,
2010 7:44 PM<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Tom Kristensen<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: Mark Thompson;
<a href="mailto:xcon@ietf.org">xcon@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [XCON] WG
Adoption?<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
draft-sandbakken-xcon-bfcp-udp-02<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tom,<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Apologies for the delay
in replying.&nbsp; As you know, the<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; working group<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; is in the process of
completing its final milestones.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Publication requests
will be issued in the next few<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; days for the<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; data<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; model, CCMP,<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; and the Examples
drafts.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Taking on any new
milestones for the working group<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; would require:<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. Strong support and
interest from working group<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; participants 2.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Approval of our
ADs.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I haven't seen evidence
of either of these at this stage.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; A possible option is to
take this work to DISPATCH, get an<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; indication<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; of interests, and get
feedback on the best way to move<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; this work<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; forward.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; - Alan -<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; co-chair XCON<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On 6/7/10 8:22 AM, Tom
Kristensen wrote:<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; The draft
draft-sandbakken-xcon-bfcp-udp-02 was submitted<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; early in<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; March. No comments
received since.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We'd like guidance
on the next steps. First we ask for<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; adoption as<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; WG item. Next step
would include the merging process with<br>

<dd>&gt; bis<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; versions<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; of<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; RFC 4582 and RFC
4583.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We'd like to point
out that interested parties for this<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; work indeed<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exist.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; (For the record:
Questions was sent to XCON chairs in<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; April and May.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; See<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; below. No response
given. Therefore, this request on<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; the list.)<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -- Tom<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Wed, 2010-05-12
at 10:43 +0200, Tom Kristensen wrote:<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Chairs,<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Any thoughts or
decision on this matter?<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cheers,<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -- Tom<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Tue,
2010-04-20 at 11:58 +0200, Tom Kristensen wrote:<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON
chairs,<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; We
submitted draft-sandbakken-xcon-bfcp-udp-02<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; early in March<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; well in<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; advance of
IETF-77.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp;
<a href="http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-">
http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt; udp<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; No comments
received. Neither on XCON WG list, nor<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; directly to the<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; authors.
Therefore, we ask for adoption of this draft<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; as an XCON<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; WG
item.<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -- Tom<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
_______________________________________________<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
<a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
_______________________________________________<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
<a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
_______________________________________________<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
<a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; --<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; # TANDBERG R&amp;D<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; ##
<a href="http://www.tandberg.com">http://www.tandberg.com</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; ###
<a href="http://folk.uio.no/tomkri/" eudora="autourl">
http://folk.uio.no/tomkri/</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;
_______________________________________________<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;
<a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;
_______________________________________________<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt; XCON mailing list<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;
<a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;&gt;
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;&gt;&gt; =<br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;&gt;
_______________________________________________<br>

<dd>&gt; &gt;&gt;&gt; XCON mailing list<br>

<dd>&gt; &gt;&gt;&gt;
<a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd>&gt; &gt;&gt;&gt;
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br>

<dd>&gt; &gt;&gt;&gt;<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt;<br>

<dd>&gt; &gt;&gt; --<br>

<dd>&gt; &gt;&gt; Lorenzo Miniero<br>

<dd>&gt; &gt;&gt; Meetecho s.r.l.<br>

<dd>&gt; &gt;&gt;
<a href="http://www.meetecho.com/">http://www.meetecho.com/</a><br>

<dd>&gt; &gt;<br>

<dd>&gt; &gt; _______________________________________________<br>

<dd>&gt; &gt; XCON mailing list<br>

<dd>&gt; &gt; <a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd>&gt; &gt;
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br>

<dd>&gt; &gt;<br>

<dd>&gt; _______________________________________________<br>

<dd>&gt; XCON mailing list<br>

<dd>&gt; <a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd>&gt;
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br><br>

<dd>_______________________________________________<br>

<dd>XCON mailing list<br>

<dd><a href="mailto:XCON@ietf.org">XCON@ietf.org</a><br>

<dd><a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a><br><br>

</dl><br>
_______________________________________________<br>
XCON mailing list<br>
XCON@ietf.org<br>
<a href="https://www.ietf.org/mailman/listinfo/xcon" eudora="autourl">
https://www.ietf.org/mailman/listinfo/xcon</a></blockquote></body>
</html>

--=====================_115125953==.ALT--



From alex@vidyo.com  Mon Jun 28 08:30:17 2010
Return-Path: <alex@vidyo.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 499283A6A3E for <xcon@core3.amsl.com>; Mon, 28 Jun 2010 08:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level: 
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_50=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7UYGFngMMJZF for <xcon@core3.amsl.com>; Mon, 28 Jun 2010 08:30:03 -0700 (PDT)
Received: from mx1.myoutlookonline.com (mx1.myoutlookonline.com [64.95.72.238]) by core3.amsl.com (Postfix) with ESMTP id ED1813A6919 for <xcon@ietf.org>; Mon, 28 Jun 2010 08:30:02 -0700 (PDT)
Received: from BH018.mail.lan ([10.110.21.118]) by mx1.myoutlookonline.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 28 Jun 2010 11:30:12 -0400
Received: from HUB028.mail.lan ([10.110.17.28]) by BH018.mail.lan with Microsoft SMTPSVC(6.0.3790.3959); Mon, 28 Jun 2010 11:29:54 -0400
Received: from BE235.mail.lan ([10.110.32.235]) by HUB028.mail.lan ([10.110.17.28]) with mapi; Mon, 28 Jun 2010 11:29:54 -0400
From: Alex Eleftheriadis <alex@vidyo.com>
To: "Allyn Romanow (allyn)" <allyn@cisco.com>
Date: Mon, 28 Jun 2010 11:30:06 -0400
Thread-Topic: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
Thread-Index: AcsW1rk6S37A9XnQRISrXoyoX2DGLg==
Message-ID: <EACA7149-8206-4EAB-9220-EBC5F253C437@vidyo.com>
References: <1271757479.26184.8.camel@localhost><1273653780.2694.11.camel@localhost><1275916958.17477.9.camel@localhost> <4C0E7332.6080402@gmail.com><4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com><EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com><59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com><4c0f8c0f.9becd80a.55da.0fe2@mx.google.com><EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com><4c107733.df0ce30a.21ca.15cc@mx.google.com><20100610130009.1f1fbb03.lorenzo@meetecho.com><0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com> <AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com> <9AC2C4348FD86B4BB1F8FA9C5E3A5EDC01AE3EB5@xmb-sjc-221.amer.cisco.com>
In-Reply-To: <9AC2C4348FD86B4BB1F8FA9C5E3A5EDC01AE3EB5@xmb-sjc-221.amer.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-OriginalArrivalTime: 28 Jun 2010 15:29:54.0887 (UTC) FILETIME=[C24D9D70:01CB16D6]
Cc: Mark Thompson <mark.thompson@tandberg.com>, Alan Johnston <alan.b.johnston@gmail.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "xcon@ietf.org" <xcon@ietf.org>, Tom Kristensen <tom.kristensen@tandberg.com>
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jun 2010 15:30:17 -0000

+1.

--
Alex Eleftheriadis
alex@vidyo.com

On Jun 24, 2010, at 9:29 PM, Allyn Romanow (allyn) wrote:

> Although a general solution for TCP based media would be a very good thin=
g to be worked on, we also are in the position of needing an immediate solu=
tion, and BFCP over UDP fills that bill. So, I'm also in favor of working f=
urther on the draft and moving forward with it, in whichever venue people f=
ind convenient.
>
> Allyn
>
> -----Original Message-----
> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of M=
ary Barnes
> Sent: Wednesday, June 23, 2010 9:26 AM
> To: Richard L. Barnes
> Cc: Tom Kristensen; DRAGE,Keith (Keith); xcon@ietf.org; Mark Thompson; Al=
an Johnston
> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>
> I have reviewed the draft in question and while I agree that this
> could be viewed as a workaround for some more general problems that
> need to be solved, there is a current industry need for the solution
> in this draft.   If the general problems described go to DISPATCH
> (which is the appropriate thing to do rather than bringing this
> specific document), the timeframe for getting agreement on the problem
> to be solved and for the solutions to be agreed would be far longer
> IMHO than if this document were progressed. If XCON would prefer to
> close the WG without progressing this document (in this form or as a
> -bis to RFC  4582), my suggestion would be to do as was done for the
> remaining SIP and SIPPING documents and progress this item as an
> individual AD sponsored.
>
> Mary.
>
> On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes <rbarnes@bbn.com> wrot=
e:
>> <hat type=3D"individual"/>
>>
>> I tend to agree with Lorenzo that DISPATCH would be a better place to ha=
ve
>> these discussions, especially given that, as far as I can tell from this
>> thread, the problem seems to be a general one of NAT traversal for TCP.
>>
>>
>>
>> On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
>>
>>> Hi all,
>>>
>>> with respect to this topic, I think there are many issues implementers
>>> have to face when bringing IETF solutions to the real world. We found
>>> ourselves many times in a situation in which some kind of work-around
>>> had to be devised in order to let things work properly. Just to cite a
>>> couple of examples, with BFCP we had to find a way to let it work in a
>>> distributed conferencing scenario (which is far from easy, given the
>>> intrinsic centralized model behind such protocol). In such case, we
>>> decided to encapsulate BFCP messages in the body of XMPP
>>> server-to-server packets (see the XCON-DCON Synchronization Protocol in
>>> draft-romano-dcon-xdsp-reqs-06 for the details) and then even devised
>>> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
>>> traversal issue, we also implemented an HTTP encapsulation. Moving
>>> further we even conceived a DTMF-based frontend to BFCP ;) and also
>>> almost thought about a BFCP-over-RTP approach.
>>>
>>> That said, I nevertheless agree with Keith on the discussion. Those
>>> problems may be common to other TCP-based protocols as well, and as suc=
h
>>> a generic solution (generic TCP over UDP, for instance, or anything
>>> else) may be a much better approach than doing a protocol specific
>>> patch. Besides, whatever the solution, it should also take care of how
>>> the negotiation of such channels would be affected (as is the
>>> case of RFC4583 for BFCP, which the proposed draft actually does).
>>>
>>> As Keith already suggested, DISPATCH may be a much better place to
>>> discuss this issue: DISPATCH is where we'll also propose the above
>>> mentioned DCON work.
>>>
>>> Lorenzo
>>>
>>>
>>>
>>> On Thu, 10 Jun 2010 08:22:55 +0300
>>> "Roni Even" <ron.even.tlv@gmail.com> wrote:
>>>
>>>> Hi  Keith,
>>>>
>>>> I think that the IETF is trying to design protocols that will work ove=
r
>>>> the
>>>> Internet and also to enable interoperability between independent
>>>> implementations.
>>>>
>>>> In the BFCP case the shipping implementations support TCP as the
>>>> transport
>>>> protocol but they encountered issues when running over the Internet du=
e
>>>> to
>>>> devices like SBCs and due to lack of support for TCP media relay or
>>>> ICE-TCP
>>>> [I-D.ietf-mmusic-ice-tcp].
>>>> When implementations looked at how to address the issue, the
>>>> interoperability went away since there is no fall back solution for th=
is
>>>> real life case. Some did a fall back to HTTP and some did to UDP but n=
ot
>>>> in
>>>> an interoperable way.
>>>>
>>>> In order to achieve interoperability, this draft is trying to extend t=
he
>>>> current BFCP. It is not suggesting to replace TCP but to keep TCP as t=
he
>>>> mandatory transport and use UDP as fallback if unable to establish TCP
>>>> connection.
>>>>
>>>> As for security, if the topic will be adopted the solution will be
>>>> updated
>>>> to use DTLS as the transport for BFCP.
>>>>
>>>> I hope that people will read the draft and look at the objectives and =
the
>>>> proposed solution.
>>>>
>>>>
>>>> BTW: This is a problem for client to client media connections over TCP
>>>> and
>>>> my understanding is that RTSP offers to use both TCP and UDP since bot=
h
>>>> are
>>>> specified. Since BFCP is not a payload but is running in parallel to t=
he
>>>> RTP
>>>> payload (for the point to point calls or MCU based multipoint) it need=
s
>>>> similar transport options.
>>>>
>>>> Thanks
>>>> Roni Even
>>>>
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
>>>>> Sent: Thursday, June 10, 2010 1:54 AM
>>>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
>>>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen'; xcon@ietf.org
>>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>>
>>>>> What you are essentially saying is that all protocols in the future
>>>>> that need reliable transport, as BFCP does, have to design in their o=
wn
>>>>> reliable transport element so they can use UDP. This is not a BFCP
>>>>> specific issue.
>>>>>
>>>>> I find that an unacceptable direction for IETF to be heading in.
>>>>>
>>>>> I would also note that you are also asking for adoption of a document
>>>>> that cannot in its current form meet the security requirements of the
>>>>> original RFC.
>>>>>
>>>>> regards
>>>>>
>>>>> Keith
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>>>>> Sent: Wednesday, June 09, 2010 1:40 PM
>>>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
>>>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
>>>>>> 'Tom Kristensen'; xcon@ietf.org
>>>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>>>
>>>>>> Richard,
>>>>>> The BFCP I used as a presentation token for video
>>>>>> conferencing. What the implementers found out that TCP does
>>>>>> not work in real networks due to Session border controllers
>>>>>> not supporting TCP as used in BFCP.
>>>>>> This is why in products they try to establish TCP connection
>>>>>> and if fails tries UDP.
>>>>>> The video conferencing vendors participating in the IMTC sip
>>>>>> parity activity group defined an interoperability profile
>>>>>> that references this option Roni Even
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>>
>>>>>> On Behalf
>>>>>>>
>>>>>>> Of Richard L. Barnes
>>>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
>>>>>>> To: Tom Kristensen
>>>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
>>>>>>> Kristensen; xcon@ietf.org
>>>>>>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>
>>>>>>> Tom and others who are interested in this draft:
>>>>>>>
>>>>>>> For those who are relatively new here: Could you summarize why you
>>>>>>> think this draft is needed?  What requirement does it meet
>>>>>>
>>>>>> that BFCP
>>>>>>>
>>>>>>> doesn't right now?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> --Richard
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
>>>>>>>
>>>>>>>> The UDP/BFCP draft has been presented and discussed in
>>>>>>
>>>>>> two or three
>>>>>>>>
>>>>>>>> IETF XCON sessions. No objection to the work being
>>>>>>
>>>>>> carried on, just
>>>>>>>>
>>>>>>>> that adoption as WG item was postponed until the draft was more
>>>>>>>> complete. (This has been delayed of various reasons, but
>>>>>>
>>>>>> the authors
>>>>>>>>
>>>>>>>> believe the -02 version in question here should be ready for
>>>>>>>> adoption).
>>>>>>>>
>>>>>>>> The "current status of consensus" might be valid for some, but
>>>>>>>> participants in the XCON sessions and the minutes of meeting show
>>>>>>>> progress away from that initial consensus.
>>>>>>>>
>>>>>>>> I believe Ott's concerns are either dealt with or at
>>>>>>
>>>>>> least mentioned
>>>>>>>>
>>>>>>>> in the draft. Arrest me if I'm wrong.
>>>>>>>>
>>>>>>>> -- Tom
>>>>>>>>
>>>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
>>>>>>>> <keith.drage@alcatel-lucent.com> wrote:
>>>>>>>>>
>>>>>>>>> We made an explicit decision in the original draft that
>>>>>>
>>>>>> UDP was not
>>>>>>>>>
>>>>>>>>> required, not that we would do it later. That as far as I am
>>>>>>>>> concerned represents the current status of consensus.
>>>>>>>>>
>>>>>>>>> This was done on the basis that we had all seen how UDP
>>>>>>
>>>>>> support had
>>>>>>>>>
>>>>>>>>> complicated SIP, and we did not want to repeat that issue.
>>>>>>>>>
>>>>>>>>> So this is not continuing the work. The status is an
>>>>>>
>>>>>> author draft
>>>>>>>>>
>>>>>>>>> which goes against a WG consensus position.
>>>>>>>>>
>>>>>>>>> I believe Georg Ott also expressed some concerns which I did not
>>>>>>>>> see answered on list at all.
>>>>>>>>>
>>>>>>>>> regards
>>>>>>>>>
>>>>>>>>> Keith
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
>>>>>>>>>> Behalf Of Roni Even
>>>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
>>>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
>>>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
>>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>>
>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>>
>>>>>>>>>> Hi Alan,
>>>>>>>>>> I support this work and think it is urgent to finish it.
>>>>>>>>>> I think that updating BFCP with UDP support is very
>>>>>>
>>>>>> important. I
>>>>>>>>>>
>>>>>>>>>> would like to mention that BFCP is being used in video
>>>>>>>>>> conferencing application and since the implementers encountered
>>>>>>>>>> problems with TCP they use a fall back to UDP.
>>>>>>>>>> We discussed this work in previous IETF meeting and
>>>>>>
>>>>>> Gonzalo as far
>>>>>>>>>>
>>>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>> Roni Even
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>>>>>>
>>>>>>>>>> On Behalf
>>>>>>>>>>>
>>>>>>>>>>> Of Alan Johnston
>>>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>>>>>>>>>>> To: Tom Kristensen
>>>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
>>>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>>>
>>>>>>>>>>> Tom,
>>>>>>>>>>>
>>>>>>>>>>> Apologies for the delay in replying.  As you know, the
>>>>>>>>>>
>>>>>>>>>> working group
>>>>>>>>>>>
>>>>>>>>>>> is in the process of completing its final milestones.
>>>>>>>>>>> Publication requests will be issued in the next few
>>>>>>
>>>>>> days for the
>>>>>>>>>>>
>>>>>>>>>>> data
>>>>>>>>>>
>>>>>>>>>> model, CCMP,
>>>>>>>>>>>
>>>>>>>>>>> and the Examples drafts.
>>>>>>>>>>>
>>>>>>>>>>> Taking on any new milestones for the working group
>>>>>>
>>>>>> would require:
>>>>>>>>>>>
>>>>>>>>>>> 1. Strong support and interest from working group
>>>>>>
>>>>>> participants 2.
>>>>>>>>>>>
>>>>>>>>>>> Approval of our ADs.
>>>>>>>>>>>
>>>>>>>>>>> I haven't seen evidence of either of these at this stage.
>>>>>>>>>>>
>>>>>>>>>>> A possible option is to take this work to DISPATCH, get an
>>>>>>>>>>
>>>>>>>>>> indication
>>>>>>>>>>>
>>>>>>>>>>> of interests, and get feedback on the best way to move
>>>>>>
>>>>>> this work
>>>>>>>>>>>
>>>>>>>>>>> forward.
>>>>>>>>>>>
>>>>>>>>>>> - Alan -
>>>>>>>>>>> co-chair XCON
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>>>>>>>>>>
>>>>>>>>>> early in
>>>>>>>>>>>>
>>>>>>>>>>>> March. No comments received since.
>>>>>>>>>>>>
>>>>>>>>>>>> We'd like guidance on the next steps. First we ask for
>>>>>>>>>>
>>>>>>>>>> adoption as
>>>>>>>>>>>>
>>>>>>>>>>>> WG item. Next step would include the merging process with bis
>>>>>>>>>>>> versions
>>>>>>>>>>>
>>>>>>>>>>> of
>>>>>>>>>>>>
>>>>>>>>>>>> RFC 4582 and RFC 4583.
>>>>>>>>>>>>
>>>>>>>>>>>> We'd like to point out that interested parties for this
>>>>>>>>>>
>>>>>>>>>> work indeed
>>>>>>>>>>>>
>>>>>>>>>>>> exist.
>>>>>>>>>>>>
>>>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
>>>>>>>>>>
>>>>>>>>>> April and May.
>>>>>>>>>>>
>>>>>>>>>>> See
>>>>>>>>>>>>
>>>>>>>>>>>> below. No response given. Therefore, this request on
>>>>>>
>>>>>> the list.)
>>>>>>>>>>>>
>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Chairs,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Any thoughts or decision on this matter?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> XCON chairs,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
>>>>>>
>>>>>> early in March
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -
>>>>>>>>>>>
>>>>>>>>>>> well in
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> advance of IETF-77.
>>>>>>>>>>>>>> http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
>>>>>
>>>>> udp
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
>>>>>>>>>>
>>>>>>>>>> directly to the
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
>>>>>>>>>>
>>>>>>>>>> as an XCON
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> WG item.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> XCON mailing list
>>>>>>>>>>> XCON@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> XCON mailing list
>>>>>>>>>> XCON@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> XCON mailing list
>>>>>>>>> XCON@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> # TANDBERG R&D
>>>>>>>> ## http://www.tandberg.com
>>>>>>>> ### http://folk.uio.no/tomkri/
>>>>>>>> _______________________________________________
>>>>>>>> XCON mailing list
>>>>>>>> XCON@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> XCON mailing list
>>>>>>> XCON@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>
>>>>>> =3D
>>>>
>>>> _______________________________________________
>>>> XCON mailing list
>>>> XCON@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>
>>>
>>>
>>> --
>>> Lorenzo Miniero
>>> Meetecho s.r.l.
>>> http://www.meetecho.com/
>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>

