Re: [xml2rfc] sourcecode type for config files
Carsten Bormann <cabo@tzi.org> Wed, 26 July 2023 20:55 UTC
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 593E4C151065 for <xml2rfc@ietfa.amsl.com>; Wed, 26 Jul 2023 13:55:29 -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_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JdlJeXUuM7B for <xml2rfc@ietfa.amsl.com>; Wed, 26 Jul 2023 13:55:26 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E273C14CE5F for <xml2rfc@ietf.org>; Wed, 26 Jul 2023 13:55:25 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RB5kz62bLzDCbn; Wed, 26 Jul 2023 22:55:23 +0200 (CEST)
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: <48ee015e-b8c4-a492-6de8-c73170c62d5e@htt-consult.com>
Date: Wed, 26 Jul 2023 22:55:23 +0200
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 712097723.521939-d74aa77ff3ed75a7d6489da6d73f8984
Content-Transfer-Encoding: quoted-printable
Message-Id: <395A5D32-5D33-42C6-BB68-EA647DB88286@tzi.org>
References: <48ee015e-b8c4-a492-6de8-c73170c62d5e@htt-consult.com>
To: Robert Moskowitz <rgm@htt-consult.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/d4npJNqNGIXDlmjm_OVVcahdojU>
Subject: Re: [xml2rfc] sourcecode type for config files
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2023 20:55:29 -0000
On 2023-07-26, at 22:06, Robert Moskowitz <rgm@htt-consult.com> wrote: > > What is "recommended" type to use for conf files? "Configuration file” is a term for what you *use them for*, not what they *are*. They could be xml, yaml, even json, or some bespoke format (.ini anyone? OK, we now have toml.) What are they in your case? Grüße, Carsten
- [xml2rfc] sourcecode type for config files Robert Moskowitz
- Re: [xml2rfc] sourcecode type for config files Carsten Bormann
- Re: [xml2rfc] sourcecode type for config files Robert Moskowitz
- Re: [xml2rfc] sourcecode type for config files Randy Bush
- Re: [xml2rfc] sourcecode type for config files Carsten Bormann