[xml2rfc] section not in TOC

Robert Moskowitz <rgm@htt-consult.com> Tue, 06 June 2023 15:06 UTC

Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 70A75C151B20 for <xml2rfc@ietfa.amsl.com>; Tue, 6 Jun 2023 08:06:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.694
X-Spam-Status: No, score=-4.694 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, BITCOIN_SPAM_02=2.082, PDS_BTC_ID=0.11, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pAKwhTLtDwn7 for <xml2rfc@ietfa.amsl.com>; Tue, 6 Jun 2023 08:06:23 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA1F5C151B01 for <xml2rfc@ietf.org>; Tue, 6 Jun 2023 08:06:22 -0700 (PDT)
Received: from localhost (localhost []) by z9m9z.htt-consult.com (Postfix) with ESMTP id 678C86221A for <xml2rfc@ietf.org>; Tue, 6 Jun 2023 11:05:59 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([]) by localhost (z9m9z.htt-consult.com []) (amavisd-new, port 10024) with LMTP id x8J4Sc+k2iFO for <xml2rfc@ietf.org>; Tue, 6 Jun 2023 11:05:27 -0400 (EDT)
Received: from [] (unknown []) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 94D2D62434 for <xml2rfc@ietf.org>; Tue, 6 Jun 2023 11:05:23 -0400 (EDT)
Content-Type: multipart/mixed; boundary="------------Y5BJB9bddeZEQ1juOpC6zjYK"
Message-ID: <f4720a7f-795c-cde4-f4bc-20b351bb3fb1@htt-consult.com>
Date: Tue, 06 Jun 2023 11:05:41 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0
Content-Language: en-US
To: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
From: Robert Moskowitz <rgm@htt-consult.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/yBkdwf0DdIyi0vW9HuFjebGtFcA>
Subject: [xml2rfc] section not in TOC
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jun 2023 15:06:28 -0000

Is there a depth limit to sections in the TOC?

I cannot figure out why section Initial RAA assignments

is not in the TOC.

I really didn't want to fit the list with my xml, but could not see any 
other way to communicate the source of the problem.  So here is the xml 
I am building with the latest xml2rfc on my Fedora38 system.