IETF Logo Mail Archive

Re: [clue] CLUE call flows milestone

Roni Even <roni.even@huawei.com> Sun, 14 May 2017 04:55 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE7C127867 for <clue@ietfa.amsl.com>; Sat, 13 May 2017 21:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.52
X-Spam-Level:
X-Spam-Status: No, score=-1.52 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 8JcPDSbfaqCr for <clue@ietfa.amsl.com>; Sat, 13 May 2017 21:55:54 -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 61E7F128961 for <clue@ietf.org>; Sat, 13 May 2017 21:53:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGN76919; Sun, 14 May 2017 04:53:42 +0000 (GMT)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sun, 14 May 2017 05:53:41 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.49]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0301.000; Sun, 14 May 2017 12:53:31 +0800
From: Roni Even <roni.even@huawei.com>
To: Roni Even <roni.even@huawei.com>, "clue@ietf.org" <clue@ietf.org>
Thread-Topic: CLUE call flows milestone
Thread-Index: AdK88GT54/IumOtjR9CE7W1+zvycMwPfXG6Q
Date: Sun, 14 May 2017 04:53:30 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7C91F7@DGGEMM506-MBX.china.huawei.com>
References: <6E58094ECC8D8344914996DAD28F1CCD7B0983@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD7B0983@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.201.202]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD7C91F7DGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5917E2D6.004C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.49, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 2b1b4192a57f86de0d2af85a04dde190
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/XzLbjXWjrDIpZT0dGQwqouuDoDc>
Subject: Re: [clue] CLUE call flows milestone
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 14 May 2017 04:55:56 -0000

Hi,
It looks like there is no need for a call flow document having call flows in the signaling and protocol documents so I will remove the milestone

Roni Eve
CLUE co-chair

From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Roni Even
Sent: יום ב 24 אפריל 2017 14:52
To: clue@ietf.org
Subject: [clue] CLUE call flows milestone

Hi,
The working group finished almost all its milestones. The documents are in publication state and hopefully we will finish this work we started in 2011.
We have one milestone left :

Submit informational draft to IESG on Call Flows

We do not have any document to address this milestone.

I am looking for feedback if we need this milestone and if yes who is willing to work on it.
We have some call flows in the signaling and protocol documents

Thanks
Roni Even
CLUE co-chair

v2.23.0 | Report a Bug | By Email