Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml
Megan Ferguson <mferguson@amsl.com> Fri, 16 June 2017 16:54 UTC
Return-Path: <mferguson@amsl.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C8F7129463 for <tools-development@ietfa.amsl.com>; Fri, 16 Jun 2017 09:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 mZFPa0sBe0cz for <tools-development@ietfa.amsl.com>; Fri, 16 Jun 2017 09:54:28 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C56671200ED for <tools-development@ietf.org>; Fri, 16 Jun 2017 09:54:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4250D1CA389; Fri, 16 Jun 2017 09:54:16 -0700 (PDT)
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 5uhjPEiksTEI; Fri, 16 Jun 2017 09:54:16 -0700 (PDT)
Received: from [10.0.1.11] (cpe-76-168-191-223.socal.res.rr.com [76.168.191.223]) by c8a.amsl.com (Postfix) with ESMTPA id 0998B1CA387; Fri, 16 Jun 2017 09:54:16 -0700 (PDT)
From: Megan Ferguson <mferguson@amsl.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 16 Jun 2017 09:54:33 -0700
Message-Id: <A31CAA04-572A-411C-8BA1-4020273DC3D4@amsl.com>
Cc: tools-development@ietf.org
To: henrik@levkowetz.com
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/qcBoVZypV4ZCszHnCpUL6H-_7uI>
Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jun 2017 16:54:32 -0000
Hi Henrik, Revisiting this file using the new release (v1.0.1): >> Input file: draft-ietf-trill-directory-assist-mechanisms-12 >> Version: id2xml 1.0.0 >> Issues: File not originally generated with XML >> Files available: >> https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-mechanisms-12v3.original >> https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-mechanisms-12v3.txt >> https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-mechanisms-12v3-rfcdiff.html Note - we edited the file somewhat to combat the previously discussed issues. 1) There were a few reference oddities and follow-up questions: a) The following are the work in progress (WiP) references that could not parse. draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2237): Warning: Failed parsing a reference: [rfc6439bis] - D. Eastlake, Y. Li, M. Umair, A. Banerjee, and F. Hu, "Routing Bridges (RBridges): Appointed Forwarders", draft-ietf- trill-rfc6439bis, Work in Progress. draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2252): Warning: Failed parsing a reference: [ARPND] - Y. Li, D. Eastlake, L. Dunbar, R. Perlman, I. Gashinsky, "TRILL: ARP/ND Optimization", draft-ietf-trill-arp- optimization, Work in Progress. draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2256): Warning: Failed parsing a reference: [DirAsstEncap] L. Dunbar, D. Eastlake, R. Perlman, I. Gashingksy, "Directory Assisted TRILL Encapsulation", draft-ietf-trill- directory-assisted-encap, Work in Progress. draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2260): Warning: Failed parsing a reference: [SmartEN] R. Perlman, F. Hu, D. Eastlake, K. Krupakaran, T. Liao, "TRILL Smart Endnodes", draft-ietf-trill-smart-endnodes", draft-ietf-trill-smart-endnodes, Work in Progress. Some questions/notes: The general format for WiP references should be: [I-D.ietf-sidr-bgpsec-protocol] Lepinski, M. and K. Sriram, "BGPsec Protocol Specification", draft-ietf-sidr-bgpsec-protocol-20 (work in progress), December 2016. So we see that the first 4 references in the list above: - are missing the date - have the draft string before the Work in Progress designation - have draft strings that break across lines We are curious which, or if all, of these things make parsing fail and the empty reference to be included? b) With regard to this reference warning: draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2264): Warning: Failed parsing a reference: [X.233] - ITU-T Recommendation X.233: Protocol for providing the connectionless-mode network service: Protocol specification, International Telecommunications Union, August 1997 It seems that the colon instead of a comma is to blame. Once updated, this parsed fine. c) It seems using a 3-digit RFC number is not handled well. In the xml2rfc text output from the id2xml xml file, we see: [RFC826] - Plummer, D., "An Ethernet Address Resolution Protocol", RFC 826, November 1982. [RFC903] - Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A Reverse Address Resolution Protocol", STD 38, RFC 903, June 1984. The XML file contains: <!ENTITY RFC0826 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.0826.xml"> <!ENTITY RFC0903 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.0903.xml”> and it also contains: <reference anchor="RFC826"><front> <title>An Ethernet Address Resolution Protocol</title> <author fullname="D. - Plummer" initials="D." surname="- Plummer"> </author> <date month="November" year="1982"/> </front> <seriesInfo name="RFC" value="826"/> </reference> <reference anchor="RFC903"><front> <title>A Reverse Address Resolution Protocol</title> <author fullname="R. - Finlayson" initials="R." surname="- Finlayson"> </author> <author fullname="T. Mann" initials="T." surname="Mann"> </author> <author fullname="J. Mogul" initials="J." surname="Mogul"> </author> <author fullname="M. Theimer" initials="M." surname="Theimer"> </author> <date month="June" year="1984"/> </front> <seriesInfo name="STD" value="38"/> <seriesInfo name="RFC" value="903"/> </reference> 2) List output variances. There are several areas where the lists in this document did not translate well. Original: The nature of dynamic distributed asynchronous systems is such that it is impossible for a TRILL switch receiving Push Directory information to be absolutely certain that it has complete information. However, it can obtain a reasonable assurance of complete information by requiring two conditions to be met: 1. The PDSS field is 3 in the ESADI zero fragment from the server for the relevant Data Label. 2. In so far as it can tell, it has had continuous data connectivity to the server for a configurable amount of time that defaults to twice the server's CSNP time (PushDirTimer, see Section 2.7). Condition 2 is necessary because a client TRILL switch might be just coming up and receive an EASDI LSP meeting the requirement in condition 1 above but has not yet received all of the ESADI LSP fragments from the Push Directory server. id2xml output: The nature of dynamic distributed asynchronous systems is such that it is impossible for a TRILL switch receiving Push Directory information to be absolutely certain that it has complete information. However, it can obtain a reasonable assurance of complete information by requiring two conditions to be met: 1. The PDSS field is 3 in the ESADI zero fragment from the server for the relevant Data Label. 1. In so far as it can tell, it has had continuous data connectivity to the server for a configurable amount of time that defaults to twice the server's CSNP time (PushDirTimer, see Section 2.7). Condition 2 is necessary because a client TRILL switch might be just coming up and receive an EASDI LSP meeting the requirement in condition 1 above but has not yet received all of the ESADI LSP fragments from the Push Directory server. Original: Query Address: The query is asking for any other addresses, and the nickname of the TRILL switch from which they are reachable, that correspond to the same interface as this address, within the Data Label of the query of the address provided. A typically Query Address would be something like the following: (1) A 48-bit MAC address with the querying TRILL switch primarily interested in either (1a) the RBridge by which that MAC address is reachable so that the querying RBridge can forward an unknown (before the query) destination MAC address native frame as a unicast TRILL Data packet rather than flooding it, or (1b) the IP address corresponding to the MAC address so that RBridge can locally respond to a RARP [RFC903] native frame. (2) An IPv4 or IPv6 address with the querying RBridge interested in the corresponding MAC address so it can locally respond to an ARP [RFC826] or ND [RFC4861] native frame [ARPND]. But the query address could be some other address type for which an AFN has been assigned, such as a 64-bit MAC address [RFC7042] or a CLNS address [X.233]. id2xml output: Query Address: The query is asking for any other addresses, and the nickname of the TRILL switch from which they are reachable, that correspond to the same interface as this address, within the Data Label of the query of the address provided. A typically Query Address would be something like the following: (1) A 48-bit MAC address with the querying TRILL switch primarily interested in either (1a) the RBridge by which that MAC address is reachable so that the querying RBridge can forward an unknown (before the query) destination MAC address native frame as a unicast TRILL Data packet rather than flooding it, or (1b) the IP address corresponding to the MAC address so that RBridge can locally respond to a RARP [RFC903] native frame. (2) An IPv4 or IPv6 address with the querying RBridge interested in the corresponding MAC address so it can locally respond to an ARP [RFC826] or ND [RFC4861] native frame [ARPND]. But the query address could be some other address type for which an AFN has been assigned, such as a 64-bit MAC address [RFC7042] or a CLNS address [X.233]. Original: There are a wide variety of strategies that a TRILL switch can adopt for making use of directory assistance. A few suggestions are given below. - Even if a TRILL switch will normally be operating with information from a complete Push Directory server, there will be a period of time when it first comes up before the information it holds is complete. Or, it could be that the only Push Directories that can push information to it are incomplete or that they are just starting and may not yet have pushed the entire directory. D. Eastlake, et al [Page 41] INTERNET-DRAFT TRILL: Directory Service Mechanisms Thus, it is RECOMMENDED that all TRILL switches have a strategy for dealing with the situation where they do not have complete directory information. Examples are to send a Pull Directory query or to revert to [RFC6325] behavior. - If a TRILL switch receives a native frame X resulting in seeking directory information, a choice needs to be made as to what to do if it does not already have the directory information it needs. In particular, it could (1) immediately flood the TRILL Data packet resulting from ingressing X in parallel with seeking the directory information, (2) flood that TRILL Data packet after a delay, if it fails to obtain the directory information, or (3) discard X if it fails to obtain the information. The choice might depend on the priority of frame X since the higher that priority typically the more urgent the frame is and the greater the probability of harm in delaying it. If a Pull Directory request is sent, it is RECOMMENDED that its priority be derived from the priority of the frame X with the derived priority configurable and having the following defaults: id2xml output: There are a wide variety of strategies that a TRILL switch can adopt for making use of directory assistance. A few suggestions are given below. - Even if a TRILL switch will normally be operating with - - - - - Thus, it is RECOMMENDED that all TRILL switches have a strategy for dealing with the situation where they do not have complete Eastlake, et al. Expires September 3, 2017 [Page 41] Internet-Draft TRILL: Edge Directory Assist Mechanisms March 2017 directory information. Examples are to send a Pull Directory query or to revert to [RFC6325] behavior. - If a TRILL switch receives a native frame X resulting in - - - - - - - - - - - - - 3) Figure/table output Original: The 4-bit Flags field of the message header for an Update Message is as follows: +---+---+---+---+ | F | P | N | R | +---+---+---+---+ id2xml output: The 4-bit Flags field of the message header for an Update Message is as follows: +---+---+---+---+ | F | P | N | R | +---+---+---+---+ +---+---+---+---+ Original: Name Default Section Note Below ------------------ ------- ------- ---------- DirQueryTimeout 100 milliseconds 3.2.1 1 DirQueryRetries 3 3.2.1 1 DirGenQPriority 5 3.2.1 2 DirRespMaxPriority 6 3.2.2.1 3 DirUpdateDelay 50 milliseconds 3.3 DirUpdatePriority 5 3.3.1 DirUpdateTimeout 100 milliseconds 3.3.3 DirUpdateRetries 3 3.3.3 DirAckMaxPriority 5 3.3.2 4 Note 1: Pull Directory Query client timeout waiting for response and maximum number of retries id2xml output: Name Default Section Note Below ------------------ ------- ------- ---------- DirQueryTimeout 100 milliseconds 3.2.1 1 DirQueryRetries 3 3.2.1 1 DirGenQPriority 5 3.2.1 2 DirRespMaxPriority 6 3.2.2.1 3 DirUpdateDelay 50 milliseconds 3.3 DirUpdatePriority 5 3.3.1 DirUpdateTimeout 100 milliseconds 3.3.3 DirUpdateRetries 3 3.3.3 DirAckMaxPriority 5 3.3.2 4 Note 1: Pull Directory Query client timeout waiting for response and maximum number of retries 4) Header vs. Authors’ Addresses section Ideally, the Addresses section would show the full organization name. Thank you. RFC Editor/mf
- [TOOLS-DEVELOPMENT] Preview release of Text Submi… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Megan Ferguson
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Julian Reschke
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Sandy Ginoza
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… HANSEN, TONY L
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Julian Reschke
- [TOOLS-DEVELOPMENT] Fwd: Preview release of Text … Megan Ferguson
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Sandy Ginoza
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Fwd: Preview release of T… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Megan Ferguson
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Megan Ferguson
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Megan Ferguson
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Sandy Ginoza
- [TOOLS-DEVELOPMENT] Preview release of Text Submi… Megan Ferguson
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Henrik Levkowetz
- Re: [TOOLS-DEVELOPMENT] Preview release of Text S… Megan Ferguson