Re: document writing/editing tools used by IETF

Phillip Hallam-Baker <> Fri, 26 February 2021 03:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8A05E3A16D6 for <>; Thu, 25 Feb 2021 19:18:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oI-Tm7ucurWx for <>; Thu, 25 Feb 2021 19:18:16 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 433C13A16D4 for <>; Thu, 25 Feb 2021 19:18:16 -0800 (PST)
Received: by with SMTP id l8so7555239ybe.12 for <>; Thu, 25 Feb 2021 19:18:15 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FzcRbJpfWMKohtuMK7bmqSxkcBtlixrJRODRC1IbT+Q=; b=SmkH9geec36+bZ5vdv4jDoxoCt1ZeCXShQw4qObJGskUx7h/2R1tEOweNU5dXP2w1n LhuRAQsJmHA9Rfg3dPzm2LkrLUQ6oe3mcsZfpLN6pjPFkNR0JWj9h+Z5PxZcptXPsMnp rTB1xqzez1bDTx0jSs+5kYgNjdIYhBYQgZ/qEfnIwnG9lcm6EhLtxhwCAVl90ij3liz+ XyFdIYKcy1y9HienmGoLtyFkj7PPvtK5H8FIyFETO63ZiBOVrFLrqjL3RXHXQah5RBb2 4+2Fdpeqoatx9UaXca9NljAttR2KI8kBNFLx6o6rVYox6Ioor8EAbsUM4wMEli101D4l /WWg==
X-Gm-Message-State: AOAM530BXWrD0iUwgFunmEXTeuh0gQhcvuH5PRb1bFL0EDk4adnwwY/B lPQ1PPbMCIwrwlnZdyCfhYiOCvUyyODdQMTjyC8=
X-Google-Smtp-Source: ABdhPJxO+C0IxdN0Djw1nValr1LbYON21nrWw8G5F/K3aHJJeSARu8uvNN+PcOkXXpL4+cHQ7ev0D2n3igzQ88oh8xk=
X-Received: by 2002:a25:2ac3:: with SMTP id q186mr1534885ybq.213.1614309495222; Thu, 25 Feb 2021 19:18:15 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <LO2P265MB057322BA95B1B44D4175356BC29E9@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM> <> <> <001d01d70be3$ff0972d0$fd1c5870$>
In-Reply-To: <001d01d70be3$ff0972d0$fd1c5870$>
From: Phillip Hallam-Baker <>
Date: Thu, 25 Feb 2021 22:18:02 -0500
Message-ID: <>
Subject: Re: document writing/editing tools used by IETF
To: Larry Masinter <>
Cc: Carsten Bormann <>, Keith Moore <>, IETF Discussion Mailing List <>
Content-Type: multipart/alternative; boundary="00000000000005375305bc34b85f"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 26 Feb 2021 03:18:18 -0000

On Thu, Feb 25, 2021 at 9:08 PM Larry Masinter <> wrote:

> Keith is talking about formats for submission. For collaboration, there's
> a generation of collaborative tools from Google Docs to Dropbox and
> Microsoft tools that are a lot better than GitHub for collaboration.

There only needs to be a single interface to the ID/RFC system.

My model is to allow the authors to edit the drafts in Word/Markdown and
create HTML output close to what the ID/RFC system produces. When they have
agreed on an update, they send the .xml file to the submission system.


Source: Word (for spell checked text), Markdown (for machine generated text)
Review: HTML (caveman TXT if people must).
Submit: XML2RFC

I regard XML2RFC to be a submission format and nothing more. At the moment,
it is generated as a file format along with the HTML and TXT versions but I
am thinking about moving to a separate submit command which would interface
directly to the ID submission system. This would allow some housekeeping
functions to be done more smoothly.