
From nobody Wed Mar 22 01:02:28 2017
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0651C131465 for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 01:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 0Yj8lNrnFCUE for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 01:02:24 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59921131493 for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 01:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2M81jN2025597 for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 09:01:45 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vp2Fj4DgMzDHHX; Wed, 22 Mar 2017 09:01:45 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
X-Mao-Original-Outgoing-Id: 511862504.837878-b1ef35831ba1dbb438153fc65bcc82c4
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 22 Mar 2017 09:01:44 +0100
Message-Id: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org>
To: RFC Markdown <rfc-markdown@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/xdKw1qNvldpvsoUISGZzLUPYhLs>
Subject: [Rfc-markdown] New kramdown-rfc version 1.1.0 allows replacing reference labels
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 08:02:27 -0000

I have just pushed kramdown-rfc2629 version 1.1.0.

The major new feature that prompted finally increasing the minor release =
number is replaceable reference anchors (which then become the labels in =
the bibliography) for references imported from xml2rfc.ietf.org =E2=80=94 =
you are no longer bound to what the reference file author thought was a =
good label.

The README.md has this to say about the new feature:

+Since version 1.1, references imported from the [XML2RFC][] databases
+can be supplied with a replacement label (anchor name).  E.g., RFC 793
+could be referenced as `{{!TCP=3DRFC0793}}, further references then =
just
+can say `{{TCP}}`; both will get `[TCP]` as the label.  In the
+YAML, the same replacement can be expressed as in the first example:
+
+     normative:
+       TCP: RFC0793
+     informative:
+       SST: DOI.10.1145/1282427.1282421
+
+Notes about this feature:
+
+* At the time of writing, the DOI and IANA repositories are
+  slightly unstable.
+* Thank you, Martin Thomson, for supplying an implementation and
+  insisting this be done.
+* While this feature is now available, you are not forced to use it
+  for everything: readers of documents often benefit from not having
+  to look up references, so continuing to use the draft names and RFC
+  numbers as labels may be the preferrable style in many cases.
+* As a final caveat, renaming anchors does not work in the
+  `stand_alone: no` mode (except for IANA and DOI), as there is no
+  such mechanism in XML entity referencing; exporting to XML while
+  maintaining live references then may require some manual editing to
+  get rid of the custom anchors.

This feature required a bit more code surgery than we usually allow for =
a release, so doing this in the I-D moratorium might have been a good =
idea.  Please do run your drafts through this after updating with

	gem update

and let us know about any oddities.

Kudos again to Martin, who not only wrote the initial implementation in =
a language he is not used to liking but also had to endure my pickiness =
about this feature and generated many new versions of his pull request =
in response.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar 22 08:52:36 2017
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C96B129A08 for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 08:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 n46Y80Z4cTxO for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 08:52:32 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F5B51299E4 for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 08:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2MFqTPb010627 for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 16:52:29 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vpDhs37pbzDHY0; Wed, 22 Mar 2017 16:52:29 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org>
Date: Wed, 22 Mar 2017 16:52:28 +0100
X-Mao-Original-Outgoing-Id: 511890748.440933-dba64b171b4294bcda9da57007f1589e
Content-Transfer-Encoding: quoted-printable
Message-Id: <050B03B3-84F1-41DB-8EE0-02AFA43A9221@tzi.org>
References: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org>
To: RFC Markdown <rfc-markdown@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/2lP4JkQdC0bXJsHivV2bgsiBM_o>
Subject: Re: [Rfc-markdown] New kramdown-rfc version 1.1.0 allows replacing reference labels
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 15:52:34 -0000

On 22 Mar 2017, at 09:01, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> +* At the time of writing, the DOI and IANA repositories are
> +  slightly unstable.

No longer.  Tony put in some quality time, and we are now all set for =
the re-opening of the draft submission season...

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar 22 12:24:44 2017
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 335E51289B5 for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 12:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 OqT71r4VFSiA for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 12:24:41 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AF0D126BF6 for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 12:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2MJOcV1012371 for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 20:24:38 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vpKPf0YYmzDHdN; Wed, 22 Mar 2017 20:24:38 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org>
Date: Wed, 22 Mar 2017 20:24:37 +0100
X-Mao-Original-Outgoing-Id: 511903477.21407-2fc1eab6e78806f6bce698acfa501939
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AF0EA72-946F-4120-BBC4-9A3E55604A05@tzi.org>
References: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org>
To: RFC Markdown <rfc-markdown@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/RYzolsgDueKcb4svdhnYBYreh-k>
Subject: Re: [Rfc-markdown] New kramdown-rfc version 1.1.0 allows replacing reference labels
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 19:24:43 -0000

On 22 Mar 2017, at 09:01, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> let us know about any oddities.

One oddity did come up; that oddity may also be considered a bug fix.

In kramdown-rfc 1.0, if you referenced a specific older draft version, =
e.g.

informative:
  I-D.draft-ietf-core-links-json-05:

that reference received a label (anchor) of

[I-D.ietf-core-links-json]

which led to some confusion (and made it impossible to reference several =
different versions of a draft in the same document).

With 1.1, the label is now

[I-D.draft-ietf-core-links-json-05]

(Except in `stand_alone: false` mode, oops).

I am happy to consider that changed behavior a bug fix, in particular =
since you can get the old behavior by being explicit about your desire =
to confuse:

informative:
  I-D.ietf-core-links-json: I-D.draft-ietf-core-links-json-06

(or {{?I-D.ietf-core-links-json=3DI-D.draft-ietf-core-links-json-06}} if =
you prefer that approach.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar 22 15:48:24 2017
Return-Path: <mnot@mnot.net>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67F4F1294A9 for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 15:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 r_7WkHkjRZXP for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 15:48:20 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42D5012896F for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 15:48:20 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7E72C22E1F3; Wed, 22 Mar 2017 18:48:16 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org>
Date: Thu, 23 Mar 2017 09:48:12 +1100
Cc: RFC Markdown <rfc-markdown@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2EEE51E9-DC74-4CE2-9CE3-B9050267546B@mnot.net>
References: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/X7-nn-gm_Qn0pjAGI8SKOl5iUls>
Subject: Re: [Rfc-markdown] New kramdown-rfc version 1.1.0 allows replacing reference labels
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 22:48:23 -0000

\o/

> On 22 Mar 2017, at 7:01 pm, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> I have just pushed kramdown-rfc2629 version 1.1.0.
>=20
> The major new feature that prompted finally increasing the minor =
release number is replaceable reference anchors (which then become the =
labels in the bibliography) for references imported from =
xml2rfc.ietf.org =E2=80=94 you are no longer bound to what the reference =
file author thought was a good label.
>=20
> The README.md has this to say about the new feature:
>=20
> +Since version 1.1, references imported from the [XML2RFC][] databases
> +can be supplied with a replacement label (anchor name).  E.g., RFC =
793
> +could be referenced as `{{!TCP=3DRFC0793}}, further references then =
just
> +can say `{{TCP}}`; both will get `[TCP]` as the label.  In the
> +YAML, the same replacement can be expressed as in the first example:
> +
> +     normative:
> +       TCP: RFC0793
> +     informative:
> +       SST: DOI.10.1145/1282427.1282421
> +
> +Notes about this feature:
> +
> +* At the time of writing, the DOI and IANA repositories are
> +  slightly unstable.
> +* Thank you, Martin Thomson, for supplying an implementation and
> +  insisting this be done.
> +* While this feature is now available, you are not forced to use it
> +  for everything: readers of documents often benefit from not having
> +  to look up references, so continuing to use the draft names and RFC
> +  numbers as labels may be the preferrable style in many cases.
> +* As a final caveat, renaming anchors does not work in the
> +  `stand_alone: no` mode (except for IANA and DOI), as there is no
> +  such mechanism in XML entity referencing; exporting to XML while
> +  maintaining live references then may require some manual editing to
> +  get rid of the custom anchors.
>=20
> This feature required a bit more code surgery than we usually allow =
for a release, so doing this in the I-D moratorium might have been a =
good idea.  Please do run your drafts through this after updating with
>=20
> 	gem update
>=20
> and let us know about any oddities.
>=20
> Kudos again to Martin, who not only wrote the initial implementation =
in a language he is not used to liking but also had to endure my =
pickiness about this feature and generated many new versions of his pull =
request in response.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> _______________________________________________
> Rfc-markdown mailing list
> Rfc-markdown@ietf.org
> https://www.ietf.org/mailman/listinfo/rfc-markdown

