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

Paul Kyzivat <paul.kyzivat@comcast.net> Mon, 23 January 2017 17:04 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 DBF571295B6 for <clue@ietfa.amsl.com>; Mon, 23 Jan 2017 09:04:40 -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 haImxBzTNRsC for <clue@ietfa.amsl.com>; Mon, 23 Jan 2017 09:04:39 -0800 (PST)
Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) (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 D4D711295AD for <clue@ietf.org>; Mon, 23 Jan 2017 09:04:39 -0800 (PST)
Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230]) by resqmta-po-04v.sys.comcast.net with SMTP id Vi2ncXdQh9RIgVi2pcLWNy; Mon, 23 Jan 2017 17:04:39 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1485191079; bh=aRobzzhrE+iXdLzAJHXisc7FB2xJDZwXpT/YIdcCSNo=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=GEqM5fKCQSBJQJNKA7VTh8JX4UP+ISqtifW98NLtMK7IrgeouVZYFBsLp1N+6NzlM kZOfINpsX71CH2F3oimPOgB1KEyOgN5i7dZZ5jdszZQ/wDqm+cbQdd2QK+AfXlK5R2 3C5cpwPUo9lg4LOkYnKwo51mV32VIA4HetQG1OzBM9xMSZUIqzj3HzYhima5MTmxPy OVCGj5fj1zihNHZT2FY6AxMlsN9JwoNhwYXM1ePTeyqxQXT1Ugy+KugM+TJ/6WdWvf 06XHEudq1KMZY1uZu7F5Lr7/jO7wThl5cWdbMUsqZZXPasF9IqA2vYekGYz07yx8to pcX6oYxmYQbLA==
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-po-06v.sys.comcast.net with SMTP id Vi2ocwm1WpJ41Vi2ocyxN6; Mon, 23 Jan 2017 17:04:39 +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>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <deb78953-6d0f-0bde-c8f8-0b2d9fe9e104@comcast.net>
Date: Mon, 23 Jan 2017 12:04:38 -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: <8A070EF8-BEB7-4CA8-86C1-E10A25C91F04@unina.it>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfEbyDcicSkKGUCSNQnu2lV6aH9VGjLqcco2e04Br9qPA53gBQUMKhv6AgT5RLNU+WDIhIxHUCESjDMvXc+zYKs9K3udr9858VPHNgjuo2w53udw8Ddv5 kez3lMXDSXniaoNdbhTbRzhE5WdQM/HUCUC72EnZ8tOWUGBvt60OH6ny
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/RzmibZK5fDPtZMLuTtvvaOObdAs>
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: Mon, 23 Jan 2017 17:04:41 -0000

On 1/23/17 4:00 AM, Simon Pietro Romano wrote:

> We rephrased the sentence as follows:
>
> "Further response codes can be either defined in future versions of the
> protocol (by adding them to the related IANA registry), 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?

I don't see how having two different mechanisms for defining new 
response codes can work.

If a new response code is defined in an extension, and thus doesn't 
update the registry, then what is to prevent that code from being reused 
in a conflicting way? Considering that (IIUC) extensions don't need to 
be registered with the IETF it seems entirely possible that somebody 
defining a new one might not be aware of another that used the same new 
response code.

So, ISTM that new response codes will always need to be registered with 
IANA, and we will thus need a suitable approval mechanism for that.

	Thanks,
	Paul