IETF Logo Mail Archive

Re: [Tools-discuss] how to reference BCPs (such as BCP38)?

Carsten Bormann <cabo@tzi.org> Tue, 14 May 2019 14:21 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D9BF12013D for <tools-discuss@ietfa.amsl.com>; Tue, 14 May 2019 07:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 6L5wcMpxjfI7 for <tools-discuss@ietfa.amsl.com>; Tue, 14 May 2019 07:21:51 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 171AA120162 for <tools-discuss@ietf.org>; Tue, 14 May 2019 07:21:37 -0700 (PDT)
Received: from eduroam-pool6-0651.wlan.uni-bremen.de (eduroam-pool6-0651.wlan.uni-bremen.de [134.102.26.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 453KcZ5Mhgz10Nn; Tue, 14 May 2019 16:21:34 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <25385.1557841405@localhost>
Date: Tue, 14 May 2019 16:21:34 +0200
Cc: tools-discuss@ietf.org
X-Mao-Original-Outgoing-Id: 579536492.3844759-04c9d61aaeaaf900f3c62c656f752ad3
Content-Transfer-Encoding: quoted-printable
Message-Id: <992A21CD-1C8A-458C-8708-92B0F4141094@tzi.org>
References: <25385.1557841405@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/aPNqwegDf0XGW7huTfJUUkt2wv4>
Subject: Re: [Tools-discuss] how to reference BCPs (such as BCP38)?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2019 14:21:54 -0000

With kramdown-rfc, you get to choose the label:

normative:
  BCP38: RFC2827

(You need to set
stand_alone: true
to make this work in the current version of kramdown-rfc, but you’ll want that anyway.)

Grüße, Carsten


> On May 14, 2019, at 15:43, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> Signed PGP part
> 
> We have a comment on a document asking us to make the reference to BCP38
> explicit.  Right now we have:
> 
>            In particular, the RPL root SHOULD do BCP38 (<xref
>            target="RFC2827" />) processing on the source addresses of all IP
> 
> and:
>     <?rfc include="reference.RFC.2827" ?>
> 
> 
> We tried to do:
>     <?rfc include="reference.BCP.38" ?>
> 
> but this does not work.  Not such file exists.  Is there some other way to
> get this right?
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
>

v2.23.0 | Report a Bug | By Email