[Ntp] Format checking RFC drafts
Harlan Stenn <stenn@nwtime.org> Sat, 29 July 2023 02:57 UTC
Return-Path: <stenn@nwtime.org>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6236DC15107C for <ntp@ietfa.amsl.com>; Fri, 28 Jul 2023 19:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vOhxa0180LsH for <ntp@ietfa.amsl.com>; Fri, 28 Jul 2023 19:57:51 -0700 (PDT)
Received: from chessie.everett.org (chessie.fmt1.pfcs.com [66.220.13.234]) by ietfa.amsl.com (Postfix) with ESMTP id 50F4DC151522 for <ntp@ietf.org>; Fri, 28 Jul 2023 19:56:56 -0700 (PDT)
Received: from [10.208.75.149] (075-139-201-040.res.spectrum.com [75.139.201.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4RCTgD14BCzMQS9; Sat, 29 Jul 2023 02:56:56 +0000 (UTC)
Message-ID: <9bd038a1-30f1-5be4-9f9d-c27aeff6a27d@nwtime.org>
Date: Fri, 28 Jul 2023 19:56:54 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.1
Content-Language: en-US
To: NTP WG <ntp@ietf.org>
From: Harlan Stenn <stenn@nwtime.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/f7GPFU8S84r17Au7n1OpuWNkaik>
Subject: [Ntp] Format checking RFC drafts
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2023 02:57:55 -0000
Folks, Not too long ago I could put a README.md file in a git(hub) repo that contained, for example: https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?input=&url=https://raw.githubusercontent.com/hstenn/ietf-ntp-extended-information-ef/master/ntp-extended-information-ef.xml&modeAsFormat=txt/ascii&type=toframe&Submit=Submit and the IETF Author Tools would follow the URL, load/format the document, and display it. This no longer works, and I haven't found any documentation on how to accomplish this with the current IETF Author Tools. Would somebody please point me at the current way to do this? Thanks... -- Harlan Stenn <stenn@nwtime.org> http://networktimefoundation.org - be a member!
- [Ntp] Format checking RFC drafts Harlan Stenn
- Re: [Ntp] Format checking RFC drafts Salz, Rich
- Re: [Ntp] Format checking RFC drafts Harlan Stenn