Re: [Tools-discuss] Sup to nuts

Yaron Sheffer <> Wed, 07 July 2021 21:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C98EB3A0657 for <>; Wed, 7 Jul 2021 14:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tBAjUxlUks8m for <>; Wed, 7 Jul 2021 14:23:16 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A37E53A0653 for <>; Wed, 7 Jul 2021 14:23:16 -0700 (PDT)
Received: by with SMTP id a5-20020a7bc1c50000b02901e3bbe0939bso2620214wmj.0 for <>; Wed, 07 Jul 2021 14:23:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=6wJ2Cl+cU5UN1/eb2UisXIzpkue6TYuPVcTAuPH+yzI=; b=kT4s77qul6js9ykzS/n7eW02xRkBdfmjs3KSfMD0658pzefob4Q7W62BkI9LzUDXIZ 0Zp3FLS4IfE1jYwiaguhfaIxRtdcwuIAmYikOIOVBpXOziS6OpKlQo84hJ+K9MPF9GKW 1YRrAWXsAvW771ICS+yhUaa2I2b76jzAbS8Ue/1YS7QX451SIPTvQHQ4oLizW9b1gQdS fYeusQZIKn3fO0pVRnU24Tz+2p+MO5qbd2f1a2r5SlmVmsW2hvMJJnvLfnWgVb7IVUOo cb9mjkFHBWL4RBvUfoV9uwLUxQtQAK2zjhlKCGWsZO1NDkknl2ol3l1KS1n4AsD5PLKX KlZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=6wJ2Cl+cU5UN1/eb2UisXIzpkue6TYuPVcTAuPH+yzI=; b=CVFqw1mxjwTEiBS78ZwNZPWEs+fSmb4r3TsuTRoOh8J+gvSsKz7tjBgcooT6rGuZ9+ cZPqgoe2VIhBA/a0Gf5aa+2LPk9KPeVvxC3PfznlCDw1KbxCRYdg9a5RC83g9X79tsa1 rLjcphKqVqRWJRQFu7KQIdlAEuqycCURLDh8BFLf+FnY0L2qgR400MzBoAMTHVhT/5us sKQkjEzrQg11t+682zWEXXFtXZni7+THU5XOlk3rCk8Bpg/uHE2yz7vs34q5+XYH60CE oLG3oLDvCNeynxo8I4F2vVjhTu+lRIBTriPokkyt8N/ok4SS/5fYTh4A2eVg0xLxluSV i6Fw==
X-Gm-Message-State: AOAM530GXJ5rVK4HhSamDes1P8Uzr7rHqZ32oQonLvVb/1I4sKen8rhZ GhvXKcut0EoEcm5gwvQ3pHs=
X-Google-Smtp-Source: ABdhPJxMuh5hlSXqA6PJw79Lqni5NzP8Uw7f32rWmn//a6lIJZ2S+tBHxWY8H1S1qIh6KNti2bPg4A==
X-Received: by 2002:a7b:c351:: with SMTP id l17mr29112247wmj.120.1625692994594; Wed, 07 Jul 2021 14:23:14 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id t6sm99733wru.75.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Jul 2021 14:23:14 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.50.21061301
Date: Thu, 08 Jul 2021 00:23:07 +0300
From: Yaron Sheffer <>
To: Carsten Bormann <>
CC: tools-discuss <>
Message-ID: <>
Thread-Topic: [Tools-discuss] Sup to nuts
References: <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
Subject: Re: [Tools-discuss] Sup to nuts
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 07 Jul 2021 21:23:22 -0000

Hi Carsten,

Yes, this fixed my problem. Thanks for your help!


On 7/7/21, 19:59, "Carsten Bormann" <> wrote:

    On 2021-07-07, at 18:14, Yaron Sheffer <> wrote:
    > Hi,
    > I’ve been using the “sup” XML element (superscript). It goes well through the Markdown tooling, and through xml2rfc v3.4.0 (with –v3). But then it bombs when I submit the I-D. Is this just a version difference, or should I somehow set xml2rfc to be more strict?
    > FWIW, this message “Element sup is not declared in t list of possible children” appears to contradict RFC 7991.

    Hi Yaron,

    you are submitting something that the nostalgic software at the submission point believes to be a pure v2 document, and this it enforces historic purity.

    In order to persuade this software that it’s 2021, you need to convert it to pristine v3 first.

    You can do that with

    kdrfc -3c

    or, if you prefer to work from the xml output, by 

    kdrfc -3c foo.xml
    xml2rfc --v2v3 foo.xml

    In all of these cases, you get a foo.v2v3.xml that can be submitted without invoking v2 nostalgia in the submission software.

    Grüße, Carsten

    (Yes, I know that the submission service will be fixed very soon.)