--
Mark Nottingham   https://www.mnot.net/


From nobody Wed Mar 22 20:19:05 2017
Return-Path: <tony@att.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C67E0129BBF for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 20:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.396
X-Spam-Level: 
X-Spam-Status: No, score=-5.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 zcf05J1EXwDo for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 20:19:02 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77F5F128B38 for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 20:19:02 -0700 (PDT)
Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v2N3F8Vr013283; Wed, 22 Mar 2017 23:18:59 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049458.ppops.net-00191d01. with ESMTP id 29c4qttahu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 22 Mar 2017 23:18:59 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v2N3IwCL031469; Wed, 22 Mar 2017 23:18:59 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v2N3Irjq031417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 22 Mar 2017 23:18:55 -0400
Received: from MISOUT7MSGHUBAE.ITServices.sbc.com (MISOUT7MSGHUBAE.itservices.sbc.com [130.9.129.149]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 23 Mar 2017 03:18:44 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.103]) by MISOUT7MSGHUBAE.ITServices.sbc.com ([130.9.129.149]) with mapi id 14.03.0319.002; Wed, 22 Mar 2017 23:18:44 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: Mark Nottingham <mnot@mnot.net>
CC: RFC Markdown <rfc-markdown@ietf.org>
Thread-Topic: [Rfc-markdown] New kramdown-rfc version 1.1.0 allows replacing reference labels
Thread-Index: AQHSo15i6e9/h6GI8E2zjzKPuGw6DKGhwZyA
Date: Thu, 23 Mar 2017 03:18:43 +0000
Message-ID: <840C8C10-007A-4225-95C4-9147B98A203D@att.com>
References: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org> <2EEE51E9-DC74-4CE2-9CE3-B9050267546B@mnot.net>
In-Reply-To: <2EEE51E9-DC74-4CE2-9CE3-B9050267546B@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.110.240.92]
Content-Type: text/plain; charset="utf-8"
Content-ID: <76DFDEB7ECCA7742812EB5F879042460@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-23_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703230028
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/0HuqxYrUz4XfJQM1w-KjGGyBVKQ>
Subject: Re: [Rfc-markdown] New kramdown-rfc version 1.1.0 allows replacing reference labels
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 03:19:04 -0000

