
From nobody Tue Mar  1 22:24:51 2022
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD533A1200 for <xml2rfc@ietfa.amsl.com>; Tue,  1 Mar 2022 22:24:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.com
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 cMnoZIK0mlxg for <xml2rfc@ietfa.amsl.com>; Tue,  1 Mar 2022 22:24:44 -0800 (PST)
Received: from JPN01-TYC-obe.outbound.protection.outlook.com (mail-tycjpn01on20707.outbound.protection.outlook.com [IPv6:2a01:111:f403:7010::707]) (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 DD02D3A09B2 for <xml2rfc@ietf.org>; Tue,  1 Mar 2022 22:24:43 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SicM/5+39ic8lOo6tQICSEtkCF/g0rn77288ef6yNjSRQwB2wFVh0h4JhCl4b3dC1a8jRmktBkMyZclXEaZbkOfIsEWFQ7YBCOjg8eMq4R2miUFdqjRxprCzxv6mhMTavXpU+7rvIR240Yv8BZNSYqWWNaql9rql+Lr6b5KIpQywthHH5IoSFSd0eGLIzZGQ8/7r5fCfOShZXjNs166XZyV3yWQJeWNjge1n0PQ/f5hD8TH7qU9nT1ieEnlfCLQiTrAfVzTir2sHQ1qjm4tDfPTfA5L0ql0jm8XhJrak2bNbJsCH27JPJ7Em90COLbLZ08RKaip6gEdNqTKyl+KVCA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=pRRSMvw5stRpSZP6hLSUdh+/QmnLh7D8jc0BGaSOqdY=; b=mpuPllWHcDlhlu/C2IIvgf6lkhXUfjAfmAct4LTF11FgbFeyj+w2zB4sbjzeavRqLbGAEh4J2IPME2nlKx/tIdYupaS6sndf0UynTybDYiYbsI/AyhkNQjJnb267Tq69+zWid9RilSVwNsMSBfPLRL5KUTdZwFfFRHxkRVId4zTKtvBRxzaGfp8+ojmx0CuBtwr4aRx6Uk000gaomsioRYdRDsSBAUgXyez1SIop/L64FALZKRElzYSYiZU10GEcSpATVBpC+AX3L9bsKNMuPsKBKfKzwLuJxs7vD/BQqNB4btaoMvHy7IbRqH/o00521BtIar+MY7hE1EXVmyZ/5A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pRRSMvw5stRpSZP6hLSUdh+/QmnLh7D8jc0BGaSOqdY=; b=m2+soskV2ZlH5ZxsBaU3mIAN75dQC8lQ2wf8YG6CmcYSJyo54xXJI48eu3L2TouAe8GAwyV1joSXZIB6HOEjAi0vZQMqch9TQ8Yc/l9NL6/cbJ+jUvz32T64R7NnV0ivfO+5iUdjUepBoFttzxEQU9CvYZs/xRVzLPh+Or+yGpY=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=it.aoyama.ac.jp;
Received: from TYAPR01MB5689.jpnprd01.prod.outlook.com (2603:1096:404:8053::7) by OSBPR01MB3686.jpnprd01.prod.outlook.com (2603:1096:604:49::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5017.24; Wed, 2 Mar 2022 06:24:37 +0000
Received: from TYAPR01MB5689.jpnprd01.prod.outlook.com ([fe80::e875:83e5:cb4e:d79e]) by TYAPR01MB5689.jpnprd01.prod.outlook.com ([fe80::e875:83e5:cb4e:d79e%9]) with mapi id 15.20.5038.014; Wed, 2 Mar 2022 06:24:37 +0000
Message-ID: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp>
Date: Wed, 2 Mar 2022 15:24:35 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
From: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
To: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: TYAPR01CA0229.jpnprd01.prod.outlook.com (2603:1096:404:11e::25) To TYAPR01MB5689.jpnprd01.prod.outlook.com (2603:1096:404:8053::7)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: ec293cec-3dce-452b-bdf6-08d9fc1552fe
X-MS-TrafficTypeDiagnostic: OSBPR01MB3686:EE_
X-Microsoft-Antispam-PRVS: <OSBPR01MB3686D18E99792ADD074A84E5CA039@OSBPR01MB3686.jpnprd01.prod.outlook.com>
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: nH5pxBXBJ17QbMXhFMorimoYv986UVvZag5pJVldCFs/hjgqrJ7g21llRnuvRzwef+174XdQoOsLUh5x7JYIvLPDobAM8jGoEI77CyLp2SNSbTKHeA867abqJQyaou/wNkCXVNuyWhyG4i5WuqPSnVXzqYHzwEO3TWMRTC8quGGzLohY1MZCdr13c3KAKZjX/TGOgmnxSclqs9WnWyDRHsOnJPUg2yCdLffuJ4Imr0GlSjckYdOPkkKWMvubUIIqCSx7UqyWYiSoD+3rr5FNU4lLBRz2gpvsqSI8XrQ5R1I0oB0cHqanI8t4Pi5dvgV4cBTNEhiDQijXMwyaqqQmnZ/DWt0ljOsY+mHlp76xjPXx1302usP8qhFO5Jd/u1Xzxiqwh/K+ai6jSh6JvcVr+g6BVEsTdax0RjAoz6JL+0HGujxGDAGYHjZAJwz+XOEs+lsZyfY4lvU9SDUX8mNy+es3azgZCEHCRLmvGsvcVp6+ReZbaiSB89h7Kff+Pus8yZviYMbWS8rrRSm+XUe7UXq2KfJn7uuvc1hutlU1rO2Bd4xwkN2/Y9hBu5WbPQi8pHhwG1D1X0o5El0XbUDipgK9/1WdzyuLfWQYfLKbTW3nyoaavYSKuxudIhb0y4hAaMfSar399EPBTHmhWm3Wl3slBUI7qfPR1r1uHMbQc1qWgJoQoViw96GOnYhgkNDQ8OtjA+/fiI2v4hZqvwPfOKagTOQ7PtxwFo3kOoUG9YVMkN5hiL0+2B9nObOOkxo683llGMsXqEsQGAMqcaVpvMXkM1O5MRMGFu2+4zkdh8tW249brksFliVyakk8G69rSf3rxeEh1HDSDe/VTAu3uA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:TYAPR01MB5689.jpnprd01.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(376002)(39850400004)(346002)(136003)(396003)(366004)(786003)(86362001)(5660300002)(2616005)(6506007)(316002)(8936002)(66476007)(66556008)(66946007)(38350700002)(38100700002)(8676002)(2906002)(186003)(26005)(31696002)(66574015)(52116002)(36916002)(6486002)(966005)(508600001)(83380400001)(6916009)(31686004)(6512007)(45980500001)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?ZDFYakxoRGpSeFNmelhuSFQxaVNFd0NuQXhIbFRzYjVTMUd2M0pxZXhyVWZa?= =?utf-8?B?QVV5MHAxRVJ5ejAxWnZwK3FESDBueUlIM2h1YWRiRmQ5NjIycFZJU2dsaUll?= =?utf-8?B?bnZZcWF4UlU5RlFTdERuZGhua0s1T0I4ZjlUU2gyNDAvb0djU3dZZWxReVBj?= =?utf-8?B?R2d1WkM5YmNGaFpZNm1QWFFPY0dDTVRSemVqVGpXaUdrV0Y3ZG1Ydmh2d1dP?= =?utf-8?B?R2RYYmlZbXhpejdUVk1ucHh1R0J0V0F4dVJLR2NEMmhmWHIvakdsSEc1b0Y4?= =?utf-8?B?MXRBYkhLSmZ4VVB6UWRXTXFIYkNudzN0VE1MKzhRQllraTFYZVRtcERGSTZV?= =?utf-8?B?TWRZdU95dEc3djJ5WTMvVnNvUUppUmRLVVovN0dPcU5pWnozYW5VMTAraEdS?= =?utf-8?B?ZWpRTDQ5bDhqYlJwRnFFeTVodWZNU0M1aGgrdDlIbGczT3hJY1BhVGNmQkVz?= =?utf-8?B?bWhNMTk5d29UaFplZkxYTG02c0diUnVnNkpWbEFHVGgzUFh5WWxDSHdvYkF5?= =?utf-8?B?WVpxMHBLdXUzcnR1WlYyUlZHR0VkOHByTGpWVWIvVXZFMlNPbFl0TWhseHp6?= =?utf-8?B?ZDVJT0hjbXh2UlpLdjUwSkNMUldkNkU0dVF3bHZWMFFTSXFmR0JVZjlrRWlM?= =?utf-8?B?TDl0dVJnbWFub09EdFNUeUdaMkpUTzd3eVBjdVo2cmZTZi9FOENGSU9TMHdW?= =?utf-8?B?WExXZXB0OW0vZloyYlVRV3B5UHY0UkgxaG40ZWVtR1NzdXdwSnRnWXdzeEl5?= =?utf-8?B?cE5pSm5QU05Sczd6SURiR29CUmhKd3pTVmFIZjdmQW82d3Y4dmxQUGY2aVFw?= =?utf-8?B?VU01Z09ROFdvdVIyVlZrTWlYYjdPbUgzSG9lWVhuU01vSy9pYXNUTHM4M2sv?= =?utf-8?B?eEFVVmlGcE14Z3dZejBSWEFvbmV0Yzl3bmZFUEJFaCsxK0MvWDdPNytmeTZo?= =?utf-8?B?L2FaKzcxMGVvbFpycUdCdlZwVFhlTmNoSCtueGZ6Nmw0K2dFeWN3bFJsSldx?= =?utf-8?B?SUl5TCsvTmt3QWY4alFGcHNzNUpIWGNDQzRySFRaMEEzTGFucnFtVld4VFZk?= =?utf-8?B?ZTlFMVhyZ1cyNmYrcy9OWjJ6SFpPNzhjOWhwbjZqNEdaNWlGNnBFV05zcmN4?= =?utf-8?B?SkJEQklRS3Y1QVNUV29LWWl5WU15OGZkQWQ4NDFtejBDeUEvTmZQQ0pTQ2k3?= =?utf-8?B?VDB2cmpCR2lzbmljMXpHVWNacDNQLy81ME9DcFBWRG5qUFFGb0pSNnJWTFcy?= =?utf-8?B?UlNxYTdsUHFGVDBSUHY0V1E1MkVQSlpwdWdlRGZRcUhNMUpMbXhRODlSQ2F1?= =?utf-8?B?K1VaY2kzNE43b3huZ0l2SE5SdnNFZ2JBckNtMFFVakx1R2Y0TWlzVWt5RUp0?= =?utf-8?B?V3J3S044R3dGNWs0WWwwOWZPL1FXMVZQUkUrZW16VzRZWHd1WGQra0Q2cFVJ?= =?utf-8?B?cDBpdW5MdExjQXEvWGYzSlRJaFlIZlVoMjF5ZUFyNGJxSGdEVXVnOHVKb2Qz?= =?utf-8?B?R0QzcG92UTJaTmtYSnZFdzFNMWVzYlZZMmZyQ1dabVFiTng5ajRiSUpIdTVj?= =?utf-8?B?ekhLRytBMjV2VEpjY3c2blloaFdIQ2VNS2g3MGJVOGhCUHFEQTdwUUcxbDF4?= =?utf-8?B?cUptdTQrdGdpMGlkc0JPQUt1YWx1TGkyRm03YXh6MFVHU0poR2ZtU1huSERy?= =?utf-8?B?dy9aWnl0V1E0S0NJSXRjbVd5MlY4aG9lUUI3WHF2S01paXh6T1N2YnA2MFAx?= =?utf-8?B?U2E1NXQzajN5UTZQOGxYNzZ3aXBVbXExMkxFMjI2eThoL0tSNkQ3UHdsYWpW?= =?utf-8?B?bXZSbnEzWEEwNmlJeDB2SDJqOS9aak9lNm9KTVB1Z244S3BDbmxSQ1JlK3N3?= =?utf-8?B?N3dmWURMbUpMc2cxc3FmSHVocElJaXM4YkExTDlScGI1aWc5R0hxOVdxYStw?= =?utf-8?B?QnRKR1RRZnByclE3aEtIL1RlS3BPVG5ELzBDSU8wZHdSNGRraWNwemNpZnM1?= =?utf-8?B?b0dLeGdhbXV0U3pqQUViVGdzNHRzTW9ianpXclE0TnVBQ01aQXErUlF1Y2tZ?= =?utf-8?B?OFF0bnRxWWZIM2FmRllOWDlSTVJvZHY3Q0NDd1N5UGQ4OVRlWE9DSFE5dHV3?= =?utf-8?B?ZE12QkVaZXM2aVN2VzN3QzlXQzgwSEFYcnVMdmJzcEhHdUhUczFiVFc4a3E5?= =?utf-8?Q?+mH0PjKb6tNtbOdkZyXBUCk=3D?=
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: ec293cec-3dce-452b-bdf6-08d9fc1552fe
X-MS-Exchange-CrossTenant-AuthSource: TYAPR01MB5689.jpnprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Mar 2022 06:24:37.2355 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: wlOFU0Vy7lw/tPVkZNZP49uUUhEmInGZ3ESJuMu05W9Hv3TiIOlI/SkuLKiM5ABYLtNzBpbP4q7UTOZfek6JgQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSBPR01MB3686
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/lG4qI1cTwyadDEJMHBlD4YuPvdA>
Subject: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 06:24:49 -0000

Dear XML2RFC experts,

I just started recently with a new ID using xml2rfc, after a long 
hiatus. Things went fairly smooth, but one thing that caused problems 
was that there are links for rfc7991bis.rnc that actually go to
https://github.com/ietf-authors/rfcxml-templates-and-schemas/blob/main/rfc7991bis.rnc. 
I naively tried to just download that with "save link as" from my 
browser, but that didn't give me the actual file, just a github page 
including the actual file. It took me quite a while to figure out what 
the resulting error messages meant, and what had happened.

I no longer remember where I originally found such a link, but I have 
found one on https://authors.ietf.org/en/templates-and-schemas, in the 
Schemas section.

Anyway, if you put a link on a filename, make it so that it works for 
direct downloading. Everything else is highly confusing. If you want to 
link to the relevant github page, please add a separate link making 
clear that this link doesn't link to the actual file. Many thanks in 
advance.

Regards,   Martin.


From nobody Tue Mar  1 23:16:43 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3203A12C8 for <xml2rfc@ietfa.amsl.com>; Tue,  1 Mar 2022 23:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 8XfjGKntRofd for <xml2rfc@ietfa.amsl.com>; Tue,  1 Mar 2022 23:16:35 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0E863A12CE for <xml2rfc@ietf.org>; Tue,  1 Mar 2022 23:16:27 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K7lls3yyZzDCdJ; Wed,  2 Mar 2022 08:16:25 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp>
Date: Wed, 2 Mar 2022 08:16:24 +0100
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BFE3BFC-41AE-430C-9A7A-81A82765C311@tzi.org>
References: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp>
To: =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/oz5xo_MeQiqpUburdWHiJvPhhgY>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 07:16:41 -0000

On 2. Mar 2022, at 07:24, Martin J. D=C3=BCrst <duerst@it.aoyama.ac.jp> =
wrote:
>=20
> Dear XML2RFC experts,
>=20
> I just started recently with a new ID using xml2rfc, after a long =
hiatus. Things went fairly smooth, but one thing that caused problems =
was that there are links for rfc7991bis.rnc that actually go to
> =
https://github.com/ietf-authors/rfcxml-templates-and-schemas/blob/main/rfc=
7991bis.rnc. I naively tried to just download that with "save link as" =
from my browser, but that didn't give me the actual file, just a github =
page including the actual file. It took me quite a while to figure out =
what the resulting error messages meant, and what had happened.
>=20
> I no longer remember where I originally found such a link, but I have =
found one on https://authors.ietf.org/en/templates-and-schemas, in the =
Schemas section.
>=20
> Anyway, if you put a link on a filename, make it so that it works for =
direct downloading. Everything else is highly confusing. If you want to =
link to the relevant github page, please add a separate link making =
clear that this link doesn't link to the actual file. Many thanks in =
advance.

This is also very confusing for me.

The authoritative RFCXMLv3 grammar is at

https://github.com/ietf-tools/xml2rfc/blob/main/xml2rfc/data/v3.rnc
=
(https://raw.githubusercontent.com/ietf-tools/xml2rfc/main/xml2rfc/data/v3=
.rnc is the raw version of that.)

This appears to be a precursor to the one at =
rfcxml-templates-and-schemas, which has less indentation and more =
comment text.

I also find a version of the v3.rnc that includes grammar for =
xi:xinclude, which is needed for some tools if you use that feature.

The name rfc7991bis.rnc also seems to relate to various other =
activities.
There is an expired draft at:

https://datatracker.ietf.org/doc/html/draft-iab-rfc7991bis-03

=E2=80=A6 which points to the xml2rfc-dev mailing list as its locus of =
discussion.

While there is no repo information on that draft or its datatracker =
entry, there is a GitHub repo at

https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis

=E2=80=A6 which appears to have recent activity.

This includes a

=
https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/blob/master/xml2rfc=
v3.rng

=E2=80=A6 which is used in the accompanying Makefile to create an =
xml2rfcv3.rnc, as well as an annotated RNG from text from the I-D in =
that directory.

I don=E2=80=99t find documentation as to what the intentions with these =
various copies and versions is, and whether the naming of the files has =
any relation to those.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Mar  1 23:41:16 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4D1C3A1300 for <xml2rfc@ietfa.amsl.com>; Tue,  1 Mar 2022 23:41:14 -0800 (PST)
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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 1krLFHCeYR6h for <xml2rfc@ietfa.amsl.com>; Tue,  1 Mar 2022 23:41:10 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 354233A12FD for <xml2rfc@ietf.org>; Tue,  1 Mar 2022 23:41:09 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K7mJL6XN8zDCdS; Wed,  2 Mar 2022 08:41:06 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <3BFE3BFC-41AE-430C-9A7A-81A82765C311@tzi.org>
Date: Wed, 2 Mar 2022 08:41:06 +0100
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <62F93978-B3A2-4E9E-A52B-753B3332484F@tzi.org>
References: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp> <3BFE3BFC-41AE-430C-9A7A-81A82765C311@tzi.org>
To: =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Q2QiTeGnSe8Tnw3ROTYvnmn6kyU>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 07:41:15 -0000

On 2. Mar 2022, at 08:16, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> I don=E2=80=99t find documentation as to what the intentions with =
these various copies and versions is, and whether the naming of the =
files has any relation to those.

Further investigation shows that iab-xmlml2rfc-v3-bis, apart from some =
unnecessary reorderings, has a few sorely needed fixes:

allows blockquote in dd
allows aside in li
allows country after postalLine

(but it doesn=E2=80=99t address e.g. the <contact> weirdness [1])

plus a bizarre change:

does not allow list in t (!?), so list is now an orphan

Unfortunately, these fixes stay irrelevant to I-D authoring until they =
also are reflected in v3.rnc in xml2rfc.

Gr=C3=BC=C3=9Fe, Carsten

[1]: as addressed in http://tzi.org/~cabo/contact-hack.sh


From nobody Wed Mar  2 00:36:04 2022
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 946CC3A1399 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 00:35:56 -0800 (PST)
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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 rAowMZBUO9Im for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 00:35:52 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 074EF3A1366 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 00:35:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id CD0094396AC8; Wed,  2 Mar 2022 00:35:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-Aqfjb-OaMK; Wed,  2 Mar 2022 00:35:51 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 73DDA4396AC0; Wed,  2 Mar 2022 00:35:51 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Jay Daley <exec-director@ietf.org>
Mime-Version: 1.0 (1.0)
Date: Wed, 2 Mar 2022 21:35:46 +1300
Message-Id: <AED6215D-E9CA-4706-AB62-3245DF794497@ietf.org>
References: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp>
Cc: xml2rfc@ietf.org
In-Reply-To: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp>
To: =?utf-8?Q?"Martin_J._D=C3=BCrst"?= <duerst@it.aoyama.ac.jp>
X-Mailer: iPad Mail (19D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/9jK-M5aMUjN3kvBaWzV0EFXbFvs>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 08:36:03 -0000

Hi Martin

That should be possible.  I believe it means issuing a release of the templa=
tes and then linking to the latest release of each file.  I=E2=80=99ll ask o=
ne of the devs to help sort that and get authors.ietf.org updated.

Jay

--=20
Jay Daley
IETF Executive Director=20
exec-director@ietf.org

> On 2/03/2022, at 7:24 PM, Martin J. D=C3=BCrst <duerst@it.aoyama.ac.jp> wr=
ote:
>=20
> =EF=BB=BFDear XML2RFC experts,
>=20
> I just started recently with a new ID using xml2rfc, after a long hiatus. T=
hings went fairly smooth, but one thing that caused problems was that there a=
re links for rfc7991bis.rnc that actually go to
> https://github.com/ietf-authors/rfcxml-templates-and-schemas/blob/main/rfc=
7991bis.rnc. I naively tried to just download that with "save link as" from m=
y browser, but that didn't give me the actual file, just a github page inclu=
ding the actual file. It took me quite a while to figure out what the result=
ing error messages meant, and what had happened.
>=20
> I no longer remember where I originally found such a link, but I have foun=
d one on https://authors.ietf.org/en/templates-and-schemas, in the Schemas s=
ection.
>=20
> Anyway, if you put a link on a filename, make it so that it works for dire=
ct downloading. Everything else is highly confusing. If you want to link to t=
he relevant github page, please add a separate link making clear that this l=
ink doesn't link to the actual file. Many thanks in advance.
>=20
> Regards,   Martin.
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>=20


From nobody Wed Mar  2 00:54:48 2022
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 686023A07F2 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 00:54:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 Lr1BJ5BS-LZY for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 00:54:41 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B70E3A07F7 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 00:54:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id D053B4396ACB; Wed,  2 Mar 2022 00:54:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E_SKKeSaNhio; Wed,  2 Mar 2022 00:54:40 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 9E4BD4396AC6; Wed,  2 Mar 2022 00:54:40 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Jay Daley <exec-director@ietf.org>
Mime-Version: 1.0 (1.0)
Date: Wed, 2 Mar 2022 21:54:36 +1300
Message-Id: <48A75CA5-CC3B-446D-9FF7-A766BAFF30F6@ietf.org>
References: <3BFE3BFC-41AE-430C-9A7A-81A82765C311@tzi.org>
Cc: =?utf-8?Q?"Martin_J._D=C3=BCrst"?= <duerst@it.aoyama.ac.jp>, xml2rfc@ietf.org
In-Reply-To: <3BFE3BFC-41AE-430C-9A7A-81A82765C311@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPad Mail (19D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/VMaX91gz7F_l_i001brx4ByaCz4>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 08:54:46 -0000

> On 2/03/2022, at 8:16 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> =EF=BB=BFOn 2. Mar 2022, at 07:24, Martin J. D=C3=BCrst <duerst@it.aoyama.=
ac.jp> wrote:
>>=20
>> Dear XML2RFC experts,
>>=20
>> I just started recently with a new ID using xml2rfc, after a long hiatus.=
 Things went fairly smooth, but one thing that caused problems was that ther=
e are links for rfc7991bis.rnc that actually go to
>> https://github.com/ietf-authors/rfcxml-templates-and-schemas/blob/main/rf=
c7991bis.rnc. I naively tried to just download that with "save link as" from=
 my browser, but that didn't give me the actual file, just a github page inc=
luding the actual file. It took me quite a while to figure out what the resu=
lting error messages meant, and what had happened.
>>=20
>> I no longer remember where I originally found such a link, but I have fou=
nd one on https://authors.ietf.org/en/templates-and-schemas, in the Schemas s=
ection.
>>=20
>> Anyway, if you put a link on a filename, make it so that it works for dir=
ect downloading. Everything else is highly confusing. If you want to link to=
 the relevant github page, please add a separate link making clear that this=
 link doesn't link to the actual file. Many thanks in advance.
>=20
> This is also very confusing for me.

I believe this was explained previously but I=E2=80=99ve lost track of what l=
ist so here=E2=80=99s another explanation - the intent is to separate out th=
e authoritative grammar from xml2rfc to support that grammar being used by o=
ther tools.  For example, by schema-aware XML editors.  The change managemen=
t process should now be that changes are agreed by the xml-sg-cmt (later the=
 RSWG/RSAB) and then the grammar is updated in the templates repo and that f=
iles is then used in xml2rfc.
>=20
> The authoritative RFCXMLv3 grammar is at
>=20
> https://github.com/ietf-tools/xml2rfc/blob/main/xml2rfc/data/v3.rnc
> (https://raw.githubusercontent.com/ietf-tools/xml2rfc/main/xml2rfc/data/v3=
.rnc is the raw version of that.)

After authors.ietf.org goes live, that should no longer be the authoritative=
 version, it should be a copy of the authoritative version.
>=20
> This appears to be a precursor to the one at rfcxml-templates-and-schemas,=
 which has less indentation and more comment text.

Correct - the same but more readable.

> I also find a version of the v3.rnc that includes grammar for xi:xinclude,=
 which is needed for some tools if you use that feature.

You will unfortunately find all sorts of versions of the grammar that do not=
 appear to be documented or under any change control.  If you find some docu=
mentation on them then please point it out.

Also, what tools out there cannot work with separate XML namespaces (the nor=
mal way to enable use of xi:include)?

>=20
> The name rfc7991bis.rnc also seems to relate to various other activities.

This has been done to address the issue of stable vs changing grammar files.=
  The v3.rnc you identified above has changed multiple times since RFC 7991 w=
ith limited visibility of those changes.  In future the grammars are to be n=
amed after the RFCs that document them and bis is used here to indicate a gr=
ammar that deviates from the standard and is still in a state of flux.

> There is an expired draft at:
>=20
> https://datatracker.ietf.org/doc/html/draft-iab-rfc7991bis-03
>=20
> =E2=80=A6 which points to the xml2rfc-dev mailing list as its locus of dis=
cussion.
>=20
> While there is no repo information on that draft or its datatracker entry,=
 there is a GitHub repo at
>=20
> https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis
>=20
> =E2=80=A6 which appears to have recent activity.
>=20
> This includes a
>=20
> https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/blob/master/xml2rfc=
v3.rng
>=20
> =E2=80=A6 which is used in the accompanying Makefile to create an xml2rfcv=
3.rnc, as well as an annotated RNG from text from the I-D in that directory.=

>=20
> I don=E2=80=99t find documentation as to what the intentions with these va=
rious copies and versions is, and whether the naming of the files has any re=
lation to those.

That repo was created last year (or maybe 2020) in order to address this iss=
ue of new releases of xml2rfc including new versions of the grammar all call=
ed v3.rnc.  It basically recreates the version history of that file in a rep=
o. =20

The activity that you see isthe Temporary RFC Series PM (John Levine) buildi=
ng a new grammar that includes all the changes made since RFC 7991 that the x=
ml-sg-cmt have agreed should stay and some additional changes they have made=
.  John has kept the community up to date on these and solicited feedback.  T=
hat new grammar will of course need to be in a draft and hence rfc7991bis.

--=20
Jay Daley
IETF Executive Director=20
exec-director@ietf.org


> Gr=C3=BC=C3=9Fe, Carsten
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc


From nobody Wed Mar  2 04:31:57 2022
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B963A1347 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 04:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 GYBqhQ4I9Q_5 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 04:31:50 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 075A83A134E for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 04:31:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1646224308; bh=wxeOoiII6JsmdA9aEVVaIr+K3vznYeDbiXm/XoZjfvc=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=HLcf1omrXVms5mm6cHHOGn7Qnrv8Ts64y/uistdQUnazWtfTj0VKlBkLhNQy9nI3k jlmALhJnTV0dqjnCBhF2OV5PLP8Biy6yC2LfSCaISUzjLM1VDj64XWTCNM7PoX9gIM KFm4AINJq9R75CDmnzj5W4uv0BUNlXW0vmNsk2YQ=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([84.171.157.35]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MYNJg-1nkkVC001q-00VMGX for <xml2rfc@ietf.org>; Wed, 02 Mar 2022 13:31:48 +0100
Message-ID: <220da81d-33fc-52fa-600c-436f8e9de14f@gmx.de>
Date: Wed, 2 Mar 2022 13:31:47 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
To: xml2rfc@ietf.org
References: <3BFE3BFC-41AE-430C-9A7A-81A82765C311@tzi.org> <48A75CA5-CC3B-446D-9FF7-A766BAFF30F6@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <48A75CA5-CC3B-446D-9FF7-A766BAFF30F6@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:kCT3IaCTUTqyAQEDvQ0y1HERlgHWvNKU0LsJCFh0Qu1iOaJ4O/h auwSiKKqm0llHiwx4xFWuSrorVNa7HCAHzHAR29UQT1yjxiARk2/eId0QO6q8J3M+GPSHgL wom859VEgaV9L1nLNqRw6Efyp10+rOZ3oZ22par3kxTXFRhqw9iIdMLlQVhC7G9FBhfhD0M p8z6nis9oJk/PjhjrCcNw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:aRupW4iobOM=:2HCKSCFUPsyYSl9/e9YXnz W/PO0v88zQ4iDDGWtbNP4fPOGFiOqFoU1fzgNUOm/6BDIEFLiVPGl+y7DPEPujdToPGXizr1y psDa05MzWCkr5E3DTT8CTedDpoLaCvLdbpDUrRAg9JZBvuCowpSEQZkd+FyeLZGHMwoqtZGio i/QyivHQHOolyrPiCK9SnU3q3uRNtGUym6ho5ZGMmqeeShsi4r3C/ah0eHXSEqjQPHNt7XtFS jG3qQmD8XhJC/LeeaCoUtepGxwirqZBNiiLO1b/DaOKGR+JG2a+VrC84G0mH98c9q0xFoclcS WvAJ2QFIBT2nfHLxsahZ/ljMJb8XtCnHGt7SIWUMSzrKkSL7ctu8OIr/dOtuOVD3xqvsedW6t CU5R4NI0s4CzvY+Pbpz8QJw4BbEL09likkAU6oG58CLLUD49A4Tb44GMGTr4FO9U85ytxCiXH v9pcq7Dds2fjbBf9RlENOFrpMO5BBqpy8dZiwZfpWLPn9X2Uz9ByZBt+jXgtyh7tvjNPaOvE2 TxmL5fXIWVmOclXI8crbRx2n83Ld5owpNQK/2uxi2SV1Rp4q54KnEc/s9UhaHIhVndkhhZF4w uO0amXMb4yTw3bTd13tOPWnKOI7A3oH1Ie0HpYCckB9RxSxJqdWJPL7QUyiSIQ0VOauLVfKiZ ftApx0z5O+/Awcx3Yx8acEExGiUZT/6phGpIsLDrAQNifc7+TXBdeury4rE7g7BRfBfYg4HML gu6ukcAvMWsZkZXqCwNEakz3g/NVOeO+pAViEJ9wBCoyzwGRqzLD/65uYZ11MM7y2jeLwe4kp cnFXtWIE6Lc3O2UwmJCQG5cI/Mt/aCnYEEmzoBxlqs2DZqCefdo/vAbssTVAHr+8M1orgKrbk ybnzpNrQkLqDCx0qtKnN62LqLy3OIre0wJF3RvOgox2vKdX5gVnt6j0/eqmmE49W7qobZIFxw dZ4rQWwLFMdGKK4eex9XfMacro0d93LA65ILY/4CVXmn435BskVuuMOptnjhi7qSD1LQG7VDO yIia35DVLUABjNE5PVB6KikF3tx0rhNX7ziMGxHoAN4cM6ad8DIuX9/rwJ5c1MxGu758P3CYx uOR41onwz0x504=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Wl_qAUNqGacgOR16Ma5JFBcPsxA>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 12:31:55 -0000

Am 02.03.2022 um 09:54 schrieb Jay Daley:
> ... > That repo was created last year (or maybe 2020) in order to addres=
s
this issue of new releases of xml2rfc including new versions of the
grammar all called v3.rnc.  It basically recreates the version history
of that file in a repo.

2016.

> ...

Best regards, Julian


From nobody Wed Mar  2 10:33:25 2022
Return-Path: <johnl@iecc.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 125F23A0B69 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 10:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.862
X-Spam-Level: 
X-Spam-Status: No, score=-1.862 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=N0vTGpkR; dkim=pass (2048-bit key) header.d=taugh.com header.b=aGnmDCqH
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 YGp8m5-pqLKU for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 10:33:17 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 87DE83A0BB0 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 10:32:53 -0800 (PST)
Received: (qmail 78549 invoked from network); 2 Mar 2022 18:32:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=132d2.621fb853.k2203; bh=inZYE9+9n653NbhwQAW13zCfJ5JI3G/s5vepBFeaocg=; b=N0vTGpkRoFhmARYm/3Gfma641fY9wRWSbaC6Ye2OnJs/HrK0oSb5k9Ic3svdqUg7U8EvUiWEq+s5DA1u3UlZPxvfqCBqbweqklOGrGhrhgobw3PvoBGneIBCk9yWObIT1r3qEHgDAM01ouZKMD4aIfHOD6AOF0vjfJ4FGlExEGoaLZ9CVZQUiohRkjAUAHfHNhKfUCddkYNtur8WM4j01kYAINZGK0VPbtX86+0n79OUF4vSSzuG7TiB/3JGrTqynU70/EvhxJ7Uexvbe4kH4bpRYPMZqZ5Tb9KiFV4Xp2sTf06pwVZwH1ClXhtPZIO32dgK3cd8j0N1PmZkiNYQmQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=132d2.621fb853.k2203; bh=inZYE9+9n653NbhwQAW13zCfJ5JI3G/s5vepBFeaocg=; b=aGnmDCqHT/X9MnpHSCdjoqWBGKM9kFrFxQlEFXnZJJtwO2V6RuA/bTmGEBOsYtrui5PLuwlyIVX8r4aKGOBwvSiLaxfFEOSSkr1HRaRhNvQeLfi11rv6TtbhIzF3k9hTfeCUC1nlDmArX6TqEr365B6dVvy4NPwzZepOUBnrXoJ610ygL9hZk4HNqoFot3h8SmPV54fvLFe+slIL37NQumGOuhYqxEyMDyx2yaoIRrLvRrCSaSstFm8S/H1kupvOFW709xlUAZXhlc1MFDeZBH8snIqsaSezNJVqRnH9w54GQxtuER8VI2brbbVjXHy+RJ0VTJqd62HPBHBMBpZhJQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 02 Mar 2022 18:32:51 -0000
Received: by ary.qy (Postfix, from userid 501) id 2C7BB385EAAB; Wed,  2 Mar 2022 13:32:49 -0500 (EST)
Date: 2 Mar 2022 13:32:49 -0500
Message-Id: <20220302183250.2C7BB385EAAB@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: xml2rfc@ietf.org
In-Reply-To: <62F93978-B3A2-4E9E-A52B-753B3332484F@tzi.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/fmMeEn-pdWc96YE0sHT2awbvSTc>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 18:33:23 -0000

It appears that Carsten Bormann  <cabo@tzi.org> said:

>allows blockquote in dd
>allows aside in li
>allows country after postalLine
>
>(but it doesn’t address e.g. the <contact> weirdness [1])
>
>plus a bizarre change:
>
>does not allow list in t (!?), so list is now an orphan

Yeah, I took it out because <list> is deprecated and has never
appeared in an RFC. There was an earlier argument in which it was
added to <aside> and then removed.

Surely kramdown doesn't generate it.

R's,
John


From nobody Wed Mar  2 11:23:08 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47CF53A098C for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 11:23:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 F_y_1s0Qx9g4 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 11:23:00 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 250473A0980 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 11:23:00 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K83t83WJkzDChN; Wed,  2 Mar 2022 20:22:56 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20220302183250.2C7BB385EAAB@ary.qy>
Date: Wed, 2 Mar 2022 20:22:55 +0100
Cc: xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy>
To: "John R. Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/G_xoPAoVmqSXPTQjm_WlPEqz9P8>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 19:23:06 -0000

On 2. Mar 2022, at 19:32, John Levine <johnl@taugh.com> wrote:
>=20
> It appears that Carsten Bormann  <cabo@tzi.org> said:
>=20
>> allows blockquote in dd
>> allows aside in li
>> allows country after postalLine
>>=20
>> (but it doesn=E2=80=99t address e.g. the <contact> weirdness [1])
>>=20
>> plus a bizarre change:
>>=20
>> does not allow list in t (!?), so list is now an orphan
>=20
> Yeah, I took it out because <list> is deprecated

So is <spanx.
Deprecated v2 grammar is part of the v3 grammar; this change would be =
the first one from 7991 to be completely taken out.
(I wouldn=E2=80=99t mind having a v3-native grammar at some point, but =
this single change is premature.)

> and has never
> appeared in an RFC. There was an earlier argument in which it was
> added to <aside> and then removed.

(Well, yeah.)

> Surely kramdown doesn't generate it.

Actually, it does.  The logic in xml2rfc v2v3 to generate the various =
v3-native elements to do <list is complicated.
I also figured this logic might change over time (but haven=E2=80=99t =
followed whether it actually did =E2=80=94 which saved me a lot of time =
by the way).
I didn=E2=80=99t see a need to do a poor replica of that logic; after =
all xml2rfc is the gold standard for v3, so the right thing was to let =
the gold standard do its thing.

(It would be trivial to update the one case for which kramdown-rfc still =
generates <spanx in v3-mode, but <list is more work, and more risk.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  2 11:59:52 2022
Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 483093A0C51 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 11:59:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 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, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=kJG8qwdM; dkim=pass (2048-bit key) header.d=taugh.com header.b=RkegwOU1
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 bP939sny2hYU for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 11:59:44 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 238743A0C4C for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 11:59:43 -0800 (PST)
Received: (qmail 1396 invoked from network); 2 Mar 2022 19:59:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=572.621fccad.k2203; bh=XADTJ/dA4rgjW6adYET7qBad5Q1nyNcpt5J+sYsyqEY=; b=kJG8qwdMd/rlasIaCPfbCXPz/US3JPXrWG/M6wiEOvB+/5F/xd4JdqtuSXWJxYTOmzlzGZ49koMKkRqdE46dPzqudyCiYjLWCXoSVIXzD1x8uYg86T0tBKRylxnmuE46arHJV8MBr62ZgfeZBD2+kZ+f0TmaTjr6jbFWQ3douHUplZW6rPlpvVldcU+X/HRcaSb7AFzdGUdUM4hADRp1fzbyuIvOaY3gz/cS/xHH8kv7E0Fan4L6RouWBR8kYK2R4+tDvuxbLHd44LHQvMLvXjptG4LSGBPSyVvowcd/3Nhs/FnYiWuP7+6qH5sokBblx8t5r0qPPzh6AHgyJz4N3Q==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=572.621fccad.k2203; bh=XADTJ/dA4rgjW6adYET7qBad5Q1nyNcpt5J+sYsyqEY=; b=RkegwOU1bRSOuyLg8rtDPhHJzRE/VOsWdAt/kD/5mSHbGGNvReTKR3x6vRbe5dOr6xK86cmRRU9D+4NPdzjKC63A0xgIiYB1aeiL0zOXuzOYYZ7ZDy1J/e0ZMUgRlExENObdazt2OHzPAZCk9/2WngxsmyrPFjqAOd/6JgWnnSlVSJZtfW/nnakKDhQgnSjqrWz3QtNeMJCgWyM+hojcDJsTpjBv4m+zwC55b/ARPe2ZOIuDj45QCYLPzXQ2YVvemzBZSuSidPfMM7aqBK5lM+HgWJaxCsu9umf0+t/t5g8VoYPG6EPAFh0Vw7Jzv9SrxB6ogAgDcIVrA7InttoWhA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 02 Mar 2022 19:59:41 -0000
Received: by ary.qy (Postfix, from userid 501) id DA0C1385F7AE; Wed,  2 Mar 2022 14:59:40 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 77FF7385F790; Wed,  2 Mar 2022 14:59:40 -0500 (EST)
Date: 2 Mar 2022 14:59:40 -0500
Message-ID: <80e6ddd0-1b0c-8aac-6a89-e356fd3d3c76@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/qfi_Dit_tgEBloVUatW6jIixVVs>
Subject: Re: [xml2rfc] <list> Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 19:59:50 -0000

>> It appears that Carsten Bormann  <cabo@tzi.org> said:
>> Surely kramdown doesn't generate <list>
>
> Actually, it does.  The logic in xml2rfc v2v3 to generate the various v3-native elements to do <list is complicated.

I believe it, but I also know they all are gone by publication time, and 
when I look at the <list> elements in I-Ds it's pretty straightforward to 
see what kind of list they are.

I can put it back in, but I don't see the point.  The editors will change 
it to something else, why not figure out how to put in the right kind of 
list in the first place?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

PS: Worst lists I saw:

       <t>Type
               <list>
                       <t>This field is set to the value (TBD1) which indicates that it's a
 					  SR Candidate Path's Path SID sub-TLV.
                       </t>
               </list>
       </t>

       <t>Length
               <list>
                       <t>This field is set to the length of the sub-TLV's Value field in
 					  octets. If Headend and Endpoint fields are in IPv4 address format which
 					  is 4 octets long, it MUST be set to 40; If Headend and Endpoint fields
 					  are in IPv6 address format which is 16 octets long, it MUST be set to 64.
                       </t>
               </list>
       </t>


From nobody Wed Mar  2 12:31:23 2022
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC8EB3A0C89 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 12:31:21 -0800 (PST)
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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 xZy1Jgo7EQzE for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 12:31:17 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C9CD3A0C85 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 12:31:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id 42AAC4092764; Wed,  2 Mar 2022 12:31:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kFc55MhZuJRW; Wed,  2 Mar 2022 12:31:17 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 5D867404BF3F; Wed,  2 Mar 2022 12:31:16 -0800 (PST)
From: Jay Daley <exec-director@ietf.org>
Message-Id: <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0B284B67-AE6D-489C-AF81-1E6A221ED8B3"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
Date: Thu, 3 Mar 2022 09:31:11 +1300
In-Reply-To: <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org>
Cc: "John R. Levine" <johnl@taugh.com>, xml2rfc@ietf.org
To: Carsten Bormann <cabo@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/hPtJv3fVc2exGJ0dJRr9jtDtcPg>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 20:31:22 -0000

--Apple-Mail=_0B284B67-AE6D-489C-AF81-1E6A221ED8B3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 3/03/2022, at 8:22 AM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On 2. Mar 2022, at 19:32, John Levine <johnl@taugh.com =
<mailto:johnl@taugh.com>> wrote:
>>=20
>> It appears that Carsten Bormann  <cabo@tzi.org> said:
>>=20
>>> allows blockquote in dd
>>> allows aside in li
>>> allows country after postalLine
>>>=20
>>> (but it doesn=E2=80=99t address e.g. the <contact> weirdness [1])
>>>=20
>>> plus a bizarre change:
>>>=20
>>> does not allow list in t (!?), so list is now an orphan
>>=20
>> Yeah, I took it out because <list> is deprecated
>=20
> So is <spanx.
> Deprecated v2 grammar is part of the v3 grammar; this change would be =
the first one from 7991 to be completely taken out.
> (I wouldn=E2=80=99t mind having a v3-native grammar at some point, but =
this single change is premature.)


I think we need to be a lot clearer about our use of "deprecated" and =
how we use version numbers. =20

To make sure we=E2=80=99re all on the same page and without wishing to =
patronise anyone, in a software context, "deprecated" means "A feature =
that is still available but is targeted for removal and implementors =
should now be replacing with a different way of dong the same thing.", =
and pretty much everyone uses semantic versioning (https://semver.org)

=46rom reading RFC 7991 it=E2=80=99s not clear if "deprecated" was used =
correctly because it reads much more as if the intent was to obsolete =
those features.  However the deprecated features remain in the grammar, =
which is as expected.

The inconsistencies are that the only documentation on these features is =
to list them as deprecated features not to explain how they work, and =
the tools/processes sometimes allow the deprecated features and =
sometimes don=E2=80=99t..  This is unusual in a software context where =
deprecated features are generally still documented and still permitted =
but labelled as deprecated.

Also, it=E2=80=99s not clear what the plan is for when the deprecated =
features will be obsoleted.  If we could agree that we are using =
semantic versioning and that v2, v3 etc are major versions then if the =
next release of RFCXML is intended to be v3.1 then the deprecated =
features need to remain but if it is intended to be v4 then they can be =
removed.

Jay

>=20
>> and has never
>> appeared in an RFC. There was an earlier argument in which it was
>> added to <aside> and then removed.
>=20
> (Well, yeah.)
>=20
>> Surely kramdown doesn't generate it.
>=20
> Actually, it does.  The logic in xml2rfc v2v3 to generate the various =
v3-native elements to do <list is complicated.
> I also figured this logic might change over time (but haven=E2=80=99t =
followed whether it actually did =E2=80=94 which saved me a lot of time =
by the way).
> I didn=E2=80=99t see a need to do a poor replica of that logic; after =
all xml2rfc is the gold standard for v3, so the right thing was to let =
the gold standard do its thing.
>=20
> (It would be trivial to update the one case for which kramdown-rfc =
still generates <spanx in v3-mode, but <list is more work, and more =
risk.)
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org <mailto:xml2rfc@ietf.org>
> https://www.ietf.org/mailman/listinfo/xml2rfc =
<https://www.ietf.org/mailman/listinfo/xml2rfc>
--=20
Jay Daley
IETF Executive Director
exec-director@ietf.org


--Apple-Mail=_0B284B67-AE6D-489C-AF81-1E6A221ED8B3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 3/03/2022, at 8:22 AM, Carsten Bormann &lt;<a =
href=3D"mailto:cabo@tzi.org" class=3D"">cabo@tzi.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">On 2. Mar 2022, at 19:32, John Levine &lt;</span><a =
href=3D"mailto:johnl@taugh.com" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">johnl@taugh.com</a><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">&gt; wrote:</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">It appears that Carsten Bormann &nbsp;&lt;<a =
href=3D"mailto:cabo@tzi.org" class=3D"">cabo@tzi.org</a>&gt; said:<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">allows =
blockquote in dd<br class=3D"">allows aside in li<br class=3D"">allows =
country after postalLine<br class=3D""><br class=3D"">(but it doesn=E2=80=99=
t address e.g. the &lt;contact&gt; weirdness [1])<br class=3D""><br =
class=3D"">plus a bizarre change:<br class=3D""><br class=3D"">does not =
allow list in t (!?), so list is now an orphan<br =
class=3D""></blockquote><br class=3D"">Yeah, I took it out because =
&lt;list&gt; is deprecated<br class=3D""></blockquote><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">So is &lt;spanx.</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Deprecated v2 grammar is part of =
the v3 grammar; this change would be the first one from 7991 to be =
completely taken out.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">(I wouldn=E2=80=99t mind having a v3-native grammar at some =
point, but this single change is premature.)</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""></div></blockquote><div><br class=3D""></div><div><br =
class=3D""></div><div>I think we need to be a lot clearer about our use =
of "deprecated" and how we use version numbers. &nbsp;</div><div><br =
class=3D""></div><div>To make sure we=E2=80=99re all on the same page =
and without wishing to patronise anyone, in a software context, =
"deprecated" means "A feature that is still available but is targeted =
for removal and implementors should now be replacing with a different =
way of dong the same thing.", and pretty much everyone uses semantic =
versioning (<a href=3D"https://semver.org" =
class=3D"">https://semver.org</a>)</div><div><br =
class=3D""></div><div>=46rom reading RFC 7991 it=E2=80=99s not clear if =
"deprecated" was used correctly because it reads much more as if the =
intent was to obsolete those features. &nbsp;However the deprecated =
features remain in the grammar, which is as expected.</div><div><br =
class=3D""></div><div>The inconsistencies are that the only =
documentation on these features is to list them as deprecated features =
not to explain how they work, and the tools/processes sometimes allow =
the deprecated features and sometimes don=E2=80=99t.. &nbsp;This is =
unusual in a software context where deprecated features are generally =
still documented and still permitted but labelled as =
deprecated.</div><div><br class=3D""></div><div>Also, it=E2=80=99s not =
clear what the plan is for when the deprecated features will be =
obsoleted. &nbsp;If we could agree that we are using semantic versioning =
and that v2, v3 etc are major versions then if the next release of =
RFCXML is intended to be v3.1 then the deprecated features need to =
remain but if it is intended to be v4 then they can be =
removed.</div><div><div><br class=3D""></div><div>Jay</div></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">and =
has never<br class=3D"">appeared in an RFC. There was an earlier =
argument in which it was<br class=3D"">added to &lt;aside&gt; and then =
removed.<br class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">(Well, yeah.)</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">Surely kramdown doesn't generate =
it.<br class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Actually, it does. &nbsp;The logic in xml2rfc v2v3 to =
generate the various v3-native elements to do &lt;list is =
complicated.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">I also =
figured this logic might change over time (but haven=E2=80=99t followed =
whether it actually did =E2=80=94 which saved me a lot of time by the =
way).</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">I didn=E2=80=99=
t see a need to do a poor replica of that logic; after all xml2rfc is =
the gold standard for v3, so the right thing was to let the gold =
standard do its thing.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">(It would be trivial to update the one case for which =
kramdown-rfc still generates &lt;spanx in v3-mode, but &lt;list is more =
work, and more risk.)</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Gr=C3=BC=C3=9Fe, Carsten</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">xml2rfc mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:xml2rfc@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">xml2rfc@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/xml2rfc" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/xml2rfc</a></div></blockq=
uote></div><br class=3D""><div class=3D"">
<meta charset=3D"UTF-8" class=3D""><div>--&nbsp;<br class=3D"">Jay =
Daley<br class=3D"">IETF Executive Director<br class=3D""><a =
href=3D"mailto:exec-director@ietf.org" =
class=3D"">exec-director@ietf.org</a></div>
</div>
<br class=3D""></body></html>=

--Apple-Mail=_0B284B67-AE6D-489C-AF81-1E6A221ED8B3--


From nobody Wed Mar  2 14:12:34 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 444173A0AA5; Wed,  2 Mar 2022 14:12:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 TFYRTSiaPYYf; Wed,  2 Mar 2022 14:12:30 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C2513A09AF; Wed,  2 Mar 2022 14:12:28 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K87dh6wgSzDCgc; Wed,  2 Mar 2022 23:12:24 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org>
Date: Wed, 2 Mar 2022 23:12:24 +0100
Cc: "John R. Levine" <johnl@taugh.com>, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org>
To: Jay Daley <exec-director@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/k6eyNc1d_zrzIpFtoKltaZ3T61c>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 22:12:33 -0000

Hi Jay,

> I think we need to be a lot clearer about our use of "deprecated" and =
how we use version numbers. =20

This is a very good point.

We are using a transition model that employs the construct of a hybrid =
v2v3 document (what I have been calling the mongrel format).

Authors can continue to use v2 documents and enhance them with v3 =
elements and attributes.
xml2rfc =E2=80=94v2v3 converts these transition documents to v3, either =
with the =E2=80=94v2v3 flag or because a mongrel format document was =
supplied to =E2=80=94v3.
The v3 grammar therefore describes the mongrel format as well as pure =
v3.

Nothing about a v3.1 or v4 would change that transition model.  There =
are still tons of v2 documents out there that will gradually gain v3 =
functions.
(Given that the transition started on 2020-09-04 with xml2rfc 3.0.0, and =
I would expect the transition to last some 5 to 10 years, this means we =
can stop worrying by end-2025 to end-2030.)

Kramdown-rfc is hitchhiking on this by also outputting mongrel documents =
and using xml2rfc as the source of truth on v3.

Of course, a v3.1 could cut off this transition model.
This would simply be a hostile act to authors who are still using =
v2/mongrel.

So I think =E2=80=9Cdeprecated=E2=80=9D here means: still part of the =
admissible input (authoring side) but no longer in use on the =
editing/publishing side.
To better support the latter, it could be useful to have a v3-native =
grammar in addition to the existing v3 grammar.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  2 15:12:04 2022
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207C43A0D78 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 15:12:01 -0800 (PST)
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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 v3yrfxhNfsty for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 15:11:56 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B42D03A0D28 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 15:11:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id 951C84112A6F; Wed,  2 Mar 2022 15:11:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D1E6be28laeX; Wed,  2 Mar 2022 15:11:56 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 0E618404BF3F; Wed,  2 Mar 2022 15:11:55 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <AED6215D-E9CA-4706-AB62-3245DF794497@ietf.org>
Date: Thu, 3 Mar 2022 12:11:51 +1300
Cc: xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB39CD29-EF05-4B88-8254-E7BE649F4C49@ietf.org>
References: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp> <AED6215D-E9CA-4706-AB62-3245DF794497@ietf.org>
To: =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/A8QQpZsSohnV45fyJ0599oOqjLk>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 23:12:01 -0000

> On 2/03/2022, at 9:35 PM, Jay Daley <exec-director@ietf.org> wrote:
>=20
> Hi Martin
>=20
> That should be possible.  I believe it means issuing a release of the =
templates and then linking to the latest release of each file.  I=E2=80=99=
ll ask one of the devs to help sort that and get authors.ietf.org =
updated.

This has now been done.  For those interested - the /blob/ was replaced =
with /raw/ in the path.

Jay

>=20
> Jay
>=20
> --=20
> Jay Daley
> IETF Executive Director=20
> exec-director@ietf.org
>=20
>> On 2/03/2022, at 7:24 PM, Martin J. D=C3=BCrst =
<duerst@it.aoyama.ac.jp> wrote:
>>=20
>> =EF=BB=BFDear XML2RFC experts,
>>=20
>> I just started recently with a new ID using xml2rfc, after a long =
hiatus. Things went fairly smooth, but one thing that caused problems =
was that there are links for rfc7991bis.rnc that actually go to
>> =
https://github.com/ietf-authors/rfcxml-templates-and-schemas/blob/main/rfc=
7991bis.rnc. I naively tried to just download that with "save link as" =
from my browser, but that didn't give me the actual file, just a github =
page including the actual file. It took me quite a while to figure out =
what the resulting error messages meant, and what had happened.
>>=20
>> I no longer remember where I originally found such a link, but I have =
found one on https://authors.ietf.org/en/templates-and-schemas, in the =
Schemas section.
>>=20
>> Anyway, if you put a link on a filename, make it so that it works for =
direct downloading. Everything else is highly confusing. If you want to =
link to the relevant github page, please add a separate link making =
clear that this link doesn't link to the actual file. Many thanks in =
advance.
>>=20
>> Regards,   Martin.
>>=20
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>=20
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc

--=20
Jay Daley
IETF Executive Director
exec-director@ietf.org


From nobody Wed Mar  2 15:15:53 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93FE43A0D9E; Wed,  2 Mar 2022 15:15:52 -0800 (PST)
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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 xuFFOJnncY1r; Wed,  2 Mar 2022 15:15:48 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82D4A3A0DD6; Wed,  2 Mar 2022 15:15:47 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K892m4fVVzDCjT; Thu,  3 Mar 2022 00:15:44 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <AB39CD29-EF05-4B88-8254-E7BE649F4C49@ietf.org>
Date: Thu, 3 Mar 2022 00:15:44 +0100
Cc: =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2C87604-926A-4CCC-896A-11264962E151@tzi.org>
References: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp> <AED6215D-E9CA-4706-AB62-3245DF794497@ietf.org> <AB39CD29-EF05-4B88-8254-E7BE649F4C49@ietf.org>
To: Jay Daley <exec-director@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/jM-eJ41yScf0EH2zCj2PVssj_ys>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 23:15:53 -0000

On 3. Mar 2022, at 00:11, Jay Daley <exec-director@ietf.org> wrote:
>=20
> This has now been done. =20

Thanks!

Though not on
Martin Thompson's Markdown Template

> For those interested - the /blob/ was replaced with /raw/ in the path.

Good to know =E2=80=94 I=E2=80=99m always using =
raw.githubusercontent.com and now I=E2=80=99m wondering why.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  2 15:58:09 2022
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B977B3A0EB2; Wed,  2 Mar 2022 15:58:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.com
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 RzqGI_CcZNyF; Wed,  2 Mar 2022 15:58:06 -0800 (PST)
Received: from JPN01-OS0-obe.outbound.protection.outlook.com (mail-os0jpn01on2072d.outbound.protection.outlook.com [IPv6:2a01:111:f403:700c::72d]) (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 5A2A13A0E86; Wed,  2 Mar 2022 15:58:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dpHiDd5G5zFS+sBU0dIKAloUMAdMhIJPheTxWQZeDxGDu5hMT6x4Ma0MyTGkh7dPv8cZXnP3b9ahuyZ5GuY2RN6pJ9fLYecTeYhsnFfRzBs+bdvloJ65mbDlKmcDNN6ek9XANh0YWMcpIPKnlL2AVBHAY57qEEy6AE7goHWZ2d+oVk6ddFTDk5+4OQ20pUoI4RvyOih7+nRU9P/c5ptUVJipfXK1p7soPXcpAoZsOrSm0k4s2wtxO/Pey/iGfhMbtSkd/EN/ys7EtBbxYjGzxSFvWVYNunvPDo5RL45aZqtuJC4RYewF6hvr+kcGvERDy4s5irxY7ZUALqqnuWq52g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=fzxvlbB2Ddv8jU+saCQCEdbUKy6/ORZMlkYFjm6ZHj8=; b=nedYFK4M9pf1Ncwq5pxsXIV+UgWnCOEODD9LsDhNb3BqIXV+jFy8v6RAoCM5OdJEX6aIGqdlYTOy0juFR8PPp5BS/CaL4qKNxBu1UushDFDzJj/03ErtZvEiMiD+uuXYINutZCRMdoLJG3Dq+cQ8e8WfzMLNN4HSGYHBq11WCZhYwO3W/tUw+M0QAse6QLr8qhgdNR22RZjMqS0qgYqKp+nqcFVCIST65rPfU6bOtHYhTrpKZGn3phJ5jFziS6TmKZDbCGsExVOwI2dcqD/+Gq/haXeVLuJ/MorgoT2VH6c0cceGFNfiqwKX5Q3x1v7AKwK7RxIKSY7y4HTtlBdlcQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fzxvlbB2Ddv8jU+saCQCEdbUKy6/ORZMlkYFjm6ZHj8=; b=q4zIFnsWdkwrp8kGbL8+ZuY/Zq0faKa0YIYYT4Zv0svBlt6zmEyv36WQMjpeidlGIQU0TkDcsHnmeQr9CjaZTEFa5HiWX1ooidwJViY3hlWgHTsjRfZrXuP7RhJ3ykw8lTFC7+cNp6Nsgg3QrNjpF8Xp8xXuENdujMFDq15Ua6M=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=it.aoyama.ac.jp;
Received: from TYAPR01MB5689.jpnprd01.prod.outlook.com (2603:1096:404:8053::7) by OSAPR01MB4019.jpnprd01.prod.outlook.com (2603:1096:604:58::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5038.14; Wed, 2 Mar 2022 23:57:59 +0000
Received: from TYAPR01MB5689.jpnprd01.prod.outlook.com ([fe80::e875:83e5:cb4e:d79e]) by TYAPR01MB5689.jpnprd01.prod.outlook.com ([fe80::e875:83e5:cb4e:d79e%9]) with mapi id 15.20.5038.014; Wed, 2 Mar 2022 23:57:59 +0000
Message-ID: <c0541f45-1bbe-82db-7069-74bba9ef9ad2@it.aoyama.ac.jp>
Date: Thu, 3 Mar 2022 08:57:58 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Jay Daley <exec-director@ietf.org>
Cc: xml2rfc@ietf.org
References: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp> <AED6215D-E9CA-4706-AB62-3245DF794497@ietf.org> <AB39CD29-EF05-4B88-8254-E7BE649F4C49@ietf.org>
From: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
In-Reply-To: <AB39CD29-EF05-4B88-8254-E7BE649F4C49@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: TYAPR01CA0021.jpnprd01.prod.outlook.com (2603:1096:404::33) To TYAPR01MB5689.jpnprd01.prod.outlook.com (2603:1096:404:8053::7)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: ef637d77-f48f-40de-7c91-08d9fca87acf
X-MS-TrafficTypeDiagnostic: OSAPR01MB4019:EE_
X-Microsoft-Antispam-PRVS: <OSAPR01MB40194BF627824B533618D3E9CA039@OSAPR01MB4019.jpnprd01.prod.outlook.com>
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: bICQPDgjj8R19AenIe2hEoSnEOovfAaSRlfDx2Sa+yHZG8zwEZN5hw2l3ahK/vy47CoW+9hzYCpn7a/TN/jPaggT37iJY1qhho9Gk+sJJc3BHGtkBgWr0CaD1ZR55+6U/s4N2zgInK0trQJixMieHsrLzpm5yfu+oaqmouVRc3FOC6Dp7lKFvTWRHgAMPzFmAsG3t/+f3lZKYeuPwRne16bSXb5Nd4q9dNgo5hY0DECbhbjQ7TRTPE5w3TyKPWZBc7TcYhUlRH1ZEohM4YF6hy57R14usA0VpGTI4VOfcX5jdlCnJNUhGpccLqe1sbgmaPkgm4AXx1DV8sh2x+zjrFNyNoh43D74n/TyhBI64PRizDfKQN2qDnoSmUWYxI4TGA4oCrcICxwDf/gb7SM+gPGKZSw2o5R+cg7tX0XOZLgT02qMshnJfQEra3Mlk3cyrtIQwTVd3DnCFDKYrx8asfyvQDZ1TmWPAvHQXbjtpCMTZAEJW/eKT3d/jvuqgdBj4D18E7vmadQajZVF9FDGN23NWreK5pqWlYTPQGVNwOW0514UTnmkVKoXPjPxIZ8RJVyb8rH067rizk2jXLv6yMXjuJ9xa/UAagoefE98ky/o8sgawDDnSJmVXIvr5WsHv8HSkut7x3HXCYlGUlYIC8Oj/f/h/BPtU8N/EPz4kZQnoeG6gu8Y4/WUwXgPOq1Va9iiWPaN75yBCWAEqLG7iqzbTghqCrtfY2zhGdBHvxtU08mm20tHenQ4CtiJQPXEnx/mvhWGDOloszimiiFOzw==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:TYAPR01MB5689.jpnprd01.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(346002)(39840400004)(136003)(376002)(366004)(396003)(6486002)(186003)(26005)(38350700002)(38100700002)(4744005)(6916009)(450100002)(6512007)(31686004)(2906002)(2616005)(66476007)(31696002)(53546011)(66946007)(66556008)(4326008)(8676002)(52116002)(508600001)(83380400001)(86362001)(5660300002)(6506007)(316002)(8936002)(36916002)(786003)(45980500001)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?aitNM0hZa0hnbXpyR1R0ZmE1ZmhxTmsxU0RMM2QwckMyaVF1MTY2UUxvUTAr?= =?utf-8?B?ZGlCeU8wR2pWd1IyUmpJOVp4cDVFSlZxRjU1ZnFibUdQSWs2ZnNvMGlhTW8r?= =?utf-8?B?M0NiaEhnNUczTVlvdXd4dDhGOHpYWG5zVG1iaCtVR1pGb1gwZkEyZkUvQnZk?= =?utf-8?B?bGVWUVQyandQUk5uSnIyMXArWGpKdGZwSWU4TksxK2FIcEVkdFlpSGNra1kx?= =?utf-8?B?UHdrbFdoUXRvUE1COE9aYkhaeloyRDJSL0pZQmpoNkxEWENqMzdDRUdrM1VE?= =?utf-8?B?dUlVdDBpRUh6ZXl0MklINUR6NXJEazRXazVLTHJzMFljSFlOS1dCQk92NGdv?= =?utf-8?B?TVJlSE90cEIvSXU4Rk1CeFRkRTdHOUwvVGJMbDRscGhCZzdyYVpzZi9rdGN2?= =?utf-8?B?REUvQnd2a0NZUWpwNmxueTRSNWQ0V3J2d1R6bDBsT0Z2eXR6cFdITjRrNTdZ?= =?utf-8?B?czRLd1NlNDlocmFGa3p0WDAwWTUyTnhVZ0E5NGVrOFU3Tnc4SUNsMmZYN1JE?= =?utf-8?B?Rlp1dEJsZEs3QTRaVHJMaGpMdmcrUGptaUVEYlMyYUZtQ3VIZzV6RUoyOWpx?= =?utf-8?B?WG9RSUZNK2ZkMnJidTZMczFYamVoeVBDV2IvT0tMaUhmTldYR0ZnaDZkRjBI?= =?utf-8?B?UHpHcFNPai9scDhQdUFWdGNWQ0dhMmVCdUZmUlNveTlZVUpSMzZPTjJYeUxV?= =?utf-8?B?eW4yZUNobnpvNmUwMW0zcHRTM293amJqMEhxT3RhenF4V3dqakxralh3Ryti?= =?utf-8?B?S3Roa1BnM1E3MXBZTi9rTmtPQWRhdmdTVDN1WkUxQkVLNXRtbzRhaCtCbmQ5?= =?utf-8?B?ZkczMTN0c3ZhTmkrQzB1M1JmbXp2Z0pab055V0Rua0tOemZuZW5jZWVXZ2hG?= =?utf-8?B?YWlIOFc3MFBXMk8yS01vcUYwRzVIM0crbFdHOG1iQ1h2eUZQQXp2Z2l5aytF?= =?utf-8?B?aStzRWl4ZVRpOFNBTFBVN2RDaFNLRkFpSi91eGxrcE8xVlhydk93Q09jZVRm?= =?utf-8?B?c3I4NlA3YkFlUXpDbW8vRDhNWnloQVdUUFMvbVhRNXhaMDFUU3p3VFVPL091?= =?utf-8?B?TUNpSGV3aXJtNjRSTXJBVkdTSVBRWEc1VFFxcTJJaW5CNFlaTTZOQWx0OFVF?= =?utf-8?B?TGNtbFExdlNHU2VWQkRSVGlXbVpaOU5jUEFhSjJKRmNMOHJFYXdVWUI0T0FS?= =?utf-8?B?dnByaTkrdjVPVnVBdHhTSFR5MHRobHRiamV4TVBkSDhqMkhZcDZnc2kvN3BG?= =?utf-8?B?VFBtU0dUdlhnRVcra0t6SFQ3eVluUWh3cHZRQURITVRSQy9FY2NUWGsxZTZo?= =?utf-8?B?SVdyQ1QzS1NkVDU1T3dnbjh4RGFndkMrMGpvYk04YzlRS3AwaEQ2aDJENFoy?= =?utf-8?B?cVNubW8vRE1mL21xMzNlTlBTMUs3N2dNVk5jSkZLYVZlMlZuVFNpN2Y4cTFM?= =?utf-8?B?K0lSM2s0TzdJblBrTXhkT21DVHZqbmtZL25TL1RjRWl1WW0vK0NFU0djM2Va?= =?utf-8?B?R3NvK3lWcnVZenRKSng2S0xCN2kwbnA3ZkVLdGN4SUlGMWRtMjB6TXdlOWNw?= =?utf-8?B?aHBUZWw3OWgvVnZad2FnOFhTOEdJMFgrRjE1eVFCUlovdHFWV3ZVcU9jYUNW?= =?utf-8?B?R0xJUXpJQWJ2Nzc4SS9qVHJHdmRMSlYydTFXVzR2RHBmTmRJOGU5aTNZRTFs?= =?utf-8?B?NXVycHVLdGgxemRDeTJCRTlPQlhMQXdWNUR1QkpYUHQyUS9UcXhQYWRmKzRt?= =?utf-8?B?WkNaa2Vsb09RVnl3aTlXNXBpMmFlN2EyMVFhRTZLYWFLYW9FdVhBNjBXK2Uz?= =?utf-8?B?U3d4VS9NWkhZOTlvS0tuUE1rVEVwUWU4L2Q1RzB0NnhScnhlbEZJbWtEbE42?= =?utf-8?B?RFU5NHJLMU4wQjhsM0YvSzgyUS94cEpaLzNaN3llQlhRTmVSVGc4Qjc3QTBI?= =?utf-8?B?VmFlbWI4YVdXeW56YjdILzBnUGNEbmRiTFI5dHQrWVh4Nm04VXFCWWluTzBr?= =?utf-8?B?dUQ3SFZLaFRoQnBXSXowWHh5eDB6U1RNcUNRaTNOaEVzNEY3WExmWkVDY1hW?= =?utf-8?B?U2g4VlZRcTY3Nk5CR3E0NWN3ZlpOMUw3T25sMDdJWXRscTRQY1FlendsWmVk?= =?utf-8?B?eTB6UUcrLy8xdjhFc3pHYWMvT2dzOVl4UERrM29iV09Qa05yN1lkV2F2THNJ?= =?utf-8?Q?g3q+rAq7Pi5/4xNy1XEypvg=3D?=
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: ef637d77-f48f-40de-7c91-08d9fca87acf
X-MS-Exchange-CrossTenant-AuthSource: TYAPR01MB5689.jpnprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Mar 2022 23:57:59.6477 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 8+hipvHa+HIpoe3Z6uLWjY1kDnqt8kA228oeg/cVohC+YGzahTBK83oRG7ZBP+XNeYTzIj9HM8rt2SD7t6BMjQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSAPR01MB4019
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/rzZtDLO5Rqkbuiyr0BhJQgVwZLs>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Mar 2022 23:58:08 -0000

Hello Jay,

Many thanks for your quick action.

Regards,   Martin.

On 2022-03-03 08:11, Jay Daley wrote:
> 
> 
>> On 2/03/2022, at 9:35 PM, Jay Daley <exec-director@ietf.org> wrote:
>>
>> Hi Martin
>>
>> That should be possible.  I believe it means issuing a release of the templates and then linking to the latest release of each file.  I’ll ask one of the devs to help sort that and get authors.ietf.org updated.
> 
> This has now been done.  For those interested - the /blob/ was replaced with /raw/ in the path.
> 
> Jay
> 
>>


From nobody Wed Mar  2 16:18:55 2022
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCD53A0F5C for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 16:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ORF6_bwR0-LF for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 16:18:48 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC46F3A0F2F for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 16:18:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id BE97D40C3E5F; Wed,  2 Mar 2022 16:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9MPTX7spHhB; Wed,  2 Mar 2022 16:18:48 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 01A72404BF3F; Wed,  2 Mar 2022 16:18:47 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <A2C87604-926A-4CCC-896A-11264962E151@tzi.org>
Date: Thu, 3 Mar 2022 13:18:40 +1300
Cc: =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AA6EE03-748E-44A8-A217-C8AAEC9AB0DA@ietf.org>
References: <7f5b1796-f986-c2e7-85d8-de1bfbab7b7f@it.aoyama.ac.jp> <AED6215D-E9CA-4706-AB62-3245DF794497@ietf.org> <AB39CD29-EF05-4B88-8254-E7BE649F4C49@ietf.org> <A2C87604-926A-4CCC-896A-11264962E151@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/RC1jCkri-rdMy_icDZWu7Cc1FV4>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 00:18:54 -0000

> On 3/03/2022, at 12:15 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On 3. Mar 2022, at 00:11, Jay Daley <exec-director@ietf.org> wrote:
>>=20
>> This has now been done. =20
>=20
> Thanks!
>=20
> Though not on
> Martin Thompson's Markdown Template

Done.

Jay

>=20
>> For those interested - the /blob/ was replaced with /raw/ in the =
path.
>=20
> Good to know =E2=80=94 I=E2=80=99m always using =
raw.githubusercontent.com and now I=E2=80=99m wondering why.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20

--=20
Jay Daley
IETF Executive Director
exec-director@ietf.org


From nobody Wed Mar  2 17:02:48 2022
Return-Path: <johnl@iecc.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78A223A09EB for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 17:02:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.862
X-Spam-Level: 
X-Spam-Status: No, score=-1.862 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=SIMmv62J; dkim=pass (2048-bit key) header.d=taugh.com header.b=joNPpeRh
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 w2Mnp8T-AF2D for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 17:02:40 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 5F9A33A08A1 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 17:02:40 -0800 (PST)
Received: (qmail 75812 invoked from network); 3 Mar 2022 01:02:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=12820.622013ae.k2203; bh=tI2i7cKbQU097KeBY758xwN86gdIqFe9nA131iFSQmQ=; b=SIMmv62JwfkiSEejYB7DZRJwBQQpcjLHo4rxf579w0c01tYWHeQeyseXxClfBaeVKHUNSycAOp5Kk8ZLXTFsKVu9wBiaEpdF1DBCZidbFAy8MkKN+ewejSHpnhLUWkiaLRw8rqfiynE66ik/4QEFDV+PjTw4Yf8VPs+5fGHwFQNjLaxCX/mZySYE0SMV1CTLy3KEVgnC6xUgEVFRgQk/l7cXoFZQ68+NAfzZhCQ+lcNHbVJ6TnA1RBGQqDiVMF1V2qrjHR9sg/ZRCBT8tUdK432e2CpV+H9Tiukqdb42yUXwXq+BlC/yGi0SzCkhL6RspvrFYSO73YuvTgrLCmRNlw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=12820.622013ae.k2203; bh=tI2i7cKbQU097KeBY758xwN86gdIqFe9nA131iFSQmQ=; b=joNPpeRhvxnkEH8h+S8FDJqNOzs24//1+GZftumAJhGmdq8ZDotKThwcljeh7rvB7u1FpIiwAwZgT1nFRNcmJoKa9cYY2C6FI1ola0zj2I1U20fxkyetBdVUHD1Y1P4jkADL/rFfHtIVuI4g3znBm/2iowbuQC6plj6/dx8/eaaqBK52F9hE6XaCyoVHj/1xEDqopmDOSPgWdxSPLLIa9fd1pbaokCdaBEhu34Ya63ozhSWqgE1jHAknmQLXPEiZExqsL37yMiqwfuucd3h8kPDAniOi5zpaKJ+JIlW9/pmfBPLG936GZzXzLypAwkPYbv6s7OCrJZO32BvfgOg8EQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 03 Mar 2022 01:02:37 -0000
Received: by ary.qy (Postfix, from userid 501) id 9853838633C3; Wed,  2 Mar 2022 20:02:35 -0500 (EST)
Date: 2 Mar 2022 20:02:35 -0500
Message-Id: <20220303010237.9853838633C3@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: xml2rfc@ietf.org
In-Reply-To: <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/D5jLUEMK0MQNmKAS48XxAryiCyA>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 01:02:46 -0000

It appears that Carsten Bormann  <cabo@tzi.org> said:
>Kramdown-rfc is hitchhiking on this by also outputting mongrel documents and using xml2rfc as the source of truth on v3.

The current version of 7991bis matches xml2rfc other than taking out
<list> which I can put back if you really need it, and the optional
<country> after a seqence of <postalline> which should be added
shortly.

Other than that the grammar in xml2rfc hasn't changed since 3.0 two years ago.  Really, it's time to stop using v2.

R's,
John


From nobody Wed Mar  2 17:23:46 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5683A0A38 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 17:23:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 Y289cnt0amIg for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 17:23:39 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A5133A0854 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 17:23:39 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K8CtH31CBzDCgs; Thu,  3 Mar 2022 02:23:35 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20220303010237.9853838633C3@ary.qy>
Date: Thu, 3 Mar 2022 02:23:34 +0100
Cc: xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <23E9AC64-E66E-4B96-A94B-5A55DEED6775@tzi.org>
References: <20220303010237.9853838633C3@ary.qy>
To: "John R. Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/uliYwx79cbNYSJ1v3qlCYeYZomc>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 01:23:45 -0000

> On 3. Mar 2022, at 02:02, John Levine <johnl@taugh.com> wrote:
>=20
> It appears that Carsten Bormann  <cabo@tzi.org> said:
>> Kramdown-rfc is hitchhiking on this by also outputting mongrel =
documents and using xml2rfc as the source of truth on v3.
>=20
> The current version of 7991bis matches xml2rfc other than taking out
> <list> which I can put back if you really need it,

Yes, please.

> and the optional
> <country> after a seqence of <postalline> which should be added
> shortly.

That is a very good change.

I hope we can get some of the work on making the grammar more regular =
and more structured done next, so we can use author names in list items =
etc.

Besides the grammar work, we also need to work on the less-documented =
restrictions that are posed outside the grammar, e.g., character set =
issues.

None of these require terminating the transition prematurely.
Actually, the transition strategy merges nicely into a world where we =
distinguish format variants less by version number and more by purpose, =
e.g., authoring, RPC editing, publication.

> Other than that the grammar in xml2rfc hasn't changed since 3.0 two =
years ago.  Really, it's time to stop using v2.

Yeah, it=E2=80=99s time to stop doing a lot of things=E2=80=A6
Or, more precisely to start stopping things.
I did mean it when I said 5-10 years=E2=80=A6

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  2 18:25:11 2022
Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB013A0A13 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 18:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.111
X-Spam-Level: 
X-Spam-Status: No, score=-7.111 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=UDefKJ5a; dkim=pass (2048-bit key) header.d=taugh.com header.b=PCfMb6pZ
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 ip4zO4CFHlBu for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 18:25:04 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 00CBD3A10AF for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 18:25:03 -0800 (PST)
Received: (qmail 95445 invoked from network); 3 Mar 2022 02:25:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=174d1.622026fd.k2203; bh=w/W3h8IhaZN3U0ARgepeUond+tRqEJzKHylSGBALOmE=; b=UDefKJ5ayyys2xL8nUnLcVvuy2GRuPvmqAay3Bq1/hwlP7cX/0sGFQWT+kyO0XmjikSkb7E3DuwqtTG3hW7PiGacW9dgoz/K6mKc+f8aky3TscVXJYgv/mIrIDjHZ/JwNxsUUDLUUpq2XLnzSqCmdgg+vN4aEYyX56Ht8wJj/UM/H4vfS+uuIg686WlGypzhuAy9PR7PIpfhqS0T7Iqi+U3gNL8OCIuJH1tVFN1OL0n4d+HAyzOnRq09OmU7e10zCnyC+1KYS5B0vuFFammEcpVC/Yt5Y21cIYebOWwFD8U+qrWLLqeGjTMkN9EMnXGet+GPFWTP7G4MLByVvG8JGw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=174d1.622026fd.k2203; bh=w/W3h8IhaZN3U0ARgepeUond+tRqEJzKHylSGBALOmE=; b=PCfMb6pZCKuKlINYsvOYgCgGsQ5WOZSgcSlwHJERB4kcSn6GjiaSmOUmjWp1HK02ty34LPYNz/kKLQOI8x2ViqwMbPtnwxI3eqNME0k/gLgmTKDZTyxZcYABU3lf5xHJsvy7fypG7XL1CocranikNoMw1MmjNaUFnjZE8Oz2wnLVcx5v7JDRE6xRh3ITVWyiC7klYBC053eZ+6BGiEmxxJAsFJ4uM+h0gG8qC+A6ocYLk+GnT2FBnTAxAcwg0DgW9qAiYj8iMrJGM8YXZZbnK62JMXTzyH+XnVM+okOOKes6sJXRIkcJyoTxqbmauKU06XvQhWsiliahc3vFOO/aQw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 03 Mar 2022 02:25:01 -0000
Received: by ary.qy (Postfix, from userid 501) id 2C63F3864422; Wed,  2 Mar 2022 21:25:00 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id E81F73864404; Wed,  2 Mar 2022 21:25:00 -0500 (EST)
Date: 2 Mar 2022 21:25:00 -0500
Message-ID: <93fc2e70-99dd-3f64-f608-0885436112f3@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <23E9AC64-E66E-4B96-A94B-5A55DEED6775@tzi.org>
References: <20220303010237.9853838633C3@ary.qy> <23E9AC64-E66E-4B96-A94B-5A55DEED6775@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/aTmW3TaXkTrvf53syjp-UmQRnPM>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 02:25:09 -0000

>> The current version of 7991bis matches xml2rfc other than taking out
>> <list> which I can put back if you really need it,
>
> Yes, please.

If kramdown puts a <list> into the generated XML, that means that when the 
document is edited, the editor has to manually flag it and try to guess 
which kind of list it is, since published RFCs use the un-deprecated kinds 
of lists.  That doesn't seem like great tooling.

> I hope we can get some of the work on making the grammar more regular 
> and more structured done next, so we can use author names in list items etc.

For v4, perhaps.  As I hope you are aware, v3 has been frozen for two 
years other than a few tiny tweaks like <postalline>.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Wed Mar  2 18:34:38 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F3623A10D2 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 18:34:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 MJo8pUFlMXUt for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 18:34:33 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E52413A10CF for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 18:34:31 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K8FS43JVFzDCgc; Thu,  3 Mar 2022 03:34:28 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <93fc2e70-99dd-3f64-f608-0885436112f3@taugh.com>
Date: Thu, 3 Mar 2022 03:34:27 +0100
Cc: xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F1B0321-77C6-4AA2-AE6A-2561B88CCC8E@tzi.org>
References: <20220303010237.9853838633C3@ary.qy> <23E9AC64-E66E-4B96-A94B-5A55DEED6775@tzi.org> <93fc2e70-99dd-3f64-f608-0885436112f3@taugh.com>
To: "John R. Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/ueuYaAe6Tpg3RzWvz7wptsIxkAo>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 02:34:36 -0000

>>> The current version of 7991bis matches xml2rfc other than taking out
>>> <list> which I can put back if you really need it,
>>=20
>> Yes, please.
>=20
> If kramdown puts a <list> into the generated XML, that means that when =
the document is edited,

You keep saying that.
The document will have been processed by xml2rfc =E2=80=94v2v3 by then, =
so the editor will never see the <list.

> the editor has to manually flag it and try to guess which kind of list =
it is, since published RFCs use the un-deprecated kinds of lists.  That =
doesn't seem like great tooling.

We already have all the tooling that is needed to generate native v3 for =
editing and publishing.
It=E2=80=99s just distributed between kramdown-rfc proper, which takes =
care of the needs of the author, and xml2rfc, which takes care of the =
needs of the editing of the XML files into the form finally to be =
published.

>> I hope we can get some of the work on making the grammar more regular =
and more structured done next, so we can use author names in list items =
etc.
>=20
> For v4, perhaps.  As I hope you are aware, v3 has been frozen for two =
years other than a few tiny tweaks like <postalline>.

I honestly don=E2=80=99t know why we are doing this to ourselves.
These are bugs, and bugs need to be fixed.

I=E2=80=99m not sure we have a roadmap for a v4, but then I don=E2=80=99t =
care at the moment, as v3 is good enough for now ONCE WE FINALLY START =
FIXING ITS BUGS.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  2 18:50:15 2022
Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEA3E3A10DE for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 18:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 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, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=haQN4YTX; dkim=pass (2048-bit key) header.d=taugh.com header.b=BnLe4AL5
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 pbTV-EtEog1o for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 18:50:09 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D0C393A10DC for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 18:50:08 -0800 (PST)
Received: (qmail 2923 invoked from network); 3 Mar 2022 02:50:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=b68.62202cde.k2203; bh=ALIMN2b+ROSdJbEIApMIM7DljJynJjdWeTN5/DMUJQM=; b=haQN4YTXn7+6pIv5KEKS6fuuR1IO+ykNJc34S3ARzjPELc+RBGYzgOUCM6tIqnTNAH4FsfJT1dMM0ANjdMrysUzpR0p8LupzMQNUxPCuVmdtAxxeuxu1foAHtawutHHwwx3tF3H5jtRwuiy83MhU9t3TwcHvcVA7giO6FklkUNp/OSIZCI/gtRgSMu7IBOy1BG3nR8ehVm/7Xvv45vTbdT9iure5pbaU/AxmT8E1PLfPqi1l9d5Jvu8QTep+QgKCgj59rSfxQOnKca3Cpipn6dYiNl00ZW/bjomRqtb5sQXkcHadj7JzZ9R3TeqpczMuwhjzUEkLBOv+GoFMt5yL0Q==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=b68.62202cde.k2203; bh=ALIMN2b+ROSdJbEIApMIM7DljJynJjdWeTN5/DMUJQM=; b=BnLe4AL58wNQoEtUxad5hMeJ7jcJm36KVBeBKe3WnvtBVDBYX0l3HotAA2PRE/AaW/29n8ZQRdYt/X0w0Uh0P9T5sMtcxgTwktKFs3ogxf49DxKsCGW8d7lUyAQOiCCb6meGNlT0vPDqdgHZ5HpYusjKWtwm3PgeyXoMmVkr3G07XyARL+m+f1v0zvXlJ8V/kapsYCsNJDG1D1g8EoStoXzTuNEPIXMOfN6yNQw/OoSPYuEENAMERQ0LxTlHA93okRIEuTTfhYHF3NfhBiUG8Ovonmj+IYEgnGN2gNnulFSaQEyzpQ3xb8HbkAoGEAiaAd3FEKlRD6M4lnJmIGtrqw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 03 Mar 2022 02:50:06 -0000
Received: by ary.qy (Postfix, from userid 501) id 04D353864660; Wed,  2 Mar 2022 21:50:05 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 8F2F53864642; Wed,  2 Mar 2022 21:50:05 -0500 (EST)
Date: 2 Mar 2022 21:50:05 -0500
Message-ID: <b2dcab56-d3dc-c268-4e33-f23b91c5a47f@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <6F1B0321-77C6-4AA2-AE6A-2561B88CCC8E@tzi.org>
References: <20220303010237.9853838633C3@ary.qy> <23E9AC64-E66E-4B96-A94B-5A55DEED6775@tzi.org> <93fc2e70-99dd-3f64-f608-0885436112f3@taugh.com> <6F1B0321-77C6-4AA2-AE6A-2561B88CCC8E@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/l5qPMF3Rq07Km3mrZvahTFtYt84>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 02:50:14 -0000

>> If kramdown puts a <list> into the generated XML, that means that when the document is edited,
>
> You keep saying that.
> The document will have been processed by xml2rfc —v2v3 by then, so the editor will never see the <list.

RFC 7991bis describes the v3 grammar.   If for some reason you're still 
generating v2, that's still RFC 7749.

>>> I hope we can get some of the work on making the grammar more regular and more structured done next, so we can use author names in list items etc.
>>
>> For v4, perhaps.  As I hope you are aware, v3 has been frozen for two years other than a few tiny tweaks like <postalline>.
>
> I honestly don’t know why we are doing this to ourselves.
> These are bugs, and bugs need to be fixed.

If you believe there are bugs, please submit tickets.

R's,
John


From nobody Wed Mar  2 19:23:46 2022
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E352A3A1117 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 19:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 drg6JhpRjFSZ for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 19:23:39 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0EE63A0964 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 19:23:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id E7CE540C3E5F; Wed,  2 Mar 2022 19:23:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1bmJHjA580pn; Wed,  2 Mar 2022 19:23:38 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 39FED404BF3F; Wed,  2 Mar 2022 19:23:38 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org>
Date: Thu, 3 Mar 2022 16:23:33 +1300
Cc: "John R. Levine" <johnl@taugh.com>, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/ZUQyfBtQWoypFhNJGwGt0_04vWQ>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 03:23:44 -0000

> On 3/03/2022, at 11:12 AM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> Hi Jay,
>=20
>> I think we need to be a lot clearer about our use of "deprecated" and =
how we use version numbers. =20
>=20
> This is a very good point.
>=20
> We are using a transition model that employs the construct of a hybrid =
v2v3 document (what I have been calling the mongrel format).
>=20
> Authors can continue to use v2 documents and enhance them with v3 =
elements and attributes.
> xml2rfc =E2=80=94v2v3 converts these transition documents to v3, =
either with the =E2=80=94v2v3 flag or because a mongrel format document =
was supplied to =E2=80=94v3.
> The v3 grammar therefore describes the mongrel format as well as pure =
v3.

If I understand you correctly then your mental model of this is way off =
mine. The point about the use of deprecated features is about that means =
for forward compatibility, nothing whatsoever to do with purity.

Here is how I see it (translating your slightly unsavoury language):

pure =3D a fully v3 compliant document that should be forward compatible =
with v4 because no deprecated features are used.  In the software world =
this is normally called =E2=80=99strict=E2=80=99 format/mode.

mongrel =3D *also* a fully v3 compliant document but one that uses =
deprecated v3 features and therefore should not be forward compatible =
with v4 because those deprecated features should be obsoleted in v4.


For xml2rfc to swap out deprecated features for their intended =
replacements is just a feature of the tool, nothing more and nothing =
less. =20

For RFCs to be published in strict format (without deprecated features) =
is simply sensible future-protection and again nothing more and nothing =
less. =20

>=20
> Nothing about a v3.1 or v4 would change that transition model.  There =
are still tons of v2 documents out there that will gradually gain v3 =
functions.

If v4 obsoleted the v3 deprecated features then yes that would change.  =
In my view it is poor form to maintain deprecated features into the next =
major version as it implies that they should not have been deprecated =
and so v4 should obsolete those features and change the transition =
model.

v3.1 should not obsolete those features that if the principles of =
semantic versioning are followed.

> (Given that the transition started on 2020-09-04 with xml2rfc 3.0.0, =
and I would expect the transition to last some 5 to 10 years, this means =
we can stop worrying by end-2025 to end-2030.)
>=20
> Kramdown-rfc is hitchhiking on this by also outputting mongrel =
documents and using xml2rfc as the source of truth on v3.
>=20
> Of course, a v3.1 could cut off this transition model.
> This would simply be a hostile act to authors who are still using =
v2/mongrel.
>=20
> So I think =E2=80=9Cdeprecated=E2=80=9D here means: still part of the =
admissible input (authoring side) but no longer in use on the =
editing/publishing side.
> To better support the latter, it could be useful to have a v3-native =
grammar in addition to the existing v3 grammar.

It makes sense to have a strict version of the grammar (without the =
deprecated features) for validation by schema validators instead of =
relying on xml2rfc. =20

Jay

>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20

--=20
Jay Daley
IETF Executive Director
exec-director@ietf.org


From nobody Wed Mar  2 21:49:25 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754D13A1359 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 21:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 p57RnUAuhLUp for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 21:49:19 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED2443A1358 for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 21:49:17 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K8Kmp5nLJzDCh7; Thu,  3 Mar 2022 06:49:14 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <b2dcab56-d3dc-c268-4e33-f23b91c5a47f@taugh.com>
Date: Thu, 3 Mar 2022 06:49:13 +0100
Cc: xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5F675DD-09B5-477A-A37E-31D24D94DBA4@tzi.org>
References: <20220303010237.9853838633C3@ary.qy> <23E9AC64-E66E-4B96-A94B-5A55DEED6775@tzi.org> <93fc2e70-99dd-3f64-f608-0885436112f3@taugh.com> <6F1B0321-77C6-4AA2-AE6A-2561B88CCC8E@tzi.org> <b2dcab56-d3dc-c268-4e33-f23b91c5a47f@taugh.com>
To: "John R. Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Xru7RggzqmQBzx5yyzZg2G3Lvr8>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 05:49:24 -0000

On 3. Mar 2022, at 03:50, John R Levine <johnl@taugh.com> wrote:
>=20
>>> If kramdown puts a <list> into the generated XML, that means that =
when the document is edited,
>>=20
>> You keep saying that.
>> The document will have been processed by xml2rfc =E2=80=94v2v3 by =
then, so the editor will never see the <list.
>=20
> RFC 7991bis describes the v3 grammar.   If for some reason you're =
still generating v2, that's still RFC 7749.

Kramdown-rfc is not setting version=3D3 on the <rfc element, in order to =
trigger the v2v3 processing (*) in xml2rfc, so the end result is =
=E2=80=9Cpure=E2=80=9D v3.
Apart from that, its output should be within the v3 grammar (using v2 =
compatibility features), maybe sometimes triggering the issues in that =
grammar.

But kramdown-rfc itself does not directly put out the =E2=80=9Cpure=E2=80=9D=
 v3 grammar, as Jay called it; that is the job of the v2v3 processing in =
xml2rfc.

>>>> I hope we can get some of the work on making the grammar more =
regular and more structured done next, so we can use author names in =
list items etc.
>>>=20
>>> For v4, perhaps.  As I hope you are aware, v3 has been frozen for =
two years other than a few tiny tweaks like <postalline>.
>>=20
>> I honestly don=E2=80=99t know why we are doing this to ourselves.
>> These are bugs, and bugs need to be fixed.
>=20
> If you believe there are bugs, please submit tickets.

For a while, it wasn=E2=80=99t clear where to submit tickets on v3.rnc =
that would have advanced it further beyond 7991=E2=80=99s grammar.
But you can start with https://github.com/ietf-tools/xml2rfc/issues/519 =
and https://github.com/ietf-tools/xml2rfc/issues/570 =E2=80=94 I stopped =
submitting these when it wasn=E2=80=99t clear these would be processed.

(There are a few more non-grammar tickets at =
https://github.com/ietf-tools/xml2rfc/issues?q=3Dis%3Aissue+is%3Aopen+cabo=
+ .
Some of these are a bit hard to read because of limitations of the =
trac-to-github conversion.)

Gr=C3=BC=C3=9Fe, Carsten

(*) =
https://github.com/ietf-tools/xml2rfc/issues/658#issuecomment-1032284086



From nobody Wed Mar  2 22:11:11 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EADD63A136E; Wed,  2 Mar 2022 22:11:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 9UA89iS-emrN; Wed,  2 Mar 2022 22:11:05 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 874963A12AC; Wed,  2 Mar 2022 22:11:03 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K8LFt4C4jzDCdV; Thu,  3 Mar 2022 07:10:58 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org>
Date: Thu, 3 Mar 2022 07:10:58 +0100
Cc: "John R. Levine" <johnl@taugh.com>, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org>
To: Jay Daley <exec-director@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/p1QS_jU3_PMFwBg4kuQyPBkYplY>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 06:11:09 -0000

Hi Jay,

> If I understand you correctly then your mental model of this is way =
off mine. The point about the use of deprecated features is about that =
means for forward compatibility, nothing whatsoever to do with purity.

Right.  Not sure if I should switch to =E2=80=9Cpure=E2=80=9D (as below) =
then.

> Here is how I see it (translating your slightly unsavoury language):
>=20
> pure =3D a fully v3 compliant document that should be forward =
compatible with v4 because no deprecated features are used.  In the =
software world this is normally called =E2=80=99strict=E2=80=99 =
format/mode.

The grammar unfortunately does not express the distinction between (1) =
v3 features that are there for v2 compatibility and will be converted by =
v2v3, and (2) v3 features that are here to stay and can be published.

It would indeed be good to have a term for the latter =E2=80=94 =
publishable doesn=E2=80=99t quite hit it as that also implies prepped.

(It is somewhat ironic that prepping creates default values for =
compatibility attributes...)

> mongrel =3D *also* a fully v3 compliant document but one that uses =
deprecated v3 features and therefore should not be forward compatible =
with v4 because those deprecated features should be obsoleted in v4.

Yes.  See my answer to John; I don=E2=80=99t know whether a 7991 grammar =
compliant document that doesn=E2=80=99t set /rfc/@version to 3 is =
=E2=80=9Cfully v3 compliant=E2=80=9D.

> For xml2rfc to swap out deprecated features for their intended =
replacements is just a feature of the tool, nothing more and nothing =
less. =20

Yes.  It is also a brilliant part of the transition strategy.
I can=E2=80=99t trace who came up with this =E2=80=94 I suspect Henrik =
did.

> For RFCs to be published in strict format (without deprecated =
features) is simply sensible future-protection and again nothing more =
and nothing less. =20

Absolutely (but see the comment about attributes=E2=80=A6).

>> Nothing about a v3.1 or v4 would change that transition model.  There =
are still tons of v2 documents out there that will gradually gain v3 =
functions.
>=20
> If v4 obsoleted the v3 deprecated features then yes that would change. =
=20

There is nothing that would stop xml2rfc from having a v2v4 function =
that translates a mongrel v2..v4 into v4.

> In my view it is poor form to maintain deprecated features into the =
next major version as it implies that they should not have been =
deprecated and so v4 should obsolete those features and change the =
transition model.

There is no need for "v2 but only for compatibility in v3" features to =
be in the v4 grammar; we just need to ensure that the v2v4 processor can =
handle these.

> v3.1 should not obsolete those features that if the principles of =
semantic versioning are followed.

Right.

>> To better support the latter, it could be useful to have a v3-native =
grammar in addition to the existing v3 grammar.
>=20
> It makes sense to have a strict version of the grammar (without the =
deprecated features) for validation by schema validators instead of =
relying on xml2rfc. =20

v3-strict certainly is a better word than the one I used.
Do you happen to have one for "v2 but only for compatibility in v3=E2=80=9D=
 features (list, spanx, t/@hangtext, rfc/@seriesno =E2=80=A6)?
(We also need a word for already-deprecated v3 features such as relref; =
these should not be in v3-strict.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  2 23:33:59 2022
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B11623A13F0 for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 23:33:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 5NLqnRLp-mbY for <xml2rfc@ietfa.amsl.com>; Wed,  2 Mar 2022 23:33:52 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 502513A127C for <xml2rfc@ietf.org>; Wed,  2 Mar 2022 23:33:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id 1C719404BF40; Wed,  2 Mar 2022 23:33:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z8q65p4sJg6R; Wed,  2 Mar 2022 23:33:52 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 6288B404BF3F; Wed,  2 Mar 2022 23:33:51 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org>
Date: Thu, 3 Mar 2022 20:33:42 +1300
Cc: "John R. Levine" <johnl@taugh.com>, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B572167-50E2-4F33-9FEF-7415F4E652D6@ietf.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/NPAjMXyxr2LVIXYHLtduQn7KQjg>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 07:33:57 -0000

Hi Carsten

> On 3/03/2022, at 7:10 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> Hi Jay,
>=20
>> If I understand you correctly then your mental model of this is way =
off mine. The point about the use of deprecated features is about that =
means for forward compatibility, nothing whatsoever to do with purity.
>=20
> Right.  Not sure if I should switch to =E2=80=9Cpure=E2=80=9D (as =
below) then.
>=20
>> Here is how I see it (translating your slightly unsavoury language):
>>=20
>> pure =3D a fully v3 compliant document that should be forward =
compatible with v4 because no deprecated features are used.  In the =
software world this is normally called =E2=80=99strict=E2=80=99 =
format/mode.
>=20
> The grammar unfortunately does not express the distinction between (1) =
v3 features that are there for v2 compatibility and will be converted by =
v2v3, and (2) v3 features that are here to stay and can be published.

The grammar is never going to do that, it=E2=80=99s only a grammar.  =
Deprecation is human attribute and so expressed in the documentation

>=20
> It would indeed be good to have a term for the latter =E2=80=94 =
publishable doesn=E2=80=99t quite hit it as that also implies prepped.
>=20
> (It is somewhat ironic that prepping creates default values for =
compatibility attributes...)
>=20
>> mongrel =3D *also* a fully v3 compliant document but one that uses =
deprecated v3 features and therefore should not be forward compatible =
with v4 because those deprecated features should be obsoleted in v4.
>=20
> Yes.  See my answer to John; I don=E2=80=99t know whether a 7991 =
grammar compliant document that doesn=E2=80=99t set /rfc/@version to 3 =
is =E2=80=9Cfully v3 compliant=E2=80=9D.

I need to investigate this more but it does seem as if we have two ways =
to do the same thing in xml2rfc - by setting  /rfc/@version and by the =
-v3 or -v2v3 switch.  Ideally the version should be set in the document =
and the switches used to override but it doesn=E2=80=99t sound as if =
that is the way it works.

>=20
>> For xml2rfc to swap out deprecated features for their intended =
replacements is just a feature of the tool, nothing more and nothing =
less. =20
>=20
> Yes.  It is also a brilliant part of the transition strategy.
> I can=E2=80=99t trace who came up with this =E2=80=94 I suspect Henrik =
did.
>=20
>> For RFCs to be published in strict format (without deprecated =
features) is simply sensible future-protection and again nothing more =
and nothing less. =20
>=20
> Absolutely (but see the comment about attributes=E2=80=A6).
>=20
>>> Nothing about a v3.1 or v4 would change that transition model.  =
There are still tons of v2 documents out there that will gradually gain =
v3 functions.
>>=20
>> If v4 obsoleted the v3 deprecated features then yes that would =
change. =20
>=20
> There is nothing that would stop xml2rfc from having a v2v4 function =
that translates a mongrel v2..v4 into v4.

I don=E2=80=99t see what you mean by a "mongrel v2..v4".  None of the =
currently deprecated features in v3 should make it into v4 (or if they =
do then they should not have been deprecated). =20

>=20
>> In my view it is poor form to maintain deprecated features into the =
next major version as it implies that they should not have been =
deprecated and so v4 should obsolete those features and change the =
transition model.
>=20
> There is no need for "v2 but only for compatibility in v3" features to =
be in the v4 grammar; we just need to ensure that the v2v4 processor can =
handle these.
>=20
>> v3.1 should not obsolete those features that if the principles of =
semantic versioning are followed.
>=20
> Right.
>=20
>>> To better support the latter, it could be useful to have a v3-native =
grammar in addition to the existing v3 grammar.
>>=20
>> It makes sense to have a strict version of the grammar (without the =
deprecated features) for validation by schema validators instead of =
relying on xml2rfc. =20
>=20
> v3-strict certainly is a better word than the one I used.
> Do you happen to have one for "v2 but only for compatibility in v3=E2=80=
=9D features (list, spanx, t/@hangtext, rfc/@seriesno =E2=80=A6)?

I still think we are using language differently.  Features that were in =
v2 and are deprecated in v3 are just as much v3 features as the =
non-deprecated features - deprecation only affects their status for v4 =
where they should be removed.  Therefore there are only two grammars =
here

- v3
- v3 strict

> (We also need a word for already-deprecated v3 features such as =
relref; these should not be in v3-strict.)

Um, "deprecated features"?

Jay


>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20

--=20
Jay Daley
IETF Executive Director
exec-director@ietf.org


From nobody Wed Mar  2 23:57:39 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55C1F3A1413; Wed,  2 Mar 2022 23:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 XNaTMzeYwxpH; Wed,  2 Mar 2022 23:57:32 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EAE83A140D; Wed,  2 Mar 2022 23:57:30 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K8Nck4hc3zDDCF; Thu,  3 Mar 2022 08:57:26 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4B572167-50E2-4F33-9FEF-7415F4E652D6@ietf.org>
Date: Thu, 3 Mar 2022 08:57:26 +0100
Cc: "John R. Levine" <johnl@taugh.com>, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <297AD9FE-1947-47CD-8628-CF67E6921023@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <4B572167-50E2-4F33-9FEF-7415F4E652D6@ietf.org>
To: Jay Daley <exec-director@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/GSZO_rrb9HodqIIJqTx6BH5PYOs>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 07:57:38 -0000

>>=20
>> The grammar unfortunately does not express the distinction between =
(1) v3 features that are there for v2 compatibility and will be =
converted by v2v3, and (2) v3 features that are here to stay and can be =
published.
>=20
> The grammar is never going to do that, it=E2=80=99s only a grammar.  =
Deprecation is human attribute and so expressed in the documentation

Relax-NG has the concept of annotations.
I don=E2=80=99t know if there is a conventional way to use this like =
.feature in Section 4 of RFC 9165, but the basic infrastructure is =
there.

A grammar without such a mechanism is less helpful in protocol =
evolution, which is what we are talking about right now.

> I need to investigate this more but it does seem as if we have two =
ways to do the same thing in xml2rfc - by setting  /rfc/@version and by =
the -v3 or -v2v3 switch.  Ideally the version should be set in the =
document and the switches used to override but it doesn=E2=80=99t sound =
as if that is the way it works.

xml2rfc command line switches:
=E2=80=94v3 switches on v3 processing rules (which has been default =
since 3.0.0, 2020-09-04), so you get the formatter that has been =
rewritten for v3.
=E2=80=94v2v3 is something different: it specifies the *output*, i.e. an =
XML file that is converted to v3-strict; no rendering is done.
The document tells you the format of the *input*.
(A version field has all the typical problems that a version field has, =
I=E2=80=99m not going to elaborate here.)

> I don=E2=80=99t see what you mean by a "mongrel v2..v4".  None of the =
currently deprecated features in v3 should make it into v4 (or if they =
do then they should not have been deprecated). =20

As I said, I don=E2=80=99t care.  As long as somebody can take a v2 =
file, sprinkle in some v3 and v4 features, and get this processed by =
xml2rfc --v2v4, I=E2=80=99m fine.

Semantics one might attach to words such as =E2=80=9Cdeprecated=E2=80=9D =
and =E2=80=9Cserver=E2=80=9D are not relevant for this; this is just a =
user requirement.

(Again, we should think less in versions and more in processes and =
actors.)

> I still think we are using language differently.  Features that were =
in v2 and are deprecated in v3 are just as much v3 features as the =
non-deprecated features - deprecation only affects their status for v4 =
where they should be removed.  Therefore there are only two grammars =
here
>=20
> - v3
> - v3 strict
>=20
>> (We also need a word for already-deprecated v3 features such as =
relref; these should not be in v3-strict.)
>=20
> Um, "deprecated features"?

Yes, but I=E2=80=99m specifically talking about new RFC 7991 features =
that did not make it into what we call v3-strict now.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Mar  3 01:39:06 2022
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D14F3A14A4 for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 01:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 kDp2agV1_6bK for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 01:38:50 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B77723A08B1 for <xml2rfc@ietf.org>; Thu,  3 Mar 2022 01:38:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id 8F425404BF40; Thu,  3 Mar 2022 01:38:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TkQMG35jYosx; Thu,  3 Mar 2022 01:38:50 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id D3E8B404BF3F; Thu,  3 Mar 2022 01:38:49 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <297AD9FE-1947-47CD-8628-CF67E6921023@tzi.org>
Date: Thu, 3 Mar 2022 22:38:43 +1300
Cc: "John R. Levine" <johnl@taugh.com>, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <631D337D-7A7B-4803-8D00-F09256430305@ietf.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <4B572167-50E2-4F33-9FEF-7415F4E652D6@ietf.org> <297AD9FE-1947-47CD-8628-CF67E6921023@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/sBMbXfwbZ-MZAszSkWG3AL7PHxA>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 09:38:57 -0000

> On 3/03/2022, at 8:57 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
>>>=20
>>> The grammar unfortunately does not express the distinction between =
(1) v3 features that are there for v2 compatibility and will be =
converted by v2v3, and (2) v3 features that are here to stay and can be =
published.
>>=20
>> The grammar is never going to do that, it=E2=80=99s only a grammar.  =
Deprecation is human attribute and so expressed in the documentation
>=20
> Relax-NG has the concept of annotations.
> I don=E2=80=99t know if there is a conventional way to use this like =
.feature in Section 4 of RFC 9165, but the basic infrastructure is =
there.
>=20
> A grammar without such a mechanism is less helpful in protocol =
evolution, which is what we are talking about right now.

I=E2=80=99ve learnt something new - thank you.  My XML editor appears =
have multiple ways of displaying annotations to provide grammar =
assistance.

>=20
>> I need to investigate this more but it does seem as if we have two =
ways to do the same thing in xml2rfc - by setting  /rfc/@version and by =
the -v3 or -v2v3 switch.  Ideally the version should be set in the =
document and the switches used to override but it doesn=E2=80=99t sound =
as if that is the way it works.
>=20
> xml2rfc command line switches:
> =E2=80=94v3 switches on v3 processing rules (which has been default =
since 3.0.0, 2020-09-04), so you get the formatter that has been =
rewritten for v3.
> =E2=80=94v2v3 is something different: it specifies the *output*, i.e. =
an XML file that is converted to v3-strict; no rendering is done.
> The document tells you the format of the *input*.
> (A version field has all the typical problems that a version field =
has, I=E2=80=99m not going to elaborate here.)
>=20
>> I don=E2=80=99t see what you mean by a "mongrel v2..v4".  None of the =
currently deprecated features in v3 should make it into v4 (or if they =
do then they should not have been deprecated). =20
>=20
> As I said, I don=E2=80=99t care.  As long as somebody can take a v2 =
file, sprinkle in some v3 and v4 features, and get this processed by =
xml2rfc --v2v4, I=E2=80=99m fine.
>=20
> Semantics one might attach to words such as =E2=80=9Cdeprecated=E2=80=9D=
 and =E2=80=9Cserver=E2=80=9D are not relevant for this; this is just a =
user requirement.

AFAICT from reading RFC 7991 there is nothing in v2 that was obsoleted =
for v3, it was all deprecated (except the PIs but they are ignored) and =
if that=E2=80=99s correct there is no such thing as a "v2 document with =
a sprinkle of v3" that is simply a v3 document (even if it claims to be =
v2 in /rfc/@version).

It sounds as if you want a v4 grammar and a =
v4-with-v3-deprecated-features included, which defeats the point of =
deprecation.  When we get to v6, will be have a =
v6-with-v5-deprecated-and-v3-deprecated-and-v3-deprecated grammar?

>=20
> (Again, we should think less in versions and more in processes and =
actors.)
>=20
>> I still think we are using language differently.  Features that were =
in v2 and are deprecated in v3 are just as much v3 features as the =
non-deprecated features - deprecation only affects their status for v4 =
where they should be removed.  Therefore there are only two grammars =
here
>>=20
>> - v3
>> - v3 strict
>>=20
>>> (We also need a word for already-deprecated v3 features such as =
relref; these should not be in v3-strict.)
>>=20
>> Um, "deprecated features"?
>=20
> Yes, but I=E2=80=99m specifically talking about new RFC 7991 features =
that did not make it into what we call v3-strict now.

Now I=E2=80=99m confused.  What features are new to RFC 7991 that would =
not be in v3-strict given that v3-strict is v3 without any deprecated =
features?  Was a feature added as a new deprecated feature?

Jay

>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20

--=20
Jay Daley
IETF Executive Director
exec-director@ietf.org


From nobody Thu Mar  3 03:53:54 2022
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB813A0115 for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 03:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level: 
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 aPVG79Ed0Ice for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 03:53:47 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 4C9F93A0121 for <xml2rfc@ietf.org>; Thu,  3 Mar 2022 03:53:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1646308425; bh=94FFJ2LqfFuDH5isGgZmuQWxoqVMCPMOkYMF/fO8Kzs=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=QuDozBZObYCTrz5A3D550Kpp19I5KoVGYEFVEDOcCUtj5fL3w7TByKhjRJUaUZG9v KNikf9noqcJbu2b+Q7fzQj9Do5iETC3sfjzhZlnWDEZqw9nsXD8LgyIC4mKNcTFjVZ rFkk1XrLDYlSV22DwoC14CUVvyAeqgYH1d36tpSg=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.179] ([91.61.49.171]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N5VHG-1oEnQJ0iHi-016zNG for <xml2rfc@ietf.org>; Thu, 03 Mar 2022 12:53:45 +0100
Message-ID: <3b285169-f1f8-1a27-5308-90cf4bdbf0ff@gmx.de>
Date: Thu, 3 Mar 2022 12:53:44 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
To: xml2rfc@ietf.org
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <4B572167-50E2-4F33-9FEF-7415F4E652D6@ietf.org> <297AD9FE-1947-47CD-8628-CF67E6921023@tzi.org> <631D337D-7A7B-4803-8D00-F09256430305@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <631D337D-7A7B-4803-8D00-F09256430305@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:x8flYRhS0SI8rKGoK4s5mpHxpMv8gKru1bIDDZtPV+GCxHhFVkQ QzrrDWsbo/W3tdGM/y6Nlh5Iu6VO7t3ThaeTcWcsd3tclnkmmhliKAdl2aiyuk5KjBef/Dg EksfaowPKqOwL+yQsfn4uMUxLl92ze4kDDd9LZUjOtIQjaZYLzfjyVMkQtbVa0jMm3Qwh8J XNErfxQGESGeM7RpU43Sw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:P0fm93ze9Q8=:lT8akmJOialYw8xtft+ZB8 sUEgIcG74DRnh+Lwy1T1Ik0XOZcErR0r4c1n4JeHt4Xj5zWzsAzKM4hdvlGVRQwy6dkHr+CAA H61K0xXmmnmYEbV5CTLthJrPJmyaSBSJbIw21FmUz5hYG1BuoM57R5c7i7FWrhCHN0QrR6MMk 6A7iygCuTXVx98tlsCoUi3fvTS9mcWxJHRY5U7xbVLMRmcAphJ3uiwQI0NH9H8N3AuaJ5h5yr K+CoZLnFUYHWEtq15LL4IqMfULprC+NUA8iLaMEMuPlVIdeD90OmeooVubprxfjNu+Lmzxw0c BIn+aol0JWH1DZHU5+fIV8QpLU1ALK1fKoYoftXUdgpRhiKJBKTpDKWUmsKCz0qcsyjqwKAAp bL+SHd3QTyUNSHQaG/DK2FZJJMX05vCHFzLGKVaZzvVDmI5H1vUuSiCpE498dz333VIQYPynu vizkMicgzLJlBnZbirx+HRxeE8Mizu3EVlWZjJGF8FTyGylQ+6ZFdG2nAjK9bU4W1rVmE+9Rg tqTXU6a9STacCtZDmL7hXCZVSKKvA3W5gtE56NY35Pkpqaow1i+LBTQzCThG0Wg1PiWBDYkDZ xEGGNlQ9HdKw7OlPvnilygfxNngZZaudhu9lOUuY9STe5g9EkwKctBxrl9UrcqHBr3PhW+je/ Rs3PNeNdiZW0rU+VBb6QlPxeYDqN8mMFkGhiSoYtlcPRmVULlei4iOdU7EZU8u+Gkk9k/Y8jS P0ahdpNaEozxxwbiH/ZnRTZ0l4gIvoGVW1UIz6teFSFxzDBmJ575LGCi1MPhrvX3S6dPinGEO fIO/veqO4Gm+3SssD2PkJJZiUQsgSDlxP/LycbSAIUz7jwvpBNShB34gTPuV/PJEDizQNzEYC GmrYkmsLG2XXwQGB3cQlKEjsPXiR5P8MKF9Ul5jFAxMP7XQCZbWg9CU7NizbnO12Gqnkk1Jd/ jdu2xB9f94KXR/bHP/kL9yjGCBt2tTwmDHREno+gbJ8WwUYzIGzrbUlM7jhrh2+6LhlKjTvMh hQeyl42NDkM59Os5uxfpu8GbIsIJBIhg+IflH++cVrPdVEJxmV5euXAx0+O9W+3jJi7T0RcWy ZwECfv+07a/rFc=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/xoSAwd4l_D3kWdVIOofWpdZxGBo>
Subject: Re: [xml2rfc] Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 11:53:52 -0000

Am 03.03.2022 um 10:38 schrieb Jay Daley:
>
>
>> On 3/03/2022, at 8:57 PM, Carsten Bormann <cabo@tzi.org> wrote:
>>
>>>>
>>>> The grammar unfortunately does not express the distinction between (1=
) v3 features that are there for v2 compatibility and will be converted by=
 v2v3, and (2) v3 features that are here to stay and can be published.
>>>
>>> The grammar is never going to do that, it=E2=80=99s only a grammar.  D=
eprecation is human attribute and so expressed in the documentation
>>
>> Relax-NG has the concept of annotations.
>> I don=E2=80=99t know if there is a conventional way to use this like .f=
eature in Section 4 of RFC 9165, but the basic infrastructure is there.
>>
>> A grammar without such a mechanism is less helpful in protocol evolutio=
n, which is what we are talking about right now.
>
> I=E2=80=99ve learnt something new - thank you.  My XML editor appears ha=
ve multiple ways of displaying annotations to provide grammar assistance.

Those maybe?


<https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/blob/a15c9b47ac259=
d5da6e4b7baaa3f3061ba11e95b/xml2rfcv3-annotated.rng#L24>

:-)


From nobody Thu Mar  3 09:35:31 2022
Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 630133A07FD for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 09:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 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, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=CXIN5vmJ; dkim=pass (2048-bit key) header.d=taugh.com header.b=fbSf29mS
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 V1QvtL-qL6_j for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 09:35:23 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 4F3D03A00B1 for <xml2rfc@ietf.org>; Thu,  3 Mar 2022 09:35:22 -0800 (PST)
Received: (qmail 93135 invoked from network); 3 Mar 2022 17:35:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=16bcc.6220fc58.k2203; bh=uafbJb69eA3/bmYidhPUXi7ecg4CI+sgv2pom2bnme0=; b=CXIN5vmJizHXu3bpiW3vn3E2atI/2dnyWTH/4Qq1NbOaOhSctCwmZabWPhiKMNMGIqDhdoLdGOzMKDUzuOloikhynt/CQS/pazsDE0/IYHk/y+8fLM+7B6hP3jwPgdMPHidkOaM8cSLxzlKFzwwE8+57eqWgj9fSesea614hd7rx035gAIBJ/+ABB1TbLRhzXxHbSe1LuM+NgkpNEuweqER6dG4WuiY2kJLAGA+9mNHOAztS7s++v8ZJSkkwcMPE5elONMyRKbGBfI6EIqGoy9yFBK9Ub5jQyAYuSzPVU9UtNGrOvGPH3/x7DKaE4+sudT323T74L9Q+mjYXFi01FQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=16bcc.6220fc58.k2203; bh=uafbJb69eA3/bmYidhPUXi7ecg4CI+sgv2pom2bnme0=; b=fbSf29mSavPtt9Rzcp07olxLJ9qsgL98UgwWSGmtaBJ5Zor7TLthm/5+TVDkWJL7VVY5zP+6UJd1mExZqRVQXkPjx9RK79ySWqP93cLIJqObknQHZevTIqguYQn2ztfOWlNZexGKsHDLSXb1ot6hs1ZrTbVj5lazUrMKBWjG5EQMo9gduG54uPMz2U82ri2G2aGIywDrta8cFCYIuciM79XW2FWm55G+kQtQS9WWqUKwJPb87fWBvgoOiQEczVH+GEDIxO/Pum6RxUWWWnPSRFoRZ5a2+bDgLo6a4Ozi4fGbB4lBoqClMm8TEZ9lHicxXvp67gDlrMBHau+pPP2//w==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 03 Mar 2022 17:35:19 -0000
Received: by ary.qy (Postfix, from userid 501) id 4D11D386A269; Thu,  3 Mar 2022 12:35:17 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id A188C386A24B; Thu,  3 Mar 2022 12:35:17 -0500 (EST)
Date: 3 Mar 2022 12:35:17 -0500
Message-ID: <93d066de-7fe4-5899-bf8f-027ef4d542b6@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Carsten Bormann" <cabo@tzi.org>, "Jay Daley" <exec-director@ietf.org>
Cc: xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/gSt4lZ9e43b95yvf_z2lMoRJVdA>
Subject: Re: [xml2rfc] v3 is v3, was Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 17:35:30 -0000

> The grammar unfortunately does not express the distinction between (1) 
> v3 features that are there for v2 compatibility and will be converted by 
> v2v3, and (2) v3 features that are here to stay and can be published.

xml2rfc has separate grammars for v2 and v3.  In the github repo, look in 
the data directory for v2.rnc and v2.rng vs v3.rnc and v3.rng.

The v3 grammar is the v3 grammar, and we are not going to change it 
gratiutiously.  As many people including you have pointed out, we need to 
make a pass over it and regularize what elements can appear in similar 
contexts, e.g. text or block, but that is only going to allow things in 
addition to what's there now.

Some items like <list> and <relref> have never been used in a published 
RFC so we might as well take them out of the v3 grammar.  There are also a 
small set of things which are used but I think are ill-advised, like the 
complicated postal addresses and the rfc docName attribute.  If we change 
or remove them, we will need a plan to update the published XML so our 
published RFCs continue to match our published grammar, and we're not 
going o do that without a lot of notice.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Thu Mar  3 09:56:05 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4C8A3A1033; Thu,  3 Mar 2022 09:56:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 D9oGbcJgH-Sy; Thu,  3 Mar 2022 09:55:59 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E8533A1028; Thu,  3 Mar 2022 09:55:57 -0800 (PST)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K8dvG35sRzDChJ; Thu,  3 Mar 2022 18:55:54 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <93d066de-7fe4-5899-bf8f-027ef4d542b6@taugh.com>
Date: Thu, 3 Mar 2022 18:55:54 +0100
Cc: Jay Daley <exec-director@ietf.org>, xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 668022953.863315-2776f9243fe0986b6b73fe7605af5571
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC9F31D0-FCE2-4F07-B3D4-7E2F916D1169@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <93d066de-7fe4-5899-bf8f-027ef4d542b6@taugh.com>
To: "John R. Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/21EVurX-MzUMoX8VuGYUgxhKHOM>
Subject: Re: [xml2rfc] v3 is v3, was Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 17:56:04 -0000

> The v3 grammar is the v3 grammar, and we are not going to change it =
gratiutiously. =20

That is reassuring.

> As many people including you have pointed out, we need to make a pass =
over it and regularize what elements can appear in similar contexts, =
e.g. text or block, but that is only going to allow things in addition =
to what's there now.

Exactly the right approach.

> Some items like <list> and <relref> have never been used in a =
published RFC so we might as well take them out of the v3 grammar. =20

This mail started so good.

Now why are you proposing to take these out gratuitously?
The v3 grammar is not just for publishing RFCs.
It is a shared resource between authoring, editing, and publishing.

> There are also a small set of things which are used but I think are =
ill-advised, like the complicated postal addresses and the rfc docName =
attribute.  If we change or remove them, we will need a plan to update =
the published XML so our published RFCs continue to match our published =
grammar, and we're not going o do that without a lot of notice.

I think the grammar is the last thing that needs to change while we are =
stopping these practices (all these elements and attributes are =
optional).
More important is that the processing that we use is actually realizing =
these changes at the right point in the chain.

One thing I just noticed is that the RPC now seems to take out the =
=E2=80=9Cproduced by kramdown-rfc=E2=80=9D comments on the way to =
prerelease/rfcXXXX.notprepped.xml.  This change doesn=E2=80=99t help =
with statistics.  I don=E2=80=99t know whether this was an oversight, a =
feature of a new implementation, or a policy that is being applied =
manually.  The grammar of course does allow these comments.

Another thing we can=E2=80=99t help noticing is that the RPC is using =
old versions of xml2rfc.  E.g., the fresh AUTH48 draft I=E2=80=99m =
looking at has the line:
  <!-- xml2rfc v2v3 conversion 3.7.0 -->
Xml2rfc 3.7.0 was 2021-04-05, about 11 months ago (see [1] for more =
data).
This old version could be the cause of the spurious default-valued =
attributes on <section and <xref elements, which do not make our lives =
easier.
The grammar, of course, does allow these noise attributes, but the =
editing process obviously should not add them.

So the grammar plays a role in a few cases (including its irregular =
structure as you noted), but it is probably as important to make sure =
the processing steps actually work well.

A v3-strict grammar could exclude v2-legacy aspects and deprecated v3 =
aspects such as relref; it might be helpful to have available for tools =
that want to process published RFCs.

Gr=C3=BC=C3=9Fe, Carsten

[1]: =
https://github.com/cabo/kramdown-rfc/issues/162#issuecomment-1052859560



From nobody Thu Mar  3 10:25:03 2022
Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D86F3A107F for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 10:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=ltwnGZTX; dkim=pass (2048-bit key) header.d=taugh.com header.b=Lf9dg9/Y
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 9oYWJpTdeWLw for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 10:24:55 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 C5E703A107C for <xml2rfc@ietf.org>; Thu,  3 Mar 2022 10:24:54 -0800 (PST)
Received: (qmail 6036 invoked from network); 3 Mar 2022 18:24:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=1792.622107f4.k2203; bh=gHVqJGcJ5ogxZRYedHdkPDmuQZ2vtAFgVA8ZOlE9yiA=; b=ltwnGZTXH4EIbjfrCqQPUL8SIMy34HXNDi0hcMFWbGTW70JePSHUBG07b6fp4+64psAYdbfa7h6EDSWocpfxEg6eNo95oge96miBnp4dJFUlqxQUctzNcHIQJL+sGQzZLdUD35MPHWhr04qFrnrHYOduqvdvNLNLrBDQtC2fdXXLKFygZQoVqMcgJPzHoodT0J3oHgCIU6T2fFdZ2ir1NrKZajkrnxVSQ6nk6HKH6+3hLWNGldV5y9waRrArUQabdtS4twxBNOh9fNNBORdRp1t2/akFF5FynTGxXYCivxI2Ox24AuWpX1eKJb8zt/HwzuXss+o+YinptfQvW+VhDw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=1792.622107f4.k2203; bh=gHVqJGcJ5ogxZRYedHdkPDmuQZ2vtAFgVA8ZOlE9yiA=; b=Lf9dg9/YOxgCTA84YFitJw2bWUkLs5+93vpEMuVkfTqHE/AKCt58gn4cYlz7pI+zAXoZcmAg3Sl/1SEke/EMOd9NWTyOWzAsh98lKDb0XfH0m2eLY+aAmNcIOOhbwW+IeOOSU4YpNBWyQKl0uKn3KIC7KDR3XK2vg/YSd8j3B6Luq2NIXbcNa+RQ6mhR09qzJuB1NvHrl9qRLrkcCEqef8VjD9adC2AJwh0oDtLkGJ9eo8vaqVPZtAMtw/hWErrGXbit7zU2ZN0zh9+ACAb+3O0a03Nw0OiIrwibXa2sLGqlIPanafGGUPbe+iXqFpJSpJbPMSliCYLbhRUZUP2AbA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 03 Mar 2022 18:24:52 -0000
Received: by ary.qy (Postfix, from userid 501) id DC867386A707; Thu,  3 Mar 2022 13:24:50 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 2C12B386A6E9; Thu,  3 Mar 2022 13:24:50 -0500 (EST)
Date: 3 Mar 2022 13:24:50 -0500
Message-ID: <15a10638-790b-6dab-76e4-edceaec34606@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: "Jay Daley" <exec-director@ietf.org>, xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <BC9F31D0-FCE2-4F07-B3D4-7E2F916D1169@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <93d066de-7fe4-5899-bf8f-027ef4d542b6@taugh.com> <BC9F31D0-FCE2-4F07-B3D4-7E2F916D1169@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/y4ZXjhbIOoB9mniFRiiw5oEjSpQ>
Subject: Re: [xml2rfc] v3 is v3, was Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 18:25:00 -0000

>> Some items like <list> and <relref> have never been used in a published RFC so we might as well take them out of the v3 grammar.
>
> This mail started so good.
>
> Now why are you proposing to take these out gratuitously?
> The v3 grammar is not just for publishing RFCs.
> It is a shared resource between authoring, editing, and publishing.

If people actually use these things, sure, we can leave them in.  But the 
point of rfcxml is to provide an archival series, and the fewer bits of 
useless cruft we have to document and support, the better.

>> There are also a small set of things which are used but I think are ill-advised, like the complicated postal addresses and the rfc docName attribute.  If we change or remove them, we will need a plan to update the published XML so our published RFCs continue to match our published grammar, and we're not going o do that without a lot of notice.
>
> I think the grammar is the last thing that needs to change while we are stopping these practices (all these elements and attributes are optional).

The <postal> stuff depends on an abandonware library that I know is 
already out of date.  The processing is why we need to take it out of the 
grammar.

> Another thing we can’t help noticing is that the RPC is using old versions of xml2rfc.  E.g., the fresh AUTH48 draft I’m looking at has the line:
>  <!-- xml2rfc v2v3 conversion 3.7.0 -->
> Xml2rfc 3.7.0 was 2021-04-05, about 11 months ago (see [1] for more data).

I know their programmer installs new versions within a few days of them 
being released, so that is surprising.  I can check to be sure their staff 
isn't using old copies. but I'm also wondering at what point the 
conversion happened, perhaps when a draft was submitted.

To point out the obvious, the sooner our tools catch up and produce v3 
directly, the fewer problems we will have.  V2 has been obsolete for years 
as you have seen, trying to nurse it along just causes needless confusion.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Thu Mar  3 11:45:32 2022
Return-Path: <jmahoney@amsl.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD6BB3A0C4F for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 11:45:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 fSkTkmxb2aiq for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 11:45:24 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89CF13A0D56 for <xml2rfc@ietf.org>; Thu,  3 Mar 2022 11:45:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6990E425C195; Thu,  3 Mar 2022 11:45:24 -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 k0uyrFY-2vEO; Thu,  3 Mar 2022 11:45:24 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 30C71425C194; Thu,  3 Mar 2022 11:45:24 -0800 (PST)
Message-ID: <24f39552-6922-c32c-b82e-61fb580309d4@amsl.com>
Date: Thu, 3 Mar 2022 13:45:23 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: John R Levine <johnl@taugh.com>, Carsten Bormann <cabo@tzi.org>
Cc: xml2rfc@ietf.org
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <93d066de-7fe4-5899-bf8f-027ef4d542b6@taugh.com> <BC9F31D0-FCE2-4F07-B3D4-7E2F916D1169@tzi.org> <15a10638-790b-6dab-76e4-edceaec34606@taugh.com>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <15a10638-790b-6dab-76e4-edceaec34606@taugh.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/F4tkOJNwsXsNXzfIxcD1OHaZ2a0>
Subject: Re: [xml2rfc] v3 is v3, was Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 19:45:30 -0000

Hi all,

On 3/3/22 12:24 PM, John R Levine wrote:
>>> Some items like <list> and <relref> have never been used in a 
>>> published RFC so we might as well take them out of the v3 grammar.
>>
>> This mail started so good.
>>
>> Now why are you proposing to take these out gratuitously?
>> The v3 grammar is not just for publishing RFCs.
>> It is a shared resource between authoring, editing, and publishing.
>
> If people actually use these things, sure, we can leave them in. But 
> the point of rfcxml is to provide an archival series, and the fewer 
> bits of useless cruft we have to document and support, the better.
>
>>> There are also a small set of things which are used but I think are 
>>> ill-advised, like the complicated postal addresses and the rfc 
>>> docName attribute. If we change or remove them, we will need a plan 
>>> to update the published XML so our published RFCs continue to match 
>>> our published grammar, and we're not going o do that without a lot 
>>> of notice.
>>
>> I think the grammar is the last thing that needs to change while we 
>> are stopping these practices (all these elements and attributes are 
>> optional).
>
> The <postal> stuff depends on an abandonware library that I know is 
> already out of date.  The processing is why we need to take it out of 
> the grammar.
>
>> Another thing we can’t help noticing is that the RPC is using old 
>> versions of xml2rfc.  E.g., the fresh AUTH48 draft I’m looking at has 
>> the line:
>>  <!-- xml2rfc v2v3 conversion 3.7.0 -->
>> Xml2rfc 3.7.0 was 2021-04-05, about 11 months ago (see [1] for more 
>> data).
>
> I know their programmer installs new versions within a few days of 
> them being released, so that is surprising.  I can check to be sure 
> their staff isn't using old copies. but I'm also wondering at what 
> point the conversion happened, perhaps when a draft was submitted.

[JM]  The comment line is added when "xml2rfc --v2v3" is run on a 
document and is otherwise not updated.

All comments are stripped before a document is published.

Best regards,

Jean


>
> To point out the obvious, the sooner our tools catch up and produce v3 
> directly, the fewer problems we will have.  V2 has been obsolete for 
> years as you have seen, trying to nurse it along just causes needless 
> confusion.
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc


From nobody Thu Mar  3 12:40:18 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0DE53A0121 for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 12:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ZXdo0f9wwp_a for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 12:40:06 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F3333A00AF for <xml2rfc@ietf.org>; Thu,  3 Mar 2022 12:40:06 -0800 (PST)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K8jXg5xGBzDCdX; Thu,  3 Mar 2022 21:40:03 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <24f39552-6922-c32c-b82e-61fb580309d4@amsl.com>
Date: Thu, 3 Mar 2022 21:40:03 +0100
Cc: "John R. Levine" <johnl@taugh.com>, xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 668032803.3087471-10168a20da2681304f5d537ab95d8c7a
Content-Transfer-Encoding: quoted-printable
Message-Id: <80CA1A83-E7EE-4332-886A-F5F236E2AAF4@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <93d066de-7fe4-5899-bf8f-027ef4d542b6@taugh.com> <BC9F31D0-FCE2-4F07-B3D4-7E2F916D1169@tzi.org> <15a10638-790b-6dab-76e4-edceaec34606@taugh.com> <24f39552-6922-c32c-b82e-61fb580309d4@amsl.com>
To: Jean Mahoney <jmahoney@amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/qpUUfKRJXMdV1pgmvY2mIQ7Ygx0>
Subject: Re: [xml2rfc] v3 is v3, was Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 20:40:16 -0000

Hi Jean,

thanks for giving us some more details.

On 2022-03-03, at 20:45, Jean Mahoney <jmahoney@amsl.com> wrote:
>=20
> [JM]  The comment line is added when "xml2rfc --v2v3" is run on a =
document and is otherwise not updated.

In the specific case I was looking at, the v3 conversion was actually =
done by the authors in mid-2021 =E2=80=94 there just was a lot of =
waiting in the RFC editor queue for other documents before it could be =
edited.  So that explains the 3.7.0.  (Maybe a separate cleaning run is =
needed when editing is actually begun.)

> All comments are stripped before a document is published.

Which makes them even more useful as a transparency/diagnostic tool, =
including during the final phases of development (=E2=80=9Cediting=E2=80=9D=
).

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Mar  3 12:52:10 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7493A067A; Thu,  3 Mar 2022 12:52:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 maCNxhOlHg0Y; Thu,  3 Mar 2022 12:52:04 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C29A03A059F; Thu,  3 Mar 2022 12:52:02 -0800 (PST)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K8jpQ2ylYzDCcJ; Thu,  3 Mar 2022 21:51:58 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <15a10638-790b-6dab-76e4-edceaec34606@taugh.com>
Date: Thu, 3 Mar 2022 21:51:57 +0100
Cc: Jay Daley <exec-director@ietf.org>, xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 668033516.969722-151c12671f077f2b54e3bc1dfbc4afd4
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B32BA19-82CF-4BE4-B130-B533E6F63C86@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <93d066de-7fe4-5899-bf8f-027ef4d542b6@taugh.com> <BC9F31D0-FCE2-4F07-B3D4-7E2F916D1169@tzi.org> <15a10638-790b-6dab-76e4-edceaec34606@taugh.com>
To: "John R. Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/2eideW2VqdHInH8PFK1Tx8WAY9k>
Subject: Re: [xml2rfc] v3 is v3, was Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 20:52:09 -0000

On 2022-03-03, at 19:24, John R Levine <johnl@taugh.com> wrote:
>=20
>>> Some items like <list> and <relref> have never been used in a =
published RFC so we might as well take them out of the v3 grammar.
>>=20
>> This mail started so good.
>>=20
>> Now why are you proposing to take these out gratuitously?
>> The v3 grammar is not just for publishing RFCs.
>> It is a shared resource between authoring, editing, and publishing.
>=20
> If people actually use these things, sure, we can leave them in.  But =
the point of rfcxml is to provide an archival series,

=E2=80=A6 and supports all the steps towards that.
(Sorry, broken record mode.)

> and the fewer bits of useless cruft we have to document and support, =
the better.
>=20
>>> There are also a small set of things which are used but I think are =
ill-advised, like the complicated postal addresses and the rfc docName =
attribute.  If we change or remove them, we will need a plan to update =
the published XML so our published RFCs continue to match our published =
grammar, and we're not going o do that without a lot of notice.
>>=20
>> I think the grammar is the last thing that needs to change while we =
are stopping these practices (all these elements and attributes are =
optional).
>=20
> The <postal> stuff depends on an abandonware library that I know is =
already out of date.  The processing is why we need to take it out of =
the grammar.

Makes sense - this is just a very punctual part of the grammar, so there =
is less pain than something that affects all text.

>> Another thing we can=E2=80=99t help noticing is that the RPC is using =
old versions of xml2rfc.  E.g., the fresh AUTH48 draft I=E2=80=99m =
looking at has the line:
>> <!-- xml2rfc v2v3 conversion 3.7.0 -->
>> Xml2rfc 3.7.0 was 2021-04-05, about 11 months ago (see [1] for more =
data).
>=20
> I know their programmer installs new versions within a few days of =
them being released, so that is surprising.  I can check to be sure =
their staff isn't using old copies. but I'm also wondering at what point =
the conversion happened, perhaps when a draft was submitted.

(See my mail to Jean.  So, for this case, the RPC is off the hook, but =
I=E2=80=99m still shocked by the results of looking at rfc9???.xml.)

> To point out the obvious, the sooner our tools catch up and produce v3 =
directly, the fewer problems we will have.  V2 has been obsolete for =
years as you have seen, trying to nurse it along just causes needless =
confusion.

Yeah.  I hear that.  It=E2=80=99s a bit like IPv4.  And I need to =
explain occasionally (in about every second email) that kramdown-rfc =
produces v3 =E2=80=9Cdirectly=E2=80=9D, with the -c flag, employing =
xml2rfc as the XML writer.

I would feel much better if I didn=E2=80=99t get the impression that the =
fact that kramdown-rfc internally uses some v2 is becoming a mental =
excuse to play down issues that the authors using it do experience.

But above all, we need to get these 133 open issues addressed!

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Mar  3 13:54:59 2022
Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D35FC3A08A1 for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 13:54:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 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, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=pC/hSuiW; dkim=pass (2048-bit key) header.d=taugh.com header.b=hlUkvhgv
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 i9mqP9HsJKTN for <xml2rfc@ietfa.amsl.com>; Thu,  3 Mar 2022 13:54:49 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 7458C3A0768 for <xml2rfc@ietf.org>; Thu,  3 Mar 2022 13:54:49 -0800 (PST)
Received: (qmail 56913 invoked from network); 3 Mar 2022 21:54:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=de4e.62213926.k2203; bh=4orteU2/8I6QJR3Th+PIxxYfWzkX0pqS4SWo30BmNw4=; b=pC/hSuiWhPYme9XWgdagecgfZuT6aW2RwqNxkx1wSYpSKqst38d9hgjZOBxVc+V2dYlZEO8Oo7ddEUWCGXpxrBR5hR+Tpn8XSkqIuc39dKzFDZE9aASPCUa3oYWFHiXnQopzbwgeJUKplPhV4yeF7sKoWLaLzxDf4C2RFvWNGFjuBiSYRT92RUrNof3e6Roou1AYspCHaV4XsseWGHKzRHuOS/mIgXqd0ExRNt98sB/QSSlVN00iyNG9A9ebVmFeDHdgW3j6cXNcPyWthF3OA7k5D5EC9YU8twelewVsLqSlJV+PdkzHVpHlLSdEvy8KXEFw4TtsIE38Q7LUSYHdXg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=de4e.62213926.k2203; bh=4orteU2/8I6QJR3Th+PIxxYfWzkX0pqS4SWo30BmNw4=; b=hlUkvhgvNQU1AVG75azu4bQWkCkpDgyvE1ruwwLPlhCNnRXyo0Nw5dI8/s/wWceRqxQIcNFGhmJEj5TQzrhKpUIyL5ITsSGk9hnIDsE1VHHVvG0Vt/xlxJd6soc85VCoTCfLD0/aLZeQpcMvwHQUp7n8z2h18WqjFbKVgL7aZNzCZ/Pi3BoSG2QULoL4scP1hybn3ViDQlQzOIrSVXstpKcKKg9vMznmjvIQwRawG1qcDo6lFGLjk6CSBEkMsmYCWYhKB2jsjO52uiyYl3ckao7gNyFhZUQT8Ndn83dEy4298Q5+q3ZwCFYDY/fVZdiCxnSe0fzq+QniM/2gy5adug==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 03 Mar 2022 21:54:46 -0000
Received: by ary.qy (Postfix, from userid 501) id B453D386C5CF; Thu,  3 Mar 2022 16:54:45 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 34F67386C5B1; Thu,  3 Mar 2022 16:54:45 -0500 (EST)
Date: 3 Mar 2022 16:54:45 -0500
Message-ID: <623aefbf-6eae-140a-7a4b-2da1f5bae2d8@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: "Jay Daley" <exec-director@ietf.org>, xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <2B32BA19-82CF-4BE4-B130-B533E6F63C86@tzi.org>
References: <20220302183250.2C7BB385EAAB@ary.qy> <885C410A-5E5D-49A4-96EC-F438FA93628F@tzi.org> <83AAE938-6C40-4A94-810A-374D6BD45739@ietf.org> <CDFA681B-1CBA-416D-8561-D8EF906D3BFE@tzi.org> <BF23B915-8495-4BA8-86DD-1460C5698541@ietf.org> <C42B88DC-04BF-41D9-AA26-AE22CE3A5E96@tzi.org> <93d066de-7fe4-5899-bf8f-027ef4d542b6@taugh.com> <BC9F31D0-FCE2-4F07-B3D4-7E2F916D1169@tzi.org> <15a10638-790b-6dab-76e4-edceaec34606@taugh.com> <2B32BA19-82CF-4BE4-B130-B533E6F63C86@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/BJITeJYbPvYPFHIpaibG0iI-sTk>
Subject: Re: [xml2rfc] v3 is v3, was Links to rfc7991bis.rnc may need some fixing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Mar 2022 21:54:56 -0000

> But above all, we need to get these 133 open issues addressed!

We're working on it. got a lot addressed last month.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Sat Mar 19 05:49:42 2022
Return-Path: <roger@rogerprice.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72DB53A03F9 for <xml2rfc@ietfa.amsl.com>; Sat, 19 Mar 2022 05:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 QXAngoFh3rUd for <xml2rfc@ietfa.amsl.com>; Sat, 19 Mar 2022 05:49:37 -0700 (PDT)
Received: from relay10.mail.gandi.net (relay10.mail.gandi.net [217.70.178.230]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65AF13A00AD for <xml2rfc@ietf.org>; Sat, 19 Mar 2022 05:49:36 -0700 (PDT)
Received: (Authenticated sender: mailbox@rogerprice.org) by mail.gandi.net (Postfix) with ESMTPSA id 12DDE240007; Sat, 19 Mar 2022 12:49:33 +0000 (UTC)
Date: Sat, 19 Mar 2022 13:49:32 +0100 (CET)
From: Roger Price <roger@rogerprice.org>
X-X-Sender: rprice@maria.rogerprice.org
To: xml2rfc Mailing List <xml2rfc@ietf.org>
Message-ID: <alpine.DEB.2.20.2203191332410.4718@maria.rogerprice.org>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-Message-Flag: Supplemental report sent to reaper.nsa.gov. rc=0
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/wGS4WlxE1lARW-wW-gGTDhTNSAE>
Subject: [xml2rfc] Much repetition of "Paragraph 1" in references
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 19 Mar 2022 12:49:41 -0000

Dear List, I am seeing automatic inclusion of the mention "Paragraph 1" in many 
references.  It seems to me that these mentions are not needed and clutter up 
the output.

The anchor is coded as

  <section>
  <name>Events</name>
  <t anchor="events">A bla bla bla ... etc

The reference is coded as

  the events are listed in <xref target="events"></xref>.

The HTML displays as

  the events are listed in Section 5.2, Paragraph 1.

Is there some way of eliminating these paragraph references, except when really 
needed?

Roger


From nobody Sat Mar 19 06:03:49 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDC83A07A2 for <xml2rfc@ietfa.amsl.com>; Sat, 19 Mar 2022 06:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 q4kW7wQsneeG for <xml2rfc@ietfa.amsl.com>; Sat, 19 Mar 2022 06:03:41 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 624EF3A07DD for <xml2rfc@ietf.org>; Sat, 19 Mar 2022 06:03:40 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KLLff1JYvzDCbR; Sat, 19 Mar 2022 14:03:38 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.DEB.2.20.2203191332410.4718@maria.rogerprice.org>
Date: Sat, 19 Mar 2022 14:03:37 +0100
Cc: xml2rfc Mailing List <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 669387817.823125-4dbb909d50c45c2c7ec35444323dbd85
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B339039-ED9C-4E38-86EE-0E1C1ACA09A5@tzi.org>
References: <alpine.DEB.2.20.2203191332410.4718@maria.rogerprice.org>
To: Roger Price <roger@rogerprice.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/2DApVbMYeEvuRtt0RtJONZT2qEE>
Subject: Re: [xml2rfc] Much repetition of "Paragraph 1" in references
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 19 Mar 2022 13:03:47 -0000

On 2022-03-19, at 13:49, Roger Price <roger@rogerprice.org> wrote:
>=20
> The anchor is coded as
>=20
> <section>
> <name>Events</name>
> <t anchor=3D"events">A bla bla bla ... etc
>=20
> The reference is coded as
>=20
> the events are listed in <xref target=3D"events"></xref>.
>=20
> The HTML displays as
>=20
> the events are listed in Section 5.2, Paragraph 1.
>=20
> Is there some way of eliminating these paragraph references, except =
when really needed?

Yes.  If you don=E2=80=99t want to reference the paragraph but the =
section, put the anchor on the section and not the paragraph:

>>> <section anchor=3D"events">
>>> <name>Events</name>
>>> <t>A bla bla bla =E2=80=A6 etc

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sun Mar 20 04:11:44 2022
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D5733A1356 for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 04:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 JfnK3ZgyuSl3 for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 04:11:37 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 575B93A1328 for <xml2rfc@ietf.org>; Sun, 20 Mar 2022 04:11:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1647774694; bh=8XdSKwMoisFrwMBAqcAzgY+ib0dP9XwXdJAeyhZvQY0=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=NlckclZm/dGJ1+LlH1HTM4Gfvoh11MNGXDHGck5V3FdmaURGXra3Q4j8y9hOgJTom z6/X0RvjjUZ2y/gemjajpHdhS/QJRdkVp5d/Hr20bWbn55aOwyx2KhSV8SacYC7tLt ETq96Q/+Rvyg8PAV7ec5X4xsfzdK+Iplag7gHcdQ=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([84.171.158.65]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M2O2Q-1nWRAW0Upy-003qvq for <xml2rfc@ietf.org>; Sun, 20 Mar 2022 12:11:34 +0100
Message-ID: <062af102-4ab0-c08c-ce4d-c69360477108@gmx.de>
Date: Sun, 20 Mar 2022 12:11:31 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
To: xml2rfc@ietf.org
References: <alpine.DEB.2.20.2203191332410.4718@maria.rogerprice.org> <7B339039-ED9C-4E38-86EE-0E1C1ACA09A5@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <7B339039-ED9C-4E38-86EE-0E1C1ACA09A5@tzi.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:65pE3InJ2kTRr4krsQd0zukDPnDWfLaovVLqK7IxVm7qq/jci2E unuucZYOsfQowyAziQGWbBXH8a8Y2Qfff+ant4/t8GL1idwHIxDRWuHxR3QeH2nOtTCcomv cLTnwkzl0a4tYXueaBHHsrGJJ32IDHXozNV0rr+TgfDkpzSZP8bV9JOpJv4rtw+6mjqehA+ audqNWQjajafLKnJO6mQQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:r1wrGqerPQE=:CxdB5Tvqpx7lv3Aq+w5ws4 RECNCkfQcREVrNYnCrqFpJqXMMPkuBPJjbws888O9GBwnM2AK5QxBHnIJ2yhgPJzy9zMt2D06 /T2mCRJGNKXR4iELSKcL8b+toWOCe6fEXUiops3jKIP7gKWY5hEhwi9g9ThDnl/g7jy3R/xgI x55MhTCnYHapLvY2l4/Nsicxz1LlExV4Iqjd5zTdRAW41b3HThuoSoX9Zd5J+o7Ct87Uzcwfn UI7/GNUKSkMdnXXryWch07BqN8+Zn8DoYoASgSHpwmjByPnMQuNGaiNsSySnvfEOhDQ9H8NVy i6w+CFBcCZNOnENoExVrXdRjL2kbUhImSt/hdN6WiysM5IQlVv7xyyt90h3/M4n/1zmh9G4zE LoBOvNG2WriYwaTT7b5uZuS8U4arzrLJFHMCEBC49gGSEJkbbkaYfYDvv0JlsxAdWZg/5JFVD CQanGaZspakyInUXuT6zLJQB8B+6lbrxwvHHPEmH2s/LKbSt4t210OC299rRPuo6yixbFNgMD vr7soylHwHDS69Toiv89/P9z4jorHGG7ivZ6XstKxnGEAHyBfZOGIVhmzYBfRMWb49m9SI3l7 f0L5+bYnpxAa0UcjwW1pT9s1Fv41GTWSxIYomnHric8IRn3ATshSZnfNb8+jAW5kEfChyQGD+ Fq4j7305zqczD2F6GzPc/KWZXwi7KKkesq14/CXx6Uoor5l/ghb+/sSrWtFodg9eiuVPKptPg QbUfAiMfpmr/Y6JpSBg59Hy0fycgq5o7O5xr/1Hr4XE4ycNO/ZOe0bwBsQbOj5eM3A4atVehn 8ORpKYgPtbXUTua7DsNr56YiskTOz3tzlHevUBPZwMYmLtZaZwUvE9a642ccNnimot5ZqU4RC 0gJPgSNQMzBmY+TaPIzGfmSCSLT4Xvu9nme8bpgj7c1IqgfERk/6Y1eNEuAFawxMyJFK9qmrw bRw64nwr7EuvDmIKNXNE0RAUkVVeo73lzP7owu+aXYF5lQXMpbfiWDuoDl/qRskj/T4p6WDT4 xy3aEFhdi4YtjIdYzSc0nomDjltXFUiFhW9/L3INQv9QBoeZkXH6OYJUgPG9/m8KBJItrU0ko 0l6mw2UjWJ9CR0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Y7XeCv1IC2XK8c57kmGZUwKQnw8>
Subject: Re: [xml2rfc] Much repetition of "Paragraph 1" in references
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 20 Mar 2022 11:11:42 -0000

Am 19.03.2022 um 14:03 schrieb Carsten Bormann:
> On 2022-03-19, at 13:49, Roger Price <roger@rogerprice.org> wrote:
>>
>> The anchor is coded as
>>
>> <section>
>> <name>Events</name>
>> <t anchor=3D"events">A bla bla bla ... etc
>>
>> The reference is coded as
>>
>> the events are listed in <xref target=3D"events"></xref>.
>>
>> The HTML displays as
>>
>> the events are listed in Section 5.2, Paragraph 1.
>>
>> Is there some way of eliminating these paragraph references, except whe=
n really needed?
>
> Yes.  If you don=E2=80=99t want to reference the paragraph but the secti=
on, put the anchor on the section and not the paragraph:
>
>>>> <section anchor=3D"events">
>>>> <name>Events</name>
>>>> <t>A bla bla bla =E2=80=A6 etc
>
> Gr=C3=BC=C3=9Fe, Carsten

Note that this is a change fron xml2rfc v2, where only the Section was
mentioned. For long sections, this might be useful, but it IMHO should
be an opt-in (for the format attribute).

Best regards, Julian


From nobody Sun Mar 20 05:26:38 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5283A00E5 for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 05:26:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 R0YtlBquet45 for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 05:26:32 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A5CE3A00DF for <xml2rfc@ietf.org>; Sun, 20 Mar 2022 05:26:31 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KLxnK4NJ2zDCd6; Sun, 20 Mar 2022 13:26:29 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <062af102-4ab0-c08c-ce4d-c69360477108@gmx.de>
Date: Sun, 20 Mar 2022 13:26:29 +0100
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 669471989.192983-7772b445f5cc8395bb0c0caf2f26e13e
Content-Transfer-Encoding: quoted-printable
Message-Id: <80F3EC13-7427-4C39-9927-A53DBE386870@tzi.org>
References: <alpine.DEB.2.20.2203191332410.4718@maria.rogerprice.org> <7B339039-ED9C-4E38-86EE-0E1C1ACA09A5@tzi.org> <062af102-4ab0-c08c-ce4d-c69360477108@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/sL4pRLqhqLnSALfHjJ1RXLmV92k>
Subject: Re: [xml2rfc] Much repetition of "Paragraph 1" in references
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 20 Mar 2022 12:26:37 -0000

On 2022-03-20, at 12:11, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> Note that this is a change fron xml2rfc v2, where only the Section was
> mentioned. For long sections, this might be useful, but it IMHO should
> be an opt-in (for the format attribute).

IMHO that would be a design mistake: The referencing site should not =
have to know what is being referenced =E2=80=94 it is the job of the =
anchor site to provide this information.  (Yes, this principle is =
already being violated, but we should not pile up on this.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sun Mar 20 05:27:45 2022
Return-Path: <roger@rogerprice.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7AF33A0100 for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 05:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 SjEaU8IzSZhf for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 05:27:39 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CED53A00E5 for <xml2rfc@ietf.org>; Sun, 20 Mar 2022 05:27:38 -0700 (PDT)
Received: (Authenticated sender: mailbox@rogerprice.org) by mail.gandi.net (Postfix) with ESMTPSA id 9541440007 for <xml2rfc@ietf.org>; Sun, 20 Mar 2022 12:27:35 +0000 (UTC)
Date: Sun, 20 Mar 2022 13:27:34 +0100 (CET)
From: Roger Price <roger@rogerprice.org>
X-X-Sender: rprice@maria.rogerprice.org
To: xml2rfc Mailing List <xml2rfc@ietf.org>
In-Reply-To: <062af102-4ab0-c08c-ce4d-c69360477108@gmx.de>
Message-ID: <alpine.DEB.2.20.2203201309350.4718@maria.rogerprice.org>
References: <alpine.DEB.2.20.2203191332410.4718@maria.rogerprice.org> <7B339039-ED9C-4E38-86EE-0E1C1ACA09A5@tzi.org> <062af102-4ab0-c08c-ce4d-c69360477108@gmx.de>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-Message-Flag: Supplemental report sent to reaper.nsa.gov. rc=0
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="-636875520-379571239-1647779255=:4718"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/s0agYZSRUfK7Blu7cjWz-j9ubO8>
Subject: Re: [xml2rfc] Much repetition of "Paragraph 1" in references
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 20 Mar 2022 12:27:44 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---636875520-379571239-1647779255=:4718
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Sun, 20 Mar 2022, Julian Reschke wrote:
> Am 19.03.2022 um 14:03 schrieb Carsten Bormann:
>> On 2022-03-19, at 13:49, Roger Price <roger@rogerprice.org> wrote:
>>>
>>> Is there some way of eliminating these paragraph references, except when 
> really needed?
>>
>> Yes.  If you don’t want to reference the paragraph but the section, put the 
> anchor on the section and not the paragraph:
>>
>>>>> <section anchor="events">
>>>>> <name>Events</name>
>>>>> <t>A bla bla bla … etc
>>
>> Grüße, Carsten
>
> Note that this is a change fron xml2rfc v2, where only the Section was
> mentioned. For long sections, this might be useful, but it IMHO should
> be an opt-in (for the format attribute).

I have an HTML rendering of a link as

    See Section 6.4.5, Paragraph 4, Item 1.

which seems to me to be the most precise way of presenting that link. This 
currently happens automatically, without the need for an opt-in.  My "mistake" 
was to put the anchor on the <t> and not the <section>.  Perhaps a note in the 
documentation would be helpful.

Roger
---636875520-379571239-1647779255=:4718--


From nobody Sun Mar 20 06:43:59 2022
Return-Path: <roger@rogerprice.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACD433A0A9C for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 06:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level: 
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 KOMwpXhJOHna for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 06:43:45 -0700 (PDT)
Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B83F3A0A9B for <xml2rfc@ietf.org>; Sun, 20 Mar 2022 06:43:44 -0700 (PDT)
Received: (Authenticated sender: mailbox@rogerprice.org) by mail.gandi.net (Postfix) with ESMTPSA id 5263AE0005 for <xml2rfc@ietf.org>; Sun, 20 Mar 2022 13:43:40 +0000 (UTC)
Date: Sun, 20 Mar 2022 14:43:39 +0100 (CET)
From: Roger Price <roger@rogerprice.org>
X-X-Sender: rprice@maria.rogerprice.org
To: xml2rfc Mailing List <xml2rfc@ietf.org>
Message-ID: <alpine.DEB.2.20.2203201406300.4718@maria.rogerprice.org>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-Message-Flag: Supplemental report sent to reaper.nsa.gov. rc=0
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/_Zhm2jQ65WmheT5Y-9X5uSWdbi0>
Subject: [xml2rfc] Does anyone else mark up in SGML?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 20 Mar 2022 13:43:48 -0000

I rewrote the xml2rfc DTD as an SGML DTD which allows markup minimisation.  I 
also changed some element names to something closer to HTML, so I write:

<s3><h3>Long Term</h3>
<p anchor="LongTerm">In the long term, ...

and program osgmlnorm (the one parser that can never be wrong) renders this as:

<section>
<name>Long Term</name>
<t anchor="LongTerm">In the long term, ...

The main advantages are much markup minimisation such as the elimination of all 
</section>, </t> and </li>, and the freedom to choose element names I can 
remember.

Does anyone else use SGML to prepare I-Ds?  I am interested in sharing 
experience, but I do not wish to encourage people to use SGML if they are not 
already familiar with it.

Roger


From nobody Sun Mar 20 07:34:58 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A77753A0C35 for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 07:34:56 -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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 e7oprgKeycvA for <xml2rfc@ietfa.amsl.com>; Sun, 20 Mar 2022 07:34:52 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D255A3A0C26 for <xml2rfc@ietf.org>; Sun, 20 Mar 2022 07:34:51 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KM0dN1RLVzDCcT; Sun, 20 Mar 2022 15:34:48 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.DEB.2.20.2203201406300.4718@maria.rogerprice.org>
Date: Sun, 20 Mar 2022 15:34:47 +0100
Cc: xml2rfc Mailing List <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 669479687.752861-01e9fcdf7f5d4563971e660690ec1b83
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C6F07D3-AE8D-4D71-8747-C6B65BA08918@tzi.org>
References: <alpine.DEB.2.20.2203201406300.4718@maria.rogerprice.org>
To: Roger Price <roger@rogerprice.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/AJBxvnvtMuiBu96LurSAs6k-PPs>
Subject: Re: [xml2rfc] Does anyone else mark up in SGML?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 20 Mar 2022 14:34:57 -0000

On 2022-03-20, at 14:43, Roger Price <roger@rogerprice.org> wrote:
>=20
> Does anyone else use SGML to prepare I-Ds?  I am interested in sharing =
experience, but I do not wish to encourage people to use SGML if they =
are not already familiar with it.

The most popular authoring language for I-Ds (apart from RFCXML itself) =
is markdown.

For someone who has been using (and working on) SGML since the =
mid-1980s, supporting this evolution may be a bit surprising (at least =
my 1980s-self would say that).  In the 2000s, I switched to ASCIIDOC =
first, and had a few quite successful projects on that basis.  But in =
the end, ease of collaboration wins, and markdown is the leader in this =
space.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar 23 05:59:16 2022
Return-Path: <roger@rogerprice.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F79F3A10F4 for <xml2rfc@ietfa.amsl.com>; Wed, 23 Mar 2022 05:59:13 -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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 u5tDJ16jg_Ld for <xml2rfc@ietfa.amsl.com>; Wed, 23 Mar 2022 05:59:08 -0700 (PDT)
Received: from relay10.mail.gandi.net (relay10.mail.gandi.net [217.70.178.230]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4B4A3A0D34 for <xml2rfc@ietf.org>; Wed, 23 Mar 2022 05:59:07 -0700 (PDT)
Received: (Authenticated sender: mailbox@rogerprice.org) by mail.gandi.net (Postfix) with ESMTPSA id 2B5D5240009 for <xml2rfc@ietf.org>; Wed, 23 Mar 2022 12:59:03 +0000 (UTC)
Date: Wed, 23 Mar 2022 13:59:02 +0100 (CET)
From: Roger Price <roger@rogerprice.org>
X-X-Sender: rprice@maria.rogerprice.org
To: xml2rfc Mailing List <xml2rfc@ietf.org>
Message-ID: <alpine.DEB.2.20.2203231352110.4718@maria.rogerprice.org>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-Message-Flag: Supplemental report sent to reaper.nsa.gov. rc=0
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/S7zJiNu36fJKD7rQTvRahsDOppM>
Subject: [xml2rfc] Markup of ABNF
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 23 Mar 2022 12:59:14 -0000

Is there a "correct" way of marking up Augmented BNF in XML, as in RFC5234 
section 4? Any example would be much appreciated.

Roger

RFC5234: https://www.rfc-editor.org/rfc/rfc5234.html


From nobody Wed Mar 23 06:27:16 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB893A133A for <xml2rfc@ietfa.amsl.com>; Wed, 23 Mar 2022 06:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 NCoOsiMGynyC for <xml2rfc@ietfa.amsl.com>; Wed, 23 Mar 2022 06:27:07 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AFC63A1275 for <xml2rfc@ietf.org>; Wed, 23 Mar 2022 06:27:07 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KNpzq1hJVzDCbq; Wed, 23 Mar 2022 14:27:03 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.DEB.2.20.2203231352110.4718@maria.rogerprice.org>
Date: Wed, 23 Mar 2022 14:27:02 +0100
Cc: xml2rfc Mailing List <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 669734822.814811-fa98b59ec4f39f9365790e89cd5e9795
Content-Transfer-Encoding: quoted-printable
Message-Id: <7CDB864B-DD17-4DD7-88E2-B1AC7783941A@tzi.org>
References: <alpine.DEB.2.20.2203231352110.4718@maria.rogerprice.org>
To: Roger Price <roger@rogerprice.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/FAlj-NvzUGqO-xOUtWDcqbjkrgc>
Subject: Re: [xml2rfc] Markup of ABNF
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 23 Mar 2022 13:27:13 -0000

On 2022-03-23, at 13:59, Roger Price <roger@rogerprice.org> wrote:
>=20
> Is there a "correct" way of marking up Augmented BNF in XML, as in =
RFC5234 section 4? Any example would be much appreciated.

There are probably multiple ways that are all correct.

=46rom a recent draft:

~~~~ abnf
time-zone-initial =3D ALPHA / "." / =E2=80=9C_=E2=80=9D
; ...
alphanum          =3D ALPHA / DIGIT
~~~~
{: #grammar title=3D"ABNF grammar of extensions to RFC 3339"}

Or in RFCXMLv3:

        <figure anchor=3D"grammar">
          <name>ABNF grammar of extensions to RFC 3339</name>
          <sourcecode type=3D"abnf"><![CDATA[
time-zone-initial =3D ALPHA / "." / =E2=80=9C_=E2=80=9D
; ...
alphanum          =3D ALPHA / DIGIT
]]></sourcecode>
        </figure>

Note that you can use =C2=BBname=3D"foo.abnf"=C2=AB on <sourcecode to =
collect several ABNF snippets into one entity (=E2=80=9Cfile=E2=80=9D) =
named foo.abnf.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar 23 06:28:10 2022
Return-Path: <rjsparks@nostrum.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087073A133A for <xml2rfc@ietfa.amsl.com>; Wed, 23 Mar 2022 06:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level: 
X-Spam-Status: No, score=-2.089 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 du5hAgkUSEXl for <xml2rfc@ietfa.amsl.com>; Wed, 23 Mar 2022 06:27:58 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78F1F3A1287 for <xml2rfc@ietf.org>; Wed, 23 Mar 2022 06:27:31 -0700 (PDT)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 22NDRTdx004139 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <xml2rfc@ietf.org>; Wed, 23 Mar 2022 08:27:29 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1648042049; bh=UhmXI6eIQM79xGb2xZkCUcnno4lZuAHIRovIMrpIsYM=; h=Date:Subject:To:References:From:In-Reply-To; b=dD2TgsjA39+z3w4sJ3bHSJ2+BGMot6u/JMBCbEH8gqto+U32ksWw2XZm0i/X+527K YUZFqzqWfV33W2ZgGBvXepXvyw6GTr3vCjdjXjXbOFlu38jAE9UMTMhsxhWqXnIDf+ aLYAI+V5R91rirKzDJT0ok4joj2U3FqjYylO21L8=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <3a0ec49e-6676-1c7b-2213-d5cd38be1b06@nostrum.com>
Date: Wed, 23 Mar 2022 08:27:23 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: xml2rfc@ietf.org
References: <alpine.DEB.2.20.2203231352110.4718@maria.rogerprice.org>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <alpine.DEB.2.20.2203231352110.4718@maria.rogerprice.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/4_OCHMS_i0C9A8oraTy8lZqxqOc>
Subject: Re: [xml2rfc] Markup of ABNF
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 23 Mar 2022 13:28:10 -0000

An example of how it was done in RFC9171 
(https://www.rfc-editor.org/rfc/rfc9171.xml)

```

<sourcecode type="abnf" markers="false" pn="section-4.2.5.1.1-3">
dtn-uri = "dtn:" ("none" / dtn-hier-part)

dtn-hier-part = "//" node-name name-delim demux ; a path-rootless

node-name = reg-name

name-delim = "/"

demux = *VCHAR
</sourcecode>

```

hth,

RjS

On 3/23/22 7:59 AM, Roger Price wrote:
> Is there a "correct" way of marking up Augmented BNF in XML, as in 
> RFC5234 section 4? Any example would be much appreciated.
>
> Roger
>
> RFC5234: https://www.rfc-editor.org/rfc/rfc5234.html
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc


From nobody Wed Mar 23 07:59:16 2022
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BD983A150F for <xml2rfc@ietfa.amsl.com>; Wed, 23 Mar 2022 07:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 HTA5u9xHDIxg for <xml2rfc@ietfa.amsl.com>; Wed, 23 Mar 2022 07:59:09 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A8273A1455 for <xml2rfc@ietf.org>; Wed, 23 Mar 2022 07:59:09 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KNs225mbvzDCbP; Wed, 23 Mar 2022 15:59:06 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <3a0ec49e-6676-1c7b-2213-d5cd38be1b06@nostrum.com>
Date: Wed, 23 Mar 2022 15:59:06 +0100
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 669740346.3898931-bfec56bb0973d30c7f14422b3b81fd01
Content-Transfer-Encoding: quoted-printable
Message-Id: <0578DD4E-A769-4954-B2EA-D29692483DB0@tzi.org>
References: <alpine.DEB.2.20.2203231352110.4718@maria.rogerprice.org> <3a0ec49e-6676-1c7b-2213-d5cd38be1b06@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/KUfMjDJmkkgGoYNT-D8uWm1mnWE>
Subject: Re: [xml2rfc] Markup of ABNF
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 23 Mar 2022 14:59:14 -0000

On 2022-03-23, at 14:27, Robert Sparks <rjsparks@nostrum.com> wrote:
>=20
> <sourcecode type=3D"abnf" markers=3D"false" pn=3D"section-4.2.5.1.1-3">

=E2=80=A6 but that is published form, which authors would never supply.

The net content of that example is:

> <sourcecode type=3D"abnf">


The 9171 example is unmarked (no figure number, no caption), while my =
example was an actual figure.  Both are right for their respective =
applications (9171: part of running text, my example: a figure that is =
referenced by anchor).

Gr=C3=BC=C3=9Fe, Carsten

