IETF Logo Mail Archive

Re: [apps-discuss] Terry Manderson's Discuss on draft-ietf-appsawg-text-markdown-use-cases-02: (with DISCUSS)

Sean Leonard <dev+ietf@seantek.com> Tue, 14 July 2015 15:37 UTC

Return-Path: <dev+ietf@seantek.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 B05021A19EF; Tue, 14 Jul 2015 08:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 NUhw2CtChLX4; Tue, 14 Jul 2015 08:37:55 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D56A41A1A5D; Tue, 14 Jul 2015 08:37:39 -0700 (PDT)
Received: from [192.168.123.7] (unknown [23.241.1.22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2D6E222E200; Tue, 14 Jul 2015 11:37:34 -0400 (EDT)
Message-ID: <55A52C90.3090402@seantek.com>
Date: Tue, 14 Jul 2015 08:36:48 -0700
From: Sean Leonard <dev+ietf@seantek.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <20150708033129.16459.55993.idtracker@ietfa.amsl.com> <CALaySJKW7Yev2OaAph2Dbrp78JJSJ3tkPNKk4HWj1huNTaf6qA@mail.gmail.com> <D1C40058.647E2%terry.manderson@icann.org> <6475ED7E-017E-46CD-A1B9-2755AFC2F702@seantek.com> <CAL0qLwZE0xwzQWoxP8nZpTO_T_OkfvRc1TXUR-byiSDUXbdG3g@mail.gmail.com> <55A11ADE.1030204@dcrocker.net> <8DC2EA7C-19BC-4B01-A99F-818345AA24C3@seantek.com> <CALaySJ+MGS3kZRk=cCeFSXs0T-w6m68-EucxcHdxSFGG=izW0g@mail.gmail.com> <55A42EC4.9090002@dcrocker.net> <55A512FD.3030506@seantek.com> <CALaySJLOhHSpWUMCqtsyK61tmn3pKBYoQtG5q5fxvcXdA=BNOQ@mail.gmail.com>
In-Reply-To: <CALaySJLOhHSpWUMCqtsyK61tmn3pKBYoQtG5q5fxvcXdA=BNOQ@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms060207080009080605000804"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/uUuPGNRYTToGV4TnymJcTdXFQgA>
Cc: "appsawg-chairs@ietf.org" <appsawg-chairs@ietf.org>, IESG <iesg@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, "draft-ietf-appsawg-text-markdown-use-cases@ietf.org" <draft-ietf-appsawg-text-markdown-use-cases@ietf.org>
Subject: Re: [apps-discuss] Terry Manderson's Discuss on draft-ietf-appsawg-text-markdown-use-cases-02: (with DISCUSS)
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Jul 2015 15:37:56 -0000

On 7/14/2015 8:15 AM, Barry Leiba wrote:
>> "Guidance" is a good term to use.
>>
>> Guidance on Markdown:
>> Design Philosophies, Preservation Strategies, and Select Registrations
> That seems reasonable, with a question: What does "preservation
> strategies" mean?

It means "how to preserve the text/markdown Content-Type along with its 
parameters outside of MIME bodies",
or, "how to preserve the author's intent when the author wrote the 
Markdown content in a certain way, so that recipients know what kind of 
Markdown (variant) the content actually is, along with the charset".

(Covered in Section 2.)

Sean

v2.23.0 | Report a Bug | By Email