IETF Logo Mail Archive

Re: [dispatch] Draft new: draft-holmberg-dispatch-iotl-00

worley@ariadne.com (Dale R. Worley) Mon, 05 May 2014 21:28 UTC

Return-Path: <worley@ariadne.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D8B1A01C1 for <dispatch@ietfa.amsl.com>; Mon, 5 May 2014 14:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 Y3ovahVwPCzS for <dispatch@ietfa.amsl.com>; Mon, 5 May 2014 14:28:26 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 626B11A011A for <dispatch@ietf.org>; Mon, 5 May 2014 14:28:26 -0700 (PDT)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta12.westchester.pa.mail.comcast.net with comcast id yKvu1n0050QuhwU5CMUNkD; Mon, 05 May 2014 21:28:22 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta02.westchester.pa.mail.comcast.net with comcast id yMUN1n00B1KKtkw3NMUNrW; Mon, 05 May 2014 21:28:22 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s45LSLYF031862; Mon, 5 May 2014 17:28:21 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s45LSLN5031861; Mon, 5 May 2014 17:28:21 -0400
Date: Mon, 05 May 2014 17:28:21 -0400
Message-Id: <201405052128.s45LSLN5031861@hobgoblin.ariadne.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
In-reply-to: <53679992.5060404@alum.mit.edu> (pkyzivat@alum.mit.edu)
References: <7594FB04B1934943A5C02806D1A2204B1D2E20D2@ESESSMB209.ericsson.se> <535EC600.3010709@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D2E3F1B@ESESSMB209.ericsson.se>, <53612FCC.7000705@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D2E7936@ESESSMB209.ericsson.se>, <536272FA.9070100@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D2E81D4@ESESSMB209.ericsson.se> <5362C9E2.1040306@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D2E90B6@ESESSMB209.ericsson.se>, <5363EC80.9010709@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D2EA8E6@ESESSMB209.ericsson.se>, <201405050138.s451cIJ7002929@hobgoblin.ariadne.com> <035F9B3F-F923-4FBB-B0C1-ABAAD84491D4@att.com> <201405051344.s45Dixmj016585@hobgoblin.ariadne.com> <53679992.5060404@alum.mit.edu>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1399325302; bh=9im/NPKdNWU4BofPjfQICNulVExDZptxm+tulR6zkfg=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=vzy6WzUjob5rJ+NaBAA1j/SnTmYDOhy6LLir0SmQtHt33U2mEn7Zdq53tLEMPAYDL iu6fjzAlq5RZVSTgTv7RuxxhCc2DPlITNdusBB7mNlzHyALcvbI2qLDM+yWp0iMW5n jb3zUhopUwcMLJXjPlqCK/LxeAYZRTioFUcpCjS5o00iqD+/Zxc1KqZFvgB+MlDpl6 hvEuKg07bAWSwPCH0uxz7UO2S+FZts2flQEi/7Nyh31v/KbUdo+1iAkc5Y82pByDiN pS+Qy8y9K8Zie3pdKsTEwkF8r1ZWKwIoDl9vHGisXsMrsPkTr8P97uNzu1N9+N5M3F fwPcrFFk+/GlQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/G2Eg414Z9PIsov9c6VTQfRhio68
Cc: dispatch@ietf.org
Subject: Re: [dispatch] Draft new: draft-holmberg-dispatch-iotl-00
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 May 2014 21:28:28 -0000

> From: Paul Kyzivat <pkyzivat@alum.mit.edu>
> 
> I'm not sure I follow what you are suggesting.
> 
> As you note, the registration procedure requires "Standards Action" and 
> that requires a "Standards Track" RFC. IIUC an Informational RFC isn't 
> Standards Track. Is that the point you are making?

Yes.  If we're going to document iotl at all, it should go into the
table of URI parameters.  But strictly speaking, it seems that an
informational RFC can't add an entry to this registry.

> Are you suggesting that the IESG could override this?

I don't know for certain, but it seems to me to be likely that it can,
and that would be a way around the apparent problem.

Dale

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