Re: [apps-discuss] Comments on draft-ietf-appsawg-received-state

Ned Freed <ned.freed@mrochek.com> Sat, 09 June 2012 09:35 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A24D321F89D8 for <apps-discuss@ietfa.amsl.com>; Sat, 9 Jun 2012 02:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QOBppijIPrB for <apps-discuss@ietfa.amsl.com>; Sat, 9 Jun 2012 02:35:30 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6515821F89D6 for <apps-discuss@ietf.org>; Sat, 9 Jun 2012 02:35:28 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OGGS8CIAB4003DMZ@mauve.mrochek.com> for apps-discuss@ietf.org; Sat, 9 Jun 2012 02:35:06 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OGBNHXOPCG000058@mauve.mrochek.com>; Sat, 9 Jun 2012 02:34:58 -0700 (PDT)
Message-id: <01OGGS87OI0Q000058@mauve.mrochek.com>
Date: Sat, 09 Jun 2012 02:33:23 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sat, 09 Jun 2012 04:52:08 -0400" <CAC4RtVAbC64Bx67b6OD4LApy9p_K2xqAZYGAETHxXZE5gY0-oA@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; CHARSET="US-ASCII"
References: <CAL0qLwY1DCP9RY7cykwrPi48A_1h_FJUXo5eRWkn3Rw=rFXpBw@mail.gmail.com> <CAC4RtVBuET9h-QHEtS=genmJnJ6bfKk=KD0bTJQvZJApAsY_ww@mail.gmail.com> <4FD08CA3.6080504@dcrocker.net> <01OGEZDG0T8M000058@mauve.mrochek.com> <4FD29DF5.5010206@dcrocker.net> <CAC4RtVAbC64Bx67b6OD4LApy9p_K2xqAZYGAETHxXZE5gY0-oA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Ned Freed <ned.freed@mrochek.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Comments on draft-ietf-appsawg-received-state
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sat, 09 Jun 2012 09:35:30 -0000

> > I think the strategic media content threat is from bad media types, not
> bad
> > registrations.  By bad media types, I mean bad technologies that get into
> a
> > position of market leverage.  And we can't do anything about them.

> Exactly, and that's my point: having the registrations is the important
> point.  Not allowing registrations is not likely to prevent usage.  If
> someone wants to start using a silly, ill-advised status code, with a poor
> definition, they can and will do so whether we allow them to register it or
> not.  If it's really stupid, it won't get any uptake. If it catches on, we
> should have registered it.

> I think that we need to use more FCFS registrations, in general, and not
> have to have a designated expert (or worse, write new RFCs) for every
> registration in every registry.  For some it absolutely makes sense.  For
> media types, it's often hard to get the details right, and the expert
> review helps people along with that.  I don't think it makes sense for this
> particular one.

As I said before, if the consensus is for FCFS, I'm willing to go along since
the number of this is likely to be small and so is the risk.

				Ned