[clue] IMPORTANT: Need authors action - finish the signaling and protocol documents

Adam Roach <adam@nostrum.com> Mon, 22 April 2019 22:19 UTC

Return-Path: <adam@nostrum.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 42C011200E6; Mon, 22 Apr 2019 15:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level:
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 BqJkObJF8qAi; Mon, 22 Apr 2019 15:19:25 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 6E97312001E; Mon, 22 Apr 2019 15:19:19 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x3MMJBBQ043008 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 22 Apr 2019 17:19:13 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1555971554; bh=Jn5ZTX8tz64RdCIu4HxWLTcZifzoWpZjOsSXBccr0pQ=; h=Subject:From:To:Cc:References:Date:In-Reply-To; b=cM1SoNGrHah4Xb1NGaqRy4UjWtj50MH30WcJAzy3H1FBXs2yJt4DXs9pdNTrAFiUP kNDssHfNJbfmje1lrcED/pFGnCnRW6PczwuUNGYuZd0eVWRwJAlwRg16un3FsfdBss DxM9rPUk2HmJxZNO6smCrcDtFZfSQ/cBIaj0VOns=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
From: Adam Roach <adam@nostrum.com>
To: "Roni Even (A)" <roni.even@huawei.com>, "draft-ietf-clue-protocol.all@ietf.org" <draft-ietf-clue-protocol.all@ietf.org>, "draft-ietf-clue-signaling.all@ietf.org" <draft-ietf-clue-signaling.all@ietf.org>
Cc: "clue@ietf.org" <clue@ietf.org>
References: <6E58094ECC8D8344914996DAD28F1CCD18CB3090@dggemm526-mbx.china.huawei.com> <c239e27f-fff5-739b-7bf3-1889ffe9ba28@nostrum.com>
Message-ID: <9355686a-70c4-3fd6-5d55-fa838f5bb7b0@nostrum.com>
Date: Mon, 22 Apr 2019 17:19:06 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <c239e27f-fff5-739b-7bf3-1889ffe9ba28@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/vTWG9jSojHw8Ytvkq8HG9vxaV_I>
Subject: [clue] IMPORTANT: Need authors action - finish the signaling and protocol documents
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Apr 2019 22:19:27 -0000

Authors -- where are we with revised versions of these documents? Do you 
have an ETA?

/a

On 3/1/19 1:34 PM, Adam Roach wrote:
> Authors -- can you let me know when we might expect to see new 
> versions of the documents? While the DISCUSS points can be resolved by 
> a change to experimental, there are still a number of comments that we 
> need to address prior to handing off to the RFC editor.
>
> /a
>
> On 2/7/19 00:17, Roni Even (A) wrote:
>> Hi,
>> Based on the feedback from the WG it look OK to have the protocol 
>> document as experimental RFC.
>>
>> Can the authors of these two documents address the IESG comments so 
>> that we can finish the work.
>>
>>
>>
>> For the signaling please see 
>> https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/ballot/
>>
>> For the protocol 
>> https://datatracker.ietf.org/doc/draft-ietf-clue-protocol/ballot/
>>
>> Thanks
>> Roni Even
>> CLUE WG co-chair
>>
>>
>> -----Original Message-----
>> From: Adam Roach [mailto:adam@nostrum.com]
>> Sent: Wednesday, February 06, 2019 1:14 AM
>> To: draft-ietf-clue-protocol.all@ietf.org; 
>> draft-ietf-clue-signaling.all@ietf.org
>> Subject: CLUE: Need author action, input
>>
>> CLUE document authors (cc chairs, shepherds, and ADs) --
>>
>> The IESG review of the core CLUE documents last November resulted in 
>> significant comments, including a number of blocking ("DISCUSS") 
>> comments. Publication of these documents cannot proceed until the 
>> blocking comments have been addressed (and it is my personal policy 
>> that I expect each non-blocking comment to at least receive a 
>> response from the authors acknowledging the comment and indicating 
>> whether any changes to the document will result).
>>
>> We did have a short discussion [1] on the CLUE mailing list regarding 
>> whether it would be feasible to publish the core CLUE documents as 
>> Experimental. I read Stephen and Christer's input as indicating that 
>> doing so would cause issues with external organizations. On the other 
>> hand, if we never publish the CLUE documents, then they remain 
>> equally unavailable to those organizations along with the rest of the 
>> world.
>>
>> So I have an important decision to make: do we move forward in trying 
>> to address the DISCUSS comments on the protocol document? Or do we 
>> move to Experimental and make CLUE unavailable to ITU-T and 3GPP?
>>
>> The key to answering this question is whether the authors have the 
>> time available to address the more complicated DISCUSS points raised 
>> on the protocol document. If so, we can push forward towards fixing 
>> the documents and getting them out the door. If not, we should go for 
>> experimental and let ITU-T and 3GPP deal with the fallout in whatever 
>> way makes most sense for them. (Regardless of which path we choose, 
>> the remaining IESG comments need action.)
>>
>> Authors: what level of commitment can you make to completing these 
>> documents?
>>
>> /a
>>
>> ____
>> [1] 
>> https://mailarchive.ietf.org/arch/msg/clue/1o3-x4T_J9lZGp50Z4rOIpmsE60
>>
>