Re: [clue] Publishing CLUE protocol as Experimental?

Keith Drage <drageke@ntlworld.com> Tue, 08 January 2019 18:11 UTC

Return-Path: <drageke@ntlworld.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 B5055130F53 for <clue@ietfa.amsl.com>; Tue, 8 Jan 2019 10:11:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ntlworld.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 nXejllf1Fu68 for <clue@ietfa.amsl.com>; Tue, 8 Jan 2019 10:11:22 -0800 (PST)
Received: from know-smtprelay-omc-11.server.virginmedia.net (know-smtprelay-omc-11.server.virginmedia.net [80.0.253.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F403A130F4C for <clue@ietf.org>; Tue, 8 Jan 2019 10:11:21 -0800 (PST)
Received: from [172.17.162.16] ([88.211.126.138]) by cmsmtp with ESMTPA id gvqQgq6TXhtC0gvqQgm3rT; Tue, 08 Jan 2019 18:11:19 +0000
X-Originating-IP: [88.211.126.138]
X-Authenticated-User: drageke@ntlworld.com
X-Spam: 0
X-Authority: v=2.3 cv=KJXu82No c=1 sm=1 tr=0 a=A23Of5e5ItRGPqVSphLRgg==:117 a=A23Of5e5ItRGPqVSphLRgg==:17 a=r77TgQKjGQsHNAKrUKIA:9 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=Z80JlwQ0AAAA:8 a=RE0BCZwv57cF0JTyLqQA:9 a=2L4LXxOSTqbRSQQ-:21 a=ReRbAGhEXVRunnHA:21 a=pILNOxqGKmIA:10 a=_ByUwbrgkbwA:10 a=UqCG9HQmAAAA:8 a=8A3WR-1y-Z9cxjvMvgUA:9 a=KY9mJnK47geuRd6T:21 a=AIrS2uBmSN2ipSZ9:21 a=jjFimIRGldHz89gg:21 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=w1C3t2QeGrPiZgrLijVG:22 a=Zz-tw7mMPhxMdvFcggwQ:22
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1546971079; bh=pPfx1hQlnyUpeDp2Yoow8hld8379qLT4gNLUOHI6ZA8=; h=Subject:To:References:From:Date:In-Reply-To; b=OufSzFimtj2So4cw6adYNmRnCR7N1miXogH3bAbLb/UdHbyrpv+lQ4Lp5vcIdwP3p 49Tlwz7ypBKbDPbQl8Eo7G5FiJ8gBNi1vQvfcM+AQZjsait01MdM7X2KxeHFNnLCKY YuVpiiRwTuUlAaoMpYn2DEczyZMiXySd534VH32Sz4vwZ7wE5PsrfWWoKhjDqculYd fXURBAdSVtMAyoZ9ZgDIWZGIWs7/wugdmgBELSyM11OdZcMr3b4jKWwbQNGeRVE3/x S6QJUL881CdEEwEzc2ZxZ4dXhIprEPmUYgsT27Vt1uzvqauyvHOqWuF5a3s5zphJip 95w8PjAReZbmg==
To: clue@ietf.org
References: <371a0f51-3919-8ae2-c782-e51ce4fc6e2f@nostrum.com> <62794BF0-F1A8-4F18-BCB4-110CCF2E9D57@unina.it> <CAMC7SJ4q5ktp=aSD5uC5dvMwHKKan0HOuRJR-Wv0rq3HgEq5kA@mail.gmail.com> <AM6PR07MB5621E7F3E8FE6CC30CCCC6A893B90@AM6PR07MB5621.eurprd07.prod.outlook.com>
From: Keith Drage <drageke@ntlworld.com>
Message-ID: <c1d9cd1e-239f-c210-7d53-e8ed6ce14ee1@ntlworld.com>
Date: Tue, 8 Jan 2019 18:11:24 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <AM6PR07MB5621E7F3E8FE6CC30CCCC6A893B90@AM6PR07MB5621.eurprd07.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------D09FFB5DA04227CADEC39338"
Content-Language: en-US
X-CMAE-Envelope: MS4wfBk/cRxWysd9OQgNQmmb3ZerM5mfKj3Y3UAFHGz73fAch7SuUUX6EmMl/hueIHySpcPgdafFD6N0vUXrbAQYx8zUkO7l+BCFYYH8/N2hu7BrrOBS0KA1 0Vf+1zKPAlwAyea00ThNslYVj88rSp0gZyYN0YGmP3f2yJF3Myamxjy9
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/p0OYPNNB2F0t6njljLpbt740QmI>
Subject: Re: [clue] Publishing CLUE protocol as Experimental?
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: Tue, 08 Jan 2019 18:11:27 -0000

Unless the policy has changed recently, the only constraint on 3GPP is 
that the material that it references normatively has to be written in a 
fashion that can be understood with such intent, i.e. one can assess 
conformity, etc. In general, one would expect experimental document to 
be written in a fashion.

To 3GPP therefore, it is irrelevant whether the IETF define the document 
as standards track or experimental; the 3GPP reference from a standard 
effectively makes it equivalent to standards track for those who use the 
3GPP standard.

Keith

On 22-Dec-18 11:23 PM, Christer Holmberg wrote:
>
>
> Hi,
>
>
> I think the issue raised by Stephen also apply to 3GPP, but I will 
> double check that.
>
>
> Regards,
>
>
> Christer
>
>
>
> ------------------------------------------------------------------------
> *From:* clue <clue-bounces@ietf.org> on behalf of Stephen Botzko 
> <stephen.botzko@gmail.com>
> *Sent:* Saturday, December 22, 2018 2:57 PM
> *To:* Simon Pietro Romano
> *Cc:* draft-ietf-clue-protocol.all@tools.ietf.org; clue@ietf.org; Adam 
> Roach; Benjamin Kaduk
> *Subject:* Re: [clue] Publishing CLUE protocol as Experimental?
> This will have an impact on on-going work in the ITU-T.  The ITU-T 
> telepresence group chose to use CLUE directly instead of developing a 
> competing protocol, and they have several drafts which have been 
> waiting for the IETF publication for some years now.
>
> They cannot make normative references to an experimental RFC.  They'd 
> either need to abandon their work, or directly incorporate CLUE into 
> their recommendations.
>
> Stephen
>
> On Sat, Dec 22, 2018 at 5:07 AM Simon Pietro Romano <spromano@unina.it 
> <mailto:spromano@unina.it>> wrote:
>
>     Hello everybody,
>
>     I’m perfectly fine with Benjamin’s and Ben’s proposal.
>
>     Cheers,
>
>     Simon
>
>              _\\|//_
>       ( 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~~~~~~~~~~~~~~~~~~~~~~~~~
>                    \ (            (   )
>                                     \_)          ) /
>                            (_/
>
>
>
>>     Il giorno 22 dic 2018, alle ore 00:10, Adam Roach
>>     <adam@nostrum.com <mailto:adam@nostrum.com>> ha scritto:
>>
>>     CLUE working group and document authors:
>>
>>     During IESG evaluation, Benjamin and Ben raised some issues
>>     around the state machine design, timeouts, and interaction with
>>     the various SIP state machines. While these could probably be
>>     addressed by adding substantial new text and a handful of new
>>     states and supervisory timers to the CLUE state machines, as well
>>     as including additional detail about the interaction between such
>>     state machines and the SIP state machines, it's not clear to me
>>     that the CLUE working group has the kind of energy necessary for
>>     that kind of refinement at this point in its lifecycle.
>>
>>     An alternate path that both Ben and Benjamin would be okay with
>>     is publication of the protocol mechanism as Experimental rather
>>     than Standards Track, in order to allow the collection of
>>     operational experience around implementing and deploying the
>>     protocol with the state machines as specified. This would be
>>     sufficient to satisfy their concerns around the currently-defined
>>     state machine and would allow publication of the CLUE documents.
>>     (Note that, due to the relationship between clue-protocol,
>>     clue-signaling, and clue-datachannel, this would also result in
>>     the publication of clue-signaling and clue-datachannel as
>>     experimental.)
>>
>>     Recognizing that many people are out of the office during this
>>     time of year, I'd like to ask that anyone who has comments
>>     regarding the proposal to move the core CLUE documents to
>>     Experimental status respond before Friday, January 18th. Thanks.
>>
>>     /a
>>
>>
>
>     _______________________________________________
>     clue mailing list
>     clue@ietf.org <mailto:clue@ietf.org>
>     https://www.ietf.org/mailman/listinfo/clue
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue