IETF Logo Mail Archive

Re: [Tools-discuss] BCP 201 disagreement between tools page and RFC Editor

Sandy Ginoza <sginoza@amsl.com> Mon, 04 February 2019 18:37 UTC

Return-Path: <sginoza@amsl.com>
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 73C60130EE7 for <tools-discuss@ietfa.amsl.com>; Mon, 4 Feb 2019 10:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 3d7aDpCp7SZf for <tools-discuss@ietfa.amsl.com>; Mon, 4 Feb 2019 10:37:16 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EE29130EE6 for <tools-discuss@ietf.org>; Mon, 4 Feb 2019 10:37:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 03CB61C5748; Mon, 4 Feb 2019 10:36:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PkUJU77k5sH3; Mon, 4 Feb 2019 10:36:44 -0800 (PST)
Received: from sandygiozasmbp2.frontierlocal.net (unknown [47.156.81.60]) by c8a.amsl.com (Postfix) with ESMTPSA id CF4F21C5725; Mon, 4 Feb 2019 10:36:44 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <20190204181159.GN92608@kduck.mit.edu>
Date: Mon, 04 Feb 2019 10:33:31 -0800
Cc: tools-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC113EC4-2564-45FA-9950-9A7AC20C7A25@amsl.com>
References: <20190204181159.GN92608@kduck.mit.edu>
To: Benjamin Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/gUktFpjGPIsgAUcTCCVYl-RnCYU>
Subject: Re: [Tools-discuss] BCP 201 disagreement between tools page and RFC Editor
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: Mon, 04 Feb 2019 18:37:20 -0000

Hi Benjamin,

Thanks for bringing this to our attention.  I believe this was due to a bad link on the RFC Editor site.  I corrected it, so I expect https://tools.ietf.org/html/bcp201 will be updated shortly as well.  

Thanks,
Sandy

> On Feb 4, 2019, at 10:12 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> Hi all,
> 
> https://tools.ietf.org/html/bcp201 loads up an interesting page for me,
> that includes the contents of RFC 7703; the RFC Editor claims that BCP 201
> should be RFC 7696 (and the tools version of RFC 7696 also claims to be BCP
> 201).  Am I just confused about how this is supposed to work?
> 
> Thanks,
> 
> Ben
> 
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org
>

v2.23.0 | Report a Bug | By Email