IETF Logo Mail Archive

Re: [apps-discuss] Call for Adoption: draft-seantek-text-markdown-media-type

Ned Freed <ned.freed@mrochek.com> Tue, 12 August 2014 03:00 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91BAA1A0264 for <apps-discuss@ietfa.amsl.com>; Mon, 11 Aug 2014 20:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level:
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 MTiLrkc2NqOo for <apps-discuss@ietfa.amsl.com>; Mon, 11 Aug 2014 19:59:59 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA3A1A0263 for <apps-discuss@ietf.org>; Mon, 11 Aug 2014 19:59:59 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PB9LMIF44W00138P@mauve.mrochek.com> for apps-discuss@ietf.org; Mon, 11 Aug 2014 19:54:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1407812099; bh=TNm2T6+FlXOUzF4Gg0D+QIFGNxZzt5xmEn9gCBLbOuI=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=Yv+Lkg9oiQvLxZhmbHoSDx2krSCBBtNWU6y4Ypg9Bq+/NnkFhIZA6MRwe/MqL4rpR 30wsPNLPuq4v8z/BhISkl3tgOdLqA/4EFSnHnlDrcmqLCr+NNk/BWPLt5F+3lBhlKg MV4YMxZAX0LWTUqSOK6+nXnOHuBr16+ONNCeHs7E=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"; format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PB2RFWCBO00000SM@mauve.mrochek.com>; Mon, 11 Aug 2014 19:54:55 -0700 (PDT)
Message-id: <01PB9LMH5SXU0000SM@mauve.mrochek.com>
Date: Mon, 11 Aug 2014 19:53:18 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Mon, 11 Aug 2014 13:31:35 -0400" <53E8FDF7.4060203@att.com>
References: <64A70A8D-E82B-4269-B243-6A5DA98AEB56@standardstrack.com> <20140721195032.7791.qmail@joyce.lan> <01PAFXOJO2QQ007ZXF@mauve.mrochek.com> <20140722170739.174919sctur0hbwg@webmail.tuffmail.net> <CAL0qLwZQefg75bdcH5pxm0ipGdT4AUMOhMEuo70Kg_01yxs9fA@mail.gmail.com> <53E8FDF7.4060203@att.com>
To: Tony Hansen <tony@att.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/ZTsxHQGNyNXDOkp1CpZlJZLnU3I
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Call for Adoption: draft-seantek-text-markdown-media-type
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 12 Aug 2014 03:00:00 -0000

> On 8/4/14, 2:12 AM, Murray S. Kucherawy wrote:
> > On Tue, Jul 22, 2014 at 2:07 PM, Sean Leonard <dev+ietf@seantek.com
> > <mailto:dev+ietf@seantek.com>> wrote:
> >
> >     Just wanted to add some observations that I made at the APPSAWG
> >     presentation:
> >
> >
> > While reviewing our open calls for adoption, I just noticed that this
> > document currently requests Informational status.  Why not Proposed
> > Standard?

> For registering the media type, Informational status should be
> sufficient. It's not standardizing the format; just registering the
> media type.

Agreed. If, however, the document ends up expanding to include some sort of
shared base syntax (I'm not saying it should or will, but let's suppose), then
there's a case to be made for proposed.

				Ned

v2.23.0 | Report a Bug | By Email