VGhpcyBpcyBmdW5ueTogV2lraXBlZGlhIHNheXMgdGhhdCB0aGlzIGVtb3RpY29uIG1lYW5zIGVp
dGhlciDigJxWaWN0b3J54oCdIG9yIOKAnEV4YXNwZXJhdGlvbuKAnS4gOi0pDQoNCk9uIDMvMjIv
MTcsIDY6NDggUE0sICJSZmMtbWFya2Rvd24gb24gYmVoYWxmIG9mIE1hcmsgTm90dGluZ2hhbSIg
PHJmYy1tYXJrZG93bi1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBtbm90QG1ub3QubmV0
PiB3cm90ZToNCg0KICAgIFxvLw0KIA0KDQo=


From nobody Wed Mar 22 20:20:42 2017
Return-Path: <mnot@mnot.net>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF724128B38 for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 20:20:38 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 C5PYkPDdSkdI for <rfc-markdown@ietfa.amsl.com>; Wed, 22 Mar 2017 20:20:34 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 926B01200A0 for <rfc-markdown@ietf.org>; Wed, 22 Mar 2017 20:20:34 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7243E22E256; Wed, 22 Mar 2017 23:20:27 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <840C8C10-007A-4225-95C4-9147B98A203D@att.com>
Date: Thu, 23 Mar 2017 14:20:23 +1100
Cc: RFC Markdown <rfc-markdown@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <53AE012A-80E1-4425-A379-7D149BDBDF8B@mnot.net>
References: <8B0BD062-090A-42E5-A7E0-D545ECDCFB79@tzi.org> <2EEE51E9-DC74-4CE2-9CE3-B9050267546B@mnot.net> <840C8C10-007A-4225-95C4-9147B98A203D@att.com>
To: "HANSEN, TONY L" <tony@att.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/pQL7aiTIG6J1kam7-9L-mEzjkBg>
Subject: Re: [Rfc-markdown] New kramdown-rfc version 1.1.0 allows replacing reference labels
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 03:20:41 -0000

Many use it as a generic "yay!"



> On 23 Mar 2017, at 2:18 pm, HANSEN, TONY L <tony@att.com> wrote:
>=20
> This is funny: Wikipedia says that this emoticon means either =
=E2=80=9CVictory=E2=80=9D or =E2=80=9CExasperation=E2=80=9D. :-)
>=20
> On 3/22/17, 6:48 PM, "Rfc-markdown on behalf of Mark Nottingham" =
<rfc-markdown-bounces@ietf.org on behalf of mnot@mnot.net> wrote:
>=20
>    \o/
>=20
>=20

--
Mark Nottingham   https://www.mnot.net/

