[apps-discuss] RFC 7764 on Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations

rfc-editor@rfc-editor.org Tue, 22 March 2016 23:54 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 2E5E712D172; Tue, 22 Mar 2016 16:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 wchp6rUw09HO; Tue, 22 Mar 2016 16:53:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DEA512D156; Tue, 22 Mar 2016 16:53:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E5A41180478; Tue, 22 Mar 2016 16:53:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160322235348.E5A41180478@rfc-editor.org>
Date: Tue, 22 Mar 2016 16:53:48 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/UlP1bKmRDl1GwF0IX2D8339BgW0>
Cc: drafts-update-ref@iana.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
Subject: [apps-discuss] RFC 7764 on Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.17
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, 22 Mar 2016 23:54:05 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7764

        Title:      Guidance on Markdown: Design Philosophies, 
                    Stability Strategies, and Select Registrations 
        Author:     S. Leonard
        Status:     Informational
        Stream:     IETF
        Date:       March 2016
        Mailbox:    dev+ietf@seantek.com
        Pages:      28
        Characters: 50910
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-appsawg-text-markdown-use-cases-07.txt

        URL:        https://www.rfc-editor.org/info/rfc7764

        DOI:        http://dx.doi.org/10.17487/RFC7764

This document elaborates upon the text/markdown media type for use
with Markdown, a family of plain-text formatting syntaxes that
optionally can be converted to formal markup languages such as HTML.
Background information, local storage strategies, and additional
syntax registrations are supplied.

This document is a product of the ART Area General Application Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC