Re: [apps-discuss] draft-saintandre-xdash-considered-harmful-01

"Thomson, Martin" <Martin.Thomson@andrew.com> Mon, 25 October 2010 22:54 UTC

Return-Path: <Martin.Thomson@andrew.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71FBE3A690C for <apps-discuss@core3.amsl.com>; Mon, 25 Oct 2010 15:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.877
X-Spam-Level:
X-Spam-Status: No, score=-2.877 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3qgpJ+hwr1Tf for <apps-discuss@core3.amsl.com>; Mon, 25 Oct 2010 15:54:14 -0700 (PDT)
Received: from csmailgw2.commscope.com (csmailgw2.commscope.com [198.135.207.242]) by core3.amsl.com (Postfix) with ESMTP id 50DFB3A6826 for <apps-discuss@ietf.org>; Mon, 25 Oct 2010 15:54:14 -0700 (PDT)
Received: from [10.86.20.103] ([10.86.20.103]:16848 "EHLO ACDCE7HC2.commscope.com") by csmailgw2.commscope.com with ESMTP id S468253Ab0JYW4A (ORCPT <rfc822; apps-discuss@ietf.org>); Mon, 25 Oct 2010 17:56:00 -0500
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Mon, 25 Oct 2010 17:56:00 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Tue, 26 Oct 2010 06:55:57 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Date: Tue, 26 Oct 2010 06:55:55 +0800
Thread-Topic: [apps-discuss] draft-saintandre-xdash-considered-harmful-01
Thread-Index: Act0lnmFX7UAgii+SSmLM9vbu6/9ZgAAC+Gg
Message-ID: <8B0A9FCBB9832F43971E38010638454F03F31EAE68@SISPE7MB1.commscope.com>
References: <201010212030.WAA26704@TR-Sys.de> <DFFD2700-C4DF-4256-BA20-03C45F5BAB54@standardstrack.com> <4CC4D9D3.2060003@att.com> <0077AC96FF0947F4AE87DFA7@PST.JCK.COM> <3F3180D3-2925-47E9-92FD-3ED11FAD6D34@standardstrack.com> <8B0A9FCBB9832F43971E38010638454F03F31EAE5F@SISPE7MB1.commscope.com> <4CC608C4.8040209@stpeter.im>
In-Reply-To: <4CC608C4.8040209@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw2.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Cc: Discuss Apps IETF <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] draft-saintandre-xdash-considered-harmful-01
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 22:54:15 -0000

On 2010-10-26 at 09:46:28, Peter Saint-Andre wrote:
> > Better to make your extensibility simple.  How about having three
> > tiers of "interoperability protection":
> >
> > IP-C: Anyone can use a header with any name they choose.
> >
> > Use at own risk.
> >
> > IP-R: Anyone can register a header with any name.
> >
> > Collisions are less likely, not impossible.
> >
> > IP-S: RFCs* register headers with absolute exclusivity.
> >
> > Safe to use.
> 
> Could you compare / contrast to provisional vs. permanent
> registrations?
> The latter distinction might give us most or all of what we need
> (depending on which problem we're trying to solve).

A provisional registration would be similar to IP-R.  The only different is that two people can compete for the same name with IP-R; provisional registrations still have exclusivity.

Provisional registrations do the job pretty well.  But exclusivity seems unnecessary at this level of protection.  The main problems I was trying to address were:

 - informational registrations - it makes sense to have the registry document existing current practice, even if there is no intent to standardize a value, or intent to interoperate
 - old uses and current ones - some registrations might fall out of common use; rather than prevent the name from being picked up, this would let someone supplant the old name

> > * An standards track registration - or something similarly strong -
> > causes existing registrations for the same name get swept away.  The
> > review process can determine if this is appropriate.
> 
> Fun. :)

Can you think of a better reason?
	
--Martin

> Peter