
From nobody Mon Sep  1 07:41:48 2014
Return-Path: <rohanse2@cisco.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB161A0681 for <clue@ietfa.amsl.com>; Mon,  1 Sep 2014 07:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.458
X-Spam-Level: 
X-Spam-Status: No, score=-12.458 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Te7-663BBQCO for <clue@ietfa.amsl.com>; Mon,  1 Sep 2014 07:41:43 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05B511A6FC4 for <clue@ietf.org>; Mon,  1 Sep 2014 07:18:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16181; q=dns/txt; s=iport; t=1409581112; x=1410790712; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=kra+hYB3tZU21GrJILNXrwzzON8Zw2MWgnldfeHS920=; b=B+udYHL3nF67VdrBBKd1Je8mJU/Vb0SE/O0NDmoiNKVWrs68K8ixN3Tc MRSAS41tllrg2IwkJZ7hgAR3BK8PnJazvGy4dMB+WLrClA0v3AfuXDzix 81Xh8ry0QO3d4T1/4jpHUnPfwNrL8297jPJ+NK03sFLuD5wqW3Wui0mUs s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApERAD5/BFStJssW/2dsb2JhbABZgkeBGVeCfIVbpj0BAQEBAQEFAW8Bl2kBCYdMAYEmd4QDAQEBBAEBASAKKBkKDwIJAhgJFgsCAgkDAgECAQkMMBMGAgEBiD4NiFucPZRgARcEhXiIbwoHASQnDIJ5gVMFhhSWSIc3jWeDYjwvgQYJF4EpAQEB
X-IronPort-AV: E=Sophos;i="5.04,442,1406592000";  d="scan'208,217";a="157167158"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 01 Sep 2014 14:18:30 +0000
Received: from [10.47.200.91] ([10.47.200.91]) (authenticated bits=0) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s81EISV1005649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <clue@ietf.org>; Mon, 1 Sep 2014 14:18:30 GMT
Message-ID: <54048034.6000708@cisco.com>
Date: Mon, 01 Sep 2014 15:18:28 +0100
From: Robert Hansen <rohanse2@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: clue@ietf.org
References: <E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com>
In-Reply-To: <E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------010900080300030603090907"
X-Authenticated-User: rohanse2
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/0IRaEGD4XskOEak4K0McVTSdKTE
Subject: Re: [clue] CLUE-enabled call's fallback
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 14:41:47 -0000

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

Hi Scarlett,

1) Section 4.5.2.3. and 4.5.4.1. address when and how to disable 
non-CLUE-controlled media. There isn't a huge amount of detail (I 
removed all normative language in section 4.5.2.3. as part of the most 
recent draft to make clear it was merely illustrative) but then I'm not 
sure this is something we should be mandating; different implementations 
will likely have different opinions on when non-CLUE-controlled media 
should be disabled (some may never want it, some may want to continue it 
until they have CLUE-controlled media).

2) Section 4.5.2.3. defines when a call falls back from CLUE-enabled to 
non-CLUE enabled, defining it as the first of the options you suggest.

Can you check these sections, and say which ones you think are 
insufficient/should be changed?

Thanks,

Rob

On 30/08/14 03:16, Liuyan (Scarlett) wrote:
>
> Hello,
>
>      I have some issues about CLUE-enabled call’s fallback.
>
>      The signaling draft says:
>
>             A call in which two CLUE-capable devices have successfully 
> negotiated support for a CLUE data channel in SDP.
>
> A CLUE-enabled call is not necessarily immediately able to send 
> CLUE-controlled media; negotiation of the data channel and of the CLUE 
> protocol must complete first
>
>          But the signaling does not say something as below:
>
> 1)When and how to stop the basic media streams?
>
> wait and until the two CLUE-capable device finish the negotiation and 
> use “a=inactive” or set the port number zero related to the basic 
> media streams
>
> 2)When and how to trigger a CLUE-enabled call fall back?
>
> the data channel is explicitly closed by SDP O/A ;
>
> the data channel is closed by SCTP SSN Reset (see the draft 
> draft-ietf-rtcweb-data-protocol-03) ;or
>
> the all CLUE-controlled media streams are removed by SDP O/A
>
>      That’s all and comments welcome.
>
> Best Regards,
>
> Scarlett
>
> ------------------------------------------------------------------------
>
>
> 华为技术有限 公司Huawei Technologies Co., Ltd.
>
>
> Phone: 0086-755-28974289
> Fax:
> Mobile:
> Email: scarlett.liuyan@huawei.com
> 地址：深圳市 龙岗区坂田华为基地 邮编：518129
> Huawei Technologies Co., Ltd.
> Bantian, Longgang District,Shenzhen 518129, P.R.China
> http://www.huawei.com
>
> ------------------------------------------------------------------------
>
> 本邮件及其附件含 有华为公司的保密信息，仅限于发送给上面地址中列出的个 
> 人或群组。禁
> 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散 
> 发）本邮件中
> 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> This e-mail and its attachments contain confidential information from 
> HUAWEI, which
> is intended only for the person or entity whose address is listed 
> above. Any use of the
> information contained herein in any way (including, but not limited 
> to, total or partial
> disclosure, reproduction, or dissemination) by persons other than the 
> intended
> recipient(s) is prohibited. If you receive this e-mail in error, 
> please notify the sender by
> phone or email immediately and delete it!
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


--------------010900080300030603090907
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Scarlett,<br>
    <br>
    1) Section 4.5.2.3. and 4.5.4.1. address when and how to disable
    non-CLUE-controlled media. There isn't a huge amount of detail (I
    removed all normative language in section 4.5.2.3. as part of the
    most recent draft to make clear it was merely illustrative) but then
    I'm not sure this is something we should be mandating; different
    implementations will likely have different opinions on when
    non-CLUE-controlled media should be disabled (some may never want
    it, some may want to continue it until they have CLUE-controlled
    media).<br>
    <br>
    2) Section 4.5.2.3. defines when a call falls back from CLUE-enabled
    to non-CLUE enabled, defining it as the first of the options you
    suggest.<br>
    <br>
    Can you check these sections, and say which ones you think are
    insufficient/should be changed?<br>
    <br>
    Thanks,<br>
    <br>
    Rob<br>
    <br>
    <div class="moz-cite-prefix">On 30/08/14 03:16, Liuyan (Scarlett)
      wrote:<br>
    </div>
    <blockquote
cite="mid:E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
	{font-family:宋体;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@宋体";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:华文细黑;
	panose-1:2 1 6 0 4 1 1 1 1 1;}
@font-face
	{font-family:"\@华文细黑";
	panose-1:2 1 6 0 4 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:21.0pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1069425288;
	mso-list-type:hybrid;
	mso-list-template-ids:1714863078 -1811914638 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:39.0pt;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span lang="EN-US">Hello,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">     I have some issues
            about CLUE-enabled call’s fallback.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">     The signaling draft
            says:<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">            A call in
            which two CLUE-capable devices have successfully negotiated
            support for a CLUE data channel in SDP.
            <o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-left:15.75pt;text-indent:26.25pt"><span
            lang="EN-US">A CLUE-enabled call is not necessarily
            immediately able to send CLUE-controlled media; negotiation
            of the data channel and of the CLUE protocol must complete
            first<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">         But the
            signaling does not say something as below:<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:39.0pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo1">
          <!--[if !supportLists]--><span lang="EN-US"><span
              style="mso-list:Ignore">1)<span style="font:7.0pt
                &quot;Times New Roman&quot;">      
              </span></span></span><!--[endif]--><span lang="EN-US">When
            and how to stop the basic media streams?<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-left:21.0pt;text-indent:18.0pt"><span
            lang="EN-US">wait and until the two CLUE-capable device
            finish the negotiation and use “a=inactive” or set the port
            number zero related to the basic media streams<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:39.0pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo1">
          <!--[if !supportLists]--><span lang="EN-US"><span
              style="mso-list:Ignore">2)<span style="font:7.0pt
                &quot;Times New Roman&quot;">      
              </span></span></span><!--[endif]--><span lang="EN-US">When
            and how to trigger a CLUE-enabled call fall back?<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-left:21.0pt;text-indent:18.0pt"><span
            lang="EN-US">the data channel is explicitly closed by SDP
            O/A ;<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-left:21.0pt;text-indent:18.0pt"><span
            lang="EN-US">the data channel is closed by SCTP SSN Reset
            (see the draft draft-ietf-rtcweb-data-protocol-03) ;or<o:p></o:p></span></p>
        <p class="MsoNormal"
          style="margin-left:21.0pt;text-indent:18.0pt"><span
            lang="EN-US">the all CLUE-controlled media streams are
            removed by SDP O/A<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">     That’s all and
            comments welcome.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Best Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Scarlett<o:p></o:p></span></p>
        <div class="MsoNormal" style="text-align:center" align="center"><span
            lang="EN-US">
            <hr align="center" size="2" width="100%">
          </span></div>
        <p class="MsoNormal"><span lang="EN-US"><br>
          </span><span
            style="font-size:10.0pt;font-family:华文细黑;color:black">华为技术有限
            公司<span lang="EN-US"> Huawei Technologies Co., Ltd.<br>
            </span></span><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">
<v:stroke joinstyle="miter" />
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0" />
<v:f eqn="sum @0 1 0" />
<v:f eqn="sum 0 0 @1" />
<v:f eqn="prod @2 1 2" />
<v:f eqn="prod @3 21600 pixelWidth" />
<v:f eqn="prod @3 21600 pixelHeight" />
<v:f eqn="sum @0 0 1" />
<v:f eqn="prod @6 1 2" />
<v:f eqn="prod @7 21600 pixelWidth" />
<v:f eqn="sum @8 21600 0" />
<v:f eqn="prod @7 21600 pixelHeight" />
<v:f eqn="sum @10 21600 0" />
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
<o:lock v:ext="edit" aspectratio="t" />
</v:shapetype><v:shape id="ridImg" o:spid="_x0000_s1026" type="#_x0000_t75" alt="Company_logo" style='position:absolute;left:0;text-align:left;margin-left:0;margin-top:0;width:24pt;height:24pt;z-index:1;visibility:visible;mso-wrap-style:square;mso-wrap-distance-left:0;mso-wrap-distance-top:0;mso-wrap-distance-right:0;mso-wrap-distance-bottom:0;mso-position-horizontal:left;mso-position-horizontal-relative:text;mso-position-vertical:absolute;mso-position-vertical-relative:line' o:allowoverlap="f">
<v:imagedata src="file:///C:\Users\Administrator\Application%20Data\Microsoft\Signatures\company_logo.jpg" />
<w:wrap type="square" anchory="line"/>
</v:shape><![endif]--><span
            style="font-size:10.0pt;font-family:华文细黑;color:black"
            lang="EN-US"><br>
            <br>
            Phone: 0086-755-28974289<br>
            Fax: <br>
            Mobile: <br>
            Email: <a class="moz-txt-link-abbreviated" href="mailto:scarlett.liuyan@huawei.com">scarlett.liuyan@huawei.com</a><br>
          </span><span
            style="font-size:10.0pt;font-family:华文细黑;color:black">地址：深圳市
            龙岗区坂田华为基地 邮编：<span lang="EN-US">518129<br>
              Huawei Technologies Co., Ltd.<br>
              Bantian, Longgang District,Shenzhen 518129, P.R.China<br>
              <a class="moz-txt-link-freetext" href="http://www.huawei.com">http://www.huawei.com</a></span></span><span lang="EN-US"> <o:p></o:p></span></p>
        <div class="MsoNormal" style="text-align:center" align="center"><span
            lang="EN-US">
            <hr align="center" size="2" width="100%">
          </span></div>
        <p class="MsoNormal"><span
            style="font-size:7.5pt;font-family:华文细黑;color:gray">本邮件及其附件含
            有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁<span lang="EN-US"><br>
            </span>止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中<span
              lang="EN-US"><br>
            </span>的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！<span lang="EN-US"><br>
            </span></span><span
style="font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray"
            lang="EN-US">This e-mail and its attachments contain
            confidential information from HUAWEI, which
            <br>
            is intended only for the person or entity whose address is
            listed above. Any use of the
            <br>
            information contained herein in any way (including, but not
            limited to, total or partial
            <br>
            disclosure, reproduction, or dissemination) by persons other
            than the intended <br>
            recipient(s) is prohibited. If you receive this e-mail in
            error, please notify the sender by
            <br>
            phone or email immediately and delete it!</span><span
            lang="EN-US"><o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
clue mailing list
<a class="moz-txt-link-abbreviated" href="mailto:clue@ietf.org">clue@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/clue">https://www.ietf.org/mailman/listinfo/clue</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010900080300030603090907--


From nobody Mon Sep  1 09:13:09 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8671A01F3 for <clue@ietfa.amsl.com>; Mon,  1 Sep 2014 09:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.775
X-Spam-Level: 
X-Spam-Status: No, score=0.775 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_18=0.6, SPF_SOFTFAIL=0.665, T_FILL_THIS_FORM_SHORT=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXqIpOAbuJY5 for <clue@ietfa.amsl.com>; Mon,  1 Sep 2014 09:13:05 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC371A02B9 for <clue@ietf.org>; Mon,  1 Sep 2014 09:13:04 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta02.westchester.pa.mail.comcast.net with comcast id lqgv1o0070SCNGk51sD4yu; Mon, 01 Sep 2014 16:13:04 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta09.westchester.pa.mail.comcast.net with comcast id lsD41o0053Ge9ey3VsD44E; Mon, 01 Sep 2014 16:13:04 +0000
Message-ID: <54049B10.8090607@alum.mit.edu>
Date: Mon, 01 Sep 2014 12:13:04 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com> <54048034.6000708@cisco.com>
In-Reply-To: <54048034.6000708@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1409587984; bh=xZ0VPYg3J67bfU22M/aKUBaO0rJSbK3OgkwJKEBWjvc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=DccG8EOZM7Dge/xDyJEKgjPkD6TsqT9q2cLEOsqeboJlDu0ph4R9gm7c0hSC8y790 FQEIykUbXluO2v7TnplcHxFUanAny4Qj1hzwBcmEOuGNgFOT7wpw0XPsxCvaXpxIqY SXAZte2WwYEXPQtJG6YnM7OTsc4H5aYb3LI6vtZzRppo4Phfam9yFv4kvO9V7qOdAV AG5rRILljo7kBK+THoPoOdQkg86zijXLAOlHrXz2hzj+jhv6PPkXArdI3MJCGIpiWq Z47dGNANDxjZlLz1jKgfcaGfz3gS6yRKRIF1yCuU1Q1RI7HOv9J4XYIi/o+Oq7sA6V zXUX7hoNwqTaA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/0yb5-hc6v-u1UL2pxcp_rwcL7IQ
Subject: Re: [clue] CLUE-enabled call's fallback
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 16:13:07 -0000

Rob, Scarlett,

There is one thing that I am concerned with:

I see an analogy between moving to/from clue-enabled status and moving 
to/from hold status. With hold, if you aren't careful it is possible to 
get into a "stuck on hold" status. Similarly, I think if we aren't 
careful it will be possible to get into a "stuck in clue-disabled" status.

The "stuck on hold" arises when both ends have put the call on hold 
a=inactive has been negotiated. It occurs if one end wants to go off 
hold, but continues to offer a=inactive because it thinks the other end 
wants to be on hold. It is fixed by a policy where each end makes no 
assumptions about what the other end wants in the future when it makes 
offers - offering what it wants for itself. And this needs to be true 
when responding to offerless invites too.

The question is whether we have such issues with clue-enablement.

Consider the following, between Alice and Bob:

- Alice calls Bob, offering CLUE support clue group containing sctp.
- Bob is clue-capable, but can't initially enable it.
   (E.g., cell phone on slow link.) So refuses the SCTP.

The question is what happens subsequently. If Alice has reason to send 
an offer in the future, should she again offer the clue channel? Or 
should she assume that it is up to Bob to take the initiative in 
enabling CLUE? (There may be a cost associated offering the clue 
channel, in ICE, DTLS, etc.)

The safest answer is to say that whenever a clue-capable endpoint sends 
an offer, and is willing/able to be clue-enabled, it should offer the 
SCTP m-line.

We could explore less aggressive approaches. But then we must look very 
carefully - the cases that cause trouble are often subtle, involving 
offerless invites, B2BUAs, etc.

	Thanks,
	Paul

On 9/1/14 10:18 AM, Robert Hansen wrote:
> Hi Scarlett,
>
> 1) Section 4.5.2.3. and 4.5.4.1. address when and how to disable
> non-CLUE-controlled media. There isn't a huge amount of detail (I
> removed all normative language in section 4.5.2.3. as part of the most
> recent draft to make clear it was merely illustrative) but then I'm not
> sure this is something we should be mandating; different implementations
> will likely have different opinions on when non-CLUE-controlled media
> should be disabled (some may never want it, some may want to continue it
> until they have CLUE-controlled media).
>
> 2) Section 4.5.2.3. defines when a call falls back from CLUE-enabled to
> non-CLUE enabled, defining it as the first of the options you suggest.
>
> Can you check these sections, and say which ones you think are
> insufficient/should be changed?
>
> Thanks,
>
> Rob
>
> On 30/08/14 03:16, Liuyan (Scarlett) wrote:
>>
>> Hello,
>>
>>      I have some issues about CLUE-enabled call’s fallback.
>>
>>      The signaling draft says:
>>
>>             A call in which two CLUE-capable devices have successfully
>> negotiated support for a CLUE data channel in SDP.
>>
>> A CLUE-enabled call is not necessarily immediately able to send
>> CLUE-controlled media; negotiation of the data channel and of the CLUE
>> protocol must complete first
>>
>>          But the signaling does not say something as below:
>>
>> 1)When and how to stop the basic media streams?
>>
>> wait and until the two CLUE-capable device finish the negotiation and
>> use “a=inactive” or set the port number zero related to the basic
>> media streams
>>
>> 2)When and how to trigger a CLUE-enabled call fall back?
>>
>> the data channel is explicitly closed by SDP O/A ;
>>
>> the data channel is closed by SCTP SSN Reset (see the draft
>> draft-ietf-rtcweb-data-protocol-03) ;or
>>
>> the all CLUE-controlled media streams are removed by SDP O/A
>>
>>      That’s all and comments welcome.
>>
>> Best Regards,
>>
>> Scarlett
>>
>> ------------------------------------------------------------------------
>>
>>
>> 华为技术有限 公司Huawei Technologies Co., Ltd.
>>
>>
>> Phone: 0086-755-28974289
>> Fax:
>> Mobile:
>> Email: scarlett.liuyan@huawei.com
>> 地址：深圳市 龙岗区坂田华为基地 邮编：518129
>> Huawei Technologies Co., Ltd.
>> Bantian, Longgang District,Shenzhen 518129, P.R.China
>> http://www.huawei.com
>>
>> ------------------------------------------------------------------------
>>
>> 本邮件及其附件含 有华为公司的保密信息，仅限于发送给上面地址中列出的个
>> 人或群组。禁
>> 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散
>> 发）本邮件中
>> 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
>> This e-mail and its attachments contain confidential information from
>> HUAWEI, which
>> is intended only for the person or entity whose address is listed
>> above. Any use of the
>> information contained herein in any way (including, but not limited
>> to, total or partial
>> disclosure, reproduction, or dissemination) by persons other than the
>> intended
>> recipient(s) is prohibited. If you receive this e-mail in error,
>> please notify the sender by
>> phone or email immediately and delete it!
>>
>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Mon Sep  1 10:13:18 2014
Return-Path: <rohanse2@cisco.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 653FA1A03DE for <clue@ietfa.amsl.com>; Mon,  1 Sep 2014 10:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.569
X-Spam-Level: 
X-Spam-Status: No, score=-14.569 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b9BPXeOOTslP for <clue@ietfa.amsl.com>; Mon,  1 Sep 2014 10:13:10 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EB761A0296 for <clue@ietf.org>; Mon,  1 Sep 2014 10:13:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6631; q=dns/txt; s=iport; t=1409591590; x=1410801190; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=3BRjf3eKgBnvi9uVQsCacAu4qGHVAxOtuoQ717AcFlQ=; b=YScGz53bZIhj+4X4topzRZn9ZqQh72626w55pVXDLSK/ipLHcUDPZUk7 yYvejfIVGUfBF0cXMfHnvoKowZeKblWzf9koE0s1ShU9KRPKepMlCCzxQ cMnYXR6jRXReq/dkpcewy5HaZZkoTM3tWXmJn5aFuC4nrJ47NriFa3IMd 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoYKAIuoBFStJssW/2dsb2JhbABZg2BXgnysGAEBBAUBbwGXaQqHTwGBLHeEBAEBBAEBASAPAQUdGRkCCQIYAgIFIQICDwIKDDATBgIBAYg+DYhFnD2UWgEXBIEohFCIbwoHAUsMgnmBUwWGFJZIhzeNZ4NiPC+BBgkXgSkBAQE
X-IronPort-AV: E=Sophos;i="5.04,443,1406592000"; d="scan'208";a="157324290"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 01 Sep 2014 17:13:07 +0000
Received: from [10.47.200.91] ([10.47.200.91]) (authenticated bits=0) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s81HD6NX024875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <clue@ietf.org>; Mon, 1 Sep 2014 17:13:07 GMT
Message-ID: <5404A922.70509@cisco.com>
Date: Mon, 01 Sep 2014 18:13:06 +0100
From: Robert Hansen <rohanse2@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: clue@ietf.org
References: <E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com> <54048034.6000708@cisco.com> <54049B10.8090607@alum.mit.edu>
In-Reply-To: <54049B10.8090607@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: rohanse2
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/vzBwSr4OqWoAcHuJxh57amE6rog
Subject: Re: [clue] CLUE-enabled call's fallback
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 17:13:13 -0000

Hi Paul,

I'm definitely of the opinion that those who are willing to upgrade a 
call to CLUE-enabled should include a data channel m-line, just like 
coming off hold with media. Section 4.5.4.2. has the following language:

"A CLUE-capable device that receives an initial SDP offer from a 
non-CLUE device SHOULD include a new data channel "m" line and 
corresponding CLUE group in any subsequent offers it sends, to indicate 
that it is CLUE-capable."

I suppose this should be expanded to also cover cases where the call was 
CLUE-enabled but then downgraded, as at the moment it only talks about 
calls that were non-CLUE from the beginning.

Rob

On 01/09/14 17:13, Paul Kyzivat wrote:
> Rob, Scarlett,
>
> There is one thing that I am concerned with:
>
> I see an analogy between moving to/from clue-enabled status and moving 
> to/from hold status. With hold, if you aren't careful it is possible 
> to get into a "stuck on hold" status. Similarly, I think if we aren't 
> careful it will be possible to get into a "stuck in clue-disabled" 
> status.
>
> The "stuck on hold" arises when both ends have put the call on hold 
> a=inactive has been negotiated. It occurs if one end wants to go off 
> hold, but continues to offer a=inactive because it thinks the other 
> end wants to be on hold. It is fixed by a policy where each end makes 
> no assumptions about what the other end wants in the future when it 
> makes offers - offering what it wants for itself. And this needs to be 
> true when responding to offerless invites too.
>
> The question is whether we have such issues with clue-enablement.
>
> Consider the following, between Alice and Bob:
>
> - Alice calls Bob, offering CLUE support clue group containing sctp.
> - Bob is clue-capable, but can't initially enable it.
>   (E.g., cell phone on slow link.) So refuses the SCTP.
>
> The question is what happens subsequently. If Alice has reason to send 
> an offer in the future, should she again offer the clue channel? Or 
> should she assume that it is up to Bob to take the initiative in 
> enabling CLUE? (There may be a cost associated offering the clue 
> channel, in ICE, DTLS, etc.)
>
> The safest answer is to say that whenever a clue-capable endpoint 
> sends an offer, and is willing/able to be clue-enabled, it should 
> offer the SCTP m-line.
>
> We could explore less aggressive approaches. But then we must look 
> very carefully - the cases that cause trouble are often subtle, 
> involving offerless invites, B2BUAs, etc.
>
>     Thanks,
>     Paul
>
> On 9/1/14 10:18 AM, Robert Hansen wrote:
>> Hi Scarlett,
>>
>> 1) Section 4.5.2.3. and 4.5.4.1. address when and how to disable
>> non-CLUE-controlled media. There isn't a huge amount of detail (I
>> removed all normative language in section 4.5.2.3. as part of the most
>> recent draft to make clear it was merely illustrative) but then I'm not
>> sure this is something we should be mandating; different implementations
>> will likely have different opinions on when non-CLUE-controlled media
>> should be disabled (some may never want it, some may want to continue it
>> until they have CLUE-controlled media).
>>
>> 2) Section 4.5.2.3. defines when a call falls back from CLUE-enabled to
>> non-CLUE enabled, defining it as the first of the options you suggest.
>>
>> Can you check these sections, and say which ones you think are
>> insufficient/should be changed?
>>
>> Thanks,
>>
>> Rob
>>
>> On 30/08/14 03:16, Liuyan (Scarlett) wrote:
>>>
>>> Hello,
>>>
>>>      I have some issues about CLUE-enabled call’s fallback.
>>>
>>>      The signaling draft says:
>>>
>>>             A call in which two CLUE-capable devices have successfully
>>> negotiated support for a CLUE data channel in SDP.
>>>
>>> A CLUE-enabled call is not necessarily immediately able to send
>>> CLUE-controlled media; negotiation of the data channel and of the CLUE
>>> protocol must complete first
>>>
>>>          But the signaling does not say something as below:
>>>
>>> 1)When and how to stop the basic media streams?
>>>
>>> wait and until the two CLUE-capable device finish the negotiation and
>>> use “a=inactive” or set the port number zero related to the basic
>>> media streams
>>>
>>> 2)When and how to trigger a CLUE-enabled call fall back?
>>>
>>> the data channel is explicitly closed by SDP O/A ;
>>>
>>> the data channel is closed by SCTP SSN Reset (see the draft
>>> draft-ietf-rtcweb-data-protocol-03) ;or
>>>
>>> the all CLUE-controlled media streams are removed by SDP O/A
>>>
>>>      That’s all and comments welcome.
>>>
>>> Best Regards,
>>>
>>> Scarlett
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>>
>>> 华为技术有限 公司Huawei Technologies Co., Ltd.
>>>
>>>
>>> Phone: 0086-755-28974289
>>> Fax:
>>> Mobile:
>>> Email: scarlett.liuyan@huawei.com
>>> 地址：深圳市 龙岗区坂田华为基地 邮编：518129
>>> Huawei Technologies Co., Ltd.
>>> Bantian, Longgang District,Shenzhen 518129, P.R.China
>>> http://www.huawei.com
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> 本邮件及其附件含 有华为公司的保密信息，仅限于发送给上面地址中列出的个
>>> 人或群组。禁
>>> 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散
>>> 发）本邮件中
>>> 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
>>> This e-mail and its attachments contain confidential information from
>>> HUAWEI, which
>>> is intended only for the person or entity whose address is listed
>>> above. Any use of the
>>> information contained herein in any way (including, but not limited
>>> to, total or partial
>>> disclosure, reproduction, or dissemination) by persons other than the
>>> intended
>>> recipient(s) is prohibited. If you receive this e-mail in error,
>>> please notify the sender by
>>> phone or email immediately and delete it!
>>>
>>>
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>
>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Thu Sep  4 00:03:56 2014
Return-Path: <scarlett.liuyan@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6D81A0B83 for <clue@ietfa.amsl.com>; Thu,  4 Sep 2014 00:03:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.868
X-Spam-Level: 
X-Spam-Status: No, score=-4.868 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zrbcSpfP-qgG for <clue@ietfa.amsl.com>; Thu,  4 Sep 2014 00:03:51 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0A581A0B7D for <clue@ietf.org>; Thu,  4 Sep 2014 00:03:50 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMD00809; Thu, 04 Sep 2014 07:03:48 +0000 (GMT)
Received: from SZXEMA405-HUB.china.huawei.com (10.82.72.37) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 4 Sep 2014 08:03:47 +0100
Received: from SZXEMA503-MBX.china.huawei.com ([169.254.5.91]) by SZXEMA405-HUB.china.huawei.com ([10.82.72.37]) with mapi id 14.03.0158.001; Thu, 4 Sep 2014 15:03:43 +0800
From: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>
To: Robert Hansen <rohanse2@cisco.com>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] CLUE-enabled call's fallback
Thread-Index: Ac/D+GittEPNbekRSra4ryOrQuay7ABtCKsAAJFYSuA=
Date: Thu, 4 Sep 2014 07:03:42 +0000
Message-ID: <E97C33E5D67C2843AFA535DE2E5B80C1573F1A66@SZXEMA503-MBX.china.huawei.com>
References: <E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com> <54048034.6000708@cisco.com>
In-Reply-To: <54048034.6000708@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.63.147.208]
Content-Type: multipart/alternative; boundary="_000_E97C33E5D67C2843AFA535DE2E5B80C1573F1A66SZXEMA503MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/pkXAl9KdKcI0gw_eCFzBcOl7epA
Subject: Re: [clue] CLUE-enabled call's fallback
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 07:03:54 -0000

--_000_E97C33E5D67C2843AFA535DE2E5B80C1573F1A66SZXEMA503MBXchi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUm9iZXJ0LA0KDQogICAgICAgICBJIGhhdmUgcmVhZCB0aGUgbGF0ZXN0IHZlcnNpb24gb2Yg
ZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZy4NCiAgICAgICAgIFBsZWFzZSBzZWUgbXkgcmVwbGll
cyBiZWxvdyBhbmQgdGhhbmtzLg0KDQpCZXN0IFJlZ2FyZHMsDQpTY2FybGV0dA0KRnJvbTogY2x1
ZSBbbWFpbHRvOmNsdWUtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFJvYmVydCBIYW5z
ZW4NClNlbnQ6IE1vbmRheSwgU2VwdGVtYmVyIDAxLCAyMDE0IDEwOjE4IFBNDQpUbzogY2x1ZUBp
ZXRmLm9yZw0KU3ViamVjdDogUmU6IFtjbHVlXSBDTFVFLWVuYWJsZWQgY2FsbCdzIGZhbGxiYWNr
DQoNCkhpIFNjYXJsZXR0LA0KDQoxKSBTZWN0aW9uIDQuNS4yLjMuIGFuZCA0LjUuNC4xLiBhZGRy
ZXNzIHdoZW4gYW5kIGhvdyB0byBkaXNhYmxlIG5vbi1DTFVFLWNvbnRyb2xsZWQgbWVkaWEuIFRo
ZXJlIGlzbid0IGEgaHVnZSBhbW91bnQgb2YgZGV0YWlsIChJIHJlbW92ZWQgYWxsIG5vcm1hdGl2
ZSBsYW5ndWFnZSBpbiBzZWN0aW9uIDQuNS4yLjMuIGFzIHBhcnQgb2YgdGhlIG1vc3QgcmVjZW50
IGRyYWZ0IHRvIG1ha2UgY2xlYXIgaXQgd2FzIG1lcmVseSBpbGx1c3RyYXRpdmUpIGJ1dCB0aGVu
IEknbSBub3Qgc3VyZSB0aGlzIGlzIHNvbWV0aGluZyB3ZSBzaG91bGQgYmUgbWFuZGF0aW5nOyBk
aWZmZXJlbnQgaW1wbGVtZW50YXRpb25zIHdpbGwgbGlrZWx5IGhhdmUgZGlmZmVyZW50IG9waW5p
b25zIG9uIHdoZW4gbm9uLUNMVUUtY29udHJvbGxlZCBtZWRpYSBzaG91bGQgYmUgZGlzYWJsZWQg
KHNvbWUgbWF5IG5ldmVyIHdhbnQgaXQsIHNvbWUgbWF5IHdhbnQgdG8gY29udGludWUgaXQgdW50
aWwgdGhleSBoYXZlIENMVUUtY29udHJvbGxlZCBtZWRpYSkuDQpbU2NhcmxldHRdIFRoZSBmb2xs
b3dpbmcgZGVzY3JpcHRpb24gYW5zd2VycyB0byB0aGUgcG9pbnQgKGkuZS4gd2hlbiBhbmQgaG93
IHRvIGRpc2FibGUgbm9uLUNMVUUtY29udHJvbGxlZCBtZWRpYSksIGVzcGVjaWFsbHkgdGhlIHll
bGxvdyBoaWdobGlnaHQgcGFydC4gU2V0dGluZyB0aGUgcG9ydCBudW1iZXIgYXNzb2NpYXRlZCB3
aXRoIHRoZSBub24tQ0xVRS1jb250cm9sbGVkIG1lZGlhIHplcm8gaXMgdG8gZGlzYWJsZSB0aGUg
bm9uLUNMVUUtY29udHJvbGxlZCBtZWRpYS4gTWF5YmUgaXQgbmVlZHMgdG8gc2xpZ2h0bHkgYmUg
bm90ZWQgdGhhdCB1c2luZyDigJxhPWluYWN0aXZl4oCdIGRvZXMgYWxzbyB3b3JrLg0KVGhlIHNl
Y3Rpb24gNC41LjQuMSBzYXlzIGJlbG93Og0KT25jZSBDTFVFIG1lZGlhIGhhcyBiZWVuIHN1Y2Nl
c3NmdWxseSBuZWdvdGlhdGVkIGRldmljZXMgU0hPVUxEIGVuc3VyZSB0aGF0IG5vbi1DTFVFLWNv
bnRyb2xsZWQgbWVkaWEgaXMgZGVhY3RpdmVkIGluIGNhc2VzIHdoZXJlIGl0IGNvcnJlc3BvbmRz
IHRvIHRoZSBtZWRpYSB0eXBlIG9mIENMVUUtY29udHJvbGxlZCBtZWRpYSB0aGF0IGhhcyBiZWVu
IHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVkLiAgVGhpcyBkZWFjdGl2YXRlIG1heSByZXF1aXJlIGFu
IGFkZGl0aW9uYWwgU0RQIGV4Y2hhbmdlLCBvciBtYXkgYmUgaW5jb3Jwb3JhdGVkIGludG8gb25l
IHRoYXQgaXMgcGFydCBvZiB0aGUgQ0xVRSBuZWdvdGlhdGlvbi4NClRoZSBzZWN0aW9uIDcgc2F5
cyBiZWxvdzoNCkFsaWNlIG5vdyBzZW5kcyAyMDAgT0sgMywgbWF0Y2hpbmcgdHdvIHJlY3Zvbmx5
IG0tbGluZXMgdG8gQm9iJ3MgbmV3IHNlbmRvbmx5IGxpbmVzLiAgU2hlIGluY2x1ZGVzIHRoZWly
IG1pZCB2YWx1ZXMgaW4gdGhlIGdyb3VwaW5nIGF0dHJpYnV0ZSB0byBzaG93IHRoZXkgYXJlIGNv
bnRyb2xsZWQgYnkgdGhlIENMVUUgY2hhbm5lbC4gIEFsaWNlIGFsc28gbm93IGRlYWN0aXZhdGVz
IHRoZSBpbml0aWFsIG5vbi1DTFVFLWNvbnRyb2xsZWQgbWVkaWEsIGFzIGJpZGlyZWN0aW9uYWwg
Q0xVRS1jb250cm9sbGVkIG1lZGlhIGlzIG5vdyBhdmFpbGFibGUuDQoNCjIpIFNlY3Rpb24gNC41
LjIuMy4gZGVmaW5lcyB3aGVuIGEgY2FsbCBmYWxscyBiYWNrIGZyb20gQ0xVRS1lbmFibGVkIHRv
IG5vbi1DTFVFIGVuYWJsZWQsIGRlZmluaW5nIGl0IGFzIHRoZSBmaXJzdCBvZiB0aGUgb3B0aW9u
cyB5b3Ugc3VnZ2VzdC4NCltTY2FybGV0dF0gSSBkb24ndCB0aGluayB0aGF0IHRoZSBzZWN0aW9u
IDQuNS4yLjMgaGFzIHNwZWNpZmllZCB3aGVuIGEgY2FsbCBmYWxscyBiYWNrIGZyb20gQ0xVRS1l
bmFibGVkIHRvIG5vbi1DTFVFIGVuYWJsZWQuIEkgZ3Vlc3MgeW91IGNvdWxkIG1lYW4gdGhlIGdy
ZWVuIGhpZ2hsaWdodCBwYXJ0IG9mIHRoZSBzZWN0aW9uIDQuNS40LjMgYmVsb3cuDQogIElmLCBp
biBhbiBvbmdvaW5nIENMVUUtZW5hYmxlZCBjYWxsLCBhbiBTRFAgb2ZmZXItYW5zd2VyIG5lZ290
aWF0aW9uIGNvbXBsZXRlcyBpbiBhIGZhc2hpb24gaW4gd2hpY2ggZWl0aGVyIHRoZSBDTFVFIGRh
dGEgY2hhbm5lbCB3YXMgbm90IHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVkIG9yIG9uZSBzaWRlIGRp
ZCBub3QgaW5jbHVkZSB0aGUgZGF0YSBjaGFubmVsIGluIGEgbWF0Y2hpbmcgQ0xVRSBncm91cCB0
aGVuIENMVUUgZm9yIHRoaXMgY2hhbm5lbCBpcyBkaXNhYmxlZC4gIEluICB0aGUgZXZlbnQgdGhh
dCB0aGlzIG9jY3VycywgQ0xVRSBpcyBubyBsb25nZXIgZW5hYmxlZCBhbmQgc2VuZGluZyBvZiBh
bGwgQ0xVRS1jb250cm9sbGVkIG1lZGlhIGFzc29jaWF0ZWQgd2l0aCB0aGUgY29ycmVzcG9uZGlu
ZyBDTFVFIGdyb3VwIE1VU1Qgc3RvcC4NCiAgICAgICBJIHRoaW5rIHRoYXQgaXQganVzdCBzcGVj
aWZpZXMgbW9zdCBzY2VuYXJpb3MuIEluIGhlcmUgaWYgdGhlIFNEUCBvZmZlci1hbnN3ZXIgZG9l
cyBub3QgaW5jbHVkZSB0aGUgZGF0YSBjaGFubmVsIGluIGEgbWF0Y2hpbmcgQ0xVRSBncm91cCwg
aXMgdGhlIERUTFMvU0NUUCBhc3NvY2lhdGlvbiBjbG9zZWQgPyBBY3R1YWxseSwgd2hlbiB0aGUg
ZGF0YSBjaGFubmVsIGlzIGRldm90ZWQgbW9yZSB0aGFuIG9uZSBkYXRhIHByb3RvY29scyAoaS5l
LiBDTFVFIHByb3RvY29sIGp1c3QgaXMgb25lIG9mIHRoZSBkYXRhIHByb3RvY29scyApLCBtYXli
ZSB1c2luZyBTQ1RQIFNTTiBSZXNldCBkb2VzIHdvcmsgbm90IGJ1dCByZW1vdmUgdGhlIERUTFMv
U0NUUCBhc3NvY2lhdGlvbi4gSSB0aGluayBpdCBuZWVkcyB0byBiZSBub3RlZC4NCkJ5IHRoZSB3
YXksIGlmIGFuIHVwZGF0ZWQgU0RQIG9mZmVyLWFuc3dlciB3aXRob3V0IGFsbCBDTFVFLWNvbnRy
b2xsZWQgbWVkaWEgc3RyZWFtcywgZG9lcyB0aGUgIENMVUUgZGF0YSBjaGFubmVsIG5lZWQgZXhp
c3Q/IE1heWJlIGl0IGxlYXZlcyB0aGUgaW1wbGVtZW50ZXJzIHRvIGNob29zZS4g4pi6DQoNCkNh
biB5b3UgY2hlY2sgdGhlc2Ugc2VjdGlvbnMsIGFuZCBzYXkgd2hpY2ggb25lcyB5b3UgdGhpbmsg
YXJlIGluc3VmZmljaWVudC9zaG91bGQgYmUgY2hhbmdlZD8NCg0KVGhhbmtzLA0KDQpSb2INCk9u
IDMwLzA4LzE0IDAzOjE2LCBMaXV5YW4gKFNjYXJsZXR0KSB3cm90ZToNCkhlbGxvLA0KDQogICAg
IEkgaGF2ZSBzb21lIGlzc3VlcyBhYm91dCBDTFVFLWVuYWJsZWQgY2FsbOKAmXMgZmFsbGJhY2su
DQogICAgIFRoZSBzaWduYWxpbmcgZHJhZnQgc2F5czoNCiAgICAgICAgICAgIEEgY2FsbCBpbiB3
aGljaCB0d28gQ0xVRS1jYXBhYmxlIGRldmljZXMgaGF2ZSBzdWNjZXNzZnVsbHkgbmVnb3RpYXRl
ZCBzdXBwb3J0IGZvciBhIENMVUUgZGF0YSBjaGFubmVsIGluIFNEUC4NCkEgQ0xVRS1lbmFibGVk
IGNhbGwgaXMgbm90IG5lY2Vzc2FyaWx5IGltbWVkaWF0ZWx5IGFibGUgdG8gc2VuZCBDTFVFLWNv
bnRyb2xsZWQgbWVkaWE7IG5lZ290aWF0aW9uIG9mIHRoZSBkYXRhIGNoYW5uZWwgYW5kIG9mIHRo
ZSBDTFVFIHByb3RvY29sIG11c3QgY29tcGxldGUgZmlyc3QNCg0KICAgICAgICAgQnV0IHRoZSBz
aWduYWxpbmcgZG9lcyBub3Qgc2F5IHNvbWV0aGluZyBhcyBiZWxvdzoNCg0KMSkgICAgICAgV2hl
biBhbmQgaG93IHRvIHN0b3AgdGhlIGJhc2ljIG1lZGlhIHN0cmVhbXM/DQp3YWl0IGFuZCB1bnRp
bCB0aGUgdHdvIENMVUUtY2FwYWJsZSBkZXZpY2UgZmluaXNoIHRoZSBuZWdvdGlhdGlvbiBhbmQg
dXNlIOKAnGE9aW5hY3RpdmXigJ0gb3Igc2V0IHRoZSBwb3J0IG51bWJlciB6ZXJvIHJlbGF0ZWQg
dG8gdGhlIGJhc2ljIG1lZGlhIHN0cmVhbXMNCg0KMikgICAgICAgV2hlbiBhbmQgaG93IHRvIHRy
aWdnZXIgYSBDTFVFLWVuYWJsZWQgY2FsbCBmYWxsIGJhY2s/DQp0aGUgZGF0YSBjaGFubmVsIGlz
IGV4cGxpY2l0bHkgY2xvc2VkIGJ5IFNEUCBPL0EgOw0KdGhlIGRhdGEgY2hhbm5lbCBpcyBjbG9z
ZWQgYnkgU0NUUCBTU04gUmVzZXQgKHNlZSB0aGUgZHJhZnQgZHJhZnQtaWV0Zi1ydGN3ZWItZGF0
YS1wcm90b2NvbC0wMykgO29yDQp0aGUgYWxsIENMVUUtY29udHJvbGxlZCBtZWRpYSBzdHJlYW1z
IGFyZSByZW1vdmVkIGJ5IFNEUCBPL0ENCg0KICAgICBUaGF04oCZcyBhbGwgYW5kIGNvbW1lbnRz
IHdlbGNvbWUuDQoNCkJlc3QgUmVnYXJkcywNClNjYXJsZXR0DQoNCkh1YXdlaSBUZWNobm9sb2dp
ZXMgQ28uLCBMdGQuDQpCYW50aWFuLCBMb25nZ2FuZyBEaXN0cmljdCxTaGVuemhlbiA1MTgxMjks
IFAuUi5DaGluYQ0KaHR0cDovL3d3dy5odWF3ZWkuY29tDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KVGhpcyBlLW1haWwgYW5kIGl0cyBhdHRhY2htZW50cyBjb250YWluIGNvbmZp
ZGVudGlhbCBpbmZvcm1hdGlvbiBmcm9tIEhVQVdFSSwgd2hpY2gNCmlzIGludGVuZGVkIG9ubHkg
Zm9yIHRoZSBwZXJzb24gb3IgZW50aXR5IHdob3NlIGFkZHJlc3MgaXMgbGlzdGVkIGFib3ZlLiBB
bnkgdXNlIG9mIHRoZQ0KaW5mb3JtYXRpb24gY29udGFpbmVkIGhlcmVpbiBpbiBhbnkgd2F5IChp
bmNsdWRpbmcsIGJ1dCBub3QgbGltaXRlZCB0bywgdG90YWwgb3IgcGFydGlhbA0KZGlzY2xvc3Vy
ZSwgcmVwcm9kdWN0aW9uLCBvciBkaXNzZW1pbmF0aW9uKSBieSBwZXJzb25zIG90aGVyIHRoYW4g
dGhlIGludGVuZGVkDQpyZWNpcGllbnQocykgaXMgcHJvaGliaXRlZC4gSWYgeW91IHJlY2VpdmUg
dGhpcyBlLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBieQ0KcGhvbmUg
b3IgZW1haWwgaW1tZWRpYXRlbHkgYW5kIGRlbGV0ZSBpdCENCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0KY2x1ZSBtYWlsaW5nIGxpc3QNCg0KY2x1
ZUBpZXRmLm9yZzxtYWlsdG86Y2x1ZUBpZXRmLm9yZz4NCg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9jbHVlDQoNCg==

--_000_E97C33E5D67C2843AFA535DE2E5B80C1573F1A66SZXEMA503MBXchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOm09Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1o
dG1sNDAiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRl
bnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjwhLS1baWYgIW1zb10+
PHN0eWxlPnZcOioge2JlaGF2aW9yOnVybCgjZGVmYXVsdCNWTUwpO30NCm9cOioge2JlaGF2aW9y
OnVybCgjZGVmYXVsdCNWTUwpO30NCndcOioge2JlaGF2aW9yOnVybCgjZGVmYXVsdCNWTUwpO30N
Ci5zaGFwZSB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0KPC9zdHlsZT48IVtlbmRpZl0t
LT48c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250
LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OuWui+S9kzsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEg
MSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3Nl
LTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGli
cmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250
LWZhbWlseToiXEDlrovkvZMiOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZv
bnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQg
NCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTrljY7mlofnu4bpu5E7DQoJcGFub3Nl
LTE6MiAxIDYgMCA0IDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWN
juaWh+e7hum7kSI7DQoJcGFub3NlLTE6MiAxIDYgMCA0IDEgMSAxIDEgMTt9DQovKiBTdHlsZSBE
ZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0K
CXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgl0ZXh0LWFsaWduOmp1c3Rp
Znk7DQoJdGV4dC1qdXN0aWZ5OmludGVyLWlkZW9ncmFwaDsNCglmb250LXNpemU6MTAuNXB0Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6YmxhY2s7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCDpooTorr7moLzlvI8gQ2hhciI7DQoJbWFyZ2lu
OjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250
LWZhbWlseTrlrovkvZM7DQoJY29sb3I6YmxhY2s7fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5N
c29MaXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFncmFwaA0KCXttc28tc3R5bGUtcHJpb3Jp
dHk6MzQ7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJdGV4dC1hbGln
bjpqdXN0aWZ5Ow0KCXRleHQtanVzdGlmeTppbnRlci1pZGVvZ3JhcGg7DQoJdGV4dC1pbmRlbnQ6
MjEuMHB0Ow0KCWZvbnQtc2l6ZToxMC41cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjpibGFjazt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNv
bG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5IVE1MQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCDp
ooTorr7moLzlvI8gQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1s
aW5rOiJIVE1MIOmihOiuvuagvOW8jyI7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCglj
b2xvcjpibGFjazt9DQpzcGFuLkVtYWlsU3R5bGUyMQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMx
RjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ
Zm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5
Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYuV29yZFNl
Y3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBs
aXN0IGwwDQoJe21zby1saXN0LWlkOjEwNjk0MjUyODg7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7
DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjE3MTQ4NjMwNzggLTE4MTE5MTQ2MzggNjc2OTg3MTMg
Njc2OTg3MTUgNjc2OTg3MDMgNjc2OTg3MTMgNjc2OTg3MTUgNjc2OTg3MDMgNjc2OTg3MTMgNjc2
OTg3MTU7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC10ZXh0OiIlMVwpIjsNCgltc28t
bGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJ
bWFyZ2luLWxlZnQ6MzkuMHB0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2
ZWwyDQoJe21zby1sZXZlbC10YWItc3RvcDo3Mi4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21z
by1sZXZlbC10YWItc3RvcDoxMDguMHB0Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotMTguMHB0O30NCkBsaXN0IGwwOmxldmVsNA0KCXttc28tbGV2ZWwt
dGFiLXN0b3A6MTQ0LjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4
dC1pbmRlbnQ6LTE4LjBwdDt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7bXNvLWxldmVsLXRhYi1zdG9w
OjE4MC4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC10YWItc3RvcDoyMTYuMHB0
Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0
O30NCkBsaXN0IGwwOmxldmVsNw0KCXttc28tbGV2ZWwtdGFiLXN0b3A6MjUyLjBwdDsNCgltc28t
bGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDt9DQpAbGlz
dCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLXRhYi1zdG9wOjI4OC4wcHQ7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2
ZWw5DQoJe21zby1sZXZlbC10YWItc3RvcDozMjQuMHB0Ow0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0O30NCm9sDQoJe21hcmdpbi1ib3R0b206
MGNtO30NCnVsDQoJe21hcmdpbi1ib3R0b206MGNtO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2
IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4N
CjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGJnY29s
b3I9IndoaXRlIiBsYW5nPSJaSC1DTiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2
IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5IaSBSb2JlcnQsPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBJIGhhdmUgcmVhZCB0aGUgbGF0
ZXN0IHZlcnNpb24gb2YgZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZy4NCjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IFBsZWFzZSBzZWUgbXkgcmVwbGllcyBiZWxvdyBhbmQgdGhhbmtzLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5CZXN0
IFJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5TY2FybGV0dDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJs
dWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImxlZnQiIHN0eWxlPSJ0
ZXh0LWFsaWduOmxlZnQiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjp3aW5kb3d0ZXh0Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOndpbmRvd3RleHQiPg0KIGNsdWUgW21haWx0bzpjbHVl
LWJvdW5jZXNAaWV0Zi5vcmddIDxiPk9uIEJlaGFsZiBPZiA8L2I+Um9iZXJ0IEhhbnNlbjxicj4N
CjxiPlNlbnQ6PC9iPiBNb25kYXksIFNlcHRlbWJlciAwMSwgMjAxNCAxMDoxOCBQTTxicj4NCjxi
PlRvOjwvYj4gY2x1ZUBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW2NsdWVdIENM
VUUtZW5hYmxlZCBjYWxsJ3MgZmFsbGJhY2s8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImxlZnQiIHN0eWxlPSJ0ZXh0LWFs
aWduOmxlZnQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFu
IGxhbmc9IkVOLVVTIj5IaSBTY2FybGV0dCw8YnI+DQo8YnI+DQoxKSBTZWN0aW9uIDQuNS4yLjMu
IGFuZCA0LjUuNC4xLiBhZGRyZXNzIHdoZW4gYW5kIGhvdyB0byBkaXNhYmxlIG5vbi1DTFVFLWNv
bnRyb2xsZWQgbWVkaWEuIFRoZXJlIGlzbid0IGEgaHVnZSBhbW91bnQgb2YgZGV0YWlsIChJIHJl
bW92ZWQgYWxsIG5vcm1hdGl2ZSBsYW5ndWFnZSBpbiBzZWN0aW9uIDQuNS4yLjMuIGFzIHBhcnQg
b2YgdGhlIG1vc3QgcmVjZW50IGRyYWZ0IHRvIG1ha2UgY2xlYXIgaXQgd2FzIG1lcmVseSBpbGx1
c3RyYXRpdmUpDQogYnV0IHRoZW4gSSdtIG5vdCBzdXJlIHRoaXMgaXMgc29tZXRoaW5nIHdlIHNo
b3VsZCBiZSBtYW5kYXRpbmc7IGRpZmZlcmVudCBpbXBsZW1lbnRhdGlvbnMgd2lsbCBsaWtlbHkg
aGF2ZSBkaWZmZXJlbnQgb3BpbmlvbnMgb24gd2hlbiBub24tQ0xVRS1jb250cm9sbGVkIG1lZGlh
IHNob3VsZCBiZSBkaXNhYmxlZCAoc29tZSBtYXkgbmV2ZXIgd2FudCBpdCwgc29tZSBtYXkgd2Fu
dCB0byBjb250aW51ZSBpdCB1bnRpbCB0aGV5IGhhdmUgQ0xVRS1jb250cm9sbGVkDQogbWVkaWEp
Ljwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9t
OjEyLjBwdCI+PGI+PGk+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5b
U2NhcmxldHRdDQo8L3NwYW4+PC9pPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OiMxRjQ5N0QiPlRoZSBmb2xsb3dpbmcgZGVzY3JpcHRpb24gYW5zd2VycyB0byB0aGUgcG9pbnQg
KGkuZS4gd2hlbiBhbmQgaG93IHRvIGRpc2FibGUgbm9uLUNMVUUtY29udHJvbGxlZCBtZWRpYSks
IGVzcGVjaWFsbHkgdGhlIHllbGxvdyBoaWdobGlnaHQgcGFydC4gU2V0dGluZyB0aGUgcG9ydCBu
dW1iZXIgYXNzb2NpYXRlZCB3aXRoIHRoZSBub24tQ0xVRS1jb250cm9sbGVkDQogbWVkaWEgemVy
byBpcyB0byBkaXNhYmxlIHRoZSBub24tQ0xVRS1jb250cm9sbGVkIG1lZGlhLiBNYXliZSBpdCBu
ZWVkcyB0byBzbGlnaHRseSBiZSBub3RlZCB0aGF0IHVzaW5nIOKAnGE9aW5hY3RpdmXigJ0gZG9l
cyBhbHNvIHdvcmsuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPlRoZSBzZWN0aW9uIDQuNS40LjEgc2F5cyBiZWxvdzo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OjBjbTttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206MTIuMHB0O21hcmdpbi1sZWZ0OjUu
MHB0Ij4NCjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+T25jZSBDTFVF
IG1lZGlhIGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVkIGRldmljZXMgU0hPVUxEIGVu
c3VyZSB0aGF0IG5vbi1DTFVFLWNvbnRyb2xsZWQgbWVkaWEgaXMgZGVhY3RpdmVkIGluIGNhc2Vz
IHdoZXJlIGl0IGNvcnJlc3BvbmRzIHRvIHRoZSBtZWRpYSB0eXBlIG9mIENMVUUtY29udHJvbGxl
ZCBtZWRpYSB0aGF0IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVkLiZuYnNwOw0KIFRo
aXMgZGVhY3RpdmF0ZSBtYXkgcmVxdWlyZSBhbiBhZGRpdGlvbmFsIFNEUCBleGNoYW5nZSwgb3Ig
bWF5IGJlIGluY29ycG9yYXRlZCBpbnRvIG9uZSB0aGF0IGlzIHBhcnQgb2YgdGhlIENMVUUgbmVn
b3RpYXRpb24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OiMxRjQ5N0QiPlRoZTxiPjxpPg0KPC9pPjwvYj5zZWN0aW9uPGI+PGk+IDwvaT48L2I+NyBzYXlz
IGJlbG93OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTox
Mi4wcHQ7bWFyZ2luLWxlZnQ6NS4wcHQiPg0KPHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xv
cjojMUY0OTdEIj5BbGljZSBub3cgc2VuZHMgMjAwIE9LIDMsIG1hdGNoaW5nIHR3byByZWN2b25s
eSBtLWxpbmVzIHRvIEJvYidzIG5ldyBzZW5kb25seSBsaW5lcy4mbmJzcDsgU2hlIGluY2x1ZGVz
IHRoZWlyIG1pZCB2YWx1ZXMgaW4gdGhlIGdyb3VwaW5nIGF0dHJpYnV0ZSB0byBzaG93IHRoZXkg
YXJlIGNvbnRyb2xsZWQgYnkgdGhlIENMVUUgY2hhbm5lbC4mbmJzcDsgQWxpY2UgYWxzbyBub3cg
ZGVhY3RpdmF0ZXMNCiB0aGUgaW5pdGlhbCBub24tQ0xVRS1jb250cm9sbGVkIG1lZGlhLCA8c3Bh
biBzdHlsZT0iYmFja2dyb3VuZDp5ZWxsb3c7bXNvLWhpZ2hsaWdodDp5ZWxsb3ciPg0KYXMgYmlk
aXJlY3Rpb25hbCBDTFVFLWNvbnRyb2xsZWQgbWVkaWEgaXMgbm93IGF2YWlsYWJsZTwvc3Bhbj4u
IDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PGJyPg0KPGJyPg0KMikgU2VjdGlvbiA0LjUuMi4z
LiBkZWZpbmVzIHdoZW4gYSBjYWxsIGZhbGxzIGJhY2sgZnJvbSBDTFVFLWVuYWJsZWQgdG8gbm9u
LUNMVUUgZW5hYmxlZCwgZGVmaW5pbmcgaXQgYXMgdGhlIGZpcnN0IG9mIHRoZSBvcHRpb25zIHlv
dSBzdWdnZXN0Ljwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tYm90dG9tOjEyLjBwdCI+PGI+PGk+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjoj
MUY0OTdEIj5bU2NhcmxldHRdDQo8L3NwYW4+PC9pPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPkkgZG9uJ3QgdGhpbmsgdGhhdCB0aGUgc2VjdGlvbiA0LjUuMi4z
IGhhcyBzcGVjaWZpZWQgd2hlbiBhIGNhbGwgZmFsbHMgYmFjayBmcm9tIENMVUUtZW5hYmxlZCB0
byBub24tQ0xVRSBlbmFibGVkLiBJIGd1ZXNzIHlvdSBjb3VsZCBtZWFuIHRoZSBncmVlbiBoaWdo
bGlnaHQgcGFydCBvZiB0aGUgc2VjdGlvbiA0LjUuNC4zIGJlbG93Lg0KPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDow
Y207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjEyLjBwdDttYXJnaW4tbGVmdDo1LjBw
dCI+DQo8c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNw
O0lmLCBpbiBhbiBvbmdvaW5nIENMVUUtZW5hYmxlZCBjYWxsLCBhbiBTRFAgb2ZmZXItYW5zd2Vy
IG5lZ290aWF0aW9uIGNvbXBsZXRlcyBpbiBhIGZhc2hpb24gaW4gd2hpY2ggZWl0aGVyIHRoZSBD
TFVFIGRhdGEgY2hhbm5lbCB3YXMgbm90IHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVkDQo8c3BhbiBz
dHlsZT0iYmFja2dyb3VuZDpsaW1lO21zby1oaWdobGlnaHQ6bGltZSI+b3Igb25lIHNpZGUgZGlk
IG5vdCBpbmNsdWRlIHRoZSBkYXRhIGNoYW5uZWwgaW4gYSBtYXRjaGluZyBDTFVFIGdyb3VwPC9z
cGFuPiB0aGVuIENMVUUgZm9yIHRoaXMgY2hhbm5lbCBpcyBkaXNhYmxlZC4mbmJzcDsgSW4mbmJz
cDsgdGhlIGV2ZW50IHRoYXQgdGhpcyBvY2N1cnMsIENMVUUgaXMgbm8gbG9uZ2VyIGVuYWJsZWQg
YW5kIHNlbmRpbmcgb2YgYWxsIENMVUUtY29udHJvbGxlZA0KIG1lZGlhIGFzc29jaWF0ZWQgd2l0
aCB0aGUgY29ycmVzcG9uZGluZyBDTFVFIGdyb3VwIE1VU1Qgc3RvcC48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEkgdGhpbmsgdGhhdCBpdCBqdXN0IHNwZWNpZmllcyBtb3N0
IHNjZW5hcmlvcy4gSW4gaGVyZSBpZiB0aGUgU0RQIG9mZmVyLWFuc3dlciBkb2VzIG5vdCBpbmNs
dWRlIHRoZSBkYXRhIGNoYW5uZWwgaW4gYSBtYXRjaGluZyBDTFVFIGdyb3VwLCBpcyB0aGUgRFRM
Uy9TQ1RQIGFzc29jaWF0aW9uDQogY2xvc2VkID8gQWN0dWFsbHksIHdoZW4gdGhlIGRhdGEgY2hh
bm5lbCBpcyBkZXZvdGVkIG1vcmUgdGhhbiBvbmUgZGF0YSBwcm90b2NvbHMgKGkuZS4gQ0xVRSBw
cm90b2NvbCBqdXN0IGlzIG9uZSBvZiB0aGUgZGF0YSBwcm90b2NvbHMgKSwgbWF5YmUgdXNpbmcg
U0NUUCBTU04gUmVzZXQgZG9lcyB3b3JrIG5vdCBidXQgcmVtb3ZlIHRoZSBEVExTL1NDVFAgYXNz
b2NpYXRpb24uIEkgdGhpbmsgaXQgbmVlZHMgdG8gYmUgbm90ZWQuDQo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjBj
bTttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206MTIuMHB0O21hcmdpbi1sZWZ0OjUuMjVw
dDt0ZXh0LWluZGVudDoxNS43NXB0Ij4NCjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+QnkgdGhlIHdheSwgaWYgYW4gdXBkYXRlZCBTRFAgb2ZmZXItYW5zd2VyIHdpdGhv
dXQgYWxsIENMVUUtY29udHJvbGxlZCBtZWRpYSBzdHJlYW1zLCBkb2VzIHRoZSZuYnNwOyBDTFVF
IGRhdGEgY2hhbm5lbCBuZWVkIGV4aXN0PyBNYXliZSBpdCBsZWF2ZXMgdGhlIGltcGxlbWVudGVy
cyB0byBjaG9vc2UuDQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWls
eTpXaW5nZGluZ3M7Y29sb3I6IzFGNDk3RCI+Sjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PGJy
Pg0KPGJyPg0KQ2FuIHlvdSBjaGVjayB0aGVzZSBzZWN0aW9ucywgYW5kIHNheSB3aGljaCBvbmVz
IHlvdSB0aGluayBhcmUgaW5zdWZmaWNpZW50L3Nob3VsZCBiZSBjaGFuZ2VkPzxicj4NCjxicj4N
ClRoYW5rcyw8YnI+DQo8YnI+DQpSb2I8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPk9uIDMwLzA4LzE0IDAzOjE2LCBM
aXV5YW4gKFNjYXJsZXR0KSB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkhlbGxvLDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJz
cDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEkgaGF2ZSBzb21lIGlzc3VlcyBhYm91
dCBDTFVFLWVuYWJsZWQgY2FsbOKAmXMgZmFsbGJhY2suPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyBUaGUgc2lnbmFsaW5nIGRyYWZ0IHNheXM6PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgQSBjYWxsIGluIHdo
aWNoIHR3byBDTFVFLWNhcGFibGUgZGV2aWNlcyBoYXZlIHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVk
IHN1cHBvcnQgZm9yIGEgQ0xVRSBkYXRhIGNoYW5uZWwgaW4gU0RQLg0KPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjE1Ljc1cHQ7
dGV4dC1pbmRlbnQ6MjYuMjVwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPkEgQ0xVRS1lbmFibGVkIGNh
bGwgaXMgbm90IG5lY2Vzc2FyaWx5IGltbWVkaWF0ZWx5IGFibGUgdG8gc2VuZCBDTFVFLWNvbnRy
b2xsZWQgbWVkaWE7IG5lZ290aWF0aW9uIG9mIHRoZSBkYXRhIGNoYW5uZWwgYW5kIG9mIHRoZSBD
TFVFIHByb3RvY29sIG11c3QgY29tcGxldGUgZmlyc3Q8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBCdXQgdGhlIHNpZ25h
bGluZyBkb2VzIG5vdCBzYXkgc29tZXRoaW5nIGFzIGJlbG93OjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzkuMHB0
O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzIiPg0KPCFbaWYgIXN1
cHBvcnRMaXN0c10+PHNwYW4gbGFuZz0iRU4tVVMiPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25v
cmUiPjEpPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7
Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9z
cGFuPjwhW2VuZGlmXT48c3BhbiBsYW5nPSJFTi1VUyI+V2hlbiBhbmQgaG93IHRvIHN0b3AgdGhl
IGJhc2ljIG1lZGlhIHN0cmVhbXM/PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjIxLjBwdDt0ZXh0LWluZGVudDoxOC4wcHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj53YWl0IGFuZCB1bnRpbCB0aGUgdHdvIENMVUUtY2FwYWJsZSBkZXZp
Y2UgZmluaXNoIHRoZSBuZWdvdGlhdGlvbiBhbmQgdXNlIOKAnGE9aW5hY3RpdmXigJ0gb3Igc2V0
IHRoZSBwb3J0IG51bWJlciB6ZXJvIHJlbGF0ZWQgdG8gdGhlIGJhc2ljIG1lZGlhIHN0cmVhbXM8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9
Im1hcmdpbi1sZWZ0OjM5LjBwdDt0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVs
MSBsZm8yIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIGxhbmc9IkVOLVVTIj48c3BhbiBz
dHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4yKTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gbGFuZz0iRU4tVVMiPldoZW4g
YW5kIGhvdyB0byB0cmlnZ2VyIGEgQ0xVRS1lbmFibGVkIGNhbGwgZmFsbCBiYWNrPzxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoy
MS4wcHQ7dGV4dC1pbmRlbnQ6MTguMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+dGhlIGRhdGEgY2hh
bm5lbCBpcyBleHBsaWNpdGx5IGNsb3NlZCBieSBTRFAgTy9BIDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MjEuMHB0O3RleHQt
aW5kZW50OjE4LjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPnRoZSBkYXRhIGNoYW5uZWwgaXMgY2xv
c2VkIGJ5IFNDVFAgU1NOIFJlc2V0IChzZWUgdGhlIGRyYWZ0IGRyYWZ0LWlldGYtcnRjd2ViLWRh
dGEtcHJvdG9jb2wtMDMpIDtvcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoyMS4wcHQ7dGV4dC1pbmRlbnQ6MTguMHB0Ij48c3Bh
biBsYW5nPSJFTi1VUyI+dGhlIGFsbCBDTFVFLWNvbnRyb2xsZWQgbWVkaWEgc3RyZWFtcyBhcmUg
cmVtb3ZlZCBieSBTRFAgTy9BPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgVGhhdOKAmXMgYWxsIGFuZCBjb21tZW50cyB3ZWxjb21lLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+QmVzdCBSZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5TY2FybGV0dDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTrljY7mlofnu4bpu5EiPjxicj4NCkh1YXdlaSBUZWNobm9sb2dpZXMg
Q28uLCBMdGQuPGJyPg0KQmFudGlhbiwgTG9uZ2dhbmcgRGlzdHJpY3QsU2hlbnpoZW4gNTE4MTI5
LCBQLlIuQ2hpbmE8YnI+DQo8YSBocmVmPSJodHRwOi8vd3d3Lmh1YXdlaS5jb20iPmh0dHA6Ly93
d3cuaHVhd2VpLmNvbTwvYT48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPg0KPG86cD48L286cD48
L3NwYW4+PC9wPg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHlsZT0i
dGV4dC1hbGlnbjpjZW50ZXIiPjxzcGFuIGxhbmc9IkVOLVVTIj4NCjxociBzaXplPSIyIiB3aWR0
aD0iMTAwJSIgYWxpZ249ImNlbnRlciI+DQo8L3NwYW4+PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTo3LjVwdDtmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmdyYXkiPlRo
aXMgZS1tYWlsIGFuZCBpdHMgYXR0YWNobWVudHMgY29udGFpbiBjb25maWRlbnRpYWwgaW5mb3Jt
YXRpb24gZnJvbSBIVUFXRUksIHdoaWNoDQo8YnI+DQppcyBpbnRlbmRlZCBvbmx5IGZvciB0aGUg
cGVyc29uIG9yIGVudGl0eSB3aG9zZSBhZGRyZXNzIGlzIGxpc3RlZCBhYm92ZS4gQW55IHVzZSBv
ZiB0aGUNCjxicj4NCmluZm9ybWF0aW9uIGNvbnRhaW5lZCBoZXJlaW4gaW4gYW55IHdheSAoaW5j
bHVkaW5nLCBidXQgbm90IGxpbWl0ZWQgdG8sIHRvdGFsIG9yIHBhcnRpYWwNCjxicj4NCmRpc2Ns
b3N1cmUsIHJlcHJvZHVjdGlvbiwgb3IgZGlzc2VtaW5hdGlvbikgYnkgcGVyc29ucyBvdGhlciB0
aGFuIHRoZSBpbnRlbmRlZCA8YnI+DQpyZWNpcGllbnQocykgaXMgcHJvaGliaXRlZC4gSWYgeW91
IHJlY2VpdmUgdGhpcyBlLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBi
eQ0KPGJyPg0KcGhvbmUgb3IgZW1haWwgaW1tZWRpYXRlbHkgYW5kIGRlbGV0ZSBpdCE8L3NwYW4+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OuWu
i+S9kyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyI+X19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188bzpwPjwvbzpwPjwv
c3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiPmNsdWUgbWFpbGluZyBsaXN0PG86
cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIj48YSBocmVmPSJt
YWlsdG86Y2x1ZUBpZXRmLm9yZyI+Y2x1ZUBpZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvc3Bhbj48
L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiPjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vY2x1ZSI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9jbHVlPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPC9ibG9ja3F1b3RlPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImxlZnQiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTrl
rovkvZMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jv
ZHk+DQo8L2h0bWw+DQo=

--_000_E97C33E5D67C2843AFA535DE2E5B80C1573F1A66SZXEMA503MBXchi_--


From nobody Thu Sep  4 00:39:36 2014
Return-Path: <scarlett.liuyan@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D28381A6EEE for <clue@ietfa.amsl.com>; Thu,  4 Sep 2014 00:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.269
X-Spam-Level: 
X-Spam-Status: No, score=-4.269 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59554DvqyjtE for <clue@ietfa.amsl.com>; Thu,  4 Sep 2014 00:39:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 994AC1A6EE1 for <clue@ietf.org>; Thu,  4 Sep 2014 00:39:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BME00891; Thu, 04 Sep 2014 07:39:25 +0000 (GMT)
Received: from SZXEMA403-HUB.china.huawei.com (10.82.72.35) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 4 Sep 2014 08:39:24 +0100
Received: from SZXEMA503-MBX.china.huawei.com ([169.254.5.91]) by SZXEMA403-HUB.china.huawei.com ([10.82.72.35]) with mapi id 14.03.0158.001; Thu, 4 Sep 2014 15:39:17 +0800
From: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] CLUE-enabled call's fallback
Thread-Index: Ac/D+GittEPNbekRSra4ryOrQuay7ABtCKsAAAQAmgAAlM5vkA==
Date: Thu, 4 Sep 2014 07:39:17 +0000
Message-ID: <E97C33E5D67C2843AFA535DE2E5B80C1573F1A88@SZXEMA503-MBX.china.huawei.com>
References: <E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com> <54048034.6000708@cisco.com> <54049B10.8090607@alum.mit.edu>
In-Reply-To: <54049B10.8090607@alum.mit.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.63.147.208]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/P_ue31GmqrzBbVeOuDRzD_Ibo8g
Subject: Re: [clue] CLUE-enabled call's fallback
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 07:39:34 -0000

SGkgUGF1bCwNCg0KCU1heWJlIHdlIGlnbm9yZSB0aGUgbWVkaWEgZmVhdHVyZSB0YWcgaW5kaWNh
dGluZyBzdXBwb3J0IGZvciBDTFVFLg0KCVBsZWFzZSBzZWUgbXkgcmVwbGllcyBiZWxvdyBhbmQg
dGhhbmtzLg0KDQpCZXN0IFJlZ2FyZHMNClNjYXJsZXR0DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogY2x1ZSBbbWFpbHRvOmNsdWUtYm91bmNlc0BpZXRmLm9yZ10gT24g
QmVoYWxmIE9mIFBhdWwgS3l6aXZhdA0KPiBTZW50OiBUdWVzZGF5LCBTZXB0ZW1iZXIgMDIsIDIw
MTQgMTI6MTMgQU0NCj4gVG86IGNsdWVAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtjbHVlXSBD
TFVFLWVuYWJsZWQgY2FsbCdzIGZhbGxiYWNrDQo+IA0KPiBSb2IsIFNjYXJsZXR0LA0KPiANCj4g
VGhlcmUgaXMgb25lIHRoaW5nIHRoYXQgSSBhbSBjb25jZXJuZWQgd2l0aDoNCj4gDQo+IEkgc2Vl
IGFuIGFuYWxvZ3kgYmV0d2VlbiBtb3ZpbmcgdG8vZnJvbSBjbHVlLWVuYWJsZWQgc3RhdHVzIGFu
ZCBtb3ZpbmcNCj4gdG8vZnJvbSBob2xkIHN0YXR1cy4gV2l0aCBob2xkLCBpZiB5b3UgYXJlbid0
IGNhcmVmdWwgaXQgaXMgcG9zc2libGUgdG8gZ2V0IGludG8gYQ0KPiAic3R1Y2sgb24gaG9sZCIg
c3RhdHVzLiBTaW1pbGFybHksIEkgdGhpbmsgaWYgd2UgYXJlbid0IGNhcmVmdWwgaXQgd2lsbCBi
ZSBwb3NzaWJsZQ0KPiB0byBnZXQgaW50byBhICJzdHVjayBpbiBjbHVlLWRpc2FibGVkIiBzdGF0
dXMuDQo+IA0KPiBUaGUgInN0dWNrIG9uIGhvbGQiIGFyaXNlcyB3aGVuIGJvdGggZW5kcyBoYXZl
IHB1dCB0aGUgY2FsbCBvbiBob2xkDQo+IGE9aW5hY3RpdmUgaGFzIGJlZW4gbmVnb3RpYXRlZC4g
SXQgb2NjdXJzIGlmIG9uZSBlbmQgd2FudHMgdG8gZ28gb2ZmIGhvbGQsIGJ1dA0KPiBjb250aW51
ZXMgdG8gb2ZmZXIgYT1pbmFjdGl2ZSBiZWNhdXNlIGl0IHRoaW5rcyB0aGUgb3RoZXIgZW5kIHdh
bnRzIHRvIGJlIG9uDQo+IGhvbGQuIEl0IGlzIGZpeGVkIGJ5IGEgcG9saWN5IHdoZXJlIGVhY2gg
ZW5kIG1ha2VzIG5vIGFzc3VtcHRpb25zIGFib3V0DQo+IHdoYXQgdGhlIG90aGVyIGVuZCB3YW50
cyBpbiB0aGUgZnV0dXJlIHdoZW4gaXQgbWFrZXMgb2ZmZXJzIC0gb2ZmZXJpbmcgd2hhdA0KPiBp
dCB3YW50cyBmb3IgaXRzZWxmLiBBbmQgdGhpcyBuZWVkcyB0byBiZSB0cnVlIHdoZW4gcmVzcG9u
ZGluZyB0byBvZmZlcmxlc3MNCj4gaW52aXRlcyB0b28uDQo+IA0KPiBUaGUgcXVlc3Rpb24gaXMg
d2hldGhlciB3ZSBoYXZlIHN1Y2ggaXNzdWVzIHdpdGggY2x1ZS1lbmFibGVtZW50Lg0KPiANCj4g
Q29uc2lkZXIgdGhlIGZvbGxvd2luZywgYmV0d2VlbiBBbGljZSBhbmQgQm9iOg0KPiANCj4gLSBB
bGljZSBjYWxscyBCb2IsIG9mZmVyaW5nIENMVUUgc3VwcG9ydCBjbHVlIGdyb3VwIGNvbnRhaW5p
bmcgc2N0cC4NCj4gLSBCb2IgaXMgY2x1ZS1jYXBhYmxlLCBidXQgY2FuJ3QgaW5pdGlhbGx5IGVu
YWJsZSBpdC4NCj4gICAgKEUuZy4sIGNlbGwgcGhvbmUgb24gc2xvdyBsaW5rLikgU28gcmVmdXNl
cyB0aGUgU0NUUC4NCltTY2FybGV0dF0gSW4gdGhlIGFib3ZlIGV4YW1wbGUsIHlvdSBtZWFuIHRo
YXQgQm9iIGRvZXMgbm90IGluY2x1ZGUgdGhlIG0gbGluZSBmb3IgYSBjbHVlIGRhdGEgY2hhbm5l
bC4NCk15IHF1ZXN0aW9uIGlzIHdoZXRoZXIgQm9iIGluY2x1ZGVzIHRoZSAic2lwLmNsdWUiIG1l
ZGlhIHRhZyBmZWF0dXJlIG9yIG5vdC4NCklmIEJvYiBpbmNsdWRlcyB0aGUgInNpcC5jbHVlIiBt
ZWRpYSB0YWcgZmVhdHVyZSwgQWxpY2UgY2FuIGtub3cgdGhhdCBCb2Igc3VwcG9ydHMgZm9yIENM
VUUuDQpBY2NvcmRpbmdseSwgQWxpY2UgY2FuIG9mZmVyIGEgY2x1ZSBkYXRhIGNoYW5uZWwgYWdh
aW4gb3IgQm9iIGZvcndhcmRseSBvZmZlciBhIGNsdWUgZGF0YSBjaGFubmVsIGluIHRoZSBmdXR1
cmUuDQpJZiBCb2IgZG9lcyBub3QgaW5jbHVkZSBpdCwgQWxpY2UgU0hPVUxEIG5vdCBvZmZlciBh
IGNsdWUgZGF0YSBjaGFubmVsIGFnYWluLg0KPiANCj4gVGhlIHF1ZXN0aW9uIGlzIHdoYXQgaGFw
cGVucyBzdWJzZXF1ZW50bHkuIElmIEFsaWNlIGhhcyByZWFzb24gdG8gc2VuZCBhbg0KPiBvZmZl
ciBpbiB0aGUgZnV0dXJlLCBzaG91bGQgc2hlIGFnYWluIG9mZmVyIHRoZSBjbHVlIGNoYW5uZWw/
IE9yIHNob3VsZCBzaGUNCj4gYXNzdW1lIHRoYXQgaXQgaXMgdXAgdG8gQm9iIHRvIHRha2UgdGhl
IGluaXRpYXRpdmUgaW4gZW5hYmxpbmcgQ0xVRT8gKFRoZXJlDQo+IG1heSBiZSBhIGNvc3QgYXNz
b2NpYXRlZCBvZmZlcmluZyB0aGUgY2x1ZSBjaGFubmVsLCBpbiBJQ0UsIERUTFMsIGV0Yy4pDQo+
IA0KPiBUaGUgc2FmZXN0IGFuc3dlciBpcyB0byBzYXkgdGhhdCB3aGVuZXZlciBhIGNsdWUtY2Fw
YWJsZSBlbmRwb2ludCBzZW5kcyBhbg0KPiBvZmZlciwgYW5kIGlzIHdpbGxpbmcvYWJsZSB0byBi
ZSBjbHVlLWVuYWJsZWQsIGl0IHNob3VsZCBvZmZlciB0aGUgU0NUUCBtLWxpbmUuDQo+IA0KPiBX
ZSBjb3VsZCBleHBsb3JlIGxlc3MgYWdncmVzc2l2ZSBhcHByb2FjaGVzLiBCdXQgdGhlbiB3ZSBt
dXN0IGxvb2sgdmVyeQ0KPiBjYXJlZnVsbHkgLSB0aGUgY2FzZXMgdGhhdCBjYXVzZSB0cm91Ymxl
IGFyZSBvZnRlbiBzdWJ0bGUsIGludm9sdmluZyBvZmZlcmxlc3MNCj4gaW52aXRlcywgQjJCVUFz
LCBldGMuDQo+IA0KPiAJVGhhbmtzLA0KPiAJUGF1bA0KPiANCj4gT24gOS8xLzE0IDEwOjE4IEFN
LCBSb2JlcnQgSGFuc2VuIHdyb3RlOg0KPiA+IEhpIFNjYXJsZXR0LA0KPiA+DQo+ID4gMSkgU2Vj
dGlvbiA0LjUuMi4zLiBhbmQgNC41LjQuMS4gYWRkcmVzcyB3aGVuIGFuZCBob3cgdG8gZGlzYWJs
ZQ0KPiA+IG5vbi1DTFVFLWNvbnRyb2xsZWQgbWVkaWEuIFRoZXJlIGlzbid0IGEgaHVnZSBhbW91
bnQgb2YgZGV0YWlsIChJDQo+ID4gcmVtb3ZlZCBhbGwgbm9ybWF0aXZlIGxhbmd1YWdlIGluIHNl
Y3Rpb24gNC41LjIuMy4gYXMgcGFydCBvZiB0aGUgbW9zdA0KPiA+IHJlY2VudCBkcmFmdCB0byBt
YWtlIGNsZWFyIGl0IHdhcyBtZXJlbHkgaWxsdXN0cmF0aXZlKSBidXQgdGhlbiBJJ20NCj4gPiBu
b3Qgc3VyZSB0aGlzIGlzIHNvbWV0aGluZyB3ZSBzaG91bGQgYmUgbWFuZGF0aW5nOyBkaWZmZXJl
bnQNCj4gPiBpbXBsZW1lbnRhdGlvbnMgd2lsbCBsaWtlbHkgaGF2ZSBkaWZmZXJlbnQgb3Bpbmlv
bnMgb24gd2hlbg0KPiA+IG5vbi1DTFVFLWNvbnRyb2xsZWQgbWVkaWEgc2hvdWxkIGJlIGRpc2Fi
bGVkIChzb21lIG1heSBuZXZlciB3YW50IGl0LA0KPiA+IHNvbWUgbWF5IHdhbnQgdG8gY29udGlu
dWUgaXQgdW50aWwgdGhleSBoYXZlIENMVUUtY29udHJvbGxlZCBtZWRpYSkuDQo+ID4NCj4gPiAy
KSBTZWN0aW9uIDQuNS4yLjMuIGRlZmluZXMgd2hlbiBhIGNhbGwgZmFsbHMgYmFjayBmcm9tIENM
VUUtZW5hYmxlZA0KPiA+IHRvIG5vbi1DTFVFIGVuYWJsZWQsIGRlZmluaW5nIGl0IGFzIHRoZSBm
aXJzdCBvZiB0aGUgb3B0aW9ucyB5b3Ugc3VnZ2VzdC4NCj4gPg0KPiA+IENhbiB5b3UgY2hlY2sg
dGhlc2Ugc2VjdGlvbnMsIGFuZCBzYXkgd2hpY2ggb25lcyB5b3UgdGhpbmsgYXJlDQo+ID4gaW5z
dWZmaWNpZW50L3Nob3VsZCBiZSBjaGFuZ2VkPw0KPiA+DQo+ID4gVGhhbmtzLA0KPiA+DQo+ID4g
Um9iDQo+ID4NCj4gPiBPbiAzMC8wOC8xNCAwMzoxNiwgTGl1eWFuIChTY2FybGV0dCkgd3JvdGU6
DQo+ID4+DQo+ID4+IEhlbGxvLA0KPiA+Pg0KPiA+PiAgICAgIEkgaGF2ZSBzb21lIGlzc3VlcyBh
Ym91dCBDTFVFLWVuYWJsZWQgY2FsbOKAmXMgZmFsbGJhY2suDQo+ID4+DQo+ID4+ICAgICAgVGhl
IHNpZ25hbGluZyBkcmFmdCBzYXlzOg0KPiA+Pg0KPiA+PiAgICAgICAgICAgICBBIGNhbGwgaW4g
d2hpY2ggdHdvIENMVUUtY2FwYWJsZSBkZXZpY2VzIGhhdmUNCj4gPj4gc3VjY2Vzc2Z1bGx5IG5l
Z290aWF0ZWQgc3VwcG9ydCBmb3IgYSBDTFVFIGRhdGEgY2hhbm5lbCBpbiBTRFAuDQo+ID4+DQo+
ID4+IEEgQ0xVRS1lbmFibGVkIGNhbGwgaXMgbm90IG5lY2Vzc2FyaWx5IGltbWVkaWF0ZWx5IGFi
bGUgdG8gc2VuZA0KPiA+PiBDTFVFLWNvbnRyb2xsZWQgbWVkaWE7IG5lZ290aWF0aW9uIG9mIHRo
ZSBkYXRhIGNoYW5uZWwgYW5kIG9mIHRoZQ0KPiA+PiBDTFVFIHByb3RvY29sIG11c3QgY29tcGxl
dGUgZmlyc3QNCj4gPj4NCj4gPj4gICAgICAgICAgQnV0IHRoZSBzaWduYWxpbmcgZG9lcyBub3Qg
c2F5IHNvbWV0aGluZyBhcyBiZWxvdzoNCj4gPj4NCj4gPj4gMSlXaGVuIGFuZCBob3cgdG8gc3Rv
cCB0aGUgYmFzaWMgbWVkaWEgc3RyZWFtcz8NCj4gPj4NCj4gPj4gd2FpdCBhbmQgdW50aWwgdGhl
IHR3byBDTFVFLWNhcGFibGUgZGV2aWNlIGZpbmlzaCB0aGUgbmVnb3RpYXRpb24gYW5kDQo+ID4+
IHVzZSDigJxhPWluYWN0aXZl4oCdIG9yIHNldCB0aGUgcG9ydCBudW1iZXIgemVybyByZWxhdGVk
IHRvIHRoZSBiYXNpYw0KPiA+PiBtZWRpYSBzdHJlYW1zDQo+ID4+DQo+ID4+IDIpV2hlbiBhbmQg
aG93IHRvIHRyaWdnZXIgYSBDTFVFLWVuYWJsZWQgY2FsbCBmYWxsIGJhY2s/DQo+ID4+DQo+ID4+
IHRoZSBkYXRhIGNoYW5uZWwgaXMgZXhwbGljaXRseSBjbG9zZWQgYnkgU0RQIE8vQSA7DQo+ID4+
DQo+ID4+IHRoZSBkYXRhIGNoYW5uZWwgaXMgY2xvc2VkIGJ5IFNDVFAgU1NOIFJlc2V0IChzZWUg
dGhlIGRyYWZ0DQo+ID4+IGRyYWZ0LWlldGYtcnRjd2ViLWRhdGEtcHJvdG9jb2wtMDMpIDtvcg0K
PiA+Pg0KPiA+PiB0aGUgYWxsIENMVUUtY29udHJvbGxlZCBtZWRpYSBzdHJlYW1zIGFyZSByZW1v
dmVkIGJ5IFNEUCBPL0ENCj4gPj4NCj4gPj4gICAgICBUaGF04oCZcyBhbGwgYW5kIGNvbW1lbnRz
IHdlbGNvbWUuDQo+ID4+DQo+ID4+IEJlc3QgUmVnYXJkcywNCj4gPj4NCj4gPj4gU2NhcmxldHQN
Cj4gPj4NCj4gPj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4+IC0tLQ0KPiA+Pg0KPiA+Pg0KPiA+PiDljY7k
uLrmioDmnK/mnInpmZAg5YWs5Y+4SHVhd2VpIFRlY2hub2xvZ2llcyBDby4sIEx0ZC4NCj4gPj4N
Cj4gPj4NCj4gPj4gUGhvbmU6IDAwODYtNzU1LTI4OTc0Mjg5DQo+ID4+IEZheDoNCj4gPj4gTW9i
aWxlOg0KPiA+PiBFbWFpbDogc2NhcmxldHQubGl1eWFuQGh1YXdlaS5jb20NCj4gPj4g5Zyw5Z2A
77ya5rex5Zyz5biCIOm+meWyl+WMuuWdgueUsOWNjuS4uuWfuuWcsCDpgq7nvJbvvJo1MTgxMjkN
Cj4gPj4gSHVhd2VpIFRlY2hub2xvZ2llcyBDby4sIEx0ZC4NCj4gPj4gQmFudGlhbiwgTG9uZ2dh
bmcgRGlzdHJpY3QsU2hlbnpoZW4gNTE4MTI5LCBQLlIuQ2hpbmENCj4gPj4gaHR0cDovL3d3dy5o
dWF3ZWkuY29tDQo+ID4+DQo+ID4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+PiAtLS0NCj4gPj4NCj4gPj4g
5pys6YKu5Lu25Y+K5YW26ZmE5Lu25ZCrIOacieWNjuS4uuWFrOWPuOeahOS/neWvhuS/oeaBr++8
jOS7hemZkOS6juWPkemAgee7meS4iumdouWcsOWdgOS4rQ0KPiDliJflh7rnmoTkuKoNCj4gPj4g
5Lq65oiW576k57uE44CC56aBDQo+ID4+IOatouS7u+S9leWFtuS7luS6uuS7peS7u+S9leW9ouW8
j+S9v+eUqO+8iOWMheaLrOS9huS4jemZkOS6juWFqOmDqOaIlumDqOWIhuWcsOazhOmcsuOAgeWk
jQ0KPiDliLbjgIHmiJbmlaMNCj4gPj4g5Y+R77yJ5pys6YKu5Lu25LitDQo+ID4+IOeahOS/oeaB
r+OAguWmguaenOaCqOmUmeaUtuS6huacrOmCruS7tu+8jOivt+aCqOeri+WNs+eUteivneaIlumC
ruS7tumAmuefpeWPkeS7tuS6uuW5tuWIoA0KPiDpmaTmnKzpgq7ku7bvvIENCj4gPj4gVGhpcyBl
LW1haWwgYW5kIGl0cyBhdHRhY2htZW50cyBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlv
biBmcm9tDQo+ID4+IEhVQVdFSSwgd2hpY2ggaXMgaW50ZW5kZWQgb25seSBmb3IgdGhlIHBlcnNv
biBvciBlbnRpdHkgd2hvc2UgYWRkcmVzcw0KPiA+PiBpcyBsaXN0ZWQgYWJvdmUuIEFueSB1c2Ug
b2YgdGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBoZXJlaW4gaW4gYW55DQo+ID4+IHdheSAoaW5j
bHVkaW5nLCBidXQgbm90IGxpbWl0ZWQgdG8sIHRvdGFsIG9yIHBhcnRpYWwgZGlzY2xvc3VyZSwN
Cj4gPj4gcmVwcm9kdWN0aW9uLCBvciBkaXNzZW1pbmF0aW9uKSBieSBwZXJzb25zIG90aGVyIHRo
YW4gdGhlIGludGVuZGVkDQo+ID4+IHJlY2lwaWVudChzKSBpcyBwcm9oaWJpdGVkLiBJZiB5b3Ug
cmVjZWl2ZSB0aGlzIGUtbWFpbCBpbiBlcnJvciwNCj4gPj4gcGxlYXNlIG5vdGlmeSB0aGUgc2Vu
ZGVyIGJ5IHBob25lIG9yIGVtYWlsIGltbWVkaWF0ZWx5IGFuZCBkZWxldGUgaXQhDQo+ID4+DQo+
ID4+DQo+ID4+DQo+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQo+ID4+IGNsdWUgbWFpbGluZyBsaXN0DQo+ID4+IGNsdWVAaWV0Zi5vcmcNCj4gPj4g
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9jbHVlDQo+ID4NCj4gPg0KPiA+
DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4g
PiBjbHVlIG1haWxpbmcgbGlzdA0KPiA+IGNsdWVAaWV0Zi5vcmcNCj4gPiBodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2NsdWUNCj4gPg0KPiANCj4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gY2x1ZSBtYWlsaW5nIGxpc3QNCj4g
Y2x1ZUBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2Ns
dWUNCg==


From nobody Thu Sep  4 01:11:09 2014
Return-Path: <scarlett.liuyan@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E49911A004D for <clue@ietfa.amsl.com>; Thu,  4 Sep 2014 01:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.269
X-Spam-Level: 
X-Spam-Status: No, score=-4.269 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rq9RKGQ-fsf9 for <clue@ietfa.amsl.com>; Thu,  4 Sep 2014 01:11:03 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E3161A0079 for <clue@ietf.org>; Thu,  4 Sep 2014 01:11:03 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJB19399; Thu, 04 Sep 2014 08:11:01 +0000 (GMT)
Received: from SZXEMA404-HUB.china.huawei.com (10.82.72.36) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 4 Sep 2014 09:11:00 +0100
Received: from SZXEMA503-MBX.china.huawei.com ([169.254.5.91]) by SZXEMA404-HUB.china.huawei.com ([10.82.72.36]) with mapi id 14.03.0158.001; Thu, 4 Sep 2014 16:10:57 +0800
From: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>
To: Robert Hansen <rohanse2@cisco.com>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] CLUE-enabled call's fallback
Thread-Index: Ac/D+GittEPNbekRSra4ryOrQuay7ABtCKsAAAQAmgAAAhi+AACToZIg
Date: Thu, 4 Sep 2014 08:10:56 +0000
Message-ID: <E97C33E5D67C2843AFA535DE2E5B80C1573F1AA5@SZXEMA503-MBX.china.huawei.com>
References: <E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com> <54048034.6000708@cisco.com> <54049B10.8090607@alum.mit.edu> <5404A922.70509@cisco.com>
In-Reply-To: <5404A922.70509@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.63.147.208]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/X-pY9BPkoOsCt2_kLVjcnBfziTc
Subject: Re: [clue] CLUE-enabled call's fallback
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 08:11:06 -0000

SGkgUm9iLA0KDQoJUGxlYXNlIHNlZSBteSByZXBsaWVzIGJlbG93IGFuZCB0aGFua3MuDQoNCkJl
c3QgUmVnYXJkcywNClNjYXJsZXR0DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4g
RnJvbTogY2x1ZSBbbWFpbHRvOmNsdWUtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFJv
YmVydCBIYW5zZW4NCj4gU2VudDogVHVlc2RheSwgU2VwdGVtYmVyIDAyLCAyMDE0IDE6MTMgQU0N
Cj4gVG86IGNsdWVAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtjbHVlXSBDTFVFLWVuYWJsZWQg
Y2FsbCdzIGZhbGxiYWNrDQo+IA0KPiBIaSBQYXVsLA0KPiANCj4gSSdtIGRlZmluaXRlbHkgb2Yg
dGhlIG9waW5pb24gdGhhdCB0aG9zZSB3aG8gYXJlIHdpbGxpbmcgdG8gdXBncmFkZSBhIGNhbGwg
dG8NCj4gQ0xVRS1lbmFibGVkIHNob3VsZCBpbmNsdWRlIGEgZGF0YSBjaGFubmVsIG0tbGluZSwg
anVzdCBsaWtlIGNvbWluZyBvZmYgaG9sZA0KPiB3aXRoIG1lZGlhLiBTZWN0aW9uIDQuNS40LjIu
IGhhcyB0aGUgZm9sbG93aW5nIGxhbmd1YWdlOg0KPiANCj4gIkEgQ0xVRS1jYXBhYmxlIGRldmlj
ZSB0aGF0IHJlY2VpdmVzIGFuIGluaXRpYWwgU0RQIG9mZmVyIGZyb20gYSBub24tQ0xVRQ0KPiBk
ZXZpY2UgU0hPVUxEIGluY2x1ZGUgYSBuZXcgZGF0YSBjaGFubmVsICJtIiBsaW5lIGFuZCBjb3Jy
ZXNwb25kaW5nIENMVUUNCj4gZ3JvdXAgaW4gYW55IHN1YnNlcXVlbnQgb2ZmZXJzIGl0IHNlbmRz
LCB0byBpbmRpY2F0ZSB0aGF0IGl0IGlzIENMVUUtY2FwYWJsZS4iDQpbU2NhcmxldHRdIEkgYW0g
Y29uZnVzZWQgYWJvdXQgaXQuIFRoZSBDTFVFLWNhcGFibGUgZGV2aWNlIGNhbiBpbmNsdWRlIHRo
ZSBtZWRpYSBmZWF0dXJlIHRhZyB0byBpbmRpY2F0ZSBzdXBwb3J0IGZvciBDTFVFIGluIHRoZSBT
SVAgSU5WSVRFIGFuZCBVUERBVEUgcmVxdWVzdHMgYW5kIHJlc3BvbnNlcy4NCldoeSBkb2VzIGl0
IHlldCBuZWVkIHRvIGluY2x1ZGUgYSBuZXcgZGF0YSBjaGFubmVsICJtIiBsaW5lIHRvIGluZGlj
YXRlIHN1cHBvcnQgZm9yIENMVUUgaW4gYW55IHN1YnNlcXVlbnQuIA0KTWF5YmUgeW91IG1lYW4g
aW4gaGVyZSB0aGF0IGl0IHdhbnRzIHRvIGVzdGFibGlzaCBhIENMVUUtZW5hYmxlIGNhbGwgb3Ig
dXBncmFkZSBhIENMVUUtZW5hYmxlIGNhbGwsIG5vdCBidXQgaW5kaWNhdGVzIENMVUUtY2FwYWJs
ZS4NCj4gDQo+IEkgc3VwcG9zZSB0aGlzIHNob3VsZCBiZSBleHBhbmRlZCB0byBhbHNvIGNvdmVy
IGNhc2VzIHdoZXJlIHRoZSBjYWxsIHdhcw0KPiBDTFVFLWVuYWJsZWQgYnV0IHRoZW4gZG93bmdy
YWRlZCwgYXMgYXQgdGhlIG1vbWVudCBpdCBvbmx5IHRhbGtzIGFib3V0DQo+IGNhbGxzIHRoYXQg
d2VyZSBub24tQ0xVRSBmcm9tIHRoZSBiZWdpbm5pbmcuDQoNCj4gDQo+IFJvYg0KPiANCj4gT24g
MDEvMDkvMTQgMTc6MTMsIFBhdWwgS3l6aXZhdCB3cm90ZToNCj4gPiBSb2IsIFNjYXJsZXR0LA0K
PiA+DQo+ID4gVGhlcmUgaXMgb25lIHRoaW5nIHRoYXQgSSBhbSBjb25jZXJuZWQgd2l0aDoNCj4g
Pg0KPiA+IEkgc2VlIGFuIGFuYWxvZ3kgYmV0d2VlbiBtb3ZpbmcgdG8vZnJvbSBjbHVlLWVuYWJs
ZWQgc3RhdHVzIGFuZCBtb3ZpbmcNCj4gPiB0by9mcm9tIGhvbGQgc3RhdHVzLiBXaXRoIGhvbGQs
IGlmIHlvdSBhcmVuJ3QgY2FyZWZ1bCBpdCBpcyBwb3NzaWJsZQ0KPiA+IHRvIGdldCBpbnRvIGEg
InN0dWNrIG9uIGhvbGQiIHN0YXR1cy4gU2ltaWxhcmx5LCBJIHRoaW5rIGlmIHdlIGFyZW4ndA0K
PiA+IGNhcmVmdWwgaXQgd2lsbCBiZSBwb3NzaWJsZSB0byBnZXQgaW50byBhICJzdHVjayBpbiBj
bHVlLWRpc2FibGVkIg0KPiA+IHN0YXR1cy4NCj4gPg0KPiA+IFRoZSAic3R1Y2sgb24gaG9sZCIg
YXJpc2VzIHdoZW4gYm90aCBlbmRzIGhhdmUgcHV0IHRoZSBjYWxsIG9uIGhvbGQNCj4gPiBhPWlu
YWN0aXZlIGhhcyBiZWVuIG5lZ290aWF0ZWQuIEl0IG9jY3VycyBpZiBvbmUgZW5kIHdhbnRzIHRv
IGdvIG9mZg0KPiA+IGhvbGQsIGJ1dCBjb250aW51ZXMgdG8gb2ZmZXIgYT1pbmFjdGl2ZSBiZWNh
dXNlIGl0IHRoaW5rcyB0aGUgb3RoZXINCj4gPiBlbmQgd2FudHMgdG8gYmUgb24gaG9sZC4gSXQg
aXMgZml4ZWQgYnkgYSBwb2xpY3kgd2hlcmUgZWFjaCBlbmQgbWFrZXMNCj4gPiBubyBhc3N1bXB0
aW9ucyBhYm91dCB3aGF0IHRoZSBvdGhlciBlbmQgd2FudHMgaW4gdGhlIGZ1dHVyZSB3aGVuIGl0
DQo+ID4gbWFrZXMgb2ZmZXJzIC0gb2ZmZXJpbmcgd2hhdCBpdCB3YW50cyBmb3IgaXRzZWxmLiBB
bmQgdGhpcyBuZWVkcyB0byBiZQ0KPiA+IHRydWUgd2hlbiByZXNwb25kaW5nIHRvIG9mZmVybGVz
cyBpbnZpdGVzIHRvby4NCj4gPg0KPiA+IFRoZSBxdWVzdGlvbiBpcyB3aGV0aGVyIHdlIGhhdmUg
c3VjaCBpc3N1ZXMgd2l0aCBjbHVlLWVuYWJsZW1lbnQuDQo+ID4NCj4gPiBDb25zaWRlciB0aGUg
Zm9sbG93aW5nLCBiZXR3ZWVuIEFsaWNlIGFuZCBCb2I6DQo+ID4NCj4gPiAtIEFsaWNlIGNhbGxz
IEJvYiwgb2ZmZXJpbmcgQ0xVRSBzdXBwb3J0IGNsdWUgZ3JvdXAgY29udGFpbmluZyBzY3RwLg0K
PiA+IC0gQm9iIGlzIGNsdWUtY2FwYWJsZSwgYnV0IGNhbid0IGluaXRpYWxseSBlbmFibGUgaXQu
DQo+ID4gICAoRS5nLiwgY2VsbCBwaG9uZSBvbiBzbG93IGxpbmsuKSBTbyByZWZ1c2VzIHRoZSBT
Q1RQLg0KPiA+DQo+ID4gVGhlIHF1ZXN0aW9uIGlzIHdoYXQgaGFwcGVucyBzdWJzZXF1ZW50bHku
IElmIEFsaWNlIGhhcyByZWFzb24gdG8gc2VuZA0KPiA+IGFuIG9mZmVyIGluIHRoZSBmdXR1cmUs
IHNob3VsZCBzaGUgYWdhaW4gb2ZmZXIgdGhlIGNsdWUgY2hhbm5lbD8gT3INCj4gPiBzaG91bGQg
c2hlIGFzc3VtZSB0aGF0IGl0IGlzIHVwIHRvIEJvYiB0byB0YWtlIHRoZSBpbml0aWF0aXZlIGlu
DQo+ID4gZW5hYmxpbmcgQ0xVRT8gKFRoZXJlIG1heSBiZSBhIGNvc3QgYXNzb2NpYXRlZCBvZmZl
cmluZyB0aGUgY2x1ZQ0KPiA+IGNoYW5uZWwsIGluIElDRSwgRFRMUywgZXRjLikNCj4gPg0KPiA+
IFRoZSBzYWZlc3QgYW5zd2VyIGlzIHRvIHNheSB0aGF0IHdoZW5ldmVyIGEgY2x1ZS1jYXBhYmxl
IGVuZHBvaW50DQo+ID4gc2VuZHMgYW4gb2ZmZXIsIGFuZCBpcyB3aWxsaW5nL2FibGUgdG8gYmUg
Y2x1ZS1lbmFibGVkLCBpdCBzaG91bGQNCj4gPiBvZmZlciB0aGUgU0NUUCBtLWxpbmUuDQo+ID4N
Cj4gPiBXZSBjb3VsZCBleHBsb3JlIGxlc3MgYWdncmVzc2l2ZSBhcHByb2FjaGVzLiBCdXQgdGhl
biB3ZSBtdXN0IGxvb2sNCj4gPiB2ZXJ5IGNhcmVmdWxseSAtIHRoZSBjYXNlcyB0aGF0IGNhdXNl
IHRyb3VibGUgYXJlIG9mdGVuIHN1YnRsZSwNCj4gPiBpbnZvbHZpbmcgb2ZmZXJsZXNzIGludml0
ZXMsIEIyQlVBcywgZXRjLg0KPiA+DQo+ID4gICAgIFRoYW5rcywNCj4gPiAgICAgUGF1bA0KPiA+
DQo+ID4gT24gOS8xLzE0IDEwOjE4IEFNLCBSb2JlcnQgSGFuc2VuIHdyb3RlOg0KPiA+PiBIaSBT
Y2FybGV0dCwNCj4gPj4NCj4gPj4gMSkgU2VjdGlvbiA0LjUuMi4zLiBhbmQgNC41LjQuMS4gYWRk
cmVzcyB3aGVuIGFuZCBob3cgdG8gZGlzYWJsZQ0KPiA+PiBub24tQ0xVRS1jb250cm9sbGVkIG1l
ZGlhLiBUaGVyZSBpc24ndCBhIGh1Z2UgYW1vdW50IG9mIGRldGFpbCAoSQ0KPiA+PiByZW1vdmVk
IGFsbCBub3JtYXRpdmUgbGFuZ3VhZ2UgaW4gc2VjdGlvbiA0LjUuMi4zLiBhcyBwYXJ0IG9mIHRo
ZQ0KPiA+PiBtb3N0IHJlY2VudCBkcmFmdCB0byBtYWtlIGNsZWFyIGl0IHdhcyBtZXJlbHkgaWxs
dXN0cmF0aXZlKSBidXQgdGhlbg0KPiA+PiBJJ20gbm90IHN1cmUgdGhpcyBpcyBzb21ldGhpbmcg
d2Ugc2hvdWxkIGJlIG1hbmRhdGluZzsgZGlmZmVyZW50DQo+ID4+IGltcGxlbWVudGF0aW9ucyB3
aWxsIGxpa2VseSBoYXZlIGRpZmZlcmVudCBvcGluaW9ucyBvbiB3aGVuDQo+ID4+IG5vbi1DTFVF
LWNvbnRyb2xsZWQgbWVkaWEgc2hvdWxkIGJlIGRpc2FibGVkIChzb21lIG1heSBuZXZlciB3YW50
IGl0LA0KPiA+PiBzb21lIG1heSB3YW50IHRvIGNvbnRpbnVlIGl0IHVudGlsIHRoZXkgaGF2ZSBD
TFVFLWNvbnRyb2xsZWQgbWVkaWEpLg0KPiA+Pg0KPiA+PiAyKSBTZWN0aW9uIDQuNS4yLjMuIGRl
ZmluZXMgd2hlbiBhIGNhbGwgZmFsbHMgYmFjayBmcm9tIENMVUUtZW5hYmxlZA0KPiA+PiB0byBu
b24tQ0xVRSBlbmFibGVkLCBkZWZpbmluZyBpdCBhcyB0aGUgZmlyc3Qgb2YgdGhlIG9wdGlvbnMg
eW91IHN1Z2dlc3QuDQo+ID4+DQo+ID4+IENhbiB5b3UgY2hlY2sgdGhlc2Ugc2VjdGlvbnMsIGFu
ZCBzYXkgd2hpY2ggb25lcyB5b3UgdGhpbmsgYXJlDQo+ID4+IGluc3VmZmljaWVudC9zaG91bGQg
YmUgY2hhbmdlZD8NCj4gPj4NCj4gPj4gVGhhbmtzLA0KPiA+Pg0KPiA+PiBSb2INCj4gPj4NCj4g
Pj4gT24gMzAvMDgvMTQgMDM6MTYsIExpdXlhbiAoU2NhcmxldHQpIHdyb3RlOg0KPiA+Pj4NCj4g
Pj4+IEhlbGxvLA0KPiA+Pj4NCj4gPj4+ICAgICAgSSBoYXZlIHNvbWUgaXNzdWVzIGFib3V0IENM
VUUtZW5hYmxlZCBjYWxs4oCZcyBmYWxsYmFjay4NCj4gPj4+DQo+ID4+PiAgICAgIFRoZSBzaWdu
YWxpbmcgZHJhZnQgc2F5czoNCj4gPj4+DQo+ID4+PiAgICAgICAgICAgICBBIGNhbGwgaW4gd2hp
Y2ggdHdvIENMVUUtY2FwYWJsZSBkZXZpY2VzIGhhdmUNCj4gPj4+IHN1Y2Nlc3NmdWxseSBuZWdv
dGlhdGVkIHN1cHBvcnQgZm9yIGEgQ0xVRSBkYXRhIGNoYW5uZWwgaW4gU0RQLg0KPiA+Pj4NCj4g
Pj4+IEEgQ0xVRS1lbmFibGVkIGNhbGwgaXMgbm90IG5lY2Vzc2FyaWx5IGltbWVkaWF0ZWx5IGFi
bGUgdG8gc2VuZA0KPiA+Pj4gQ0xVRS1jb250cm9sbGVkIG1lZGlhOyBuZWdvdGlhdGlvbiBvZiB0
aGUgZGF0YSBjaGFubmVsIGFuZCBvZiB0aGUNCj4gPj4+IENMVUUgcHJvdG9jb2wgbXVzdCBjb21w
bGV0ZSBmaXJzdA0KPiA+Pj4NCj4gPj4+ICAgICAgICAgIEJ1dCB0aGUgc2lnbmFsaW5nIGRvZXMg
bm90IHNheSBzb21ldGhpbmcgYXMgYmVsb3c6DQo+ID4+Pg0KPiA+Pj4gMSlXaGVuIGFuZCBob3cg
dG8gc3RvcCB0aGUgYmFzaWMgbWVkaWEgc3RyZWFtcz8NCj4gPj4+DQo+ID4+PiB3YWl0IGFuZCB1
bnRpbCB0aGUgdHdvIENMVUUtY2FwYWJsZSBkZXZpY2UgZmluaXNoIHRoZSBuZWdvdGlhdGlvbg0K
PiA+Pj4gYW5kIHVzZSDigJxhPWluYWN0aXZl4oCdIG9yIHNldCB0aGUgcG9ydCBudW1iZXIgemVy
byByZWxhdGVkIHRvIHRoZQ0KPiA+Pj4gYmFzaWMgbWVkaWEgc3RyZWFtcw0KPiA+Pj4NCj4gPj4+
IDIpV2hlbiBhbmQgaG93IHRvIHRyaWdnZXIgYSBDTFVFLWVuYWJsZWQgY2FsbCBmYWxsIGJhY2s/
DQo+ID4+Pg0KPiA+Pj4gdGhlIGRhdGEgY2hhbm5lbCBpcyBleHBsaWNpdGx5IGNsb3NlZCBieSBT
RFAgTy9BIDsNCj4gPj4+DQo+ID4+PiB0aGUgZGF0YSBjaGFubmVsIGlzIGNsb3NlZCBieSBTQ1RQ
IFNTTiBSZXNldCAoc2VlIHRoZSBkcmFmdA0KPiA+Pj4gZHJhZnQtaWV0Zi1ydGN3ZWItZGF0YS1w
cm90b2NvbC0wMykgO29yDQo+ID4+Pg0KPiA+Pj4gdGhlIGFsbCBDTFVFLWNvbnRyb2xsZWQgbWVk
aWEgc3RyZWFtcyBhcmUgcmVtb3ZlZCBieSBTRFAgTy9BDQo+ID4+Pg0KPiA+Pj4gICAgICBUaGF0
4oCZcyBhbGwgYW5kIGNvbW1lbnRzIHdlbGNvbWUuDQo+ID4+Pg0KPiA+Pj4gQmVzdCBSZWdhcmRz
LA0KPiA+Pj4NCj4gPj4+IFNjYXJsZXR0DQo+ID4+Pg0KPiA+Pj4gLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPj4+
IC0tLS0NCj4gPj4+DQo+ID4+Pg0KPiA+Pj4NCj4gPj4+IOWNjuS4uuaKgOacr+aciemZkCDlhazl
j7hIdWF3ZWkgVGVjaG5vbG9naWVzIENvLiwgTHRkLg0KPiA+Pj4NCj4gPj4+DQo+ID4+PiBQaG9u
ZTogMDA4Ni03NTUtMjg5NzQyODkNCj4gPj4+IEZheDoNCj4gPj4+IE1vYmlsZToNCj4gPj4+IEVt
YWlsOiBzY2FybGV0dC5saXV5YW5AaHVhd2VpLmNvbQ0KPiA+Pj4g5Zyw5Z2A77ya5rex5Zyz5biC
IOm+meWyl+WMuuWdgueUsOWNjuS4uuWfuuWcsCDpgq7nvJbvvJo1MTgxMjkNCj4gPj4+IEh1YXdl
aSBUZWNobm9sb2dpZXMgQ28uLCBMdGQuDQo+ID4+PiBCYW50aWFuLCBMb25nZ2FuZyBEaXN0cmlj
dCxTaGVuemhlbiA1MTgxMjksIFAuUi5DaGluYQ0KPiA+Pj4gaHR0cDovL3d3dy5odWF3ZWkuY29t
DQo+ID4+Pg0KPiA+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPj4+IC0tLS0NCj4gPj4+DQo+ID4+Pg0KPiA+
Pj4g5pys6YKu5Lu25Y+K5YW26ZmE5Lu25ZCrIOacieWNjuS4uuWFrOWPuOeahOS/neWvhuS/oeaB
r++8jOS7hemZkOS6juWPkemAgee7meS4iumdouWcsOWdgA0KPiDkuK3liJflh7rnmoTkuKoNCj4g
Pj4+IOS6uuaIlue+pOe7hOOAguemgQ0KPiA+Pj4g5q2i5Lu75L2V5YW25LuW5Lq65Lul5Lu75L2V
5b2i5byP5L2/55So77yI5YyF5ous5L2G5LiN6ZmQ5LqO5YWo6YOo5oiW6YOo5YiG5Zyw5rOE6Zyy
44CB5aSNDQo+IOWItuOAgeaIluaVow0KPiA+Pj4g5Y+R77yJ5pys6YKu5Lu25LitDQo+ID4+PiDn
moTkv6Hmga/jgILlpoLmnpzmgqjplJnmlLbkuobmnKzpgq7ku7bvvIzor7fmgqjnq4vljbPnlLXo
r53miJbpgq7ku7bpgJrnn6Xlj5Hku7bkurrlubbliKANCj4g6Zmk5pys6YKu5Lu277yBDQo+ID4+
PiBUaGlzIGUtbWFpbCBhbmQgaXRzIGF0dGFjaG1lbnRzIGNvbnRhaW4gY29uZmlkZW50aWFsIGlu
Zm9ybWF0aW9uDQo+ID4+PiBmcm9tIEhVQVdFSSwgd2hpY2ggaXMgaW50ZW5kZWQgb25seSBmb3Ig
dGhlIHBlcnNvbiBvciBlbnRpdHkgd2hvc2UNCj4gPj4+IGFkZHJlc3MgaXMgbGlzdGVkIGFib3Zl
LiBBbnkgdXNlIG9mIHRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaGVyZWluDQo+ID4+PiBpbiBh
bnkgd2F5IChpbmNsdWRpbmcsIGJ1dCBub3QgbGltaXRlZCB0bywgdG90YWwgb3IgcGFydGlhbA0K
PiA+Pj4gZGlzY2xvc3VyZSwgcmVwcm9kdWN0aW9uLCBvciBkaXNzZW1pbmF0aW9uKSBieSBwZXJz
b25zIG90aGVyIHRoYW4NCj4gPj4+IHRoZSBpbnRlbmRlZA0KPiA+Pj4gcmVjaXBpZW50KHMpIGlz
IHByb2hpYml0ZWQuIElmIHlvdSByZWNlaXZlIHRoaXMgZS1tYWlsIGluIGVycm9yLA0KPiA+Pj4g
cGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGJ5IHBob25lIG9yIGVtYWlsIGltbWVkaWF0ZWx5IGFu
ZCBkZWxldGUNCj4gPj4+IGl0IQ0KPiA+Pj4NCj4gPj4+DQo+ID4+Pg0KPiA+Pj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj4+IGNsdWUgbWFpbGlu
ZyBsaXN0DQo+ID4+PiBjbHVlQGlldGYub3JnDQo+ID4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2NsdWUNCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj4gY2x1ZSBtYWlsaW5nIGxp
c3QNCj4gPj4gY2x1ZUBpZXRmLm9yZw0KPiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2NsdWUNCj4gPj4NCj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+ID4gY2x1ZSBtYWlsaW5nIGxpc3QNCj4gPiBjbHVlQGll
dGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9jbHVlDQo+
IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBj
bHVlIG1haWxpbmcgbGlzdA0KPiBjbHVlQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vY2x1ZQ0K


From nobody Thu Sep  4 12:52:45 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A248B1A00AB for <clue@ietfa.amsl.com>; Thu,  4 Sep 2014 12:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_18=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WAFaDXmQnRm0 for <clue@ietfa.amsl.com>; Thu,  4 Sep 2014 12:52:40 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id CDE691A004E for <clue@ietf.org>; Thu,  4 Sep 2014 12:52:39 -0700 (PDT)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta01.westchester.pa.mail.comcast.net with comcast id n6uh1o0070EZKEL517sf0n; Thu, 04 Sep 2014 19:52:39 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta01.westchester.pa.mail.comcast.net with comcast id n7se1o00i3Ge9ey3M7sfND; Thu, 04 Sep 2014 19:52:39 +0000
Message-ID: <5408C306.8030107@alum.mit.edu>
Date: Thu, 04 Sep 2014 15:52:38 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>,  "clue@ietf.org" <clue@ietf.org>
References: <E97C33E5D67C2843AFA535DE2E5B80C1573F1699@SZXEMA503-MBX.china.huawei.com> <54048034.6000708@cisco.com> <54049B10.8090607@alum.mit.edu> <E97C33E5D67C2843AFA535DE2E5B80C1573F1A88@SZXEMA503-MBX.china.huawei.com>
In-Reply-To: <E97C33E5D67C2843AFA535DE2E5B80C1573F1A88@SZXEMA503-MBX.china.huawei.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1409860359; bh=zLHhb2RMfNYPWrg7KXc6NwVQ21aIoAU6VQkCXTs5fzk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=RZ57yzxdFyFrYircZr4NvPGziGYVe+zrSvAZE7xucd23riGTBX6aUpsCweHAylWdd aZupANvUAbrLtaUoJXTsL/T6jDmE+LO4uMENtsI90ORqXzMO6aGQKOG7Jc2yHeDPMh divoB+vkhP1iD1uY1dCqGfC7lMmeukWps6b6F4zBm1ET4ZSTWRyCw6ZSBDKkgkyrcg 65ZVFcXN1ONldy4/InpyfwqBRgKicCCDtzt4iSNUJFc/8xsoJ+ZnZtcwT6PPed2XGM GTOYLFJhhLiR+8W6eHUr4x4fXm0UuMbpe8+ahIXVa0qqt6QM5qdoAM9t0m6vc71SEX ccImu1OZhQekQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/JlTR_jECo7P5HyE3uxuI9xQbaFg
Subject: Re: [clue] CLUE-enabled call's fallback
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 19:52:41 -0000

On 9/4/14 3:39 AM, Liuyan (Scarlett) wrote:
> Hi Paul,
>
> 	Maybe we ignore the media feature tag indicating support for CLUE.
> 	Please see my replies below and thanks.

We must be careful. The feature tag indicates clue-capable, but not 
clue-enabled.

And perhaps even clue-capable isn't quite right - maybe it should 
indicate clue-aware.

The reason I make the distinction is that the device might have all the 
software necessary to do clue, but sometimes it might lack some of the 
resources necessary to do so. And the resource availability might change 
mid-call.

> Best Regards
> Scarlett
>
>> -----Original Message-----
>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Paul Kyzivat
>> Sent: Tuesday, September 02, 2014 12:13 AM
>> To: clue@ietf.org
>> Subject: Re: [clue] CLUE-enabled call's fallback
>>
>> Rob, Scarlett,
>>
>> There is one thing that I am concerned with:
>>
>> I see an analogy between moving to/from clue-enabled status and moving
>> to/from hold status. With hold, if you aren't careful it is possible to get into a
>> "stuck on hold" status. Similarly, I think if we aren't careful it will be possible
>> to get into a "stuck in clue-disabled" status.
>>
>> The "stuck on hold" arises when both ends have put the call on hold
>> a=inactive has been negotiated. It occurs if one end wants to go off hold, but
>> continues to offer a=inactive because it thinks the other end wants to be on
>> hold. It is fixed by a policy where each end makes no assumptions about
>> what the other end wants in the future when it makes offers - offering what
>> it wants for itself. And this needs to be true when responding to offerless
>> invites too.
>>
>> The question is whether we have such issues with clue-enablement.
>>
>> Consider the following, between Alice and Bob:
>>
>> - Alice calls Bob, offering CLUE support clue group containing sctp.
>> - Bob is clue-capable, but can't initially enable it.
>>     (E.g., cell phone on slow link.) So refuses the SCTP.
> [Scarlett] In the above example, you mean that Bob does not include the m line for a clue data channel.

Bob is the answerer. He can't omit the m-line.
He either sets port to zero or sets a=inactive.

> My question is whether Bob includes the "sip.clue" media tag feature or not.
> If Bob includes the "sip.clue" media tag feature, Alice can know that Bob supports for CLUE.

I think Bob continues to include the feature tag, meaning he is 
"capable" (or "aware") even though he is unwilling to *enable* clue 
right now.

> Accordingly, Alice can offer a clue data channel again or Bob forwardly offer a clue data channel in the future.
> If Bob does not include it, Alice SHOULD not offer a clue data channel again.

Certainly we could *consider* using the feature tag that way.

	Thanks,
	Paul

>> The question is what happens subsequently. If Alice has reason to send an
>> offer in the future, should she again offer the clue channel? Or should she
>> assume that it is up to Bob to take the initiative in enabling CLUE? (There
>> may be a cost associated offering the clue channel, in ICE, DTLS, etc.)
>>
>> The safest answer is to say that whenever a clue-capable endpoint sends an
>> offer, and is willing/able to be clue-enabled, it should offer the SCTP m-line.
>>
>> We could explore less aggressive approaches. But then we must look very
>> carefully - the cases that cause trouble are often subtle, involving offerless
>> invites, B2BUAs, etc.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 9/1/14 10:18 AM, Robert Hansen wrote:
>>> Hi Scarlett,
>>>
>>> 1) Section 4.5.2.3. and 4.5.4.1. address when and how to disable
>>> non-CLUE-controlled media. There isn't a huge amount of detail (I
>>> removed all normative language in section 4.5.2.3. as part of the most
>>> recent draft to make clear it was merely illustrative) but then I'm
>>> not sure this is something we should be mandating; different
>>> implementations will likely have different opinions on when
>>> non-CLUE-controlled media should be disabled (some may never want it,
>>> some may want to continue it until they have CLUE-controlled media).
>>>
>>> 2) Section 4.5.2.3. defines when a call falls back from CLUE-enabled
>>> to non-CLUE enabled, defining it as the first of the options you suggest.
>>>
>>> Can you check these sections, and say which ones you think are
>>> insufficient/should be changed?
>>>
>>> Thanks,
>>>
>>> Rob
>>>
>>> On 30/08/14 03:16, Liuyan (Scarlett) wrote:
>>>>
>>>> Hello,
>>>>
>>>>       I have some issues about CLUE-enabled call’s fallback.
>>>>
>>>>       The signaling draft says:
>>>>
>>>>              A call in which two CLUE-capable devices have
>>>> successfully negotiated support for a CLUE data channel in SDP.
>>>>
>>>> A CLUE-enabled call is not necessarily immediately able to send
>>>> CLUE-controlled media; negotiation of the data channel and of the
>>>> CLUE protocol must complete first
>>>>
>>>>           But the signaling does not say something as below:
>>>>
>>>> 1)When and how to stop the basic media streams?
>>>>
>>>> wait and until the two CLUE-capable device finish the negotiation and
>>>> use “a=inactive” or set the port number zero related to the basic
>>>> media streams
>>>>
>>>> 2)When and how to trigger a CLUE-enabled call fall back?
>>>>
>>>> the data channel is explicitly closed by SDP O/A ;
>>>>
>>>> the data channel is closed by SCTP SSN Reset (see the draft
>>>> draft-ietf-rtcweb-data-protocol-03) ;or
>>>>
>>>> the all CLUE-controlled media streams are removed by SDP O/A
>>>>
>>>>       That’s all and comments welcome.
>>>>
>>>> Best Regards,
>>>>
>>>> Scarlett
>>>>
>>>> ---------------------------------------------------------------------
>>>> ---
>>>>
>>>>
>>>> 华为技术有限 公司Huawei Technologies Co., Ltd.
>>>>
>>>>
>>>> Phone: 0086-755-28974289
>>>> Fax:
>>>> Mobile:
>>>> Email: scarlett.liuyan@huawei.com
>>>> 地址：深圳市 龙岗区坂田华为基地 邮编：518129
>>>> Huawei Technologies Co., Ltd.
>>>> Bantian, Longgang District,Shenzhen 518129, P.R.China
>>>> http://www.huawei.com
>>>>
>>>> ---------------------------------------------------------------------
>>>> ---
>>>>
>>>> 本邮件及其附件含 有华为公司的保密信息，仅限于发送给上面地址中
>> 列出的个
>>>> 人或群组。禁
>>>> 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复
>> 制、或散
>>>> 发）本邮件中
>>>> 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删
>> 除本邮件！
>>>> This e-mail and its attachments contain confidential information from
>>>> HUAWEI, which is intended only for the person or entity whose address
>>>> is listed above. Any use of the information contained herein in any
>>>> way (including, but not limited to, total or partial disclosure,
>>>> reproduction, or dissemination) by persons other than the intended
>>>> recipient(s) is prohibited. If you receive this e-mail in error,
>>>> please notify the sender by phone or email immediately and delete it!
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>>
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue


From nobody Fri Sep  5 10:23:00 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 884261A0ADB for <clue@ietfa.amsl.com>; Fri,  5 Sep 2014 10:22:58 -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_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NiqwgPWywwyf for <clue@ietfa.amsl.com>; Fri,  5 Sep 2014 10:22:56 -0700 (PDT)
Received: from mail1.bemta8.messagelabs.com (mail1.bemta8.messagelabs.com [216.82.243.204]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 721261A0AE2 for <clue@ietf.org>; Fri,  5 Sep 2014 10:22:56 -0700 (PDT)
Received: from [216.82.241.100:59705] by server-12.bemta-8.messagelabs.com id 44/15-26875-F61F9045; Fri, 05 Sep 2014 17:22:55 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-12.tower-220.messagelabs.com!1409937641!16476999!10
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26337 invoked from network); 5 Sep 2014 17:22:54 -0000
Received: from crpehubprd01.polycom.com (HELO Crpehubprd01.polycom.com) (140.242.64.158) by server-12.tower-220.messagelabs.com with AES128-SHA encrypted SMTP; 5 Sep 2014 17:22:54 -0000
Received: from PWEHUB01.polycom.com (10.236.2.221) by Crpehubprd01.polycom.com (10.236.0.158) with Microsoft SMTP Server (TLS) id 8.3.192.1; Fri, 5 Sep 2014 10:22:07 -0700
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by PWEHUB01.polycom.com ([fe80::99a8:f785:3f0c:2bb6%17]) with mapi; Fri, 5 Sep 2014 10:22:07 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "clue@ietf.org" <clue@ietf.org>
Date: Fri, 5 Sep 2014 10:22:05 -0700
Thread-Topic: Summary of Framework action items and issues
Thread-Index: Ac/JLKKXJy0rRwUbTVKvZiwsenlO2w==
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F078C059470@CRPMBOXPRD08.polycom.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_5C4AC54BFF7A0842A6A11F554D6FB52F078C059470CRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/O62Drzq678YQQDXYUmxWY5XvSPY
Subject: [clue] Summary of Framework action items and issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 17:22:58 -0000

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

Following up from IETF90, here is the current list of everything I know abo=
ut that I need to update in the framework.

*         These are straightforward, we agreed already on the list or at To=
ronto, so I will just update the framework and let people review it in the =
next version:
o    Change some terminology
*         Ticket #59 - CSE -> Capture Scene View
*         Ticket #60 - Global CSE List -> Global View List
*         An item in the Global View List is a Global View
*         A Global View is a set of CSVs
o    Update example 12.1.1 to clarify the spatial coordinates regarding aud=
io point of capture and axis of capture
o    Encoding Group can include multiple media types - make this explicit
o    Clarify that a media capture does not have to be included in a Capture=
 Scene View.
o    Area of capture is for video only, not for other media types
o    make other clarifications based on pre-WGLC email list discussion from=
 around July 16, 2014
*         For this one, I will put a proposal on the email list for discuss=
ion before changing the framework document:
o    Ticket #61 - Clarify coordinate system definition to remove potential =
problem with multiple cameras in different locations pointing in different =
directions

Regards,
Mark

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F078C059470CRPMBOXPRD08p_
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:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m=3D"http://sc=
hemas.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 14 (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;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1231959162;
	mso-list-template-ids:-574958142;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1983190514;
	mso-list-template-ids:333197184;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Following up fro=
m IETF90, here is the current list of everything I know about that I need t=
o update in the framework.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</=
o:p></p><p class=3DMsoNormal style=3D'margin-left:27.0pt;text-indent:-.25in=
;mso-list:l0 level1 lfo1;vertical-align:middle'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol'><span style=3D'mso-list:Ignor=
e'>&middot;<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>These are stra=
ightforward, we agreed already on the list or at Toronto, so I will just up=
date the framework and let people review it in the next version:<span style=
=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></sp=
an></p><p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;m=
so-list:l0 level2 lfo1;vertical-align:middle'><![if !supportLists]><span st=
yle=3D'font-size:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:=
Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </=
span></span></span><![endif]>Change some terminology<span style=3D'font-siz=
e:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p cl=
ass=3DMsoNormal style=3D'margin-left:81.0pt;text-indent:-.25in;mso-list:l0 =
level3 lfo1;vertical-align:middle'><![if !supportLists]><span style=3D'font=
-size:10.0pt;font-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<s=
pan style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </span></span></span><![endif]>Ticket #59 - CSE -&gt; Capt=
ure Scene View<span style=3D'font-size:12.0pt;font-family:"Times New Roman"=
,"serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:8=
1.0pt;text-indent:-.25in;mso-list:l0 level3 lfo1;vertical-align:middle'><![=
if !supportLists]><span style=3D'font-size:10.0pt;font-family:Symbol'><span=
 style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Rom=
an"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>=
<![endif]>Ticket #60 - Global CSE List -&gt; Global View List<span style=3D=
'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span>=
</p><p class=3DMsoNormal style=3D'margin-left:81.0pt;text-indent:-.25in;mso=
-list:l0 level3 lfo1;vertical-align:middle'><![if !supportLists]><span styl=
e=3D'font-size:10.0pt;font-family:Symbol'><span style=3D'mso-list:Ignore'>&=
middot;<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>An item in the Glo=
bal View List is a Global View<span style=3D'font-size:12.0pt;font-family:"=
Times New Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'margin-left:81.0pt;text-indent:-.25in;mso-list:l0 level3 lfo1;vertical-=
align:middle'><![if !supportLists]><span style=3D'font-size:10.0pt;font-fam=
ily:Symbol'><span style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0=
pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </sp=
an></span></span><![endif]>A Global View is a set of CSVs<span style=3D'fon=
t-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>=
<p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-list=
:l0 level2 lfo1;vertical-align:middle'><![if !supportLists]><span style=3D'=
font-size:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'=
>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></=
span></span><![endif]>Update example 12.1.1 to clarify the spatial coordina=
tes regarding audio point of capture and axis of capture<span style=3D'font=
-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><=
p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-list:=
l0 level2 lfo1;vertical-align:middle'><![if !supportLists]><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>=
o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></s=
pan></span><![endif]>Encoding Group can include multiple media types - make=
 this explicit<span style=3D'font-size:12.0pt;font-family:"Times New Roman"=
,"serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:.=
75in;text-indent:-.25in;mso-list:l0 level2 lfo1;vertical-align:middle'><![i=
f !supportLists]><span style=3D'font-size:10.0pt;font-family:"Courier New"'=
><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roma=
n"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Clarify that a media =
capture does not have to be included in a Capture Scene View.<span style=3D=
'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span>=
</p><p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-=
list:l0 level2 lfo1;vertical-align:middle'><![if !supportLists]><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ign=
ore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </spa=
n></span></span><![endif]>Area of capture is for video only, not for other =
media types<span style=3D'font-size:12.0pt;font-family:"Times New Roman","s=
erif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:.75i=
n;text-indent:-.25in;mso-list:l0 level2 lfo1;vertical-align:middle'><![if !=
supportLists]><span style=3D'font-size:10.0pt;font-family:"Courier New"'><s=
pan style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'=
>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>make other clarification=
s based on pre-WGLC email list discussion from around July 16, 2014<span st=
yle=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p><=
/span></p><p class=3DMsoNormal style=3D'margin-left:27.0pt;text-indent:-.25=
in;mso-list:l1 level1 lfo2;vertical-align:middle'><![if !supportLists]><spa=
n style=3D'font-size:10.0pt;font-family:Symbol'><span style=3D'mso-list:Ign=
ore'>&middot;<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>For this one=
, I will put a proposal on the email list for discussion before changing th=
e framework document:<span style=3D'font-size:12.0pt;font-family:"Times New=
 Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin=
-left:.75in;text-indent:-.25in;mso-list:l1 level2 lfo2;vertical-align:middl=
e'><![if !supportLists]><span style=3D'font-size:10.0pt;font-family:"Courie=
r New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times N=
ew Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Ticket #61 - C=
larify coordinate system definition to remove potential problem with multip=
le cameras in different locations pointing in different directions<o:p></o:=
p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Regard=
s,<o:p></o:p></p><p class=3DMsoNormal>Mark<o:p></o:p></p></div></body></htm=
l>=

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F078C059470CRPMBOXPRD08p_--


From nobody Tue Sep  9 06:14:10 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3D511A02E7 for <clue@ietfa.amsl.com>; Tue,  9 Sep 2014 06:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zeifsh9oikyQ for <clue@ietfa.amsl.com>; Tue,  9 Sep 2014 06:14:05 -0700 (PDT)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0F3E1A02DE for <clue@ietf.org>; Tue,  9 Sep 2014 06:14:04 -0700 (PDT)
Received: by mail-la0-f46.google.com with SMTP id pv20so19270232lab.5 for <clue@ietf.org>; Tue, 09 Sep 2014 06:14:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=xkiJG2HpN8qz/H8Vo7r15CGgpkR2c0oLfCEzfn3kHKU=; b=ZkpCdqbdUG9ax4BzxlqiEZ805FiPV0GTqOBqBGNRaANrqSKis1fvGlXZq2hu7OyitM ur0jOvNN3lZIZzzV2jfs/WEatIOVVm49YZmZAGw5v3t8g5bi+3yIZ1iVEpdOGZTL2nct uqjsjUR40hdicoTxTdAXo5U7BScwtc3WabOscfRlc9SGtwAbQlDkT5RXgwzMD0YFzhVV D9MCN2Uk2JeMLhqESGH3wiAnuNDDJDmnrPsv4nUNywogTU6frNiwkhh5pprPldWD+2bV N58nJLy/r4rm9638f6zh6toOxJ0DtPz+akEUmlBrzYR9cVtfJYgBL4YVFMPtKsy2k4FR jHoA==
MIME-Version: 1.0
X-Received: by 10.153.11.132 with SMTP id ei4mr28029530lad.24.1410268442687; Tue, 09 Sep 2014 06:14:02 -0700 (PDT)
Received: by 10.25.42.79 with HTTP; Tue, 9 Sep 2014 06:14:02 -0700 (PDT)
Date: Tue, 9 Sep 2014 08:14:02 -0500
Message-ID: <CAHBDyN7C8F8MY1utWVVpvE+8A0rhBDD_VUT_1MbdXEgoOCBZMA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: CLUE <clue@ietf.org>
Content-Type: multipart/alternative; boundary=001a1134787a907b110502a1b5f6
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/OryrTsZ5GxXoCxUYNAYYpP8w4kg
Subject: [clue] Design team calls
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 13:14:08 -0000

--001a1134787a907b110502a1b5f6
Content-Type: text/plain; charset=UTF-8

Hi all,

Obviously, there is no call today. The wiki has been updated with the
documents that we will focus on for each of the upcoming meetings:
http://trac.tools.ietf.org/wg/clue/trac/wiki/Design-Team

The focus of the meetings is on the open issues:
http://trac.tools.ietf.org/wg/clue/trac/report/1?asc=1&sort=component

If the document editors think an issue has already been resolved, then
please post a note with a short summary of the resolution on the mailing
list, so we can get the ticket closed before the DT call.

If individuals have solution proposals for the tickets, then please post
those prior to the meeting or let the chairs & document editors know if you
think presenting something for discussion on the call will be more
effective.

As I previously highlighted, a number of documents have no security
section. We cannot move forward without that section. So, ideally, having
some proposed text either in the document or posted to the mailing list
will help us to get back on track with moving these documents forward.

Thanks,
Mary & Paul

--001a1134787a907b110502a1b5f6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>Obviously, there is no call tod=
ay. The wiki has been updated with the documents that we will focus on for =
each of the upcoming meetings:</div><div><a href=3D"http://trac.tools.ietf.=
org/wg/clue/trac/wiki/Design-Team">http://trac.tools.ietf.org/wg/clue/trac/=
wiki/Design-Team</a></div><div><br></div><div>The focus of the meetings is =
on the open issues:</div><div><a href=3D"http://trac.tools.ietf.org/wg/clue=
/trac/report/1?asc=3D1&amp;sort=3Dcomponent">http://trac.tools.ietf.org/wg/=
clue/trac/report/1?asc=3D1&amp;sort=3Dcomponent</a></div><div><br></div><di=
v>If the document editors think an issue has already been resolved, then pl=
ease post a note with a short summary of the resolution on the mailing list=
, so we can get the ticket closed before the DT call.=C2=A0</div><div><br><=
/div><div>If individuals have solution proposals for the tickets, then plea=
se post those prior to the meeting or let the chairs &amp; document editors=
 know if you think presenting something for discussion on the call will be =
more effective. =C2=A0=C2=A0<br></div><div><br></div><div>As I previously h=
ighlighted, a number of documents have no security section. We cannot move =
forward without that section. So, ideally, having some proposed text either=
 in the document or posted to the mailing list will help us to get back on =
track with moving these documents forward.</div><div><br></div><div>Thanks,=
</div><div>Mary &amp; Paul</div></div>

--001a1134787a907b110502a1b5f6--


From nobody Thu Sep 11 14:48:46 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB6201A0264 for <clue@ietfa.amsl.com>; Thu, 11 Sep 2014 14:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level: 
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZEmEMACqGrS for <clue@ietfa.amsl.com>; Thu, 11 Sep 2014 14:48:42 -0700 (PDT)
Received: from mail1.bemta7.messagelabs.com (mail1.bemta7.messagelabs.com [216.82.254.110]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 425A51A0144 for <clue@ietf.org>; Thu, 11 Sep 2014 14:48:42 -0700 (PDT)
Received: from [216.82.254.19:10849] by server-14.bemta-7.messagelabs.com id 0F/BC-14464-9B812145; Thu, 11 Sep 2014 21:48:41 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-4.tower-96.messagelabs.com!1410472121!18466358!1
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16501 invoked from network); 11 Sep 2014 21:48:41 -0000
Received: from crpehubprd01.polycom.com (HELO Crpehubprd01.polycom.com) (140.242.64.158) by server-4.tower-96.messagelabs.com with AES128-SHA encrypted SMTP; 11 Sep 2014 21:48:41 -0000
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by Crpehubprd01.polycom.com ([::1]) with mapi; Thu, 11 Sep 2014 14:48:41 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "clue@ietf.org" <clue@ietf.org>
Date: Thu, 11 Sep 2014 14:48:38 -0700
Thread-Topic: Ticket #61 Proposal for describing the coordinate system
Thread-Index: Ac/OBABNLFTOcMTxSzGQWegMI2vl0g==
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.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_5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0CRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/m-T7uCE3IJTJnWqoYPgY7IJV1wg
Subject: [clue] Ticket #61 Proposal for describing the coordinate system
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 21:48:44 -0000

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

The ticket says describe it without using left/right/front/back terminology=
, but I don't think that was the point.  I think the point is to make it cl=
ear the provider can pick the one coordinate system origin and orientation =
for a scene even if there are multiple cameras pointing in different (even =
opposite) directions within that scene.

So here is a proposal, I would like your feedback.

Remove the definition of Front in section 3.  Remove the definitions of Cam=
era-Left and Right, and Stage-Left and Right.

In section 6. Spatial Relationships, starting with the last bullet item, re=
place the rest of that section with this:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D begin new text =3D=3D=3D=3D=3D=
=3D=3D=3D=3D
o The coordinate system is right-handed Cartesian X, Y, Z with the origin a=
t a spatial location of the Provider's choosing.  The Provider MUST use the=
 same coordinate system with the same scale and origin for all coordinates =
within the same Capture Scene.

The direction of increasing coordinate values is:
X increases from left to right, from the point of view of an observer at th=
e front of the room looking toward the back
Y increases from the front of the room to the back of the room
Z increases from low to high (i.e. floor to ceiling)

Cameras in a scene typically point in the direction of increasing Y, from f=
ront to back.  But there could be multiple cameras pointing in different di=
rections.  If the physical space does not have a well-defined front and bac=
k, the provider chooses any direction for X and Y consistent with right-han=
ded coordinates.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D end new text =3D=3D=3D=3D=3D=3D=
=3D=3D=3D

In section 12 examples, replace "camera-left" and "camera-right" with "left=
" and "right".

Regards,
Mark


--_000_5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0CRPMBOXPRD08p_
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"Micros=
oft Word 14 (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;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>The ticket says =
describe it without using left/right/front/back terminology, but I don&#821=
7;t think that was the point.&nbsp; I think the point is to make it clear t=
he provider can pick the one coordinate system origin and orientation for a=
 scene even if there are multiple cameras pointing in different (even oppos=
ite) directions within that scene.<o:p></o:p></p><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p><p class=3DMsoNormal>So here is a proposal, I would like yo=
ur feedback.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cla=
ss=3DMsoNormal>Remove the definition of Front in section 3.&nbsp; Remove th=
e definitions of Camera-Left and Right, and Stage-Left and Right.<o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>In sect=
ion 6. Spatial Relationships, starting with the last bullet item, replace t=
he rest of that section with this:<o:p></o:p></p><p class=3DMsoNormal>=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D begin new text =3D=3D=3D=3D=3D=3D=
=3D=3D=3D<o:p></o:p></p><p class=3DMsoNormal>o The coordinate system is rig=
ht-handed Cartesian X, Y, Z with the origin at a spatial location of the Pr=
ovider's choosing.&nbsp; The Provider MUST use the same coordinate system w=
ith the same scale and origin for all coordinates within the same Capture S=
cene.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal>The direction of increasing coordinate values is:<br>X increases fr=
om left to right, from the point of view of an observer at the front of the=
 room looking toward the back<o:p></o:p></p><p class=3DMsoNormal>Y increase=
s from the front of the room to the back of the room<o:p></o:p></p><p class=
=3DMsoNormal>Z increases from low to high (i.e. floor to ceiling)<o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Cameras=
 in a scene typically point in the direction of increasing Y, from front to=
 back.&nbsp; But there could be multiple cameras pointing in different dire=
ctions.&nbsp; If the physical space does not have a well-defined front and =
back, the provider chooses any direction for X and Y consistent with right-=
handed coordinates.<o:p></o:p></p><p class=3DMsoNormal>=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D end new text =3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>In sect=
ion 12 examples, replace &#8220;camera-left&#8221; and &#8220;camera-right&=
#8221; with &#8220;left&#8221; and &#8220;right&#8221;.<br><br><o:p></o:p><=
/p><p class=3DMsoNormal>Regards,<o:p></o:p></p><p class=3DMsoNormal>Mark<o:=
p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0CRPMBOXPRD08p_--


From nobody Thu Sep 11 19:00:36 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 162A51A0351 for <clue@ietfa.amsl.com>; Thu, 11 Sep 2014 19:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEReb8a3rADQ for <clue@ietfa.amsl.com>; Thu, 11 Sep 2014 19:00:33 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ED081A0114 for <clue@ietf.org>; Thu, 11 Sep 2014 19:00:32 -0700 (PDT)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by resqmta-ch2-11v.sys.comcast.net with comcast id q1tZ1o0060xGWP80120XDh; Fri, 12 Sep 2014 02:00:32 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta12.westchester.pa.mail.comcast.net with comcast id q20X1o00P3Ge9ey3Y20XM1; Fri, 12 Sep 2014 02:00:31 +0000
Message-ID: <541253BF.8070401@alum.mit.edu>
Date: Thu, 11 Sep 2014 22:00:31 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com>
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1410487232; bh=h4Qrc8hZWZoMODKGYpxgIU5BCy4K/SDHtQoo0Li8JOw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=FdobqUt1KxJHBxPFkZ/atrjIoVBfjl8mbWef/j8kXgBVZvt1jaPDMTrij2lusRpqW 2tZH/0cJK5CHYBPGrQECYMq3SVZ0hLwK1Tf48zyCk+2YLmbl33vYEDmn+D5AZTdSlv I1KNhhnERLw6H2ZQzPCGpnHoBhrZlGwC1/Cw39/wfI0Asd6CfTnKRY/LrGS81d6rT+ t5YsGS/5BKxvWlNVIwjo9GnRwBrasWj9SnKbG1uQRF2FqodzQFtHW3Jeel5MZ2m7n/ mMidsk28VgKnJkmnRD9/ceGzW53TNeXgBWSh59CSyjKW78yLAuu+dPaxLDk9icJCXW DRH+A0bI5QRVw==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/u41D5bTPunA1jp7l3xoNW1spGhA
Subject: Re: [clue] Ticket #61 Proposal for describing the coordinate system
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 02:00:35 -0000

Mark,

WFM.

I will note that there *could* be scenes where low/high, floor/ceiling 
aren't well defined. (E.g. in a space station.) But these are rare 
enough that I don't think we need to worry about them.

	Thanks,
	Paul

On 9/11/14 5:48 PM, Duckworth, Mark wrote:
> The ticket says describe it without using left/right/front/back
> terminology, but I don’t think that was the point.  I think the point is
> to make it clear the provider can pick the one coordinate system origin
> and orientation for a scene even if there are multiple cameras pointing
> in different (even opposite) directions within that scene.
>
> So here is a proposal, I would like your feedback.
>
> Remove the definition of Front in section 3.  Remove the definitions of
> Camera-Left and Right, and Stage-Left and Right.
>
> In section 6. Spatial Relationships, starting with the last bullet item,
> replace the rest of that section with this:
>
> ============== begin new text =========
>
> o The coordinate system is right-handed Cartesian X, Y, Z with the
> origin at a spatial location of the Provider's choosing.  The Provider
> MUST use the same coordinate system with the same scale and origin for
> all coordinates within the same Capture Scene.
>
> The direction of increasing coordinate values is:
> X increases from left to right, from the point of view of an observer at
> the front of the room looking toward the back
>
> Y increases from the front of the room to the back of the room
>
> Z increases from low to high (i.e. floor to ceiling)
>
> Cameras in a scene typically point in the direction of increasing Y,
> from front to back.  But there could be multiple cameras pointing in
> different directions.  If the physical space does not have a
> well-defined front and back, the provider chooses any direction for X
> and Y consistent with right-handed coordinates.
>
> ============== end new text =========
>
> In section 12 examples, replace “camera-left” and “camera-right” with
> “left” and “right”.
>
> Regards,
>
> Mark
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Fri Sep 12 09:54:10 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 060CE1A6FE5 for <clue@ietfa.amsl.com>; Fri, 12 Sep 2014 09:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8uDQ0ExgZFoD for <clue@ietfa.amsl.com>; Fri, 12 Sep 2014 09:53:58 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DB161A6FCB for <clue@ietf.org>; Fri, 12 Sep 2014 09:53:57 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id b17so1353284lan.18 for <clue@ietf.org>; Fri, 12 Sep 2014 09:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8Rf4PwWxaI2d0pyPZrert78NB5SXQZJei0nWM0yiIYo=; b=vgowqKWX3Pw0ubVetemvn/MG2wo5W7isa393gV9ge3bggS8RJSz2wrJaTZXCY/2+oW isfMnxkLGErJHsk4ONlNe8u21l9xi0D1VA6zeEsJJTzQxtnoi/OW63Nzy9Qxu7qnYx4o nVjeDdrMI61hXw1G/5L2DtxcqZ/VW9+BV2Yd3oSq1LAq2YSIWvKB4Oh7F1I0dTgOK011 UASS+NiFewfRdu9JRiOI41jYQ2V1Rzk6/5LbIcn0hKFT2uBJwvIy+QJ+t3b2hkFyJ8sg R0iFr6NCfvuh3iV0bRMrvugJTG4CqBOcquonECJtR54frZSUMFl0u6BbDcEHQptbmEQf XySA==
MIME-Version: 1.0
X-Received: by 10.152.36.73 with SMTP id o9mr10263377laj.88.1410540835782; Fri, 12 Sep 2014 09:53:55 -0700 (PDT)
Received: by 10.25.42.79 with HTTP; Fri, 12 Sep 2014 09:53:55 -0700 (PDT)
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com>
References: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com>
Date: Fri, 12 Sep 2014 11:53:55 -0500
Message-ID: <CAHBDyN7U9ekzJoaLq9GxNotF3ZfDPWJZ=bye4Sh7HeLAJ5ddDw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
Content-Type: multipart/alternative; boundary=089e0160adf87544760502e121d6
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/5M6AvVBCfqp3gGNs0J1c1sJSRYA
Cc: "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] Ticket #61 Proposal for describing the coordinate system
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 16:54:04 -0000

--089e0160adf87544760502e121d6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Mark,

Thanks for the posting the proposed solution.  I think the proposal ought
to work - we do need additional WG to review and comment.

One comment below [MB].

Mary.

On Thu, Sep 11, 2014 at 4:48 PM, Duckworth, Mark <Mark.Duckworth@polycom.co=
m
> wrote:

> The ticket says describe it without using left/right/front/back
> terminology, but I don=E2=80=99t think that was the point.
>
[MB] Please feel free to update the text in the ticket. The ticket text is
based upon what is captured in notes and meeting minutes:
http://www.ietf.org/proceedings/90/minutes/minutes-90-clue
 It's too late to change those (deadline was Monday), but it would be good
to have the ticket accurate so that it's much more clear that the solution
proposed resolves the ticket. [/MB]


> I think the point is to make it clear the provider can pick the one
> coordinate system origin and orientation for a scene even if there are
> multiple cameras pointing in different (even opposite) directions within
> that scene.
>
>
>
> So here is a proposal, I would like your feedback.
>
>
>
> Remove the definition of Front in section 3.  Remove the definitions of
> Camera-Left and Right, and Stage-Left and Right.
>
>
>
> In section 6. Spatial Relationships, starting with the last bullet item,
> replace the rest of that section with this:
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D begin new text =3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>
> o The coordinate system is right-handed Cartesian X, Y, Z with the origin
> at a spatial location of the Provider's choosing.  The Provider MUST use
> the same coordinate system with the same scale and origin for all
> coordinates within the same Capture Scene.
>
>
>
> The direction of increasing coordinate values is:
> X increases from left to right, from the point of view of an observer at
> the front of the room looking toward the back
>
> Y increases from the front of the room to the back of the room
>
> Z increases from low to high (i.e. floor to ceiling)
>
>
>
> Cameras in a scene typically point in the direction of increasing Y, from
> front to back.  But there could be multiple cameras pointing in different
> directions.  If the physical space does not have a well-defined front and
> back, the provider chooses any direction for X and Y consistent with
> right-handed coordinates.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D end new text =3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>
>
>
> In section 12 examples, replace =E2=80=9Ccamera-left=E2=80=9D and =E2=80=
=9Ccamera-right=E2=80=9D with
> =E2=80=9Cleft=E2=80=9D and =E2=80=9Cright=E2=80=9D.
>
> Regards,
>
> Mark
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>
>

--089e0160adf87544760502e121d6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Mark,<div><br></div><div>Thanks for the posting the propos=
ed solution. =C2=A0I think the proposal ought to work - we do need addition=
al WG to review and comment.</div><div><br></div><div>One comment below [MB=
].</div><div><br></div><div>Mary.=C2=A0</div><div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Thu, Sep 11, 2014 at 4:48 PM, Duckworth=
, Mark <span dir=3D"ltr">&lt;<a href=3D"mailto:Mark.Duckworth@polycom.com" =
target=3D"_blank">Mark.Duckworth@polycom.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-=
width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddin=
g-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p clas=
s=3D"MsoNormal">The ticket says describe it without using left/right/front/=
back terminology, but I don=E2=80=99t think that was the point.=C2=A0 </p><=
/div></div></blockquote><div>[MB] Please feel free to update the text in th=
e ticket. The ticket text is based upon what is captured in notes and meeti=
ng minutes:</div><div><a href=3D"http://www.ietf.org/proceedings/90/minutes=
/minutes-90-clue">http://www.ietf.org/proceedings/90/minutes/minutes-90-clu=
e</a></div><div>=C2=A0It&#39;s too late to change those (deadline was Monda=
y), but it would be good to have the ticket accurate so that it&#39;s much =
more clear that the solution proposed resolves the ticket. [/MB]<br></div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-le=
ft-style:solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D=
"purple"><div><p class=3D"MsoNormal">I think the point is to make it clear =
the provider can pick the one coordinate system origin and orientation for =
a scene even if there are multiple cameras pointing in different (even oppo=
site) directions within that scene.<u></u><u></u></p><p class=3D"MsoNormal"=
><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal">So here is a proposal, I wo=
uld like your feedback.<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=
=A0<u></u></p><p class=3D"MsoNormal">Remove the definition of Front in sect=
ion 3.=C2=A0 Remove the definitions of Camera-Left and Right, and Stage-Lef=
t and Right.<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></=
p><p class=3D"MsoNormal">In section 6. Spatial Relationships, starting with=
 the last bullet item, replace the rest of that section with this:<u></u><u=
></u></p><p class=3D"MsoNormal">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =
begin new text =3D=3D=3D=3D=3D=3D=3D=3D=3D<u></u><u></u></p><p class=3D"Mso=
Normal">o The coordinate system is right-handed Cartesian X, Y, Z with the =
origin at a spatial location of the Provider&#39;s choosing.=C2=A0 The Prov=
ider MUST use the same coordinate system with the same scale and origin for=
 all coordinates within the same Capture Scene.<u></u><u></u></p><p class=
=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal">The direction=
 of increasing coordinate values is:<br>X increases from left to right, fro=
m the point of view of an observer at the front of the room looking toward =
the back<u></u><u></u></p><p class=3D"MsoNormal">Y increases from the front=
 of the room to the back of the room<u></u><u></u></p><p class=3D"MsoNormal=
">Z increases from low to high (i.e. floor to ceiling)<u></u><u></u></p><p =
class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal">Cameras =
in a scene typically point in the direction of increasing Y, from front to =
back.=C2=A0 But there could be multiple cameras pointing in different direc=
tions.=C2=A0 If the physical space does not have a well-defined front and b=
ack, the provider chooses any direction for X and Y consistent with right-h=
anded coordinates.<u></u><u></u></p><p class=3D"MsoNormal">=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D end new text =3D=3D=3D=3D=3D=3D=3D=3D=3D<u></u>=
<u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNo=
rmal">In section 12 examples, replace =E2=80=9Ccamera-left=E2=80=9D and =E2=
=80=9Ccamera-right=E2=80=9D with =E2=80=9Cleft=E2=80=9D and =E2=80=9Cright=
=E2=80=9D.<br><br><u></u><u></u></p><p class=3D"MsoNormal">Regards,<u></u><=
u></u></p><p class=3D"MsoNormal">Mark<u></u><u></u></p><p class=3D"MsoNorma=
l"><u></u>=C2=A0<u></u></p></div></div><br>________________________________=
_______________<br>
clue mailing list<br>
<a href=3D"mailto:clue@ietf.org">clue@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/clue" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/clue</a><br>
<br></blockquote></div><br></div></div></div>

--089e0160adf87544760502e121d6--


From nobody Sun Sep 14 17:50:27 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 426BF1A045E for <clue@ietfa.amsl.com>; Sun, 14 Sep 2014 17:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xbezy7oFqb1 for <clue@ietfa.amsl.com>; Sun, 14 Sep 2014 17:50:24 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D0B91A045B for <clue@ietf.org>; Sun, 14 Sep 2014 17:50:24 -0700 (PDT)
Received: from ppp118-209-95-210.lns20.mel4.internode.on.net ([118.209.95.210]:51689 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XTKTS-0003N4-UO for clue@ietf.org; Mon, 15 Sep 2014 10:48:59 +1000
Message-ID: <541637CD.8060103@nteczone.com>
Date: Mon, 15 Sep 2014 10:50:21 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com>
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/WY__PQ47vXvSiOKKFvzE-Lfb7xQ
Subject: Re: [clue] Ticket #61 Proposal for describing the coordinate system
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 00:50:26 -0000

Hello Mark,

I'm OK with the proposal. Do you have an example that you were thinking 
about for the "not well-defined" case?

Regards, Christian

On 12/09/2014 7:48 AM, Duckworth, Mark wrote:
>
> The ticket says describe it without using left/right/front/back 
> terminology, but I don’t think that was the point. I think the point 
> is to make it clear the provider can pick the one coordinate system 
> origin and orientation for a scene even if there are multiple cameras 
> pointing in different (even opposite) directions within that scene.
>
> So here is a proposal, I would like your feedback.
>
> Remove the definition of Front in section 3. Remove the definitions of 
> Camera-Left and Right, and Stage-Left and Right.
>
> In section 6. Spatial Relationships, starting with the last bullet 
> item, replace the rest of that section with this:
>
> ============== begin new text =========
>
> o The coordinate system is right-handed Cartesian X, Y, Z with the 
> origin at a spatial location of the Provider's choosing. The Provider 
> MUST use the same coordinate system with the same scale and origin for 
> all coordinates within the same Capture Scene.
>
> The direction of increasing coordinate values is:
> X increases from left to right, from the point of view of an observer 
> at the front of the room looking toward the back
>
> Y increases from the front of the room to the back of the room
>
> Z increases from low to high (i.e. floor to ceiling)
>
> Cameras in a scene typically point in the direction of increasing Y, 
> from front to back. But there could be multiple cameras pointing in 
> different directions. If the physical space does not have a 
> well-defined front and back, the provider chooses any direction for X 
> and Y consistent with right-handed coordinates.
>
> ============== end new text =========
>
> In section 12 examples, replace “camera-left” and “camera-right” with 
> “left” and “right”.
>
> Regards,
>
> Mark
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Mon Sep 15 06:00:15 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 278F91A0334 for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 06:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJNWxIb0zI-r for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 06:00:11 -0700 (PDT)
Received: from mail1.bemta12.messagelabs.com (mail1.bemta12.messagelabs.com [216.82.251.7]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B4A81A032C for <clue@ietf.org>; Mon, 15 Sep 2014 06:00:11 -0700 (PDT)
Received: from [216.82.249.212:33379] by server-7.bemta-12.messagelabs.com id F3/65-10811-AD2E6145; Mon, 15 Sep 2014 13:00:10 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-8.tower-219.messagelabs.com!1410786008!3699383!2
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7405 invoked from network); 15 Sep 2014 13:00:10 -0000
Received: from crpehubprd01.polycom.com (HELO Crpehubprd01.polycom.com) (140.242.64.158) by server-8.tower-219.messagelabs.com with AES128-SHA encrypted SMTP; 15 Sep 2014 13:00:10 -0000
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by Crpehubprd01.polycom.com ([::1]) with mapi; Mon, 15 Sep 2014 06:00:09 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Mon, 15 Sep 2014 06:00:06 -0700
Thread-Topic: [clue] Ticket #61 Proposal for describing the coordinate system
Thread-Index: Ac/OqiadgU06seCjS4G5hm/NZwG/mACOq7fQ
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9221D0@CRPMBOXPRD08.polycom.com>
References: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com> <CAHBDyN7U9ekzJoaLq9GxNotF3ZfDPWJZ=bye4Sh7HeLAJ5ddDw@mail.gmail.com>
In-Reply-To: <CAHBDyN7U9ekzJoaLq9GxNotF3ZfDPWJZ=bye4Sh7HeLAJ5ddDw@mail.gmail.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_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9221D0CRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/07nxgSL1LQwDXyfDmwBfB4Q0SYc
Cc: "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] Ticket #61 Proposal for describing the coordinate system
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 13:00:13 -0000

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9221D0CRPMBOXPRD08p_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhhbmtzIE1hcnkuDQpJIGNvdWxkbuKAmXQgZmlndXJlIG91dCBob3cgdG8gZWRpdCB0aGUgZGVz
Y3JpcHRpb24gaW4gdGhlIHRpY2tldC4gIEFtIEkgc3VwcG9zZWQgdG8gYmUgYWJsZSB0byBkbyB0
aGF0PyAgU28gSSBhZGRlZCBhIGNvbW1lbnQgdG8gdGhlIHRpY2tldC4NCk1hcmsNCg0KRnJvbTog
TWFyeSBCYXJuZXMgW21haWx0bzptYXJ5LmlldGYuYmFybmVzQGdtYWlsLmNvbV0NClNlbnQ6IEZy
aWRheSwgU2VwdGVtYmVyIDEyLCAyMDE0IDEyOjU0IFBNDQpUbzogRHVja3dvcnRoLCBNYXJrDQpD
YzogY2x1ZUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtjbHVlXSBUaWNrZXQgIzYxIFByb3Bvc2Fs
IGZvciBkZXNjcmliaW5nIHRoZSBjb29yZGluYXRlIHN5c3RlbQ0KDQpNYXJrLA0KDQpUaGFua3Mg
Zm9yIHRoZSBwb3N0aW5nIHRoZSBwcm9wb3NlZCBzb2x1dGlvbi4gIEkgdGhpbmsgdGhlIHByb3Bv
c2FsIG91Z2h0IHRvIHdvcmsgLSB3ZSBkbyBuZWVkIGFkZGl0aW9uYWwgV0cgdG8gcmV2aWV3IGFu
ZCBjb21tZW50Lg0KDQpPbmUgY29tbWVudCBiZWxvdyBbTUJdLg0KDQpNYXJ5Lg0KDQpPbiBUaHUs
IFNlcCAxMSwgMjAxNCBhdCA0OjQ4IFBNLCBEdWNrd29ydGgsIE1hcmsgPE1hcmsuRHVja3dvcnRo
QHBvbHljb20uY29tPG1haWx0bzpNYXJrLkR1Y2t3b3J0aEBwb2x5Y29tLmNvbT4+IHdyb3RlOg0K
VGhlIHRpY2tldCBzYXlzIGRlc2NyaWJlIGl0IHdpdGhvdXQgdXNpbmcgbGVmdC9yaWdodC9mcm9u
dC9iYWNrIHRlcm1pbm9sb2d5LCBidXQgSSBkb27igJl0IHRoaW5rIHRoYXQgd2FzIHRoZSBwb2lu
dC4NCltNQl0gUGxlYXNlIGZlZWwgZnJlZSB0byB1cGRhdGUgdGhlIHRleHQgaW4gdGhlIHRpY2tl
dC4gVGhlIHRpY2tldCB0ZXh0IGlzIGJhc2VkIHVwb24gd2hhdCBpcyBjYXB0dXJlZCBpbiBub3Rl
cyBhbmQgbWVldGluZyBtaW51dGVzOg0KaHR0cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy85
MC9taW51dGVzL21pbnV0ZXMtOTAtY2x1ZQ0KIEl0J3MgdG9vIGxhdGUgdG8gY2hhbmdlIHRob3Nl
IChkZWFkbGluZSB3YXMgTW9uZGF5KSwgYnV0IGl0IHdvdWxkIGJlIGdvb2QgdG8gaGF2ZSB0aGUg
dGlja2V0IGFjY3VyYXRlIHNvIHRoYXQgaXQncyBtdWNoIG1vcmUgY2xlYXIgdGhhdCB0aGUgc29s
dXRpb24gcHJvcG9zZWQgcmVzb2x2ZXMgdGhlIHRpY2tldC4gWy9NQl0NCg0KSSB0aGluayB0aGUg
cG9pbnQgaXMgdG8gbWFrZSBpdCBjbGVhciB0aGUgcHJvdmlkZXIgY2FuIHBpY2sgdGhlIG9uZSBj
b29yZGluYXRlIHN5c3RlbSBvcmlnaW4gYW5kIG9yaWVudGF0aW9uIGZvciBhIHNjZW5lIGV2ZW4g
aWYgdGhlcmUgYXJlIG11bHRpcGxlIGNhbWVyYXMgcG9pbnRpbmcgaW4gZGlmZmVyZW50IChldmVu
IG9wcG9zaXRlKSBkaXJlY3Rpb25zIHdpdGhpbiB0aGF0IHNjZW5lLg0KDQpTbyBoZXJlIGlzIGEg
cHJvcG9zYWwsIEkgd291bGQgbGlrZSB5b3VyIGZlZWRiYWNrLg0KDQpSZW1vdmUgdGhlIGRlZmlu
aXRpb24gb2YgRnJvbnQgaW4gc2VjdGlvbiAzLiAgUmVtb3ZlIHRoZSBkZWZpbml0aW9ucyBvZiBD
YW1lcmEtTGVmdCBhbmQgUmlnaHQsIGFuZCBTdGFnZS1MZWZ0IGFuZCBSaWdodC4NCg0KSW4gc2Vj
dGlvbiA2LiBTcGF0aWFsIFJlbGF0aW9uc2hpcHMsIHN0YXJ0aW5nIHdpdGggdGhlIGxhc3QgYnVs
bGV0IGl0ZW0sIHJlcGxhY2UgdGhlIHJlc3Qgb2YgdGhhdCBzZWN0aW9uIHdpdGggdGhpczoNCj09
PT09PT09PT09PT09IGJlZ2luIG5ldyB0ZXh0ID09PT09PT09PQ0KbyBUaGUgY29vcmRpbmF0ZSBz
eXN0ZW0gaXMgcmlnaHQtaGFuZGVkIENhcnRlc2lhbiBYLCBZLCBaIHdpdGggdGhlIG9yaWdpbiBh
dCBhIHNwYXRpYWwgbG9jYXRpb24gb2YgdGhlIFByb3ZpZGVyJ3MgY2hvb3NpbmcuICBUaGUgUHJv
dmlkZXIgTVVTVCB1c2UgdGhlIHNhbWUgY29vcmRpbmF0ZSBzeXN0ZW0gd2l0aCB0aGUgc2FtZSBz
Y2FsZSBhbmQgb3JpZ2luIGZvciBhbGwgY29vcmRpbmF0ZXMgd2l0aGluIHRoZSBzYW1lIENhcHR1
cmUgU2NlbmUuDQoNClRoZSBkaXJlY3Rpb24gb2YgaW5jcmVhc2luZyBjb29yZGluYXRlIHZhbHVl
cyBpczoNClggaW5jcmVhc2VzIGZyb20gbGVmdCB0byByaWdodCwgZnJvbSB0aGUgcG9pbnQgb2Yg
dmlldyBvZiBhbiBvYnNlcnZlciBhdCB0aGUgZnJvbnQgb2YgdGhlIHJvb20gbG9va2luZyB0b3dh
cmQgdGhlIGJhY2sNClkgaW5jcmVhc2VzIGZyb20gdGhlIGZyb250IG9mIHRoZSByb29tIHRvIHRo
ZSBiYWNrIG9mIHRoZSByb29tDQpaIGluY3JlYXNlcyBmcm9tIGxvdyB0byBoaWdoIChpLmUuIGZs
b29yIHRvIGNlaWxpbmcpDQoNCkNhbWVyYXMgaW4gYSBzY2VuZSB0eXBpY2FsbHkgcG9pbnQgaW4g
dGhlIGRpcmVjdGlvbiBvZiBpbmNyZWFzaW5nIFksIGZyb20gZnJvbnQgdG8gYmFjay4gIEJ1dCB0
aGVyZSBjb3VsZCBiZSBtdWx0aXBsZSBjYW1lcmFzIHBvaW50aW5nIGluIGRpZmZlcmVudCBkaXJl
Y3Rpb25zLiAgSWYgdGhlIHBoeXNpY2FsIHNwYWNlIGRvZXMgbm90IGhhdmUgYSB3ZWxsLWRlZmlu
ZWQgZnJvbnQgYW5kIGJhY2ssIHRoZSBwcm92aWRlciBjaG9vc2VzIGFueSBkaXJlY3Rpb24gZm9y
IFggYW5kIFkgY29uc2lzdGVudCB3aXRoIHJpZ2h0LWhhbmRlZCBjb29yZGluYXRlcy4NCj09PT09
PT09PT09PT09IGVuZCBuZXcgdGV4dCA9PT09PT09PT0NCg0KSW4gc2VjdGlvbiAxMiBleGFtcGxl
cywgcmVwbGFjZSDigJxjYW1lcmEtbGVmdOKAnSBhbmQg4oCcY2FtZXJhLXJpZ2h04oCdIHdpdGgg
4oCcbGVmdOKAnSBhbmQg4oCccmlnaHTigJ0uDQpSZWdhcmRzLA0KTWFyaw0KDQoNCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpjbHVlIG1haWxpbmcgbGlz
dA0KY2x1ZUBpZXRmLm9yZzxtYWlsdG86Y2x1ZUBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vY2x1ZQ0KDQo=

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9221D0CRPMBOXPRD08p_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw
YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCglj
b2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KQHBhZ2UgV29yZFNl
Y3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAx
LjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT48L2hlYWQ+
PGJvZHkgbGFuZz1FTi1VUyBsaW5rPWJsdWUgdmxpbms9cHVycGxlPjxkaXYgY2xhc3M9V29yZFNl
Y3Rpb24xPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPlRoYW5rcyBN
YXJ5LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xv
cjojMUY0OTdEJz5JIGNvdWxkbuKAmXQgZmlndXJlIG91dCBob3cgdG8gZWRpdCB0aGUgZGVzY3Jp
cHRpb24gaW4gdGhlIHRpY2tldC7CoCBBbSBJIHN1cHBvc2VkIHRvIGJlIGFibGUgdG8gZG8gdGhh
dD/CoCBTbyBJIGFkZGVkIGEgY29tbWVudCB0byB0aGUgdGlja2V0LjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5NYXJrPG86cD48
L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0Qn
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQnPjxkaXY+
PGRpdiBzdHlsZT0nYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3Bh
ZGRpbmc6My4wcHQgMGluIDBpbiAwaW4nPjxwIGNsYXNzPU1zb05vcm1hbD48Yj48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPkZy
b206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToi
VGFob21hIiwic2Fucy1zZXJpZiInPiBNYXJ5IEJhcm5lcyBbbWFpbHRvOm1hcnkuaWV0Zi5iYXJu
ZXNAZ21haWwuY29tXSA8YnI+PGI+U2VudDo8L2I+IEZyaWRheSwgU2VwdGVtYmVyIDEyLCAyMDE0
IDEyOjU0IFBNPGJyPjxiPlRvOjwvYj4gRHVja3dvcnRoLCBNYXJrPGJyPjxiPkNjOjwvYj4gY2x1
ZUBpZXRmLm9yZzxicj48Yj5TdWJqZWN0OjwvYj4gUmU6IFtjbHVlXSBUaWNrZXQgIzYxIFByb3Bv
c2FsIGZvciBkZXNjcmliaW5nIHRoZSBjb29yZGluYXRlIHN5c3RlbTxvOnA+PC9vOnA+PC9zcGFu
PjwvcD48L2Rpdj48L2Rpdj48cCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L3A+
PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWw+TWFyayw8bzpwPjwvbzpwPjwvcD48ZGl2PjxwIGNsYXNz
PU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05v
cm1hbD5UaGFua3MgZm9yIHRoZSBwb3N0aW5nIHRoZSBwcm9wb3NlZCBzb2x1dGlvbi4gJm5ic3A7
SSB0aGluayB0aGUgcHJvcG9zYWwgb3VnaHQgdG8gd29yayAtIHdlIGRvIG5lZWQgYWRkaXRpb25h
bCBXRyB0byByZXZpZXcgYW5kIGNvbW1lbnQuPG86cD48L286cD48L3A+PC9kaXY+PGRpdj48cCBj
bGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz1N
c29Ob3JtYWw+T25lIGNvbW1lbnQgYmVsb3cgW01CXS48bzpwPjwvbzpwPjwvcD48L2Rpdj48ZGl2
PjxwIGNsYXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48L2Rpdj48ZGl2PjxwIGNs
YXNzPU1zb05vcm1hbD5NYXJ5LiZuYnNwOzxvOnA+PC9vOnA+PC9wPjwvZGl2PjxkaXY+PGRpdj48
cCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L3A+PGRpdj48cCBjbGFzcz1Nc29O
b3JtYWw+T24gVGh1LCBTZXAgMTEsIDIwMTQgYXQgNDo0OCBQTSwgRHVja3dvcnRoLCBNYXJrICZs
dDs8YSBocmVmPSJtYWlsdG86TWFyay5EdWNrd29ydGhAcG9seWNvbS5jb20iIHRhcmdldD0iX2Js
YW5rIj5NYXJrLkR1Y2t3b3J0aEBwb2x5Y29tLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+
PC9wPjxkaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz5UaGUgdGlja2V0IHNheXMgZGVzY3Jp
YmUgaXQgd2l0aG91dCB1c2luZyBsZWZ0L3JpZ2h0L2Zyb250L2JhY2sgdGVybWlub2xvZ3ksIGJ1
dCBJIGRvbuKAmXQgdGhpbmsgdGhhdCB3YXMgdGhlIHBvaW50LiZuYnNwOyA8bzpwPjwvbzpwPjwv
cD48L2Rpdj48L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD5bTUJdIFBsZWFzZSBmZWVsIGZy
ZWUgdG8gdXBkYXRlIHRoZSB0ZXh0IGluIHRoZSB0aWNrZXQuIFRoZSB0aWNrZXQgdGV4dCBpcyBi
YXNlZCB1cG9uIHdoYXQgaXMgY2FwdHVyZWQgaW4gbm90ZXMgYW5kIG1lZXRpbmcgbWludXRlczo8
bzpwPjwvbzpwPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48YSBocmVmPSJodHRw
Oi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzkwL21pbnV0ZXMvbWludXRlcy05MC1jbHVlIj5o
dHRwOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzkwL21pbnV0ZXMvbWludXRlcy05MC1jbHVl
PC9hPjxvOnA+PC9vOnA+PC9wPjwvZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwO0l0
J3MgdG9vIGxhdGUgdG8gY2hhbmdlIHRob3NlIChkZWFkbGluZSB3YXMgTW9uZGF5KSwgYnV0IGl0
IHdvdWxkIGJlIGdvb2QgdG8gaGF2ZSB0aGUgdGlja2V0IGFjY3VyYXRlIHNvIHRoYXQgaXQncyBt
dWNoIG1vcmUgY2xlYXIgdGhhdCB0aGUgc29sdXRpb24gcHJvcG9zZWQgcmVzb2x2ZXMgdGhlIHRp
Y2tldC4gWy9NQl08bzpwPjwvbzpwPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD4m
bmJzcDs8bzpwPjwvbzpwPjwvcD48L2Rpdj48YmxvY2txdW90ZSBzdHlsZT0nYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4nPjxkaXY+PGRpdj48cCBjbGFzcz1N
c29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvJz5JIHRoaW5rIHRoZSBwb2ludCBpcyB0byBtYWtlIGl0IGNsZWFyIHRoZSBwcm92
aWRlciBjYW4gcGljayB0aGUgb25lIGNvb3JkaW5hdGUgc3lzdGVtIG9yaWdpbiBhbmQgb3JpZW50
YXRpb24gZm9yIGEgc2NlbmUgZXZlbiBpZiB0aGVyZSBhcmUgbXVsdGlwbGUgY2FtZXJhcyBwb2lu
dGluZyBpbiBkaWZmZXJlbnQgKGV2ZW4gb3Bwb3NpdGUpIGRpcmVjdGlvbnMgd2l0aGluIHRoYXQg
c2NlbmUuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+Jm5ic3A7PG86cD48L286
cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+U28gaGVyZSBpcyBhIHByb3Bvc2FsLCBJIHdvdWxk
IGxpa2UgeW91ciBmZWVkYmFjay48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5
bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4m
bmJzcDs8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz5SZW1vdmUgdGhlIGRlZmlu
aXRpb24gb2YgRnJvbnQgaW4gc2VjdGlvbiAzLiZuYnNwOyBSZW1vdmUgdGhlIGRlZmluaXRpb25z
IG9mIENhbWVyYS1MZWZ0IGFuZCBSaWdodCwgYW5kIFN0YWdlLUxlZnQgYW5kIFJpZ2h0LjxvOnA+
PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPiZuYnNwOzxvOnA+PC9vOnA+PC9wPjxwIGNs
YXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8nPkluIHNlY3Rpb24gNi4gU3BhdGlhbCBSZWxhdGlvbnNoaXBzLCBzdGFy
dGluZyB3aXRoIHRoZSBsYXN0IGJ1bGxldCBpdGVtLCByZXBsYWNlIHRoZSByZXN0IG9mIHRoYXQg
c2VjdGlvbiB3aXRoIHRoaXM6PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxl
PSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PT09
PT09PT09PT09PT0gYmVnaW4gbmV3IHRleHQgPT09PT09PT09PG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byc+byBUaGUgY29vcmRpbmF0ZSBzeXN0ZW0gaXMgcmlnaHQtaGFuZGVkIENh
cnRlc2lhbiBYLCBZLCBaIHdpdGggdGhlIG9yaWdpbiBhdCBhIHNwYXRpYWwgbG9jYXRpb24gb2Yg
dGhlIFByb3ZpZGVyJ3MgY2hvb3NpbmcuJm5ic3A7IFRoZSBQcm92aWRlciBNVVNUIHVzZSB0aGUg
c2FtZSBjb29yZGluYXRlIHN5c3RlbSB3aXRoIHRoZSBzYW1lIHNjYWxlIGFuZCBvcmlnaW4gZm9y
IGFsbCBjb29yZGluYXRlcyB3aXRoaW4gdGhlIHNhbWUgQ2FwdHVyZSBTY2VuZS48bzpwPjwvbzpw
PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4mbmJzcDs8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1N
c29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvJz5UaGUgZGlyZWN0aW9uIG9mIGluY3JlYXNpbmcgY29vcmRpbmF0ZSB2YWx1ZXMg
aXM6PGJyPlggaW5jcmVhc2VzIGZyb20gbGVmdCB0byByaWdodCwgZnJvbSB0aGUgcG9pbnQgb2Yg
dmlldyBvZiBhbiBvYnNlcnZlciBhdCB0aGUgZnJvbnQgb2YgdGhlIHJvb20gbG9va2luZyB0b3dh
cmQgdGhlIGJhY2s8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz5ZIGluY3JlYXNl
cyBmcm9tIHRoZSBmcm9udCBvZiB0aGUgcm9vbSB0byB0aGUgYmFjayBvZiB0aGUgcm9vbTxvOnA+
PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPlogaW5jcmVhc2VzIGZyb20gbG93IHRvIGhp
Z2ggKGkuZS4gZmxvb3IgdG8gY2VpbGluZyk8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3Jt
YWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvJz4mbmJzcDs8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz5DYW1lcmFzIGlu
IGEgc2NlbmUgdHlwaWNhbGx5IHBvaW50IGluIHRoZSBkaXJlY3Rpb24gb2YgaW5jcmVhc2luZyBZ
LCBmcm9tIGZyb250IHRvIGJhY2suJm5ic3A7IEJ1dCB0aGVyZSBjb3VsZCBiZSBtdWx0aXBsZSBj
YW1lcmFzIHBvaW50aW5nIGluIGRpZmZlcmVudCBkaXJlY3Rpb25zLiZuYnNwOyBJZiB0aGUgcGh5
c2ljYWwgc3BhY2UgZG9lcyBub3QgaGF2ZSBhIHdlbGwtZGVmaW5lZCBmcm9udCBhbmQgYmFjaywg
dGhlIHByb3ZpZGVyIGNob29zZXMgYW55IGRpcmVjdGlvbiBmb3IgWCBhbmQgWSBjb25zaXN0ZW50
IHdpdGggcmlnaHQtaGFuZGVkIGNvb3JkaW5hdGVzLjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1z
b05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8nPj09PT09PT09PT09PT09IGVuZCBuZXcgdGV4dCA9PT09PT09PT08bzpwPjwvbzpw
PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4mbmJzcDs8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1N
c29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1ib3R0b206MTIu
MHB0Jz5JbiBzZWN0aW9uIDEyIGV4YW1wbGVzLCByZXBsYWNlIOKAnGNhbWVyYS1sZWZ04oCdIGFu
ZCDigJxjYW1lcmEtcmlnaHTigJ0gd2l0aCDigJxsZWZ04oCdIGFuZCDigJxyaWdodOKAnS48bzpw
PjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz5SZWdhcmRzLDxvOnA+PC9vOnA+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8nPk1hcms8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwg
c3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Jz4mbmJzcDs8bzpwPjwvbzpwPjwvcD48L2Rpdj48L2Rpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5
bGU9J21hcmdpbi1ib3R0b206MTIuMHB0Jz48YnI+X19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188YnI+Y2x1ZSBtYWlsaW5nIGxpc3Q8YnI+PGEgaHJlZj0ibWFp
bHRvOmNsdWVAaWV0Zi5vcmciPmNsdWVAaWV0Zi5vcmc8L2E+PGJyPjxhIGhyZWY9Imh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vY2x1ZSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vY2x1ZTwvYT48bzpwPjwvbzpwPjwvcD48
L2Jsb2NrcXVvdGU+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
PjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2PjwvYm9keT48L2h0bWw+

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9221D0CRPMBOXPRD08p_--


From nobody Mon Sep 15 06:02:17 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9CA81A032A for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 06:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pU_1Ir8hh2QM for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 06:02:14 -0700 (PDT)
Received: from mail1.bemta7.messagelabs.com (mail1.bemta7.messagelabs.com [216.82.254.107]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 529331A0328 for <clue@ietf.org>; Mon, 15 Sep 2014 06:02:14 -0700 (PDT)
Received: from [216.82.254.19:33270] by server-11.bemta-7.messagelabs.com id BB/CF-31290-553E6145; Mon, 15 Sep 2014 13:02:13 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-8.tower-96.messagelabs.com!1410786132!10500613!1
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25635 invoked from network); 15 Sep 2014 13:02:13 -0000
Received: from crpehubprd01.polycom.com (HELO crpehubprd02.polycom.com) (140.242.64.158) by server-8.tower-96.messagelabs.com with AES128-SHA encrypted SMTP; 15 Sep 2014 13:02:13 -0000
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by crpehubprd02.polycom.com ([::1]) with mapi; Mon, 15 Sep 2014 06:02:13 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: Christian Groves <Christian.Groves@nteczone.com>, "clue@ietf.org" <clue@ietf.org>
Date: Mon, 15 Sep 2014 06:02:10 -0700
Thread-Topic: [clue] Ticket #61 Proposal for describing the coordinate system
Thread-Index: Ac/QfwyVqGANNpyVSSirXFlTJO/yiwAZfeHA
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9221D1@CRPMBOXPRD08.polycom.com>
References: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com> <541637CD.8060103@nteczone.com>
In-Reply-To: <541637CD.8060103@nteczone.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
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/Eo_HBkwGaiZ_Ry4-eJKLFy8VY1s
Subject: Re: [clue] Ticket #61 Proposal for describing the coordinate system
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 13:02:15 -0000

Hi Christian,
One possibility is a room with a table in the center, people seated all aro=
und the table, with a camera on one wall pointed toward the table, and a ca=
mera on another wall pointed toward the table.
Mark

> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian Groves
> Sent: Sunday, September 14, 2014 8:50 PM
> To: clue@ietf.org
> Subject: Re: [clue] Ticket #61 Proposal for describing the coordinate sys=
tem
>=20
> Hello Mark,
>=20
> I'm OK with the proposal. Do you have an example that you were thinking
> about for the "not well-defined" case?
>=20
> Regards, Christian
>=20
> On 12/09/2014 7:48 AM, Duckworth, Mark wrote:
> >
> > The ticket says describe it without using left/right/front/back
> > terminology, but I don't think that was the point. I think the point
> > is to make it clear the provider can pick the one coordinate system
> > origin and orientation for a scene even if there are multiple cameras
> > pointing in different (even opposite) directions within that scene.
> >
> > So here is a proposal, I would like your feedback.
> >
> > Remove the definition of Front in section 3. Remove the definitions of
> > Camera-Left and Right, and Stage-Left and Right.
> >
> > In section 6. Spatial Relationships, starting with the last bullet
> > item, replace the rest of that section with this:
> >
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D begin new text =3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> >
> > o The coordinate system is right-handed Cartesian X, Y, Z with the
> > origin at a spatial location of the Provider's choosing. The Provider
> > MUST use the same coordinate system with the same scale and origin for
> > all coordinates within the same Capture Scene.
> >
> > The direction of increasing coordinate values is:
> > X increases from left to right, from the point of view of an observer
> > at the front of the room looking toward the back
> >
> > Y increases from the front of the room to the back of the room
> >
> > Z increases from low to high (i.e. floor to ceiling)
> >
> > Cameras in a scene typically point in the direction of increasing Y,
> > from front to back. But there could be multiple cameras pointing in
> > different directions. If the physical space does not have a
> > well-defined front and back, the provider chooses any direction for X
> > and Y consistent with right-handed coordinates.
> >
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D end new text =3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> >
> > In section 12 examples, replace "camera-left" and "camera-right" with
> > "left" and "right".
> >
> > Regards,
> >
> > Mark
> >
> >
> >
> > _______________________________________________
> > clue mailing list
> > clue@ietf.org
> > https://www.ietf.org/mailman/listinfo/clue
>=20
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Mon Sep 15 06:24:31 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA271A034E; Mon, 15 Sep 2014 06:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3gIEewEb8AC; Mon, 15 Sep 2014 06:24:25 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44D0D1A0338; Mon, 15 Sep 2014 06:24:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140915132425.22182.27756.idtracker@ietfa.amsl.com>
Date: Mon, 15 Sep 2014 06:24:25 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/HXeo7EoBQX6AVx-XP3ddXX5YWng
Cc: clue@ietf.org
Subject: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 13:24:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the ControLling mUltiple streams for tElepresence Working Group of the IETF.

        Title           : CLUE Protocol Data Channel
        Author          : Christer Holmberg
	Filename        : draft-ietf-clue-datachannel-01.txt
	Pages           : 13
	Date            : 2014-09-15

Abstract:
   This document defines how to use the WebRTC Data Channel mechanism,
   together with the Data Channel Establishment Protocol (DCEP) in order
   to establish a data channel, referred to as CLUE Data Channel, for
   transporting CLUE protocol messages between two CLUE entities.

   The document defines the SCTP considerations specific to a CLUE Data
   Channel, the SDP offer/answer procedures for negotiating the
   establishment of, and the DCEP procedures for opening, a CLUE Data
   Channel.

   Details and procedures associated with the CLUE protocol are outside
   the scope of this document.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-clue-datachannel-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-clue-datachannel-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Mon Sep 15 06:29:35 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14AEE1A034B for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 06:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jzM3xiHd6Y_G for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 06:29:32 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D071B1A034A for <clue@ietf.org>; Mon, 15 Sep 2014 06:29:31 -0700 (PDT)
X-AuditID: c1b4fb2d-f793d6d000005356-a0-5416e9b98e7a
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 30.21.21334.9B9E6145; Mon, 15 Sep 2014 15:29:30 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0174.001; Mon, 15 Sep 2014 15:29:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "clue@ietf.org" <clue@ietf.org>
Thread-Topic: Draft new version: clue-data-channel-01
Thread-Index: Ac/Q6P1eNDrLxC9JTsiySht2hyqOBQ==
Date: Mon, 15 Sep 2014 13:29:28 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.147]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D44B7EEESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyM+Jvje6ul2IhBs8u8FnsP3WZ2YHRY8mS n0wBjFFcNimpOZllqUX6dglcGdsP3mEqmCBWMXn+J+YGxpvCXYycHBICJhKXdz1nhbDFJC7c W8/WxcjFISRwlFFifut+KGcJo8SevTeYuxg5ONgELCS6/2mDNIgIKEsc3dzPBmILCxhIbD54 iRUibiqxaEMvE4StJ3Hs5Up2EJtFQFXi5p7zzCA2r4CvxMvbd8DijECLv59aA1bPLCAucevJ fCaIgwQklkDVSwiISrx8/I8V5AQJASWJaVvTQExmgXyJ7zOcISYKSpyc+YRlAqPQLCSDZiFU zUJSBVGiI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9iFC1OLS7OTTcy1kstykwuLs7P08tL LdnECIyGg1t+6+5gXP3a8RCjAAejEg/vgh1iIUKsiWXFlbmHGKU5WJTEeRedmxcsJJCeWJKa nZpakFoUX1Sak1p8iJGJg1OqgbFOYuodjV1cUfPurVGU9/v+SOhWxkL+8hbDgLU1D/R+mgXw 7jC75PWW36i03HLlY/GzXIZpHad+VDoyzDK8U3R+ns2ilPC//3m3PC5OLo+Yb+PJ8FFRRqpp ue2GnNR3enHrtd9Pci3P0/M5Ee697r4ip9kS93bx5euWSAY3R3pJct3IVtP6psRSnJFoqMVc VJwIAOYSWtVnAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/dQ1vilDQvqtyvIPdEJJiuJY9yb0
Subject: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 13:29:34 -0000

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

Hi,

I've submitted a new version of the CLUE data channel draft.

The changes are mostly editorial: I structured the O/A procedures according=
 to 3264, and updated the references.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D44B7EEESESSMB209erics_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (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:0cm;
	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;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I&#8217;ve submitted a new version of the CLUE data =
channel draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The changes are mostly editorial: I structured the O=
/A procedures according to 3264, and updated the references.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D44B7EEESESSMB209erics_--


From nobody Mon Sep 15 06:36:53 2014
Return-Path: <spromano@unina.it>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC1501A034D for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 06:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.028
X-Spam-Level: *
X-Spam-Status: No, score=1.028 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rwgQjh9MYi9 for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 06:36:49 -0700 (PDT)
Received: from brc2.unina.it (brc2.unina.it [192.132.34.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44B381A034E for <clue@ietf.org>; Mon, 15 Sep 2014 06:36:49 -0700 (PDT)
X-ASG-Debug-ID: 1410788205-05f2753c1e289d3a0001-dOUo1C
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by brc2.unina.it with ESMTP id qjtwhHUx6kNYcMwz (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Mon, 15 Sep 2014 15:36:45 +0200 (CEST)
X-Barracuda-Envelope-From: spromano@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.62
Received: from [143.225.28.169] ([143.225.28.169]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id s8FDai27031386 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 15 Sep 2014 15:36:45 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_DEDCFCE6-0795-4E51-84FB-C151BC4A43FC"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Simon Pietro Romano <spromano@unina.it>
X-ASG-Orig-Subj: Re: [clue] READV
In-Reply-To: <53DEE1E2.7080208@nteczone.com>
Date: Mon, 15 Sep 2014 15:36:44 +0200
Message-Id: <EA0BDD2F-DB6D-4B27-B5F9-B47B3E89A413@unina.it>
References: <53D05C32.8080500@nteczone.com> <53DEE1E2.7080208@nteczone.com>
To: Christian Groves <Christian.Groves@nteczone.com>
X-Mailer: Apple Mail (2.1878.2)
X-Barracuda-Connect: smtp2.unina.it[192.132.34.62]
X-Barracuda-Start-Time: 1410788205
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.42:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210
X-Barracuda-Spam-Score: -2.02
X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.9504 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE           BODY: HTML included in message
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/NlMDSe-przAmrGEYwndvnuouU-g
Cc: CLUE <clue@ietf.org>
Subject: Re: [clue] READV
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 13:36:52 -0000

--Apple-Mail=_DEDCFCE6-0795-4E51-84FB-C151BC4A43FC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hello Christian,

first of all let me apologize for the long delay before this answer to =
your message. We're currently working on the long mail backlog we =
accumulated during Summer holidays.
As to your question, we actually discussed the points that you had =
raised before the face-to-face meeting in Toronto. The part related to =
READV messages (and responses) is available here:

=
http://recordings.conf.meetecho.com/Recordings/watch.jsp?recording=3DIETF9=
0_CLUE&chapter=3Dpart_2

You can seek directly to minute 0:15:58 for the start of the discussion, =
which lasts approximately until minute 0:21:48.

Cheers,

Simon


On 04/ago/2014, at 03:29, Christian Groves =
<Christian.Groves@nteczone.com> wrote:

> Any reasoning? I can't see the reason why READV-ACK must contain an =
CLUEinfo structure.
>=20
> Christian
>=20
> On 24/07/2014 11:06 AM, Christian Groves wrote:
>> Hello
>>=20
>> I heard that there were some discussions at the meeting regarding the =
READV and in particular questions:
>> 1. Do we need a separate READV response message to carry the CLUE =
data?
>> 2. Couldn't the READV simply trigger the MP to send an ADV?
>>=20
>> It seems that the answer at the meeting to 1 was "Yes" and the answer =
to 2 was "No". Can anyone give some background / reasons for those =
answers? Is there some fundamental issue with using the READV as a =
trigger rather having to send CLUE Advertisement data in the READV =
response? The state machines in the protocol draft appear to use ADV in =
response to a READV.
>>=20
>>=20
>> Regards, Christian
>>=20
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>=20
>=20
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>=20

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

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







--Apple-Mail=_DEDCFCE6-0795-4E51-84FB-C151BC4A43FC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div>Hello Christian,</div><div><br></div><div>first =
of all let me apologize for the long delay before this answer to your =
message. We're currently working on the long mail backlog we accumulated =
during Summer holidays.</div><div>As to your question, we actually =
discussed the points that you had raised before the face-to-face meeting =
in Toronto. The part related to READV messages (and responses) is =
available here:</div><div><br></div><a =
href=3D"http://recordings.conf.meetecho.com/Recordings/watch.jsp?recording=
=3DIETF90_CLUE&amp;chapter=3Dpart_2">http://recordings.conf.meetecho.com/R=
ecordings/watch.jsp?recording=3DIETF90_CLUE&amp;chapter=3Dpart_2</a><div><=
br></div><div>You can seek directly to minute 0:15:58 for the start of =
the discussion, which lasts approximately until minute =
0:21:48.</div><div><br></div><div>Cheers,</div><div><br></div><div>Simon<b=
r><div><br></div><div><br><div><div>On 04/ago/2014, at 03:29, Christian =
Groves &lt;<a =
href=3D"mailto:Christian.Groves@nteczone.com">Christian.Groves@nteczone.co=
m</a>&gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Any reasoning? I can't see the reason why READV-ACK must =
contain an CLUEinfo structure.<br><br>Christian<br><br>On 24/07/2014 =
11:06 AM, Christian Groves wrote:<br><blockquote =
type=3D"cite">Hello<br><br>I heard that there were some discussions at =
the meeting regarding the READV and in particular questions:<br>1. Do we =
need a separate READV response message to carry the CLUE data?<br>2. =
Couldn't the READV simply trigger the MP to send an ADV?<br><br>It seems =
that the answer at the meeting to 1 was "Yes" and the answer to 2 was =
"No". Can anyone give some background / reasons for those answers? Is =
there some fundamental issue with using the READV as a trigger rather =
having to send CLUE Advertisement data in the READV response? The state =
machines in the protocol draft appear to use ADV in response to a =
READV.<br><br><br>Regards, =
Christian<br><br>_______________________________________________<br>clue =
mailing list<br><a =
href=3D"mailto:clue@ietf.org">clue@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/clue<br><br></blockquote><br>______________________________=
_________________<br>clue mailing list<br><a =
href=3D"mailto:clue@ietf.org">clue@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/clue<br><br></blockquote></div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">					=
</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; &nbsp; =
&nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =E8 =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&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; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></div></body></html>=

--Apple-Mail=_DEDCFCE6-0795-4E51-84FB-C151BC4A43FC--


From nobody Mon Sep 15 08:01:46 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A375B1A036B for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 08:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f5jvnWB0AHi6 for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 08:01:43 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 13DBC1A034E for <clue@ietf.org>; Mon, 15 Sep 2014 08:01:42 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta12.westchester.pa.mail.comcast.net with comcast id rS2f1o0031uE5Es5CT1ik1; Mon, 15 Sep 2014 15:01:42 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta16.westchester.pa.mail.comcast.net with comcast id rT1i1o0053Ge9ey3cT1iky; Mon, 15 Sep 2014 15:01:42 +0000
Message-ID: <5416FF56.10605@alum.mit.edu>
Date: Mon, 15 Sep 2014 11:01:42 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F078C1206D0@CRPMBOXPRD08.polycom.com> <541637CD.8060103@nteczone.com>
In-Reply-To: <541637CD.8060103@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1410793302; bh=H/jlT96EByeUom4QFm+brc/Oz2QXWzibnQ/w1GhmUh8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=iP6WM6+IG+jic8fbu/ndPHUKOLBFX4G8TVaaHycqBuRh+lIJUx79GQ+wOm9My7IYO ISiQo2K3a9t45JoLasw3KmOd3wsf3DlHfjSmOuVPf1KF1fJMmKiWQKuqN38HWwMUSz 6FMFQZBt3o3pv/Wi099Gg+nGNiN6i3RlRBB5FZWoc+ZpK4Yk8C7jshR9h2fYrWhasO vOXIIpZaMRcjewsacF/Ax/+mlRP6/XUHfDBz1f/ekWKEt3OWzONsv8VUnFgiTX12O3 79CpzpO1Acy8zcJ1VIDpUkTS885Kwy1TUAa89OvOljrU9ftekdPMkBGdX/e2vUqDs8 nhr/Y7yFXcpsw==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/i_zknhUPwUsj-1cowPRlfYdG8Bc
Subject: Re: [clue] Ticket #61 Proposal for describing the coordinate system
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 15:01:44 -0000

On 9/14/14 8:50 PM, Christian Groves wrote:
> Hello Mark,
>
> I'm OK with the proposal. Do you have an example that you were thinking
> about for the "not well-defined" case?

The operating room in the telemedical use case.

	Thanks,
	Paul

> Regards, Christian
>
> On 12/09/2014 7:48 AM, Duckworth, Mark wrote:
>>
>> The ticket says describe it without using left/right/front/back
>> terminology, but I don’t think that was the point. I think the point
>> is to make it clear the provider can pick the one coordinate system
>> origin and orientation for a scene even if there are multiple cameras
>> pointing in different (even opposite) directions within that scene.
>>
>> So here is a proposal, I would like your feedback.
>>
>> Remove the definition of Front in section 3. Remove the definitions of
>> Camera-Left and Right, and Stage-Left and Right.
>>
>> In section 6. Spatial Relationships, starting with the last bullet
>> item, replace the rest of that section with this:
>>
>> ============== begin new text =========
>>
>> o The coordinate system is right-handed Cartesian X, Y, Z with the
>> origin at a spatial location of the Provider's choosing. The Provider
>> MUST use the same coordinate system with the same scale and origin for
>> all coordinates within the same Capture Scene.
>>
>> The direction of increasing coordinate values is:
>> X increases from left to right, from the point of view of an observer
>> at the front of the room looking toward the back
>>
>> Y increases from the front of the room to the back of the room
>>
>> Z increases from low to high (i.e. floor to ceiling)
>>
>> Cameras in a scene typically point in the direction of increasing Y,
>> from front to back. But there could be multiple cameras pointing in
>> different directions. If the physical space does not have a
>> well-defined front and back, the provider chooses any direction for X
>> and Y consistent with right-handed coordinates.
>>
>> ============== end new text =========
>>
>> In section 12 examples, replace “camera-left” and “camera-right” with
>> “left” and “right”.
>>
>> Regards,
>>
>> Mark
>>
>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Mon Sep 15 14:05:22 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B7481A875A for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 14:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vTehd3CyIWUr for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 14:05:15 -0700 (PDT)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C3AF1A874F for <clue@ietf.org>; Mon, 15 Sep 2014 14:05:14 -0700 (PDT)
Received: by mail-lb0-f173.google.com with SMTP id w7so5300933lbi.32 for <clue@ietf.org>; Mon, 15 Sep 2014 14:05:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=S+SvzB56zXBSEGiBXRrNbQGXWl9AvkUS7ZyqOf4jQcc=; b=W/E3Mk9tcxVhLEIc4iS24tfrddhirVhCWUBunMmWPonD3kLzFapOWtBOS3SDKJ0oPs +arLjGbQVYA8IYvrhYtNmPBK95uY/b8dQ4krJg/PSpW4q1wLfkNovpojh2ffHntFMQK2 QVspOPBNEvoAmwCCwPFazcvgTucrzMQeey7WROeWBLsX2IGfQdv2jSIr7Rfvn0UHI/fl by29EMUNwyOiPxnwJ4EYQ6uB+yxXcUQiPG01Dkqj8CexUAwifD1vg2DfYUgfFotzkXPu kKVcgZ6Vh77NHLZtaJWiHABrdEaeqUoZ294NcvczBF0L7YeV5fvELNfbYIjupeMIueQO XtHg==
MIME-Version: 1.0
X-Received: by 10.152.26.133 with SMTP id l5mr32228603lag.4.1410815112825; Mon, 15 Sep 2014 14:05:12 -0700 (PDT)
Received: by 10.25.12.207 with HTTP; Mon, 15 Sep 2014 14:05:12 -0700 (PDT)
Date: Mon, 15 Sep 2014 16:05:12 -0500
Message-ID: <CAHBDyN5+LFjxKSEPK99BCqqVyHvXUfuhFr2k1QtA+7ER-OWoZg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: CLUE <clue@ietf.org>
Content-Type: multipart/alternative; boundary=089e0160a6faa4d149050320fd52
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/CiTOIKjSae58W9VaYhgnfm-ruz4
Subject: [clue] Reminder: Design Team meeting tomorrow
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 21:05:22 -0000

--089e0160a6faa4d149050320fd52
Content-Type: text/plain; charset=UTF-8

Hi all,

As noted in the email last week, we have identified topics for each of the
upcoming design team meetings. The focus is on discussing and resolving
open issues for each of the WG documents:
http://trac.tools.ietf.org/wg/clue/trac/wiki/Design-Team

Thus, we will be talking about open issues in the signaling document:
http://trac.tools.ietf.org/wg/clue/trac/ticket/50
http://trac.tools.ietf.org/wg/clue/trac/ticket/53

The call logistics are on the wiki.

Regards,
Mary

--089e0160a6faa4d149050320fd52
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>As noted in the email last week=
, we have identified topics for each of the upcoming design team meetings. =
The focus is on discussing and resolving open issues for each of the WG doc=
uments:</div><div><a href=3D"http://trac.tools.ietf.org/wg/clue/trac/wiki/D=
esign-Team">http://trac.tools.ietf.org/wg/clue/trac/wiki/Design-Team</a></d=
iv><div><br></div><div>Thus, we will be talking about open issues in the si=
gnaling document:<br></div><div><a href=3D"http://trac.tools.ietf.org/wg/cl=
ue/trac/ticket/50">http://trac.tools.ietf.org/wg/clue/trac/ticket/50</a></d=
iv><div><a href=3D"http://trac.tools.ietf.org/wg/clue/trac/ticket/53">http:=
//trac.tools.ietf.org/wg/clue/trac/ticket/53</a></div><div><br></div><div>T=
he call logistics are on the wiki.<br></div><div><br></div><div>Regards,<br=
></div><div>Mary=C2=A0</div><div><br></div></div>

--089e0160a6faa4d149050320fd52--


From nobody Mon Sep 15 17:31:09 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 567261A00AD for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 17:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rWzH19VtJHOg for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 17:31:06 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E05C61A00A7 for <clue@ietf.org>; Mon, 15 Sep 2014 17:31:05 -0700 (PDT)
Received: from ppp118-209-111-109.lns20.mel4.internode.on.net ([118.209.111.109]:53255 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XTge7-0007bG-0K for clue@ietf.org; Tue, 16 Sep 2014 10:29:27 +1000
Message-ID: <541784C5.1090403@nteczone.com>
Date: Tue, 16 Sep 2014 10:31:01 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "clue@ietf.org" <clue@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/WAL1rWFpaUvMUHkx1H2UWrHTSB4
Subject: [clue] Partial updates draft-groves-clue-partial-update-00
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 00:31:07 -0000

Hello all,

I've submitted a new draft draft-groves-clue-partial-update-00 
(http://tools.ietf.org/html/draft-groves-clue-partial-update-00) 
addressing ticket #25: Advertisement: Complete "all" or "delta" Changes.

Basically it discusses a partial update mechanism using XML patch ops as 
per RFC6502. The declarations of the XML schema may need tweaking but 
hopefully the intention is clear.

Regards, Christian


From nobody Mon Sep 15 17:57:37 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 189371A00AF for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 17:57:36 -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_40=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zNwTtRVJZxBz for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 17:57:34 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F06851A0099 for <clue@ietf.org>; Mon, 15 Sep 2014 17:57:33 -0700 (PDT)
Received: from ppp118-209-111-109.lns20.mel4.internode.on.net ([118.209.111.109]:53459 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XTh3j-00039Q-Eu; Tue, 16 Sep 2014 10:55:55 +1000
Message-ID: <54178AFA.3060101@nteczone.com>
Date: Tue, 16 Sep 2014 10:57:30 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Simon Pietro Romano <spromano@unina.it>
References: <53D05C32.8080500@nteczone.com> <53DEE1E2.7080208@nteczone.com> <EA0BDD2F-DB6D-4B27-B5F9-B47B3E89A413@unina.it>
In-Reply-To: <EA0BDD2F-DB6D-4B27-B5F9-B47B3E89A413@unina.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/A6birQlRV7TWT8Ux_oaeRy35_DY
Cc: CLUE <clue@ietf.org>
Subject: Re: [clue] READV
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 00:57:36 -0000

Hello Simon,

Thanks for the reply. I listened to the discussion and it seemed that 
the motivation was to identify the different between CLUE data from an 
MP initiated message (i.e. Advertisement) versus a MC initiated message 
(Readv/Readv.response). Is that correct?

I wonder what the MC makes of this distinction? My understanding is that 
given a point in time the MP would send exactly the same CLUE data in an 
Advertisement or Readv.response because it's media capabilities remain 
the same. Is that a fair assumption?

Regards, Christian

On 15/09/2014 11:36 PM, Simon Pietro Romano wrote:
> Hello Christian,
>
> first of all let me apologize for the long delay before this answer to 
> your message. We're currently working on the long mail backlog we 
> accumulated during Summer holidays.
> As to your question, we actually discussed the points that you had 
> raised before the face-to-face meeting in Toronto. The part related to 
> READV messages (and responses) is available here:
>
> http://recordings.conf.meetecho.com/Recordings/watch.jsp?recording=IETF90_CLUE&chapter=part_2 
>
>
> You can seek directly to minute 0:15:58 for the start of the 
> discussion, which lasts approximately until minute 0:21:48.
>
> Cheers,
>
> Simon
>
>
> On 04/ago/2014, at 03:29, Christian Groves 
> <Christian.Groves@nteczone.com <mailto:Christian.Groves@nteczone.com>> 
> wrote:
>
>> Any reasoning? I can't see the reason why READV-ACK must contain an 
>> CLUEinfo structure.
>>
>> Christian
>>
>> On 24/07/2014 11:06 AM, Christian Groves wrote:
>>> Hello
>>>
>>> I heard that there were some discussions at the meeting regarding 
>>> the READV and in particular questions:
>>> 1. Do we need a separate READV response message to carry the CLUE data?
>>> 2. Couldn't the READV simply trigger the MP to send an ADV?
>>>
>>> It seems that the answer at the meeting to 1 was "Yes" and the 
>>> answer to 2 was "No". Can anyone give some background / reasons for 
>>> those answers? Is there some fundamental issue with using the READV 
>>> as a trigger rather having to send CLUE Advertisement data in the 
>>> READV response? The state machines in the protocol draft appear to 
>>> use ADV in response to a READV.
>>>
>>>
>>> Regards, Christian
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org <mailto:clue@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org <mailto:clue@ietf.org>
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
>     _\\|//_
>   ( O-O )
>  ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
> Simon Pietro Romano
> Universita' di Napoli Federico II
>  Computer Engineering Department
>          Phone: +39 081 7683823 -- Fax: +39 081 7683816
>    e-mail: spromano@unina.it <mailto:spromano@unina.it>
>
> <<Molti mi dicono che lo scoraggiamento è l'alibi degli
>  idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>                  oooO
>   ~~~~~~~~~~~~~~~~~~~~~~~( )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>              \ (            (   )
>                               \_)  ) /
>                                (_/
>
>
>
>
>
>


From nobody Mon Sep 15 18:12:53 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E63571A00D8 for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 18:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fBE34_C-6CU4 for <clue@ietfa.amsl.com>; Mon, 15 Sep 2014 18:12:51 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE2401A00D7 for <clue@ietf.org>; Mon, 15 Sep 2014 18:12:50 -0700 (PDT)
Received: from ppp118-209-111-109.lns20.mel4.internode.on.net ([118.209.111.109]:53515 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XThIW-0005cD-Rg for clue@ietf.org; Tue, 16 Sep 2014 11:11:12 +1000
Message-ID: <54178E8F.8090809@nteczone.com>
Date: Tue, 16 Sep 2014 11:12:47 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/rnq9A7YQaswGcmO6Z2SDnrsZTIc
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 01:12:52 -0000

Hello Christer,

Just a question on 5.7 where it says "If an offerer wants to disable the 
CLUE Data Channel in an offer, it assigns a zero port value to the "m=" 
line representing the SCTPoDTLS association used to realize the CLUE 
Data channel."

Wouldn't this have the effect of closing the SCTP/DTLS association 
causing CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 
seem to be for a generic webrtc data channel. To have a "CLUE data 
channel" we use the a=group.

i.e. Generic Data Channel
m=application 54111 SCTP/DTLS 54111
a=sctpmap:54111 webrtc-datachannel

CLUE data channel
a=group:CLUE 100
m=application 54111 SCTP/DTLS 54111
a=sctpmap:54111 webrtc-datachannel
a=mid:100

Therefore if an endpoint wanted to remove CLUE from the data channel 
(without closing the SCTP/DTLS associated) it would remove the a=group 
and a=mid.

There's also a typo in clause 5.7 "are unchanged" is repeated.

Regards, Christian

On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>
> Hi,
>
> I’ve submitted a new version of the CLUE data channel draft.
>
> The changes are mostly editorial: I structured the O/A procedures 
> according to 3264, and updated the references.
>
> Regards,
>
> Christer
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Tue Sep 16 05:15:16 2014
Return-Path: <spromano@unina.it>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8161C1A0672 for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 05:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.672
X-Spam-Level: 
X-Spam-Status: No, score=-1.672 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2dgZiI7bWFA for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 05:15:11 -0700 (PDT)
Received: from brc2.unina.it (brc2.unina.it [192.132.34.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 252E11A02D4 for <clue@ietf.org>; Tue, 16 Sep 2014 05:15:11 -0700 (PDT)
X-ASG-Debug-ID: 1410869707-05f2753c20290df00001-dOUo1C
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by brc2.unina.it with ESMTP id LEVqEX3dqOtRxy8L (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Tue, 16 Sep 2014 14:15:07 +0200 (CEST)
X-Barracuda-Envelope-From: spromano@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.62
Received: from [143.225.28.169] ([143.225.28.169]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id s8GCF4Fd011162 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Sep 2014 14:15:05 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_C1D09684-49B8-4783-B50F-782FDB931BFA"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Simon Pietro Romano <spromano@unina.it>
X-ASG-Orig-Subj: Re: [clue] READV
In-Reply-To: <54178AFA.3060101@nteczone.com>
Date: Tue, 16 Sep 2014 14:15:05 +0200
Message-Id: <05D0CB08-299C-4842-B2C3-84649305312C@unina.it>
References: <53D05C32.8080500@nteczone.com> <53DEE1E2.7080208@nteczone.com> <EA0BDD2F-DB6D-4B27-B5F9-B47B3E89A413@unina.it> <54178AFA.3060101@nteczone.com>
To: Christian Groves <Christian.Groves@nteczone.com>
X-Mailer: Apple Mail (2.1878.2)
X-Barracuda-Connect: smtp2.unina.it[192.132.34.62]
X-Barracuda-Start-Time: 1410869707
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.42:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210
X-Barracuda-Spam-Score: -2.02
X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.9545 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE           BODY: HTML included in message
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/aaZUpl7R_3HT7DmiHhYfZgvRMWk
Cc: CLUE <clue@ietf.org>
Subject: Re: [clue] READV
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 12:15:13 -0000

--Apple-Mail=_C1D09684-49B8-4783-B50F-782FDB931BFA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hello Christian,

> I wonder what the MC makes of this distinction? My understanding is =
that given a point in time the MP would send exactly the same CLUE data =
in an Advertisement or Readv.response because it's media capabilities =
remain the same. Is that a fair assumption?

It is. As I said, there is just a (subtle) semantic difference.

Cheers,

Simon

> Regards, Christian
>=20
> On 15/09/2014 11:36 PM, Simon Pietro Romano wrote:
>> Hello Christian,
>>=20
>> first of all let me apologize for the long delay before this answer =
to your message. We're currently working on the long mail backlog we =
accumulated during Summer holidays.
>> As to your question, we actually discussed the points that you had =
raised before the face-to-face meeting in Toronto. The part related to =
READV messages (and responses) is available here:
>>=20
>> =
http://recordings.conf.meetecho.com/Recordings/watch.jsp?recording=3DIETF9=
0_CLUE&chapter=3Dpart_2=20
>>=20
>> You can seek directly to minute 0:15:58 for the start of the =
discussion, which lasts approximately until minute 0:21:48.
>>=20
>> Cheers,
>>=20
>> Simon
>>=20
>>=20
>> On 04/ago/2014, at 03:29, Christian Groves =
<Christian.Groves@nteczone.com<mailto:Christian.Groves@nteczone.com>> =
wrote:
>>=20
>>> Any reasoning? I can't see the reason why READV-ACK must contain an =
CLUEinfo structure.
>>>=20
>>> Christian
>>>=20
>>> On 24/07/2014 11:06 AM, Christian Groves wrote:
>>>> Hello
>>>>=20
>>>> I heard that there were some discussions at the meeting regarding =
the READV and in particular questions:
>>>> 1. Do we need a separate READV response message to carry the CLUE =
data?
>>>> 2. Couldn't the READV simply trigger the MP to send an ADV?
>>>>=20
>>>> It seems that the answer at the meeting to 1 was "Yes" and the =
answer to 2 was "No". Can anyone give some background / reasons for =
those answers? Is there some fundamental issue with using the READV as a =
trigger rather having to send CLUE Advertisement data in the READV =
response? The state machines in the protocol draft appear to use ADV in =
response to a READV.
>>>>=20
>>>>=20
>>>> Regards, Christian
>>>>=20
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org <mailto:clue@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>=20
>>>=20
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org <mailto:clue@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/clue
>>>=20
>>=20
>>    _\\|//_
>>  ( O-O )
>> ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>> Simon Pietro Romano
>> Universita' di Napoli Federico II
>> Computer Engineering Department
>>         Phone: +39 081 7683823 -- Fax: +39 081 7683816
>>   e-mail: spromano@unina.it <mailto:spromano@unina.it>
>>=20
>> <<Molti mi dicono che lo scoraggiamento =E8 l'alibi degli
>> idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>>                 oooO
>>  ~~~~~~~~~~~~~~~~~~~~~~~( )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>>             \ (            (   )
>>                              \_)  ) /
>>                               (_/

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

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







--Apple-Mail=_C1D09684-49B8-4783-B50F-782FDB931BFA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello =
Christian,<div><br><div><div><blockquote type=3D"cite"><div =
style=3D"font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;">I wonder what the MC makes of this =
distinction? My understanding is that given a point in time the MP would =
send exactly the same CLUE data in an Advertisement or Readv.response =
because it's media capabilities remain the same. Is that a fair =
assumption?<br></div></blockquote><div><br></div>It is. As I said, there =
is just a (subtle) semantic =
difference.</div><div><br></div><div>Cheers,</div><div><br></div><div>Simo=
n</div><div><br><blockquote type=3D"cite"><div style=3D"font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">Regards, Christian<br><br>On 15/09/2014 11:36 PM, Simon Pietro =
Romano wrote:<br><blockquote type=3D"cite">Hello Christian,<br><br>first =
of all let me apologize for the long delay before this answer to your =
message. We're currently working on the long mail backlog we accumulated =
during Summer holidays.<br>As to your question, we actually discussed =
the points that you had raised before the face-to-face meeting in =
Toronto. The part related to READV messages (and responses) is available =
here:<br><br><a =
href=3D"http://recordings.conf.meetecho.com/Recordings/watch.jsp?recording=
=3DIETF90_CLUE&amp;chapter=3Dpart_2">http://recordings.conf.meetecho.com/R=
ecordings/watch.jsp?recording=3DIETF90_CLUE&amp;chapter=3Dpart_2</a><span =
class=3D"Apple-converted-space">&nbsp;</span><br><br>You can seek =
directly to minute 0:15:58 for the start of the discussion, which lasts =
approximately until minute =
0:21:48.<br><br>Cheers,<br><br>Simon<br><br><br>On 04/ago/2014, at =
03:29, Christian Groves &lt;<a =
href=3D"mailto:Christian.Groves@nteczone.com">Christian.Groves@nteczone.co=
m</a>&lt;<a =
href=3D"mailto:Christian.Groves@nteczone.com">mailto:Christian.Groves@ntec=
zone.com</a>&gt;&gt; wrote:<br><br><blockquote type=3D"cite">Any =
reasoning? I can't see the reason why READV-ACK must contain an CLUEinfo =
structure.<br><br>Christian<br><br>On 24/07/2014 11:06 AM, Christian =
Groves wrote:<br><blockquote type=3D"cite">Hello<br><br>I heard that =
there were some discussions at the meeting regarding the READV and in =
particular questions:<br>1. Do we need a separate READV response message =
to carry the CLUE data?<br>2. Couldn't the READV simply trigger the MP =
to send an ADV?<br><br>It seems that the answer at the meeting to 1 was =
"Yes" and the answer to 2 was "No". Can anyone give some background / =
reasons for those answers? Is there some fundamental issue with using =
the READV as a trigger rather having to send CLUE Advertisement data in =
the READV response? The state machines in the protocol draft appear to =
use ADV in response to a READV.<br><br><br>Regards, =
Christian<br><br>_______________________________________________<br>clue =
mailing list<br><a href=3D"mailto:clue@ietf.org">clue@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>&lt;<a =
href=3D"mailto:clue@ietf.org">mailto:clue@ietf.org</a>&gt;<br><a =
href=3D"https://www.ietf.org/mailman/listinfo/clue">https://www.ietf.org/m=
ailman/listinfo/clue</a><br><br></blockquote><br>_________________________=
______________________<br>clue mailing list<br><a =
href=3D"mailto:clue@ietf.org">clue@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>&lt;<a =
href=3D"mailto:clue@ietf.org">mailto:clue@ietf.org</a>&gt;<br><a =
href=3D"https://www.ietf.org/mailman/listinfo/clue">https://www.ietf.org/m=
ailman/listinfo/clue</a><br><br></blockquote><br>&nbsp;&nbsp;&nbsp;_\\|//_=
<br>&nbsp;( O-O =
)<br>~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~<br>Simon =
Pietro Romano<br>Universita' di Napoli Federico II<br>Computer =
Engineering =
Department<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Phone: +39 =
081 7683823 -- Fax: +39 081 7683816<br>&nbsp;&nbsp;e-mail:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a><span =
class=3D"Apple-converted-space">&nbsp;</span>&lt;<a =
href=3D"mailto:spromano@unina.it">mailto:spromano@unina.it</a>&gt;<br><br>=
&lt;&lt;Molti mi dicono che lo scoraggiamento =E8 l'alibi =
degli<br>idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;oooO<br>&nbsp;~~~~~~~~~~~~~~~~~~~~~~~( =
)~~~ =
Oooo~~~~~~~~~~~~~~~~~~~~~~~~~<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;)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&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;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(_/</blockquote></div></blockquote></=
div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">					=
</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; &nbsp; =
&nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =E8 =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&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; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></div></body></html>=

--Apple-Mail=_C1D09684-49B8-4783-B50F-782FDB931BFA--


From nobody Tue Sep 16 06:13:51 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A831A06EF for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 06:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R3XaB6zNF3zl for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 06:13:46 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE2C81A06ED for <clue@ietf.org>; Tue, 16 Sep 2014 06:13:45 -0700 (PDT)
Received: from ppp118-209-111-109.lns20.mel4.internode.on.net ([118.209.111.109]:52335 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XTsY4-0000Ok-1Z; Tue, 16 Sep 2014 23:12:00 +1000
Message-ID: <54183785.1040003@nteczone.com>
Date: Tue, 16 Sep 2014 23:13:41 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Simon Pietro Romano <spromano@unina.it>
References: <53D05C32.8080500@nteczone.com> <53DEE1E2.7080208@nteczone.com> <EA0BDD2F-DB6D-4B27-B5F9-B47B3E89A413@unina.it> <54178AFA.3060101@nteczone.com> <05D0CB08-299C-4842-B2C3-84649305312C@unina.it>
In-Reply-To: <05D0CB08-299C-4842-B2C3-84649305312C@unina.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/i1L8vXw5R0jYP4EsNdvKtDbEhSI
Cc: CLUE <clue@ietf.org>
Subject: Re: [clue] READV
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 13:13:49 -0000

Hello Simon,

Given its the same media capabilities then I'm not sure there is a 
semantic difference.

The other concern I have is what happens in terms of error handling? If 
a Media Consumer has trouble parsing the CLUE info in a received 
Advertisement it can send a NACK. What happens when a Media Consumer has 
trouble parsing CLUEinfo in a READV.response?

As I mentioned below the state machine seems to support the READV 
triggering a new Advertisement.

Regards, Christian

On 16/09/2014 10:15 PM, Simon Pietro Romano wrote:
> Hello Christian,
>
>> I wonder what the MC makes of this distinction? My understanding is 
>> that given a point in time the MP would send exactly the same CLUE 
>> data in an Advertisement or Readv.response because it's media 
>> capabilities remain the same. Is that a fair assumption?
>
> It is. As I said, there is just a (subtle) semantic difference.
>
> Cheers,
>
> Simon
>
>> Regards, Christian
>>
>> On 15/09/2014 11:36 PM, Simon Pietro Romano wrote:
>>> Hello Christian,
>>>
>>> first of all let me apologize for the long delay before this answer 
>>> to your message. We're currently working on the long mail backlog we 
>>> accumulated during Summer holidays.
>>> As to your question, we actually discussed the points that you had 
>>> raised before the face-to-face meeting in Toronto. The part related 
>>> to READV messages (and responses) is available here:
>>>
>>> http://recordings.conf.meetecho.com/Recordings/watch.jsp?recording=IETF90_CLUE&chapter=part_2
>>>
>>> You can seek directly to minute 0:15:58 for the start of the 
>>> discussion, which lasts approximately until minute 0:21:48.
>>>
>>> Cheers,
>>>
>>> Simon
>>>
>>>
>>> On 04/ago/2014, at 03:29, Christian Groves 
>>> <Christian.Groves@nteczone.com 
>>> <mailto:Christian.Groves@nteczone.com><mailto:Christian.Groves@nteczone.com>> 
>>> wrote:
>>>
>>>> Any reasoning? I can't see the reason why READV-ACK must contain an 
>>>> CLUEinfo structure.
>>>>
>>>> Christian
>>>>
>>>> On 24/07/2014 11:06 AM, Christian Groves wrote:
>>>>> Hello
>>>>>
>>>>> I heard that there were some discussions at the meeting regarding 
>>>>> the READV and in particular questions:
>>>>> 1. Do we need a separate READV response message to carry the CLUE 
>>>>> data?
>>>>> 2. Couldn't the READV simply trigger the MP to send an ADV?
>>>>>
>>>>> It seems that the answer at the meeting to 1 was "Yes" and the 
>>>>> answer to 2 was "No". Can anyone give some background / reasons 
>>>>> for those answers? Is there some fundamental issue with using the 
>>>>> READV as a trigger rather having to send CLUE Advertisement data 
>>>>> in the READV response? The state machines in the protocol draft 
>>>>> appear to use ADV in response to a READV.
>>>>>
>>>>>
>>>>> Regards, Christian
>>>>>
>>>>> _______________________________________________
>>>>> clue mailing list
>>>>> clue@ietf.org <mailto:clue@ietf.org><mailto:clue@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>>
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org <mailto:clue@ietf.org><mailto:clue@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>
>>>
>>>    _\\|//_
>>>  ( O-O )
>>> ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>>> Simon Pietro Romano
>>> Universita' di Napoli Federico II
>>> Computer Engineering Department
>>>         Phone: +39 081 7683823 -- Fax: +39 081 7683816
>>>   e-mail:spromano@unina.it 
>>> <mailto:spromano@unina.it><mailto:spromano@unina.it>
>>>
>>> <<Molti mi dicono che lo scoraggiamento è l'alibi degli
>>> idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>>>                 oooO
>>>  ~~~~~~~~~~~~~~~~~~~~~~~( )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>>>             \ (            (   )
>>>                              \_)  ) /
>>>                               (_/
>
>     _\\|//_
>   ( O-O )
>  ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
> Simon Pietro Romano
> Universita' di Napoli Federico II
>  Computer Engineering Department
>          Phone: +39 081 7683823 -- Fax: +39 081 7683816
>    e-mail: spromano@unina.it <mailto:spromano@unina.it>
>
> <<Molti mi dicono che lo scoraggiamento è l'alibi degli
>  idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>                  oooO
>   ~~~~~~~~~~~~~~~~~~~~~~~( )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>              \ (            (   )
>                               \_)  ) /
>                                (_/
>
>
>
>
>
>


From nobody Tue Sep 16 06:46:45 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF5C51A0709 for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 06:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c7c4MW9fr-3W for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 06:46:35 -0700 (PDT)
Received: from mail1.bemta7.messagelabs.com (mail1.bemta7.messagelabs.com [216.82.254.111]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 107111A0515 for <clue@ietf.org>; Tue, 16 Sep 2014 06:46:26 -0700 (PDT)
Received: from [216.82.254.19:13524] by server-15.bemta-7.messagelabs.com id 99/5A-09096-23F38145; Tue, 16 Sep 2014 13:46:26 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-16.tower-96.messagelabs.com!1410875143!11829267!1
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3385 invoked from network); 16 Sep 2014 13:45:44 -0000
Received: from crpehubprd01.polycom.com (HELO Crpehubprd01.polycom.com) (140.242.64.158) by server-16.tower-96.messagelabs.com with AES128-SHA encrypted SMTP; 16 Sep 2014 13:45:44 -0000
Received: from PWEHUB01.polycom.com (10.236.2.221) by Crpehubprd01.polycom.com (10.236.0.158) with Microsoft SMTP Server (TLS) id 8.3.192.1; Tue, 16 Sep 2014 06:45:43 -0700
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by PWEHUB01.polycom.com ([fe80::99a8:f785:3f0c:2bb6%17]) with mapi; Tue, 16 Sep 2014 06:45:42 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "clue@ietf.org" <clue@ietf.org>
Date: Tue, 16 Sep 2014 06:45:39 -0700
Thread-Topic: Notes from design team meeting re: signaling open issues
Thread-Index: Ac/RtGsutx78PYASQWO5au764TKMEQ==
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.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_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FECRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/AIEOQUGXKmFOpgTu18UHuhAruMA
Subject: [clue] Notes from design team meeting re: signaling open issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 13:46:42 -0000

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

Here are my notes from the design team meeting.

CLUE signaling design team meeting
Sep 16, 2014
Rob Hansen, Mary Barnes, Paul Kyzivat, Mark Duckworth, Christian Groves, Ro=
berta Presta, Roni Even, Jonathan Lennox
Rob discussed issues
*         Fallback to non-CLUE - when does it happen?
o    signalling document has a proposal that defines when this happens, but=
 there are other ideas
o    Rob's idea (in the signaling doc) is to use the same criteria to enabl=
e CLUE as to disable it
o    If data channel connection is lost, probably don't want that to mean t=
he call is not CLUE enabled any more
o    The group agrees with Rob's proposal
*         Fallback to non-CLUE - what does it mean?
o    When fallback to non CLUE-enabled occurs, then CLUE-controlled media s=
tops.
o    some other details about handling data channel and CLUE protocol shoul=
d be defined
o    Should close the CLUE channel.  Can keep SCTP open if it is used for o=
ther things.
*         When making an SDP offer, if the offerer wants to enable CLUE the=
n SDP should indicate this.  Even if previous O/A exchanges have not enable=
d CLUE.  This is consistent with an offerer always including video if it wa=
nts to add video to an audio call.
*         Security issues
o    Mary made suggestions
o    This doc shouldn't have a heavy security section.  Using existing prot=
ocols.
o    Jonathan suggested mention case of SDP and SCTP going to different add=
resses, one is attacker one is victim?
o    Mary plans to get a security review done during WGLC


--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FECRPMBOXPRD08p_
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:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m=3D"http://sc=
hemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-=
html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; chars=
et=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 (filtere=
d 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;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:34472937;
	mso-list-template-ids:-2024756612;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1526937716;
	mso-list-template-ids:21677732;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2
	{mso-list-id:1593664333;
	mso-list-template-ids:-1863956686;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3
	{mso-list-id:1868518767;
	mso-list-template-ids:-1166388616;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Here are my note=
s from the design team meeting.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal>CLUE signaling design team meeting<o:p></=
o:p></p><p class=3DMsoNormal>Sep 16, 2014 <o:p></o:p></p><p class=3DMsoNorm=
al>Rob Hansen, Mary Barnes, Paul Kyzivat, Mark Duckworth, Christian Groves,=
 Roberta Presta, Roni Even, Jonathan Lennox<o:p></o:p></p><p class=3DMsoNor=
mal>Rob discussed issues<o:p></o:p></p><p class=3DMsoNormal style=3D'margin=
-left:27.0pt;text-indent:-.25in;mso-list:l2 level1 lfo1;vertical-align:midd=
le'><![if !supportLists]><span style=3D'font-size:10.0pt;font-family:Symbol=
'><span style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>=
</span><![endif]>Fallback to non-CLUE - when does it happen?<span style=3D'=
font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span><=
/p><p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-l=
ist:l2 level2 lfo1;vertical-align:middle'><![if !supportLists]><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ign=
ore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </spa=
n></span></span><![endif]>signalling document has a proposal that defines w=
hen this happens, but there are other ideas<span style=3D'font-size:12.0pt;=
font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=3DMso=
Normal style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l2 level2 lfo=
1;vertical-align:middle'><![if !supportLists]><span style=3D'font-size:10.0=
pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><=
![endif]>Rob's idea (in the signaling doc) is to use the same criteria to e=
nable CLUE as to disable it<span style=3D'font-size:12.0pt;font-family:"Tim=
es New Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'=
margin-left:.75in;text-indent:-.25in;mso-list:l2 level2 lfo1;vertical-align=
:middle'><![if !supportLists]><span style=3D'font-size:10.0pt;font-family:"=
Courier New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "T=
imes New Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>If data =
channel connection is lost, probably don't want that to mean the call is no=
t CLUE enabled any more<span style=3D'font-size:12.0pt;font-family:"Times N=
ew Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'marg=
in-left:.75in;text-indent:-.25in;mso-list:l2 level2 lfo1;vertical-align:mid=
dle'><![if !supportLists]><span style=3D'font-size:10.0pt;font-family:"Cour=
ier New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times=
 New Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>The group ag=
rees with Rob's proposal<span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'mar=
gin-left:27.0pt;text-indent:-.25in;mso-list:l1 level1 lfo2;vertical-align:m=
iddle'><![if !supportLists]><span style=3D'font-size:10.0pt;font-family:Sym=
bol'><span style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Tim=
es New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></sp=
an></span><![endif]>Fallback to non-CLUE - what does it mean?<span style=3D=
'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span>=
</p><p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-=
list:l1 level2 lfo2;vertical-align:middle'><![if !supportLists]><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ign=
ore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </spa=
n></span></span><![endif]>When fallback to non CLUE-enabled occurs, then CL=
UE-controlled media stops.<span style=3D'font-size:12.0pt;font-family:"Time=
s New Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'm=
argin-left:.75in;text-indent:-.25in;mso-list:l1 level2 lfo2;vertical-align:=
middle'><![if !supportLists]><span style=3D'font-size:10.0pt;font-family:"C=
ourier New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Ti=
mes New Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>some othe=
r details about handling data channel and CLUE protocol should be defined<s=
pan style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p><=
/o:p></span></p><p class=3DMsoNormal style=3D'margin-left:.75in;text-indent=
:-.25in;mso-list:l1 level2 lfo2;vertical-align:middle'><![if !supportLists]=
><span style=3D'font-size:10.0pt;font-family:"Courier New"'><span style=3D'=
mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;=
&nbsp; </span></span></span><![endif]>Should close the CLUE channel.&nbsp; =
Can keep SCTP open if it is used for other things.<span style=3D'font-size:=
12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p clas=
s=3DMsoNormal style=3D'margin-left:27.0pt;text-indent:-.25in;mso-list:l0 le=
vel1 lfo3;vertical-align:middle'><![if !supportLists]><span style=3D'font-s=
ize:10.0pt;font-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<spa=
n style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; </span></span></span><![endif]>When making an SDP offer, if =
the offerer wants to enable CLUE then SDP should indicate this.&nbsp; Even =
if previous O/A exchanges have not enabled CLUE.&nbsp; This is consistent w=
ith an offerer always including video if it wants to add video to an audio =
call.<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'=
><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:27.0pt;tex=
t-indent:-.25in;mso-list:l3 level1 lfo4;vertical-align:middle'><![if !suppo=
rtLists]><span style=3D'font-size:10.0pt;font-family:Symbol'><span style=3D=
'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Roman"'>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]=
>Security issues<span style=3D'font-size:12.0pt;font-family:"Times New Roma=
n","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left=
:.75in;text-indent:-.25in;mso-list:l3 level2 lfo4;vertical-align:middle'><!=
[if !supportLists]><span style=3D'font-size:10.0pt;font-family:"Courier New=
"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New Ro=
man"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Mary made suggestio=
ns<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o=
:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:.75in;text-in=
dent:-.25in;mso-list:l3 level2 lfo4;vertical-align:middle'><![if !supportLi=
sts]><span style=3D'font-size:10.0pt;font-family:"Courier New"'><span style=
=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&n=
bsp;&nbsp; </span></span></span><![endif]>This doc shouldn't have a heavy s=
ecurity section.&nbsp; Using existing protocols.<span style=3D'font-size:12=
.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=
=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l3 leve=
l2 lfo4;vertical-align:middle'><![if !supportLists]><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span></s=
pan><![endif]>Jonathan suggested mention case of SDP and SCTP going to diff=
erent addresses, one is attacker one is victim?<span style=3D'font-size:12.=
0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=
=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l3 leve=
l2 lfo4;vertical-align:middle'><![if !supportLists]><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span></s=
pan><![endif]>Mary plans to get a security review done during WGLC<span sty=
le=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></=
span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FECRPMBOXPRD08p_--


From nobody Tue Sep 16 07:24:50 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56F8C1A0709 for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 07:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOuX2kWfWB32 for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 07:24:47 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id E67F01A0350 for <clue@ietf.org>; Tue, 16 Sep 2014 07:24:46 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta02.westchester.pa.mail.comcast.net with comcast id rqP81o0030vyq2s51qQmC3; Tue, 16 Sep 2014 14:24:46 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta05.westchester.pa.mail.comcast.net with comcast id rqQm1o00F3Ge9ey3RqQmLp; Tue, 16 Sep 2014 14:24:46 +0000
Message-ID: <5418482D.1010603@alum.mit.edu>
Date: Tue, 16 Sep 2014 10:24:45 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com>
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1410877486; bh=kSn2SrMznDD0vJw3pEjV1UdakTrU0HO5xX9JofbSoOU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Idk/KDKL4kEH1Tw+91jk5j6ylNKjepznJ2GJa8WAAQiKNw2ec8kaB6owq7fmE+vDH rKexXok2s7FYUBOScv89p1FfrWsa4kwooYK/xqZ8PavHy8Ft8ecdCr87kncd+yx6VB d0CaSFHZi4goN+z3OmQSFN0UwqMMvD3Pvmrskk+JgP9keb/QESWDssPr8G/jWXIhsm F6bo8GWWr6mvs2SZaiFQJOhdLCHEgJfmW7d2pWWDM+vL15NbLxdo39MzBTNygZIDEA eoIYQGeqmssOjN4jLe7dIZulLNW3ikXDJH/nTzRDogvjeob9Uq3hzOr/56bbgtqhvO zHiLrnTl4yETA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/WjN1rqqWXYTlmMILC5HD9vpZLFA
Subject: Re: [clue] Notes from design team meeting re: signaling open issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 14:24:48 -0000

Thanks Mark.

In addition, There was discussion of defining a new state for when the 
clue channel itself has been established. One term suggested was "CLUE 
Active". I think there was support for this. (Another suggestion was 
"CLUE Awesome", but I don't think it was serious.)

On 9/16/14 9:45 AM, Duckworth, Mark wrote:
> Here are my notes from the design team meeting.

[snip]

> oJonathan suggested mention case of SDP and SCTP going to different
> addresses, one is attacker one is victim?

He was referring specifically to
http://tools.ietf.org/html/rfc5245#section-18.5.1

	Thanks,
	Paul


From nobody Tue Sep 16 10:03:29 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B39971A8833 for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 10:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vl8TICtdB3HP for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 10:03:26 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9CFE1A8859 for <clue@ietf.org>; Tue, 16 Sep 2014 10:03:23 -0700 (PDT)
X-AuditID: c1b4fb3a-f79da6d0000008c7-0e-54186d59894c
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 52.E8.02247.95D68145; Tue, 16 Sep 2014 19:03:21 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0174.001; Tue, 16 Sep 2014 19:03:20 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] Draft new version: clue-data-channel-01
Thread-Index: Ac/Q6P1eNDrLxC9JTsiySht2hyqOBQAUZKOAACUlsyA=
Date: Tue, 16 Sep 2014 17:03:20 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com>
In-Reply-To: <54178E8F.8090809@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUyM+JvjW5krkSIwfYPmhZf3jeyWOw/dZnZ gcljyZKfTB4rzs9kCWCK4rJJSc3JLEst0rdL4Mq40sVfMEW4YtrCRsYGxoP8XYycHBICJhKP H3cyQdhiEhfurWfrYuTiEBI4yijx4v9NNpCEkMASRonJjwy7GDk42AQsJLr/aYOERQTCJTq2 XWEEsYUFrCVaDraygpSICNhILFqaCVFiJXGyfzU7iM0ioCrxfN1KsIm8Ar4Ss+ctZoWYni8x 7c50sBM4BXQkGq62gtmMQOd8P7UGzGYWEJe49WQ+1JkCEkv2nGeGsEUlXj7+xwphK0ksuv0Z ql5HYsHuT2wQtrbEsoWvmSH2CkqcnPmEZQKj6CwkY2chaZmFpGUWkpYFjCyrGEWLU4uLc9ON jPRSizKTi4vz8/TyUks2MQIj5OCW31Y7GA8+dzzEKMDBqMTDq8AlESLEmlhWXJl7iFGag0VJ nHfhuXnBQgLpiSWp2ampBalF8UWlOanFhxiZODilGhhbSwSln2WfVxX+X5sa1GpksHPm8czp s39eSbtbUW0bLty1d3bc9pNaz7oiRPZnRE8VN//WJPiHnW11zILpLG1zlfK3Br5r/3PjVr1Z VORMrnrO+wp2XvklfGmHfj9lsrWKmXlzxwaHy4XLXtU9XLjcavdPwZ3X3KZW+/UtyZn94uQH 5iSPRmslluKMREMt5qLiRACDnN7ucQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/yq-afmdYJskhj4-hX4TolVtCzZM
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 17:03:28 -0000

Hi Christian,

I am not sure I agree with what you are saying.

Sure, we can use the grouping to indicate that the SCTPoDTLS association wi=
ll be used within a CLUE session.

But, in order to open a data channel for CLUE, you need to use DCEP. Also, =
in order to close a data channel for CLUE, you need to reset the STCPoDTLS =
association. Just removing the m=3D line from the CLUE group won't do that =
- and I am not even sure we should allow that.

Also, if we use a mid attribute to associate the SCTPoDTLS association with=
 CLUE, can we then also use it for non-CLUE protocol? Does not seem semanti=
cally correct in my opinion.=20

Regards,

Christer

-----Original Message-----
From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian Groves
Sent: 16 September 2014 04:13
To: clue@ietf.org
Subject: Re: [clue] Draft new version: clue-data-channel-01

Hello Christer,

Just a question on 5.7 where it says "If an offerer wants to disable the CL=
UE Data Channel in an offer, it assigns a zero port value to the "m=3D"=20
line representing the SCTPoDTLS association used to realize the CLUE Data c=
hannel."

Wouldn't this have the effect of closing the SCTP/DTLS association causing =
CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to be =
for a generic webrtc data channel. To have a "CLUE data channel" we use the=
 a=3Dgroup.

i.e. Generic Data Channel
m=3Dapplication 54111 SCTP/DTLS 54111
a=3Dsctpmap:54111 webrtc-datachannel

CLUE data channel
a=3Dgroup:CLUE 100
m=3Dapplication 54111 SCTP/DTLS 54111
a=3Dsctpmap:54111 webrtc-datachannel
a=3Dmid:100

Therefore if an endpoint wanted to remove CLUE from the data channel (witho=
ut closing the SCTP/DTLS associated) it would remove the a=3Dgroup and a=3D=
mid.

There's also a typo in clause 5.7 "are unchanged" is repeated.

Regards, Christian

On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>
> Hi,
>
> I've submitted a new version of the CLUE data channel draft.
>
> The changes are mostly editorial: I structured the O/A procedures=20
> according to 3264, and updated the references.
>
> Regards,
>
> Christer
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue

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


From nobody Tue Sep 16 10:34:26 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD6AA1A7011 for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 10:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level: 
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vay5nT6-HcfC for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 10:34:19 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id A86201A8702 for <clue@ietf.org>; Tue, 16 Sep 2014 10:34:14 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta05.westchester.pa.mail.comcast.net with comcast id rscX1o00317dt5G55taEKu; Tue, 16 Sep 2014 17:34:14 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta13.westchester.pa.mail.comcast.net with comcast id rtaD1o00b3Ge9ey3ZtaE8o; Tue, 16 Sep 2014 17:34:14 +0000
Message-ID: <54187495.5080501@alum.mit.edu>
Date: Tue, 16 Sep 2014 13:34:13 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1410888854; bh=tjP/J0v+UDV4Ta2z8yYQtU0QEOO8nRutLUqhe9kctgU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=hmtn94E0Yi+EEpaOdWKpCvs/dSfBYa6u9MsWam5rrPHaG4kJ2gR+mZhfUM3h6srmB PmEsqJQ48cBFY3+bxogts9Qpzs5vO/2Qp0uubOU/6QtHYNCp19iK+VGb1Eud9eBFZH QJB8FL4VumJNMxUlVEK+dD/t6TDwDwW3qw5ZLoz3WuxGlJZZuA1E2ZNHo2pev7FU6C 3PZGNNDjeqtR1WZPPsuMoDuF20n12ZsMCSbYjfkNSW7lD15awwOVSMBX8e2vPNqVPT rNs3VLAxeUHcFttnlculrF3Gynpxo0sIrYArvineJGGI/sTHPj3oEk0LYs7yKKhAHX rRHJoVSisfRIQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/hASe2IkHhK1KCNk1-YiEwGgV6kU
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 17:34:20 -0000

Christer,

We had a design team call today and discussed fallback.

Bottom line (my interpretation from the discussion):

If you negotiate the sctp association *and* include it in the clue 
group, you are saying that you *intend* to enable clue. Of course you 
still have to use DCEP to open the clue channel, but it is expected that 
you will do that.

If you want to fallback, and you still want to retain the sctp 
association for other purposes, then you need to:
- close the clue data channel (sctp stream)
- use O/A to remove the sctp association from the clue group

If you want to fallback, and you don't want to retain the sctp 
association, then you can:
- use O/A to remove the sctp association (port 0)
- terminate the actual sctp association
- (I think you can do the above in either order)
- it would be nice if you closed the clue data channel first,
   but probably not necessary to do so.

If the sctp association is closed for some reason, and you want to 
remain clue enabled, then you should:
- send another offer including the sctp m-line in the clue group
- start things up again
- (I think you don't try to reestablish the association until
   the new offer is sent.)

	Thanks,
	Paul

On 9/16/14 1:03 PM, Christer Holmberg wrote:
> Hi Christian,
>
> I am not sure I agree with what you are saying.
>
> Sure, we can use the grouping to indicate that the SCTPoDTLS association will be used within a CLUE session.
>
> But, in order to open a data channel for CLUE, you need to use DCEP. Also, in order to close a data channel for CLUE, you need to reset the STCPoDTLS association. Just removing the m= line from the CLUE group won't do that - and I am not even sure we should allow that.
>
> Also, if we use a mid attribute to associate the SCTPoDTLS association with CLUE, can we then also use it for non-CLUE protocol? Does not seem semantically correct in my opinion.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian Groves
> Sent: 16 September 2014 04:13
> To: clue@ietf.org
> Subject: Re: [clue] Draft new version: clue-data-channel-01
>
> Hello Christer,
>
> Just a question on 5.7 where it says "If an offerer wants to disable the CLUE Data Channel in an offer, it assigns a zero port value to the "m="
> line representing the SCTPoDTLS association used to realize the CLUE Data channel."
>
> Wouldn't this have the effect of closing the SCTP/DTLS association causing CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to be for a generic webrtc data channel. To have a "CLUE data channel" we use the a=group.
>
> i.e. Generic Data Channel
> m=application 54111 SCTP/DTLS 54111
> a=sctpmap:54111 webrtc-datachannel
>
> CLUE data channel
> a=group:CLUE 100
> m=application 54111 SCTP/DTLS 54111
> a=sctpmap:54111 webrtc-datachannel
> a=mid:100
>
> Therefore if an endpoint wanted to remove CLUE from the data channel (without closing the SCTP/DTLS associated) it would remove the a=group and a=mid.
>
> There's also a typo in clause 5.7 "are unchanged" is repeated.
>
> Regards, Christian
>
> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>
>> Hi,
>>
>> I've submitted a new version of the CLUE data channel draft.
>>
>> The changes are mostly editorial: I structured the O/A procedures
>> according to 3264, and updated the references.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Tue Sep 16 18:12:57 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 544E71A008B for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 18:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmzMFNj8RcK8 for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 18:12:54 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94DEA1A005C for <clue@ietf.org>; Tue, 16 Sep 2014 18:12:54 -0700 (PDT)
Received: from ppp118-209-111-109.lns20.mel4.internode.on.net ([118.209.111.109]:50849 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XU3lr-00008y-DT; Wed, 17 Sep 2014 11:10:59 +1000
Message-ID: <5418E00E.4060207@nteczone.com>
Date: Wed, 17 Sep 2014 11:12:46 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "clue@ietf.org" <clue@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/f-Y3qKLK9zxe2wqDFce3Otqlcl4
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 01:12:56 -0000

Hello Christer,

I think Paul has covered the issue with regards to fall back. We have to 
distinguish between the overall data channel and the resultant streams 
being used for CLUE. DCEP doesn't open the overall SCTP/DTLS association 
it establishes a protocol on a certain stream/s. Closure is done by 
resetting the stream (see clause 6.7/draft-ietf-rtcweb-data-channel-11) 
not by resetting the whole SCTP/DTLS association.

With regards to the SCTP/DTLS association my understanding of the WebRTC 
datachannel is that you can use several application protocols within 
that association, i.e. CLUE and say BFCP. I think think we can say that 
an SCTP/DTLS association must only contain CLUE. I think its valid to 
use an mid in multiple groups. RFC5888 clause 6 says "An "m" line 
identified by its "mid" attribute MAY appear in more than one "a=group" 
line."

Regards, Christian

On 17/09/2014 3:03 AM, Christer Holmberg wrote:
> Hi Christian,
>
> I am not sure I agree with what you are saying.
>
> Sure, we can use the grouping to indicate that the SCTPoDTLS association will be used within a CLUE session.
>
> But, in order to open a data channel for CLUE, you need to use DCEP. Also, in order to close a data channel for CLUE, you need to reset the STCPoDTLS association. Just removing the m= line from the CLUE group won't do that - and I am not even sure we should allow that.
>
> Also, if we use a mid attribute to associate the SCTPoDTLS association with CLUE, can we then also use it for non-CLUE protocol? Does not seem semantically correct in my opinion.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian Groves
> Sent: 16 September 2014 04:13
> To: clue@ietf.org
> Subject: Re: [clue] Draft new version: clue-data-channel-01
>
> Hello Christer,
>
> Just a question on 5.7 where it says "If an offerer wants to disable the CLUE Data Channel in an offer, it assigns a zero port value to the "m="
> line representing the SCTPoDTLS association used to realize the CLUE Data channel."
>
> Wouldn't this have the effect of closing the SCTP/DTLS association causing CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to be for a generic webrtc data channel. To have a "CLUE data channel" we use the a=group.
>
> i.e. Generic Data Channel
> m=application 54111 SCTP/DTLS 54111
> a=sctpmap:54111 webrtc-datachannel
>
> CLUE data channel
> a=group:CLUE 100
> m=application 54111 SCTP/DTLS 54111
> a=sctpmap:54111 webrtc-datachannel
> a=mid:100
>
> Therefore if an endpoint wanted to remove CLUE from the data channel (without closing the SCTP/DTLS associated) it would remove the a=group and a=mid.
>
> There's also a typo in clause 5.7 "are unchanged" is repeated.
>
> Regards, Christian
>
> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>> Hi,
>>
>> I've submitted a new version of the CLUE data channel draft.
>>
>> The changes are mostly editorial: I structured the O/A procedures
>> according to 3264, and updated the references.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Tue Sep 16 18:38:29 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB64A1A01EF for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 18:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXgX4DQ9emkh for <clue@ietfa.amsl.com>; Tue, 16 Sep 2014 18:38:01 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83DC51A0175 for <clue@ietf.org>; Tue, 16 Sep 2014 18:38:01 -0700 (PDT)
Received: from ppp118-209-111-109.lns20.mel4.internode.on.net ([118.209.111.109]:51110 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XU4AD-0004q7-7d for clue@ietf.org; Wed, 17 Sep 2014 11:36:09 +1000
Message-ID: <5418E5F4.7040204@nteczone.com>
Date: Wed, 17 Sep 2014 11:37:56 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com>
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/fDef9sWar6Tpr9N8pNznaDN_qmY
Subject: Re: [clue] Notes from design team meeting re: signaling open issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 01:38:03 -0000

I just want to make sure I understand what was being proposed for 
fallback of CLUE media streams. I'm going to try to avoid the use of 
"CLUE enabled" and "CLUE capable" and focus on the SDP and what it means.

Consider the following SDP where a CLUE controlled video stream has been 
configured, established and everything is awesome :-).

       a=group:CLUE 1 2
       m=application 6100 SCTP/DTLS 6100
       a=sctpmap:1 webrtc-datachannel
       a=mid:1
       ...
       m=video 6004 RTP/AVP 96
       a=rtpmap:96 H264/90000
       a=fmtp:96 profile-level-id=42e016
       a=sendonly
       a=mid:2
       a=label:enc1

Case 1) The SDP is updated to remove mid:2 effectively removing the 
video stream from CLUE control. However a=sendonly remains, i.e.
       a=group:CLUE 1
       m=application 6100 SCTP/DTLS 6100
       a=sctpmap:1 webrtc-datachannel
       a=mid:1
       ...
       m=video 6004 RTP/AVP 96
       a=rtpmap:96 H264/90000
       a=fmtp:96 profile-level-id=42e016
       a=sendonly

My assumption is that video continues to flow because the media stream 
is no longer under CLUE control (thus rules regarding configuring don't 
apply) and the sending direction is still send only. However as its not 
part of a CLUE group anymore any previously Advertised CLUEinfo 
regarding the video stream is no longer valid.

Case 2) The SDP is updated to remove mid:2 effectively removing the 
video stream from CLUE control the endpoint wants to stop the stream. My 
assumption is that to stop sending the video media stream either the 
port has to be changed to zero or a=inactive is set. Any CLUE info 
regarding the stream is discarded.

Case 3) The SDP is updated to remove mid:1 effectively closing the CLUE 
channel. However the video stream remain in the CLUE group, e.g.
       a=group:CLUE 2
       m=application 6100 SCTP/DTLS 6100
       a=sctpmap:1 webrtc-datachannel
       ...
       m=video 6004 RTP/AVP 96
       a=rtpmap:96 H264/90000
       a=fmtp:96 profile-level-id=42e016
       a=sendonly
       a=mid:2
       a=label:enc1
My assumption is that the video stream continues unchanged and as its 
still in a CLUE group any advertised CLUEinfo is still valid for the stream.

Case 4) To remove the CLUE protocol and media channels the CLUE group 
should be removed and the media line zeroed/made inactive, e.g.
       m=application 6100 SCTP/DTLS 6100
       a=sctpmap:1 webrtc-datachannel
       ...
       m=video 0 RTP/AVP 96

Rob is that what you were proposing?

Regards, Christian

On 16/09/2014 11:45 PM, Duckworth, Mark wrote:
>
> Here are my notes from the design team meeting.
>
> CLUE signaling design team meeting
>
> Sep 16, 2014
>
> Rob Hansen, Mary Barnes, Paul Kyzivat, Mark Duckworth, Christian 
> Groves, Roberta Presta, Roni Even, Jonathan Lennox
>
> Rob discussed issues
>
> ·Fallback to non-CLUE - when does it happen?
>
> osignalling document has a proposal that defines when this happens, 
> but there are other ideas
>
> oRob's idea (in the signaling doc) is to use the same criteria to 
> enable CLUE as to disable it
>
> oIf data channel connection is lost, probably don't want that to mean 
> the call is not CLUE enabled any more
>
> oThe group agrees with Rob's proposal
>
> ·Fallback to non-CLUE - what does it mean?
>
> oWhen fallback to non CLUE-enabled occurs, then CLUE-controlled media 
> stops.
>
> osome other details about handling data channel and CLUE protocol 
> should be defined
>
> oShould close the CLUE channel.  Can keep SCTP open if it is used for 
> other things.
>
> ·When making an SDP offer, if the offerer wants to enable CLUE then 
> SDP should indicate this.  Even if previous O/A exchanges have not 
> enabled CLUE.  This is consistent with an offerer always including 
> video if it wants to add video to an audio call.
>
> ·Security issues
>
> oMary made suggestions
>
> oThis doc shouldn't have a heavy security section.  Using existing 
> protocols.
>
> oJonathan suggested mention case of SDP and SCTP going to different 
> addresses, one is attacker one is victim?
>
> oMary plans to get a security review done during WGLC
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Wed Sep 17 00:11:24 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED0981A6FC0 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 00:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level: 
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lShee1Y41jwP for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 00:11:17 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 338DD1A6FBC for <clue@ietf.org>; Wed, 17 Sep 2014 00:11:17 -0700 (PDT)
X-AuditID: c1b4fb25-f791c6d00000617b-33-54193413a630
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E6.20.24955.31439145; Wed, 17 Sep 2014 09:11:15 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0174.001; Wed, 17 Sep 2014 09:11:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] Draft new version: clue-data-channel-01
Thread-Index: Ac/Q6P1eNDrLxC9JTsiySht2hyqOBQAUZKOAACUlsyD//+kIgP/+/Ujw
Date: Wed, 17 Sep 2014 07:11:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D44E68B@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <54187495.5080501@alum.mit.edu>
In-Reply-To: <54187495.5080501@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUyM+Jvja6wiWSIwb8WKYv9py4zW6zYcIDV gcnj7/sPTB5LlvxkCmCK4rJJSc3JLEst0rdL4Mq4dLa+4IZaxdyHL5gbGN/LdTFycEgImEgc n5DSxcgJZIpJXLi3nq2LkYtDSOAoo8TO/TfYIZwljBKrup6xgTSwCVhIdP/TBmkQEfCU2PFx CjOILSxgLdFysJUVpEREwEZi0dJMiBI3iS27brCA2CwCqhJ3Lj0Bm8Ir4Csxfb8qxPSrjBKv DzwFq+EU0JHY9202K4jNCHTP91NrmEBsZgFxiVtP5jNB3CkgsWTPeWYIW1Ti5eN/rBC2osTH V/sYIep1JBbs/sQGYWtLLFv4GqyeV0BQ4uTMJywTGEVnIRk7C0nLLCQts5C0LGBkWcUoWpxa nJSbbmSsl1qUmVxcnJ+nl5dasokRGCEHt/xW3cF4+Y3jIUYBDkYlHl6F1xIhQqyJZcWVuYcY pTlYlMR5F56bFywkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBkfPA5uaL0nX3V7bfDH154Bvn fM+lk3ZuPvi/jmPtV6/YKzO9v1ltmbBjZfD3uLp3JWz2nk6aq76zx0v0imzbKclv77Qw6sFl l82R0n2fTlb8LN7wu0vrirhb5l2H0h6muwbXbdv6Vk/Mu7fmREQYOyfLzHMnu4RftnlOPb/T 0XDr3QMBC6/+N1NiKc5INNRiLipOBAATvzRycQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/QAb3UwncKWK9uAQ8p1SgFO4BkeY
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 07:11:23 -0000

Hi Paul,

>We had a design team call today and discussed fallback.

I know. Unfortunately I wasn't able to attend, due to some personal issues =
 :(

>Bottom line (my interpretation from the discussion):
>
>If you negotiate the sctp association *and* include it in the clue group, =
you are saying that you *intend* to enable clue. Of course you still have t=
o use DCEP to open the clue channel, but it is expected that you will do th=
at.

Correct.

>If you want to fallback, and you still want to retain the sctp association=
 for other purposes, then you need to:
>- close the clue data channel (sctp stream)
>- use O/A to remove the sctp association from the clue group

Correct.

I do think we need to have some text on what happens if one removes the sct=
p association from the clue group - WITHOUT closing the clue data channel f=
irst. In my opinion it is an error case, but I think we should say that one=
 MUST NOT send CLUE messages on such stream, and MUST discard any CLUE mess=
age received on such stream.

>If you want to fallback, and you don't want to retain the sctp association=
, then you can:
>- use O/A to remove the sctp association (port 0)
>- terminate the actual sctp association
>- (I think you can do the above in either order)
>- it would be nice if you closed the clue data channel first,
>   but probably not necessary to do so.

Correct.

But, one of my question (which is not specific to fallback) was: if we asso=
ciate the SCTP association with the CLUE group, would it be semantically co=
rrect to also use the SCTP association for non-CLUE purpose (technically th=
ere is no problem)?


>If the sctp association is closed for some reason, and you want to remain =
clue enabled, then you should:
>- send another offer including the sctp m-line in the clue group
>- start things up again
>- (I think you don't try to reestablish the association until
   the new offer is sent.)

Regarding the last point, I guess that should be covered in the sctp-sdp dr=
aft.

Regards,

Christer




On 9/16/14 1:03 PM, Christer Holmberg wrote:
> Hi Christian,
>
> I am not sure I agree with what you are saying.
>
> Sure, we can use the grouping to indicate that the SCTPoDTLS association =
will be used within a CLUE session.
>
> But, in order to open a data channel for CLUE, you need to use DCEP. Also=
, in order to close a data channel for CLUE, you need to reset the STCPoDTL=
S association. Just removing the m=3D line from the CLUE group won't do tha=
t - and I am not even sure we should allow that.
>
> Also, if we use a mid attribute to associate the SCTPoDTLS association wi=
th CLUE, can we then also use it for non-CLUE protocol? Does not seem seman=
tically correct in my opinion.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian=20
> Groves
> Sent: 16 September 2014 04:13
> To: clue@ietf.org
> Subject: Re: [clue] Draft new version: clue-data-channel-01
>
> Hello Christer,
>
> Just a question on 5.7 where it says "If an offerer wants to disable the =
CLUE Data Channel in an offer, it assigns a zero port value to the "m=3D"
> line representing the SCTPoDTLS association used to realize the CLUE Data=
 channel."
>
> Wouldn't this have the effect of closing the SCTP/DTLS association causin=
g CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to b=
e for a generic webrtc data channel. To have a "CLUE data channel" we use t=
he a=3Dgroup.
>
> i.e. Generic Data Channel
> m=3Dapplication 54111 SCTP/DTLS 54111
> a=3Dsctpmap:54111 webrtc-datachannel
>
> CLUE data channel
> a=3Dgroup:CLUE 100
> m=3Dapplication 54111 SCTP/DTLS 54111
> a=3Dsctpmap:54111 webrtc-datachannel
> a=3Dmid:100
>
> Therefore if an endpoint wanted to remove CLUE from the data channel (wit=
hout closing the SCTP/DTLS associated) it would remove the a=3Dgroup and a=
=3Dmid.
>
> There's also a typo in clause 5.7 "are unchanged" is repeated.
>
> Regards, Christian
>
> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>
>> Hi,
>>
>> I've submitted a new version of the CLUE data channel draft.
>>
>> The changes are mostly editorial: I structured the O/A procedures=20
>> according to 3264, and updated the references.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>

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


From nobody Wed Sep 17 00:16:49 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECC7C1A0336 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 00:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level: 
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wR2dY_aBmDI for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 00:16:46 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1EB71A0312 for <clue@ietf.org>; Wed, 17 Sep 2014 00:16:45 -0700 (PDT)
X-AuditID: c1b4fb2d-f793d6d000005356-05-5419355bc210
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id B8.15.21334.B5539145; Wed, 17 Sep 2014 09:16:44 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0174.001; Wed, 17 Sep 2014 09:16:43 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] Draft new version: clue-data-channel-01
Thread-Index: Ac/Q6P1eNDrLxC9JTsiySht2hyqOBQAUZKOAACUlsyAADSTBAAAQuB8A
Date: Wed, 17 Sep 2014 07:16:42 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D44E6BC@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <5418E00E.4060207@nteczone.com>
In-Reply-To: <5418E00E.4060207@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrLLMWRmVeSWpSXmKPExsUyM+JvjW6MqWSIwZ1+dosv7xtZLPafuszs wOSxZMlPJo8V52eyBDBFcdmkpOZklqUW6dslcGXMWe9a8E6u4sqL7ywNjA8kuhg5OSQETCTm bL3HAmGLSVy4t54NxBYSOMooMaWZtYuRC8hewihxaeIb9i5GDg42AQuJ7n/aIDUiAuESHduu MILYwgLWEi0HW1lBSkQEbCQWLc2EKHGTWP78Ilgni4CqxOe2KJAwr4CvxOUd06GmX2WU+Pbl FyNIDaeAjsTvackgNYxA13w/tYYJxGYWEJe49WQ+E8SVAhJL9pxnhrBFJV4+/scKYStKfHy1 jxGiXkdiwe5PbBC2tsSyha+ZIfYKSpyc+YRlAqPoLCRjZyFpmYWkZRaSlgWMLKsYRYtTi4tz 042M9VKLMpOLi/Pz9PJSSzYxAuPj4JbfujsYV792PMQowMGoxMOr8FoiRIg1say4MvcQozQH i5I476Jz84KFBNITS1KzU1MLUovii0pzUosPMTJxcEo1MC7k8J4z587lyQUc7brn1n5TFJ+h l9l88H1RdGee/JRmbRdD2fslmU82rGE76B5UVBX9unHul1OsZi0RGxOCstj/f53NdSr4xfaj vZc9A39zykezqHpnWn0RPpER3/mg0Ihb2Gb9jdZ9d9wvdUrm/DdnPai5wW31QyOdsGSphbu4 5PiYjs+wUWIpzkg01GIuKk4EAEt6cT9wAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/QGR67tsCyrGznFSv32NF7tmEZqg
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 07:16:48 -0000

Hi,

>I think Paul has covered the issue with regards to fall back. We have to d=
istinguish between the overall data channel and the resultant streams being=
 used for CLUE. DCEP doesn't open the overall SCTP/DTLS association it esta=
blishes a protocol on a certain stream/s. Closure is done by >resetting the=
 stream (see clause 6.7/draft-ietf-rtcweb-data-channel-11) not by resetting=
 the whole SCTP/DTLS association.

I agree.=20

I guess my concern was triggered by the fact that the design team minutes d=
id not mention the resetting of the stream - only the removal of the sctp a=
ssociation from the CLUE group.

>With regards to the SCTP/DTLS association my understanding of the WebRTC d=
atachannel is that you can use several application protocols within that as=
sociation, i.e. CLUE and say BFCP. I think think we can say that an SCTP/DT=
LS association must only contain CLUE.

I agree, and the clue data channel draft currently says that.

> I think its valid to use an mid in multiple groups. RFC5888 clause 6 says=
 "An "m" line identified by its "mid" attribute MAY appear in more than one=
 "a=3Dgroup"  line."

That is also true, but other users of the sctp association may not have any=
 groups associated... Again, it is not a technical problem, but more semant=
ical.

Regards,

Christer


On 17/09/2014 3:03 AM, Christer Holmberg wrote:
> Hi Christian,
>
> I am not sure I agree with what you are saying.
>
> Sure, we can use the grouping to indicate that the SCTPoDTLS association =
will be used within a CLUE session.
>
> But, in order to open a data channel for CLUE, you need to use DCEP. Also=
, in order to close a data channel for CLUE, you need to reset the STCPoDTL=
S association. Just removing the m=3D line from the CLUE group won't do tha=
t - and I am not even sure we should allow that.
>
> Also, if we use a mid attribute to associate the SCTPoDTLS association wi=
th CLUE, can we then also use it for non-CLUE protocol? Does not seem seman=
tically correct in my opinion.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian=20
> Groves
> Sent: 16 September 2014 04:13
> To: clue@ietf.org
> Subject: Re: [clue] Draft new version: clue-data-channel-01
>
> Hello Christer,
>
> Just a question on 5.7 where it says "If an offerer wants to disable the =
CLUE Data Channel in an offer, it assigns a zero port value to the "m=3D"
> line representing the SCTPoDTLS association used to realize the CLUE Data=
 channel."
>
> Wouldn't this have the effect of closing the SCTP/DTLS association causin=
g CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to b=
e for a generic webrtc data channel. To have a "CLUE data channel" we use t=
he a=3Dgroup.
>
> i.e. Generic Data Channel
> m=3Dapplication 54111 SCTP/DTLS 54111
> a=3Dsctpmap:54111 webrtc-datachannel
>
> CLUE data channel
> a=3Dgroup:CLUE 100
> m=3Dapplication 54111 SCTP/DTLS 54111
> a=3Dsctpmap:54111 webrtc-datachannel
> a=3Dmid:100
>
> Therefore if an endpoint wanted to remove CLUE from the data channel (wit=
hout closing the SCTP/DTLS associated) it would remove the a=3Dgroup and a=
=3Dmid.
>
> There's also a typo in clause 5.7 "are unchanged" is repeated.
>
> Regards, Christian
>
> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>> Hi,
>>
>> I've submitted a new version of the CLUE data channel draft.
>>
>> The changes are mostly editorial: I structured the O/A procedures=20
>> according to 3264, and updated the references.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Wed Sep 17 02:07:50 2014
Return-Path: <rohanse2@cisco.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AAFF1A0031 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 02:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.353
X-Spam-Level: 
X-Spam-Status: No, score=-14.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HUEcBGDdPdd1 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 02:07:45 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E75951A0052 for <clue@ietf.org>; Wed, 17 Sep 2014 02:07:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5061; q=dns/txt; s=iport; t=1410944865; x=1412154465; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=9HbOskp4iVYJuS284aJdLt90hIswdWU51xS3ezgobVA=; b=J2xABDrlXiLmuc/bg+YmhKl8Fc1AngcpGnchcoJB0mfk5EKCpviYSnOv NbyEBF8hvuDnieDJsYUXJIfc4eWzRIr9lber/MsGi7dTK+pI8MB1iWIEe 192RS2oS51T5YBlBRiifQRNtlYUnAP2U4u6kJ/p1duG8GvxIAWwhMKYuM Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgKABROGVStJssW/2dsb2JhbABgg2BXtGIFAW+TQAqHTgGBLwF5hAQBAQQBAQEvAQU2ChELGAkWDwkDAgECARUwEwYCAQGIOg29YQETBIV8iVaESwEEnQqHSI1+g188L4JKAQEB
X-IronPort-AV: E=Sophos;i="5.04,539,1406592000"; d="scan'208";a="176290221"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 17 Sep 2014 09:07:43 +0000
Received: from [10.47.200.91] ([10.47.200.91]) (authenticated bits=0) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s8H97got030051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <clue@ietf.org>; Wed, 17 Sep 2014 09:07:43 GMT
Message-ID: <54194F5E.3020205@cisco.com>
Date: Wed, 17 Sep 2014 10:07:42 +0100
From: Robert Hansen <rohanse2@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com> <5418E5F4.7040204@nteczone.com>
In-Reply-To: <5418E5F4.7040204@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: rohanse2
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/BuCNYNJuKsb4kpeN6n-MWXViQsA
Subject: Re: [clue] Notes from design team meeting re: signaling open issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 09:07:48 -0000

1) Yes
2) Yes
3) No. At present, the proposal is that by removing the SCTP association 
from the CLUE group the call is no longer CLUE-enabled. However, because 
the CLUE group is still present and still contains the video that video 
is still CLUE-controlled and hence can't be sent under these conditions.
4) Yes

Rob

On 17/09/14 02:37, Christian Groves wrote:
>
> I just want to make sure I understand what was being proposed for 
> fallback of CLUE media streams. I'm going to try to avoid the use of 
> "CLUE enabled" and "CLUE capable" and focus on the SDP and what it means.
>
> Consider the following SDP where a CLUE controlled video stream has 
> been configured, established and everything is awesome :-).
>
>       a=group:CLUE 1 2
>       m=application 6100 SCTP/DTLS 6100
>       a=sctpmap:1 webrtc-datachannel
>       a=mid:1
>       ...
>       m=video 6004 RTP/AVP 96
>       a=rtpmap:96 H264/90000
>       a=fmtp:96 profile-level-id=42e016
>       a=sendonly
>       a=mid:2
>       a=label:enc1
>
> Case 1) The SDP is updated to remove mid:2 effectively removing the 
> video stream from CLUE control. However a=sendonly remains, i.e.
>       a=group:CLUE 1
>       m=application 6100 SCTP/DTLS 6100
>       a=sctpmap:1 webrtc-datachannel
>       a=mid:1
>       ...
>       m=video 6004 RTP/AVP 96
>       a=rtpmap:96 H264/90000
>       a=fmtp:96 profile-level-id=42e016
>       a=sendonly
>
> My assumption is that video continues to flow because the media stream 
> is no longer under CLUE control (thus rules regarding configuring 
> don't apply) and the sending direction is still send only. However as 
> its not part of a CLUE group anymore any previously Advertised 
> CLUEinfo regarding the video stream is no longer valid.
>
> Case 2) The SDP is updated to remove mid:2 effectively removing the 
> video stream from CLUE control the endpoint wants to stop the stream. 
> My assumption is that to stop sending the video media stream either 
> the port has to be changed to zero or a=inactive is set. Any CLUE info 
> regarding the stream is discarded.
>
> Case 3) The SDP is updated to remove mid:1 effectively closing the 
> CLUE channel. However the video stream remain in the CLUE group, e.g.
>       a=group:CLUE 2
>       m=application 6100 SCTP/DTLS 6100
>       a=sctpmap:1 webrtc-datachannel
>       ...
>       m=video 6004 RTP/AVP 96
>       a=rtpmap:96 H264/90000
>       a=fmtp:96 profile-level-id=42e016
>       a=sendonly
>       a=mid:2
>       a=label:enc1
> My assumption is that the video stream continues unchanged and as its 
> still in a CLUE group any advertised CLUEinfo is still valid for the 
> stream.
>
> Case 4) To remove the CLUE protocol and media channels the CLUE group 
> should be removed and the media line zeroed/made inactive, e.g.
>       m=application 6100 SCTP/DTLS 6100
>       a=sctpmap:1 webrtc-datachannel
>       ...
>       m=video 0 RTP/AVP 96
>
> Rob is that what you were proposing?
>
> Regards, Christian
>
> On 16/09/2014 11:45 PM, Duckworth, Mark wrote:
>>
>> Here are my notes from the design team meeting.
>>
>> CLUE signaling design team meeting
>>
>> Sep 16, 2014
>>
>> Rob Hansen, Mary Barnes, Paul Kyzivat, Mark Duckworth, Christian 
>> Groves, Roberta Presta, Roni Even, Jonathan Lennox
>>
>> Rob discussed issues
>>
>> ·Fallback to non-CLUE - when does it happen?
>>
>> osignalling document has a proposal that defines when this happens, 
>> but there are other ideas
>>
>> oRob's idea (in the signaling doc) is to use the same criteria to 
>> enable CLUE as to disable it
>>
>> oIf data channel connection is lost, probably don't want that to mean 
>> the call is not CLUE enabled any more
>>
>> oThe group agrees with Rob's proposal
>>
>> ·Fallback to non-CLUE - what does it mean?
>>
>> oWhen fallback to non CLUE-enabled occurs, then CLUE-controlled media 
>> stops.
>>
>> osome other details about handling data channel and CLUE protocol 
>> should be defined
>>
>> oShould close the CLUE channel.  Can keep SCTP open if it is used for 
>> other things.
>>
>> ·When making an SDP offer, if the offerer wants to enable CLUE then 
>> SDP should indicate this.  Even if previous O/A exchanges have not 
>> enabled CLUE.  This is consistent with an offerer always including 
>> video if it wants to add video to an audio call.
>>
>> ·Security issues
>>
>> oMary made suggestions
>>
>> oThis doc shouldn't have a heavy security section.  Using existing 
>> protocols.
>>
>> oJonathan suggested mention case of SDP and SCTP going to different 
>> addresses, one is attacker one is victim?
>>
>> oMary plans to get a security review done during WGLC
>>
>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Wed Sep 17 04:19:14 2014
Return-Path: <scarlett.liuyan@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E71221A01D2 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 04:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.253
X-Spam-Level: 
X-Spam-Status: No, score=-5.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zcxymq2nSXPm for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 04:19:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D4DE1A015F for <clue@ietf.org>; Wed, 17 Sep 2014 04:19:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMS00047; Wed, 17 Sep 2014 11:19:09 +0000 (GMT)
Received: from SZXEMA404-HUB.china.huawei.com (10.82.72.36) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 17 Sep 2014 12:19:08 +0100
Received: from SZXEMA503-MBX.china.huawei.com ([169.254.5.43]) by SZXEMA404-HUB.china.huawei.com ([10.82.72.36]) with mapi id 14.03.0158.001; Wed, 17 Sep 2014 19:19:00 +0800
From: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
Thread-Index: AQHP0mkt7llefKfx50OLrad4L6ph4A==
Date: Wed, 17 Sep 2014 11:18:59 +0000
Message-ID: <E97C33E5D67C2843AFA535DE2E5B80C157402EDC@SZXEMA503-MBX.china.huawei.com>
References: <20140321141121.16330.32657.idtracker@ietfa.amsl.com> <E97C33E5D67C2843AFA535DE2E5B80C1573A7DA6@SZXEMA503-MBX.china.huawei.com> <7594FB04B1934943A5C02806D1A2204B1D2EFC38@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2EFC38@ESESSMB209.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.63.147.208]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/vrdZPfAhX1cKj1eF-NUt6WfYPIY
Cc: "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 11:19:13 -0000

Hi Christer,

	There is still a typo in the draft-ietf-clue-datachannel-01 and the typo w=
as confirmed by you in the previous e-mail below .=20
	Maybe you forgot it.
	By the way, the draft-ietf-mmusic-sctp-sdp-07 says below:

	4.1.1.  sctp-port

       sctp-port-attr   =3D  "a=3Dsctp-port=3D" portnumber
       port-number      =3D  port
	4.1.2.  max-message-size

    sctpmap-attr        =3D  "a=3Dfmtp:" association-usage [max-message-siz=
e]
    max-message-size    =3D  "max-message-size" EQUALS 1*DIGIT

	8.3.  SDP description for SCTP over DTLS Connection
	m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel
    a=3Dfmtp:webrtc-datachannel max-message-size=3D100000
    a=3Dsctp-port 5000

	At least ,I have a question.=20
	Do you think that your example in the draft-ietf-clue-datachannel-01 shoul=
d keep the consistency with the example of draft-ietf-mmusic-sctp-sdp-07 ?=
=20

Best Regards,
Scarlett

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Wednesday, May 07, 2014 6:00 PM
> To: Liuyan (Scarlett)
> Cc: clue@ietf.org
> Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt
>=20
> Hi Scarlett,
>=20
> Thanks for spotting the typo! :)
>=20
> Regards,
>=20
> Christer
>=20
> -----Original Message-----
> From: Liuyan (Scarlett) [mailto:scarlett.liuyan@huawei.com]
> Sent: 7. toukokuuta 2014 5:41
> To: Christer Holmberg
> Cc: clue@ietf.org
> Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt
>=20
> Hi Christer,
>=20
>     I notice that there is a typo in section 5.6 of
> draft-ietf-clue-datachannel-00 below:
>=20
>           5.6.  Example
>=20
>            m=3Dapplication 54111 SCTP/DTLS 54111
>            a=3Dsctpmap:54111 webrtc-datachannel
>=20
>           Figure 1: SDP Media Description for a CLUE Data Channel
>=20
>    As described in section 3 of draft-ietf-mmusic-sctp-sdp-06 below:
>=20
>    The 'SCTP/DTLS' protocol identifier indicates that the media
>    described will use the Datagram Transport Layer Security (DTLS)
>    [RFC4347] over SCTP as specified in [RFC6083].
>=20
>    The 'DTLS/SCTP' protocol identifier indicates that the media
>    described will use SCTP on top of the Datagram Transport Layer
>    Security (DTLS) protocol as specified in
>    [I-D.tuexen-tsvwg-sctp-dtls-encaps].  The actual layer below DTLS can
>    be plain UDP or what ICE agrees on (in the case ICE is used to
>    negotiate the actual transport flow).  The lower layer used is
>    identified from the elements present inside the m=3D line block.
>=20
>    so it should be reworded below:
>=20
>     5.6.  Example
>=20
>            m=3Dapplication 54111 DTLS/SCTP 54111
>            a=3Dsctpmap:54111 webrtc-datachannel
>=20
>           Figure 1: SDP Media Description for a CLUE Data Channel
>=20
> Best Regards,
> Scarlett
>=20
> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Friday, March 21, 2014 10:11 PM
> To: i-d-announce@ietf.org
> Cc: clue@ietf.org
> Subject: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the ControLling mUltiple streams for
> tElepresence Working Group of the IETF.
>=20
>         Title           : CLUE Protocol Data Channel
>         Author          : Christer Holmberg
> 	Filename        : draft-ietf-clue-datachannel-00.txt
> 	Pages           : 12
> 	Date            : 2014-03-20
>=20
> Abstract:
>    This document defines how to use the WebRTC Data Channel mechanism,
>    together with the Data Channel Establishment Protocol (DCEP) in order
>    to establish a data channel, referred to as CLUE Data Channel, for
>    transporting CLUE protocol messages between two CLUE entities.
>=20
>    The document defines the SCTP considerations specific to a CLUE Data
>    Channel, the SDP offer/answer procedures for negotiating the
>    establishment of, and the DCEP procedures for opening, a CLUE Data
>    Channel.
>=20
>    Details and procedures associated with the CLUE protocol are outside
>    the scope of this document.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-clue-datachannel-00
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Wed Sep 17 06:45:10 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6719C1A0310 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 06:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level: 
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2BJ1HXF6punf for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 06:45:04 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EBC41A0102 for <clue@ietf.org>; Wed, 17 Sep 2014 06:45:04 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by resqmta-ch2-04v.sys.comcast.net with comcast id sDVe1o0021uE5Es01Dl3Vy; Wed, 17 Sep 2014 13:45:03 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta16.westchester.pa.mail.comcast.net with comcast id sDku1o00h3Ge9ey3cDkyAq; Wed, 17 Sep 2014 13:45:01 +0000
Message-ID: <54199056.7050101@alum.mit.edu>
Date: Wed, 17 Sep 2014 09:44:54 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "clue@ietf.org" <clue@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <54187495.5080501@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D44E68B@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D44E68B@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1410961503; bh=eDf6VfppwnYK6KC1rD0HuLvI+IsPDGKTw6YqY/9Jw2Q=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=VTXqZ9M4PQ+/0CgrSSH9tfrVbOTODXwY11KqmGWbg7nzKrsYiF54bgu+PmX+G9AnN gUzudY4Y6+tJTHWdjzQvJmNCwPM5u+Ebar+uIg/Mu0xOOiVt/4r3PRb5Be5BenG5Le 6NpRFL5uwzMP6MnsK8gRkkW3UUu4J6alYJ7mvXjOEQ1wKcNeX8yNITtxOFJxDLxQAy 1a+mawNVRiJ+Pzbgut9erR7Af2Y2E+IT5SeD293BOSaZ7RAo2aE/+NyBWhtYZdLSlv lwdoNTDiQccaMIOlnKnu+b0MQVRSiQaoeUIXafiqtIbIcxaxuTFTMkhWTbcNBj8vap LLxSwHem+kvtA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/tFhZ6iII-i_IsAKgfFVhDhzozG0
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 13:45:06 -0000

On 9/17/14 3:11 AM, Christer Holmberg wrote:
> Hi Paul,
>
>> We had a design team call today and discussed fallback.
>
> I know. Unfortunately I wasn't able to attend, due to some personal issues  :(
>
>> Bottom line (my interpretation from the discussion):
>>
>> If you negotiate the sctp association *and* include it in the clue group, you are saying that you *intend* to enable clue. Of course you still have to use DCEP to open the clue channel, but it is expected that you will do that.
>
> Correct.
>
>> If you want to fallback, and you still want to retain the sctp association for other purposes, then you need to:
>> - close the clue data channel (sctp stream)
>> - use O/A to remove the sctp association from the clue group
>
> Correct.
>
> I do think we need to have some text on what happens if one removes the sctp association from the clue group - WITHOUT closing the clue data channel first. In my opinion it is an error case, but I think we should say that one MUST NOT send CLUE messages on such stream, and MUST discard any CLUE message received on such stream.

agree.

>> If you want to fallback, and you don't want to retain the sctp association, then you can:
>> - use O/A to remove the sctp association (port 0)
>> - terminate the actual sctp association
>> - (I think you can do the above in either order)
>> - it would be nice if you closed the clue data channel first,
>>    but probably not necessary to do so.
>
> Correct.
>
> But, one of my question (which is not specific to fallback) was: if we associate the SCTP association with the CLUE group, would it be semantically correct to also use the SCTP association for non-CLUE purpose (technically there is no problem)?

If we want the possibility of sharing the use of the association then 
this must be valid.

How the application determines what else the association is used for is 
out of scope for clue.

>> If the sctp association is closed for some reason, and you want to remain clue enabled, then you should:
>> - send another offer including the sctp m-line in the clue group
>> - start things up again
>> - (I think you don't try to reestablish the association until
>     the new offer is sent.)
>
> Regarding the last point, I guess that should be covered in the sctp-sdp draft.

I think this is implicitly inherited by SCTP from the definition of 
comedia. (RFC4145). But it would probably be good to spell it out.

At least for TCP, the issue is whether the app needs to maintain a 
listener for new connections after the initial connection has been 
established. (The mechanics for SCTP may be different, especially SCTP 
over DTLS, because it is an application layer stack rather than a socket 
interface.)

	Thanks,
	Paul

> Regards,
>
> Christer
>
>
>
>
> On 9/16/14 1:03 PM, Christer Holmberg wrote:
>> Hi Christian,
>>
>> I am not sure I agree with what you are saying.
>>
>> Sure, we can use the grouping to indicate that the SCTPoDTLS association will be used within a CLUE session.
>>
>> But, in order to open a data channel for CLUE, you need to use DCEP. Also, in order to close a data channel for CLUE, you need to reset the STCPoDTLS association. Just removing the m= line from the CLUE group won't do that - and I am not even sure we should allow that.
>>
>> Also, if we use a mid attribute to associate the SCTPoDTLS association with CLUE, can we then also use it for non-CLUE protocol? Does not seem semantically correct in my opinion.
>>
>> Regards,
>>
>> Christer
>>
>> -----Original Message-----
>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian
>> Groves
>> Sent: 16 September 2014 04:13
>> To: clue@ietf.org
>> Subject: Re: [clue] Draft new version: clue-data-channel-01
>>
>> Hello Christer,
>>
>> Just a question on 5.7 where it says "If an offerer wants to disable the CLUE Data Channel in an offer, it assigns a zero port value to the "m="
>> line representing the SCTPoDTLS association used to realize the CLUE Data channel."
>>
>> Wouldn't this have the effect of closing the SCTP/DTLS association causing CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to be for a generic webrtc data channel. To have a "CLUE data channel" we use the a=group.
>>
>> i.e. Generic Data Channel
>> m=application 54111 SCTP/DTLS 54111
>> a=sctpmap:54111 webrtc-datachannel
>>
>> CLUE data channel
>> a=group:CLUE 100
>> m=application 54111 SCTP/DTLS 54111
>> a=sctpmap:54111 webrtc-datachannel
>> a=mid:100
>>
>> Therefore if an endpoint wanted to remove CLUE from the data channel (without closing the SCTP/DTLS associated) it would remove the a=group and a=mid.
>>
>> There's also a typo in clause 5.7 "are unchanged" is repeated.
>>
>> Regards, Christian
>>
>> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>>
>>> Hi,
>>>
>>> I've submitted a new version of the CLUE data channel draft.
>>>
>>> The changes are mostly editorial: I structured the O/A procedures
>>> according to 3264, and updated the references.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Wed Sep 17 06:51:29 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 791DA1A03E6 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 06:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level: 
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBi3SUehRirs for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 06:51:21 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 79AE81A041D for <clue@ietf.org>; Wed, 17 Sep 2014 06:51:21 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta12.westchester.pa.mail.comcast.net with comcast id sDcb1o0031ei1Bg5CDrLFs; Wed, 17 Sep 2014 13:51:20 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta24.westchester.pa.mail.comcast.net with comcast id sDrL1o00G3Ge9ey3kDrLqE; Wed, 17 Sep 2014 13:51:20 +0000
Message-ID: <541991D8.9070009@alum.mit.edu>
Date: Wed, 17 Sep 2014 09:51:20 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <5418E00E.4060207@nteczone.com>
In-Reply-To: <5418E00E.4060207@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1410961880; bh=fW56XQYpiD0tBfYIrOhlzszgELA4y6hLVZgGZ2brFfc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=F+PpeOIxHimTKLt5et+5TjFK/+wJuFvux7jvsmzocViFYu+vjRTGBxh0kbcI2W5rT guizDIGoOu7XGORUIB9k9YWrjrUxxXXJQbzSiE1ItZvVc4yotKIM5g2Q6Lqshrdrhi Bo+t8QAC6kMps/MKmjnc1+BvwMyFYX8IPLI2Ns0nC8F1bOQRit4vWFHDMy8iBoMxmJ 13HZZPPgZtmYBA5uSWJ1DEKs515r7iT/egcwRt1CzgEx8n9nwuWuS2AH9kC7cd25TH qP9JBNX9hqkMfQMF/qdmgBOV+c6eNmsjKnveWhZAygpdhqKbZiMGE7cH4/xzMNgMPy SsGDYMXhQJXBg==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/TOQLU-cNfTafnSV4vv7KjIbw9XA
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 13:51:23 -0000

On 9/16/14 9:12 PM, Christian Groves wrote:
> Hello Christer,
>
> I think Paul has covered the issue with regards to fall back. We have to
> distinguish between the overall data channel and the resultant streams
> being used for CLUE.

We need to use terminology consistently. In your sentence above you 
mention "overall data channel". I infer you are talking about the SCTP 
association. IMO it is inappropriate to refer to that as a data channel.

IIUC a data channel is a pair of SCTP streams, one in each direction, 
while the only term for the collection of all of the streams is SCTP 
association.

	Thanks,
	Paul

> DCEP doesn't open the overall SCTP/DTLS association
> it establishes a protocol on a certain stream/s. Closure is done by
> resetting the stream (see clause 6.7/draft-ietf-rtcweb-data-channel-11)
> not by resetting the whole SCTP/DTLS association.
>
> With regards to the SCTP/DTLS association my understanding of the WebRTC
> datachannel is that you can use several application protocols within
> that association, i.e. CLUE and say BFCP. I think think we can say that
> an SCTP/DTLS association must only contain CLUE. I think its valid to
> use an mid in multiple groups. RFC5888 clause 6 says "An "m" line
> identified by its "mid" attribute MAY appear in more than one "a=group"
> line."
>
> Regards, Christian
>
> On 17/09/2014 3:03 AM, Christer Holmberg wrote:
>> Hi Christian,
>>
>> I am not sure I agree with what you are saying.
>>
>> Sure, we can use the grouping to indicate that the SCTPoDTLS
>> association will be used within a CLUE session.
>>
>> But, in order to open a data channel for CLUE, you need to use DCEP.
>> Also, in order to close a data channel for CLUE, you need to reset the
>> STCPoDTLS association. Just removing the m= line from the CLUE group
>> won't do that - and I am not even sure we should allow that.
>>
>> Also, if we use a mid attribute to associate the SCTPoDTLS association
>> with CLUE, can we then also use it for non-CLUE protocol? Does not
>> seem semantically correct in my opinion.
>>
>> Regards,
>>
>> Christer
>>
>> -----Original Message-----
>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian Groves
>> Sent: 16 September 2014 04:13
>> To: clue@ietf.org
>> Subject: Re: [clue] Draft new version: clue-data-channel-01
>>
>> Hello Christer,
>>
>> Just a question on 5.7 where it says "If an offerer wants to disable
>> the CLUE Data Channel in an offer, it assigns a zero port value to the
>> "m="
>> line representing the SCTPoDTLS association used to realize the CLUE
>> Data channel."
>>
>> Wouldn't this have the effect of closing the SCTP/DTLS association
>> causing CLUE AND any other protocols to be disabled? Clause 5.7 and
>> 5.8 seem to be for a generic webrtc data channel. To have a "CLUE data
>> channel" we use the a=group.
>>
>> i.e. Generic Data Channel
>> m=application 54111 SCTP/DTLS 54111
>> a=sctpmap:54111 webrtc-datachannel
>>
>> CLUE data channel
>> a=group:CLUE 100
>> m=application 54111 SCTP/DTLS 54111
>> a=sctpmap:54111 webrtc-datachannel
>> a=mid:100
>>
>> Therefore if an endpoint wanted to remove CLUE from the data channel
>> (without closing the SCTP/DTLS associated) it would remove the a=group
>> and a=mid.
>>
>> There's also a typo in clause 5.7 "are unchanged" is repeated.
>>
>> Regards, Christian
>>
>> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>> Hi,
>>>
>>> I've submitted a new version of the CLUE data channel draft.
>>>
>>> The changes are mostly editorial: I structured the O/A procedures
>>> according to 3264, and updated the references.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Wed Sep 17 11:47:50 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B98FE1A0AD6 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 11:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MK1vI5e8jz3Y for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 11:47:44 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0476E1A0ACA for <clue@ietf.org>; Wed, 17 Sep 2014 11:47:43 -0700 (PDT)
X-AuditID: c1b4fb3a-f79da6d0000008c7-68-5419d74d117e
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 6B.EF.02247.D47D9145; Wed, 17 Sep 2014 20:47:41 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0174.001; Wed, 17 Sep 2014 20:47:41 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>
Thread-Topic: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
Thread-Index: AQHP0mk0GdjPYll8W0+041HOtHVL0pwFqq/w
Date: Wed, 17 Sep 2014 18:47:40 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D450449@ESESSMB209.ericsson.se>
References: <20140321141121.16330.32657.idtracker@ietfa.amsl.com> <E97C33E5D67C2843AFA535DE2E5B80C1573A7DA6@SZXEMA503-MBX.china.huawei.com> <7594FB04B1934943A5C02806D1A2204B1D2EFC38@ESESSMB209.ericsson.se> <E97C33E5D67C2843AFA535DE2E5B80C157402EDC@SZXEMA503-MBX.china.huawei.com>
In-Reply-To: <E97C33E5D67C2843AFA535DE2E5B80C157402EDC@SZXEMA503-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyM+Jvja7vdckQgx/rrCz2n7rMbHHwRQuT A5NHy5G3rB5LlvxkCmCK4rJJSc3JLEst0rdL4Mr4eOUsW8EOrYr2dW/ZGhiXKnYxcnJICJhI rLu3gAXCFpO4cG89WxcjF4eQwFFGibNHL7FCOEsYJTb/283cxcjBwSZgIdH9TxukQQSo+cjU t6wgNrOAssTXhk1MILawgJPEqraXzBA1zhIvNt5gh7CNJI7deM4KMoZFQFVi3cQ0kDCvgK/E w/sHwFqFBOYySRzdVQxicwqESfx81M4GYjMC3fb91BomiFXiEreezGeCuFlAYsme88wQtqjE y8f/WCFsJYkV2y8xQtTrSCzY/YkNwtaWWLbwNTPEXkGJkzOfsExgFJuFZOwsJC2zkLTMQtKy gJFlFaNocWpxcW66kZFealFmcnFxfp5eXmrJJkZg9Bzc8ttqB+PB546HGAU4GJV4eBVeS4QI sSaWFVfmHmKU5mBREuddeG5esJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGpr/VT7vl99z0 vJoRbfD8bszON/y7A/nvrba/tfyksFv8qSopZ2c3j8xnrlcv2kQ07ZbKvHzkRmu51FzT9d4x 6kenRzXYRNlzf7BuDg4xv8d++8XZ0jyL/+/rLuUuVplaO1FuVo+K7cQnJY1TX/Bp6xs+uMzA XP/k52vbNdmGx7Z3mr+pOM2mxFKckWioxVxUnAgA2hxlRX8CAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/fLU5SddrwvVe-GWTn8ixo2jNtSI
Cc: "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 18:47:46 -0000

Hi Scarlett,

I apologise that I forgot to fix the typo. I'll do it in the next version :=
)

I'll also try to keep the examples etc aligned with the sctp-sdp draft.

Thanks for reminding me :)

Regards,

Christer

-----Original Message-----
From: Liuyan (Scarlett) [mailto:scarlett.liuyan@huawei.com]=20
Sent: 17 September 2014 14:19
To: Christer Holmberg
Cc: clue@ietf.org
Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt

Hi Christer,

	There is still a typo in the draft-ietf-clue-datachannel-01 and the typo w=
as confirmed by you in the previous e-mail below .=20
	Maybe you forgot it.
	By the way, the draft-ietf-mmusic-sctp-sdp-07 says below:

	4.1.1.  sctp-port

       sctp-port-attr   =3D  "a=3Dsctp-port=3D" portnumber
       port-number      =3D  port
	4.1.2.  max-message-size

    sctpmap-attr        =3D  "a=3Dfmtp:" association-usage [max-message-siz=
e]
    max-message-size    =3D  "max-message-size" EQUALS 1*DIGIT

	8.3.  SDP description for SCTP over DTLS Connection
	m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel
    a=3Dfmtp:webrtc-datachannel max-message-size=3D100000
    a=3Dsctp-port 5000

	At least ,I have a question.=20
	Do you think that your example in the draft-ietf-clue-datachannel-01 shoul=
d keep the consistency with the example of draft-ietf-mmusic-sctp-sdp-07 ?=
=20

Best Regards,
Scarlett

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Wednesday, May 07, 2014 6:00 PM
> To: Liuyan (Scarlett)
> Cc: clue@ietf.org
> Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt
>=20
> Hi Scarlett,
>=20
> Thanks for spotting the typo! :)
>=20
> Regards,
>=20
> Christer
>=20
> -----Original Message-----
> From: Liuyan (Scarlett) [mailto:scarlett.liuyan@huawei.com]
> Sent: 7. toukokuuta 2014 5:41
> To: Christer Holmberg
> Cc: clue@ietf.org
> Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt
>=20
> Hi Christer,
>=20
>     I notice that there is a typo in section 5.6 of
> draft-ietf-clue-datachannel-00 below:
>=20
>           5.6.  Example
>=20
>            m=3Dapplication 54111 SCTP/DTLS 54111
>            a=3Dsctpmap:54111 webrtc-datachannel
>=20
>           Figure 1: SDP Media Description for a CLUE Data Channel
>=20
>    As described in section 3 of draft-ietf-mmusic-sctp-sdp-06 below:
>=20
>    The 'SCTP/DTLS' protocol identifier indicates that the media
>    described will use the Datagram Transport Layer Security (DTLS)
>    [RFC4347] over SCTP as specified in [RFC6083].
>=20
>    The 'DTLS/SCTP' protocol identifier indicates that the media
>    described will use SCTP on top of the Datagram Transport Layer
>    Security (DTLS) protocol as specified in
>    [I-D.tuexen-tsvwg-sctp-dtls-encaps].  The actual layer below DTLS can
>    be plain UDP or what ICE agrees on (in the case ICE is used to
>    negotiate the actual transport flow).  The lower layer used is
>    identified from the elements present inside the m=3D line block.
>=20
>    so it should be reworded below:
>=20
>     5.6.  Example
>=20
>            m=3Dapplication 54111 DTLS/SCTP 54111
>            a=3Dsctpmap:54111 webrtc-datachannel
>=20
>           Figure 1: SDP Media Description for a CLUE Data Channel
>=20
> Best Regards,
> Scarlett
>=20
> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of=20
> internet-drafts@ietf.org
> Sent: Friday, March 21, 2014 10:11 PM
> To: i-d-announce@ietf.org
> Cc: clue@ietf.org
> Subject: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the ControLling mUltiple streams for=20
> tElepresence Working Group of the IETF.
>=20
>         Title           : CLUE Protocol Data Channel
>         Author          : Christer Holmberg
> 	Filename        : draft-ietf-clue-datachannel-00.txt
> 	Pages           : 12
> 	Date            : 2014-03-20
>=20
> Abstract:
>    This document defines how to use the WebRTC Data Channel mechanism,
>    together with the Data Channel Establishment Protocol (DCEP) in order
>    to establish a data channel, referred to as CLUE Data Channel, for
>    transporting CLUE protocol messages between two CLUE entities.
>=20
>    The document defines the SCTP considerations specific to a CLUE Data
>    Channel, the SDP offer/answer procedures for negotiating the
>    establishment of, and the DCEP procedures for opening, a CLUE Data
>    Channel.
>=20
>    Details and procedures associated with the CLUE protocol are outside
>    the scope of this document.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-clue-datachannel-00
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Wed Sep 17 11:56:21 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDFF1A0745 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 11:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oYbzEgfNJdfH for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 11:56:17 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA581A0422 for <clue@ietf.org>; Wed, 17 Sep 2014 11:56:16 -0700 (PDT)
X-AuditID: c1b4fb3a-f79da6d0000008c7-67-5419d94ea72c
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id F4.60.02247.E49D9145; Wed, 17 Sep 2014 20:56:14 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0174.001; Wed, 17 Sep 2014 20:56:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] Draft new version: clue-data-channel-01
Thread-Index: Ac/Q6P1eNDrLxC9JTsiySht2hyqOBQAUZKOAACUlsyD//+kIgP/+/UjwgAJU+gD//4khUA==
Date: Wed, 17 Sep 2014 18:56:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D450478@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <54187495.5080501@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D44E68B@ESESSMB209.ericsson.se> <54199056.7050101@alum.mit.edu>
In-Reply-To: <54199056.7050101@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrALMWRmVeSWpSXmKPExsUyM+Jvja7fTckQg+t/bSz2n7rMbLFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugStj/ZwrLAWHVCrurnRsYJwn28XIySEhYCJx 7cQldghbTOLCvfVsXYxcHEICRxklHr1+zA7hLGGU2NY9hbWLkYODTcBCovufNkiDiICnxI6P U5hBbGEBa4mWg61gJSICNhKLlmZClIRJPDnSyQZiswioSnx41s0CYvMK+EocfngVatduJon5 ky6DFXEK6Eis2HyDEcRmBDro+6k1TCA2s4C4xK0n85kgDhWQWLLnPDOELSrx8vE/VghbSWLF 9kuMEPU6Egt2f2KDsLUlli18zQyxWFDi5MwnLBMYRWchGTsLScssJC2zkLQsYGRZxShanFpc nJtuZKSXWpSZXFycn6eXl1qyiREYJQe3/LbawXjwueMhRgEORiUeXoXXEiFCrIllxZW5hxil OViUxHkXnpsXLCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoFResoze67dqe9ZX1x4zOEeP9H3 jjvrypMcx1uKwzqiP/I5rJD7GtK1a+vkr5M2Mn+ZduFgyn6d3mgPxpDCmdL2k352f3F1lOTJ U71j48N5WiF1+Z70SRPqFoUfO8tYby/X3ZR/KOj06gaO1ujm5NQdC16L25xnDGuScfxVt2HB J5PuLQYhLTOVWIozEg21mIuKEwGJDmLxcwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/6k2425BUQcek9_gDejfUFTSQzys
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 18:56:19 -0000

Hi,

...

>> But, one of my question (which is not specific to fallback) was: if we a=
ssociate the SCTP association >> with the CLUE group, would it be semantica=
lly correct to also use the SCTP association for non-
>> CLUE purpose (technically there is no problem)?
>
> If we want the possibility of sharing the use of the association then thi=
s must be valid.

I guess we could think about whether the SCTP association really needs to b=
e within the CLUE group.

The main purpose of the CLUE group is to indicate which media is CLUE contr=
olled.

Is it really that important to associate the SCTP association with the CLUE=
 group? After all, what matters is whether you have established a CLUE data=
 channel (using DCEP) on that SCTP association or not...

Regards,

Christer




>> If the sctp association is closed for some reason, and you want to remai=
n clue enabled, then you should:
>> - send another offer including the sctp m-line in the clue group
>> - start things up again
>> - (I think you don't try to reestablish the association until
>     the new offer is sent.)
>
> Regarding the last point, I guess that should be covered in the sctp-sdp =
draft.

I think this is implicitly inherited by SCTP from the definition of comedia=
. (RFC4145). But it would probably be good to spell it out.

At least for TCP, the issue is whether the app needs to maintain a listener=
 for new connections after the initial connection has been established. (Th=
e mechanics for SCTP may be different, especially SCTP over DTLS, because i=
t is an application layer stack rather than a socket
interface.)

	Thanks,
	Paul

> Regards,
>
> Christer
>
>
>
>
> On 9/16/14 1:03 PM, Christer Holmberg wrote:
>> Hi Christian,
>>
>> I am not sure I agree with what you are saying.
>>
>> Sure, we can use the grouping to indicate that the SCTPoDTLS association=
 will be used within a CLUE session.
>>
>> But, in order to open a data channel for CLUE, you need to use DCEP. Als=
o, in order to close a data channel for CLUE, you need to reset the STCPoDT=
LS association. Just removing the m=3D line from the CLUE group won't do th=
at - and I am not even sure we should allow that.
>>
>> Also, if we use a mid attribute to associate the SCTPoDTLS association w=
ith CLUE, can we then also use it for non-CLUE protocol? Does not seem sema=
ntically correct in my opinion.
>>
>> Regards,
>>
>> Christer
>>
>> -----Original Message-----
>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian=20
>> Groves
>> Sent: 16 September 2014 04:13
>> To: clue@ietf.org
>> Subject: Re: [clue] Draft new version: clue-data-channel-01
>>
>> Hello Christer,
>>
>> Just a question on 5.7 where it says "If an offerer wants to disable the=
 CLUE Data Channel in an offer, it assigns a zero port value to the "m=3D"
>> line representing the SCTPoDTLS association used to realize the CLUE Dat=
a channel."
>>
>> Wouldn't this have the effect of closing the SCTP/DTLS association causi=
ng CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to =
be for a generic webrtc data channel. To have a "CLUE data channel" we use =
the a=3Dgroup.
>>
>> i.e. Generic Data Channel
>> m=3Dapplication 54111 SCTP/DTLS 54111
>> a=3Dsctpmap:54111 webrtc-datachannel
>>
>> CLUE data channel
>> a=3Dgroup:CLUE 100
>> m=3Dapplication 54111 SCTP/DTLS 54111
>> a=3Dsctpmap:54111 webrtc-datachannel
>> a=3Dmid:100
>>
>> Therefore if an endpoint wanted to remove CLUE from the data channel (wi=
thout closing the SCTP/DTLS associated) it would remove the a=3Dgroup and a=
=3Dmid.
>>
>> There's also a typo in clause 5.7 "are unchanged" is repeated.
>>
>> Regards, Christian
>>
>> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>>
>>> Hi,
>>>
>>> I've submitted a new version of the CLUE data channel draft.
>>>
>>> The changes are mostly editorial: I structured the O/A procedures=20
>>> according to 3264, and updated the references.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Wed Sep 17 12:26:33 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501C21A0ACD for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 12:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level: 
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vPmF1yyNmR6 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 12:26:29 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9E2D1A0AF1 for <clue@ietf.org>; Wed, 17 Sep 2014 12:26:28 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by resqmta-ch2-02v.sys.comcast.net with comcast id sJdl1o0040vyq2s01KSTLK; Wed, 17 Sep 2014 19:26:27 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta05.westchester.pa.mail.comcast.net with comcast id sKST1o0013Ge9ey3RKSTNp; Wed, 17 Sep 2014 19:26:27 +0000
Message-ID: <5419E062.40507@alum.mit.edu>
Date: Wed, 17 Sep 2014 15:26:26 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "clue@ietf.org" <clue@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <54187495.5080501@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D44E68B@ESESSMB209.ericsson.se> <54199056.7050101@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D450478@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D450478@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1410981987; bh=ywfDoOAVloHOGxkfFhGH9226K4jKoAME8WgBF8Jaaq0=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=fH8FtkfP6SkJjLu/x/5m7kkEVgWGoMyrfparhfxo3cIMkAJvY0TsqaejYh80wQw0x nbRatHn/WceI6EEafp/inqBZiU+z09LqpO7ZUCvC3nQXhHg25yEy96CwqWqs+34X23 ADt/mxsQm4ZoW561yfypCh41oap1bp4zduhAL+fw6jDQs+y8rj4xTm1MhvMw27Inx4 lECQV/9rnrvIWeyqGguu5ezfWjQ5kgRmQwSiJz1TbNZ9m3ubylIzkYJdD+UBfnpjrl H2eFpt6D46JP5RKUDdG/FqrGl8YQDEc5kB60CJKgb9yyvyVsolMHUqHATjabf7zN8W rGu7IIs9wSuhA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/XWgze1w8D6nH6s1-5zrRulVLp4w
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 19:26:31 -0000

On 9/17/14 2:56 PM, Christer Holmberg wrote:
> Hi,
>
> ...
>
>>> But, one of my question (which is not specific to fallback) was: if we associate the SCTP association >> with the CLUE group, would it be semantically correct to also use the SCTP association for non-
>>> CLUE purpose (technically there is no problem)?
>>
>> If we want the possibility of sharing the use of the association then this must be valid.
>
> I guess we could think about whether the SCTP association really needs to be within the CLUE group.
>
> The main purpose of the CLUE group is to indicate which media is CLUE controlled.
>
> Is it really that important to associate the SCTP association with the CLUE group? After all, what matters is whether you have established a CLUE data channel (using DCEP) on that SCTP association or not...

I see no problem with including it in the clue group as long as we 
specify what that means to us.

I can think of at least two reasons why we want/need it in the clue group:

1) In the initial offer, it may be the *only* thing in the clue group. I 
think we need it to be clear we are clue enabled.

2) If it happened that there were multiple SCTP associations, the clue 
group is how we know which one is to contain the clue channel.

	Thanks,
	Paul

> Regards,
>
> Christer
>
>
>
>
>>> If the sctp association is closed for some reason, and you want to remain clue enabled, then you should:
>>> - send another offer including the sctp m-line in the clue group
>>> - start things up again
>>> - (I think you don't try to reestablish the association until
>>      the new offer is sent.)
>>
>> Regarding the last point, I guess that should be covered in the sctp-sdp draft.
>
> I think this is implicitly inherited by SCTP from the definition of comedia. (RFC4145). But it would probably be good to spell it out.
>
> At least for TCP, the issue is whether the app needs to maintain a listener for new connections after the initial connection has been established. (The mechanics for SCTP may be different, especially SCTP over DTLS, because it is an application layer stack rather than a socket
> interface.)
>
> 	Thanks,
> 	Paul
>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>> On 9/16/14 1:03 PM, Christer Holmberg wrote:
>>> Hi Christian,
>>>
>>> I am not sure I agree with what you are saying.
>>>
>>> Sure, we can use the grouping to indicate that the SCTPoDTLS association will be used within a CLUE session.
>>>
>>> But, in order to open a data channel for CLUE, you need to use DCEP. Also, in order to close a data channel for CLUE, you need to reset the STCPoDTLS association. Just removing the m= line from the CLUE group won't do that - and I am not even sure we should allow that.
>>>
>>> Also, if we use a mid attribute to associate the SCTPoDTLS association with CLUE, can we then also use it for non-CLUE protocol? Does not seem semantically correct in my opinion.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>> -----Original Message-----
>>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian
>>> Groves
>>> Sent: 16 September 2014 04:13
>>> To: clue@ietf.org
>>> Subject: Re: [clue] Draft new version: clue-data-channel-01
>>>
>>> Hello Christer,
>>>
>>> Just a question on 5.7 where it says "If an offerer wants to disable the CLUE Data Channel in an offer, it assigns a zero port value to the "m="
>>> line representing the SCTPoDTLS association used to realize the CLUE Data channel."
>>>
>>> Wouldn't this have the effect of closing the SCTP/DTLS association causing CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to be for a generic webrtc data channel. To have a "CLUE data channel" we use the a=group.
>>>
>>> i.e. Generic Data Channel
>>> m=application 54111 SCTP/DTLS 54111
>>> a=sctpmap:54111 webrtc-datachannel
>>>
>>> CLUE data channel
>>> a=group:CLUE 100
>>> m=application 54111 SCTP/DTLS 54111
>>> a=sctpmap:54111 webrtc-datachannel
>>> a=mid:100
>>>
>>> Therefore if an endpoint wanted to remove CLUE from the data channel (without closing the SCTP/DTLS associated) it would remove the a=group and a=mid.
>>>
>>> There's also a typo in clause 5.7 "are unchanged" is repeated.
>>>
>>> Regards, Christian
>>>
>>> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>>>
>>>> Hi,
>>>>
>>>> I've submitted a new version of the CLUE data channel draft.
>>>>
>>>> The changes are mostly editorial: I structured the O/A procedures
>>>> according to 3264, and updated the references.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
>


From nobody Wed Sep 17 17:12:10 2014
Return-Path: <scarlett.liuyan@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 406121A6F29 for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 17:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.652
X-Spam-Level: 
X-Spam-Status: No, score=-4.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5l-fc_JnKOJp for <clue@ietfa.amsl.com>; Wed, 17 Sep 2014 17:12:03 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2476F1A6EED for <clue@ietf.org>; Wed, 17 Sep 2014 17:12:02 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMS51964; Thu, 18 Sep 2014 00:12:00 +0000 (GMT)
Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 18 Sep 2014 01:11:58 +0100
Received: from SZXEMA503-MBX.china.huawei.com ([169.254.5.43]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Thu, 18 Sep 2014 08:11:53 +0800
From: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
Thread-Index: AQHP0mkt7llefKfx50OLrad4L6ph4JwFJMgAgADfFUA=
Date: Thu, 18 Sep 2014 00:11:52 +0000
Message-ID: <E97C33E5D67C2843AFA535DE2E5B80C157402F4C@SZXEMA503-MBX.china.huawei.com>
References: <20140321141121.16330.32657.idtracker@ietfa.amsl.com> <E97C33E5D67C2843AFA535DE2E5B80C1573A7DA6@SZXEMA503-MBX.china.huawei.com> <7594FB04B1934943A5C02806D1A2204B1D2EFC38@ESESSMB209.ericsson.se> <E97C33E5D67C2843AFA535DE2E5B80C157402EDC@SZXEMA503-MBX.china.huawei.com> <7594FB04B1934943A5C02806D1A2204B1D450449@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D450449@ESESSMB209.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.63.147.208]
Content-Type: multipart/alternative; boundary="_000_E97C33E5D67C2843AFA535DE2E5B80C157402F4CSZXEMA503MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/kROg9IiBZUoQdhWGBkhbw5JAom4
Cc: "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 00:12:07 -0000

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

Hi Christer,



         OK.

         By the way, there is also a typo in the example of draft-ietf-mmus=
ic-sctp-sdp-07 below.

         8.4.  SDP description for SCTP over DTLS Connection using default =
values

         m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel

          c=3DIN IP4 192.0.2.2

          a=3Dsetup:actpass

          a=3Dconnection:new

          a=3Dfingerprint:SHA-1 \

            4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB



                                 Figure 7



   The endpoint at 192.0.2.1 responds with the following description,

   with default value for the sctp-port and max-message-size parameters:



          m=3Dapplication 62442 DTLS/SCTP webrtc-datachannel

          c=3DIN IP4 192.0.2.1

          a=3Dsetup:actpass=3D=3D=3D=3D=3D=3D=3D=3D=3Dit should be passive

          a=3Dconnection:new

          a=3Dfingerprint:SHA-1 \

            4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB



                                 Figure 8

         If you refers to the examples, please notice that and thanks.



Best Regards,

Scarlett



> -----Original Message-----

> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]

> Sent: Thursday, September 18, 2014 2:48 AM

> To: Liuyan (Scarlett)

> Cc: clue@ietf.org

> Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt

>

> Hi Scarlett,

>

> I apologise that I forgot to fix the typo. I'll do it in the next version=
 :)

>

> I'll also try to keep the examples etc aligned with the sctp-sdp draft.

>

> Thanks for reminding me :)

>

> Regards,

>

> Christer

>

> -----Original Message-----

> From: Liuyan (Scarlett) [mailto:scarlett.liuyan@huawei.com]

> Sent: 17 September 2014 14:19

> To: Christer Holmberg

> Cc: clue@ietf.org<mailto:clue@ietf.org>

> Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt

>

> Hi Christer,

>

>      There is still a typo in the draft-ietf-clue-datachannel-01 and the =
typo

> was confirmed by you in the previous e-mail below .

>      Maybe you forgot it.

>      By the way, the draft-ietf-mmusic-sctp-sdp-07 says below:

>

>      4.1.1.  sctp-port

>

>        sctp-port-attr   =3D  "a=3Dsctp-port=3D" portnumber

>        port-number      =3D  port

>      4.1.2.  max-message-size

>

>     sctpmap-attr        =3D  "a=3Dfmtp:" association-usage

> [max-message-size]

>     max-message-size    =3D  "max-message-size" EQUALS 1*DIGIT

>

>      8.3.  SDP description for SCTP over DTLS Connection

>      m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel

>     a=3Dfmtp:webrtc-datachannel max-message-size=3D100000

>     a=3Dsctp-port 5000

>

>      At least ,I have a question.

>      Do you think that your example in the draft-ietf-clue-datachannel-01

> should keep the consistency with the example of

> draft-ietf-mmusic-sctp-sdp-07 ?

>

> Best Regards,

> Scarlett

>

> > -----Original Message-----

> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]

> > Sent: Wednesday, May 07, 2014 6:00 PM

> > To: Liuyan (Scarlett)

> > Cc: clue@ietf.org<mailto:clue@ietf.org>

> > Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt

> >

> > Hi Scarlett,

> >

> > Thanks for spotting the typo! :)

> >

> > Regards,

> >

> > Christer

> >

> > -----Original Message-----

> > From: Liuyan (Scarlett) [mailto:scarlett.liuyan@huawei.com]

> > Sent: 7. toukokuuta 2014 5:41

> > To: Christer Holmberg

> > Cc: clue@ietf.org<mailto:clue@ietf.org>

> > Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt

> >

> > Hi Christer,

> >

> >     I notice that there is a typo in section 5.6 of

> > draft-ietf-clue-datachannel-00 below:

> >

> >           5.6.  Example

> >

> >            m=3Dapplication 54111 SCTP/DTLS 54111

> >            a=3Dsctpmap:54111 webrtc-datachannel

> >

> >           Figure 1: SDP Media Description for a CLUE Data Channel

> >

> >    As described in section 3 of draft-ietf-mmusic-sctp-sdp-06 below:

> >

> >    The 'SCTP/DTLS' protocol identifier indicates that the media

> >    described will use the Datagram Transport Layer Security (DTLS)

> >    [RFC4347] over SCTP as specified in [RFC6083].

> >

> >    The 'DTLS/SCTP' protocol identifier indicates that the media

> >    described will use SCTP on top of the Datagram Transport Layer

> >    Security (DTLS) protocol as specified in

> >    [I-D.tuexen-tsvwg-sctp-dtls-encaps].  The actual layer below DTLS ca=
n

> >    be plain UDP or what ICE agrees on (in the case ICE is used to

> >    negotiate the actual transport flow).  The lower layer used is

> >    identified from the elements present inside the m=3D line block.

> >

> >    so it should be reworded below:

> >

> >     5.6.  Example

> >

> >            m=3Dapplication 54111 DTLS/SCTP 54111

> >            a=3Dsctpmap:54111 webrtc-datachannel

> >

> >           Figure 1: SDP Media Description for a CLUE Data Channel

> >

> > Best Regards,

> > Scarlett

> >

> > -----Original Message-----

> > From: clue [mailto:clue-bounces@ietf.org] On Behalf Of

> > internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>

> > Sent: Friday, March 21, 2014 10:11 PM

> > To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>

> > Cc: clue@ietf.org<mailto:clue@ietf.org>

> > Subject: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt

> >

> >

> > A New Internet-Draft is available from the on-line Internet-Drafts

> directories.

> >  This draft is a work item of the ControLling mUltiple streams for

> > tElepresence Working Group of the IETF.

> >

> >         Title           : CLUE Protocol Data Channel

> >         Author          : Christer Holmberg

> > Filename        : draft-ietf-clue-datachannel-00.txt

> > Pages           : 12

> > Date            : 2014-03-20

> >

> > Abstract:

> >    This document defines how to use the WebRTC Data Channel

> mechanism,

> >    together with the Data Channel Establishment Protocol (DCEP) in orde=
r

> >    to establish a data channel, referred to as CLUE Data Channel, for

> >    transporting CLUE protocol messages between two CLUE entities.

> >

> >    The document defines the SCTP considerations specific to a CLUE Data

> >    Channel, the SDP offer/answer procedures for negotiating the

> >    establishment of, and the DCEP procedures for opening, a CLUE Data

> >    Channel.

> >

> >    Details and procedures associated with the CLUE protocol are outside

> >    the scope of this document.

> >

> >

> > The IETF datatracker status page for this draft is:

> > https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/

> >

> > There's also a htmlized version available at:

> > http://tools.ietf.org/html/draft-ietf-clue-datachannel-00

> >

> >

> > Please note that it may take a couple of minutes from the time of

> > submission until the htmlized version and diff are available at tools.i=
etf.org.

> >

> > Internet-Drafts are also available by anonymous FTP at:

> > ftp://ftp.ietf.org/internet-drafts/

> >

> > _______________________________________________

> > clue mailing list

> > clue@ietf.org<mailto:clue@ietf.org>

> > https://www.ietf.org/mailman/listinfo/clue

--_000_E97C33E5D67C2843AFA535DE2E5B80C157402F4CSZXEMA503MBXchi_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:9.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
span.Char0
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 137.75pt 72.0pt 137.7pt;}
div.WordSection1
	{page:WordSection1;}
--></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=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Hi Christer,<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; OK.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; By the way, there is also a typo in the example of dra=
ft-ietf-mmusic-sctp-sdp-07 below.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; 8.4.&nbsp; SDP description for SCTP over DTLS Connecti=
on using default values<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel<o:p=
></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; c=3DIN IP4 192.0.2.2<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; <span style=3D"background:yellow;mso-highlight:y=
ellow">
a=3Dsetup:actpass</span><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dconnection:new<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dfingerprint:SHA-1 \<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:=
3E:5D:49:6B:19:E5:7C:AB<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Figure 7<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; The endpoint at=
 192.0.2.1 responds with the following description,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; with default va=
lue for the sctp-port and max-message-size parameters:<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; m=3Dapplication 62442 DTLS/SCTP webrtc-datachann=
el<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; c=3DIN IP4 192.0.2.1<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; <span style=3D"background:yellow;mso-highlight:y=
ellow">
a=3Dsetup:actpass</span>=3D=3D=3D=3D=3D=3D=3D=3D=3D<span style=3D"backgroun=
d:lime;mso-highlight:lime">it should be passive</span><o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dconnection:new<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dfingerprint:SHA-1 \<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:=
3E:5D:49:6B:19:E5:7C:AB<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;Figure 8<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; If you refers to the examples, please notice that and =
thanks.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Best Regards,<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Scarlett<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; -----Original Message--=
---<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; From: Christer Holmberg=
 [mailto:christer.holmberg@ericsson.com]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Sent: Thursday, Septemb=
er 18, 2014 2:48 AM<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; To: Liuyan (Scarlett)<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Cc: clue@ietf.org<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Subject: RE: [clue] I-D=
 Action: draft-ietf-clue-datachannel-01.txt<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Hi Scarlett,<o:p></o:p>=
</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; I apologise that I forg=
ot to fix the typo. I'll do it in the next version :)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; I'll also try to keep t=
he examples etc aligned with the sctp-sdp draft.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Thanks for reminding me=
 :)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Regards,<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Christer<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; -----Original Message--=
---<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; From: Liuyan (Scarlett)=
 [<a href=3D"mailto:scarlett.liuyan@huawei.com"><span style=3D"color:window=
text;text-decoration:none">mailto:scarlett.liuyan@huawei.com</span></a>]<o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Sent: 17 September 2014=
 14:19<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; To: Christer Holmberg<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Cc: <a href=3D"mailto:c=
lue@ietf.org"><span style=3D"color:windowtext;text-decoration:none">clue@ie=
tf.org</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Subject: RE: [clue] I-D=
 Action: draft-ietf-clue-datachannel-01.txt<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Hi Christer,<o:p></o:p>=
</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; There is still a typo in the draft-ietf-clue-datachannel-01 and the typo<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; was confirmed by you in=
 the previous e-mail below .<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; Maybe you forgot it.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; By the way, the draft-ietf-mmusic-sctp-sdp-07 says below:<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; 4.1.1.&nbsp; sctp-port<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;sctp-port-attr&nbsp;&nbsp; =3D&nbsp; &quot;a=3Dsctp-port=
=3D&quot; portnumber<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;port-number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&nbsp; port=
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; 4.1.2.&nbsp; max-message-size<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
;sctpmap-attr&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&nbsp; &quot;a=
=3Dfmtp:&quot; association-usage<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; [max-message-size]<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
;max-message-size&nbsp;&nbsp;&nbsp; =3D&nbsp; &quot;max-message-size&quot; =
EQUALS 1*DIGIT<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; 8.3.&nbsp; SDP description for SCTP over DTLS Connection<o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
;a=3Dfmtp:webrtc-datachannel max-message-size=3D100000<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
;a=3Dsctp-port 5000<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; At least ,I have a question.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &nbsp;&nbsp;&nbsp;&nbsp=
; Do you think that your example in the draft-ietf-clue-datachannel-01<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; should keep the consist=
ency with the example of<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; draft-ietf-mmusic-sctp-=
sdp-07 ?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Best Regards,<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; Scarlett<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; -----Original Mess=
age-----<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; From: Christer Hol=
mberg [<a href=3D"mailto:christer.holmberg@ericsson.com"><span style=3D"col=
or:windowtext;text-decoration:none">mailto:christer.holmberg@ericsson.com</=
span></a>]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Sent: Wednesday, M=
ay 07, 2014 6:00 PM<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; To: Liuyan (Scarle=
tt)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Cc: <a href=3D"mai=
lto:clue@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">clue@ietf.org</span><=
/a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Subject: RE: [clue=
] I-D Action: draft-ietf-clue-datachannel-00.txt<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Hi Scarlett,<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Thanks for spottin=
g the typo! :)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Regards,<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Christer<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; -----Original Mess=
age-----<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; From: Liuyan (Scar=
lett) [<a href=3D"mailto:scarlett.liuyan@huawei.com"><span style=3D"color:w=
indowtext;text-decoration:none">mailto:scarlett.liuyan@huawei.com</span></a=
>]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Sent: 7. toukokuut=
a 2014 5:41<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; To: Christer Holmb=
erg<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Cc: <a href=3D"mai=
lto:clue@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">clue@ietf.org</span><=
/a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Subject: RE: [clue=
] I-D Action: draft-ietf-clue-datachannel-00.txt<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Hi Christer,<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp; I notice that there is a typo in section 5.6 of<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; draft-ietf-clue-da=
tachannel-00 below:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5.6.&nbsp; Example<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=3Dapplication 54111 SCTP/=
DTLS 54111<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dsctpmap:54111 webrtc-da=
tachannel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Figure 1: SDP Media Description f=
or a CLUE Data Channel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
As described in section 3 of draft-ietf-mmusic-sctp-sdp-06 below:<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
The 'SCTP/DTLS' protocol identifier indicates that the media<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
described will use the Datagram Transport Layer Security (DTLS)<o:p></o:p><=
/span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
[RFC4347] over SCTP as specified in [RFC6083].<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
The 'DTLS/SCTP' protocol identifier indicates that the media<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
described will use SCTP on top of the Datagram Transport Layer<o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
Security (DTLS) protocol as specified in<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
[I-D.tuexen-tsvwg-sctp-dtls-encaps].&nbsp; The actual layer below DTLS can<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
be plain UDP or what ICE agrees on (in the case ICE is used to<o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
negotiate the actual transport flow).&nbsp; The lower layer used is<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
identified from the elements present inside the m=3D line block.<o:p></o:p>=
</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
so it should be reworded below:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp; 5.6.&nbsp; Example<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=3Dapplication 54111 DTLS/=
SCTP 54111<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dsctpmap:54111 webrtc-da=
tachannel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Figure 1: SDP Media Description f=
or a CLUE Data Channel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Best Regards,<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Scarlett<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; -----Original Mess=
age-----<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; From: clue [<a hre=
f=3D"mailto:clue-bounces@ietf.org"><span style=3D"color:windowtext;text-dec=
oration:none">mailto:clue-bounces@ietf.org</span></a>] On Behalf Of<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; <a href=3D"mailto:=
internet-drafts@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">internet-drafts@ietf.=
org</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Sent: Friday, Marc=
h 21, 2014 10:11 PM<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; To: <a href=3D"mai=
lto:i-d-announce@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">i-d-announce@ietf.org=
</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Cc: <a href=3D"mai=
lto:clue@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">clue@ietf.org</span><=
/a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Subject: [clue] I-=
D Action: draft-ietf-clue-datachannel-00.txt<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; A New Internet-Dra=
ft is available from the on-line Internet-Drafts<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; directories.<o:p></o:p>=
</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp; This draft i=
s a work item of the ControLling mUltiple streams for<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; tElepresence Worki=
ng Group of the IETF.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; : CLUE Protocol Data Channel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; : Christer Holmberg<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Filename&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-ietf-clue-datachannel-00.txt<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Pages&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 12<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Date&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;: 2014-03-20<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Abstract:<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
This document defines how to use the WebRTC Data Channel<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; mechanism,<o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
together with the Data Channel Establishment Protocol (DCEP) in order<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
to establish a data channel, referred to as CLUE Data Channel, for<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp; &nbsp;=
transporting CLUE protocol messages between two CLUE entities.<o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
The document defines the SCTP considerations specific to a CLUE Data<o:p></=
o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
Channel, the SDP offer/answer procedures for negotiating the<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
establishment of, and the DCEP procedures for opening, a CLUE Data<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
Channel.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
Details and procedures associated with the CLUE protocol are outside<o:p></=
o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;&nbsp;&nbsp;&nbsp; =
the scope of this document.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; The IETF datatrack=
er status page for this draft is:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; <a href=3D"https:/=
/datatracker.ietf.org/doc/draft-ietf-clue-datachannel/">
<span style=3D"color:windowtext;text-decoration:none">https://datatracker.i=
etf.org/doc/draft-ietf-clue-datachannel/</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; There's also a htm=
lized version available at:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; <a href=3D"http://=
tools.ietf.org/html/draft-ietf-clue-datachannel-00">
<span style=3D"color:windowtext;text-decoration:none">http://tools.ietf.org=
/html/draft-ietf-clue-datachannel-00</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Please note that i=
t may take a couple of minutes from the time of<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; submission until t=
he htmlized version and diff are available at tools.ietf.org.<o:p></o:p></s=
pan></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; Internet-Drafts ar=
e also available by anonymous FTP at:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; <a href=3D"ftp://f=
tp.ietf.org/internet-drafts/">
<span style=3D"color:windowtext;text-decoration:none">ftp://ftp.ietf.org/in=
ternet-drafts/</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt;<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; __________________=
_____________________________<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; clue mailing list<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; <a href=3D"mailto:=
clue@ietf.org"><span style=3D"color:windowtext;text-decoration:none">clue@i=
etf.org</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt; &gt; <a href=3D"https:/=
/www.ietf.org/mailman/listinfo/clue">
<span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org/=
mailman/listinfo/clue</span></a><o:p></o:p></span></p>
</div>
</body>
</html>

--_000_E97C33E5D67C2843AFA535DE2E5B80C157402F4CSZXEMA503MBXchi_--


From nobody Thu Sep 18 02:36:38 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F9DC1A86FF for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 02:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level: 
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ZxCtldoH9AZ for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 02:36:29 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8B6D1A00D1 for <clue@ietf.org>; Thu, 18 Sep 2014 02:36:28 -0700 (PDT)
X-AuditID: c1b4fb25-f791c6d00000617b-0f-541aa77f30f9
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id B6.09.24955.F77AA145; Thu, 18 Sep 2014 11:36:00 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0174.001; Thu, 18 Sep 2014 11:35:59 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: [clue] Draft new version: clue-data-channel-01
Thread-Index: Ac/Q6P1eNDrLxC9JTsiySht2hyqOBQAUZKOAACUlsyD//+kIgP/+/UjwgAJU+gD//4khUIAA1kwA//7yoGA=
Date: Thu, 18 Sep 2014 09:35:58 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D450F17@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <54187495.5080501@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D44E68B@ESESSMB209.ericsson.se> <54199056.7050101@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D450478@ESESSMB209.ericsson.se> <5419E062.40507@alum.mit.edu>
In-Reply-To: <5419E062.40507@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyM+JvjW7DcqkQg9mPOS32n7rMbLFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugStj1omUguU6FdNP/mFuYNyp3MXIySEhYCLx dNpvNghbTOLCvfVgtpDAUUaJt/8duhi5gOwljBLHrl1n6WLk4GATsJDo/qcNUiMi4Cmx4+MU ZhBbWMBaouVgKytIiYiAjcSipZkQJUkSJ3/dYgWxWQRUJQ5s2cMIYvMK+ErM2jCJFWL8fGaJ be+6mEASnAJaEo37JoLdwAh0z/dTa8DizALiEreezGeCuFNAYsme88wQtqjEy8f/WCFsRYmP r/YxQtTrSCzY/YkNwtaWWLbwNTPEYkGJkzOfsExgFJ2FZOwsJC2zkLTMQtKygJFlFaNocWpx Um66kbFealFmcnFxfp5eXmrJJkZgjBzc8lt1B+PlN46HGAU4GJV4eBfYSIUIsSaWFVfmHmKU 5mBREuddeG5esJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQZGpV08GQVXgq68EtzC8nny+fsf zymULFjkua/6mpCJotVO70UdlhOEFyh4r9VqFRHtWDdha8ezXvkk36Q9cgdjTSwjmCeEzrBZ dmbh9a6SUKtd67aIX/wbPu+S1iMmiWIrgSlX/NVDvjJfMrhkv9/RyKPfYnLahoxP0c13dNkM Uz5/5Cps9b6mxFKckWioxVxUnAgANsPyA3ICAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/2Jw5Efg_j8SIRENwCpw0gk6BGJc
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 09:36:36 -0000

Hi,

>>>> But, one of my question (which is not specific to fallback) was: if=20
>>>> we associate the SCTP association >> with the CLUE group, would it be =
semantically correct to also use the SCTP association for non- CLUE purpose=
 (technically there is no problem)?
>>>
>>> If we want the possibility of sharing the use of the association then t=
his must be valid.
>>
>> I guess we could think about whether the SCTP association really needs t=
o be within the CLUE group.
>>
>> The main purpose of the CLUE group is to indicate which media is CLUE co=
ntrolled.
>>
>> Is it really that important to associate the SCTP association with the C=
LUE group? After all, what matters is whether you have established a CLUE d=
ata channel (using DCEP) on that SCTP association or not...
>
> I see no problem with including it in the clue group as long as we specif=
y what that means to us.
>
> I can think of at least two reasons why we want/need it in the clue group=
:
>
> 1) In the initial offer, it may be the *only* thing in the clue group. I =
think we need it to be clear we are clue enabled.

In my opinion, the media feature tag indicates that we support CLUE, and on=
ce you've established the CLUE data channel we have enabled clue.

> 2) If it happened that there were multiple SCTP associations, the clue gr=
oup is how we know which one is to contain the clue channel.

I was thinking about that, but I think that is a more generic problem, affe=
cting whatever protocol you are going to use on the data channel(s). Also, =
maybe you don't care on which SCTP association you open the CLUE channel.

Regards,

Christer





>>> If the sctp association is closed for some reason, and you want to rema=
in clue enabled, then you should:
>>> - send another offer including the sctp m-line in the clue group
>>> - start things up again
>>> - (I think you don't try to reestablish the association until
>>      the new offer is sent.)
>>
>> Regarding the last point, I guess that should be covered in the sctp-sdp=
 draft.
>
> I think this is implicitly inherited by SCTP from the definition of comed=
ia. (RFC4145). But it would probably be good to spell it out.
>
> At least for TCP, the issue is whether the app needs to maintain a=20
> listener for new connections after the initial connection has been=20
> established. (The mechanics for SCTP may be different, especially SCTP=20
> over DTLS, because it is an application layer stack rather than a=20
> socket
> interface.)
>
> 	Thanks,
> 	Paul
>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>> On 9/16/14 1:03 PM, Christer Holmberg wrote:
>>> Hi Christian,
>>>
>>> I am not sure I agree with what you are saying.
>>>
>>> Sure, we can use the grouping to indicate that the SCTPoDTLS associatio=
n will be used within a CLUE session.
>>>
>>> But, in order to open a data channel for CLUE, you need to use DCEP. Al=
so, in order to close a data channel for CLUE, you need to reset the STCPoD=
TLS association. Just removing the m=3D line from the CLUE group won't do t=
hat - and I am not even sure we should allow that.
>>>
>>> Also, if we use a mid attribute to associate the SCTPoDTLS association =
with CLUE, can we then also use it for non-CLUE protocol? Does not seem sem=
antically correct in my opinion.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>> -----Original Message-----
>>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian=20
>>> Groves
>>> Sent: 16 September 2014 04:13
>>> To: clue@ietf.org
>>> Subject: Re: [clue] Draft new version: clue-data-channel-01
>>>
>>> Hello Christer,
>>>
>>> Just a question on 5.7 where it says "If an offerer wants to disable th=
e CLUE Data Channel in an offer, it assigns a zero port value to the "m=3D"
>>> line representing the SCTPoDTLS association used to realize the CLUE Da=
ta channel."
>>>
>>> Wouldn't this have the effect of closing the SCTP/DTLS association caus=
ing CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to=
 be for a generic webrtc data channel. To have a "CLUE data channel" we use=
 the a=3Dgroup.
>>>
>>> i.e. Generic Data Channel
>>> m=3Dapplication 54111 SCTP/DTLS 54111
>>> a=3Dsctpmap:54111 webrtc-datachannel
>>>
>>> CLUE data channel
>>> a=3Dgroup:CLUE 100
>>> m=3Dapplication 54111 SCTP/DTLS 54111
>>> a=3Dsctpmap:54111 webrtc-datachannel
>>> a=3Dmid:100
>>>
>>> Therefore if an endpoint wanted to remove CLUE from the data channel (w=
ithout closing the SCTP/DTLS associated) it would remove the a=3Dgroup and =
a=3Dmid.
>>>
>>> There's also a typo in clause 5.7 "are unchanged" is repeated.
>>>
>>> Regards, Christian
>>>
>>> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>>>
>>>> Hi,
>>>>
>>>> I've submitted a new version of the CLUE data channel draft.
>>>>
>>>> The changes are mostly editorial: I structured the O/A procedures=20
>>>> according to 3264, and updated the references.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
>


From nobody Thu Sep 18 05:52:51 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1121A878C for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 05:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level: 
X-Spam-Status: No, score=-3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  HTML_MESSAGE=0.001, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6,  RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id abUVClL_5aAD for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 05:52:41 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59B1D1A02D5 for <clue@ietf.org>; Thu, 18 Sep 2014 05:52:40 -0700 (PDT)
X-AuditID: c1b4fb30-f79736d0000053b8-a8-541ad596ecda
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id C6.E8.21432.695DA145; Thu, 18 Sep 2014 14:52:38 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0174.001; Thu, 18 Sep 2014 14:52:37 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>
Thread-Topic: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
Thread-Index: AQHP0mk0GdjPYll8W0+041HOtHVL0pwFqq/wgAA5QgCAAPWlcA==
Date: Thu, 18 Sep 2014 12:52:37 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D451599@ESESSMB209.ericsson.se>
References: <20140321141121.16330.32657.idtracker@ietfa.amsl.com> <E97C33E5D67C2843AFA535DE2E5B80C1573A7DA6@SZXEMA503-MBX.china.huawei.com> <7594FB04B1934943A5C02806D1A2204B1D2EFC38@ESESSMB209.ericsson.se> <E97C33E5D67C2843AFA535DE2E5B80C157402EDC@SZXEMA503-MBX.china.huawei.com> <7594FB04B1934943A5C02806D1A2204B1D450449@ESESSMB209.ericsson.se> <E97C33E5D67C2843AFA535DE2E5B80C157402F4C@SZXEMA503-MBX.china.huawei.com>
In-Reply-To: <E97C33E5D67C2843AFA535DE2E5B80C157402F4C@SZXEMA503-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D451599ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnkeLIzCtJLcpLzFFi42KZGfG3RnfaVakQgx9n+C32n7rMbHHwRQuT A5NHy5G3rB5LlvxkCmCK4rJJSc3JLEst0rdL4Mq4PekuU8H8x0wV019dY2xgbN7N1MXIySEh YCLxqKEXyhaTuHBvPVsXIxeHkMBRRokvu68xQThLGCV+rvwOlOHgYBOwkOj+pw3SIALUfGTq W1YQm1lAWeJrwyawQcICThKr2l4yQ9Q4S7zYeIMdpFUEKP55jhhImEVAVeLHlYlg5bwCvhKn 205D7V3LLPHzezdYglMgTOLgiVcsIDYj0HHfT61hgtglLnHryXyoowUkluw5zwxhi0q8fPyP FcJWlPj4ah8jRH2+xIG/MxghlglKnJz5hGUCo+gsJKNmISmbhaQMIq4jsWD3JzYIW1ti2cLX zDD2mQOPmZDFFzCyr2IULU4tTspNNzLSSy3KTC4uzs/Ty0st2cQIjLmDW34b7GB8+dzxEKMA B6MSD+8CG6kQIdbEsuLK3EOM0hwsSuK8C8/NCxYSSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXA mPsoaI7vea+3aod4io9t7d6+YEPXya2vPedaPKivutycmVqyZ+anKdO2Kf+f5/v61Mnt37Y5 nT5uuWjzi2sLn+vkTrWY0vTFx/ylF9uEZdNv12SE7/4yR+0e54RUx86Wreu3bXvBu37Fp8UR e293fv/74sgX3jP2exsu8GiduJMZUJinsdV2st0EJZbijERDLeai4kQA61X1KpoCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/WGgmbW36fqi9EpChZlWyPSHVJW4
Cc: "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 12:52:46 -0000

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

Hi Scarlett,

I don't think we, in our draft, should fix bugs in other drafts. Instead we=
 should raise the bugs in the appropriate forum (in this case, MMUSIC).

Anyway, I am sitting a few meters from the sctp-sdp draft authors, and I ha=
ve informed them about this :)

Regards,

Christer


From: Liuyan (Scarlett) [mailto:scarlett.liuyan@huawei.com]
Sent: 18. syyskuuta 2014 3:12
To: Christer Holmberg
Cc: clue@ietf.org
Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt


Hi Christer,



         OK.

         By the way, there is also a typo in the example of draft-ietf-mmus=
ic-sctp-sdp-07 below.

         8.4.  SDP description for SCTP over DTLS Connection using default =
values

         m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel

          c=3DIN IP4 192.0.2.2

          a=3Dsetup:actpass

          a=3Dconnection:new

          a=3Dfingerprint:SHA-1 \

            4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB



                                 Figure 7



   The endpoint at 192.0.2.1 responds with the following description,

   with default value for the sctp-port and max-message-size parameters:



          m=3Dapplication 62442 DTLS/SCTP webrtc-datachannel

          c=3DIN IP4 192.0.2.1

          a=3Dsetup:actpass=3D=3D=3D=3D=3D=3D=3D=3D=3Dit should be passive

          a=3Dconnection:new

          a=3Dfingerprint:SHA-1 \

            4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB



                                 Figure 8

         If you refers to the examples, please notice that and thanks.



Best Regards,

Scarlett



> -----Original Message-----

> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]

> Sent: Thursday, September 18, 2014 2:48 AM

> To: Liuyan (Scarlett)

> Cc: clue@ietf.org<mailto:clue@ietf.org>

> Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt

>

> Hi Scarlett,

>

> I apologise that I forgot to fix the typo. I'll do it in the next version=
 :)

>

> I'll also try to keep the examples etc aligned with the sctp-sdp draft.

>

> Thanks for reminding me :)

>

> Regards,

>

> Christer

>

> -----Original Message-----

> From: Liuyan (Scarlett) [mailto:scarlett.liuyan@huawei.com]

> Sent: 17 September 2014 14:19

> To: Christer Holmberg

> Cc: clue@ietf.org<mailto:clue@ietf.org>

> Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt

>

> Hi Christer,

>

>      There is still a typo in the draft-ietf-clue-datachannel-01 and the =
typo

> was confirmed by you in the previous e-mail below .

>      Maybe you forgot it.

>      By the way, the draft-ietf-mmusic-sctp-sdp-07 says below:

>

>      4.1.1.  sctp-port

>

>        sctp-port-attr   =3D  "a=3Dsctp-port=3D" portnumber

>        port-number      =3D  port

>      4.1.2.  max-message-size

>

>     sctpmap-attr        =3D  "a=3Dfmtp:" association-usage

> [max-message-size]

>     max-message-size    =3D  "max-message-size" EQUALS 1*DIGIT

>

>      8.3.  SDP description for SCTP over DTLS Connection

>      m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel

>     a=3Dfmtp:webrtc-datachannel max-message-size=3D100000

>     a=3Dsctp-port 5000

>

>      At least ,I have a question.

>      Do you think that your example in the draft-ietf-clue-datachannel-01

> should keep the consistency with the example of

> draft-ietf-mmusic-sctp-sdp-07 ?

>

> Best Regards,

> Scarlett

>

> > -----Original Message-----

> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]

> > Sent: Wednesday, May 07, 2014 6:00 PM

> > To: Liuyan (Scarlett)

> > Cc: clue@ietf.org<mailto:clue@ietf.org>

> > Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt

> >

> > Hi Scarlett,

> >

> > Thanks for spotting the typo! :)

> >

> > Regards,

> >

> > Christer

> >

> > -----Original Message-----

> > From: Liuyan (Scarlett) [mailto:scarlett.liuyan@huawei.com]

> > Sent: 7. toukokuuta 2014 5:41

> > To: Christer Holmberg

> > Cc: clue@ietf.org<mailto:clue@ietf.org>

> > Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt

> >

> > Hi Christer,

> >

> >     I notice that there is a typo in section 5.6 of

> > draft-ietf-clue-datachannel-00 below:

> >

> >           5.6.  Example

> >

> >            m=3Dapplication 54111 SCTP/DTLS 54111

> >            a=3Dsctpmap:54111 webrtc-datachannel

> >

> >           Figure 1: SDP Media Description for a CLUE Data Channel

> >

> >    As described in section 3 of draft-ietf-mmusic-sctp-sdp-06 below:

> >

> >    The 'SCTP/DTLS' protocol identifier indicates that the media

> >    described will use the Datagram Transport Layer Security (DTLS)

> >    [RFC4347] over SCTP as specified in [RFC6083].

> >

> >    The 'DTLS/SCTP' protocol identifier indicates that the media

> >    described will use SCTP on top of the Datagram Transport Layer

> >    Security (DTLS) protocol as specified in

> >    [I-D.tuexen-tsvwg-sctp-dtls-encaps].  The actual layer below DTLS ca=
n

> >    be plain UDP or what ICE agrees on (in the case ICE is used to

> >    negotiate the actual transport flow).  The lower layer used is

> >    identified from the elements present inside the m=3D line block.

> >

> >    so it should be reworded below:

> >

> >     5.6.  Example

> >

> >            m=3Dapplication 54111 DTLS/SCTP 54111

> >            a=3Dsctpmap:54111 webrtc-datachannel

> >

> >           Figure 1: SDP Media Description for a CLUE Data Channel

> >

> > Best Regards,

> > Scarlett

> >

> > -----Original Message-----

> > From: clue [mailto:clue-bounces@ietf.org] On Behalf Of

> > internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>

> > Sent: Friday, March 21, 2014 10:11 PM

> > To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>

> > Cc: clue@ietf.org<mailto:clue@ietf.org>

> > Subject: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt

> >

> >

> > A New Internet-Draft is available from the on-line Internet-Drafts

> directories.

> >  This draft is a work item of the ControLling mUltiple streams for

> > tElepresence Working Group of the IETF.

> >

> >         Title           : CLUE Protocol Data Channel

> >         Author          : Christer Holmberg

> > Filename        : draft-ietf-clue-datachannel-00.txt

> > Pages           : 12

> > Date            : 2014-03-20

> >

> > Abstract:

> >    This document defines how to use the WebRTC Data Channel

> mechanism,

> >    together with the Data Channel Establishment Protocol (DCEP) in orde=
r

> >    to establish a data channel, referred to as CLUE Data Channel, for

> >    transporting CLUE protocol messages between two CLUE entities.

> >

> >    The document defines the SCTP considerations specific to a CLUE Data

> >    Channel, the SDP offer/answer procedures for negotiating the

> >    establishment of, and the DCEP procedures for opening, a CLUE Data

> >    Channel.

> >

> >    Details and procedures associated with the CLUE protocol are outside

> >    the scope of this document.

> >

> >

> > The IETF datatracker status page for this draft is:

> > https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/

> >

> > There's also a htmlized version available at:

> > http://tools.ietf.org/html/draft-ietf-clue-datachannel-00

> >

> >

> > Please note that it may take a couple of minutes from the time of

> > submission until the htmlized version and diff are available at tools.i=
etf.org.

> >

> > Internet-Drafts are also available by anonymous FTP at:

> > ftp://ftp.ietf.org/internet-drafts/

> >

> > _______________________________________________

> > clue mailing list

> > clue@ietf.org<mailto:clue@ietf.org>

> > https://www.ietf.org/mailman/listinfo/clue

--_000_7594FB04B1934943A5C02806D1A2204B1D451599ESESSMB209erics_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:9.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.a, li.a, div.a
	{mso-style-name:\7EAF\6587\672C;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
p.a0, li.a0, div.a0
	{mso-style-name:\6279\6CE8\6846\6587\672C;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char0
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 137.75pt 72.0pt 137.7pt;}
div.WordSection1
	{page:WordSection1;}
--></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=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Hi Sc=
arlett,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">I don=
&#8217;t think we, in our draft, should fix bugs in other drafts. Instead w=
e should raise the bugs in the appropriate forum (in this case, MMUSIC).<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Anywa=
y, I am sitting a few meters from the sctp-sdp draft authors, and I have in=
formed them about this :)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Regar=
ds,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Chris=
ter<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><b><span st=
yle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quo=
t;">From:</span></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahom=
a&quot;,&quot;sans-serif&quot;"> Liuyan (Scarlett) [mailto:scarlett.liuyan@=
huawei.com]
<br>
<b>Sent:</b> 18. syyskuuta 2014 3:12<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> clue@ietf.org<br>
<b>Subject:</b> RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt<o=
:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><o:p>&nbsp;=
</o:p></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">Hi Chr=
ister,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OK.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; By the way, there is also a typo=
 in the example of draft-ietf-mmusic-sctp-sdp-07 below.<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8.4.&nbsp; SDP description for S=
CTP over DTLS Connection using default values<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=3Dapplication 54111 DTLS/SCTP =
webrtc-datachannel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c=3DIN IP4 192.0.2.2<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style=3D"background:=
yellow;mso-highlight:yellow">
a=3Dsetup:actpass</span><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dconnection:new<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dfingerprint:SHA-1 \<o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4A:AD:B9:B1:3F=
:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Figure 7<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp; The endpoint at 192.0.2.1 responds with the following description,<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp; with default value for the sctp-port and max-message-size parameters=
:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=3Dapplication 62442 DTLS=
/SCTP webrtc-datachannel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c=3DIN IP4 192.0.2.1<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style=3D"background:=
yellow;mso-highlight:yellow">
a=3Dsetup:actpass</span>=3D=3D=3D=3D=3D=3D=3D=3D=3D<span style=3D"backgroun=
d:lime;mso-highlight:lime">it should be passive</span><o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dconnection:new<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Dfingerprint:SHA-1 \<o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4A:AD:B9:B1:3F=
:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Figure 8<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If you refers to the examples, p=
lease notice that and thanks.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">Best R=
egards,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">Scarle=
tt<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; -=
----Original Message-----<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; F=
rom: Christer Holmberg [<a href=3D"mailto:christer.holmberg@ericsson.com">m=
ailto:christer.holmberg@ericsson.com</a>]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; S=
ent: Thursday, September 18, 2014 2:48 AM<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; T=
o: Liuyan (Scarlett)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; C=
c: <a href=3D"mailto:clue@ietf.org">
clue@ietf.org</a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; S=
ubject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; H=
i Scarlett,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; I=
 apologise that I forgot to fix the typo. I'll do it in the next version :)=
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; I=
'll also try to keep the examples etc aligned with the sctp-sdp draft.<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; T=
hanks for reminding me :)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; R=
egards,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; C=
hrister<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; -=
----Original Message-----<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; F=
rom: Liuyan (Scarlett) [<a href=3D"mailto:scarlett.liuyan@huawei.com"><span=
 style=3D"color:windowtext;text-decoration:none">mailto:scarlett.liuyan@hua=
wei.com</span></a>]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; S=
ent: 17 September 2014 14:19<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; T=
o: Christer Holmberg<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; C=
c: <a href=3D"mailto:clue@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">clue@ietf.org</span><=
/a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; S=
ubject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-01.txt<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; H=
i Christer,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; There is still a typo in the draft-ietf-clue-datach=
annel-01 and the typo<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; w=
as confirmed by you in the previous e-mail below .<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; Maybe you forgot it.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; By the way, the draft-ietf-mmusic-sctp-sdp-07 says =
below:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; 4.1.1.&nbsp; sctp-port<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sctp-port-attr&nbsp;&nbsp; =3D&nbs=
p; &quot;a=3Dsctp-port=3D&quot; portnumber<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port-number&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =3D&nbsp; port<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; 4.1.2.&nbsp; max-message-size<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp;sctpmap-attr&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; =3D&nbsp; &quot;a=3Dfmtp:&quot; association-usage<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; [=
max-message-size]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp;max-message-size&nbsp;&nbsp;&nbsp; =3D&nbsp; &quot;m=
ax-message-size&quot; EQUALS 1*DIGIT<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; 8.3.&nbsp; SDP description for SCTP over DTLS Conne=
ction<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; m=3Dapplication 54111 DTLS/SCTP webrtc-datachannel<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp;a=3Dfmtp:webrtc-datachannel max-message-size=3D10000=
0<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp;a=3Dsctp-port 5000<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; At least ,I have a question.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
nbsp;&nbsp;&nbsp;&nbsp; Do you think that your example in the draft-ietf-cl=
ue-datachannel-01<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; s=
hould keep the consistency with the example of<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; d=
raft-ietf-mmusic-sctp-sdp-07 ?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; B=
est Regards,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; S=
carlett<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; <=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; -----Original Message-----<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; From: Christer Holmberg [<a href=3D"mailto:christer.holmberg@ericsson.c=
om"><span style=3D"color:windowtext;text-decoration:none">mailto:christer.h=
olmberg@ericsson.com</span></a>]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Sent: Wednesday, May 07, 2014 6:00 PM<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; To: Liuyan (Scarlett)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Cc: <a href=3D"mailto:clue@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">clue@ietf.org</span><=
/a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Hi Scarlett,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Thanks for spotting the typo! :)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Regards,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Christer<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; -----Original Message-----<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; From: Liuyan (Scarlett) [<a href=3D"mailto:scarlett.liuyan@huawei.com">=
<span style=3D"color:windowtext;text-decoration:none">mailto:scarlett.liuya=
n@huawei.com</span></a>]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Sent: 7. toukokuuta 2014 5:41<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; To: Christer Holmberg<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Cc: <a href=3D"mailto:clue@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">clue@ietf.org</span><=
/a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Subject: RE: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Hi Christer,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp; I notice that there is a typo in section 5.6 of=
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; draft-ietf-clue-datachannel-00 below:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5.6.&nbsp; =
Example<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=3Da=
pplication 54111 SCTP/DTLS 54111<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Ds=
ctpmap:54111 webrtc-datachannel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Figure 1: S=
DP Media Description for a CLUE Data Channel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; As described in section 3 of draft-ietf-mmusic-sctp-s=
dp-06 below:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; The 'SCTP/DTLS' protocol identifier indicates that th=
e media<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; described will use the Datagram Transport Layer Secur=
ity (DTLS)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; [RFC4347] over SCTP as specified in [RFC6083].<o:p></=
o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; The 'DTLS/SCTP' protocol identifier indicates that th=
e media<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; described will use SCTP on top of the Datagram Transp=
ort Layer<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; Security (DTLS) protocol as specified in<o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; [I-D.tuexen-tsvwg-sctp-dtls-encaps].&nbsp; The actual=
 layer below DTLS can<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; be plain UDP or what ICE agrees on (in the case ICE i=
s used to<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; negotiate the actual transport flow).&nbsp; The lower=
 layer used is<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; identified from the elements present inside the m=3D =
line block.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; so it should be reworded below:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp; 5.6.&nbsp; Example<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=3Da=
pplication 54111 DTLS/SCTP 54111<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Ds=
ctpmap:54111 webrtc-datachannel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Figure 1: S=
DP Media Description for a CLUE Data Channel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Best Regards,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Scarlett<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; -----Original Message-----<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; From: clue [<a href=3D"mailto:clue-bounces@ietf.org"><span style=3D"col=
or:windowtext;text-decoration:none">mailto:clue-bounces@ietf.org</span></a>=
] On Behalf Of<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; <a href=3D"mailto:internet-drafts@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">internet-drafts@ietf.=
org</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Sent: Friday, March 21, 2014 10:11 PM<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; To: <a href=3D"mailto:i-d-announce@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">i-d-announce@ietf.org=
</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Cc: <a href=3D"mailto:clue@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">clue@ietf.org</span><=
/a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Subject: [clue] I-D Action: draft-ietf-clue-datachannel-00.txt<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; A New Internet-Draft is available from the on-line Internet-Drafts<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; d=
irectories.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp; This draft is a work item of the ControLling mUltiple streams for=
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; tElepresence Working Group of the IETF.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : CLUE Protocol Data Channel<o:p=
></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Christer Holmberg<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-ietf-clue-da=
tachannel-00.txt<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 12<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;=
: 2014-03-20<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Abstract:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; This document defines how to use the WebRTC Data Chan=
nel<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; m=
echanism,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; together with the Data Channel Establishment Protocol=
 (DCEP) in order<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; to establish a data channel, referred to as CLUE Data=
 Channel, for<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp; &nbsp;transporting CLUE protocol messages between two CLUE =
entities.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; The document defines the SCTP considerations specific=
 to a CLUE Data<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; Channel, the SDP offer/answer procedures for negotiat=
ing the<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; establishment of, and the DCEP procedures for opening=
, a CLUE Data<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; Channel.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; Details and procedures associated with the CLUE proto=
col are outside<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;&nbsp;&nbsp;&nbsp; the scope of this document.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; The IETF datatracker status page for this draft is:<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel=
/">
<span style=3D"color:windowtext;text-decoration:none">https://datatracker.i=
etf.org/doc/draft-ietf-clue-datachannel/</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; There's also a htmlized version available at:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-clue-datachannel-00">
<span style=3D"color:windowtext;text-decoration:none">http://tools.ietf.org=
/html/draft-ietf-clue-datachannel-00</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Please note that it may take a couple of minutes from the time of<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; submission until the htmlized version and diff are available at tools.i=
etf.org.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; Internet-Drafts are also available by anonymous FTP at:<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/">
<span style=3D"color:windowtext;text-decoration:none">ftp://ftp.ietf.org/in=
ternet-drafts/</span></a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; _______________________________________________<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; clue mailing list<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; <a href=3D"mailto:clue@ietf.org">
<span style=3D"color:windowtext;text-decoration:none">clue@ietf.org</span><=
/a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-fareast-language:ZH-CN">&gt; &=
gt; <a href=3D"https://www.ietf.org/mailman/listinfo/clue">
<span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org/=
mailman/listinfo/clue</span></a><o:p></o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D451599ESESSMB209erics_--


From nobody Thu Sep 18 10:25:16 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39CAC1A04D2 for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 10:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level: 
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9FtpjZdVY7k for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 10:25:08 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 839751A046C for <clue@ietf.org>; Thu, 18 Sep 2014 10:24:15 -0700 (PDT)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta02.westchester.pa.mail.comcast.net with comcast id sgxd1o00516LCl051hQEmF; Thu, 18 Sep 2014 17:24:14 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta06.westchester.pa.mail.comcast.net with comcast id shQE1o00P3Ge9ey3ShQE1f; Thu, 18 Sep 2014 17:24:14 +0000
Message-ID: <541B153E.3010301@alum.mit.edu>
Date: Thu, 18 Sep 2014 13:24:14 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "clue@ietf.org" <clue@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <54187495.5080501@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D44E68B@ESESSMB209.ericsson.se> <54199056.7050101@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D450478@ESESSMB209.ericsson.se> <5419E062.40507@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D450F17@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D450F17@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1411061054; bh=ehCWqt2dzxt1VgcanezduA/AyGFFbB2ZW8y4Uw5KiXs=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=WjcktKJ5SUClstwsCs7uQybQvGMG5rFyvB/G+u0ORBnh92LPEdFQTsZfImBOnHBaa olhClxzCvRmdgXXK7OWzUEAIRvcGhbnCc0rYao7vYVEp5mG893J+F5sXawDDPLBmZr ItCfRxBiSJs5qtL1ZSQeRdWBf9YKZd9GgOoFVFtlDb5PGhkD51CVsEj3af3nHv6Et3 SqiOb+uguPTv+5lnbobKMblCF2/WNp4xdxfUt/1Ye2q/4abUS0nTEuOxsTUYDWaUVR OsQoHS46WzE9UmqA0mt3x6Mv+P198jqsEI2mXdBNkTBn6qu8Fb0TAtHDmV6V+waUHi mjCW/xNDthpTQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/Ry-U6lmNoOrVsgeJW1UeykLr794
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 17:25:11 -0000

On 9/18/14 5:35 AM, Christer Holmberg wrote:
> Hi,
>
>>>>> But, one of my question (which is not specific to fallback) was: if
>>>>> we associate the SCTP association >> with the CLUE group, would it be semantically correct to also use the SCTP association for non- CLUE purpose (technically there is no problem)?
>>>>
>>>> If we want the possibility of sharing the use of the association then this must be valid.
>>>
>>> I guess we could think about whether the SCTP association really needs to be within the CLUE group.
>>>
>>> The main purpose of the CLUE group is to indicate which media is CLUE controlled.
>>>
>>> Is it really that important to associate the SCTP association with the CLUE group? After all, what matters is whether you have established a CLUE data channel (using DCEP) on that SCTP association or not...
>>
>> I see no problem with including it in the clue group as long as we specify what that means to us.
>>
>> I can think of at least two reasons why we want/need it in the clue group:
>>
>> 1) In the initial offer, it may be the *only* thing in the clue group. I think we need it to be clear we are clue enabled.
>
> In my opinion, the media feature tag indicates that we support CLUE, and once you've established the CLUE data channel we have enabled clue.

The media feature tag indicates that you have the *capability* to do 
CLUE. It doesn't indicate that you want to do it.

The discussion we had on Tuesday indicates the importance of having a 
way to signal that an SCTP association being offered it intended to be 
used to *enable* clue.

>> 2) If it happened that there were multiple SCTP associations, the clue group is how we know which one is to contain the clue channel.
>
> I was thinking about that, but I think that is a more generic problem, affecting whatever protocol you are going to use on the data channel(s). Also, maybe you don't care on which SCTP association you open the CLUE channel.

The other protocols aren't our problem.
The clue group solves it for CLUE. Others can use a similar approach if 
they want, or do something else.

	Thanks,
	Paul

> Regards,
>
> Christer
>
>
>
>
>
>>>> If the sctp association is closed for some reason, and you want to remain clue enabled, then you should:
>>>> - send another offer including the sctp m-line in the clue group
>>>> - start things up again
>>>> - (I think you don't try to reestablish the association until
>>>       the new offer is sent.)
>>>
>>> Regarding the last point, I guess that should be covered in the sctp-sdp draft.
>>
>> I think this is implicitly inherited by SCTP from the definition of comedia. (RFC4145). But it would probably be good to spell it out.
>>
>> At least for TCP, the issue is whether the app needs to maintain a
>> listener for new connections after the initial connection has been
>> established. (The mechanics for SCTP may be different, especially SCTP
>> over DTLS, because it is an application layer stack rather than a
>> socket
>> interface.)
>>
>> 	Thanks,
>> 	Paul
>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>
>>>
>>> On 9/16/14 1:03 PM, Christer Holmberg wrote:
>>>> Hi Christian,
>>>>
>>>> I am not sure I agree with what you are saying.
>>>>
>>>> Sure, we can use the grouping to indicate that the SCTPoDTLS association will be used within a CLUE session.
>>>>
>>>> But, in order to open a data channel for CLUE, you need to use DCEP. Also, in order to close a data channel for CLUE, you need to reset the STCPoDTLS association. Just removing the m= line from the CLUE group won't do that - and I am not even sure we should allow that.
>>>>
>>>> Also, if we use a mid attribute to associate the SCTPoDTLS association with CLUE, can we then also use it for non-CLUE protocol? Does not seem semantically correct in my opinion.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>> -----Original Message-----
>>>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian
>>>> Groves
>>>> Sent: 16 September 2014 04:13
>>>> To: clue@ietf.org
>>>> Subject: Re: [clue] Draft new version: clue-data-channel-01
>>>>
>>>> Hello Christer,
>>>>
>>>> Just a question on 5.7 where it says "If an offerer wants to disable the CLUE Data Channel in an offer, it assigns a zero port value to the "m="
>>>> line representing the SCTPoDTLS association used to realize the CLUE Data channel."
>>>>
>>>> Wouldn't this have the effect of closing the SCTP/DTLS association causing CLUE AND any other protocols to be disabled? Clause 5.7 and 5.8 seem to be for a generic webrtc data channel. To have a "CLUE data channel" we use the a=group.
>>>>
>>>> i.e. Generic Data Channel
>>>> m=application 54111 SCTP/DTLS 54111
>>>> a=sctpmap:54111 webrtc-datachannel
>>>>
>>>> CLUE data channel
>>>> a=group:CLUE 100
>>>> m=application 54111 SCTP/DTLS 54111
>>>> a=sctpmap:54111 webrtc-datachannel
>>>> a=mid:100
>>>>
>>>> Therefore if an endpoint wanted to remove CLUE from the data channel (without closing the SCTP/DTLS associated) it would remove the a=group and a=mid.
>>>>
>>>> There's also a typo in clause 5.7 "are unchanged" is repeated.
>>>>
>>>> Regards, Christian
>>>>
>>>> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I've submitted a new version of the CLUE data channel draft.
>>>>>
>>>>> The changes are mostly editorial: I structured the O/A procedures
>>>>> according to 3264, and updated the references.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Christer
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> clue mailing list
>>>>> clue@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>
>>
>
>


From nobody Thu Sep 18 17:10:40 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1D4E1A0B10 for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 17:10:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.799
X-Spam-Level: *
X-Spam-Status: No, score=1.799 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQhId3GA8oP7 for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 17:10:35 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDF4B1A02F2 for <clue@ietf.org>; Thu, 18 Sep 2014 17:10:34 -0700 (PDT)
Received: from ppp118-209-249-195.lns20.mel8.internode.on.net ([118.209.249.195]:51619 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XUlkF-0002pk-Nl for clue@ietf.org; Fri, 19 Sep 2014 10:08:15 +1000
Message-ID: <541B7473.5090709@nteczone.com>
Date: Fri, 19 Sep 2014 10:10:27 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com> <5418E5F4.7040204@nteczone.com> <54194F5E.3020205@cisco.com>
In-Reply-To: <54194F5E.3020205@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/bf5-4ZZdgSdJGAJtXDiUvWZ_6Tg
Subject: Re: [clue] Notes from design team meeting re: signaling open issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 00:10:38 -0000

Hello Rob,

With respect to 3), I guess there's two points at which the video could 
stop. Actual closure of the CLUE SCTP streams through the data channel 
reset procedure, or once the updated SDP is received. I guess the actual 
trigger is the closure of the CLUE stream rather than the reception of 
the SDP.

Christian

On 17/09/2014 7:07 PM, Robert Hansen wrote:
> 1) Yes
> 2) Yes
> 3) No. At present, the proposal is that by removing the SCTP 
> association from the CLUE group the call is no longer CLUE-enabled. 
> However, because the CLUE group is still present and still contains 
> the video that video is still CLUE-controlled and hence can't be sent 
> under these conditions.
> 4) Yes
>
> Rob
>
> On 17/09/14 02:37, Christian Groves wrote:
>>
>> I just want to make sure I understand what was being proposed for 
>> fallback of CLUE media streams. I'm going to try to avoid the use of 
>> "CLUE enabled" and "CLUE capable" and focus on the SDP and what it 
>> means.
>>
>> Consider the following SDP where a CLUE controlled video stream has 
>> been configured, established and everything is awesome :-).
>>
>>       a=group:CLUE 1 2
>>       m=application 6100 SCTP/DTLS 6100
>>       a=sctpmap:1 webrtc-datachannel
>>       a=mid:1
>>       ...
>>       m=video 6004 RTP/AVP 96
>>       a=rtpmap:96 H264/90000
>>       a=fmtp:96 profile-level-id=42e016
>>       a=sendonly
>>       a=mid:2
>>       a=label:enc1
>>
>> Case 1) The SDP is updated to remove mid:2 effectively removing the 
>> video stream from CLUE control. However a=sendonly remains, i.e.
>>       a=group:CLUE 1
>>       m=application 6100 SCTP/DTLS 6100
>>       a=sctpmap:1 webrtc-datachannel
>>       a=mid:1
>>       ...
>>       m=video 6004 RTP/AVP 96
>>       a=rtpmap:96 H264/90000
>>       a=fmtp:96 profile-level-id=42e016
>>       a=sendonly
>>
>> My assumption is that video continues to flow because the media 
>> stream is no longer under CLUE control (thus rules regarding 
>> configuring don't apply) and the sending direction is still send 
>> only. However as its not part of a CLUE group anymore any previously 
>> Advertised CLUEinfo regarding the video stream is no longer valid.
>>
>> Case 2) The SDP is updated to remove mid:2 effectively removing the 
>> video stream from CLUE control the endpoint wants to stop the stream. 
>> My assumption is that to stop sending the video media stream either 
>> the port has to be changed to zero or a=inactive is set. Any CLUE 
>> info regarding the stream is discarded.
>>
>> Case 3) The SDP is updated to remove mid:1 effectively closing the 
>> CLUE channel. However the video stream remain in the CLUE group, e.g.
>>       a=group:CLUE 2
>>       m=application 6100 SCTP/DTLS 6100
>>       a=sctpmap:1 webrtc-datachannel
>>       ...
>>       m=video 6004 RTP/AVP 96
>>       a=rtpmap:96 H264/90000
>>       a=fmtp:96 profile-level-id=42e016
>>       a=sendonly
>>       a=mid:2
>>       a=label:enc1
>> My assumption is that the video stream continues unchanged and as its 
>> still in a CLUE group any advertised CLUEinfo is still valid for the 
>> stream.
>>
>> Case 4) To remove the CLUE protocol and media channels the CLUE group 
>> should be removed and the media line zeroed/made inactive, e.g.
>>       m=application 6100 SCTP/DTLS 6100
>>       a=sctpmap:1 webrtc-datachannel
>>       ...
>>       m=video 0 RTP/AVP 96
>>
>> Rob is that what you were proposing?
>>
>> Regards, Christian
>>
>> On 16/09/2014 11:45 PM, Duckworth, Mark wrote:
>>>
>>> Here are my notes from the design team meeting.
>>>
>>> CLUE signaling design team meeting
>>>
>>> Sep 16, 2014
>>>
>>> Rob Hansen, Mary Barnes, Paul Kyzivat, Mark Duckworth, Christian 
>>> Groves, Roberta Presta, Roni Even, Jonathan Lennox
>>>
>>> Rob discussed issues
>>>
>>> ·Fallback to non-CLUE - when does it happen?
>>>
>>> osignalling document has a proposal that defines when this happens, 
>>> but there are other ideas
>>>
>>> oRob's idea (in the signaling doc) is to use the same criteria to 
>>> enable CLUE as to disable it
>>>
>>> oIf data channel connection is lost, probably don't want that to 
>>> mean the call is not CLUE enabled any more
>>>
>>> oThe group agrees with Rob's proposal
>>>
>>> ·Fallback to non-CLUE - what does it mean?
>>>
>>> oWhen fallback to non CLUE-enabled occurs, then CLUE-controlled 
>>> media stops.
>>>
>>> osome other details about handling data channel and CLUE protocol 
>>> should be defined
>>>
>>> oShould close the CLUE channel.  Can keep SCTP open if it is used 
>>> for other things.
>>>
>>> ·When making an SDP offer, if the offerer wants to enable CLUE then 
>>> SDP should indicate this.  Even if previous O/A exchanges have not 
>>> enabled CLUE.  This is consistent with an offerer always including 
>>> video if it wants to add video to an audio call.
>>>
>>> ·Security issues
>>>
>>> oMary made suggestions
>>>
>>> oThis doc shouldn't have a heavy security section.  Using existing 
>>> protocols.
>>>
>>> oJonathan suggested mention case of SDP and SCTP going to different 
>>> addresses, one is attacker one is victim?
>>>
>>> oMary plans to get a security review done during WGLC
>>>
>>>
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Thu Sep 18 17:18:59 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B01D1A0B75 for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 17:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kG0NcYi0bOje for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 17:18:51 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD81D1A070F for <clue@ietf.org>; Thu, 18 Sep 2014 17:18:50 -0700 (PDT)
Received: from ppp118-209-249-195.lns20.mel8.internode.on.net ([118.209.249.195]:51720 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XUlsG-0004OR-Vi for clue@ietf.org; Fri, 19 Sep 2014 10:16:33 +1000
Message-ID: <541B7664.6040400@nteczone.com>
Date: Fri, 19 Sep 2014 10:18:44 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D44B7EE@ESESSMB209.ericsson.se> <54178E8F.8090809@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D44DE63@ESESSMB209.ericsson.se> <5418E00E.4060207@nteczone.com> <541991D8.9070009@alum.mit.edu>
In-Reply-To: <541991D8.9070009@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/FmCQ8aF638FnYdognfF52BVrMyE
Subject: Re: [clue] Draft new version: clue-data-channel-01
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 00:18:52 -0000

Hello Paul,

I wasn't proposing updated terminology. I was just trying to illustrate 
the issue to Christer and he seems to have understood me.

Regards, Christian

On 17/09/2014 11:51 PM, Paul Kyzivat wrote:
> On 9/16/14 9:12 PM, Christian Groves wrote:
>> Hello Christer,
>>
>> I think Paul has covered the issue with regards to fall back. We have to
>> distinguish between the overall data channel and the resultant streams
>> being used for CLUE.
>
> We need to use terminology consistently. In your sentence above you 
> mention "overall data channel". I infer you are talking about the SCTP 
> association. IMO it is inappropriate to refer to that as a data channel.
>
> IIUC a data channel is a pair of SCTP streams, one in each direction, 
> while the only term for the collection of all of the streams is SCTP 
> association.
>
>     Thanks,
>     Paul
>
>> DCEP doesn't open the overall SCTP/DTLS association
>> it establishes a protocol on a certain stream/s. Closure is done by
>> resetting the stream (see clause 6.7/draft-ietf-rtcweb-data-channel-11)
>> not by resetting the whole SCTP/DTLS association.
>>
>> With regards to the SCTP/DTLS association my understanding of the WebRTC
>> datachannel is that you can use several application protocols within
>> that association, i.e. CLUE and say BFCP. I think think we can say that
>> an SCTP/DTLS association must only contain CLUE. I think its valid to
>> use an mid in multiple groups. RFC5888 clause 6 says "An "m" line
>> identified by its "mid" attribute MAY appear in more than one "a=group"
>> line."
>>
>> Regards, Christian
>>
>> On 17/09/2014 3:03 AM, Christer Holmberg wrote:
>>> Hi Christian,
>>>
>>> I am not sure I agree with what you are saying.
>>>
>>> Sure, we can use the grouping to indicate that the SCTPoDTLS
>>> association will be used within a CLUE session.
>>>
>>> But, in order to open a data channel for CLUE, you need to use DCEP.
>>> Also, in order to close a data channel for CLUE, you need to reset the
>>> STCPoDTLS association. Just removing the m= line from the CLUE group
>>> won't do that - and I am not even sure we should allow that.
>>>
>>> Also, if we use a mid attribute to associate the SCTPoDTLS association
>>> with CLUE, can we then also use it for non-CLUE protocol? Does not
>>> seem semantically correct in my opinion.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>> -----Original Message-----
>>> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christian Groves
>>> Sent: 16 September 2014 04:13
>>> To: clue@ietf.org
>>> Subject: Re: [clue] Draft new version: clue-data-channel-01
>>>
>>> Hello Christer,
>>>
>>> Just a question on 5.7 where it says "If an offerer wants to disable
>>> the CLUE Data Channel in an offer, it assigns a zero port value to the
>>> "m="
>>> line representing the SCTPoDTLS association used to realize the CLUE
>>> Data channel."
>>>
>>> Wouldn't this have the effect of closing the SCTP/DTLS association
>>> causing CLUE AND any other protocols to be disabled? Clause 5.7 and
>>> 5.8 seem to be for a generic webrtc data channel. To have a "CLUE data
>>> channel" we use the a=group.
>>>
>>> i.e. Generic Data Channel
>>> m=application 54111 SCTP/DTLS 54111
>>> a=sctpmap:54111 webrtc-datachannel
>>>
>>> CLUE data channel
>>> a=group:CLUE 100
>>> m=application 54111 SCTP/DTLS 54111
>>> a=sctpmap:54111 webrtc-datachannel
>>> a=mid:100
>>>
>>> Therefore if an endpoint wanted to remove CLUE from the data channel
>>> (without closing the SCTP/DTLS associated) it would remove the a=group
>>> and a=mid.
>>>
>>> There's also a typo in clause 5.7 "are unchanged" is repeated.
>>>
>>> Regards, Christian
>>>
>>> On 15/09/2014 11:29 PM, Christer Holmberg wrote:
>>>> Hi,
>>>>
>>>> I've submitted a new version of the CLUE data channel draft.
>>>>
>>>> The changes are mostly editorial: I structured the O/A procedures
>>>> according to 3264, and updated the references.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Thu Sep 18 21:02:15 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE611A9168 for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 21:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bpsDKSgyjoEe for <clue@ietfa.amsl.com>; Thu, 18 Sep 2014 21:02:09 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DEA91A9153 for <clue@ietf.org>; Thu, 18 Sep 2014 21:02:09 -0700 (PDT)
Received: from ppp118-209-249-195.lns20.mel8.internode.on.net ([118.209.249.195]:53926 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XUpMK-0002vl-K0 for clue@ietf.org; Fri, 19 Sep 2014 13:59:48 +1000
Message-ID: <541BAAB9.5000504@nteczone.com>
Date: Fri, 19 Sep 2014 14:02:01 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "clue@ietf.org" <clue@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/aqqE_ezjMP9CtDEFzbHxwQdevO4
Subject: [clue] Question of deactivation scenario
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 04:02:13 -0000

I want to see if people have a common understanding of an re-ADV 
removing a media capture. Consider a scenario where an audio and two 
video captures have been Advertised, Configured and the SDP has been 
provided. Media is flowing.

The Media Provider for some reason decides that one of the video media 
captures is no longer available and sends an updated Advertisement 
removing the video capture.

Q1. Does the Media Consumer need to send an updated Configure message? I 
assume not as if the MP is not Advertising a media capture there's 
little else the MC can do but accept the removal.

Q2. I assume that it wouldn't matter at what stage the MP stops sending 
the media e.g. before the re-Advertisement, after the re-Advertisement 
or after the updated SIP-reinvite moving the media stream? Again there's 
little the MP could do to influence this.

Regards, Christian


From nobody Fri Sep 19 08:23:12 2014
Return-Path: <rohanse2@cisco.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4701A002B for <clue@ietfa.amsl.com>; Fri, 19 Sep 2014 08:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.353
X-Spam-Level: 
X-Spam-Status: No, score=-14.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id opOiTI6tU814 for <clue@ietfa.amsl.com>; Fri, 19 Sep 2014 08:23:08 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC3AE1A0009 for <clue@ietf.org>; Fri, 19 Sep 2014 08:23:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6168; q=dns/txt; s=iport; t=1411140188; x=1412349788; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=zkybjgSae8m8KUaHZ6Pf5pTZykiWmFJFnQ2ldPlqTMs=; b=f9ukJW3IrA6zE94LU4VxRkkF1HbLKlN827RgwR7WOTX7GHpCK7WbsjiJ cbIFwnwMjMZijSCcUIga9xkMiHhzA2ua+azAtNr57sxf2KlkNUOpsWv4d PnWaUYjuKLZbY8hIxX/D4hn3FKiVM/WtkEAwiOJadM2JbUUOZS03H70RG A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlQKADlJHFStJssW/2dsb2JhbABgg2BXtT8FAXKTNgqHTQGBGAF5hAQBAQQBAQEvAQU2ChELGAkWDwkDAgECARUwEwYCAQGIOg3DMgETBIMQgnuJfYRLAQSdE4dMjgKDYDwvgkoBAQE
X-IronPort-AV: E=Sophos;i="5.04,555,1406592000"; d="scan'208";a="178455134"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 19 Sep 2014 15:23:05 +0000
Received: from [10.47.200.91] ([10.47.200.91]) (authenticated bits=0) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s8JFN4oU013975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <clue@ietf.org>; Fri, 19 Sep 2014 15:23:05 GMT
Message-ID: <541C4A5B.9050804@cisco.com>
Date: Fri, 19 Sep 2014 16:23:07 +0100
From: Robert Hansen <rohanse2@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com> <5418E5F4.7040204@nteczone.com> <54194F5E.3020205@cisco.com> <541B7473.5090709@nteczone.com>
In-Reply-To: <541B7473.5090709@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: rohanse2
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/gTohpuvxFkvd-BE2gl5JddUF0GQ
Subject: Re: [clue] Notes from design team meeting re: signaling open issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 15:23:10 -0000

I would say that the answer is whichever happens first.

Rob

On 19/09/14 01:10, Christian Groves wrote:
> Hello Rob,
>
> With respect to 3), I guess there's two points at which the video 
> could stop. Actual closure of the CLUE SCTP streams through the data 
> channel reset procedure, or once the updated SDP is received. I guess 
> the actual trigger is the closure of the CLUE stream rather than the 
> reception of the SDP.
>
> Christian
>
> On 17/09/2014 7:07 PM, Robert Hansen wrote:
>> 1) Yes
>> 2) Yes
>> 3) No. At present, the proposal is that by removing the SCTP 
>> association from the CLUE group the call is no longer CLUE-enabled. 
>> However, because the CLUE group is still present and still contains 
>> the video that video is still CLUE-controlled and hence can't be sent 
>> under these conditions.
>> 4) Yes
>>
>> Rob
>>
>> On 17/09/14 02:37, Christian Groves wrote:
>>>
>>> I just want to make sure I understand what was being proposed for 
>>> fallback of CLUE media streams. I'm going to try to avoid the use of 
>>> "CLUE enabled" and "CLUE capable" and focus on the SDP and what it 
>>> means.
>>>
>>> Consider the following SDP where a CLUE controlled video stream has 
>>> been configured, established and everything is awesome :-).
>>>
>>>       a=group:CLUE 1 2
>>>       m=application 6100 SCTP/DTLS 6100
>>>       a=sctpmap:1 webrtc-datachannel
>>>       a=mid:1
>>>       ...
>>>       m=video 6004 RTP/AVP 96
>>>       a=rtpmap:96 H264/90000
>>>       a=fmtp:96 profile-level-id=42e016
>>>       a=sendonly
>>>       a=mid:2
>>>       a=label:enc1
>>>
>>> Case 1) The SDP is updated to remove mid:2 effectively removing the 
>>> video stream from CLUE control. However a=sendonly remains, i.e.
>>>       a=group:CLUE 1
>>>       m=application 6100 SCTP/DTLS 6100
>>>       a=sctpmap:1 webrtc-datachannel
>>>       a=mid:1
>>>       ...
>>>       m=video 6004 RTP/AVP 96
>>>       a=rtpmap:96 H264/90000
>>>       a=fmtp:96 profile-level-id=42e016
>>>       a=sendonly
>>>
>>> My assumption is that video continues to flow because the media 
>>> stream is no longer under CLUE control (thus rules regarding 
>>> configuring don't apply) and the sending direction is still send 
>>> only. However as its not part of a CLUE group anymore any previously 
>>> Advertised CLUEinfo regarding the video stream is no longer valid.
>>>
>>> Case 2) The SDP is updated to remove mid:2 effectively removing the 
>>> video stream from CLUE control the endpoint wants to stop the 
>>> stream. My assumption is that to stop sending the video media stream 
>>> either the port has to be changed to zero or a=inactive is set. Any 
>>> CLUE info regarding the stream is discarded.
>>>
>>> Case 3) The SDP is updated to remove mid:1 effectively closing the 
>>> CLUE channel. However the video stream remain in the CLUE group, e.g.
>>>       a=group:CLUE 2
>>>       m=application 6100 SCTP/DTLS 6100
>>>       a=sctpmap:1 webrtc-datachannel
>>>       ...
>>>       m=video 6004 RTP/AVP 96
>>>       a=rtpmap:96 H264/90000
>>>       a=fmtp:96 profile-level-id=42e016
>>>       a=sendonly
>>>       a=mid:2
>>>       a=label:enc1
>>> My assumption is that the video stream continues unchanged and as 
>>> its still in a CLUE group any advertised CLUEinfo is still valid for 
>>> the stream.
>>>
>>> Case 4) To remove the CLUE protocol and media channels the CLUE 
>>> group should be removed and the media line zeroed/made inactive, e.g.
>>>       m=application 6100 SCTP/DTLS 6100
>>>       a=sctpmap:1 webrtc-datachannel
>>>       ...
>>>       m=video 0 RTP/AVP 96
>>>
>>> Rob is that what you were proposing?
>>>
>>> Regards, Christian
>>>
>>> On 16/09/2014 11:45 PM, Duckworth, Mark wrote:
>>>>
>>>> Here are my notes from the design team meeting.
>>>>
>>>> CLUE signaling design team meeting
>>>>
>>>> Sep 16, 2014
>>>>
>>>> Rob Hansen, Mary Barnes, Paul Kyzivat, Mark Duckworth, Christian 
>>>> Groves, Roberta Presta, Roni Even, Jonathan Lennox
>>>>
>>>> Rob discussed issues
>>>>
>>>> ·Fallback to non-CLUE - when does it happen?
>>>>
>>>> osignalling document has a proposal that defines when this happens, 
>>>> but there are other ideas
>>>>
>>>> oRob's idea (in the signaling doc) is to use the same criteria to 
>>>> enable CLUE as to disable it
>>>>
>>>> oIf data channel connection is lost, probably don't want that to 
>>>> mean the call is not CLUE enabled any more
>>>>
>>>> oThe group agrees with Rob's proposal
>>>>
>>>> ·Fallback to non-CLUE - what does it mean?
>>>>
>>>> oWhen fallback to non CLUE-enabled occurs, then CLUE-controlled 
>>>> media stops.
>>>>
>>>> osome other details about handling data channel and CLUE protocol 
>>>> should be defined
>>>>
>>>> oShould close the CLUE channel.  Can keep SCTP open if it is used 
>>>> for other things.
>>>>
>>>> ·When making an SDP offer, if the offerer wants to enable CLUE then 
>>>> SDP should indicate this.  Even if previous O/A exchanges have not 
>>>> enabled CLUE.  This is consistent with an offerer always including 
>>>> video if it wants to add video to an audio call.
>>>>
>>>> ·Security issues
>>>>
>>>> oMary made suggestions
>>>>
>>>> oThis doc shouldn't have a heavy security section.  Using existing 
>>>> protocols.
>>>>
>>>> oJonathan suggested mention case of SDP and SCTP going to different 
>>>> addresses, one is attacker one is victim?
>>>>
>>>> oMary plans to get a security review done during WGLC
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Fri Sep 19 09:55:04 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA0BC1A0338 for <clue@ietfa.amsl.com>; Fri, 19 Sep 2014 09:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.565
X-Spam-Level: 
X-Spam-Status: No, score=0.565 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuQQ1yyh0a2k for <clue@ietfa.amsl.com>; Fri, 19 Sep 2014 09:55:01 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2030C1A0332 for <clue@ietf.org>; Fri, 19 Sep 2014 09:55:00 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by resqmta-ch2-02v.sys.comcast.net with comcast id t4dR1o0010bG4ec014v0gl; Fri, 19 Sep 2014 16:55:00 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta03.westchester.pa.mail.comcast.net with comcast id t4uz1o00J3Ge9ey3P4uzzB; Fri, 19 Sep 2014 16:55:00 +0000
Message-ID: <541C5FE3.5060502@alum.mit.edu>
Date: Fri, 19 Sep 2014 12:54:59 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com> <5418E5F4.7040204@nteczone.com> <54194F5E.3020205@cisco.com> <541B7473.5090709@nteczone.com> <541C4A5B.9050804@cisco.com>
In-Reply-To: <541C4A5B.9050804@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1411145700; bh=DdQ5FSdn8HK/5bZMNWeFnEqkqENUrwVK0YmnpHvn66o=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=vCle0QGBw/Jx1McE2rm+M3Goi7DtSHX3gJqpL3qGgbLIn1LQnx0OsN+2jtw37SlvD BDl++mTYP84bDESoQN4vOgdhOLBmj3oV/hLtWQub3jPyxLJSCLNcBguuwr4VYvh5HP IrRseXgsprN5ZPP8HKHpmcMhVPjmrWIqSuhx3011cF9Pej3FShG4u3mUnsVzCCWCKp EDkTMKzKatCyfJ9K1bIYZMpyMlIqlX7krGPpHow8zGG4BodJRGxiJEiMl25j2jApGD ofe5Nhrv2Y+ySzUt9S+JS3TT4/yS64uFwUFXsKvEN6T0VRjs3D1qjJOk1yj2/z1vEK Fk2xsY7UceNhg==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/2uqJKT74larCa8ir62DArIhFf80
Subject: Re: [clue] Notes from design team meeting re: signaling open issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 16:55:03 -0000

On 9/19/14 11:23 AM, Robert Hansen wrote:
> I would say that the answer is whichever happens first.

I'm question that. Can you tell an intentional closure of the stream 
from a reset due to an error of some sort? And even an intentional 
closure might be in preparation for an O/A to change the SCTP address.

I think it isn't until you get a new O/A that you know what is intended. 
Until then, ISTM it is better to leave the media running in accord with 
the last configurations.

	Thanks,
	Paul

> Rob
>
> On 19/09/14 01:10, Christian Groves wrote:
>> Hello Rob,
>>
>> With respect to 3), I guess there's two points at which the video
>> could stop. Actual closure of the CLUE SCTP streams through the data
>> channel reset procedure, or once the updated SDP is received. I guess
>> the actual trigger is the closure of the CLUE stream rather than the
>> reception of the SDP.
>>
>> Christian
>>
>> On 17/09/2014 7:07 PM, Robert Hansen wrote:
>>> 1) Yes
>>> 2) Yes
>>> 3) No. At present, the proposal is that by removing the SCTP
>>> association from the CLUE group the call is no longer CLUE-enabled.
>>> However, because the CLUE group is still present and still contains
>>> the video that video is still CLUE-controlled and hence can't be sent
>>> under these conditions.
>>> 4) Yes
>>>
>>> Rob
>>>
>>> On 17/09/14 02:37, Christian Groves wrote:
>>>>
>>>> I just want to make sure I understand what was being proposed for
>>>> fallback of CLUE media streams. I'm going to try to avoid the use of
>>>> "CLUE enabled" and "CLUE capable" and focus on the SDP and what it
>>>> means.
>>>>
>>>> Consider the following SDP where a CLUE controlled video stream has
>>>> been configured, established and everything is awesome :-).
>>>>
>>>>       a=group:CLUE 1 2
>>>>       m=application 6100 SCTP/DTLS 6100
>>>>       a=sctpmap:1 webrtc-datachannel
>>>>       a=mid:1
>>>>       ...
>>>>       m=video 6004 RTP/AVP 96
>>>>       a=rtpmap:96 H264/90000
>>>>       a=fmtp:96 profile-level-id=42e016
>>>>       a=sendonly
>>>>       a=mid:2
>>>>       a=label:enc1
>>>>
>>>> Case 1) The SDP is updated to remove mid:2 effectively removing the
>>>> video stream from CLUE control. However a=sendonly remains, i.e.
>>>>       a=group:CLUE 1
>>>>       m=application 6100 SCTP/DTLS 6100
>>>>       a=sctpmap:1 webrtc-datachannel
>>>>       a=mid:1
>>>>       ...
>>>>       m=video 6004 RTP/AVP 96
>>>>       a=rtpmap:96 H264/90000
>>>>       a=fmtp:96 profile-level-id=42e016
>>>>       a=sendonly
>>>>
>>>> My assumption is that video continues to flow because the media
>>>> stream is no longer under CLUE control (thus rules regarding
>>>> configuring don't apply) and the sending direction is still send
>>>> only. However as its not part of a CLUE group anymore any previously
>>>> Advertised CLUEinfo regarding the video stream is no longer valid.
>>>>
>>>> Case 2) The SDP is updated to remove mid:2 effectively removing the
>>>> video stream from CLUE control the endpoint wants to stop the
>>>> stream. My assumption is that to stop sending the video media stream
>>>> either the port has to be changed to zero or a=inactive is set. Any
>>>> CLUE info regarding the stream is discarded.
>>>>
>>>> Case 3) The SDP is updated to remove mid:1 effectively closing the
>>>> CLUE channel. However the video stream remain in the CLUE group, e.g.
>>>>       a=group:CLUE 2
>>>>       m=application 6100 SCTP/DTLS 6100
>>>>       a=sctpmap:1 webrtc-datachannel
>>>>       ...
>>>>       m=video 6004 RTP/AVP 96
>>>>       a=rtpmap:96 H264/90000
>>>>       a=fmtp:96 profile-level-id=42e016
>>>>       a=sendonly
>>>>       a=mid:2
>>>>       a=label:enc1
>>>> My assumption is that the video stream continues unchanged and as
>>>> its still in a CLUE group any advertised CLUEinfo is still valid for
>>>> the stream.
>>>>
>>>> Case 4) To remove the CLUE protocol and media channels the CLUE
>>>> group should be removed and the media line zeroed/made inactive, e.g.
>>>>       m=application 6100 SCTP/DTLS 6100
>>>>       a=sctpmap:1 webrtc-datachannel
>>>>       ...
>>>>       m=video 0 RTP/AVP 96
>>>>
>>>> Rob is that what you were proposing?
>>>>
>>>> Regards, Christian
>>>>
>>>> On 16/09/2014 11:45 PM, Duckworth, Mark wrote:
>>>>>
>>>>> Here are my notes from the design team meeting.
>>>>>
>>>>> CLUE signaling design team meeting
>>>>>
>>>>> Sep 16, 2014
>>>>>
>>>>> Rob Hansen, Mary Barnes, Paul Kyzivat, Mark Duckworth, Christian
>>>>> Groves, Roberta Presta, Roni Even, Jonathan Lennox
>>>>>
>>>>> Rob discussed issues
>>>>>
>>>>> ·Fallback to non-CLUE - when does it happen?
>>>>>
>>>>> osignalling document has a proposal that defines when this happens,
>>>>> but there are other ideas
>>>>>
>>>>> oRob's idea (in the signaling doc) is to use the same criteria to
>>>>> enable CLUE as to disable it
>>>>>
>>>>> oIf data channel connection is lost, probably don't want that to
>>>>> mean the call is not CLUE enabled any more
>>>>>
>>>>> oThe group agrees with Rob's proposal
>>>>>
>>>>> ·Fallback to non-CLUE - what does it mean?
>>>>>
>>>>> oWhen fallback to non CLUE-enabled occurs, then CLUE-controlled
>>>>> media stops.
>>>>>
>>>>> osome other details about handling data channel and CLUE protocol
>>>>> should be defined
>>>>>
>>>>> oShould close the CLUE channel.  Can keep SCTP open if it is used
>>>>> for other things.
>>>>>
>>>>> ·When making an SDP offer, if the offerer wants to enable CLUE then
>>>>> SDP should indicate this.  Even if previous O/A exchanges have not
>>>>> enabled CLUE.  This is consistent with an offerer always including
>>>>> video if it wants to add video to an audio call.
>>>>>
>>>>> ·Security issues
>>>>>
>>>>> oMary made suggestions
>>>>>
>>>>> oThis doc shouldn't have a heavy security section.  Using existing
>>>>> protocols.
>>>>>
>>>>> oJonathan suggested mention case of SDP and SCTP going to different
>>>>> addresses, one is attacker one is victim?
>>>>>
>>>>> oMary plans to get a security review done during WGLC
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> clue mailing list
>>>>> clue@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>>
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Fri Sep 19 12:23:16 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82DE1A8761 for <clue@ietfa.amsl.com>; Fri, 19 Sep 2014 12:23:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qDliV7VlAVH for <clue@ietfa.amsl.com>; Fri, 19 Sep 2014 12:23:11 -0700 (PDT)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:56]) by ietfa.amsl.com (Postfix) with ESMTP id 296A51A068B for <clue@ietf.org>; Fri, 19 Sep 2014 12:23:10 -0700 (PDT)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta06.westchester.pa.mail.comcast.net with comcast id t7171o0091HzFnQ567PA79; Fri, 19 Sep 2014 19:23:10 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta14.westchester.pa.mail.comcast.net with comcast id t7PA1o00A3Ge9ey3a7PAGh; Fri, 19 Sep 2014 19:23:10 +0000
Message-ID: <541C829E.10208@alum.mit.edu>
Date: Fri, 19 Sep 2014 15:23:10 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <541BAAB9.5000504@nteczone.com>
In-Reply-To: <541BAAB9.5000504@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1411154590; bh=vivLblFpG/R3mLR/uFQ+XV36jKJUl0VKKwx6z9TF9hk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=lZzfCr3yBFIJlLXBL8Wkzsg1P0JpPKMelILWyKQuDQTuWqXJpIiUeks+MbFqiZyW9 FyFs5gwmvH7xxjYgPnA+dFi+TJm0/rBWSlJvYag9KlOoChTaDyyHCWxWiC8S8dCudX 3aytuiXkqa3ngixpnPwUErlKyZvkv0j+LKxbU3XO26lOBMHVrbps+3gXZHuD3C1kJ8 sZ/D53qEqXdzcXJorjgxKusANzRxnQYUSecoP5VOrtRxZtx4scqJnQArem+GOeCOKB yEBiqmcnq29eiMsS+g0SWvSC6+vmwzm1eWuJ1iwaXGJ5RjSOjvXcAF+Zc0exk6i+Q7 suGHlqRa+8K2g==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/oYzFMJaH3dXJxJXS-svwTq-tXX4
Subject: Re: [clue] Question of deactivation scenario
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 19:23:13 -0000

On 9/19/14 12:02 AM, Christian Groves wrote:
> I want to see if people have a common understanding of an re-ADV
> removing a media capture. Consider a scenario where an audio and two
> video captures have been Advertised, Configured and the SDP has been
> provided. Media is flowing.
>
> The Media Provider for some reason decides that one of the video media
> captures is no longer available and sends an updated Advertisement
> removing the video capture.
>
> Q1. Does the Media Consumer need to send an updated Configure message? I
> assume not as if the MP is not Advertising a media capture there's
> little else the MC can do but accept the removal.

IMO the consumer SHOULD send a new Configure, even if it is unchanged.
But I don't think it MUST.

Until it does, I think the provider SHOULD consider to send whatever is 
is capable of among what was last configured.

OR, perhaps we should assume that the provider applies the last received 
Config to the new advertisement and sends what matches. (But in this 
case it must ignore things that don't match, whereas when it receives a 
new Config it will reject it if some things don't match.)

Note that the above alternatives are not equivalent. In principle the 
provider can assign new identifiers to everything in the new 
advertisement, for captures, scenes, etc., even when the substance of 
what is being advertised is not changed. (This might be silly, but there 
may be cases where it is what makes sense.)

> Q2. I assume that it wouldn't matter at what stage the MP stops sending
> the media e.g. before the re-Advertisement, after the re-Advertisement
> or after the updated SIP-reinvite moving the media stream? Again there's
> little the MP could do to influence this.

I think there is potentially a difference to error reporting.

If you stop receiving a capture-encoding and don't know why, it may make 
sense to display some sort of error message to the local administrator 
and/or users. If you are told it is going away first, then you can avoid 
that.

Much of this is an implementation issue. But without some guidelines, we 
might get poor interop experiences.

	Thanks,
	Paul


From nobody Sun Sep 21 17:37:30 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AFFD1A0396 for <clue@ietfa.amsl.com>; Sun, 21 Sep 2014 17:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zrmESuKkDQy4 for <clue@ietfa.amsl.com>; Sun, 21 Sep 2014 17:37:26 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 830621A0395 for <clue@ietf.org>; Sun, 21 Sep 2014 17:37:26 -0700 (PDT)
Received: from ppp118-209-206-23.lns20.mel8.internode.on.net ([118.209.206.23]:53376 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XVraE-0002GI-I7 for clue@ietf.org; Mon, 22 Sep 2014 10:34:26 +1000
Message-ID: <541F6F43.9090105@nteczone.com>
Date: Mon, 22 Sep 2014 10:37:23 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <541BAAB9.5000504@nteczone.com> <541C829E.10208@alum.mit.edu>
In-Reply-To: <541C829E.10208@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/Ebngt6e0KrYOO-0ihkMZ9Nc1mWk
Subject: Re: [clue] Question of deactivation scenario
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Sep 2014 00:37:29 -0000

Hello Paul,

Please see below.

Regards, Christian

On 20/09/2014 5:23 AM, Paul Kyzivat wrote:
> On 9/19/14 12:02 AM, Christian Groves wrote:
>> I want to see if people have a common understanding of an re-ADV
>> removing a media capture. Consider a scenario where an audio and two
>> video captures have been Advertised, Configured and the SDP has been
>> provided. Media is flowing.
>>
>> The Media Provider for some reason decides that one of the video media
>> captures is no longer available and sends an updated Advertisement
>> removing the video capture.
>>
>> Q1. Does the Media Consumer need to send an updated Configure message? I
>> assume not as if the MP is not Advertising a media capture there's
>> little else the MC can do but accept the removal.
>
> IMO the consumer SHOULD send a new Configure, even if it is unchanged.
> But I don't think it MUST.
[CNG] I wonder if this is really a should given that the message is 
basically a no-op. What does the configure do?

>
> Until it does, I think the provider SHOULD consider to send whatever 
> is is capable of among what was last configured.
[CNG] I think this is the issue. Sometimes there's a "graceful" 
situation where it is possible to send an Advertisement before stopping 
sending media, then there's a "non-graceful" (i.e. someone powers off a 
camera) where the media stops before the Advertisement.

>
> OR, perhaps we should assume that the provider applies the last 
> received Config to the new advertisement and sends what matches. (But 
> in this case it must ignore things that don't match, whereas when it 
> receives a new Config it will reject it if some things don't match.)
[CNG] A MC doesn't have to send a Config in response to an Advertisement 
so I think the MP has to do this as part of normal processing.

>
> Note that the above alternatives are not equivalent. In principle the 
> provider can assign new identifiers to everything in the new 
> advertisement, for captures, scenes, etc., even when the substance of 
> what is being advertised is not changed. (This might be silly, but 
> there may be cases where it is what makes sense.)
[CNG] I theory yes. I think it would be good to document somewhere what 
the consequence of this is.

>
>> Q2. I assume that it wouldn't matter at what stage the MP stops sending
>> the media e.g. before the re-Advertisement, after the re-Advertisement
>> or after the updated SIP-reinvite moving the media stream? Again there's
>> little the MP could do to influence this.
>
> I think there is potentially a difference to error reporting.
>
> If you stop receiving a capture-encoding and don't know why, it may 
> make sense to display some sort of error message to the local 
> administrator and/or users. If you are told it is going away first, 
> then you can avoid that.
>
> Much of this is an implementation issue. But without some guidelines, 
> we might get poor interop experiences.
[CNG] Yes

>
>     Thanks,
>     Paul
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Sun Sep 21 17:43:50 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52C731A039C for <clue@ietfa.amsl.com>; Sun, 21 Sep 2014 17:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.6
X-Spam-Level: **
X-Spam-Status: No, score=2.6 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gxj7PUJ2o7z2 for <clue@ietfa.amsl.com>; Sun, 21 Sep 2014 17:43:47 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 895B91A039B for <clue@ietf.org>; Sun, 21 Sep 2014 17:43:46 -0700 (PDT)
Received: from ppp118-209-206-23.lns20.mel8.internode.on.net ([118.209.206.23]:53433 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XVrgN-00034i-RZ for clue@ietf.org; Mon, 22 Sep 2014 10:40:48 +1000
Message-ID: <541F70C0.3080203@nteczone.com>
Date: Mon, 22 Sep 2014 10:43:44 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9222FE@CRPMBOXPRD08.polycom.com> <5418E5F4.7040204@nteczone.com> <54194F5E.3020205@cisco.com> <541B7473.5090709@nteczone.com> <541C4A5B.9050804@cisco.com> <541C5FE3.5060502@alum.mit.edu>
In-Reply-To: <541C5FE3.5060502@alum.mit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/D8Egz-W7jEklConuf7PoDjJ8xx8
Subject: Re: [clue] Notes from design team meeting re: signaling open issues
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Sep 2014 00:43:48 -0000

I tend to agree with Paul, from a media flow perspective. I guess that 
means the criteria for establishing a media flow is different from 
removing a media flow.

Regards, Christian

On 20/09/2014 2:54 AM, Paul Kyzivat wrote:
>
>
> On 9/19/14 11:23 AM, Robert Hansen wrote:
>> I would say that the answer is whichever happens first.
>
> I'm question that. Can you tell an intentional closure of the stream 
> from a reset due to an error of some sort? And even an intentional 
> closure might be in preparation for an O/A to change the SCTP address.
>
> I think it isn't until you get a new O/A that you know what is 
> intended. Until then, ISTM it is better to leave the media running in 
> accord with the last configurations.
>
>     Thanks,
>     Paul
>
>> Rob
>>
>> On 19/09/14 01:10, Christian Groves wrote:
>>> Hello Rob,
>>>
>>> With respect to 3), I guess there's two points at which the video
>>> could stop. Actual closure of the CLUE SCTP streams through the data
>>> channel reset procedure, or once the updated SDP is received. I guess
>>> the actual trigger is the closure of the CLUE stream rather than the
>>> reception of the SDP.
>>>
>>> Christian
>>>
>>> On 17/09/2014 7:07 PM, Robert Hansen wrote:
>>>> 1) Yes
>>>> 2) Yes
>>>> 3) No. At present, the proposal is that by removing the SCTP
>>>> association from the CLUE group the call is no longer CLUE-enabled.
>>>> However, because the CLUE group is still present and still contains
>>>> the video that video is still CLUE-controlled and hence can't be sent
>>>> under these conditions.
>>>> 4) Yes
>>>>
>>>> Rob
>>>>
>>>> On 17/09/14 02:37, Christian Groves wrote:
>>>>>
>>>>> I just want to make sure I understand what was being proposed for
>>>>> fallback of CLUE media streams. I'm going to try to avoid the use of
>>>>> "CLUE enabled" and "CLUE capable" and focus on the SDP and what it
>>>>> means.
>>>>>
>>>>> Consider the following SDP where a CLUE controlled video stream has
>>>>> been configured, established and everything is awesome :-).
>>>>>
>>>>>       a=group:CLUE 1 2
>>>>>       m=application 6100 SCTP/DTLS 6100
>>>>>       a=sctpmap:1 webrtc-datachannel
>>>>>       a=mid:1
>>>>>       ...
>>>>>       m=video 6004 RTP/AVP 96
>>>>>       a=rtpmap:96 H264/90000
>>>>>       a=fmtp:96 profile-level-id=42e016
>>>>>       a=sendonly
>>>>>       a=mid:2
>>>>>       a=label:enc1
>>>>>
>>>>> Case 1) The SDP is updated to remove mid:2 effectively removing the
>>>>> video stream from CLUE control. However a=sendonly remains, i.e.
>>>>>       a=group:CLUE 1
>>>>>       m=application 6100 SCTP/DTLS 6100
>>>>>       a=sctpmap:1 webrtc-datachannel
>>>>>       a=mid:1
>>>>>       ...
>>>>>       m=video 6004 RTP/AVP 96
>>>>>       a=rtpmap:96 H264/90000
>>>>>       a=fmtp:96 profile-level-id=42e016
>>>>>       a=sendonly
>>>>>
>>>>> My assumption is that video continues to flow because the media
>>>>> stream is no longer under CLUE control (thus rules regarding
>>>>> configuring don't apply) and the sending direction is still send
>>>>> only. However as its not part of a CLUE group anymore any previously
>>>>> Advertised CLUEinfo regarding the video stream is no longer valid.
>>>>>
>>>>> Case 2) The SDP is updated to remove mid:2 effectively removing the
>>>>> video stream from CLUE control the endpoint wants to stop the
>>>>> stream. My assumption is that to stop sending the video media stream
>>>>> either the port has to be changed to zero or a=inactive is set. Any
>>>>> CLUE info regarding the stream is discarded.
>>>>>
>>>>> Case 3) The SDP is updated to remove mid:1 effectively closing the
>>>>> CLUE channel. However the video stream remain in the CLUE group, e.g.
>>>>>       a=group:CLUE 2
>>>>>       m=application 6100 SCTP/DTLS 6100
>>>>>       a=sctpmap:1 webrtc-datachannel
>>>>>       ...
>>>>>       m=video 6004 RTP/AVP 96
>>>>>       a=rtpmap:96 H264/90000
>>>>>       a=fmtp:96 profile-level-id=42e016
>>>>>       a=sendonly
>>>>>       a=mid:2
>>>>>       a=label:enc1
>>>>> My assumption is that the video stream continues unchanged and as
>>>>> its still in a CLUE group any advertised CLUEinfo is still valid for
>>>>> the stream.
>>>>>
>>>>> Case 4) To remove the CLUE protocol and media channels the CLUE
>>>>> group should be removed and the media line zeroed/made inactive, e.g.
>>>>>       m=application 6100 SCTP/DTLS 6100
>>>>>       a=sctpmap:1 webrtc-datachannel
>>>>>       ...
>>>>>       m=video 0 RTP/AVP 96
>>>>>
>>>>> Rob is that what you were proposing?
>>>>>
>>>>> Regards, Christian
>>>>>
>>>>> On 16/09/2014 11:45 PM, Duckworth, Mark wrote:
>>>>>>
>>>>>> Here are my notes from the design team meeting.
>>>>>>
>>>>>> CLUE signaling design team meeting
>>>>>>
>>>>>> Sep 16, 2014
>>>>>>
>>>>>> Rob Hansen, Mary Barnes, Paul Kyzivat, Mark Duckworth, Christian
>>>>>> Groves, Roberta Presta, Roni Even, Jonathan Lennox
>>>>>>
>>>>>> Rob discussed issues
>>>>>>
>>>>>> ·Fallback to non-CLUE - when does it happen?
>>>>>>
>>>>>> osignalling document has a proposal that defines when this happens,
>>>>>> but there are other ideas
>>>>>>
>>>>>> oRob's idea (in the signaling doc) is to use the same criteria to
>>>>>> enable CLUE as to disable it
>>>>>>
>>>>>> oIf data channel connection is lost, probably don't want that to
>>>>>> mean the call is not CLUE enabled any more
>>>>>>
>>>>>> oThe group agrees with Rob's proposal
>>>>>>
>>>>>> ·Fallback to non-CLUE - what does it mean?
>>>>>>
>>>>>> oWhen fallback to non CLUE-enabled occurs, then CLUE-controlled
>>>>>> media stops.
>>>>>>
>>>>>> osome other details about handling data channel and CLUE protocol
>>>>>> should be defined
>>>>>>
>>>>>> oShould close the CLUE channel.  Can keep SCTP open if it is used
>>>>>> for other things.
>>>>>>
>>>>>> ·When making an SDP offer, if the offerer wants to enable CLUE then
>>>>>> SDP should indicate this.  Even if previous O/A exchanges have not
>>>>>> enabled CLUE.  This is consistent with an offerer always including
>>>>>> video if it wants to add video to an audio call.
>>>>>>
>>>>>> ·Security issues
>>>>>>
>>>>>> oMary made suggestions
>>>>>>
>>>>>> oThis doc shouldn't have a heavy security section. Using existing
>>>>>> protocols.
>>>>>>
>>>>>> oJonathan suggested mention case of SDP and SCTP going to different
>>>>>> addresses, one is attacker one is victim?
>>>>>>
>>>>>> oMary plans to get a security review done during WGLC
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> clue mailing list
>>>>>> clue@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>>
>>>>> _______________________________________________
>>>>> clue mailing list
>>>>> clue@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>
>>>> _______________________________________________
>>>> clue mailing list
>>>> clue@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/clue
>>>>
>>>
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Mon Sep 22 07:29:48 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 739CD1A1AF5 for <clue@ietfa.amsl.com>; Mon, 22 Sep 2014 07:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tDH5m-0XhII7 for <clue@ietfa.amsl.com>; Mon, 22 Sep 2014 07:29:44 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 854701A1AF4 for <clue@ietf.org>; Mon, 22 Sep 2014 07:29:39 -0700 (PDT)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by resqmta-ch2-12v.sys.comcast.net with comcast id uDoL1o0021ZXKqc01EVePw; Mon, 22 Sep 2014 14:29:38 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by omta21.westchester.pa.mail.comcast.net with comcast id uEVe1o0063Ge9ey3hEVeb1; Mon, 22 Sep 2014 14:29:38 +0000
Message-ID: <54203252.1040702@alum.mit.edu>
Date: Mon, 22 Sep 2014 10:29:38 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <541BAAB9.5000504@nteczone.com> <541C829E.10208@alum.mit.edu> <541F6F43.9090105@nteczone.com>
In-Reply-To: <541F6F43.9090105@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1411396178; bh=AeW61fS82foosYYySJiI6bdaFmOsedygJs4pJ3a8/dU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ax5ncgilodOXdUANpyqLPs5K/CfmenJ21zti7O4c8BxHyB3yF1ocycIQaj7rdiUB0 yY2OGYuyKQr3hj/P90CMIE+teGHQEWJ+OBZyWl6i8Z9yA4A3yDxnpVtRhljppbYJpp /RIalMfQddz5NP5/vxzewDii3hkm52QSTNnK4n9O74IBTXNg9hFRJT90cpEKvfg3kN j2PFA2bOIswnQ6yqe1nC1pdUZTiRdqdvitODlphvZUKEpbpHZVEuHtTVeLYQTAWzD1 O+tIVnlQrqkMGS2vOM0P1Ti05Wg0g3RilpgtEhLnmlaIE9CrZiui83rz9i4nkaKzk5 v8tHAdJzaXHuw==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/7ehhhbquLvMry8wHpVFEVbtruFc
Subject: Re: [clue] Question of deactivation scenario
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Sep 2014 14:29:45 -0000

Inline.

On 9/21/14 8:37 PM, Christian Groves wrote:
> Hello Paul,
>
> Please see below.
>
> Regards, Christian
>
> On 20/09/2014 5:23 AM, Paul Kyzivat wrote:
>> On 9/19/14 12:02 AM, Christian Groves wrote:
>>> I want to see if people have a common understanding of an re-ADV
>>> removing a media capture. Consider a scenario where an audio and two
>>> video captures have been Advertised, Configured and the SDP has been
>>> provided. Media is flowing.
>>>
>>> The Media Provider for some reason decides that one of the video media
>>> captures is no longer available and sends an updated Advertisement
>>> removing the video capture.
>>>
>>> Q1. Does the Media Consumer need to send an updated Configure message? I
>>> assume not as if the MP is not Advertising a media capture there's
>>> little else the MC can do but accept the removal.
>>
>> IMO the consumer SHOULD send a new Configure, even if it is unchanged.
>> But I don't think it MUST.
> [CNG] I wonder if this is really a should given that the message is
> basically a no-op. What does the configure do?

I'll comment on this below.

>> Until it does, I think the provider SHOULD consider to send whatever
>> is is capable of among what was last configured.
> [CNG] I think this is the issue. Sometimes there's a "graceful"
> situation where it is possible to send an Advertisement before stopping
> sending media, then there's a "non-graceful" (i.e. someone powers off a
> camera) where the media stops before the Advertisement.
>
>>
>> OR, perhaps we should assume that the provider applies the last
>> received Config to the new advertisement and sends what matches. (But
>> in this case it must ignore things that don't match, whereas when it
>> receives a new Config it will reject it if some things don't match.)
> [CNG] A MC doesn't have to send a Config in response to an Advertisement
> so I think the MP has to do this as part of normal processing.

I listed two *alternatives* above. They are conceptually different, 
though in most common cases they will yield the same result. It is 
possible to construct cases where they produce different results:

>> Note that the above alternatives are not equivalent. In principle the
>> provider can assign new identifiers to everything in the new
>> advertisement, for captures, scenes, etc., even when the substance of
>> what is being advertised is not changed. (This might be silly, but
>> there may be cases where it is what makes sense.)
> [CNG] I theory yes. I think it would be good to document somewhere what
> the consequence of this is.

Exactly. This is why we need to be precise on what happens between the 
sending of the new advertisement and the receipt of a new Configure that 
references it. Restating my two alternatives:

1) the provider keeps sending as many of the previously configured 
capture encodings as it can, defined by the last received Configure and 
the advertisement that it referred to. In this alternative, this could 
potentially include captures that are no longer advertised. It would 
also cover the case where the new advertisement renamed things such that 
the old config wouldn't select anything in the new advertisement.

2) at the time the provider sends the new advertisement it also 
reinterprets the last received configure against the new adv, and sends 
only those things that are selected.

ISTM that (2) is very well defined and should provide consistent results 
across all implementations. OTOH, (1) when well implemented might 
provide a more "graceful" transition, but probably not as consistent.

Also factoring into this is the question of what to do between the time 
the advertisement is sent and the ACK received, and what to do if the 
advertisement receives a NAK.

>>> Q2. I assume that it wouldn't matter at what stage the MP stops sending
>>> the media e.g. before the re-Advertisement, after the re-Advertisement
>>> or after the updated SIP-reinvite moving the media stream? Again there's
>>> little the MP could do to influence this.
>>
>> I think there is potentially a difference to error reporting.
>>
>> If you stop receiving a capture-encoding and don't know why, it may
>> make sense to display some sort of error message to the local
>> administrator and/or users. If you are told it is going away first,
>> then you can avoid that.
>>
>> Much of this is an implementation issue. But without some guidelines,
>> we might get poor interop experiences.
> [CNG] Yes

So I think it would be good to provide some (non-normative) guidelines.

	Thanks,
	Paul


From nobody Tue Sep 23 04:48:46 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D081A70FE for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 04:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1WrPs3lBITA4 for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 04:48:43 -0700 (PDT)
Received: from mail1.bemta7.messagelabs.com (mail1.bemta7.messagelabs.com [216.82.254.103]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE41B1A1A98 for <clue@ietf.org>; Tue, 23 Sep 2014 04:48:43 -0700 (PDT)
Received: from [216.82.254.20:36919] by server-7.bemta-7.messagelabs.com id 10/03-02060-B1E51245; Tue, 23 Sep 2014 11:48:43 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-12.tower-47.messagelabs.com!1411472922!13506171!1
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.12.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29389 invoked from network); 23 Sep 2014 11:48:43 -0000
Received: from crpehubprd01.polycom.com (HELO Crpehubprd01.polycom.com) (140.242.64.158) by server-12.tower-47.messagelabs.com with AES128-SHA encrypted SMTP; 23 Sep 2014 11:48:43 -0000
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by Crpehubprd01.polycom.com ([::1]) with mapi; Tue, 23 Sep 2014 04:48:42 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "clue@ietf.org" <clue@ietf.org>
Date: Tue, 23 Sep 2014 04:48:39 -0700
Thread-Topic: framework issues for design team meeting today
Thread-Index: Ac/XI+XYOlzyNpF3QLmC1AfkVLmwng==
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9227ED@CRPMBOXPRD08.polycom.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_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9227EDCRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/aprlk_FDiYphczVVyS4GLWts1SY
Subject: [clue] framework issues for design team meeting today
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 11:48:45 -0000

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

Hi All,
There is very little left to discuss that we haven't already discussed.  I =
have only these two things on my list:

1.       I'm looking for help on deciding which references are normative an=
d informative

2.       Want to resolve the editor's note in section 12.3.3 about associat=
ing incoming packets with the original capture that is a constituent of an =
MCC

Regards,
Mark

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9227EDCRPMBOXPRD08p_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:dt=3D"uuid:C2F4101=
0-65B3-11d1-A29F-00AA00C14882" xmlns:m=3D"http://schemas.microsoft.com/offi=
ce/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META HTTP=
-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"><meta nam=
e=3DGenerator content=3D"Microsoft Word 14 (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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:382221065;
	mso-list-type:hybrid;
	mso-list-template-ids:196910358 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi All,<o:p></o:=
p></p><p class=3DMsoNormal>There is very little left to discuss that we hav=
en&#8217;t already discussed.&nbsp; I have only these two things on my list=
:<o:p></o:p></p><p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso=
-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>=
1.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; </span></span><![endif]>I&#8217;m looking for help on deciding whi=
ch references are normative and informative<o:p></o:p></p><p class=3DMsoLis=
tParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supp=
ortLists]><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Time=
s New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>=
Want to resolve the editor&#8217;s note in section 12.3.3 about associating=
 incoming packets with the original capture that is a constituent of an MCC=
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al>Regards,<o:p></o:p></p><p class=3DMsoNormal>Mark<o:p></o:p></p></div></b=
ody></html>=

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9227EDCRPMBOXPRD08p_--


From nobody Tue Sep 23 05:03:02 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3383A1A710D for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 05:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFsBh9IDkXIp for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 05:02:58 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C64F1A7113 for <clue@ietf.org>; Tue, 23 Sep 2014 05:02:57 -0700 (PDT)
X-AuditID: c1b4fb30-f79736d0000053b8-8f-542161701959
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 3D.68.21432.07161245; Tue, 23 Sep 2014 14:02:56 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0174.001; Tue, 23 Sep 2014 14:02:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Duckworth, Mark" <Mark.Duckworth@polycom.com>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: framework issues for design team meeting today
Thread-Index: Ac/XI+XYOlzyNpF3QLmC1AfkVLmwngAAluSw
Date: Tue, 23 Sep 2014 12:02:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D457A67@ESESSMB209.ericsson.se>
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9227ED@CRPMBOXPRD08.polycom.com>
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A9227ED@CRPMBOXPRD08.polycom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D457A67ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKLMWRmVeSWpSXmKPExsUyM+JvjW5BomKIweppAhb7T11mtlh35Cmz A5PHkiU/mTxePFAKYIrisklJzcksSy3St0vgytjV/JmlYIF5xZMPs9gbGF8YdDFyckgImEgs 3XiWCcIWk7hwbz1bFyMXh5DAUUaJi+c7oZwljBK7364CquLgYBOwkOj+pw3SICIQKrF65iYW EFtYwFri0+pr7CAlIgI2EqfeW0KUGEnMXPSPDcRmEVCV+PX8PNgUXgFfibUfZEBMIYFAiRNX BEEqOAWCJJY+PQo2kBHomu+n1oBdxiwgLnHryXyoKwUkluw5zwxhi0q8fPyPFcJWlGh/2sAI UZ8vcXF5M9hWXgFBiZMzn7BMYBSZhWTULCRls5CUQcR1JBbs/sQGYWtLLFv4mhnGPnPgMROy +AJG9lWMosWpxUm56UZGeqlFmcnFxfl5enmpJZsYgfF0cMtvgx2ML587HmIU4GBU4uFVuKIQ IsSaWFZcmXuIUZqDRUmcd+G5ecFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGGee/zHJ5mhz b3SmimbrgjtWZYu13UyFWyJyGRxm75e7lblPZ59WXsonuTBOCW39KfuTkxaZTzc4efDwBr+d u460RkYsTuezv3khwNtw5rbAy3r8N92Z9xzsPCxTqSWyfc5nWxGTsAl/rE0tRd8szBJf0bDu Wn+N+EzZ74vMO14t278p8PKcH0osxRmJhlrMRcWJAOk12cCIAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/gXzirEPR94p_4dm31_hSkxi7KYI
Subject: Re: [clue] framework issues for design team meeting today
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 12:03:01 -0000

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

Hi,

Due to private issues, I will unfortunately not be able to attend today eit=
her.

Regards,

Christer

From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Duckworth, Mark
Sent: 23. syyskuuta 2014 14:49
To: clue@ietf.org
Subject: [clue] framework issues for design team meeting today

Hi All,
There is very little left to discuss that we haven't already discussed.  I =
have only these two things on my list:

1.       I'm looking for help on deciding which references are normative an=
d informative

2.       Want to resolve the editor's note in section 12.3.3 about associat=
ing incoming packets with the original capture that is a constituent of an =
MCC

Regards,
Mark

--_000_7594FB04B1934943A5C02806D1A2204B1D457A67ESESSMB209erics_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:382221065;
	mso-list-type:hybrid;
	mso-list-template-ids:196910358 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Due to private issues,=
 I will unfortunately not be able to attend today either.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> clue [ma=
ilto:clue-bounces@ietf.org]
<b>On Behalf Of </b>Duckworth, Mark<br>
<b>Sent:</b> 23. syyskuuta 2014 14:49<br>
<b>To:</b> clue@ietf.org<br>
<b>Subject:</b> [clue] framework issues for design team meeting today<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi All,<o:p></o:p></p>
<p class=3D"MsoNormal">There is very little left to discuss that we haven&#=
8217;t already discussed.&nbsp; I have only these two things on my list:<o:=
p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span><![endif]>I&#8217;m looking for help on deciding which refere=
nces are normative and informative<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span><![endif]>Want to resolve the editor&#8217;s note in section =
12.3.3 about associating incoming packets with the original capture that is=
 a constituent of an MCC<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Mark<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D457A67ESESSMB209erics_--


From nobody Tue Sep 23 09:06:06 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 937E91A872B for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 09:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id STvUFsUKNYc2 for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 09:05:57 -0700 (PDT)
Received: from resqmta-po-06v.sys.comcast.net (resqmta-po-06v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:165]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F4A51A1B18 for <clue@ietf.org>; Tue, 23 Sep 2014 09:05:57 -0700 (PDT)
Received: from resomta-po-19v.sys.comcast.net ([96.114.154.243]) by resqmta-po-06v.sys.comcast.net with comcast id ug4C1o0015FMDhs01g5wv9; Tue, 23 Sep 2014 16:05:56 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-19v.sys.comcast.net with comcast id ug5v1o00P3Ge9ey01g5wsu; Tue, 23 Sep 2014 16:05:56 +0000
Message-ID: <54219A63.5070009@alum.mit.edu>
Date: Tue, 23 Sep 2014 12:05:55 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: CLUE <clue@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1411488356; bh=IFYDU9qXxSZji+rHMtFD8/tLrdhUr77bmz129dl9Eqg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ZhFfsZhnB38LPF97Jc7+dlTSPzUy27tNLQs45YTZrvZ/1Kpkf2nfsHrgOR2x9OSnJ pO6r2/nq3rYZV0u9WuY4oyn9NesCBgnuzhmHovZBHTjiP9cAnjhsIxpGcKSeTYtakG w3nRsX3z63l/6RK83iwnfLDiFm0RU5dlt9MlCrS75Qg0yavrIDl/r+kD0K01zC2bw0 wMvzSCPou6WuAQuJriVTNor1Mk9YvKtQptoH/vIMrWt8RaOCJZ9cEunJOOxp1+fQrA TiBvJdocgtTiyPlYqLJWeT1de3j4xqfJmPWiPEbZCOkHr2BawX3ATI6bZlBR7gW/Yj tDMh07H0gAmrQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/lZ7X9p7d9fX9G_OBo3OSpWK706c
Subject: [clue] Minutes from today's design team meeting have been posted
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 16:05:58 -0000

http://trac.tools.ietf.org/wg/clue/trac/attachment/wiki/Design-Team/minutes-140923.txt


From nobody Tue Sep 23 11:16:33 2014
Return-Path: <trac+clue@trac.tools.ietf.org>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 831D81A87E3 for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 11:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9lvKQoSuO0IG for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 11:16:30 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AF471A1BBF for <clue@ietf.org>; Tue, 23 Sep 2014 11:16:30 -0700 (PDT)
Received: from localhost ([::1]:49729 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+clue@trac.tools.ietf.org>) id 1XWUdV-00055R-MM; Tue, 23 Sep 2014 11:16:25 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "clue issue tracker" <trac+clue@zinfandel.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-clue-framework@tools.ietf.org, mark.duckworth@polycom.com
X-Trac-Project: clue
Date: Tue, 23 Sep 2014 18:16:25 -0000
X-URL: http://tools.ietf.org/wg/clue/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/clue/trac/ticket/64
Message-ID: <068.900b073e446e3451e11d30245ca663b6@trac.tools.ietf.org>
X-Trac-Ticket-ID: 64
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-clue-framework@tools.ietf.org, mark.duckworth@polycom.com, clue@ietf.org
X-SA-Exim-Mail-From: trac+clue@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: apeppere@gmail.com, mark.duckworth@polycom.com, stewe@stewe.org
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/6sZomGVfW1IjL0vHxtPRyrPDFYE
Cc: clue@ietf.org
Subject: [clue] #64 (framework): Framework should refer to mechanism for determining capture ID from incoming RTP
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 18:16:31 -0000

#64: Framework should refer to mechanism for determining capture ID from
incoming RTP

 Framework example has an editor's note about how to associate incoming RTP
 packets with the original capture that is a constituent of an MCC.  The
 framework should probably refer to something in the RTP Mapping document
 that isn't ready yet.  Related to Ticket #11.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |      Owner:  draft-ietf-clue-
  mark.duckworth@polycom.com         |  framework@tools.ietf.org
     Type:  task                     |     Status:  new
 Priority:  minor                    |  Milestone:
Component:  framework                |    Version:
 Severity:  -                        |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/clue/trac/ticket/64>
clue <http://tools.ietf.org/wg/clue/>


From nobody Tue Sep 23 20:47:36 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E101A8A56 for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 20:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8vxK3Pd89YoE for <clue@ietfa.amsl.com>; Tue, 23 Sep 2014 20:47:33 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B27EB1A8A54 for <clue@ietf.org>; Tue, 23 Sep 2014 20:47:32 -0700 (PDT)
Received: from ppp118-209-115-110.lns20.mel4.internode.on.net ([118.209.115.110]:55675 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XWdUq-0002yi-4p for clue@ietf.org; Wed, 24 Sep 2014 13:44:04 +1000
Message-ID: <54223ECF.6050205@nteczone.com>
Date: Wed, 24 Sep 2014 13:47:27 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <541BAAB9.5000504@nteczone.com> <541C829E.10208@alum.mit.edu> <541F6F43.9090105@nteczone.com> <54203252.1040702@alum.mit.edu>
In-Reply-To: <54203252.1040702@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/ZRxJyqvmg7Qzm5Mvn0tRLPgSpg0
Subject: Re: [clue] Question of deactivation scenario
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2014 03:47:35 -0000

Hello Paul,

..snip..
>>> Note that the above alternatives are not equivalent. In principle the
>>> provider can assign new identifiers to everything in the new
>>> advertisement, for captures, scenes, etc., even when the substance of
>>> what is being advertised is not changed. (This might be silly, but
>>> there may be cases where it is what makes sense.)
>> [CNG] I theory yes. I think it would be good to document somewhere what
>> the consequence of this is.
>
> Exactly. This is why we need to be precise on what happens between the 
> sending of the new advertisement and the receipt of a new Configure 
> that references it. Restating my two alternatives:
>
> 1) the provider keeps sending as many of the previously configured 
> capture encodings as it can, defined by the last received Configure 
> and the advertisement that it referred to. In this alternative, this 
> could potentially include captures that are no longer advertised. It 
> would also cover the case where the new advertisement renamed things 
> such that the old config wouldn't select anything in the new 
> advertisement.

> 2) at the time the provider sends the new advertisement it also 
> reinterprets the last received configure against the new adv, and 
> sends only those things that are selected.
>
> ISTM that (2) is very well defined and should provide consistent 
> results across all implementations. OTOH, (1) when well implemented 
> might provide a more "graceful" transition, but probably not as 
> consistent.

> Also factoring into this is the question of what to do between the 
> time the advertisement is sent and the ACK received, and what to do if 
> the advertisement receives a NAK.

[CNG] I think there's a modification of the behaviour of (1) that 
factors in the ACK.

(3) If possible, the provider keeps sending the previously configured 
capture encodings until it receives an ACK to the Advertisement at which 
point it applies the behaviour of (2). At least the MC knows that the 
capture encoding is being removed before the media packets stop in 
situations where the MP can give notice.
In the NACK case the MP should probably resend the Advertisement and 
hopefully receive an ACK but in reality if there's a syntax error 
causing a NACK its probably not going to be fixed by resending so the MP 
could just drop the media stream.

>
>>>> Q2. I assume that it wouldn't matter at what stage the MP stops 
>>>> sending
>>>> the media e.g. before the re-Advertisement, after the re-Advertisement
>>>> or after the updated SIP-reinvite moving the media stream? Again 
>>>> there's
>>>> little the MP could do to influence this.
>>>
>>> I think there is potentially a difference to error reporting.
>>>
>>> If you stop receiving a capture-encoding and don't know why, it may
>>> make sense to display some sort of error message to the local
>>> administrator and/or users. If you are told it is going away first,
>>> then you can avoid that.
>>>
>>> Much of this is an implementation issue. But without some guidelines,
>>> we might get poor interop experiences.
>> [CNG] Yes
>
> So I think it would be good to provide some (non-normative) guidelines.
>
>     Thanks,
>     Paul
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Fri Sep 26 03:38:55 2014
Return-Path: <roberta.presta@unina.it>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 069D81A1AC7 for <clue@ietfa.amsl.com>; Fri, 26 Sep 2014 03:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.663
X-Spam-Level: **
X-Spam-Status: No, score=2.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-N8_qTJw5N1 for <clue@ietfa.amsl.com>; Fri, 26 Sep 2014 03:38:47 -0700 (PDT)
Received: from brc1.unina.it (brc1.unina.it [192.132.34.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E89FE1A1AC8 for <clue@ietf.org>; Fri, 26 Sep 2014 03:38:46 -0700 (PDT)
X-ASG-Debug-ID: 1411727924-05ce377d186773c0001-dOUo1C
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by brc1.unina.it with ESMTP id MI95CSuCXkYxrPSe (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for <clue@ietf.org>; Fri, 26 Sep 2014 12:38:44 +0200 (CEST)
X-Barracuda-Envelope-From: roberta.presta@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.61
Received: from [127.0.0.1] ([193.206.114.54]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id s8QAcgTr016482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 26 Sep 2014 12:38:43 +0200
Message-ID: <54254238.4000201@unina.it>
Date: Fri, 26 Sep 2014 12:38:48 +0200
From: Roberta Presta <roberta.presta@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "clue@ietf.org" <clue@ietf.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
X-ASG-Orig-Subj: data model ticket solved: #48 - Linking participant information with participant type
Content-Transfer-Encoding: 7bit
X-Barracuda-Connect: smtp1.unina.it[192.132.34.61]
X-Barracuda-Start-Time: 1411727924
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.50:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210
X-Barracuda-Spam-Score: -2.02
X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.9901 Rule breakdown below pts rule name              description ---- ---------------------- --------------------------------------------------
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/82PY8C6_o6CFOVsxRGts4sPeFzk
Subject: [clue] data model ticket solved: #48 - Linking participant information with participant type
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2014 10:38:49 -0000

Dear all,

the ticket #48 was discussed in the design team meeting of June 10 
(http://trac.tools.ietf.org/wg/clue/trac/attachment/wiki/Design-Team/CLUE-datamodel-design-team-meeting-140610.pptx). 


Here the solution (already included in the current version of the 
datamodel draft).
A <mediaCapture> has an optional <capturedPeople> field containing a 
list of <personID>s referring to the <people> section in the ADV.
Within the <people> section, for each represented person, there is a 
<person> element containing one <personInfo> (xcard) and zero or more 
<personType>, representing the role(s) of that person in the 
telepresence session. By this way, it is possible to link the person 
information with one or more participant types.
Please see the advertisement example in datamodel document or the slides 
presented during the CLUE session at IETF90 
(http://www.ietf.org/proceedings/90/slides/slides-90-clue-1.pdf) for a 
sample representation of the above solution.

It seems that nobody is unhappy with that, so we would like to consider 
the ticket closed.
Do you agree?

Roberta


From nobody Fri Sep 26 08:28:49 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32B291A6FE3 for <clue@ietfa.amsl.com>; Fri, 26 Sep 2014 08:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JmUVXTr7uiXz for <clue@ietfa.amsl.com>; Fri, 26 Sep 2014 08:28:46 -0700 (PDT)
Received: from mail1.bemta7.messagelabs.com (mail1.bemta7.messagelabs.com [216.82.254.108]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD7E61A004D for <clue@ietf.org>; Fri, 26 Sep 2014 08:28:46 -0700 (PDT)
Received: from [216.82.254.19:53100] by server-12.bemta-7.messagelabs.com id 27/49-05501-C2685245; Fri, 26 Sep 2014 15:28:44 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-5.tower-96.messagelabs.com!1411745264!13945050!6
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.12.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7888 invoked from network); 26 Sep 2014 15:28:36 -0000
Received: from crpehubprd01.polycom.com (HELO Crpehubprd01.polycom.com) (140.242.64.158) by server-5.tower-96.messagelabs.com with AES128-SHA encrypted SMTP; 26 Sep 2014 15:28:36 -0000
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by Crpehubprd01.polycom.com ([::1]) with mapi; Fri, 26 Sep 2014 08:27:58 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: Roberta Presta <roberta.presta@unina.it>, "clue@ietf.org" <clue@ietf.org>
Date: Fri, 26 Sep 2014 08:27:56 -0700
Thread-Topic: [clue] data model ticket solved: #48 - Linking participant information with participant type
Thread-Index: Ac/ZdhG2NRPGJuv4QpWX8/3uDj9cIAAKE2rA
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922BB3@CRPMBOXPRD08.polycom.com>
References: <54254238.4000201@unina.it>
In-Reply-To: <54254238.4000201@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/L7IU27Dlq75NnigrAt2aZKqujeQ
Subject: Re: [clue] data model ticket solved: #48 - Linking participant information with participant type
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2014 15:28:48 -0000

Roberta, Yes I agree.
Mark

> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Roberta Presta
> Sent: Friday, September 26, 2014 6:39 AM
> To: clue@ietf.org
> Subject: [clue] data model ticket solved: #48 - Linking participant infor=
mation
> with participant type
>=20
> Dear all,
>=20
> the ticket #48 was discussed in the design team meeting of June 10
> (http://trac.tools.ietf.org/wg/clue/trac/attachment/wiki/Design-
> Team/CLUE-datamodel-design-team-meeting-140610.pptx).
>=20
>=20
> Here the solution (already included in the current version of the
> datamodel draft).
> A <mediaCapture> has an optional <capturedPeople> field containing a
> list of <personID>s referring to the <people> section in the ADV.
> Within the <people> section, for each represented person, there is a
> <person> element containing one <personInfo> (xcard) and zero or more
> <personType>, representing the role(s) of that person in the
> telepresence session. By this way, it is possible to link the person
> information with one or more participant types.
> Please see the advertisement example in datamodel document or the slides
> presented during the CLUE session at IETF90
> (http://www.ietf.org/proceedings/90/slides/slides-90-clue-1.pdf) for a
> sample representation of the above solution.
>=20
> It seems that nobody is unhappy with that, so we would like to consider
> the ticket closed.
> Do you agree?
>=20
> Roberta
>=20
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Fri Sep 26 10:01:38 2014
Return-Path: <trac+clue@trac.tools.ietf.org>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89D6F1A00D8 for <clue@ietfa.amsl.com>; Fri, 26 Sep 2014 10:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SaZ-b9xclT04 for <clue@ietfa.amsl.com>; Fri, 26 Sep 2014 10:01:33 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B483C1A6F07 for <clue@ietf.org>; Fri, 26 Sep 2014 10:01:33 -0700 (PDT)
Received: from localhost ([::1]:42015 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+clue@trac.tools.ietf.org>) id 1XXYtd-0008VT-4q; Fri, 26 Sep 2014 10:01:29 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "clue issue tracker" <trac+clue@zinfandel.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-clue-data-model-schema@tools.ietf.org, mary.ietf.barnes@gmail.com
X-Trac-Project: clue
Date: Fri, 26 Sep 2014 17:01:29 -0000
X-URL: http://tools.ietf.org/wg/clue/
X-Trac-Ticket-URL: https://tools.ietf.org/wg/clue/trac/ticket/48#comment:1
Message-ID: <083.b7d74de15dd393f91fbdd95e1393db8e@trac.tools.ietf.org>
References: <068.f474680f0078514d75dce3b2ea6090d2@trac.tools.ietf.org>
X-Trac-Ticket-ID: 48
In-Reply-To: <068.f474680f0078514d75dce3b2ea6090d2@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-clue-data-model-schema@tools.ietf.org, mary.ietf.barnes@gmail.com, clue@ietf.org
X-SA-Exim-Mail-From: trac+clue@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: roberta.presta@unina.it, spromano@unina.it
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/xKbD8sSMPdSqEm_tbgJDNlYAQkk
Cc: clue@ietf.org
Subject: Re: [clue] #48 (draft-ietf-clue-data-model-schema): Linking participant Information with Participant Type
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2014 17:01:36 -0000

#48: Linking participant Information with Participant Type

Changes (by mary.ietf.barnes@gmail.com):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 The ticket was discussed in the design team meeting of June 10
 (http://trac.tools.ietf.org/wg/clue/trac/attachment/wiki/Design-Team/CLUE-
 datamodel-design-team-meeting-140610.pptx).

 Here the solution (already included in the current version (-06) of the
 datamodel draft).
 A <mediaCapture> has an optional <capturedPeople> field containing a list
 of <personID>s referring to the <people> section in the ADV.
 Within the <people> section, for each represented person, there is a
 <person> element containing one <personInfo> (xcard) and zero or more
 <personType>, representing the role(s) of that person in the telepresence
 session. By this way, it is possible to link the person information with
 one or more participant types.
 Please see the advertisement example in datamodel document or the slides
 presented during the CLUE session at IETF90
 (http://www.ietf.org/proceedings/90/slides/slides-90-clue-1.pdf) for a
 sample representation of the above solution.T

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |       Owner:  draft-ietf-clue-data-
  mary.ietf.barnes@gmail.com         |  model-schema@tools.ietf.org
     Type:  task                     |      Status:  closed
 Priority:  minor                    |   Milestone:  milestone1
Component:  draft-ietf-clue-data-    |     Version:  1.0
  model-schema                       |  Resolution:  fixed
 Severity:  Active WG Document       |
 Keywords:                           |
-------------------------------------+-------------------------------------

Ticket URL: <https://tools.ietf.org/wg/clue/trac/ticket/48#comment:1>
clue <http://tools.ietf.org/wg/clue/>


From nobody Fri Sep 26 10:02:18 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F00B1A014E for <clue@ietfa.amsl.com>; Fri, 26 Sep 2014 10:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDKPTzO7hdxD for <clue@ietfa.amsl.com>; Fri, 26 Sep 2014 10:02:15 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DF241A00D8 for <clue@ietf.org>; Fri, 26 Sep 2014 10:02:14 -0700 (PDT)
Received: by mail-lb0-f179.google.com with SMTP id 10so14026580lbg.24 for <clue@ietf.org>; Fri, 26 Sep 2014 10:02:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Mr/dBD5V3MYqp8gJG1jcRXOgsAoOpEwuD2eCjI0lA58=; b=g3rYvq5vaa06YVYBFWlBpmEPBMBodpqIlJ+/7yY9iQbUHbcGfrVEOCEbtoILR7ShBe 3ny1zz+PLLE6f5eAMQxDT4Yuhp0v1FS6NjQDWqqKBmW9LtJqpO9bok73WU1D71imm1db aXN0btJ1kkXXRiwLpaIxtgw1CQVcHRfn0H0HQh7CZ05LWE5zvaa8sa9KQVpYKV+V9qig CsjBlxMaVGcM0A8Z9iw/RPL1RNDGvfxPIF2MDZ9cUd8T2+arNWMJLDQkc3FLlSWVe9r2 OBRKgu306t/QbtJlPvDKSp+GLHpw13v15thJRWtGq3zlE5CW3wuYKY9qVBMWwaw8/0ti nogg==
MIME-Version: 1.0
X-Received: by 10.112.55.7 with SMTP id n7mr20768825lbp.16.1411750933407; Fri, 26 Sep 2014 10:02:13 -0700 (PDT)
Received: by 10.25.12.207 with HTTP; Fri, 26 Sep 2014 10:02:13 -0700 (PDT)
In-Reply-To: <54254238.4000201@unina.it>
References: <54254238.4000201@unina.it>
Date: Fri, 26 Sep 2014 12:02:13 -0500
Message-ID: <CAHBDyN5-eD99DCeWh3ZBKwi4Mt5fWEXSUM-2Lp8jFQ_=P0OyFA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Roberta Presta <roberta.presta@unina.it>
Content-Type: multipart/alternative; boundary=001a11c3d11ee5adf30503fae078
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/4gr6tVVZrCldfh4DQSOn-OKyhzc
Cc: "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] data model ticket solved: #48 - Linking participant information with participant type
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2014 17:02:17 -0000

--001a11c3d11ee5adf30503fae078
Content-Type: text/plain; charset=UTF-8

Perfect (I had a feeling we had missed closing some of these that were
already fixed).  I've closed the ticket as fixed including the details you
provided.

Thanks,
Mary

On Fri, Sep 26, 2014 at 5:38 AM, Roberta Presta <roberta.presta@unina.it>
wrote:

> Dear all,
>
> the ticket #48 was discussed in the design team meeting of June 10 (
> http://trac.tools.ietf.org/wg/clue/trac/attachment/wiki/
> Design-Team/CLUE-datamodel-design-team-meeting-140610.pptx).
>
> Here the solution (already included in the current version of the
> datamodel draft).
> A <mediaCapture> has an optional <capturedPeople> field containing a list
> of <personID>s referring to the <people> section in the ADV.
> Within the <people> section, for each represented person, there is a
> <person> element containing one <personInfo> (xcard) and zero or more
> <personType>, representing the role(s) of that person in the telepresence
> session. By this way, it is possible to link the person information with
> one or more participant types.
> Please see the advertisement example in datamodel document or the slides
> presented during the CLUE session at IETF90 (http://www.ietf.org/
> proceedings/90/slides/slides-90-clue-1.pdf) for a sample representation
> of the above solution.
>
> It seems that nobody is unhappy with that, so we would like to consider
> the ticket closed.
> Do you agree?
>
> Roberta
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>

--001a11c3d11ee5adf30503fae078
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Perfect (I had a feeling we had missed closing some of the=
se that were already fixed).=C2=A0 I&#39;ve closed the ticket as fixed incl=
uding the details you provided.<div><br></div><div>Thanks,</div><div>Mary</=
div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri,=
 Sep 26, 2014 at 5:38 AM, Roberta Presta <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:roberta.presta@unina.it" target=3D"_blank">roberta.presta@unina.it</a=
>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all,<br>
<br>
the ticket #48 was discussed in the design team meeting of June 10 (<a href=
=3D"http://trac.tools.ietf.org/wg/clue/trac/attachment/wiki/Design-Team/CLU=
E-datamodel-design-team-meeting-140610.pptx" target=3D"_blank">http://trac.=
tools.ietf.org/<u></u>wg/clue/trac/attachment/wiki/<u></u>Design-Team/CLUE-=
datamodel-<u></u>design-team-meeting-140610.<u></u>pptx</a>). <br>
<br>
Here the solution (already included in the current version of the datamodel=
 draft).<br>
A &lt;mediaCapture&gt; has an optional &lt;capturedPeople&gt; field contain=
ing a list of &lt;personID&gt;s referring to the &lt;people&gt; section in =
the ADV.<br>
Within the &lt;people&gt; section, for each represented person, there is a =
&lt;person&gt; element containing one &lt;personInfo&gt; (xcard) and zero o=
r more &lt;personType&gt;, representing the role(s) of that person in the t=
elepresence session. By this way, it is possible to link the person informa=
tion with one or more participant types.<br>
Please see the advertisement example in datamodel document or the slides pr=
esented during the CLUE session at IETF90 (<a href=3D"http://www.ietf.org/p=
roceedings/90/slides/slides-90-clue-1.pdf" target=3D"_blank">http://www.iet=
f.org/<u></u>proceedings/90/slides/slides-<u></u>90-clue-1.pdf</a>) for a s=
ample representation of the above solution.<br>
<br>
It seems that nobody is unhappy with that, so we would like to consider the=
 ticket closed.<br>
Do you agree?<br>
<br>
Roberta<br>
<br>
______________________________<u></u>_________________<br>
clue mailing list<br>
<a href=3D"mailto:clue@ietf.org" target=3D"_blank">clue@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/clue" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/clue</a><br>
</blockquote></div><br></div>

--001a11c3d11ee5adf30503fae078--


From nobody Mon Sep 29 00:14:18 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 687201A6FCF for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 00:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.4
X-Spam-Level: *
X-Spam-Status: No, score=1.4 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  J_CHICKENPOX_111=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NmBAwuiMWAAT for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 00:14:16 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FDC71A1B79 for <clue@ietf.org>; Mon, 29 Sep 2014 00:14:16 -0700 (PDT)
Received: from ppp118-209-8-148.lns20.mel4.internode.on.net ([118.209.8.148]:56396 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XYV91-0005B4-0A for clue@ietf.org; Mon, 29 Sep 2014 17:13:15 +1000
Message-ID: <542906C3.5030502@nteczone.com>
Date: Mon, 29 Sep 2014 17:14:11 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "clue@ietf.org" <clue@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/0fzrmGd0fO-CapWJKUxAR7MOD4A
Subject: [clue] Examples in draft-ietf-clue-signaling-03 and draft-ietf-clue-signaling-03
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 07:14:17 -0000

There's an error that seems to have crept into the CLUE SDP example 
syntax in our documents.

The RTCWeb-datachannel uses an SCTP over DTLS transport i.e. DTLS/SCTP. 
Whereas in the examples where CLUE is involved SCTP/DTLS is specified. 
We should probably update that.

Also the latest draft draft-ietf-mmusic-sctp-sdp-07 has changed the 
syntax for specifying a SCTP m-line.

So:
[draft-ietf-clue-datachannel-01]/5.8. Example
m=application 54111 SCTP/DTLS 54111
a=sctpmap:54111 webrtc-datachannel

could be changed to:
m=application 54111 DTLS/SCTP webrtc-datachannel
a=fmtp:webrtc-datachannel max-message-size=100000
a=sctp-port 5000

more correctly to describe a "CLUE datachannel" the webrtc-datachannel 
would need to be added to a CLUE group. Therefore I think the following 
is probably a better example:
a=group:CLUE 3
...
m=application 54111 DTLS/SCTP webrtc-datachannel
a=fmtp:webrtc-datachannel max-message-size=100000
a=sctp-port 5000
a=mid:3

draft-ietf-clue-signaling-03 needs to be updated accordingly.

Regards, Christian


From nobody Mon Sep 29 07:23:50 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C93331A8723; Mon, 29 Sep 2014 07:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y_kiBY_PoieM; Mon, 29 Sep 2014 07:23:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC5B1A8727; Mon, 29 Sep 2014 07:23:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140929142334.25594.41624.idtracker@ietfa.amsl.com>
Date: Mon, 29 Sep 2014 07:23:34 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/Rgo5fNKZwNo_xVCE6fpW9S20vZE
Cc: clue@ietf.org
Subject: [clue] I-D Action: draft-ietf-clue-framework-17.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 14:23:36 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the ControLling mUltiple streams for tElepresence Working Group of the IETF.

        Title           : Framework for Telepresence Multi-Streams
        Authors         : Mark Duckworth
                          Andrew Pepperell
                          Stephan Wenger
	Filename        : draft-ietf-clue-framework-17.txt
	Pages           : 78
	Date            : 2014-09-29

Abstract:
   This document defines a framework for a protocol to enable devices
   in a telepresence conference to interoperate.  The protocol enables
   communication of information about multiple media streams so a
   sending system and receiving system can make reasonable decisions
   about transmitting, selecting and rendering the media streams.
   This protocol is used in addition to SIP signaling for setting up a
   telepresence session.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-clue-framework-17

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-clue-framework-17


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Mon Sep 29 07:28:24 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7EFF1A6F33 for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 07:28:22 -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_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bTjgT918ZJrn for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 07:28:20 -0700 (PDT)
Received: from mail1.bemta8.messagelabs.com (mail1.bemta8.messagelabs.com [216.82.243.195]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5FE01A1AD6 for <clue@ietf.org>; Mon, 29 Sep 2014 07:28:19 -0700 (PDT)
Received: from [216.82.241.100:19173] by server-3.bemta-8.messagelabs.com id EB/A8-01183-28C69245; Mon, 29 Sep 2014 14:28:18 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-14.tower-220.messagelabs.com!1412000896!16357809!3
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.12.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1942 invoked from network); 29 Sep 2014 14:28:18 -0000
Received: from crpehubprd01.polycom.com (HELO crpehubprd02.polycom.com) (140.242.64.158) by server-14.tower-220.messagelabs.com with AES128-SHA encrypted SMTP; 29 Sep 2014 14:28:18 -0000
Received: from PWEHUB01.polycom.com (10.236.2.221) by crpehubprd02.polycom.com (10.236.0.154) with Microsoft SMTP Server (TLS) id 8.3.192.1; Mon, 29 Sep 2014 07:27:34 -0700
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by PWEHUB01.polycom.com ([fe80::99a8:f785:3f0c:2bb6%17]) with mapi; Mon, 29 Sep 2014 07:27:34 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "clue@ietf.org" <clue@ietf.org>
Date: Mon, 29 Sep 2014 07:27:30 -0700
Thread-Topic: Updates in framework-17
Thread-Index: Ac/b8UZsWW3uZAXMQ/2YsMvV+eqabg==
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CB4@CRPMBOXPRD08.polycom.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_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CB4CRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/Vk_BPCcLFLHRHEojfUbmMycaoaM
Subject: [clue] Updates in framework-17
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 14:28:22 -0000

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

Changes from 16 to 17:

1. Ticket #59 - rename Capture Scene Entry (CSE) to Capture Scene View (CSV=
)

2. Ticket #60 - rename Global CSE List to Global View List

3. Ticket #61 - Proposal for describing the coordinate system.  Describe it=
 better, without conflicts if cameras point in different directions.

4. Minor clarifications and improved wording for Synchronisation Identity, =
MCC, Simultaneous Transmission Set.

5. Add definitions for CLUE-capable device and CLUE-enabled call, taken fro=
m the signaling draft.

6. Update definitions of Capture Device, Media Consumer, Media Provider, En=
dpoint, MCU, MCC.

7. Replace "middle box" with "MCU".

8. Explicitly state there can also be Media Captures that are not included =
in a Capture Scene View.

9. Explicitly state "A single Encoding Group MAY refer to encodings for dif=
ferent media types."

10.   In example 12.1.1 add axes and audio captures to the diagram, and des=
cribe placement of microphones.

11.   Add references to data model and signaling drafts.

12.   Split references into Normative and Informative sections.  Add headin=
g number for references section.

Mark

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CB4CRPMBOXPRD08p_
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=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:12.0pt;
	font-family:"Courier New";}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:72;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.5in;
	mso-add-space:auto;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:12.0pt;
	font-family:"Courier New";}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst
	{mso-style-priority:72;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:12.0pt;
	font-family:"Courier New";}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListPar=
agraphCxSpMiddle
	{mso-style-priority:72;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:12.0pt;
	font-family:"Courier New";}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagra=
phCxSpLast
	{mso-style-priority:72;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.5in;
	mso-add-space:auto;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	font-size:12.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:750540515;
	mso-list-type:hybrid;
	mso-list-template-ids:215645700 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.3in;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:1.8in;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.3in;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.8in;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:3.3in;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.8in;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.3in;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:4.8in;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Changes from 16 =
to 17:<o:p></o:p></p><p class=3DMsoListParagraph style=3D'mso-margin-top-al=
t:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:.8in;text-indent:-.2=
5in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:I=
gnore'>1.<span style=3D'font:7.0pt "Times New Roman"'> </span></span><![end=
if]>Ticket #59 &#8211; rename Capture Scene Entry (CSE) to Capture Scene Vi=
ew (CSV)<o:p></o:p></p><p class=3DMsoListParagraph style=3D'mso-margin-top-=
alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:.8in;text-indent:-=
.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list=
:Ignore'>2.<span style=3D'font:7.0pt "Times New Roman"'> </span></span><![e=
ndif]>Ticket #60 &#8211; rename Global CSE List to Global View List<o:p></o=
:p></p><p class=3DMsoListParagraph style=3D'mso-margin-top-alt:0in;margin-r=
ight:0in;margin-bottom:6.0pt;margin-left:.8in;text-indent:-.25in;mso-list:l=
0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>3.<span=
 style=3D'font:7.0pt "Times New Roman"'> </span></span><![endif]>Ticket #61=
 &#8211; Proposal for describing the coordinate system.&nbsp; Describe it b=
etter, without conflicts if cameras point in different directions.<o:p></o:=
p></p><p class=3DMsoListParagraph style=3D'mso-margin-top-alt:0in;margin-ri=
ght:0in;margin-bottom:6.0pt;margin-left:.8in;text-indent:-.25in;mso-list:l0=
 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>4.<span =
style=3D'font:7.0pt "Times New Roman"'> </span></span><![endif]>Minor clari=
fications and improved wording for Synchronisation Identity, MCC, Simultane=
ous Transmission Set.<o:p></o:p></p><p class=3DMsoListParagraph style=3D'ms=
o-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:.8in;=
text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span styl=
e=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New Roman"'> </spa=
n></span><![endif]>Add definitions for CLUE-capable device and CLUE-enabled=
 call, taken from the signaling draft.<o:p></o:p></p><p class=3DMsoListPara=
graph style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;=
margin-left:.8in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !support=
Lists]><span style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times N=
ew Roman"'> </span></span><![endif]>Update definitions of Capture Device, M=
edia Consumer, Media Provider, Endpoint, MCU, MCC.<o:p></o:p></p><p class=
=3DMsoListParagraph style=3D'mso-margin-top-alt:0in;margin-right:0in;margin=
-bottom:6.0pt;margin-left:.8in;text-indent:-.25in;mso-list:l0 level1 lfo1'>=
<![if !supportLists]><span style=3D'mso-list:Ignore'>7.<span style=3D'font:=
7.0pt "Times New Roman"'> </span></span><![endif]>Replace &quot;middle box&=
quot; with &quot;MCU&quot;.<o:p></o:p></p><p class=3DMsoListParagraph style=
=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left=
:.8in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><spa=
n style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New Roman"'>=
 </span></span><![endif]>Explicitly state there can also be Media Captures =
that are not included in a Capture Scene View.<o:p></o:p></p><p class=3DMso=
ListParagraph style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-botto=
m:6.0pt;margin-left:.8in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt =
"Times New Roman"'> </span></span><![endif]>Explicitly state &quot;A single=
 Encoding Group MAY refer to encodings for different media types.&quot;<o:p=
></o:p></p><p class=3DMsoListParagraph style=3D'mso-margin-top-alt:0in;marg=
in-right:0in;margin-bottom:6.0pt;margin-left:.8in;text-indent:-.25in;mso-li=
st:l0 level1 lfo1'><![if !supportLists]><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>10.<span s=
tyle=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span></span><![=
endif]>In example 12.1.1 add axes and audio captures to the diagram, and de=
scribe placement of microphones.<span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif"'><o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin=
-left:.8in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Times New Roman"'>&=
nbsp;&nbsp; </span></span></span><![endif]>Add references to data model and=
 signaling drafts.<span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif"'><o:p></o:p></span></p><p class=3DMsoListParagraph style=3D'mso-m=
argin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:.8in;tex=
t-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso=
-list:Ignore'>12.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span></span><![endif]>Split references into Normative and Informat=
ive sections.&nbsp; Add heading number for references section.<span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span>=
</p><p class=3DMsoNormal style=3D'margin-bottom:6.0pt'><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal style=3D'margin-bottom:6.0pt'><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif"'>Mark<o:p></o:p></span></p></di=
v></body></html>=

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CB4CRPMBOXPRD08p_--


From nobody Mon Sep 29 07:38:44 2014
Return-Path: <rohanse2@cisco.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E82711A876C for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 07:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.687
X-Spam-Level: 
X-Spam-Status: No, score=-14.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_111=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jyRcQa8jhi6m for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 07:38:36 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEEB61A875E for <clue@ietf.org>; Mon, 29 Sep 2014 07:38:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1426; q=dns/txt; s=iport; t=1412001517; x=1413211117; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=z61NDtSUku/XA+pUqjVOHqkcd5cihvn3FnU1mmEvy3Y=; b=CWarykNGTnRsPd8Q8mafL88bTvvWOm3zxkdjt1krvxaoBhkgwHLbtqy1 5scHFtRhPfJchtrobIeiPWZCeVv5gMvZQHeBNuQW4H/Q03s/GYM5kIsCj nmNPESQ/ZOGpZHNAVHrsxo9WKiU4f6wMX1RFgOOU5UjJ656TmBfBsjwQg s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjAKAJRuKVStJssW/2dsb2JhbABgg2G2bQUBcpJ/CodOAoEkAXuEBAEBBAEBATU2ChELGAkWDwkDAgECARUwEwYCAQGIOg2/PAETBIYSihMWhDUBBJ0oh1KOC4IggUQ8L4JKAQEB
X-IronPort-AV: E=Sophos;i="5.04,620,1406592000"; d="scan'208";a="193392897"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 29 Sep 2014 14:38:35 +0000
Received: from [10.47.200.91] ([10.47.200.91]) (authenticated bits=0) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s8TEcVEt001318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <clue@ietf.org>; Mon, 29 Sep 2014 14:38:33 GMT
Message-ID: <54296EE8.4040709@cisco.com>
Date: Mon, 29 Sep 2014 15:38:32 +0100
From: Robert Hansen <rohanse2@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: clue@ietf.org
References: <542906C3.5030502@nteczone.com>
In-Reply-To: <542906C3.5030502@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: rohanse2
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/M7QjFGljQJ23DX4U1HTZ4gcOkR8
Subject: Re: [clue] Examples in draft-ietf-clue-signaling-03 and draft-ietf-clue-signaling-03
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 14:38:41 -0000

Hi Christian,

Good catch - thanks. Will make sure that gets fixed in -04 of the 
signalling doc.

Rob

On 29/09/14 08:14, Christian Groves wrote:
> There's an error that seems to have crept into the CLUE SDP example 
> syntax in our documents.
>
> The RTCWeb-datachannel uses an SCTP over DTLS transport i.e. 
> DTLS/SCTP. Whereas in the examples where CLUE is involved SCTP/DTLS is 
> specified. We should probably update that.
>
> Also the latest draft draft-ietf-mmusic-sctp-sdp-07 has changed the 
> syntax for specifying a SCTP m-line.
>
> So:
> [draft-ietf-clue-datachannel-01]/5.8. Example
> m=application 54111 SCTP/DTLS 54111
> a=sctpmap:54111 webrtc-datachannel
>
> could be changed to:
> m=application 54111 DTLS/SCTP webrtc-datachannel
> a=fmtp:webrtc-datachannel max-message-size=100000
> a=sctp-port 5000
>
> more correctly to describe a "CLUE datachannel" the webrtc-datachannel 
> would need to be added to a CLUE group. Therefore I think the 
> following is probably a better example:
> a=group:CLUE 3
> ...
> m=application 54111 DTLS/SCTP webrtc-datachannel
> a=fmtp:webrtc-datachannel max-message-size=100000
> a=sctp-port 5000
> a=mid:3
>
> draft-ietf-clue-signaling-03 needs to be updated accordingly.
>
> Regards, Christian
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Mon Sep 29 07:52:40 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AF5E1A8723 for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 07:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhYCyh_8lIA9 for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 07:52:34 -0700 (PDT)
Received: from mail1.bemta7.messagelabs.com (mail1.bemta7.messagelabs.com [216.82.254.99]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38E351A6FAD for <clue@ietf.org>; Mon, 29 Sep 2014 07:52:34 -0700 (PDT)
Received: from [216.82.254.20:40682] by server-3.bemta-7.messagelabs.com id 9B/18-01770-03279245; Mon, 29 Sep 2014 14:52:32 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-10.tower-47.messagelabs.com!1412002351!14979478!1
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.12.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20688 invoked from network); 29 Sep 2014 14:52:32 -0000
Received: from crpehubprd01.polycom.com (HELO Crpehubprd01.polycom.com) (140.242.64.158) by server-10.tower-47.messagelabs.com with AES128-SHA encrypted SMTP; 29 Sep 2014 14:52:32 -0000
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by Crpehubprd01.polycom.com ([::1]) with mapi; Mon, 29 Sep 2014 07:52:31 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "clue@ietf.org" <clue@ietf.org>
Date: Mon, 29 Sep 2014 07:52:29 -0700
Thread-Topic: data model comments
Thread-Index: Ac/b8nrKqyLUQJc7TlCmPnF8lXn3Uw==
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.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_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0CRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/6iQ5FlwMmdxwZayXMDL2YVe3hdk
Subject: [clue] data model comments
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 14:52:37 -0000

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

Hi,

I'm sorry I won't be able to attend the design team discussion tomorrow abo=
ut the data model.  I have a few more comments here related to the new fram=
ework updates that impact the data model.  This is in addition to my commen=
ts on the list from July 21<http://www.ietf.org/mail-archive/web/clue/curre=
nt/msg03995.html>.

Update names of <sceneEntry> and <globalSceneEntries> to better match new t=
erms in framework, according to Ticket #59 and Ticket #60.

In the data model, it looks like the only way to associate a capture with a=
 scene is through a Capture Scene Entry (see <sceneEntriesType>) (now calle=
d CSV).  The framework says media captures are associated with a particular=
 scene.  Framework-17 now says a media capture does not have to be referenc=
ed by a CSV.  So linking a capture to a scene through a CSV can't be the on=
ly way to make the association between capture and scene.  Should <captureS=
ceneType> include a <mediaCapturesType> to fix this?

10.4.2 <captureArea> should say it is for video only.

16 <encodingGroup> - can include different media types in the same encoding=
 group

Regards,
Mark


--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0CRPMBOXPRD08p_
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"Micros=
oft Word 14 (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;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi,<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I&#8217;m =
sorry I won&#8217;t be able to attend the design team discussion tomorrow a=
bout the data model.&nbsp; I have a few more comments here related to the n=
ew framework updates that impact the data model.&nbsp; This is in addition =
to my <a href=3D"http://www.ietf.org/mail-archive/web/clue/current/msg03995=
.html">comments on the list from July 21</a>.<o:p></o:p></p><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Update names of &lt;sceneEn=
try&gt; and &lt;globalSceneEntries&gt; to better match new terms in framewo=
rk, according to Ticket #59 and Ticket #60.<o:p></o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>In the data model, it looks l=
ike the only way to associate a capture with a scene is through a Capture S=
cene Entry (see &lt;sceneEntriesType&gt;) (now called CSV).&nbsp; The frame=
work says media captures are associated with a particular scene.&nbsp; Fram=
ework-17 now says a media capture does not have to be referenced by a CSV.&=
nbsp; So linking a capture to a scene through a CSV can&#8217;t be the only=
 way to make the association between capture and scene.&nbsp; Should &lt;ca=
ptureSceneType&gt; include a &lt;mediaCapturesType&gt; to fix this?<o:p></o=
:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>10.4.=
2 &lt;captureArea&gt; should say it is for video only.<o:p></o:p></p><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>16 &lt;encodingGro=
up&gt; - can include different media types in the same encoding group<o:p><=
/o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Reg=
ards,<o:p></o:p></p><p class=3DMsoNormal>Mark<o:p></o:p></p><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0CRPMBOXPRD08p_--


From nobody Mon Sep 29 10:23:47 2014
Return-Path: <roberta.presta@unina.it>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD301A8A50 for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 10:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.036
X-Spam-Level: 
X-Spam-Status: No, score=-0.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6YnA4ifhQ3D for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 10:23:40 -0700 (PDT)
Received: from brc2.unina.it (brc2.unina.it [192.132.34.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DB741A8A48 for <clue@ietf.org>; Mon, 29 Sep 2014 10:23:30 -0700 (PDT)
X-ASG-Debug-ID: 1412011406-05f2753c1d2f1dbb0001-dOUo1C
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by brc2.unina.it with ESMTP id SiwPYBa1eiFKN2De (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Mon, 29 Sep 2014 19:23:27 +0200 (CEST)
X-Barracuda-Envelope-From: roberta.presta@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.62
Received: from [127.0.0.1] ([193.206.114.54]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id s8THNP7Y020781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 29 Sep 2014 19:23:26 +0200
Message-ID: <54299594.6060705@unina.it>
Date: Mon, 29 Sep 2014 19:23:32 +0200
From: Roberta Presta <roberta.presta@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Duckworth, Mark" <Mark.Duckworth@polycom.com>, "clue@ietf.org" <clue@ietf.org>
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com>
X-ASG-Orig-Subj: Re: [clue] data model comments
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com>
Content-Type: multipart/alternative; boundary="------------060009040300060605000202"
X-Barracuda-Connect: smtp2.unina.it[192.132.34.62]
X-Barracuda-Start-Time: 1412011407
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.42:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210
X-Barracuda-Spam-Score: -2.02
X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=BSF_SC0_MISMATCH_TO, HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.10030 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO    Envelope rcpt doesn't match header 0.00 HTML_MESSAGE           BODY: HTML included in message
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/4yvEMHVyf2xTDhf2hg5C0Zqsh-Y
Subject: Re: [clue] data model comments
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 17:23:42 -0000

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

Hi Mark,
please see below.

Il 29/09/2014 16:52, Duckworth, Mark ha scritto:
>
> Hi,
>
> I'm sorry I won't be able to attend the design team discussion 
> tomorrow about the data model.  I have a few more comments here 
> related to the new framework updates that impact the data model.  This 
> is in addition to my comments on the list from July 21 
> <http://www.ietf.org/mail-archive/web/clue/current/msg03995.html>.
>
I'm sending you the reply after this email.
>
> Update names of <sceneEntry> and <globalSceneEntries> to better match 
> new terms in framework, according to Ticket #59 and Ticket #60.
>
Ok.
>
> In the data model, it looks like the only way to associate a capture 
> with a scene is through a Capture Scene Entry (see <sceneEntriesType>) 
> (now called CSV). The framework says media captures are associated 
> with a particular scene.  Framework-17 now says a media capture does 
> not have to be referenced by a CSV.  So linking a capture to a scene 
> through a CSV can't be the only way to make the association between 
> capture and scene.  Should <captureSceneType> include a 
> <mediaCapturesType> to fix this?
>
Media captures have a mandatory <captureSceneIDREF> to refer to a 
capture scene. Currently in the datamodel draft there is no text saying 
that they must appear within capture scene view(s).
In a capture scene, besides the <sceneViews> element,  we could add a 
<mediaCaptures> section for listing media captures that do not appear in 
capture scene views, but it is not strictly necessary, thanks to the 
<captureSceneIDREF>.  If we do not add this further section, we could 
just clarify in the text.
Which solution is better?

> 10.4.2 <captureArea> should say it is for video only.
>
OK.
>
> 16 <encodingGroup> - can include different media types in the same 
> encoding group
>
Ok.
>
> Regards,
>
> Mark
>
>
Thank you,

Roberta


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Mark,<br>
      please see below.<br>
      <br>
      Il 29/09/2014 16:52, Duckworth, Mark ha scritto:<br>
    </div>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (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;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">Hi,<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">I&#8217;m sorry I won&#8217;t be able to attend the
          design team discussion tomorrow about the data model.&nbsp; I have
          a few more comments here related to the new framework updates
          that impact the data model.&nbsp; This is in addition to my <a
            moz-do-not-send="true"
            href="http://www.ietf.org/mail-archive/web/clue/current/msg03995.html">comments
            on the list from July 21</a>.</p>
      </div>
    </blockquote>
    I'm sending you the reply after this email.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Update names of &lt;sceneEntry&gt; and
          &lt;globalSceneEntries&gt; to better match new terms in
          framework, according to Ticket #59 and Ticket #60.<o:p></o:p></p>
      </div>
    </blockquote>
    Ok.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">In the data model, it looks like the only
          way to associate a capture with a scene is through a Capture
          Scene Entry (see &lt;sceneEntriesType&gt;) (now called CSV).&nbsp;
          The framework says media captures are associated with a
          particular scene.&nbsp; Framework-17 now says a media capture does
          not have to be referenced by a CSV.&nbsp; So linking a capture to a
          scene through a CSV can&#8217;t be the only way to make the
          association between capture and scene.&nbsp; Should
          &lt;captureSceneType&gt; include a &lt;mediaCapturesType&gt;
          to fix this?<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    Media captures have a mandatory &lt;captureSceneIDREF&gt; to refer
    to a capture scene. Currently in the datamodel draft there is no
    text saying that they must appear within capture scene view(s).<br>
    In a capture scene, besides the &lt;sceneViews&gt; element,&nbsp; we
    could add a &lt;mediaCaptures&gt; section for listing media captures
    that do not appear in capture scene views, but it is not strictly
    necessary, thanks to the &lt;captureSceneIDREF&gt;.&nbsp; If we do not
    add this further section, we could just clarify in the text. <br>
    Which solution is better?<br>
    <br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">10.4.2 &lt;captureArea&gt; should say it is
          for video only.</p>
      </div>
    </blockquote>
    OK.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">16 &lt;encodingGroup&gt; - can include
          different media types in the same encoding group<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    Ok.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">Regards,<o:p></o:p></p>
        <p class="MsoNormal">Mark<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
      <br>
    </blockquote>
    Thank you, <br>
    <br>
    Roberta<br>
    <br>
  </body>
</html>

--------------060009040300060605000202--


From nobody Mon Sep 29 10:27:36 2014
Return-Path: <roberta.presta@unina.it>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5B11A8A87 for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 10:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.164
X-Spam-Level: *
X-Spam-Status: No, score=1.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, J_CHICKENPOX_25=0.6, J_CHICKENPOX_27=0.6, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8cjookAOqL6 for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 10:27:20 -0700 (PDT)
Received: from brc2.unina.it (brc2.unina.it [192.132.34.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E0081A8A6E for <clue@ietf.org>; Mon, 29 Sep 2014 10:26:56 -0700 (PDT)
X-ASG-Debug-ID: 1412011613-05f2753c1d2f1dec0001-dOUo1C
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by brc2.unina.it with ESMTP id CrCXNKHePUVi3w8S (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Mon, 29 Sep 2014 19:26:53 +0200 (CEST)
X-Barracuda-Envelope-From: roberta.presta@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.62
Received: from [127.0.0.1] ([193.206.114.54]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id s8THQqgu021031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 29 Sep 2014 19:26:53 +0200
Message-ID: <54299663.1030007@unina.it>
Date: Mon, 29 Sep 2014 19:26:59 +0200
From: Roberta Presta <roberta.presta@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Duckworth, Mark" <Mark.Duckworth@polycom.com>, "clue@ietf.org" <clue@ietf.org>
References: <5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com>
X-ASG-Orig-Subj: Re: [clue] pre-WGLC comments on data model
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com>
Content-Type: multipart/alternative; boundary="------------090902080907060201060804"
X-Barracuda-Connect: smtp2.unina.it[192.132.34.62]
X-Barracuda-Start-Time: 1412011613
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.42:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210
X-Barracuda-Spam-Score: -2.02
X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=BSF_SC0_MISMATCH_TO, HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.10030 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO    Envelope rcpt doesn't match header 0.00 HTML_MESSAGE           BODY: HTML included in message
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/pHBL5vQLXuRrbxZ5npxkKy2lRXk
Subject: Re: [clue] pre-WGLC comments on data model
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 17:27:23 -0000

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

Dear Mark,
thank you very much for your review.
We are about to upload version 7.
Please see below our answers.

Il 21/07/2014 16:34, Duckworth, Mark ha scritto:
>
> I thought we agreed <capturePoint> should be optional, and some text 
> and the XML for it needs to be updated.  See the previous discussion here:
>
> http://www.ietf.org/mail-archive/web/clue/current/msg03594.html
>
[RP] Capture point is now optional, both in the schema definition and in 
the textual description.
>
> >>>>> Minor Issues:
>
> Is it possible to have a media capture type that is not video or audio 
> or text?  Could it be done using just the mediaCaptureType generic 
> element?  Or would there need to be a new element type that inherits 
> from mediaCaptureType?  Is it worth mentioning this in the 
> extensibility section?
>

[RP] Actually, elements of type mediaCaptureType cannot be instantied 
since  mediaCaptureType is an abstract type.
You need to define a new type inheriting from the current 
mediaCaptureType and specializing it, as done for audioCaptureType and 
videoCaptureType.
We provide a first example of this kind of extension in the n version in 
the Extensibility section.

> <capturedMedia> element -- how about calling this something like 
> <mediaType> instead?  Would this be better as an attribute rather than 
> an element, like the "mediaType" attribute for CSE in section 15.3?
>

[RP] We changed the schema accordingly.
Please note that, when changing from version 5 to version 6, we removed 
all the mediaType attributes from scene views and encoding groups since 
they were considered unnecessary. The reason was that it is possible to 
understand the media type of such envelopes by looking at the media type 
of the first item contained in them.
In version 6 we did not append the diff section with version 5, but we 
discussed it in the IETF 90 slides:
http://www.ietf.org/proceedings/90/slides/slides-90-clue-1.pdf
This is the link to the mailing list discussion:
http://www.ietf.org/mail-archive/web/clue/current/msg03950.html ("Do we 
need the mediaType attribute if mediaType is also an attribute of the 
referenced media captures?")

> "simultaneousSetType" -- the framework says "For shorthand 
> convenience, a Provider MAY describe a Simultaneous Transmission Set 
> in terms of Capture Scene Entries and Capture Scenes".  Looks like the 
> data model allows using CSE for shorthand, but not Capture Scenes.  So 
> should there be a "sceneIDREF" element here?  Also, as Paul noted in 
> his review of the framework, there needs to be a way to identify the 
> media type for an STS if it includes only scenes.  I suggest adding a 
> <capturedMedia> (or <mediaType>) element to the simultaneousSetType, 
> with the same meaning it has elsewhere.  Then all the media captures 
> referenced in the STS must be of that media type.
>
[RP] We added both a <captureSceneIDREF> list and the mediaType 
attribute to solve the issue as Paul and you suggested.
>
> "captureEncodingType" - I agree with Christian it would be good to use 
> "mm" for millimeters in the schema.  So the scaleType would have a 
> line for enumeration value="mm" instead of value="millimeters".
>
[RP] Ok.
>
> "maxGroupBandwidth" -- I think we should specify the units for this 
> are bits per second.  The type is "xs:integer", but I think we should 
> avoid using numeric types that don't have a range limit.  How about 
> using "xs:unsignedLong" instead?
>
[RP] Ok, we changed both the schema and the description of 
<maxGroupBandwidth>.
>
> "pointType" - I think we should avoid using numeric types that don't 
> have a range limit.  How about using "xs:int" instead of 
> "xs:decimal"?  I was assuming we do not need to represent fractional 
> millimeters here, I was always assuming an int type.  If people think 
> we need to represent fractions, then should we use xs:float instead of 
> xs:decimal?
>
[RP] No problem with changing the type. We prefer xs:float instead of 
xs:decimal.
>
> "sceneEntryType" -- is the schema for this missing an attribute called 
> "mediaType"?  This is described in section 15.3, but I don't see it in 
> the schema.
>
[RP] Please see the mediaType issue above. Do you think we still need it?
>
> 10.4 paragraph 3 -- it gives switched captures as an example of non 
> spatially definable, but the framework says "For a switched capture 
> that switches between different sections within a larger area, the 
> area of capture MUST use coordinates for the larger potential area".  
> So right now this looks like a contradiction.  I think the framework 
> is correct though.
>
[RP] We removed the sentence.
>
> 10.6 <content> the text implies there must be some references to 
> captures or CSEs, but the framework says "A MCC MAY contain no 
> references to other Captures to indicate that the MCC contains content 
> from multiple sources but no information regarding those sources is 
> given."  The schema looks okay, as it has minOccurs="0" for 
> "captureIDREF" and "sceneEntryIDREF".  And it also has minOccurs="0" 
> for "content" in the media capture type in section 10.  So I think the 
> schema is fine, but the text is wrong that says this stuff is mandatory.
>
[RP] Corrected.
>
> 10.7 <synchronizationID> - "...contain at each time captures coming 
> from the same endpoint".  I think it is more flexible than the same 
> endpoint.  The framework says "It is the Provider that determines what 
> the source for the Captures is, so a Provider can choose how to group 
> together Single Media Captures for the purpose of keeping them 
> synchronized according to the SynchronisationID attribute."  The 
> provider is allowed flexibility in choosing how to switch, even when 
> it gives a syncID.  For example, the provider might decide to take 
> video streams from three separate single camera endpoints and switch 
> them together to send to a consumer that receives three video streams 
> simultaneously.
>
[RP] Corrected.
>
> audio captures -- needs to be updated for recent decisions to remove 
> audioChannelFormat, add the sensitivity pattern, and disallow area of 
> capture.
>
[RP] Done.
>
> 21 <clueInfo> - is the intent to remove this section, since an 
> advertisement is defined in the protocol document?
>
[RP] The intent is to remove this section as soon as the ADV structure 
is stably agreed, otherwise we have to modify the data model examples 
each time the ADV structure changes.

> 22 extensibility -- is there a way to extend an enumerated type to 
> include more values?
>
> >>>>> Editorial Issues:
>
> The title page says "Intended status: Informational", but I think this 
> should be Standards Track.
>
[RP] Done.
>
> 10.4 paragraph 3 "Capture of this kind are for example those related 
> to registrations..."  I'm not sure what "registrations" means here.
>
[RP] Replaced with recordings.
>
> 10.6 has (MMCC), I think this should be (MCC)
>
[RP] Done.
>
> 10.15 "refers to my means..." should be "refers to by means"
>
[RP] Done.
>
> Regards,
>
> Mark
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Dear Mark, <br>
    <div class="moz-cite-prefix">thank you very much for your review.<br>
      We are about to upload version 7.<br>
      Please see below our answers.<br>
      <br>
      Il 21/07/2014 16:34, Duckworth, Mark ha scritto:<br>
    </div>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1"><o:p>&nbsp;</o:p>
        <p class="MsoNormal">I thought we agreed &lt;capturePoint&gt;
          should be optional, and some text and the XML for it needs to
          be updated.&nbsp; See the previous discussion here:<o:p></o:p></p>
        <p class="MsoNormal"><a moz-do-not-send="true"
            href="http://www.ietf.org/mail-archive/web/clue/current/msg03594.html"><span
              style="color:windowtext">http://www.ietf.org/mail-archive/web/clue/current/msg03594.html</span></a><o:p></o:p></p>
      </div>
    </blockquote>
    [RP] Capture point is now optional, both in the schema definition
    and in the textual description.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">&gt;&gt;&gt;&gt;&gt; Minor Issues:<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Is it possible to have a media capture type
          that is not video or audio or text?&nbsp; Could it be done using
          just the mediaCaptureType generic element?&nbsp; Or would there
          need to be a new element type that inherits from
          mediaCaptureType?&nbsp; Is it worth mentioning this in the
          extensibility section?<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    <br>
    [RP] Actually, elements of type mediaCaptureType cannot be
    instantied since&nbsp; mediaCaptureType is an abstract type.<br>
    You need to define a new type inheriting from the current
    mediaCaptureType and specializing it, as done for audioCaptureType
    and videoCaptureType.<br>
    We provide a first example of this kind of extension in the n
    version in the Extensibility section.<br>
    <br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">&lt;capturedMedia&gt; element &#8211; how about
          calling this something like &lt;mediaType&gt; instead?&nbsp; Would
          this be better as an attribute rather than an element, like
          the &#8220;mediaType&#8221; attribute for CSE in section 15.3?<o:p></o:p></p>
      </div>
    </blockquote>
    <br>
    [RP] We changed the schema accordingly.<br>
    Please note that, when changing from version 5 to version 6, we
    removed all the mediaType attributes from scene views and encoding
    groups since they were considered unnecessary. The reason was that
    it is possible to understand the media type of such envelopes by
    looking at the media type of the first item contained in them.<br>
    <font color="#000000">In version 6 we did not append the diff
      section with version 5, but we discussed it in the IETF 90 slides:<br>
      <a class="moz-txt-link-freetext"
        href="http://www.ietf.org/proceedings/90/slides/slides-90-clue-1.pdf">http://www.ietf.org/proceedings/90/slides/slides-90-clue-1.pdf</a><br>
    </font> This is the link to the mailing list discussion:<br>
    <a class="moz-txt-link-freetext"
      href="http://www.ietf.org/mail-archive/web/clue/current/msg03950.html">http://www.ietf.org/mail-archive/web/clue/current/msg03950.html</a>
    ("<font color="#000000">Do we need the mediaType attribute if
      mediaType is also an attribute of the referenced media captures?")</font><o:p><br>
      <br>
    </o:p>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">&#8220;simultaneousSetType&#8221; &#8211; the framework says
          &#8220;For shorthand convenience, a Provider MAY describe a
          Simultaneous Transmission Set in terms of Capture Scene
          Entries and Capture Scenes&#8221;.&nbsp; Looks like the data model allows
          using CSE for shorthand, but not Capture Scenes. &nbsp;So should
          there be a &#8220;sceneIDREF&#8221; element here? &nbsp;Also, as Paul noted in
          his review of the framework, there needs to be a way to
          identify the media type for an STS if it includes only
          scenes.&nbsp; I suggest adding a <span
            style="font-size:9.5pt;font-family:Courier">&lt;capturedMedia&gt;</span>
          (or &lt;mediaType&gt;) element to the simultaneousSetType,
          with the same meaning it has elsewhere.&nbsp; Then all the media
          captures referenced in the STS must be of that media type.<o:p></o:p></p>
      </div>
    </blockquote>
    [RP] We added both a &lt;captureSceneIDREF&gt; list and the
    mediaType attribute to solve the issue as Paul and you suggested.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">&#8220;captureEncodingType&#8221; - I agree with
          Christian it would be good to use &#8220;mm&#8221; for millimeters in the
          schema.&nbsp; So the scaleType would have a line for enumeration
          value=&#8221;mm&#8221; instead of value=&#8221;millimeters&#8221;.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] Ok.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">&#8220;maxGroupBandwidth&#8221; &#8211; I think we should
          specify the units for this are bits per second.&nbsp; The type is
          &#8220;xs:integer&#8221;, but I think we should avoid using numeric types
          that don&#8217;t have a range limit.&nbsp; How about using
          &#8220;xs:unsignedLong&#8221; instead?</p>
      </div>
    </blockquote>
    [RP] Ok, we changed both the schema and the description of
    &lt;maxGroupBandwidth&gt;.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">&#8220;pointType&#8221; - I think we should avoid using
          numeric types that don&#8217;t have a range limit.&nbsp; How about using
          &#8220;xs:int&#8221; instead of &#8220;xs:decimal&#8221;?&nbsp; I was assuming we do not
          need to represent fractional millimeters here, I was always
          assuming an int type.&nbsp; If people think we need to represent
          fractions, then should we use xs:float instead of xs:decimal?</p>
      </div>
    </blockquote>
    [RP] No problem with changing the type. We prefer xs:float instead
    of xs:decimal. <br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">&#8220;sceneEntryType&#8221; &#8211; is the schema for this
          missing an attribute called &#8220;mediaType&#8221;?&nbsp; This is described in
          section 15.3, but I don&#8217;t see it in the schema.</p>
      </div>
    </blockquote>
    [RP] Please see the mediaType issue above. Do you think we still
    need it?<o:p> <br>
    </o:p>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">10.4 paragraph 3 &#8211; it gives switched
          captures as an example of non spatially definable, but the
          framework says &#8220;For a switched capture that switches between
          different sections within a larger area, the area of capture
          MUST use coordinates for the larger potential area&#8221;.&nbsp; So right
          now this looks like a contradiction.&nbsp; I think the framework is
          correct though.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] We removed the sentence.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">10.6 &lt;content&gt; the text implies there
          must be some references to captures or CSEs, but the framework
          says &#8220;A MCC MAY contain no references to other Captures to
          indicate that the MCC contains content from multiple sources
          but no information regarding those sources is given.&#8221;&nbsp; The
          schema looks okay, as it has minOccurs=&#8221;0&#8221; for &#8220;captureIDREF&#8221;
          and &#8220;sceneEntryIDREF&#8221;.&nbsp; And it also has minOccurs=&#8221;0&#8221; for
          &#8220;content&#8221; in the media capture type in section 10.&nbsp; So I think
          the schema is fine, but the text is wrong that says this stuff
          is mandatory.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] Corrected.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">10.7 &lt;synchronizationID&gt; -
          &#8220;...contain at each time captures coming from the same
          endpoint&#8221;.&nbsp; I think it is more flexible than the same
          endpoint.&nbsp; The framework says &#8220;It is the Provider that
          determines what the source for the Captures is, so a Provider
          can choose how to group together Single Media Captures for the
          purpose of keeping them synchronized according to the
          SynchronisationID attribute.&#8221;&nbsp; The provider is allowed
          flexibility in choosing how to switch, even when it gives a
          syncID.&nbsp; For example, the provider might decide to take video
          streams from three separate single camera endpoints and switch
          them together to send to a consumer that receives three video
          streams simultaneously.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] Corrected.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">audio captures &#8211; needs to be updated for
          recent decisions to remove audioChannelFormat, add the
          sensitivity pattern, and disallow area of capture.<o:p></o:p></p>
      </div>
    </blockquote>
    [RP] Done.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">21 &lt;clueInfo&gt; - is the intent to
          remove this section, since an advertisement is defined in the
          protocol document?<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] The intent is to remove this section as soon as the ADV
    structure is stably agreed, otherwise we have to modify the data
    model examples each time the ADV structure changes.<br>
    <br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">22 extensibility &#8211; is there a way to extend
          an enumerated type to include more values?<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">&gt;&gt;&gt;&gt;&gt; Editorial Issues:<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">The title page says &#8220;Intended status:
          Informational&#8221;, but I think this should be Standards Track.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] Done.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">10.4 paragraph 3 &#8220;Capture of this kind are
          for example those related to registrations...&#8221;&nbsp; I&#8217;m not sure
          what &#8220;registrations&#8221; means here.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] Replaced with recordings.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">10.6 has (MMCC), I think this should be
          (MCC)<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] Done.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">10.15 &#8220;refers to my means...&#8221; should be
          &#8220;refers to by means&#8221;<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    [RP] Done.<br>
    <blockquote
cite="mid:5C4AC54BFF7A0842A6A11F554D6FB52F078BE5B034@CRPMBOXPRD08.polycom.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">Regards,<o:p></o:p></p>
        <p class="MsoNormal">Mark<o:p></o:p></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
clue mailing list
<a class="moz-txt-link-abbreviated" href="mailto:clue@ietf.org">clue@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/clue">https://www.ietf.org/mailman/listinfo/clue</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090902080907060201060804--


From nobody Mon Sep 29 10:34:56 2014
Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15FFB1A8A56 for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 10:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zk7FKr1EEAn for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 10:34:53 -0700 (PDT)
Received: from mail1.bemta8.messagelabs.com (mail1.bemta8.messagelabs.com [216.82.243.197]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D3E61A8F43 for <clue@ietf.org>; Mon, 29 Sep 2014 10:34:52 -0700 (PDT)
Received: from [216.82.241.100:47781] by server-5.bemta-8.messagelabs.com id 87/A9-05345-C3899245; Mon, 29 Sep 2014 17:34:52 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-9.tower-220.messagelabs.com!1412012081!16389925!3
X-Originating-IP: [140.242.64.158]
X-StarScan-Received: 
X-StarScan-Version: 6.12.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11694 invoked from network); 29 Sep 2014 17:34:50 -0000
Received: from crpehubprd01.polycom.com (HELO crpehubprd02.polycom.com) (140.242.64.158) by server-9.tower-220.messagelabs.com with AES128-SHA encrypted SMTP; 29 Sep 2014 17:34:50 -0000
Received: from CRPMBOXPRD08.polycom.com ([fe80::9050:ae9:abfa:9da8]) by crpehubprd02.polycom.com ([::1]) with mapi; Mon, 29 Sep 2014 10:34:46 -0700
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: Roberta Presta <roberta.presta@unina.it>, "clue@ietf.org" <clue@ietf.org>
Date: Mon, 29 Sep 2014 10:34:44 -0700
Thread-Topic: [clue] data model comments
Thread-Index: Ac/cChf8C9cqiaoPSnCBfrpbubZXSgAASUGQ
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922D1C@CRPMBOXPRD08.polycom.com>
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CC0@CRPMBOXPRD08.polycom.com> <54299594.6060705@unina.it>
In-Reply-To: <54299594.6060705@unina.it>
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_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922D1CCRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/x8vQIeF9DLcw8XuhCf7e8nyUPeI
Subject: Re: [clue] data model comments
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 17:34:55 -0000

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

Hi Roberta,

Sorry I forgot about the <captureSceneIDREF>, thanks for reminding me.  Tha=
t should be fine, with no need for any additional list of captures in a sce=
ne.

Mark

From: Roberta Presta [mailto:roberta.presta@unina.it]
Sent: Monday, September 29, 2014 1:24 PM
To: Duckworth, Mark; clue@ietf.org
Subject: Re: [clue] data model comments

Hi Mark,
please see below.

Il 29/09/2014 16:52, Duckworth, Mark ha scritto:
Hi,

I'm sorry I won't be able to attend the design team discussion tomorrow abo=
ut the data model.  I have a few more comments here related to the new fram=
ework updates that impact the data model.  This is in addition to my commen=
ts on the list from July 21<http://www.ietf.org/mail-archive/web/clue/curre=
nt/msg03995.html>.
I'm sending you the reply after this email.


Update names of <sceneEntry> and <globalSceneEntries> to better match new t=
erms in framework, according to Ticket #59 and Ticket #60.
Ok.


In the data model, it looks like the only way to associate a capture with a=
 scene is through a Capture Scene Entry (see <sceneEntriesType>) (now calle=
d CSV).  The framework says media captures are associated with a particular=
 scene.  Framework-17 now says a media capture does not have to be referenc=
ed by a CSV.  So linking a capture to a scene through a CSV can't be the on=
ly way to make the association between capture and scene.  Should <captureS=
ceneType> include a <mediaCapturesType> to fix this?

Media captures have a mandatory <captureSceneIDREF> to refer to a capture s=
cene. Currently in the datamodel draft there is no text saying that they mu=
st appear within capture scene view(s).
In a capture scene, besides the <sceneViews> element,  we could add a <medi=
aCaptures> section for listing media captures that do not appear in capture=
 scene views, but it is not strictly necessary, thanks to the <captureScene=
IDREF>.  If we do not add this further section, we could just clarify in th=
e text.
Which solution is better?


10.4.2 <captureArea> should say it is for video only.
OK.


16 <encodingGroup> - can include different media types in the same encoding=
 group

Ok.

Regards,
Mark


Thank you,

Roberta

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922D1CCRPMBOXPRD08p_
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=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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 bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'color:#1F497D'>Hi Roberta,<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>Sorry I forgot about the &lt;cap=
tureSceneIDREF&gt;, thanks for reminding me.&nbsp; That should be fine, wit=
h no need for any additional list of captures in a scene.<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>Mark<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o=
:p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;paddin=
g:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4D=
F 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</=
span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";=
color:windowtext'> Roberta Presta [mailto:roberta.presta@unina.it] <br><b>S=
ent:</b> Monday, September 29, 2014 1:24 PM<br><b>To:</b> Duckworth, Mark; =
clue@ietf.org<br><b>Subject:</b> Re: [clue] data model comments<o:p></o:p><=
/span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p cla=
ss=3DMsoNormal>Hi Mark,<br>please see below.<br><br>Il 29/09/2014 16:52, Du=
ckworth, Mark ha scritto:<o:p></o:p></p></div><blockquote style=3D'margin-t=
op:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal>Hi,<o:p></o:p></p><p cla=
ss=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>I&#8217;m sorry I =
won&#8217;t be able to attend the design team discussion tomorrow about the=
 data model.&nbsp; I have a few more comments here related to the new frame=
work updates that impact the data model.&nbsp; This is in addition to my <a=
 href=3D"http://www.ietf.org/mail-archive/web/clue/current/msg03995.html">c=
omments on the list from July 21</a>.<o:p></o:p></p></blockquote><p class=
=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New Roman",=
"serif"'>I'm sending you the reply after this email.<br><br><o:p></o:p></sp=
an></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>Updat=
e names of &lt;sceneEntry&gt; and &lt;globalSceneEntries&gt; to better matc=
h new terms in framework, according to Ticket #59 and Ticket #60.<o:p></o:p=
></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Time=
s New Roman","serif"'>Ok.<br><br><o:p></o:p></span></p><p class=3DMsoNormal=
>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>In the data model, it looks like=
 the only way to associate a capture with a scene is through a Capture Scen=
e Entry (see &lt;sceneEntriesType&gt;) (now called CSV).&nbsp; The framewor=
k says media captures are associated with a particular scene.&nbsp; Framewo=
rk-17 now says a media capture does not have to be referenced by a CSV.&nbs=
p; So linking a capture to a scene through a CSV can&#8217;t be the only wa=
y to make the association between capture and scene.&nbsp; Should &lt;captu=
reSceneType&gt; include a &lt;mediaCapturesType&gt; to fix this?<o:p></o:p>=
</p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span st=
yle=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Media captur=
es have a mandatory &lt;captureSceneIDREF&gt; to refer to a capture scene. =
Currently in the datamodel draft there is no text saying that they must app=
ear within capture scene view(s).<br>In a capture scene, besides the &lt;sc=
eneViews&gt; element,&nbsp; we could add a &lt;mediaCaptures&gt; section fo=
r listing media captures that do not appear in capture scene views, but it =
is not strictly necessary, thanks to the &lt;captureSceneIDREF&gt;.&nbsp; I=
f we do not add this further section, we could just clarify in the text. <b=
r>Which solution is better?<br><br><br><o:p></o:p></span></p><p class=3DMso=
Normal>10.4.2 &lt;captureArea&gt; should say it is for video only.<o:p></o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Tim=
es New Roman","serif"'>OK.<br><br><o:p></o:p></span></p><p class=3DMsoNorma=
l>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>16 &lt;encodingGroup&gt; - can =
include different media types in the same encoding group<o:p></o:p></p><p c=
lass=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span style=3D'f=
ont-size:12.0pt;font-family:"Times New Roman","serif"'>Ok.<br><br><o:p></o:=
p></span></p><p class=3DMsoNormal>Regards,<o:p></o:p></p><p class=3DMsoNorm=
al>Mark<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3D=
MsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","se=
rif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-bott=
om:12.0pt'><span style=3D'font-size:12.0pt;font-family:"Times New Roman","s=
erif"'>Thank you, <br><br>Roberta<o:p></o:p></span></p></div></div></body><=
/html>=

--_000_5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922D1CCRPMBOXPRD08p_--


From nobody Mon Sep 29 13:55:10 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15FBD1ABD39 for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 13:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Mqeil8Pdiax for <clue@ietfa.amsl.com>; Mon, 29 Sep 2014 13:55:06 -0700 (PDT)
Received: from resqmta-po-05v.sys.comcast.net (resqmta-po-05v.sys.comcast.net [96.114.154.164]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD14B1A9252 for <clue@ietf.org>; Mon, 29 Sep 2014 13:55:06 -0700 (PDT)
Received: from resomta-po-04v.sys.comcast.net ([96.114.154.228]) by resqmta-po-05v.sys.comcast.net with comcast id x8us1o00A4vw8ds018v4E2; Mon, 29 Sep 2014 20:55:04 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-04v.sys.comcast.net with comcast id x8v31o0063Ge9ey018v39l; Mon, 29 Sep 2014 20:55:03 +0000
Message-ID: <5429C727.7070407@alum.mit.edu>
Date: Mon, 29 Sep 2014 16:55:03 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CB4@CRPMBOXPRD08.polycom.com>
In-Reply-To: <5C4AC54BFF7A0842A6A11F554D6FB52F5C5A922CB4@CRPMBOXPRD08.polycom.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1412024104; bh=QqqGFMyGHGpQp3IqMRWRVpD8sYNsAn4YlkL+jw4L+ms=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=U9uUKK+mFdMOetKN6KxRfVeXGP151ekB2BQKvoZDF8g7hIJQtu8q4wjpo2+Adws+j aMlNNOoF3rKdSKlZFkOKoe8wN6PA//I28PSxnP02SJs3Jy6xbf7eiDwPEfyaQYb1FP KnY2AiUVVPCTcX3rw8jXvFkPIVP9Tg52U4Avs7Rn/SiAX1nECoESgF9nHt6FlZDSl5 cyfcCOnoH6/zeAFrAErmTDWvxTCUIsWwW73i4KrlRkjVlsf0LuzBsgFWqrvwtVI2P2 S6SNGV8eG3Ktdy0LdQIHlnIblonHUpk9wC5lSmrDO4GZR322tD7ZMJfqTP/J1vl00W +Fc8o5lzXJJfQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/2WGGecQP_9FNhIvB9fGnbeC286M
Subject: Re: [clue] Updates in framework-17
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 20:55:08 -0000

A few comments on the changes in this version:

Section 3:

    Global View: A set of references to one or more Capture Scene Views
    of the same media type that are defined within scenes of the same
    advertisement.  Each Global View in the list is a suggestion from
    the Provider to the Consumer for which CSVs provide a complete
    representation of the simultaneous captures provided by the
    Provider, across multiple scenes.

This has munged two things into one. It is in part a definition of 
Global View and in part a definition of Global View List. I think both 
should be in the definitions.

    Media Consumer: a CLUE-capable device that that is capable of
    receiving Capture Encodings

    Media Provider: a CLUE-capable device that is capable of sending
    Capture Encodings

I wonder if these defs should say "a CLUE-enabled* device.

Figure 1:

While this shows the Global View List, it doesn't show any Global Views. 
Ideally it would - each referencing Scene Views. But it may be hard to 
fit all that into the single diagram.

	Thanks,
	Paul


On 9/29/14 10:27 AM, Duckworth, Mark wrote:
> Changes from 16 to 17:
>
> 1.Ticket #59 – rename Capture Scene Entry (CSE) to Capture Scene View (CSV)
>
> 2.Ticket #60 – rename Global CSE List to Global View List
>
> 3.Ticket #61 – Proposal for describing the coordinate system.  Describe
> it better, without conflicts if cameras point in different directions.
>
> 4.Minor clarifications and improved wording for Synchronisation
> Identity, MCC, Simultaneous Transmission Set.
>
> 5.Add definitions for CLUE-capable device and CLUE-enabled call, taken
> from the signaling draft.
>
> 6.Update definitions of Capture Device, Media Consumer, Media Provider,
> Endpoint, MCU, MCC.
>
> 7.Replace "middle box" with "MCU".
>
> 8.Explicitly state there can also be Media Captures that are not
> included in a Capture Scene View.
>
> 9.Explicitly state "A single Encoding Group MAY refer to encodings for
> different media types."
>
> 10.In example 12.1.1 add axes and audio captures to the diagram, and
> describe placement of microphones.
>
> 11.Add references to data model and signaling drafts.
>
> 12.Split references into Normative and Informative sections.  Add
> heading number for references section.
>
> Mark
>
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>


From nobody Mon Sep 29 22:59:30 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 306681A01D6; Mon, 29 Sep 2014 22:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BA4dAtbIReqf; Mon, 29 Sep 2014 22:59:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E09301A019C; Mon, 29 Sep 2014 22:59:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140930055926.2775.75038.idtracker@ietfa.amsl.com>
Date: Mon, 29 Sep 2014 22:59:26 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/SlJxHYaoK9or8Ar7mw9oT21NM8I
Cc: clue@ietf.org
Subject: [clue] I-D Action: draft-ietf-clue-data-model-schema-07.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Sep 2014 05:59:28 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the ControLling mUltiple streams for tElepresence Working Group of the IETF.

        Title           : An XML Schema for the CLUE data model
        Authors         : Roberta Presta
                          Simon Pietro Romano
	Filename        : draft-ietf-clue-data-model-schema-07.txt
	Pages           : 59
	Date            : 2014-09-29

Abstract:
   This document provides an XML schema file for the definition of CLUE
   data model types.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-clue-data-model-schema/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-clue-data-model-schema-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-clue-data-model-schema-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Tue Sep 30 08:16:21 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C301B1A1A5B for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 08:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTpVLS6jSAc3 for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 08:16:17 -0700 (PDT)
Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:160]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1C9C1A1A59 for <clue@ietf.org>; Tue, 30 Sep 2014 08:16:16 -0700 (PDT)
Received: from resomta-po-05v.sys.comcast.net ([96.114.154.229]) by resqmta-po-01v.sys.comcast.net with comcast id xTEv1o0054xDoy801TGGzf; Tue, 30 Sep 2014 15:16:16 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-05v.sys.comcast.net with comcast id xTGF1o0033Ge9ey01TGFxx; Tue, 30 Sep 2014 15:16:16 +0000
Message-ID: <542AC93E.4000900@alum.mit.edu>
Date: Tue, 30 Sep 2014 11:16:14 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Roberta Presta <roberta.presta@unina.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1412090176; bh=ev+KSOKB3/lVA25e2pbpjL8kB7LLOy6gpV374PW7jqI=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=R4jEzmDDdTCOwkFcRfhR1fZwF4F3WtWENHzl9ofJl156hXdY6+LdKod9MnygXVx3B On6vt5A7Fn/8zL/r/iqrCc2SHoZL1Y52BtESS3xbvu55PQ9l8UNu3DVPLRO8BD3VLJ 9P0jc19xz0nbam43DTR2qdq3RJLjl6W3QB8UqAwEZBCKeGzvR3UTxgwrW4DUiH8WjT aD8WHpguwVLh6AmdKRQp3EX/djpBHziV56zO6SjHiWG9Eo+yKvw/DH0iJ+dIRzMYTt VKgN6qp0IUn4c57eo7p/k/O4MqCN+oasLbB/Ou/RpnVuTPMxofvuiSCw1wt3OSsoWH obyAY51RMNqMg==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/ZdFj-1WLI5abfISofCn0U2TCty8
Cc: CLUE <clue@ietf.org>
Subject: [clue] IANA considerations for XML schemas
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Sep 2014 15:16:18 -0000

Roberta,

I took an action item to get you some info on how to register the xml 
schema. I am no expert on this - I have just been following precedent 
from prior documents. For an example you can look at the IANA 
considerations in RFC 5628.

	Thanks,
	Paul


From nobody Tue Sep 30 08:29:37 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28C061A1A4C for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 08:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xaz6yalUUXuS for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 08:29:32 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 664AC1A1A3B for <clue@ietf.org>; Tue, 30 Sep 2014 08:29:32 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id q58so5774130wes.29 for <clue@ietf.org>; Tue, 30 Sep 2014 08:29:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zh0l0+EMcLWBQJCuCeNA5ud6q3AOMahojVsD6NuvvLk=; b=BuJU6Nu736vfFo22hf9klnoGPUkyV5k8q2aQTQRe4Of+Sv1MLlg3vztocH9efwPJbz ElclyGHFG78ZcdyE2XiZJL/fxiwS+nqhlS5jlMxhY6cvXsGvYoxNaFin90tK1j5ZNMHD Ts1zgR0noGlPJBF4VkSOEDouFZB6qPQUvkk6ZAbTVg6iFEufnA1ZmGDHQoBsLn10lGsP OyJKIADvLDI5KXRDtsvknlmwOWCSSq4nMkPlNGwzO2br5ZVD/O7BpwfbcPTUACqiKNHV TVTohZhhe2xIxOoCKYq1B0VYd1TUaR4hBui3cc0N4XZuI0NGz+L7GdnaqtiSBNetNzN2 UAVw==
MIME-Version: 1.0
X-Received: by 10.194.78.136 with SMTP id b8mr13499849wjx.106.1412090971097; Tue, 30 Sep 2014 08:29:31 -0700 (PDT)
Received: by 10.194.17.67 with HTTP; Tue, 30 Sep 2014 08:29:31 -0700 (PDT)
In-Reply-To: <542AC93E.4000900@alum.mit.edu>
References: <542AC93E.4000900@alum.mit.edu>
Date: Tue, 30 Sep 2014 10:29:31 -0500
Message-ID: <CAHBDyN4dMzzWaZGuqW6j=YxQxEWA5HhhaPwHS80AyMuoOhTBaw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=047d7bd91a8cb911ef05044a0cff
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/jvciwV6iJfG8cMldxiRdE9oVxYA
Cc: CLUE <clue@ietf.org>
Subject: Re: [clue] IANA considerations for XML schemas
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Sep 2014 15:29:34 -0000

--047d7bd91a8cb911ef05044a0cff
Content-Type: text/plain; charset=UTF-8

Actually, the IANA considerations section in 6501(section 9.2) is likely a
better example.  As I said on the call, it's fairly cookie cutter, it just
needed to be done.

Mary.

On Tue, Sep 30, 2014 at 10:16 AM, Paul Kyzivat <pkyzivat@alum.mit.edu>
wrote:

> Roberta,
>
> I took an action item to get you some info on how to register the xml
> schema. I am no expert on this - I have just been following precedent from
> prior documents. For an example you can look at the IANA considerations in
> RFC 5628.
>
>         Thanks,
>         Paul
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>

--047d7bd91a8cb911ef05044a0cff
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Actually, the IANA considerations section in 6501(section =
9.2) is likely a better example.=C2=A0 As I said on the call, it&#39;s fair=
ly cookie cutter, it just needed to be done. =C2=A0<div><br></div><div>Mary=
.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On T=
ue, Sep 30, 2014 at 10:16 AM, Paul Kyzivat <span dir=3D"ltr">&lt;<a href=3D=
"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Roberta,<br>
<br>
I took an action item to get you some info on how to register the xml schem=
a. I am no expert on this - I have just been following precedent from prior=
 documents. For an example you can look at the IANA considerations in RFC 5=
628.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul<br>
<br>
______________________________<u></u>_________________<br>
clue mailing list<br>
<a href=3D"mailto:clue@ietf.org" target=3D"_blank">clue@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/clue" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/clue</a><br>
</blockquote></div><br></div>

--047d7bd91a8cb911ef05044a0cff--


From nobody Tue Sep 30 14:08:05 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 718B71A9131 for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 14:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t_acLcQyyAvy for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 14:07:56 -0700 (PDT)
Received: from resqmta-po-08v.sys.comcast.net (resqmta-po-08v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:167]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CE631A9123 for <clue@ietf.org>; Tue, 30 Sep 2014 14:07:55 -0700 (PDT)
Received: from resomta-po-15v.sys.comcast.net ([96.114.154.239]) by resqmta-po-08v.sys.comcast.net with comcast id xZ7r1o0045AAYLo01Z7vr1; Tue, 30 Sep 2014 21:07:55 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-15v.sys.comcast.net with comcast id xZ7u1o0033Ge9ey01Z7uHE; Tue, 30 Sep 2014 21:07:54 +0000
Message-ID: <542B1BA9.30907@alum.mit.edu>
Date: Tue, 30 Sep 2014 17:07:53 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: CLUE <clue@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1412111275; bh=9CLlcFOp2eInwnpr3YPmFq+ULSlv5CVVvvZkD0mKosI=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=OFAHSwDrcwVBIvx5xDsKsc2lmsGIsgnm0g66g6zlWsqwh3BRRNgdUI6/DQthu8WWU 4kDD7XThdcyp/fBO8gXLzaoCiZgjLhS/X57HGZ6ol41dDIolQe4C+iuoAw0Bm2pwTn BUawdRe7x5Th61kb+JVNZN/jhNhredmkKQI+lVBxpW55uTvA6YsjZpxf4D6ObWYHHF yPtgK1aG/9dmfs2FtxWV9FVwx/Qms7CxVX4O1XEa5emNdLE1h1XdXUzVkraQ8nKg3c 7+spnpbfnQm1cKhZUeCxfLmZn4ieXCwefb4nQQyil9fm26cU+9RLZmeZZSuLpuNFzN ec2I6EiAQcNhA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/T8TECAz9XvDD-NEO2Dp0FDMi4no
Subject: [clue] Question about draft-ietf-clue-data-model-schema-07
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Sep 2014 21:07:57 -0000

(I think this is really a basic xml question)

The examples (in sections 23.1, 26, and 27) define media captures as 
follows:

<mediaCaptures>
     <mediaCapture xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:type="audioCaptureType"
     captureID="AC0"
     mediaType="audio">
...

I was expecting something like:

<mediaCaptures>
     <audioCapture captureID="AC0" mediaType="audio">
...

Is what is shown necessary because "audioCapture" isn't defined as an 
element in the schema, though "audioCaptureType" is defined as a type?

If <audioCapture> was defined, would the two forms above be equivalent?

	Thanks,
	Paul


From nobody Tue Sep 30 14:32:25 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64F1E1A9231 for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 14:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ljG6ikZxv1wg for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 14:32:22 -0700 (PDT)
Received: from resqmta-po-11v.sys.comcast.net (resqmta-po-11v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:170]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A5A51A916B for <clue@ietf.org>; Tue, 30 Sep 2014 14:32:22 -0700 (PDT)
Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230]) by resqmta-po-11v.sys.comcast.net with comcast id xZXE1o00E4yXVJQ01ZYMt7; Tue, 30 Sep 2014 21:32:21 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-06v.sys.comcast.net with comcast id xZYL1o00j3Ge9ey01ZYMqZ; Tue, 30 Sep 2014 21:32:21 +0000
Message-ID: <542B2164.1060207@alum.mit.edu>
Date: Tue, 30 Sep 2014 17:32:20 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: CLUE <clue@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1412112741; bh=80hirXQT5u2obHXxLl3VVbw/DIYP9eLPy4I4CRHxB5U=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=N2wd89y3YD9Vm4IijzJrg2z8vBcpGWDofh0c1jAjoOrLneRcm2Kj1hsica+tSb0DM vF2Ex0ItZdvElKzrfQAMz7fUjKkxOvPPmNmFVMJj0WTt0r3AoUFRKgNb2tHYKWYWKP lKTeqxd+ITDEEHbx6WIvnBSi8QnkyAgffZiFEJiRdHDMpQlbncZmlLiYGIWZeFIhnt oKsm4894FyPiQ/q7jBaY0ksqMOFkkmzqb8jhjfvXam5103cPbUqzqRx0vQeUXsitD9 cgDoHTOKsKKLOjRKojx7WHyCkx/s/bJiybgUf9wxqTt1HoFWNGCcAWg7hIp84/CUG8 JUYc0aUgLSNhQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/75-t5jKESSCctWfvTK9SiQxvAto
Subject: [clue] comments on draft-ietf-clue-data-model-schema-07
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Sep 2014 21:32:23 -0000

Roberta,

I tried to do a careful review of the schema again. The following are my 
notes from that:

* Terminology:

Camera-Left and Right: this is now out of date with the -17 framework.

Why has the definition of Simultaneous Transmission Set been changed to 
constrain to captures of the same type? I thought we explicitly agreed 
that there should be no such restriction.

* <mediaCaptureType>:

There is a sequence containing spatialInformation. But there are no 
bounds on it. IIUC, it should be optional - minOccurs=0, maxOccurs=1. 
(Doesn't make sense to appear more than once.)

That assumes it belongs in mediaCaptureType. While there is a single 
type for <spatialInformation>, audio and video have differing 
constraints on which parts of this may/must be present and which must 
not. ISTM that the benefit of having a single type has been lost. 
Perhaps there should just be separate spatial info types for audio and 
video.

Also, can somebody please remind me why we need an explicit notation for 
nonSpatiallyDefinable? (Rather than simply omitting spatial information.)

Similarly, is there a reason why we need "individual" as an alternative 
to to the MCC info? Couldn't we simply have MCC info as an optional fields?

The optional field element "view" of type "viewType" is confusing since 
we switched to the sceneView and globalView terminology. I think we 
should come up with a new name for this. A couple of terms that come to 
mind are: "contentType" or "subjectType".

* <personTypeType>:

I still find this, and the element "personType" of this type, to be very 
confusing to read and think about. Can we find some less confusing term 
for this? I'm tempted to suggest personRole, even though I know our past 
discussions add a lot of baggage to this. Some other terms that might 
work are: "personDuty", "personFunction", "personJob".

* Extensibility of enumerations:

This came up on the call wrt sensitivityPatternType. But there are 
several enumerations that probably have the same concern:
- personTypeType
- viewType
- presentationType
- mobilityType
- ? scaleType

The usual ietf solution for extensibility is an IANA registry. That 
would be in lieu of enumerating them in the schema. If we went that way 
then the element would probably simply be of type string, and text would 
say that the valid values are defined in a registry, and that if a value 
is not understood it should be ignored.

* <capturePointType>:

The name of this has troubled me for some time, because, once you add 
lineOfCapturePoint it is no longer a point. As an alternative, how about 
"captureOriginType"? (I don't love that, but I like it better than what 
we have and haven't thought of anything better.)

* <encodingIDListType>:

Why is the type of encID "string"? Shouldn't it be IDREF?

* <mediaCaptureIDListType>:

IIUC there is a requirement that all the captureIDREFs included in one 
list must be of the same mediaType. But this isn't stated. ISTM that 
this should be stated.

* Sample of extensibility (section 23.1):

This section says:

    The extension defines ... an
    attribute for characterizing the captures belonging to an
    "otherCaptureType" defined by the user.

 From this I infer that the recipient is expected to classify the 
predefined capture types by their type, but that extension types are to 
be classified using attributes/elements that fit within the "any" 
atttributes/elements of otherCaptureType.

Is that what is intended? It seems unnatural.

Why can't extension capture types be defined as extensions of 
mediaCaptureType, just like the builtin ones are?

* Nit - the xml schema isn't all consistently indented.


	Thanks,
	Paul


From nobody Tue Sep 30 15:15:32 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86B9F1ACC85 for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 15:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BKbGKEeXE0dt for <clue@ietfa.amsl.com>; Tue, 30 Sep 2014 15:15:30 -0700 (PDT)
Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A4BE1ACC81 for <clue@ietf.org>; Tue, 30 Sep 2014 15:15:30 -0700 (PDT)
Received: from resomta-po-08v.sys.comcast.net ([96.114.154.232]) by resqmta-po-09v.sys.comcast.net with comcast id xaF61o007516pyw01aFWd3; Tue, 30 Sep 2014 22:15:30 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-08v.sys.comcast.net with comcast id xaFV1o0023Ge9ey01aFV0p; Tue, 30 Sep 2014 22:15:29 +0000
Message-ID: <542B2B80.8070800@alum.mit.edu>
Date: Tue, 30 Sep 2014 18:15:28 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: CLUE <clue@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1412115330; bh=AkAI0r+w9CX9jbsFg8RGLTI7BxYAk4L9N2vVIfpPA70=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=tmypdcMrt4ZrGXPEqfPpcyzyZYegXB7XZ5dnDGhiVWoVHi3X58kCYS2cVEKPXA99P C0F5ZZBXVjY6QOoHfKZIb5P38CBwRLVPsIxTThRZSNKPKi7ENfUOBJdCruCMSXdtqd 8/M/rpGTOOPUIsaUw0D8LHvBclEhMGFC7YSitljQmCEKAm3vRnfHdHRUvjL7eEcUAN spd+6P4ZeYF28pTDpoVRBcud2i1z6l2b7h1YbCWLZ0waOKPQPDNaA6vnn+rTXy4typ toXn25FGxIMF9wMY2quWj6spj6xgyKO6gvCxh6Lu/uw8ING0kX/iZhVlATN8WIcbds UY58cgXieLlWw==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/JUds528VxANDAveT3JQPMSAq_VM
Subject: [clue] clue design team minutes for September 30, 2014
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Sep 2014 22:15:31 -0000

I posted the minutes and the slides from today's design team call to the 
wiki. You can find them at:

http://trac.tools.ietf.org/wg/clue/trac/attachment/wiki/Design-Team/minutes-140930.txt

I am pretty certain I didn't capture all the actions from the meeting, 
so please let me know about anything I missed.

	Thanks,
	Paul

