Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-interest and the IAB
Ronald Tse <tse@ribose.com> Tue, 03 March 2020 05:22 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4653A1889 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Mon, 2 Mar 2020 21:22:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ribose.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 AjYaOhIGCwnj for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Mon, 2 Mar 2020 21:21:56 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C91283A1883 for <rfc-interest-archive-SieQuei0be@ietf.org>; Mon, 2 Mar 2020 21:21:56 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 771BFF4071E; Mon, 2 Mar 2020 21:21:36 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 04F1FF4071E for <rfc-interest@rfc-editor.org>; Mon, 2 Mar 2020 21:21:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ribose.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TzvrQJNPSFfG for <rfc-interest@rfc-editor.org>; Mon, 2 Mar 2020 21:21:31 -0800 (PST)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-eopbgr1310080.outbound.protection.outlook.com [40.107.131.80]) by rfc-editor.org (Postfix) with ESMTPS id 3DC1BF4071C for <rfc-interest@rfc-editor.org>; Mon, 2 Mar 2020 21:21:29 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IYWRrYeHnjxCKmvIc47N276CXn8sgPhapil9Oq0DosT7wTWulHcI0sIJUOSpvP1EtDxfy6TXRozF80szofch68JPDqjizHS2tBY+NmY8Pkc91cAEqZtZQxoiJXVWfzegxJXJY4jzYgZ0NRCDbOZ62dF+P2UeVOxB6qK27lZ5W+r3zThsQYI/AxoMebRCnHSC+4XuvqG5J9YbYC2DUOsvlFaBdFTijEQrPLkI4vuqXAq/hLx0PoZvrGUDoffBBW+Nvpwa2CQbIyCJuu1t3D3syf8v+hk42Fau4raangDJFy/heM5z8+yKZF9h2rtq0Sr5LwliYC0yy7qEPr97bhef4A==
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-SenderADCheck;bh=zcoB7TM9mAE/4vC4dIVB707qP8KseWqcx9xKP4UrJV0=; b=dKLQ15+lmjNE1xfTcnc8cgwVk9Eg9rpApHo9jXcgMOFKrP2NBCL3aXyJULcTKhpdTrJrxBL03KMlk8vLTEkX1W6/Eg1r+zNabxldUcr3rm+CFUtQkywUQZNQR+EopfNn8Yo7CGTZnlndfZ2XF76+9ifEMS8XaHOY80/PzV2/qSOD2dzxdmkXcYOUXnWHZPDHDGRQ2KKh0PMIZqgB5XI3WIx7sFliiLjotuTJ8sBPRisaGI+QHOANgrJCpZsXvKrNk/jYXqFjReGVM9dlqhfN1ZMNnsjnyV/S4AgNhDKUbN+NIlEstgGtu4yLmDW9V9kbdRiNdogvSlS/FViV3/M/tw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ribose.com; dmarc=pass action=none header.from=ribose.com; dkim=pass header.d=ribose.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ribose.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=zcoB7TM9mAE/4vC4dIVB707qP8KseWqcx9xKP4UrJV0=; b=r+BrbNpugYKPRaCqznlGiyneP4XXAz0fZb/dRqTV3UxE6KoRGLUV9BvXKsIXAJyRFIND6lCVO5Yu/FbF7/0B+D/lUSeGk5ATk+lYpdTQss8egUJtLMtdVltbtKN/eq7xx/Kl5WP6KHudrBpMsT1AGsoICp7bUv5MoD71MzrEMaA=
Received: from HK0PR01MB2770.apcprd01.prod.exchangelabs.com (20.177.167.212) by HK0PR01MB2419.apcprd01.prod.exchangelabs.com (20.177.70.204) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.15; Tue, 3 Mar 2020 05:21:43 +0000
Received: from HK0PR01MB2770.apcprd01.prod.exchangelabs.com ([fe80::178:964c:732a:502f]) by HK0PR01MB2770.apcprd01.prod.exchangelabs.com ([fe80::178:964c:732a:502f%7]) with mapi id 15.20.2772.019; Tue, 3 Mar 2020 05:21:37 +0000
From: Ronald Tse <tse@ribose.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Thread-Topic: [rfc-i] [IAB] [Rsoc] Archival format to rfc-interest and the IAB
Thread-Index: AQHV8L80NzSf/1vlnUaSeu0qJRW/YKg1vn2AgACXPAA=
Date: Tue, 03 Mar 2020 05:21:36 +0000
Message-ID: <70076BD7-5315-4B6E-8477-1028F228904F@ribose.com>
References: <57ce444e-4ee9-26c5-9e76-ae6906e69159@gmail.com> <52BA75DF-6D58-4BF1-953F-1911F301DB20@encrypted.net> <8f3e62b9-03ff-9fc2-bef9-a341ce7ca897@gmail.com> <CA+9kkMBm7dH05mks2mREWO+n4A+f_m=MBC6pEicp=VVrmg6VKA@mail.gmail.com> <4e426227-a7b6-b4d0-8333-aa92d679f03b@mozilla.com> <1d6af0d5-a2c2-b239-43fd-7c937f06ccb2@gmail.com> <alpine.OSX.2.22.407.2002210838240.88568@ary.local> <165f02c8-3573-9454-ed98-efd7d3764d0f@gmx.de> <CANk3-NBv3Y+-G8VSt-M=NgShfjbvz+gsQTPtKUAsr3hBarW7Hg@mail.gmail.com> <10ea86bd-053c-37d3-2966-21a8187748d5@levkowetz.com>
In-Reply-To: <10ea86bd-053c-37d3-2966-21a8187748d5@levkowetz.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=tse@ribose.com;
x-originating-ip: [58.153.245.161]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 685621e1-787a-40aa-41af-08d7bf32bf03
x-ms-traffictypediagnostic: HK0PR01MB2419:
x-microsoft-antispam-prvs: <HK0PR01MB241988AD691BF11C5DE17581D7E40@HK0PR01MB2419.apcprd01.prod.exchangelabs.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 03319F6FEF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39830400003)(396003)(346002)(376002)(136003)(366004)(199004)(189003)(64756008)(5660300002)(6506007)(186003)(966005)(53546011)(71200400001)(86362001)(36756003)(2906002)(6512007)(66946007)(76116006)(8936002)(4326008)(508600001)(6486002)(26005)(66556008)(66446008)(33656002)(2616005)(66476007)(54906003)(91956017)(6916009)(316002)(81156014)(8676002)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:HK0PR01MB2419; H:HK0PR01MB2770.apcprd01.prod.exchangelabs.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ribose.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TSh1CRKy9Td//2ynWlxIUd13xuIP+gc5rQr4newwTQbG5qglA2B0GVZNs1Q/gOJrdV8qudnaHcFUAD9P4BVb1YnBONrzmeEyf9CvaQFpKg5sIyMUxv0lvQiPLpLJf/fpjqIcrj1JClvSITBW0q/tXENRwSUvTshaYNYfBhjn1/LRIl75qCk1zQ7tYUmJiG6c4ALTYKpwjbzqY78GOtMJnEqd1dHMB1zg2Yyg4Q3MOb+fmUZ83EDwMWXZKKSt+zHIw2jRywjg+ncNJVaipBVivbiIQzFGv+91pVFIBeHumrrCPBQy2K+lwq1CQZtFHGVXdA2UeUmGGFPN3Fqw2A388i/26gMTnX5wqx44Nfa6eFBFaji+bJJmUmYkO21DvQhPEWU4J00zAco1BMUMNcvjgEynGo71k7tBgAghdlJyNeZehJOrzqtyeJK8TkKA0HPatSpDD9cK7JJQjCKsEPCfEAlQrLug6ZTOHCvAmtkyTD3wTVsm+bKhcHs1idAFx/t3rjWeghKsk3/Xttuj3E5Piw==
x-ms-exchange-antispam-messagedata: 4flxzyPFZYxlENKz7TfFaNSbhh3T/ZzYCw7KQMsccVJC3FdfsIAcSXcxX5ZgCnwR+Ot6FbR28OBUeLe4+jxT9FJKH6xvtkiYR+OyHP5BDS61YrtQjEOUs+RQ5arfA6U/UgZQVfuBeyW3xJ+8+E/zxQ==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: ribose.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 685621e1-787a-40aa-41af-08d7bf32bf03
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Mar 2020 05:21:36.8637 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d98a04ff-ef98-489b-b33c-13c23a2e091a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: +on3wFAHvhsbD66c8wsTGBBlRX4CXd3HMnK0X0tzMaPDjt/rbELTbHHkJpa984c6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK0PR01MB2419
Subject: Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-interest and the IAB
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: Julian Reschke <julian.reschke@gmx.de>, RFC Interest <rfc-interest@rfc-editor.org>, RSOC <rsoc@iab.org>, "John R. Levine" <johnl@iecc.com>, Wes Hardaker <hardaker@isi.edu>, Internet Architecture Board <iab@iab.org>
Content-Type: multipart/mixed; boundary="===============6336037330450453734=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
I have been tracking this list since we first implemented AsciiRFC for RFC XML v2, the draft v3, and now the “official" v3. (As we speak, the "draft-ribose-asciirfc” document has already been stuck in AUTH for over 2 years). To be fair, I concur with many of Julian’s comments and they are true concerns, especially since we’re dealing with “standardized documents” that need to be interoperable by different tools. The draft v3 and the current v3 are sufficiently incompatible that we consider them as different implementations — files that comply with draft v3 grammar crashes today's official toolset. I understand the frustration. But as Julian has mentioned a couple times, there are practices and assumptions in the existing toolset that are not documented in spec. This is more likely the cause for stagnated progress. Kind regards, Ron _____________________________________ Ronald Tse Ribose Inc. On Mar 3, 2020, at 4:20 AM, Henrik Levkowetz <henrik@levkowetz.com<mailto:henrik@levkowetz.com>> wrote: Given the number of lists copied here, I'd like to make just one observation, in reply to Julian's assertion, so that people who haven't been following the discussions on the xml2rfc-dev list in the last half of 2018 have a bit more data to work with: On 2020-03-02 19:19, Wes Hardaker wrote: FWIW, the fact that *you* do not know the answer is kind of scary. I expect that one of the things to come out of the upcoming discussions for the future of the RSE roll will be where decisions are formally held and what the right level of independence is with respect to the RSE role. It's now something like 9 months since I tried to draw attention to the current mess, and there seems absolutely no measurable progress on this issue since At this point, people should be aware that the reason we haven't made progress in determining a revised specification is that when I started to feed back issues to the discussion list, Julian was sufficiently obstructionist in his responses to many proposed adjustments that there was absolutely no hope of both having that extended conversation and at the same time producing a tool release that would let the RPC carry out their planned transition. I deplore the situation we have, but the primary reason we are in this situation is that sensible discussion and progress in resolving proposed changes was killed by an Not-Invented-Here attitude from the v3 design team members active on the discussion list in the autumn of 2018, with Julian the most active in preventing any progress at all from taking place on some issues. Henrik _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org<mailto:rfc-interest@rfc-editor.org> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
_______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Archival format to rfc-interest and the I… Sarah Banks
- Re: [rfc-i] Archival format to rfc-interest and t… Andrew G. Malis
- Re: [rfc-i] [Rsoc] Archival format to rfc-interes… John R. Levine
- Re: [rfc-i] Archival format to rfc-interest and t… Brian E Carpenter
- Re: [rfc-i] Archival format to rfc-interest and t… Sarah Banks
- Re: [rfc-i] Archival format to rfc-interest and t… Brian E Carpenter
- Re: [rfc-i] Archival format to rfc-interest and t… Ted Hardie
- Re: [rfc-i] Archival format to rfc-interest and t… Peter Saint-Andre
- Re: [rfc-i] Archival format to rfc-interest and t… Brian E Carpenter
- Re: [rfc-i] [Rsoc] Archival format to rfc-interes… John R. Levine
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… Wes Hardaker
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… Julian Reschke
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… John R. Levine
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… Julian Reschke
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… John R. Levine
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… Henrik Levkowetz
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… Julian Reschke
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… Ronald Tse
- Re: [rfc-i] [IAB] [Rsoc] Archival format to rfc-i… Carsten Bormann
- [rfc-i] [Rsoc] Archival format to rfc-interest an… Julian Reschke