Re: [clue] WGLC for draft-ietf-clue-protocol-10

Paul Kyzivat <paul.kyzivat@comcast.net> Tue, 24 January 2017 16:11 UTC

Return-Path: <paul.kyzivat@comcast.net>
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 B2C3812962B for <clue@ietfa.amsl.com>; Tue, 24 Jan 2017 08:11:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.899
X-Spam-Level:
X-Spam-Status: No, score=-5.899 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 7rV4r53wGHQJ for <clue@ietfa.amsl.com>; Tue, 24 Jan 2017 08:11:17 -0800 (PST)
Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (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 152D8129617 for <clue@ietf.org>; Tue, 24 Jan 2017 08:10:58 -0800 (PST)
Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230]) by resqmta-po-03v.sys.comcast.net with SMTP id W3gKcVs33IMkuW3gOcBolP; Tue, 24 Jan 2017 16:10:56 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1485274256; bh=rSGtfFjzpKe+wn0V92YwwZMf5h+hHw8EjUKZdIqPRMY=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=Q0lP1By42MFwNexqy+b+YRwlp8687b26pEHVyc1/RkHerkzht/r5zRQIWaK32omNJ UCq3QX51as+6XHent8bosoRioxa7sqwo76hBWo2u2MIx+nDUjXnciSvv/QBqavQ+o8 h1qLbtltA1QDPkQchWBMhU2bLnI8ojc9mwHHRmN/Y8l9UOwMCzS2qpOOPIcBQ6b/eq hcIjvVsTxpYgceGwd1UyU95eDuz90YgveFEXhRs7Zhpvol3Ip34u0ZYyl31fQ1Unuu s4kbUdwAQ0r+xWYWo59WyZ30MgK8Dj40j7dIzGjaEFcm5c3axDaX44aJ81kzIT79GN 01HrXsWPc2pSw==
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-po-06v.sys.comcast.net with SMTP id W3gNc1UNRpJ41W3gOc19mK; Tue, 24 Jan 2017 16:10:56 +0000
To: clue@ietf.org
References: <ac44e23d-061b-5d1b-b6e5-24e8f5ef0ffc@alum.mit.edu> <075716a0-ab1d-f943-50d0-a65fd339f165@nteczone.com> <4B2480BA-75CA-4E73-A3D4-ABA3058EE6AD@unina.it> <e220de50-db77-e021-c824-1d246f2eb2dd@nteczone.com> <8A070EF8-BEB7-4CA8-86C1-E10A25C91F04@unina.it> <5f5ddf96-41a9-9c55-c692-077791a04ec7@nteczone.com>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <6dc934ae-0485-8eca-b8c8-db887a82f50e@comcast.net>
Date: Tue, 24 Jan 2017 11:10:55 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <5f5ddf96-41a9-9c55-c692-077791a04ec7@nteczone.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfHk3FUJEDm8YzVE9mYXO5dl8xkoyffkDcGJ7e7U9MstE7JFrZFXA1t7PcRlX8wiob3Jg9UuowfI3VMc3heZLKF++fZkSSDmmQa+rUanbmZEBm4AFPlsb w7xWMOgi0s2fS5A4KqGOa2zdKtcRvm1SxcGu9/0xtEyvhu5mJdZZxCeM
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/DeKobmoAQGCyBxjqzdlIO8YHmQc>
Subject: Re: [clue] WGLC for draft-ietf-clue-protocol-10
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.17
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, 24 Jan 2017 16:11:19 -0000

On 1/24/17 12:08 AM, Christian Groves wrote:

>> We rephrased the sentence as follows:
>>
>> "Further response codes can be either defined in future versions of the
>> protocol  or defined
>> by leveraging the extension mechanism. In any case, such new response
>> codes MUST NOT overwrite the ones here defined and they MUST
>> respect the semantics of the first code digit.”
>>
>> Does this sound OK to you?
> [CNG] I agree with Paul in that any new response code will need to be
> registered by IANA. However I don't see the problem with having two
> mechanisms to define codes within the protocol. It should be possible to
> add an error code to CLUE without having to bump the version. I think if
> you delete "(by adding them to the related IANA registry)," and add a
> sentence along the lines of:
> "In both cases the new response code MUST be registered with IANA".

In principle that would work. But that leaves the issue of what policy 
to use for the registry. A new version of the protocol will be standards 
track, which is sufficient to control the registry. But IIUC anybody can 
define an extension. I doubt we would want to make the registry FCFS 
because the codes are a limited resource.

For simplicity in the interest of getting this done I would be satisfied 
with requiring a new version to define a new response code.

	Thanks,
	Paul