[xml2rfc-dev] First draft of the v3-bis document

Paul Hoffman <paul.hoffman@icann.org> Wed, 03 October 2018 02:43 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFE091311D5 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 2 Oct 2018 19:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 QGFQP67fROXz for <xml2rfc-dev@ietfa.amsl.com>; Tue, 2 Oct 2018 19:43:46 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D838F1311C5 for <xml2rfc-dev@ietf.org>; Tue, 2 Oct 2018 19:43:45 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 2 Oct 2018 19:43:43 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Tue, 2 Oct 2018 19:43:43 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
Thread-Topic: First draft of the v3-bis document
Thread-Index: AQHUWsLm4q/QzwVhRUukD8KDuKNtUA==
Date: Wed, 03 Oct 2018 02:43:43 +0000
Message-ID: <19E99A55-1441-4AF1-AB5C-D4E21641BC86@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; boundary="Apple-Mail=_A1ECCFB7-D463-46E7-8395-2D1E5C9B6F7D"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/4V9b8CZUaTuG7eKPJLNzqrenoNc>
Subject: [xml2rfc-dev] First draft of the v3-bis document
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2018 02:43:48 -0000

Greetings. I have published draft-iab-xml2rfc-v3-bis-00 as a starting point for the efforts that you are seeing discussed on this list. See
   https://datatracker.ietf.org/doc/draft-iab-xml2rfc-v3-bis/

The -00 is very close to exactly RFC 7791 except that it doesn't say that it obsoletes the v2 RFC because RFC 7791 already does that.

I'll try to issue the -01 in a few weeks once we have a handful of issues that have been brought to the list and have resolution. I'll keep doing that on maybe a bi-weekly basis.

--Paul Hoffman