IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Fri, 15 June 2012 01:15 UTC

Return-Path: <dhc@dcrocker.net>
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 8CB9E11E809F for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jun 2012 18:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level:
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 BQglrtbxQsrk for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jun 2012 18:15:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id F131711E809A for <apps-discuss@ietf.org>; Thu, 14 Jun 2012 18:15:21 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q5F1FJKE029225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 14 Jun 2012 18:15:19 -0700
Message-ID: <4FDA8CA3.3020003@dcrocker.net>
Date: Thu, 14 Jun 2012 18:15:15 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
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> <01OGGS87OI0Q000058@mauve.mrochek.com> <CAC4RtVBReXuj473yvkNt3nOL6AyEPkZpyjqgsd2-fF5SiFs_aQ@mail.gmail.com> <03a901cd487e$908c37c0$4001a8c0@gateway.2wire.net> <4FD75939.6060200@dcrocker.net> <6.2.5.6.2.20120614075629.07eb21f0@resistor.net> <CAL0qLwa5KOyfg+mFH6WaS_-_6AO=3z7FkwQW-T1nebjwWhyxyw@mail.gmail.com> <6.2.5.6.2.20120614111103.09b6e3b8@resistor.net> <CAL0qLwaiQN+F_-1QNugv-gGfrRqvVC0iOPaGDj_PRNri=9JmWQ@mail.gmail.com>
In-Reply-To: <CAL0qLwaiQN+F_-1QNugv-gGfrRqvVC0iOPaGDj_PRNri=9JmWQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 14 Jun 2012 18:15:20 -0700 (PDT)
Cc: 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
Reply-To: dcrocker@bbiw.net
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: Fri, 15 Jun 2012 01:15:22 -0000

On 6/14/2012 11:41 AM, Murray S. Kucherawy wrote:
> Based on what you said, we could do "FCFS" and just encourage IANA to
> interact with the IESG if they have any doubts at all about the request.


This issue goes beyond this specification.

In effect, it is a 'security' issue concerning authorization to make 
changes to an existing IANA entry.

I believe we should not be expected to resolve that issue for this 
specification.

On the other hand, I agree it does need resolving.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

v2.26.15 | Report a Bug | By Email | System Status