From nobody Mon Jun 5 07:55:05 2017 Return-Path: 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 0C83A129AE3 for ; Mon, 5 Jun 2017 07:55:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.719 X-Spam-Level: X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=tMooL7hO; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=UZq2zYQ0 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 ermUChKjsCar for ; Mon, 5 Jun 2017 07:55:01 -0700 (PDT) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D7F81286D6 for ; Mon, 5 Jun 2017 07:55:00 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 04A01208CF for ; Mon, 5 Jun 2017 10:55:00 -0400 (EDT) Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Mon, 05 Jun 2017 10:55:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=IBPCb9LGfXvBQjmfXhcDgWLO85eo6MO6haKJ3bQIQq8=; b=tMooL7hO k6E+l6+nhDHeFGNlCVsHAHSvSpe9gSEneJ/THe/21ZmraMranFZXQ8kNxXBFtVbt 6Z0f+DHoWVzE9uwNkSnj5Y5/n2CrtDLm+0KApzG0V+KC4g/t9eWwnEa2oItEaMMl fwevjCkfBCWRBTA6dR6Q+wf+SzdF6Cm5Xh9pz7dTKwmKakrUKC7wQRhb/UXaWyeg yMH2zvWntt7+7JidnjldRNJVINyVaPvEdREFDNQEGYnibPCFE9Rk6whxHJ9JXT0M hw07pXxyHUaZSUyxbWzNUEs4QrxfsNVluJK2ao/yc7jkbPf4sNoXP/ILaoMY7ZEy ECpLpIthwgERpw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=IBPCb9LGfXvBQjmfXhcDgWLO85eo6 MO6haKJ3bQIQq8=; b=UZq2zYQ04/qZw1YWthKnn0hAXQj9/u0GBa8FliYWxMHLJ t5v1vabXt0CaZ92/YtnnuAw5AWvrCNebeuSVskL/Pd80+C3NKGYv3eNPA7z2xd7l 1bGtxjE0V11nGOUEt9YZIz5MLdqXhD/NK2AdNjl55BtIY2KQxHXlvu5rzXemMSLH B+V4U4j+g/zNUY7CQee89gD38EkU0A9/9uWDsH5AvJJmUNe/LsMAB/PHLJjGmnCt lzATOeZVDU8awnzc2VymEgRdRBfTn7ii7Mgbvc5tK3CRDFXJnuE+dmTzw0mNg3Uh DTL9Rb8jDJ0wrKzhhvSRg+nWBM+LrJeMAtjHJxGPA== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id DA7519E281; Mon, 5 Jun 2017 10:54:59 -0400 (EDT) Message-Id: <1496674499.709690.999199896.6E9A7681@webmail.messagingengine.com> From: Alexey Melnikov To: tools-development@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-48639608 Date: Mon, 05 Jun 2017 15:54:59 +0100 X-Forwarded-Message-Id: <1D276B8B-AD53-4EA8-8F3C-8B67F70EB5E0@nostrum.com> Archived-At: Subject: [TOOLS-DEVELOPMENT] Fwd: Tools Request for Review Team Management Tool X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2017 14:55:03 -0000 Dear Tools team, This is a request from ART ADs to be able to add a free form text to reviewers of Directorates, so that people's expertise can be recorded there. I hope this is not controversial. Thank you, Alexey ----- Original message ----- From: Ben Campbell To: Alexey Melnikov , Adam Roach Subject: Tools Request for Review Team Management Tool Date: Fri, 2 Jun 2017 10:01:52 -0500 HI, On the call today, we mentioned wanting a free-form =E2=80=9Cexpertise=E2= =80=9D field in the review team tool for ART-ART members. Alexey, will you handle that request as tools liaison? Thanks! Ben. From nobody Tue Jun 6 17:17:07 2017 Return-Path: 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 F0C38126DED for ; Tue, 6 Jun 2017 17:17:05 -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 ghwZS7OpfuZH for ; Tue, 6 Jun 2017 17:17:04 -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 D15D6126DD9 for ; Tue, 6 Jun 2017 17:17:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 5E7471CA517; Tue, 6 Jun 2017 17:17:01 -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 aqi5DmlYDLqm; Tue, 6 Jun 2017 17:17:01 -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 272631C6B8C; Tue, 6 Jun 2017 17:17:01 -0700 (PDT) From: Megan Ferguson Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Tue, 6 Jun 2017 17:17:03 -0700 Message-Id: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2017 00:17:06 -0000 Hi Henrik, Input file: draft-ietf-sidr-bgpsec-protocol-23 Version: id2xml 1.0.0 Issues: Figures/Tables and References=20 1) Figures & Tables Note - the related figures triggered a warning as the example that = follows (i.e., Figures 3-7),=20 so perhaps these issues are already known. draft-ietf-sidr-bgpsec-protocol-23test.txt(422): Warning: Unexpected = title: expected 'Table ...=92,=20 found 'Figure 4: Secure_Path format.'. This looks like a texttable that = has been entered as a figure. The generated XML will need adjustment. a) Extra space added in figures. =20 Original text: +-----------------------------------------------+ | Secure_Path Length (2 octets) | +-----------------------------------------------+ | One or More Secure_Path Segments (variable) | +-----------------------------------------------+ Figure 4: Secure_Path format. id2xml text output version: +-----------------------------------------------+ | Secure_Path Length (2 octets) | +-----------------------------------------------+ | One or More Secure_Path Segments (variable) | | | +-----------------------------------------------+ Figure 4: Secure_Path format. b) Perhaps because of the error mentioned, the figure numbers were = changed. This also occurred with Figure 8, which was renumbered as Figure 4, = Figure 9 which=20 became Figure 5, Figure 10 which became Figure 6, and Figure 11 which = became Figure 7. Original: +------------------------------------------------------+ | pCount (1 octet) | +------------------------------------------------------+ | Confed_Segment flag (1 bit) | Unassigned (7 bits) | (Flags) +------------------------------------------------------+ | AS Number (4 octets) | +------------------------------------------------------+ Figure 5: Secure_Path Segment format. id2xml output version: +------------------------------------------------------+ | pCount (1 octet) | +------------------------------------------------------+ | Confed_Segment flag (1 bit) | Unassigned (7 bits) | (Flags) +------------------------------------------------------+ | AS Number (4 octets) | +------------------------------------------------------+ Figure 3: Secure_Path Segment format. An example in the xml created by id2xml:
The AS Number (in Figure 5) is the AS number of the BGP speaker that added this Secure_Path Segment to the BGPsec_Path attribute. (See for more information on populating this = field.) c) We see that the =93Figures=94 that were made into texttables did not = use a title element, but created the following. Additionally, we do not = see any alignment designation for the text (e.g., text). id2xml XML: Figure 3 provides the specification of the format for the BGPsec_Path attribute. Secure_Path = (variable) Sequence of one or two Signature_Blocks (variable) Figure 3: BGPsec_Path attribute format. 2) We note that references to sections and figures within the document = did not use elements consistently. For example: id2xml in xml file: If the update message was received from a peer that is not expected to set pCount=3D0 (see and Section 4.3) then check to ensure that the pCount field in the most-recently added Secure_Path Segment is not equal to zero. (Note: See router configuration guidance related to this in Section 7.2.) With figure mentions not using them at all (at least in this file). 3) A few missed reference entries (creating empty reference elements) = and xref elements in the running text (this issue was previously = reported). The output XML file wouldn't validate because of the errors.=20= ERROR: Unable to validate the XML document: = draft-ietf-sidr-bgpsec-protocol-23test.xml draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2002: Element front = content does not follow the DTD, expecting (title , author+ , date , = area* , workgroup* , keyword* , abstract? , note*), got nothing. draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2006: Element front = content does not follow the DTD, expecting (title , author+ , date , = area* , workgroup* , keyword* , abstract? , note*), got nothing. draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2025: Element front = content does not follow the DTD, expecting (title , author+ , date , = area* , workgroup* , keyword* , abstract? , note*), got nothing. Thanks! Megan= From nobody Wed Jun 7 09:08:30 2017 Return-Path: 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 63D9D1293D9 for ; Wed, 7 Jun 2017 09:08:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 EiL9AamC4YuA for ; Wed, 7 Jun 2017 09:08:25 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F38351293FF for ; Wed, 7 Jun 2017 09:08:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 537EF300483 for ; Wed, 7 Jun 2017 12:08:24 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ivjF1AAx5vY2 for ; Wed, 7 Jun 2017 12:08:23 -0400 (EDT) Received: from [5.5.33.19] (vpn.snozzages.com [204.42.252.17]) by mail.smeinc.net (Postfix) with ESMTPSA id D0E0730023A for ; Wed, 7 Jun 2017 12:08:22 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Message-Id: <570CB681-E34E-478B-986B-7BB677CBA9B2@vigilsec.com> Date: Wed, 7 Jun 2017 12:08:23 -0400 To: IETF Tools Development X-Mailer: Apple Mail (2.3273) Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 13 June 2017 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2017 16:08:28 -0000 Tools Call Agenda -- 13 June 2017 at 1:00 Eastern JOIN WEBEX MEETING https://ietf.webex.com/ietf/j.php?MTID=3Dm440dd848726339c03e605b9956e38bac= Meeting number (access code): 640 103 570 Meeting password: tools JOIN BY PHONE 1-877-668-4493 Call-in toll free number (US/Canada)=20 1-650-479-3208 Call-in toll number (US/Canada) Meeting number (access code): 640 103 570 Meeting password: tools 1. Datatracker Projects - Expected Datatracker Releases -- Robert and Henrik -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan - Volunteer Enhancements -- Submit an I-D directly from GitHub -- Robert -- Improve NomCom feedback tools -- Robert - Migrate to Django 1.11 when it is released -- Henrik 2. Community & Other Projects - Discontinue MonArch email archives -- Robert - IETF Website Makeover -- Greg and Russ 3. RFC Services Projects - RFC Format Contracts -- Heather and Robert -- IDnits -- Publication Formatter -- RFClint -- SVGcheck -- Text Submission -- XMLdiff 4. Server Infrastructure - IESG discussions of DMARC -- Robert and Alexey -- Mailman upgrade -- Impact on Internet-Draft-specific mail aliases - Libraries for HTML of I-Ds -- Henrik 5. Parking Lot - Migrate from Python 2.7 to Python 3 - CDN support for HTML and PDF I-Ds -- Henrik - Migrate from MySQL to PostgreSQL -- Henrik - Improve infrastructure for finding and fetching artifacts -- Robert - Author information for very old I-Ds in the datatracker -- Robert - Replace I-Ds in proceedings with links to archive copy? - Performance improvements and transition to Postgres -- Henrik - VM Architecture for Servers -- Robert - Add view of recent ballots by telechat - Allow meetecho to associate recordings with sessions as they become = available - Mailman support for internationalized email addresses -- Requires Mailman 3.1, which is expected in early 2017 - Meeting registration support for internationalized email addresses -- Mailman must be done first; user is added to meeting mail lists 6. AOB From nobody Wed Jun 7 11:43:12 2017 Return-Path: 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 D1ADB131462 for ; Wed, 7 Jun 2017 11:43:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 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, 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 tnsAlXne06eX for ; Wed, 7 Jun 2017 11:43:05 -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 3A1C313145F for ; Wed, 7 Jun 2017 11:41:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0C49C1CA3B4; Wed, 7 Jun 2017 11:41:52 -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 JxVzBQD1synC; Wed, 7 Jun 2017 11:41:51 -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 C6C771CA3A9; Wed, 7 Jun 2017 11:41:51 -0700 (PDT) From: Megan Ferguson Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Wed, 7 Jun 2017 11:41:54 -0700 Message-Id: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2017 18:43:11 -0000 Hi Henrik, Input file: draft-ietf-trill-directory-assist-mechanisms-12 Version: id2xml 1.0.0 Issues: File not originally generated with XML Files available:=20 = https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-me= chanisms-12v3.original=20 = https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-me= chanisms-12v3.txt = https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-me= chanisms-12v3-rfcdiff.html (The .txt version above includes our manual updates and the rfcdiff = highlights these from the original.) Note - This file is very representative of the types of issues we = receive when getting a file not originally=20 created with xml2rfc and the case where we feel the id2xml tool would be = most useful for the RPC. That is,=20 we believe that this is a good example of a common use case of id2xml. Testing this file raised a number of questions/errors. 1) Header a) The status =93Proposed Standard=94 does not seem to be recognized. = This is a common value we see in I-Ds not created with xml2rfc. For our purposes, Proposed Standard, Draft Standard, Internet Standard, = Standard Track, and Standards Track should all map to=20 =93Standards Track=94 handling. File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1403, in = get_category self.warn(line, "Expected a recognized status name, found '%s'" % = (line.txt, )) b) WG name: This document did not include a working group name in the = header. We receive documents with no working=20 group indicated (as with this one), with the full WG name, or with the = abbreviation. Is this required for parsing? c) Does the use of the authors=92 full names in the header (or if they = included more than one initial) have any affect on output? We are getting the following error *whether or not* the initials or full = first names appear: Failure converting: 'NoneType' object does not support item assignment Traceback (most recent call last): File "/usr/bin/id2xml", line 9, in load_entry_point('id2xml=3D=3D1.0.0', 'console_scripts', 'id2xml')() File "/usr/lib/python2.7/site-packages/id2xml/run.py", line 222, in = run xml =3D parser.parse_to_xml() File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 953, in = parse_to_xml doc =3D self.document() File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 978, in = document self.root.append(self.back()) File "", line 2, in back File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, in = wrap ret =3D fn(self, *params,**kwargs) File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 2669, = in back self.read_authors_addresses() File "", line 2, in read_authors_addresses File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, in = wrap ret =3D fn(self, *params,**kwargs) File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1693, = in read_authors_addresses self.maybe_author_address(item) File "", line 2, in maybe_author_address File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, in = wrap ret =3D fn(self, *params,**kwargs) File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1793, = in maybe_author_address item['address'] =3D {} TypeError: 'NoneType' object does not support item assignment *However*, we get the following similar error on another file that = previously parsed correctly when we=20 solely updated to use the authors=92 full names in the header (instead = of just initials): Failure converting: 'NoneType' object does not support item assignment Traceback (most recent call last): File "/usr/bin/id2xml", line 9, in load_entry_point('id2xml=3D=3D1.0.0', 'console_scripts', 'id2xml')() File "/usr/lib/python2.7/site-packages/id2xml/run.py", line 222, in = run xml =3D parser.parse_to_xml() File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 953, in = parse_to_xml doc =3D self.document() File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 978, in = document self.root.append(self.back()) File "", line 2, in back File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, in = wrap ret =3D fn(self, *params,**kwargs) File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 2669, = in back self.read_authors_addresses() File "", line 2, in read_authors_addresses File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, in = wrap ret =3D fn(self, *params,**kwargs) File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1693, = in read_authors_addresses self.maybe_author_address(item) File "", line 2, in maybe_author_address File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, in = wrap ret =3D fn(self, *params,**kwargs) File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1793, = in maybe_author_address item['address'] =3D {} TypeError: 'NoneType' object does not support item assignment We tried (to no avail): -updating full first names to initials only -matching 1:1 the affiliation of each author with what appears in the = Authors=92 Addresses section=20 (original uses Huawei for two authors and Huawei Technologies was used = in the Addresses section). -updating the header to include Internet-Draft -removing blank space in the left side of the header Follow ups on header-related issues: i) What regulations/limitations exist on how items must appear in the = header? We are also curious about documents=20 from other streams such as IRTF or Independent (which we have yet to = test). ii) We are unsure about the meaning of some of the header-related = errors. For example: Warning: Expected a label indication top left, found none Perhaps getting a bit more information on this would help us = troubleshoot. iii) Perhaps "Intended status" and the like should be case insensitive? 2) The Status of This Memo did not match the current version. This = caused an error: Error: Unexpected text: expected 'Internet-Drafts are working documents = of the Internet Engineering Task Force (IETF). Note that other groups may also = distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at = http://datatracker.ietf.org/drafts/current/.', found 'Distribution of = this document is unlimited. Comments should be sent=92 3) Older documents frequently have Copyright notices at the end of the = document (such as this one). This caused an error: Error: Unexpected text: expected 'Copyright Notice', found 'D. Eastlake, = et al [Page 1]=92 4) The running header (perhaps due to the period after D?) was a problem = and needed to be manually stripped. D. Eastlake, et al [Page 2] INTERNET-DRAFT TRILL: Directory Service Mechanisms Error: Unexpected section number; expected '1' or a subsection, found = 'D. Eastlake, et al [Page 1]' 5) The references section is unnumbered. This (maybe)creates an error. =20= Error: Expected an Authors' Addresses section, found 'Normative = References=92 Thank you in advance for your help! Megan From nobody Mon Jun 12 13:53:24 2017 Return-Path: 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 C10D8129AB0 for ; Mon, 12 Jun 2017 13:53:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.7 X-Spam-Level: X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.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 gzlmh4Dlu0q8 for ; Mon, 12 Jun 2017 13:53:21 -0700 (PDT) Received: from gproxy7.mail.unifiedlayer.com (gproxy7-pub.mail.unifiedlayer.com [70.40.196.235]) (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 75F3A129AA8 for ; Mon, 12 Jun 2017 13:53:21 -0700 (PDT) Received: from cmgw2 (unknown [10.0.90.83]) by gproxy7.mail.unifiedlayer.com (Postfix) with ESMTP id 45233215E2A for ; Mon, 12 Jun 2017 14:53:21 -0600 (MDT) Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with id XwtH1v00L2SSUrH01wtLgJ; Mon, 12 Jun 2017 14:53:21 -0600 X-Authority-Analysis: v=2.2 cv=Ibz3YSia c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=48vgC7mUAAAA:8 a=kj9zAlcOel0A:10 a=LWSFodeU3zMA:10 a=wU2YTnxGAAAA:8 a=u07AKapRAAAA:8 a=OUXY8nFuAAAA:8 a=NEAV23lmAAAA:8 a=Z8LUrVZHNf7EY4X7ap4A:9 a=CjuIK1q_8ugA:10 a=v2312BZ5C20A:10 a=w1C3t2QeGrPiZgrLijVG:22 a=Yz9wTY_ffGCQnEDHKrcv:22 a=SkebfZ6J2Mmvk2rLHZle:22 a=cAcMbU7R10T-QSRYIcO_:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject: References:In-Reply-To:Message-ID:Date:To:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Ny5dis4b4cZXxkPZOAjccv8qYr8GsojB9dCSPcu7fRM=; b=TJQsFmK70RKnD/5E6zRsLCK3DI iY6kxZDas5nGTcEaMUK0x4qI437PbWZZHKpwXx9hhyJep/g6bq9LV7xh39U2P2MYxYFcfhXo3JTO/ r3t2TqSR9zrsXT9JolBjQAN04; Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:37972 helo=[11.4.0.6]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from ) id 1dKWKr-000380-4a for tools-development@ietf.org; Mon, 12 Jun 2017 14:53:17 -0600 From: Lou Berger To: IETF Development Date: Mon, 12 Jun 2017 16:53:14 -0400 Message-ID: <15c9e14fa90.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> In-Reply-To: References: <795a401e-6801-1290-5511-618889610f3b@labn.net> <20170612.103029.1545590698735704132.mbj@tail-f.com> <15c9bea90e0.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> User-Agent: AquaMail/1.10.0-403 (build: 101000001) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="us-ascii" Content-Transfer-Encoding: 8bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box313.bluehost.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - labn.net X-BWhitelist: no X-Source-IP: 100.15.84.20 X-Exim-ID: 1dKWKr-000380-4a X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([11.4.0.6]) [100.15.84.20]:37972 X-Source-Auth: lberger@labn.net X-Email-Count: 2 X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ== Archived-At: Subject: [TOOLS-DEVELOPMENT] Fwd: [www.ietf.org/rt #171633] Fwd: Re: post interim schema mount follow up X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jun 2017 20:53:24 -0000 Hi tools team, Is there a good (or any) solution for taking interim meeting recordings and converting them to something usable? (Mp3, mp4, youtube...) Thanks, Lou --- Forwarded message --- From: Cindy Morgan via RT Date: June 12, 2017 4:35:47 PM Subject: [www.ietf.org/rt #171633] Fwd: Re: post interim schema mount follow up To: lberger@labn.net Hi Lou, Unfortunately, there isn't currently a way to incorporate the WebEx recordings into the meeting proceedings. The WG chairs can send the link to the recording out to the mailing list, and people can listen/watch it from that. To send out the recording: - Log into WebEx - Click the icon with three vertical lines on the right side of the screen to get the WebEx site menus - Click on the Meeting Center tab - Choose My Recorded Meetings from the list on the left side of the screen - Click the mail (envelope) icon for the recording you wish to share - In the window that pops up, send the recording to yourself. (If you try to send the recording to the WG list directly from WebEx, there is a good chance that it won't make it through, hence sending it to yourself first.) - Once you receive the link to the recording in your email, forward that to the WG list. Best regards, Cindy On Mon Jun 12 03:47:52 2017, lberger@labn.net wrote: > Hello, > > How are webex recordings of interim meetings made available to the > general > community? > > Thanks, > Lou > > > > > --- Forwarded message --- > From: Martin Bjorklund > Date: June 12, 2017 4:30:53 AM > Subject: Re: post interim schema mount follow up > To: lberger@labn.net > CC: lhotka@nic.cz, draft-ietf-netmod-schema-mount@ietf.org, > kwatsen@juniper.net > > Lou, > > Is the webex recording avialable? > > > /martin > > > Lou Berger wrote: > > I think martin was going to consider a couple of additional items: > > See http://etherpad.tools.ietf.org:9000/p/notes-2017-may-interim- > netmod > > > > Line 49: > > > Lou: perhaps put parent-reference in mount point extension, and > then can > > have leaf-ref to specific instance value, e..g., NI=red > > > Martin: idea of placing parent reference in mount point is worth > thinking > > about > > > > Line 65: > > > Andy: I don't see why not follow restconf approach of using module > name, > > but this is okay too > > > Kent: yang-library bis is using module-name as well > > > Martin: using such an implied expansion is worth considering > > > > Lou > > > > > > On 6/5/2017 1:53 PM, Lou Berger wrote: > > > > > > > > > On 6/5/2017 11:38 AM, Ladislav Lhotka wrote: > > >> Hi Lou, > > >> > > >> IMO the only outstanding issue is B.1, which is somewhat awkward > but we > > probably have to paper over it somehow. Any ideas? > > > This is the rpc issue right? To me this is a design time issue > WRT the > > > mount point, so I see no issue documenting the > limitation/restrictions > > > and moving on. > > > > > >> The there are two easy editorial fixes: > > >> > > >> https://github.com/netmod-wg/schema-mount/issues > > > I thought there is some more general cleanup needed as well as an > intent > > > to add more examples, right? > > > > > > Thanks, > > > Lou > > > > > > > > >> Lada > > >> > > >>> On 5 Jun 2017, at 16:36, Lou Berger wrote: > > >>> > > >>> Martin, Lada, > > >>> > > >>> I want to follow up on the post interim meeting actions. Do you > have a > > >>> plan for a post meeting update? What issues do you see are > still > > >>> outstanding? If at all possible, I'd like to help get any open > issues > > >>> resolved (at least among the authors and Rtg DT) before Prague. > > >>> > > >>> Thanks, > > >>> > > >>> Lou > > >>> > > >> -- > > >> Ladislav Lhotka, CZ.NIC Labs > > >> PGP Key ID: 0xB8F92B08A9F76C67 > > >> > > >> > > >> > > >> > > >> > > >> > > > > > > > > From nobody Tue Jun 13 05:18:29 2017 Return-Path: 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 845B21317D0 for ; Tue, 13 Jun 2017 05:18:28 -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] 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 Nv_rgvYZ9ER4 for ; Tue, 13 Jun 2017 05:18:26 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACE7D13169E for ; Tue, 13 Jun 2017 05:18:26 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:54819 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dKkm9-0001wC-Lg; Tue, 13 Jun 2017 05:18:26 -0700 To: Megan Ferguson References: Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <593FD809.4040809@levkowetz.com> Date: Tue, 13 Jun 2017 14:18:17 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="hRq7H1ggV5tV7tSRX608Oc0pQNkLG07mM" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-development@ietf.org, mferguson@amsl.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2017 12:18:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --hRq7H1ggV5tV7tSRX608Oc0pQNkLG07mM Content-Type: multipart/mixed; boundary="pGqvGch4k6SjB5EKOlTbHpE9VW4uha8E7"; protected-headers="v1" From: Henrik Levkowetz To: Megan Ferguson Cc: tools-development@ietf.org Message-ID: <593FD809.4040809@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml References: In-Reply-To: --pGqvGch4k6SjB5EKOlTbHpE9VW4uha8E7 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Megan, On 2017-06-07 02:17, Megan Ferguson wrote: > Hi Henrik, >=20 > Input file: draft-ietf-sidr-bgpsec-protocol-23 > Version: id2xml 1.0.0 > Issues: Figures/Tables and References=20 >=20 > 1) Figures & Tables >=20 > Note - the related figures triggered a warning as the example that foll= ows (i.e., Figures 3-7),=20 > so perhaps these issues are already known. >=20 > draft-ietf-sidr-bgpsec-protocol-23test.txt(422): Warning: Unexpected ti= tle: expected 'Table ...=E2=80=99,=20 > found 'Figure 4: Secure_Path format.'. This looks like a texttable tha= t has been entered as a figure. The generated XML will need adjustment. >=20 > a) Extra space added in figures. =20 >=20 >=20 > Original text: >=20 > +-----------------------------------------------+ > | Secure_Path Length (2 octets) | > +-----------------------------------------------+ > | One or More Secure_Path Segments (variable) | > +-----------------------------------------------+ >=20 > Figure 4: Secure_Path format. >=20 >=20 > id2xml text output version: >=20 > +-----------------------------------------------+ > | Secure_Path Length (2 octets) | > +-----------------------------------------------+ > | One or More Secure_Path Segments (variable) | > | | > +-----------------------------------------------+ Right. This is a bug, an empty table cell. Will fix. > Figure 4: Secure_Path format. >=20 > b) Perhaps because of the error mentioned, the figure numbers were chan= ged. Yes. So, there are related issues here. The basic question is how to handle things which can be marked up as tabl= es. id2xml takes the approach that if it can be marked up as tables, it will = be, because even if it makes no difference if it's done as tables or as figur= es in the text output, it will make a lot of difference in the quality of ht= ml output. So if it is recognized as a table, the generated xml will be for= a texttable, rather than for a figure. When it turns out that the draft numbers it as a figure, you have 2 optio= ns: either change the markup, removing the texttable markup and adding in fig= ure artwork instead, which will preserve the figure numbering, or, what I'd recommend in most cases, accept the change from Figure to Table, and adju= st the title accordingly. This will in most cases give the best html output= =2E > c) We see that the =E2=80=9CFigures=E2=80=9D that were made into textta= bles did not > use a title element, but created the following. Additionally, we do > not see any alignment designation for the text (e.g., align=3D'center=E2=80=99>text). Yes. For tables which have a Figure title, but get texttable markup, no title is created. I could change that, so that I recognize the Figure= : as an indication of a title line, also for texttables. That would probab= ly remove some manual work. Will fix. >=20 > id2xml XML: >=20 > > Figure 3 provides the specification of the format for the BGPsec_Path= > attribute. >=20 > Secure_Path = (variable) > Sequence of one or two Signature_Blocks (variable) > > > > Figure 3: BGPsec_Path attribute format. > > >=20 >=20 > 2) We note that references to sections and figures within the > document did not use elements consistently. For example: >=20 > id2xml in xml file: >=20 > > If the update message was received from a peer that is not > expected to set pCount=3D0 (see > and Section 4.3) then > check to ensure that the pCount field in the most-recently added > Secure_Path Segment is not equal to zero. (Note: See router > configuration guidance related to this in Section 7.2.) Aha. Ok. That's a bug in the pattern that recognizes Section references.= Will fix. >=20 > With figure mentions not using them at all (at least in this file). Right. I can add that, but there's an issue here, with the potential re-numbering of Table: and Figure: items. I'll see what I can do. > 3) A few missed reference entries (creating empty reference elements) > and xref elements in the running text (this issue was previously > reported). The output XML file wouldn't validate because of the > errors. >=20 >=20 > ERROR: Unable to validate the XML document: draft-ietf-sidr-bgpsec-prot= ocol-23test.xml > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2002: Element front co= ntent does not follow the DTD, expecting (title , author+ , date , area* = , workgroup* , keyword* , abstract? , note*), got nothing. > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2006: Element front co= ntent does not follow the DTD, expecting (title , author+ , date , area* = , workgroup* , keyword* , abstract? , note*), got nothing. > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2025: Element front co= ntent does not follow the DTD, expecting (title , author+ , date , area* = , workgroup* , keyword* , abstract? , note*), got nothing. Aha. Ok, I'll dig into that. Looks like a clear bug. Thank you for the feedback! Best regards, Henrik --pGqvGch4k6SjB5EKOlTbHpE9VW4uha8E7-- --hRq7H1ggV5tV7tSRX608Oc0pQNkLG07mM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZP9gJAAoJEE6bV0uPuxcaVqAP/A3G3T88X4fgAVWkCcDuaePo F2nJYB+NmXENiMVvleA1ljL0yI1oUZjyTwEkeIE58VIihk4JSWlYqNbooWnddxrL ZVNd7HWkWXXASkWuQ5YdxSnu2ZY73rbMAeqFlMQOSrhIbaZcQi8/P7XSikUnxH8Z TACHTUGVRidhmG/o3cSKNi9IwayUZ5ciaOKjlukknkzxBY0t87tukIyXe0TZ0RNq Uoc/+OytlF7eD4YXtVGuTVe0M8u+mLbUhtH9SpNuZSOpyVlMtnu6Pr11cJ+2S57m 0Cjt6gDd3ZOagmqOC1xnapguT4D+LXQcT6grs+yOlo3xwM84SnZ9YASfJBmtoFHZ 5fNj1YUwbMdxwxd80KkA5NTM41TbwCP07/sMUamCLfa0GakN4h3E3rC6OiI8EAYV d4qiXdPT4hxPwySi5VGawAXtwGVLd0x2NOt8ytvMTVXwBylZ/17FtuHzQ+ITkcXr t3Ao9DwMXPRAEZCSK/WDQ4XJwb8UlkE/pCOcPpO8J0g/sUqngXDLBlnrXrNq+Xnt 54WP1gt+3HdGtoFr/E3Nv/kBLsFhUw/f4P2iwxWhRxazlHK8pZ7u0/QfKdxS/XAX obRyvWxUMBX86N/wpR5w0DnUf+ox60v5pOGOYWMLkgsC5jlM/uENudajJM3MKp7i Bjb6eCtfHVj0k6Hbo0ut =FWZc -----END PGP SIGNATURE----- --hRq7H1ggV5tV7tSRX608Oc0pQNkLG07mM-- From nobody Tue Jun 13 05:26:27 2017 Return-Path: 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 4DC2A1317A1 for ; Tue, 13 Jun 2017 05:26:25 -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] 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 0VFoQJJjXV0A for ; Tue, 13 Jun 2017 05:26:24 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 084591316A3 for ; Tue, 13 Jun 2017 05:26:24 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:54982 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dKktr-0001wt-E4; Tue, 13 Jun 2017 05:26:23 -0700 To: Megan Ferguson References: <593FD809.4040809@levkowetz.com> Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <593FD9E8.4020403@levkowetz.com> Date: Tue, 13 Jun 2017 14:26:16 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <593FD809.4040809@levkowetz.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3EVAlmjPkkeIffmLlHVMUgfMB9spdHsjq" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-development@ietf.org, mferguson@amsl.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2017 12:26:25 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3EVAlmjPkkeIffmLlHVMUgfMB9spdHsjq Content-Type: multipart/mixed; boundary="aLkvUcuiukcQ5C8bbX8ijWHOQHJIdmQ9t"; protected-headers="v1" From: Henrik Levkowetz To: Megan Ferguson Cc: tools-development@ietf.org Message-ID: <593FD9E8.4020403@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml References: <593FD809.4040809@levkowetz.com> In-Reply-To: <593FD809.4040809@levkowetz.com> --aLkvUcuiukcQ5C8bbX8ijWHOQHJIdmQ9t Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable So, regarding this: On 2017-06-13 14:18, Henrik Levkowetz wrote: >> > 3) A few missed reference entries (creating empty reference elements= ) >> > and xref elements in the running text (this issue was previously >> > reported). The output XML file wouldn't validate because of the >> > errors. >> >=20 >> >=20 >> > ERROR: Unable to validate the XML document: draft-ietf-sidr-bgpsec-p= rotocol-23test.xml >> > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2002: Element front= content does not follow the DTD, expecting (title , author+ , date , are= a* , workgroup* , keyword* , abstract? , note*), got nothing. >> > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2006: Element front= content does not follow the DTD, expecting (title , author+ , date , are= a* , workgroup* , keyword* , abstract? , note*), got nothing. >> > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2025: Element front= content does not follow the DTD, expecting (title , author+ , date , are= a* , workgroup* , keyword* , abstract? , note*), got nothing. > Aha. Ok, I'll dig into that. Looks like a clear bug. When id2xml fails to parse a reference, it inserts a element= with only a , which will not convert. This is so that you don't unintentionally end up with missing references in the converted XML. The= solution is generally to adjust the reference text in the input file to match the format you would expect; I think that id2xml is now at a point where it will recognize pretty much all reference text entries which have= the format used in published RFCs. I'm going to look at the 3 instances in draft-ietf-sidr-bgpsec-protocol-2= 3 and see if additional patterns make sense, though. If you would like a different approach than leaving empty elemen= ts in the file, I'd be happy to adjust things the way you want them; just le= t me know what you'd like. Best regards, Henrik --aLkvUcuiukcQ5C8bbX8ijWHOQHJIdmQ9t-- --3EVAlmjPkkeIffmLlHVMUgfMB9spdHsjq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZP9noAAoJEE6bV0uPuxcajk4P/R83kOIQNQmvUma2a7a300Zk 17PeuGQn0rbWU6UiH/CKwUavcFSIzzrQQOLpK+p+iiEPN/xTPY6huXhDvpoY49kv anwCkccrQ1wI4PbsK4MpInSXfjxL5OWP6eHXP8IXI0H3gdFllrt6EB3mgQVcToi+ HwIhkWoICtcrQxgegCaRAiTHhMsfnvDsEDf6qbvs+ihzXrZdKZRabsmIpexrucVR lhRR0UvxxxECdby+OVfeSL22W/n2tDWKRoeCcQtGZUCU48nV0vPBePQRpaDp7amV 6BNwWj8EFNInoESki8weWOxs0urRSph/gzsw9RK/D2nnOc30jFqXLpTDvCGdyrrI oB8OKfQ2SxlwF8NAyP79s6YcVNXyShXphZosj8AKaFv99crQ+QGZWR+UtJqgSlwp nyo4o8q+ISkQfnQY1XR5/koQIBr46emTfwJ6oeNkDHPv/ZWmvfasqrw7rkRahy4z 8S/oJfB6pxWigqejyk03oXcsUtJkeiLWfGrHUtH/FYSQ06VyYrQcVSc61U203PkF 4mZqK7DZBWI1smThbB0VqWqEx/+xHPnO1bYIxCejOYtqdz8jz9+CXEI91Yq0fOlX 6JRFpjm9PHmZcoUMw7P9T+lJYkmnpUdujbdZH7VAmypMn8/PhBSXiaW1y1pRz7Aw P0s9ccbkEk0YPYcxmuKy =UB2E -----END PGP SIGNATURE----- --3EVAlmjPkkeIffmLlHVMUgfMB9spdHsjq-- From nobody Tue Jun 13 05:39:18 2017 Return-Path: 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 E9622131823 for ; Tue, 13 Jun 2017 05:39:16 -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] 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 4gsVN5MeFhk4 for ; Tue, 13 Jun 2017 05:39:15 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F94D13181E for ; Tue, 13 Jun 2017 05:39:14 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:55237 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dKl6H-0000me-PP; Tue, 13 Jun 2017 05:39:14 -0700 To: Megan Ferguson References: <593FD809.4040809@levkowetz.com> <593FD9E8.4020403@levkowetz.com> Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <593FDCE9.3090701@levkowetz.com> Date: Tue, 13 Jun 2017 14:39:05 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <593FD9E8.4020403@levkowetz.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Hbi2QqvFSsC00OBgi1jnaHQv8jk2Jqo0R" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-development@ietf.org, mferguson@amsl.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2017 12:39:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Hbi2QqvFSsC00OBgi1jnaHQv8jk2Jqo0R Content-Type: multipart/mixed; boundary="FcdAHmn22qmkBf8URclMhO3nIpTvJHbHF"; protected-headers="v1" From: Henrik Levkowetz To: Megan Ferguson Cc: tools-development@ietf.org Message-ID: <593FDCE9.3090701@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml References: <593FD809.4040809@levkowetz.com> <593FD9E8.4020403@levkowetz.com> In-Reply-To: <593FD9E8.4020403@levkowetz.com> --FcdAHmn22qmkBf8URclMhO3nIpTvJHbHF Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Returning to this issue again: On 2017-06-13 14:26, Henrik Levkowetz wrote: > So, regarding this: >=20 > On 2017-06-13 14:18, Henrik Levkowetz wrote: >>> > 3) A few missed reference entries (creating empty reference element= s) >>> > and xref elements in the running text (this issue was previously >>> > reported). The output XML file wouldn't validate because of the >>> > errors. >>> >=20 >>> >=20 >>> > ERROR: Unable to validate the XML document: draft-ietf-sidr-bgpsec-= protocol-23test.xml >>> > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2002: Element fron= t content does not follow the DTD, expecting (title , author+ , date , ar= ea* , workgroup* , keyword* , abstract? , note*), got nothing. >>> > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2006: Element fron= t content does not follow the DTD, expecting (title , author+ , date , ar= ea* , workgroup* , keyword* , abstract? , note*), got nothing. >>> > draft-ietf-sidr-bgpsec-protocol-23test.xml: Line 2025: Element fron= t content does not follow the DTD, expecting (title , author+ , date , ar= ea* , workgroup* , keyword* , abstract? , note*), got nothing. >> Aha. Ok, I'll dig into that. Looks like a clear bug. >=20 > When id2xml fails to parse a reference, it inserts a eleme= nt > with only a , which will not convert. This is so that you don'= t > unintentionally end up with missing references in the converted XML. T= he > solution is generally to adjust the reference text in the input file to= > match the format you would expect; I think that id2xml is now at a poin= t > where it will recognize pretty much all reference text entries which ha= ve > the format used in published RFCs. >=20 > I'm going to look at the 3 instances in draft-ietf-sidr-bgpsec-protocol= -23 > and see if additional patterns make sense, though. Changing "February 10, 2016" to "10 February 2016" lets the [Borchert] reference entry be parsed. I would prefer not to add another pattern to handle this, as commas generally separate the reference parts, and adding= patterns for individual parts that contain commas are bound to lead to complications. For the other 2 entries ([FIPS186-4] and [SP800-90A]) I've now added a ne= w pattern which will convert them. Henrik > If you would like a different approach than leaving empty elem= ents > in the file, I'd be happy to adjust things the way you want them; just = let > me know what you'd like. >=20 >=20 > Best regards, >=20 > Henrik >=20 >=20 --FcdAHmn22qmkBf8URclMhO3nIpTvJHbHF-- --Hbi2QqvFSsC00OBgi1jnaHQv8jk2Jqo0R Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZP9zqAAoJEE6bV0uPuxcaq98QAKvvNW9VmfssKrdv7KcuPg4T DeVH7cM0hGOZzl3IzUaWEAVEPsZvcrZgS+xLfyGxbQMl0/XsV347ZH/qbtf8AWsx lvSYICMkmaxyaKPU6tS1+uBMXnZ7VAzZWPVzTyVefakBSv20cnGPvz3RvrioaGDx qDSASXr2LDd9XsZ/zCgTZ/7v9Mxw3hHzucF2wMMefGt3jI+kas+kH2Zgb5XaxYwe JiqBM+YKCddzIlyOv5MnNl+W4l4UBQpExvIlX5uXMpofpcQbAYyDOeK74c+y3jua 053B1+vPUmPNZYnQGO5OpGYSNfv84/WPtNQ9SFxtRwCsLoxp82k3DwXz74Zl+UQE V16HCieRENon7R41wjQ5BEPv2bEL3mNnd3hgIcaBtukHoCz8fG0zFmE9H4Bk68Sw QfhnQkqIw0PtQNl+c72Qkgg777rvhQe7fsENGVACpwM8SaqGTetwmG0UyCTSOPrd MyX7LU7Yj64+MdsBxrI+RUPWvGZj6sT+Prr6pmHxJpJldwYzHNyFAL9NIgirj4J8 AV0WEWOghQ33cDyhHTgL/37DZ+auRTdaUinBwrCfmQ4KO5mDBf9AVhDyr1qsMLEk GyjHstWWHCFGDmEl9cSiO6V/7WwCIzf41WdLnq6CoroCaf3YzdlBwc5kqMrHmG/4 TaTmhySGRks2FeoGVRYv =HKS4 -----END PGP SIGNATURE----- --Hbi2QqvFSsC00OBgi1jnaHQv8jk2Jqo0R-- From nobody Tue Jun 13 08:51:56 2017 Return-Path: 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 E1125131898 for ; Tue, 13 Jun 2017 08:51:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.88 X-Spam-Level: X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=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 uwLB9lpr9Kb9 for ; Tue, 13 Jun 2017 08:51:52 -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 DDB2B1317D7 for ; Tue, 13 Jun 2017 08:40:06 -0700 (PDT) Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v5DFe5uF042663 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 13 Jun 2017 10:40:06 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local To: tools-development@ietf.org References: <570CB681-E34E-478B-986B-7BB677CBA9B2@vigilsec.com> From: Robert Sparks Message-ID: Date: Tue, 13 Jun 2017 10:40:05 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <570CB681-E34E-478B-986B-7BB677CBA9B2@vigilsec.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 13 June 2017 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2017 15:51:55 -0000 Notes inline: On 6/7/17 11:08 AM, Russ Housley wrote: > Tools Call Agenda -- 13 June 2017 at 1:00 Eastern > > > JOIN WEBEX MEETING > https://ietf.webex.com/ietf/j.php?MTID=m440dd848726339c03e605b9956e38bac > Meeting number (access code): 640 103 570 > Meeting password: tools > > JOIN BY PHONE > 1-877-668-4493 Call-in toll free number (US/Canada) > 1-650-479-3208 Call-in toll number (US/Canada) > Meeting number (access code): 640 103 570 > Meeting password: tools > > > 1. Datatracker Projects > - Expected Datatracker Releases -- Robert and Henrik > -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan Updated. See also https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN > - Volunteer Enhancements > -- Submit an I-D directly from GitHub -- Robert Still in queue - not started > -- Improve NomCom feedback tools -- Robert In progress - lots finished and deployed. See Of particular note: The nomcom can now collect feedback on an arbitrary question. Remaining: > - Migrate to Django 1.11 when it is released -- Henrik > > 2. Community & Other Projects > - Discontinue MonArch email archives -- Robert Nothing new since last call to report on this. > - IETF Website Makeover -- Greg and Russ > > 3. RFC Services Projects > - RFC Format Contracts -- Heather and Robert > -- IDnits > -- Publication Formatter > -- RFClint > -- SVGcheck > -- Text Submission > -- XMLdiff See https://trac.tools.ietf.org/tools/ietfdb/wiki/FormatToolsPlan. The text submission converter to v2 (id2xml) is released and is in testing with the production center. > > 4. Server Infrastructure > - IESG discussions of DMARC -- Robert and Alexey > -- Mailman upgrade > -- Impact on Internet-Draft-specific mail aliases > - Libraries for HTML of I-Ds -- Henrik > > 5. Parking Lot > - Migrate from Python 2.7 to Python 3 > - CDN support for HTML and PDF I-Ds -- Henrik > - Migrate from MySQL to PostgreSQL -- Henrik > - Improve infrastructure for finding and fetching artifacts -- Robert > - Author information for very old I-Ds in the datatracker -- Robert > - Replace I-Ds in proceedings with links to archive copy? > - Performance improvements and transition to Postgres -- Henrik > - VM Architecture for Servers -- Robert > - Add view of recent ballots by telechat > - Allow meetecho to associate recordings with sessions as they become available > - Mailman support for internationalized email addresses > -- Requires Mailman 3.1, which is expected in early 2017 > - Meeting registration support for internationalized email addresses > -- Mailman must be done first; user is added to meeting mail lists > > 6. AOB > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Tue Jun 13 09:05:11 2017 Return-Path: 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 DC9F5131AAF for ; Tue, 13 Jun 2017 09:05:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.88 X-Spam-Level: X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=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 0oGdxjkiW4OZ for ; Tue, 13 Jun 2017 09:05:06 -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 820E813189F for ; Tue, 13 Jun 2017 08:54:31 -0700 (PDT) Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v5DFsUn3044957 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 13 Jun 2017 10:54:31 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local From: Robert Sparks To: tools-development@ietf.org References: <570CB681-E34E-478B-986B-7BB677CBA9B2@vigilsec.com> Message-ID: <6e86ccf3-2729-beaa-95bb-1ca9c8779ee0@nostrum.com> Date: Tue, 13 Jun 2017 10:54:30 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 13 June 2017 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2017 16:05:09 -0000 New things to consider: * The review tool is unfairly assigning load to reviewers (https://trac.tools.ietf.org/tools/ietfdb/ticket/2305) * The meeting scheduling tool needs some maintenance (https://trac.tools.ietf.org/tools/ietfdb/ticket/2313) * Lou forwarded a request to make webex recordings of interims more easily available from the proceedings. On 6/13/17 10:40 AM, Robert Sparks wrote: > Notes inline: > > On 6/7/17 11:08 AM, Russ Housley wrote: >> Tools Call Agenda -- 13 June 2017 at 1:00 Eastern >> >> >> JOIN WEBEX MEETING >> https://ietf.webex.com/ietf/j.php?MTID=m440dd848726339c03e605b9956e38bac >> Meeting number (access code): 640 103 570 >> Meeting password: tools >> >> JOIN BY PHONE >> 1-877-668-4493 Call-in toll free number (US/Canada) >> 1-650-479-3208 Call-in toll number (US/Canada) >> Meeting number (access code): 640 103 570 >> Meeting password: tools >> >> >> 1. Datatracker Projects >> - Expected Datatracker Releases -- Robert and Henrik >> -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan > Updated. See also > https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN >> - Volunteer Enhancements >> -- Submit an I-D directly from GitHub -- Robert > Still in queue - not started >> -- Improve NomCom feedback tools -- Robert > In progress - lots finished and deployed. > > See > > > > > > Of particular note: The nomcom can now collect feedback on an > arbitrary question. > > Remaining: > > >> - Migrate to Django 1.11 when it is released -- Henrik >> >> 2. Community & Other Projects >> - Discontinue MonArch email archives -- Robert > Nothing new since last call to report on this. >> - IETF Website Makeover -- Greg and Russ >> >> 3. RFC Services Projects >> - RFC Format Contracts -- Heather and Robert >> -- IDnits >> -- Publication Formatter >> -- RFClint >> -- SVGcheck >> -- Text Submission >> -- XMLdiff > See https://trac.tools.ietf.org/tools/ietfdb/wiki/FormatToolsPlan. > The text submission converter to v2 (id2xml) is released and is in > testing with the production center. >> >> 4. Server Infrastructure >> - IESG discussions of DMARC -- Robert and Alexey >> -- Mailman upgrade >> -- Impact on Internet-Draft-specific mail aliases >> - Libraries for HTML of I-Ds -- Henrik >> >> 5. Parking Lot >> - Migrate from Python 2.7 to Python 3 >> - CDN support for HTML and PDF I-Ds -- Henrik >> - Migrate from MySQL to PostgreSQL -- Henrik >> - Improve infrastructure for finding and fetching artifacts -- >> Robert >> - Author information for very old I-Ds in the datatracker -- Robert >> - Replace I-Ds in proceedings with links to archive copy? >> - Performance improvements and transition to Postgres -- Henrik >> - VM Architecture for Servers -- Robert >> - Add view of recent ballots by telechat >> - Allow meetecho to associate recordings with sessions as they >> become available >> - Mailman support for internationalized email addresses >> -- Requires Mailman 3.1, which is expected in early 2017 >> - Meeting registration support for internationalized email addresses >> -- Mailman must be done first; user is added to meeting mail lists >> >> 6. AOB >> >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development > From nobody Tue Jun 13 09:16:40 2017 Return-Path: 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 5FAA113191D for ; Tue, 13 Jun 2017 09:16:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.7 X-Spam-Level: X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.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 0XdXlJOJllYD for ; Tue, 13 Jun 2017 09:16:25 -0700 (PDT) Received: from gproxy6.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) (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 33186131AF5 for ; Tue, 13 Jun 2017 09:07:52 -0700 (PDT) Received: from cmgw3 (unknown [10.0.90.84]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id 2F83A1E0635 for ; Tue, 13 Jun 2017 10:07:51 -0600 (MDT) Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id YG7n1v0012SSUrH01G7qEd; Tue, 13 Jun 2017 10:07:51 -0600 X-Authority-Analysis: v=2.2 cv=VKStp5HX c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=LWSFodeU3zMA:10 a=48vgC7mUAAAA:8 a=NojvYFcnAAAA:8 a=eXVmCkOyt0dxajxoz60A:9 a=bO5qvCn87X1yNpS_:21 a=YC75Zz3iP446GiVz:21 a=QEXdDO2ut3YA:10 a=NU7HZUQD-k8A:10 a=T8E0iRN_syYA:10 a=9uUzcS5Nrb8A:10 a=w1C3t2QeGrPiZgrLijVG:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=AqkfPlmFa9gT7a0w2tnap02d1ESPNMzeNeAAWqLaM5g=; b=KkDGInleVLcZ3zNjKQuTb0+Zmr 13lZMEoETLPZUJzCDEUcMUDSDz80ForhpBcYOQxsqakLJ5BDIoyRCo3tv6+29b5pPXezhaaR4KTbO 7tRepNsDgnS7Ki5mI1drl2XTn; Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:48422 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from ) id 1dKoM6-0004s7-F0; Tue, 13 Jun 2017 10:07:46 -0600 To: Robert Sparks , tools-development@ietf.org References: <570CB681-E34E-478B-986B-7BB677CBA9B2@vigilsec.com> <6e86ccf3-2729-beaa-95bb-1ca9c8779ee0@nostrum.com> From: Lou Berger Message-ID: Date: Tue, 13 Jun 2017 12:07:42 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <6e86ccf3-2729-beaa-95bb-1ca9c8779ee0@nostrum.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box313.bluehost.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - labn.net X-BWhitelist: no X-Source-IP: 100.15.84.20 X-Exim-ID: 1dKoM6-0004s7-F0 X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([IPv6:::1]) [100.15.84.20]:48422 X-Source-Auth: lberger@labn.net X-Email-Count: 2 X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ== Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 13 June 2017 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2017 16:16:28 -0000 On 6/13/2017 11:54 AM, Robert Sparks wrote: > New things to consider: > > * The review tool is unfairly assigning load to reviewers > (https://trac.tools.ietf.org/tools/ietfdb/ticket/2305) > > * The meeting scheduling tool needs some maintenance > (https://trac.tools.ietf.org/tools/ietfdb/ticket/2313) > > * Lou forwarded a request to make webex recordings of interims more > easily available from the proceedings. > Thanks - the germination of this is access to interim recordings in a non-proprietary (and multi-platform) format... Lou > On 6/13/17 10:40 AM, Robert Sparks wrote: >> Notes inline: >> >> On 6/7/17 11:08 AM, Russ Housley wrote: >>> Tools Call Agenda -- 13 June 2017 at 1:00 Eastern >>> >>> >>> JOIN WEBEX MEETING >>> https://ietf.webex.com/ietf/j.php?MTID=m440dd848726339c03e605b9956e38bac >>> Meeting number (access code): 640 103 570 >>> Meeting password: tools >>> >>> JOIN BY PHONE >>> 1-877-668-4493 Call-in toll free number (US/Canada) >>> 1-650-479-3208 Call-in toll number (US/Canada) >>> Meeting number (access code): 640 103 570 >>> Meeting password: tools >>> >>> >>> 1. Datatracker Projects >>> - Expected Datatracker Releases -- Robert and Henrik >>> -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan >> Updated. See also >> https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN >>> - Volunteer Enhancements >>> -- Submit an I-D directly from GitHub -- Robert >> Still in queue - not started >>> -- Improve NomCom feedback tools -- Robert >> In progress - lots finished and deployed. >> >> See >> >> >> >> >> >> Of particular note: The nomcom can now collect feedback on an >> arbitrary question. >> >> Remaining: >> >> >>> - Migrate to Django 1.11 when it is released -- Henrik >>> >>> 2. Community & Other Projects >>> - Discontinue MonArch email archives -- Robert >> Nothing new since last call to report on this. >>> - IETF Website Makeover -- Greg and Russ >>> >>> 3. RFC Services Projects >>> - RFC Format Contracts -- Heather and Robert >>> -- IDnits >>> -- Publication Formatter >>> -- RFClint >>> -- SVGcheck >>> -- Text Submission >>> -- XMLdiff >> See https://trac.tools.ietf.org/tools/ietfdb/wiki/FormatToolsPlan. >> The text submission converter to v2 (id2xml) is released and is in >> testing with the production center. >>> 4. Server Infrastructure >>> - IESG discussions of DMARC -- Robert and Alexey >>> -- Mailman upgrade >>> -- Impact on Internet-Draft-specific mail aliases >>> - Libraries for HTML of I-Ds -- Henrik >>> >>> 5. Parking Lot >>> - Migrate from Python 2.7 to Python 3 >>> - CDN support for HTML and PDF I-Ds -- Henrik >>> - Migrate from MySQL to PostgreSQL -- Henrik >>> - Improve infrastructure for finding and fetching artifacts -- >>> Robert >>> - Author information for very old I-Ds in the datatracker -- Robert >>> - Replace I-Ds in proceedings with links to archive copy? >>> - Performance improvements and transition to Postgres -- Henrik >>> - VM Architecture for Servers -- Robert >>> - Add view of recent ballots by telechat >>> - Allow meetecho to associate recordings with sessions as they >>> become available >>> - Mailman support for internationalized email addresses >>> -- Requires Mailman 3.1, which is expected in early 2017 >>> - Meeting registration support for internationalized email addresses >>> -- Mailman must be done first; user is added to meeting mail lists >>> >>> 6. AOB >>> >>> _______________________________________________ >>> TOOLS-DEVELOPMENT mailing list >>> TOOLS-DEVELOPMENT@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-development > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development > From nobody Tue Jun 13 09:35:07 2017 Return-Path: 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 9C4151293DF for ; Tue, 13 Jun 2017 09:35:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ETl3FhJjT3hp for ; Tue, 13 Jun 2017 09:35:01 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00E9D12EAE4 for ; Tue, 13 Jun 2017 09:34:46 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:60171 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dKomC-0002Xu-Pf; Tue, 13 Jun 2017 09:34:45 -0700 To: Megan Ferguson References: Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <5940141D.1060903@levkowetz.com> Date: Tue, 13 Jun 2017 18:34:37 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="p6ufxjb2SmpIQlutc1oS4Ou6jJM7736Ft" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-development@ietf.org, mferguson@amsl.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2017 16:35:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --p6ufxjb2SmpIQlutc1oS4Ou6jJM7736Ft Content-Type: multipart/mixed; boundary="DRbSNJEixPD9LUCLCSom7iCtD6gpelbWh"; protected-headers="v1" From: Henrik Levkowetz To: Megan Ferguson Cc: tools-development@ietf.org Message-ID: <5940141D.1060903@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml References: In-Reply-To: --DRbSNJEixPD9LUCLCSom7iCtD6gpelbWh Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Megan, On 2017-06-07 20:41, Megan Ferguson wrote: > Hi Henrik, >=20 > Input file: draft-ietf-trill-directory-assist-mechanisms-12 > Version: id2xml 1.0.0 > Issues: File not originally generated with XML > Files available:=20 > https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist= -mechanisms-12v3.original=20 > 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 >=20 > (The .txt version above includes our manual updates and the rfcdiff > highlights these from the original.) >=20 > Note - This file is very representative of the types of issues we > receive when getting a file not originally created with xml2rfc and > the case where we feel the id2xml tool would be most useful for the > RPC. That is, we believe that this is a good example of a common use > case of id2xml. Ok, good to know. I'm adding this to the test suite. >=20 > Testing this file raised a number of questions/errors. >=20 > 1) Header >=20 > a) The status =E2=80=9CProposed Standard=E2=80=9D does not seem to be r= ecognized. > This is a common value we see in I-Ds not created with xml2rfc. For > our purposes, Proposed Standard, Draft Standard, Internet Standard, > Standard Track, and Standards Track should all map to =E2=80=9CStandard= s > Track=E2=80=9D handling. Right. Fixed in my sources. > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1403, i= n get_category > self.warn(line, "Expected a recognized status name, found '%s'" % (l= ine.txt, )) >=20 > b) WG name: This document did not include a working group name in the > header. We receive documents with no working group indicated (as with > this one), with the full WG name, or with the abbreviation. Is this > required for parsing? No. If no working group name is found, the generated xml will produce 'Network Working Group' top left. > c) Does the use of the authors=E2=80=99 full names in the header (or if= they > included more than one initial) have any affect on output? > We are getting the following error *whether or not* the initials or > full first names appear: >=20 > Failure converting: 'NoneType' object does not support item assignment > Traceback (most recent call last): > File "/usr/bin/id2xml", line 9, in > load_entry_point('id2xml=3D=3D1.0.0', 'console_scripts', 'id2xml')(= ) > File "/usr/lib/python2.7/site-packages/id2xml/run.py", line 222, in r= un > xml =3D parser.parse_to_xml() > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 953, i= n parse_to_xml > doc =3D self.document() > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 978, i= n document > self.root.append(self.back()) > File "", line 2, in back > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, i= n wrap > ret =3D fn(self, *params,**kwargs) > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 2669, = in back > self.read_authors_addresses() > File "", line 2, in read_authors_addresses > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, i= n wrap > ret =3D fn(self, *params,**kwargs) > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1693, = in read_authors_addresses > self.maybe_author_address(item) > File "", line 2, in maybe_author_address > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, i= n wrap > ret =3D fn(self, *params,**kwargs) > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1793, = in maybe_author_address > item['address'] =3D {} > TypeError: 'NoneType' object does not support item assignment Oops. This is an internal error. Fixed in my sources. > *However*, we get the following similar error on another file that prev= iously parsed correctly when we=20 > solely updated to use the authors=E2=80=99 full names in the header (in= stead of just initials): >=20 > Failure converting: 'NoneType' object does not support item assignment > Traceback (most recent call last): > File "/usr/bin/id2xml", line 9, in > load_entry_point('id2xml=3D=3D1.0.0', 'console_scripts', 'id2xml')(= ) > File "/usr/lib/python2.7/site-packages/id2xml/run.py", line 222, in r= un > xml =3D parser.parse_to_xml() > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 953, i= n parse_to_xml > doc =3D self.document() > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 978, i= n document > self.root.append(self.back()) > File "", line 2, in back > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, i= n wrap > ret =3D fn(self, *params,**kwargs) > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 2669, = in back > self.read_authors_addresses() > File "", line 2, in read_authors_addresses > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, i= n wrap > ret =3D fn(self, *params,**kwargs) > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1693, = in read_authors_addresses > self.maybe_author_address(item) > File "", line 2, in maybe_author_address > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 560, i= n wrap > ret =3D fn(self, *params,**kwargs) > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1793, = in maybe_author_address > item['address'] =3D {} > TypeError: 'NoneType' object does not support item assignment >=20 > We tried (to no avail): > -updating full first names to initials only > -matching 1:1 the affiliation of each author with what appears in the A= uthors=E2=80=99 Addresses section=20 > (original uses Huawei for two authors and Huawei Technologies was used = in the Addresses section). > -updating the header to include Internet-Draft > -removing blank space in the left side of the header The root cause of this was an incorrect starting value for line counting internally. If there had been blank lines ahead of the first text lines,= you would not have seen this (but then I would not have found the related= bug). Fixed in my sources. > Follow ups on header-related issues: >=20 > i) What regulations/limitations exist on how items must appear in the > header? We are also curious about documents from other streams such > as IRTF or Independent (which we have yet to test). If there is a working group name, it must appear on the first line. All left-hand header items which have the form 'Key word: Text' can appear in any order, top left, but it is expected that there are no interleaved blank lines top left. > ii) We are unsure about the meaning of some of the header-related > errors. For example: >=20 > Warning: Expected a label indication top left, found none This is the Internet-Draft or Request for Comments indication. > Perhaps getting a bit more information on this would help us > troubleshoot. Ack, understood. I'll see what I can do. > iii) Perhaps "Intended status" and the like should be case > insensitive? I've made it somewhat less case sensitive, but not completely in the next version. If more feedback show that complete case insensitivity would be best, I'll be happy to make it so. > 2) The Status of This Memo did not match the current version. This > caused an error: >=20 > Error: Unexpected text: expected 'Internet-Drafts are working documents= of the Internet > Engineering Task Force (IETF). Note that other groups may also distr= ibute working documents as Internet-Drafts. The > list of current Internet-Drafts is at http://datatracker.ietf.org/dra= fts/current/.', found 'Distribution of this > document is unlimited. Comments should be sent=E2=80=99 Yes. id2xml uses the Status of This Memo text to derive the category=3D setting of the element. I can change that to just ignore the status of memo section, if you would prefer to manually insert the proper= category in the element. > 3) Older documents frequently have Copyright notices at the end of the = document (such as this one). This caused an error: >=20 > Error: Unexpected text: expected 'Copyright Notice', found 'D. Eastlake= , et al > [Page 1]=E2=80=99 Mmm. Ok. I'll do some tests on making the copyright notice optional. > 4) The running header (perhaps due to the period after D?) was a proble= m and needed to be manually stripped. >=20 > D. Eastlake, et al [Page 2= ] > INTERNET-DRAFT TRILL: Directory Service Mechanism= s Maybe. Or the ", et al". I'll have a look at that. > Error: Unexpected section number; expected '1' or a subsection, found '= D. Eastlake, et al > [Page 1]' >=20 > 5) The references section is unnumbered. This (maybe)creates an error.= =20 >=20 > Error: Expected an Authors' Addresses section, found 'Normative Referen= ces=E2=80=99 Ok, will check. > Thank you in advance for your help! Sure :-) Best regards, Henrik --DRbSNJEixPD9LUCLCSom7iCtD6gpelbWh-- --p6ufxjb2SmpIQlutc1oS4Ou6jJM7736Ft Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZQBQdAAoJEE6bV0uPuxcaP3QQAKHVFQ7wbGN1wXdMLO+t2wX8 JjhcCkYmxoNAoIpl/dK2VnrvDA2oJ/FF8bsp+tz0WYJAM+DfcTl6YY5SaorBAzkn pt21MasTTsmX/pCa6hz8FeUqi/x+Ce7FIzWG7oXdkseZ5KC33Tp96BwLJg6bR68A M0gJZwdCaZWiEWjAPxQZr08CKrxcbQ5eTOTwPpUjsYuv+N9i4XdF/mYESF8AQai5 GcLpdTEo9DbHEvwc7xYkIwsPujngsQd9gCPSqhRiybP7FusT8kPWcpgAMz1sBtOp sQlzbgg+JuFliXFG7v8ujajubcjhGqFIRT8ei4Pumi9tPEQXf32R1OOr6kWRch3y UY5Vobv509h1kvpD05ntQPZT7m6e4gvEKyITyXPIfjTCl1A3rwrq1N95szbbouUF zyPYRKnl/KUObVTbhML5N/xyMv8NfTjc3PvcvnqskoaYif8WFujjd+vPWeuvdKLw 6og1WV+yZA5W5E2jpkECUjrDfkGRJWMe1Q6EbWXSSm0DnPxUIyIpK7N7RQgnLJRi 3FttGDR9/NgDG2KokxoWkWxW+/Y0t64cfykoKb6ennayUegw1vTst1d9+7pMSelw XbQtBgd5GxRk4WObQTSMKUmyJJZ89KbkBT1zLVTV1ig8OwPd9ufH4HuXQ8NypAZR DnTjCeVP2WXuMGMUV1BW =4u0U -----END PGP SIGNATURE----- --p6ufxjb2SmpIQlutc1oS4Ou6jJM7736Ft-- From nobody Fri Jun 16 09:54:33 2017 Return-Path: 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 ; 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 ; 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 ; 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 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Fri, 16 Jun 2017 09:54:33 -0700 Message-Id: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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:=20 >> = https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-me= chanisms-12v3.original=20 >> = https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-me= chanisms-12v3.txt >> = https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assist-me= chanisms-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. =20 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 = =20 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=20 - 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: and it also contains: An Ethernet Address Resolution Protocol A Reverse Address Resolution Protocol 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=92 Addresses section Ideally, the Addresses section would show the full organization name. Thank you. RFC Editor/mf From nobody Fri Jun 16 10:54:14 2017 Return-Path: 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 EBA1D12957F for ; Fri, 16 Jun 2017 10:54:12 -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] 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 sKbHHoHVH-Ft for ; Fri, 16 Jun 2017 10:54:09 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A982A129B48 for ; Fri, 16 Jun 2017 10:54:09 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:51472 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dLvRg-0001zg-8n; Fri, 16 Jun 2017 10:54:09 -0700 To: Megan Ferguson References: Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <557d6a64-92ef-4616-66c1-8e522e7c2dbd@levkowetz.com> Date: Fri, 16 Jun 2017 19:54:00 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="F1LqoWf3HNMTCAvPnlXNqBrJIhk7HW3pS" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-development@ietf.org, mferguson@amsl.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jun 2017 17:54:13 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --F1LqoWf3HNMTCAvPnlXNqBrJIhk7HW3pS Content-Type: multipart/mixed; boundary="JOotAxVTcnIb1QE5LF0FmgUuokNHgjET6"; protected-headers="v1" From: Henrik Levkowetz To: Megan Ferguson Cc: tools-development@ietf.org Message-ID: <557d6a64-92ef-4616-66c1-8e522e7c2dbd@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml References: In-Reply-To: --JOotAxVTcnIb1QE5LF0FmgUuokNHgjET6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Megan, On 2017-06-16 18:54, Megan Ferguson wrote: > Hi Henrik, >=20 > Revisiting this file using the new release (v1.0.1): >=20 >>> Input file: draft-ietf-trill-directory-assist-mechanisms-12 >>> Version: id2xml 1.0.0 >>> Issues: File not originally generated with XML >>> Files available:=20 >>> https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assi= st-mechanisms-12v3.original=20 >>> https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assi= st-mechanisms-12v3.txt >>> https://www.rfc-editor.org/rfc/v3test/draft-ietf-trill-directory-assi= st-mechanisms-12v3-rfcdiff.html >=20 > Note - we edited the file somewhat to combat the previously discussed i= ssues. >=20 > 1) There were a few reference oddities and follow-up questions: >=20 >=20 > a) The following are the work in progress (WiP) references that could n= ot parse. =20 >=20 > draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2237): Warning: F= ailed 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. >=20 > draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2252): Warning: F= ailed 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. >=20 > draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2256): Warning: F= ailed 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. >=20 > draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2260): Warning: F= ailed 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. >=20 > Some questions/notes: >=20 > The general format for WiP references should be: >=20 > [I-D.ietf-sidr-bgpsec-protocol] > Lepinski, M. and K. Sriram, "BGPsec Protocol = =20 > Specification", draft-ietf-sidr-bgpsec-protocol-20 (work > in progress), December 2016. >=20 > So we see that the first 4 references in the list above: >=20 > - are missing the date=20 > - have the draft string before the Work in Progress designation > - have draft strings that break across lines >=20 > We are curious which, or if all, of these things make parsing fail > and the empty reference to be included? None of them. I believe the patterns in place will catch all of those. In 1.0.0 there was no pattern to handle ', work in progress' rather than '(work in progress)', but I added that in 1.0.1. What is throwing the matching off is that in all cases above, all the non-ultimate names in the author list are given as 'A. Nonymous' instead of 'Nonymous, A'. > b) With regard to this reference warning: >=20 >=20 > draft-ietf-trill-directory-assist-mechanisms-12v3.txt(2264): Warning: F= ailed 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 >=20 > It seems that the colon instead of a comma is to blame. Once updated, = this parsed fine. That's lucky, in that case -- there really should be double quotes around= the title. Adding missing quotes around any title would be among the fir= st fixes to improve parsing. > c) It seems using a 3-digit RFC number is not handled well. >=20 > In the xml2rfc text output from the id2xml xml file, we see: >=20 > [RFC826] - Plummer, D., "An Ethernet Address Resolution Protocol", > RFC 826, November 1982. >=20 > [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: > > >=20 > and it also contains: >=20 > > An Ethernet Address Resolution Protocol > > >=20 > > >=20 >=20 > > A Reverse Address Resolution Protocol > > >=20 > > >=20 > > >=20 > > >=20 > > >=20 > > > Oops. Right. That's a bug. Will fix. >=20 >=20 > 2) List output variances. There are several areas where the lists in > this document did not translate well. Yes. Out of the 195 hours spent on id2xml so far, I would guess that alm= ost half has been spent on variations of list analysis and handling. Lists t= urned out to be difficult! >=20 > 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. >=20 > id2xml output: >=20 > 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: >=20 > 1. The PDSS field is 3 in the ESADI zero fragment from the server > for the relevant Data Label. >=20 > 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 >=20 > 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. Right. Clearly not optimal. I've not seen this issue, with the same list number repeated, but I think that if you insert blank lines in the original to make it more like the default list output, it should be parse= d better. > 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]. Ouch. That is going to be hard, particularly because of the non-standard= list markers (1) etc. I don't think I'm even going to try to make it handle this well. Adding blank lines and using 1. instead of (1) is probably the best approach, if you want this converted to something sensi= ble. > 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 >=20 > (1b) the IP address corresponding to the MAC address so > that RBridge can locally respond to a RARP [RFC903] native= > frame. >=20 > (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]. Right. Sorry, but I've discovered that this is really hard for a program= =2E I don't have suggestions beyond those given above, for this. > 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. >=20 > - 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. >=20 >=20 > D. Eastlake, et al [Page 41= ] >=20 > INTERNET-DRAFT TRILL: Directory Service Mechanism= s >=20 >=20 > 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. >=20 > - 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: Yup, the '-' is seen as a list bullet, but then the text doesn't have the= right following indentation. When I tested this document, I edited the indentation of the lines which follow the dash, and things were fine. >=20 >=20 > 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. >=20 >=20 >=20 > - Even if a TRILL switch will normally be operating with > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 >=20 > Thus, it is RECOMMENDED that all TRILL switches have a strategy > for dealing with the situation where they do not have complete >=20 >=20 >=20 > Eastlake, et al. Expires September 3, 2017 [Page 41= ] >=20 > Internet-Draft TRILL: Edge Directory Assist Mechanisms March 201= 7 >=20 >=20 > directory information. Examples are to send a Pull Directory > query or to revert to [RFC6325] behavior. >=20 >=20 >=20 > - If a TRILL switch receives a native frame X resulting in > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 > - >=20 >=20 > 3) Figure/table output >=20 > Original: > The 4-bit Flags field of the message header for an Update Message is > as follows: >=20 > +---+---+---+---+ > | F | P | N | R | > +---+---+---+---+ >=20 >=20 > id2xml output: >=20 > The 4-bit Flags field of the message header for an Update Message is > as follows: >=20 > +---+---+---+---+ > | F | P | N | R | > +---+---+---+---+ > +---+---+---+---+ Hmm. This is identified as a texttable, but since there's only the one row, things turn out wrong. I may be able to fix this. >=20 > Original: >=20 > Name Default Section Note Below > ------------------ ------- ------- ---------- >=20 > DirQueryTimeout 100 milliseconds 3.2.1 1 > DirQueryRetries 3 3.2.1 1 > DirGenQPriority 5 3.2.1 2 >=20 > DirRespMaxPriority 6 3.2.2.1 3 >=20 > DirUpdateDelay 50 milliseconds 3.3 > DirUpdatePriority 5 3.3.1 > DirUpdateTimeout 100 milliseconds 3.3.3 > DirUpdateRetries 3 3.3.3 >=20 > DirAckMaxPriority 5 3.3.2 4 >=20 > Note 1: Pull Directory Query client timeout waiting for response and > maximum number of retries >=20 >=20 > id2xml output: >=20 > Name Default Section Note Below > ------------------ ------- ------- ---------- >=20 > DirQueryTimeout 100 milliseconds 3.2.1 1 > DirQueryRetries 3 3.2.1 1 > DirGenQPriority 5 3.2.1 2 >=20 >=20 >=20 > DirRespMaxPriority 6 3.2.2.1 3 >=20 >=20 > DirUpdateDelay 50 milliseconds 3.3 > DirUpdatePriority 5 3.3.1 > DirUpdateTimeout 100 milliseconds 3.3.3 > DirUpdateRetries 3 3.3.3 >=20 >=20 >=20 > DirAckMaxPriority 5 3.3.2 4 >=20 >=20 > Note 1: Pull Directory Query client timeout waiting for response and > maximum number of retries I actually don't know for sure what this should be modelled as. Do you have a suggestion of how to handle this? >=20 > 4) Header vs. Authors=E2=80=99 Addresses section >=20 > Ideally, the Addresses section would show the full organization name. Yees, agreed. Could you send me an example of where it doesn't? Best regards, Henrik --JOotAxVTcnIb1QE5LF0FmgUuokNHgjET6-- --F1LqoWf3HNMTCAvPnlXNqBrJIhk7HW3pS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZRBs4AAoJEE6bV0uPuxcaaP4QALx98s5YIqekUIPI/6P+ZLNS uQCPnoMalSciErdbJoWxl0g53b9XEH4l82VtpWHOJeRj53VkF+fYQAFP+vUYRD1T rf00fL3Zfw0FE9KjXYQUt8iGK+sxAEuZwjQlDkbv4CoXT9ksPFYvbvsmXOOvvqyA v3Oq5ChPEHwLTeBTnQz851rDxgfbxnyQtlbyqbAgXiqntEBNIzvJ1AyaazWDTt0R YqV112RYHyQRujMkWD+MQI4QMV5ubxhGtXj2+9oykjNXHqNmJM1BAhLfTJ69QlFk 39dVSd+xCMahcV4PfXBaFMZ2Qo1V95S6kg9gsnqEf3+LrmkLrDTMO0jVzuTKIRTe 1LimZQxumhX5Yjt4BGHL9gvtIlJMaA8oWnqQJ662/vBx/zgd+pA9s8EuYaV+vIVF RANyfHuE54yjCvx+6kHzhYINCV5Jzvsd8cIg7KsWXGFB6lOSHpH4UqLvkNE60g0E muTdKYAwVDNHygxD4NoUR+puso5n0iIbMWZokR0Fj0eAUsyHKF7qKqQaUJNnPR+0 yZjCMaRHrGqdakVv54WfbWDrS3USEJq8FHIwl9BAvPy0wPiV2+mapv0P2lMefJ+O l2tMPSwKImZ0Fh6aTch7HEoYJ5tcEo8oBnbqaqjkj+EEkr0s9s/FNy4USyQ7F0NV fRrgrMMhNuHDWGxMi4QM =Esbf -----END PGP SIGNATURE----- --F1LqoWf3HNMTCAvPnlXNqBrJIhk7HW3pS-- From nobody Fri Jun 16 12:37:26 2017 Return-Path: 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 0E5E4131837 for ; Fri, 16 Jun 2017 12:37:25 -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] 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 igb3XXYQH6LP for ; Fri, 16 Jun 2017 12:37:23 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8266D131618 for ; Fri, 16 Jun 2017 12:37:23 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:53399 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dLx3a-0002vR-TA; Fri, 16 Jun 2017 12:37:23 -0700 To: Megan Ferguson References: <557d6a64-92ef-4616-66c1-8e522e7c2dbd@levkowetz.com> Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <134fdbc6-7a90-8d6e-1d6b-9a92ad20bcbb@levkowetz.com> Date: Fri, 16 Jun 2017 21:37:14 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <557d6a64-92ef-4616-66c1-8e522e7c2dbd@levkowetz.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6e83gjj2JpmqaG1hJSsSNG2UqIDrL3RsH" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-development@ietf.org, mferguson@amsl.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jun 2017 19:37:25 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6e83gjj2JpmqaG1hJSsSNG2UqIDrL3RsH Content-Type: multipart/mixed; boundary="Vu9vUqNohM2E0FJKS5MIQEWDe8TPCGVPU"; protected-headers="v1" From: Henrik Levkowetz To: Megan Ferguson Cc: tools-development@ietf.org Message-ID: <134fdbc6-7a90-8d6e-1d6b-9a92ad20bcbb@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml References: <557d6a64-92ef-4616-66c1-8e522e7c2dbd@levkowetz.com> In-Reply-To: <557d6a64-92ef-4616-66c1-8e522e7c2dbd@levkowetz.com> --Vu9vUqNohM2E0FJKS5MIQEWDe8TPCGVPU Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi again, Some more information on some particular points, below: On 2017-06-16 19:54, Henrik Levkowetz wrote: <> >> The XML file contains: >> >> >>=20 >> and it also contains: >>=20 >> >> An Ethernet Address Resolution Protocol >> >> ... >> >=20 > Oops. Right. That's a bug. Will fix. This is fixed in my sources, will be in 1.0.2 <> >>=20 >> 3) Figure/table output >>=20 >> Original: >> The 4-bit Flags field of the message header for an Update Message is= >> as follows: >>=20 >> +---+---+---+---+ >> | F | P | N | R | >> +---+---+---+---+ >>=20 >>=20 >> id2xml output: >>=20 >> The 4-bit Flags field of the message header for an Update Message is= >> as follows: >>=20 >> +---+---+---+---+ >> | F | P | N | R | >> +---+---+---+---+ >> +---+---+---+---+ >=20 > Hmm. This is identified as a texttable, but since there's only the one= > row, things turn out wrong. I may be able to fix this. This is also fixed in my sources now, and will be in 1.0.2 >> 4) Header vs. Authors=E2=80=99 Addresses section >>=20 >> Ideally, the Addresses section would show the full organization name. Ok, I see the issue, and will fix in 1.0.2 Best regards, Henrik --Vu9vUqNohM2E0FJKS5MIQEWDe8TPCGVPU-- --6e83gjj2JpmqaG1hJSsSNG2UqIDrL3RsH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZRDNqAAoJEE6bV0uPuxcazWwP+gIx0xzvAyWYKs/7yDKdlfq5 xSDCxdDUoLevcaxz/BXf6AsmPkLtHxTtb6qSKa0mcRcsmdfpKN7TLnysbpXLSQtY JSek+xGKsrMzuUTHwgp+rmwMMFlYf9xqnH3eOxV8lObvVswGGBF3jFNOHgNXJP8M uuMNlrmiY/AvHRVf+HtzAWBhJ380CEqTmSg5D2P48iZP5PX1i+wT5D0XCTizLeKA VKD7Gc/ktmvwe7TdlNoAURcb/swnpJT5xD4UbwMoKN7w6k+yo/+m2UypaJ2Ymrwn osCVwbCl1zN8E/3Alo+uBJJ/wySWifz+BfGtcwe1N4H0UIFNVFxWW2i+vRPnkP/y XDLZ+39h7C7aXM7mHKUqVJTMDU0Ds78BWxeu8i/8LrG9IwLODPHhsTED6MCxW19U e0/sATnxKTc3mNgQk9P46D5SdfdNY18xtzdFD6EROlTCZET8k6bQAYBBiuvHMAvF O7lV3mQlcGiDhDgCfMsUQhwTKMOBe3D2nFZHRuvPMnWiv+h7kNzQ/GY8fkXPuumN XPaTu75R5tfhIHC/vfMeReo6fn+OIXPCTD4eFvmILQVuH6if5vm9pJJ13gMTSPMf +DRBLCDfz7zBHOebBIG8+Pes1bX7isv7BRQXcNfMfGJOmz008APhVWrKRj243GmH wIeB04YBCbTK8G4CF45g =wSDU -----END PGP SIGNATURE----- --6e83gjj2JpmqaG1hJSsSNG2UqIDrL3RsH-- From nobody Mon Jun 19 08:21:28 2017 Return-Path: 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 F38D9128AFE for ; Mon, 19 Jun 2017 08:21:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.718 X-Spam-Level: X-Spam-Status: No, score=-2.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=Pa1nckfW; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dPlW/bfw 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 l9zvK-OPh-pF for ; Mon, 19 Jun 2017 08:21:24 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 230F9128C82 for ; Mon, 19 Jun 2017 08:21:20 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6C95120B91; Mon, 19 Jun 2017 11:21:19 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 19 Jun 2017 11:21:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=3iDA/KKtTasn34ONjf4s3jm71TFYH+XO2b8oE4bEg AM=; b=Pa1nckfWTm6x1BLPoxzaw19U9IFRdPE4ianDVii6GoLdY+h41gJ8QTh3o XcJrsB1rmj2YqbhAiKNS/dc8pXQ/hWN0xiXaCOAXJpsawK25xjyFarBryf6nHx7y BSR7d23dihUtSRXjzmO06oD4SsF2o0ttkjNkWMVFyl12VnU/x9LJXahICS8LZemn bacwoY34raRU7J8Awa8lKfhEsNzCGhqc6Uavhv/MbsTgwZSqRqwZBfmHjSS7DgIv UaXjJXQwkKtXdsj/LY+5tnggSjnZcZ0vnKhG3C7DbJebJ/JfgPjz2DQTeUHDC54h 1b31EVy6JNnIW6WW8O46eyWLNfmFw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=3iDA/KKtTasn34ONjf 4s3jm71TFYH+XO2b8oE4bEgAM=; b=dPlW/bfw3+dhr+S69zLwrcJYJ+gf11oYVb 1cQ5Pd9HOIGSD3R438VP9XKNU+fqZEZAZLq/jw9sCuqUnL3v82SUCJpQZeU9KgLr nPHaWn341J/ekCVLmEiD2TnLy6zdZIiXCXMY1eH38V15MnV9kj6TSronaPJzD2XN es2dkqG/b3bmh4Qo7O1JjPD+Zu/nb/yUK4KL1rdC832CNdu19VoHTiJSVngpSVMI G3GKyZVXCvouwYamBgI0Ntwmtf6xO7jGubRgoDHxRsBXgWIoYIStBnD864OkBM6R eqZpYuxD+2REuHpwhjOJwf+A7Dw7viiKNqokthlwbLrZ6cW5GMBw== X-ME-Sender: X-Sasl-enc: qKB0L+cj2gSohQXJV0GRiN4lj9FVor8Qz2/kyEkjFT0p 1497885678 Received: from [172.22.50.11] (unknown [62.232.206.186]) by mail.messagingengine.com (Postfix) with ESMTPA id B9ADF248B0; Mon, 19 Jun 2017 11:21:18 -0400 (EDT) Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary=Apple-Mail-2A25805C-D98F-4F71-A480-4110D0D8DBAA From: Alexey Melnikov Mime-Version: 1.0 (1.0) Message-Id: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> Date: Mon, 19 Jun 2017 16:44:45 +0100 To: Tools Development X-Mailer: iPad Mail (14F89) Archived-At: Subject: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 15:21:26 -0000 --Apple-Mail-2A25805C-D98F-4F71-A480-4110D0D8DBAA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I hope this would be easy to add. This just needs to be a URL. Begin forwarded message: > From: Martin Thomson > Date: 12 June 2017 at 16:41:01 BST > To: Alexey Melnikov > Subject: Field for drafts > > Please add a link to draft metadata so that we can point to the > github/source control for the draft. --Apple-Mail-2A25805C-D98F-4F71-A480-4110D0D8DBAA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
I hope this would be easy to add. This just needs to be a URL.

Begin forwarded message:

From: Martin Thomson <martin.thomson@gmail.com>
Date: 12 June 2017 at 16:41:01 BST
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Field for drafts

Please add a link to draft metadata so that we can point to the
github/source control for the draft.
--Apple-Mail-2A25805C-D98F-4F71-A480-4110D0D8DBAA-- From nobody Mon Jun 19 08:27:06 2017 Return-Path: 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 BC5B7131526 for ; Mon, 19 Jun 2017 08:26:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 RwVDfa1B6qWV for ; Mon, 19 Jun 2017 08:26:57 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64795128C83 for ; Mon, 19 Jun 2017 08:26:57 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BF180300448 for ; Mon, 19 Jun 2017 11:26:56 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id OrjDK6tZZqrp for ; Mon, 19 Jun 2017 11:26:55 -0400 (EDT) Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id D157D30009D; Mon, 19 Jun 2017 11:26:54 -0400 (EDT) From: Russ Housley Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_24130E37-406A-4F94-9E55-AF1A8A245B0C" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Mon, 19 Jun 2017 11:26:54 -0400 In-Reply-To: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> Cc: IETF Tools Development To: Alexey Melnikov , Martin Thomson References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 15:27:00 -0000 --Apple-Mail=_24130E37-406A-4F94-9E55-AF1A8A245B0C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Which metadata is of interest? Is it just the information at the top of = the doc page (see = https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for an = example)? Or, is som of the information that requires additional button = clicks also of interest? Russ > On Jun 19, 2017, at 11:44 AM, Alexey Melnikov = wrote: >=20 > I hope this would be easy to add. This just needs to be a URL. >=20 > Begin forwarded message: >=20 >> From: Martin Thomson > >> Date: 12 June 2017 at 16:41:01 BST >> To: Alexey Melnikov > >> Subject: Field for drafts >>=20 >> Please add a link to draft metadata so that we can point to the >> github/source control for the draft. --Apple-Mail=_24130E37-406A-4F94-9E55-AF1A8A245B0C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Which metadata is of interest?  Is it just the = information at the top of the doc page (see https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong= / for an example)?  Or, is som of the information that requires = additional button clicks also of interest?

Russ


On Jun 19, 2017, at 11:44 AM, = Alexey Melnikov <aamelnikov@fastmail.fm> wrote:

I hope this would be easy to add. This = just needs to be a URL.

Begin forwarded = message:

From: Martin Thomson <martin.thomson@gmail.com>
Date: 12 June 2017 at 16:41:01 BST
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Field for drafts

Please add a link to draft = metadata so that we can point to the
github/source control for the draft.

= --Apple-Mail=_24130E37-406A-4F94-9E55-AF1A8A245B0C-- From nobody Mon Jun 19 09:04:08 2017 Return-Path: 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 D6D3E131531 for ; Mon, 19 Jun 2017 09:04:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=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 j_2-TcNKbe8O for ; Mon, 19 Jun 2017 09:04:02 -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 9186B131541 for ; Mon, 19 Jun 2017 09:03:59 -0700 (PDT) Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v5JG3vUA042046 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 19 Jun 2017 11:03:58 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local To: tools-development@ietf.org, Alexey Melnikov References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> From: Robert Sparks Message-ID: <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> Date: Mon, 19 Jun 2017 11:03:57 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------4FB45BEA00A6B4CF1AFF7492" Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 16:04:05 -0000 This is a multi-part message in MIME format. --------------4FB45BEA00A6B4CF1AFF7492 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I think this is asking that we have a section like "Additional URLs" for documents the same as we have for groups. Am I missing the point? RjS On 6/19/17 10:26 AM, Russ Housley wrote: > Which metadata is of interest? Is it just the information at the top > of the doc page (see > https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for > an example)? Or, is som of the information that requires additional > button clicks also of interest? > > Russ > > >> On Jun 19, 2017, at 11:44 AM, Alexey Melnikov > > wrote: >> >> I hope this would be easy to add. This just needs to be a URL. >> >> Begin forwarded message: >> >>> *From:* Martin Thomson >> > >>> *Date:* 12 June 2017 at 16:41:01 BST >>> *To:* Alexey Melnikov >> > >>> *Subject:* *Field for drafts* >>> >>> Please add a link to draft metadata so that we can point to the >>> github/source control for the draft. > > > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development --------------4FB45BEA00A6B4CF1AFF7492 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit

I think this is asking that we have a section like "Additional URLs" for documents the same as we have for groups.

Am I missing the point?

RjS

On 6/19/17 10:26 AM, Russ Housley wrote:
Which metadata is of interest?  Is it just the information at the top of the doc page (see https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for an example)?  Or, is som of the information that requires additional button clicks also of interest?

Russ


On Jun 19, 2017, at 11:44 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:

I hope this would be easy to add. This just needs to be a URL.

Begin forwarded message:

From: Martin Thomson <martin.thomson@gmail.com>
Date: 12 June 2017 at 16:41:01 BST
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Field for drafts

Please add a link to draft metadata so that we can point to the
github/source control for the draft.



_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

--------------4FB45BEA00A6B4CF1AFF7492-- From nobody Mon Jun 19 09:16:21 2017 Return-Path: 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 147D8131549 for ; Mon, 19 Jun 2017 09:16:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 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, 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 RvSa_8nwE4-A for ; Mon, 19 Jun 2017 09:16:16 -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 5169D13154F for ; Mon, 19 Jun 2017 09:16:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 082731CA39A; Mon, 19 Jun 2017 09:16:01 -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 2E1X_nCQQ3hG; Mon, 19 Jun 2017 09:16:00 -0700 (PDT) Received: from sandygiozasmbp2.home (unknown [47.156.91.59]) by c8a.amsl.com (Postfix) with ESMTPSA id D33C31C362A; Mon, 19 Jun 2017 09:16:00 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Sandy Ginoza In-Reply-To: <134fdbc6-7a90-8d6e-1d6b-9a92ad20bcbb@levkowetz.com> Date: Mon, 19 Jun 2017 09:16:14 -0700 Cc: Megan Ferguson , tools-development@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <8158A447-3AE2-413F-8BF0-6EDA08B5B121@amsl.com> References: <557d6a64-92ef-4616-66c1-8e522e7c2dbd@levkowetz.com> <134fdbc6-7a90-8d6e-1d6b-9a92ad20bcbb@levkowetz.com> To: Henrik Levkowetz X-Mailer: Apple Mail (2.3273) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 16:16:20 -0000 Hi Henrik, Thanks for the quick response! We=E2=80=99ll test this again and let = you know if we run into any issues. Thanks, Sandy > On Jun 16, 2017, at 12:37 PM, Henrik Levkowetz = wrote: >=20 > Hi again, >=20 > Some more information on some particular points, below: >=20 > On 2017-06-16 19:54, Henrik Levkowetz wrote: >=20 > <> >=20 >>> The XML file contains: >>> >>> >>>=20 >>> and it also contains: >>>=20 >>> >>> An Ethernet Address Resolution Protocol >>> >>> ... >>> >>=20 >> Oops. Right. That's a bug. Will fix. >=20 > This is fixed in my sources, will be in 1.0.2 >=20 >=20 >=20 > <> >=20 >>>=20 >>> 3) Figure/table output >>>=20 >>> Original: >>> The 4-bit Flags field of the message header for an Update Message = is >>> as follows: >>>=20 >>> +---+---+---+---+ >>> | F | P | N | R | >>> +---+---+---+---+ >>>=20 >>>=20 >>> id2xml output: >>>=20 >>> The 4-bit Flags field of the message header for an Update Message = is >>> as follows: >>>=20 >>> +---+---+---+---+ >>> | F | P | N | R | >>> +---+---+---+---+ >>> +---+---+---+---+ >>=20 >> Hmm. This is identified as a texttable, but since there's only the = one >> row, things turn out wrong. I may be able to fix this. >=20 > This is also fixed in my sources now, and will be in 1.0.2 >=20 >=20 >>> 4) Header vs. Authors=E2=80=99 Addresses section >>>=20 >>> Ideally, the Addresses section would show the full organization = name. >=20 > Ok, I see the issue, and will fix in 1.0.2 >=20 >=20 > Best regards, >=20 > Henrik >=20 >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Mon Jun 19 09:19:45 2017 Return-Path: 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 97EE9131549 for ; Mon, 19 Jun 2017 09:19:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.953 X-Spam-Level: X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 oenVqM-61p9v for ; Mon, 19 Jun 2017 09:19:38 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DAC0131566 for ; Mon, 19 Jun 2017 09:18:52 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id F009620AFA for ; Mon, 19 Jun 2017 12:18:51 -0400 (EDT) Received: from web5 ([10.202.2.215]) by compute3.internal (MEProxy); Mon, 19 Jun 2017 12:18:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=goV4d+ Q7f+nUmhTeEXv0LR/uyy634LF0s5UvFgKlxuk=; b=ouLZ40Lv2BhBI+l0iQZ6ZZ yxdFw6QIiTrR85yubygQSYipjZj9GdVQxJRwu3C7+kFtPCst/Tu6UV5fnAN9n5nz hJUsqbVrTATRoYP8w2ImSr8o+mGbcAYynSja0NT0l9N/0HA8/ZlL1s77cAOs1F8P ORhYcvzo5BTruok9E7+dLpoROSy6OB2YEzVe7wWgaC5/A8OoUQ3hiVqcgc8TXfBh weLoRiq2SIiOMdVpp+PkKL6ZulKTuhUkHoDHxAsQuycaaUKiJwkv8dps3Gpdt8J9 01TJWWHyMfcVAhBDfhXwhCS7zWH17VgtJ4gv3o2kmHk7gVzj4iSSKxdeCLaWvCiw == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id B6E0B9E295; Mon, 19 Jun 2017 12:18:51 -0400 (EDT) Message-Id: <1497889131.565982.1014292056.35881489@webmail.messagingengine.com> From: Alexey Melnikov To: tools-development@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_14978891315659822" X-Mailer: MessagingEngine.com Webmail Interface - ajax-72841c42 In-Reply-To: <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> Date: Mon, 19 Jun 2017 17:18:51 +0100 References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 16:19:40 -0000 This is a multi-part message in MIME format. --_----------=_14978891315659822 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Mon, Jun 19, 2017, at 05:03 PM, Robert Sparks wrote: > I think this is asking that we have a section like "Additional URLs" > for documents the same as we have for groups.That is my understanding. It should be editable by WG Chairs/ADs/editors. > Am I missing the point? > > RjS > > > On 6/19/17 10:26 AM, Russ Housley wrote: >> Which metadata is of interest? Is it just the information at the top >> of the doc page (see >> https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for >> an example)? Or, is som of the information that requires additional >> button clicks also of interest?>> >> Russ >> >> >>> On Jun 19, 2017, at 11:44 AM, Alexey Melnikov >>> wrote:>>> >>> >>> I hope this would be easy to add. This just needs to be a URL. >>> >>> Begin forwarded message: >>> >>>> *From:* Martin Thomson >>>> *Date:* 12 June 2017 at 16:41:01 BST >>>> *To:* Alexey Melnikov >>>> *Subject:* *Field for drafts* >>>> >>>> Please add a link to draft metadata so that we can point to the >>>> github/source control for the draft. >> >> >> >> _______________________________________________ TOOLS-DEVELOPMENT >> mailing list TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development >>> > _________________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development --_----------=_14978891315659822 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
On Mon, Jun 19, 2017, at 05:03 PM, Robert Sparks wrote:

I think this is asking that we have a section like "Additional URLs" for documents the same as we have for groups.

That is my understanding. It should be editable by WG Chairs/ADs/editors.

Am I missing the point?

RjS


On 6/19/17 10:26 AM, Russ Housley wrote:
Which metadata is of interest?  Is it just the information at the top of the doc page (see https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for an example)?  Or, is som of the information that requires additional button clicks also of interest?

Russ


On Jun 19, 2017, at 11:44 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:


I hope this would be easy to add. This just needs to be a URL.

Begin forwarded message:

From: Martin Thomson <martin.thomson@gmail.com>
Date: 12 June 2017 at 16:41:01 BST
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Field for drafts

Please add a link to draft metadata so that we can point to the
github/source control for the draft.



_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

_______________________________________________
TOOLS-DEVELOPMENT mailing list

--_----------=_14978891315659822-- From nobody Mon Jun 19 10:24:47 2017 Return-Path: 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 A05601315B1 for ; Mon, 19 Jun 2017 10:24:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=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 dHKRhKhJX1Va for ; Mon, 19 Jun 2017 10:24:43 -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 867F51316DC for ; Mon, 19 Jun 2017 10:23:26 -0700 (PDT) Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v5JHNO2H054793 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 19 Jun 2017 12:23:25 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local To: tools-development@ietf.org References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> <1497889131.565982.1014292056.35881489@webmail.messagingengine.com> From: Robert Sparks Message-ID: <84f0cc23-fe52-21e4-efa1-bd8e2b5939f2@nostrum.com> Date: Mon, 19 Jun 2017 12:23:24 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <1497889131.565982.1014292056.35881489@webmail.messagingengine.com> Content-Type: multipart/alternative; boundary="------------AF4B576E92C807F7566241A4" Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 17:24:46 -0000 This is a multi-part message in MIME format. --------------AF4B576E92C807F7566241A4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 6/19/17 11:18 AM, Alexey Melnikov wrote: > On Mon, Jun 19, 2017, at 05:03 PM, Robert Sparks wrote: >> >> I think this is asking that we have a section like "Additional URLs" >> for documents the same as we have for groups. >> > That is my understanding. It should be editable by WG Chairs/ADs/editors. I'm not sure that editors should be in that set. Maybe for WG drafts, but for individual submissions, I expect it is too open. > >> Am I missing the point? >> >> RjS >> >> >> On 6/19/17 10:26 AM, Russ Housley wrote: >>> Which metadata is of interest? Is it just the information at the >>> top of the doc page (see >>> https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for >>> an example)? Or, is som of the information that requires additional >>> button clicks also of interest? >>> >>> Russ >>> >>> >>>> On Jun 19, 2017, at 11:44 AM, Alexey Melnikov >>>> > wrote: >>>> >>>> >>>> I hope this would be easy to add. This just needs to be a URL. >>>> >>>> Begin forwarded message: >>>> >>>>> *From:* Martin Thomson >>>> > >>>>> *Date:* 12 June 2017 at 16:41:01 BST >>>>> *To:* Alexey Melnikov >>>> > >>>>> *Subject:* *Field for drafts* >>>>> >>>>> Please add a link to draft metadata so that we can point to the >>>>> github/source control for the draft. >>> >>> >>> >>> _______________________________________________ >>> TOOLS-DEVELOPMENT mailing list >>> TOOLS-DEVELOPMENT@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-development >>> >> >> _________________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development > > > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development --------------AF4B576E92C807F7566241A4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit



On 6/19/17 11:18 AM, Alexey Melnikov wrote:
On Mon, Jun 19, 2017, at 05:03 PM, Robert Sparks wrote:

I think this is asking that we have a section like "Additional URLs" for documents the same as we have for groups.

That is my understanding. It should be editable by WG Chairs/ADs/editors.
I'm not sure that editors should be in that set. Maybe for WG drafts, but for individual submissions, I expect it is too open.

Am I missing the point?

RjS


On 6/19/17 10:26 AM, Russ Housley wrote:
Which metadata is of interest?  Is it just the information at the top of the doc page (see https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for an example)?  Or, is som of the information that requires additional button clicks also of interest?

Russ


On Jun 19, 2017, at 11:44 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:


I hope this would be easy to add. This just needs to be a URL.

Begin forwarded message:

From: Martin Thomson <martin.thomson@gmail.com>
Date: 12 June 2017 at 16:41:01 BST
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Field for drafts

Please add a link to draft metadata so that we can point to the
github/source control for the draft.



_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

_______________________________________________
TOOLS-DEVELOPMENT mailing list



_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

--------------AF4B576E92C807F7566241A4-- From nobody Mon Jun 19 10:37:23 2017 Return-Path: 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 A527D131610 for ; Mon, 19 Jun 2017 10:37:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.718 X-Spam-Level: X-Spam-Status: No, score=-2.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=f/ztxBzQ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=e7YvvF2p 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 65qZUGW1jq-j for ; Mon, 19 Jun 2017 10:37:19 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0633013154A for ; Mon, 19 Jun 2017 10:37:18 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 38B2420AF8; Mon, 19 Jun 2017 13:37:18 -0400 (EDT) Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Mon, 19 Jun 2017 13:37:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=xhFyQAJ0uPjyeakkS5Vll5Idg826p uoOTG1Y2jO4MMc=; b=f/ztxBzQY7EWe2k5HbyzmMRi/URcs7AS78pB1sWOSZM15 fB1nIirgMNF6PObynM56jM5I7PLmr3XYhfFt64ytPmWoVJOAe5jhf3rGUg+GhcVf IUOHlUo1jHPFVcuc3Vu1XJss70wrm29b5WRutp2ok5AQJwZzOvePYeGbiTtg/alJ 91Y3Jov9DBrN8XEi5NVsEx5X63a6S9LzVDBYDGxY+gZe/VqIb7pU0G2HkdIyXEa9 CYpL7IceFY3q16WCzjnlsmD3nrMXE6YZsBteyt6KAWuse95wMRwEpWGS/ttYlwm8 8Maq+eLNWOX4kZs2133F9PvbZZK8pDSJ+WZFtFuAw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=xhFyQA J0uPjyeakkS5Vll5Idg826puoOTG1Y2jO4MMc=; b=e7YvvF2pAtKyscEIio9UQL CyLkZ8KzXZCjXH02NeD2lRz/dzhQtcwL85W10nxqnP85bDrPbQCABjTuMU6RsL7d ny49Jq8qod5zgDXbRV3gPx4JhCze/0Bkjbd44Vc0m8XQIxR1zli1D3MuNwNvz9ec OJYvaYceIyl3V9i2xhXkkxtwXzejd6bbmEoVg1hxhzC82o4UmdZYfJJBZulZQbE3 otK5tKCS+1EKNE58Q5p203CXM58YUsH0toKgUPnWz48Tn/VDYaGsImpTAqWd/Q+R uBfVBQLLtmtam3VwLAWFLBBXoB1ZKpBvZ/nH0AVlJ835Y0GxBnAolF/fDWV2CEqw == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 15EFD9E249; Mon, 19 Jun 2017 13:37:18 -0400 (EDT) Message-Id: <1497893837.583084.1014380640.5774CCFB@webmail.messagingengine.com> From: Alexey Melnikov To: Robert Sparks , tools-development@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_14978938385830840" X-Mailer: MessagingEngine.com Webmail Interface - ajax-72841c42 In-Reply-To: <84f0cc23-fe52-21e4-efa1-bd8e2b5939f2@nostrum.com> References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> <1497889131.565982.1014292056.35881489@webmail.messagingengine.com> <84f0cc23-fe52-21e4-efa1-bd8e2b5939f2@nostrum.com> Date: Mon, 19 Jun 2017 18:37:17 +0100 Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 17:37:22 -0000 This is a multi-part message in MIME format. --_----------=_14978938385830840 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Hi Robert, On Mon, Jun 19, 2017, at 06:23 PM, Robert Sparks wrote: > On 6/19/17 11:18 AM, Alexey Melnikov wrote: >> On Mon, Jun 19, 2017, at 05:03 PM, Robert Sparks wrote: >>> I think this is asking that we have a section like "Additional URLs" >>> for documents the same as we have for groups.>> That is my understanding. It should be editable by WG >> Chairs/ADs/editors.> I'm not sure that editors should be in that set. Maybe for WG drafts, > but for individual submissions, I expect it is too open.This is a detail, but can you elaborate on your concern? Are you concerned about malicious URIs? For individual submissions it seems sensible that editors of the document can set/change the repository URI.For WGs, I think it is Ok to leave this ability to WG chairs and ADs, but I don't see much harm for allowing editors to do that. Best Regards, Alexey > >> >>> Am I missing the point? >>> >>> RjS >>> >>> >>> On 6/19/17 10:26 AM, Russ Housley wrote: >>>> Which metadata is of interest? Is it just the information at the >>>> top of the doc page (see >>>> https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ >>>> for an example)? Or, is som of the information that requires >>>> additional button clicks also of interest?>>>> >>>> Russ >>>> >>>> >>>>> On Jun 19, 2017, at 11:44 AM, Alexey Melnikov >>>>> wrote:>>>>> >>>>> >>>>> I hope this would be easy to add. This just needs to be a URL. >>>>> >>>>> Begin forwarded message: >>>>> >>>>>> *From:* Martin Thomson >>>>>> *Date:* 12 June 2017 at 16:41:01 BST >>>>>> *To:* Alexey Melnikov >>>>>> *Subject:* *Field for drafts* >>>>>> >>>>>> Please add a link to draft metadata so that we can point to the >>>>>> github/source control for the draft. >>>> >>>> >>>> >>>> _______________________________________________ TOOLS-DEVELOPMENT >>>> mailing list TOOLS-DEVELOPMENT@ietf.org >>>> https://www.ietf.org/mailman/listinfo/tools-development >>>>>>> >>> _________________________________________________ >>> TOOLS-DEVELOPMENT mailing list >>> TOOLS-DEVELOPMENT@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-development >> >> >> >> _______________________________________________ TOOLS-DEVELOPMENT >> mailing list TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development >>> > _________________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development --_----------=_14978938385830840 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
Hi Robert,

On Mon, Jun 19, 2017, at 06:23 PM, Robert Sparks wrote:

On 6/19/17 11:18 AM, Alexey Melnikov wrote:

On Mon, Jun 19, 2017, at 05:03 PM, Robert Sparks wrote:

I think this is asking that we have a section like "Additional URLs" for documents the same as we have for groups.

That is my understanding. It should be editable by WG Chairs/ADs/editors.
I'm not sure that editors should be in that set. Maybe for WG drafts, but for individual submissions, I expect it is too open.
This is a detail, but can you elaborate on your concern? Are you concerned about malicious URIs?

For individual submissions it seems sensible that editors of the document can set/change the repository URI.
For WGs, I think it is Ok to leave this ability to WG chairs and ADs, but I don't see much harm for allowing editors to do that.

Best Regards,
Alexey



Am I missing the point?

RjS


On 6/19/17 10:26 AM, Russ Housley wrote:
Which metadata is of interest?  Is it just the information at the top of the doc page (see https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for an example)?  Or, is som of the information that requires additional button clicks also of interest?

Russ


On Jun 19, 2017, at 11:44 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:


I hope this would be easy to add. This just needs to be a URL.

Begin forwarded message:

From: Martin Thomson <martin.thomson@gmail.com>
Date: 12 June 2017 at 16:41:01 BST
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Field for drafts

Please add a link to draft metadata so that we can point to the
github/source control for the draft.



_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

_______________________________________________
TOOLS-DEVELOPMENT mailing list



_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

_______________________________________________
TOOLS-DEVELOPMENT mailing list

--_----------=_14978938385830840-- From nobody Mon Jun 19 10:51:40 2017 Return-Path: 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 4AFAA131764 for ; Mon, 19 Jun 2017 10:51:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=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 EyZeJyhaiRbg for ; Mon, 19 Jun 2017 10:51:37 -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 69EEA13176A for ; Mon, 19 Jun 2017 10:51:36 -0700 (PDT) Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v5JHpXTr059409 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 19 Jun 2017 12:51:33 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local To: Alexey Melnikov , tools-development@ietf.org References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> <1497889131.565982.1014292056.35881489@webmail.messagingengine.com> <84f0cc23-fe52-21e4-efa1-bd8e2b5939f2@nostrum.com> <1497893837.583084.1014380640.5774CCFB@webmail.messagingengine.com> From: Robert Sparks Message-ID: Date: Mon, 19 Jun 2017 12:51:33 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <1497893837.583084.1014380640.5774CCFB@webmail.messagingengine.com> Content-Type: multipart/alternative; boundary="------------B4039F4204EABCF83449A041" Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 17:51:39 -0000 This is a multi-part message in MIME format. --------------B4039F4204EABCF83449A041 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 6/19/17 12:37 PM, Alexey Melnikov wrote: > Hi Robert, > > On Mon, Jun 19, 2017, at 06:23 PM, Robert Sparks wrote: >> >> On 6/19/17 11:18 AM, Alexey Melnikov wrote: >> >>> On Mon, Jun 19, 2017, at 05:03 PM, Robert Sparks wrote: >>>> >>>> I think this is asking that we have a section like "Additional >>>> URLs" for documents the same as we have for groups. >>>> >>> That is my understanding. It should be editable by WG >>> Chairs/ADs/editors. >> I'm not sure that editors should be in that set. Maybe for WG drafts, >> but for individual submissions, I expect it is too open. > This is a detail, but can you elaborate on your concern? Are you > concerned about malicious URIs? Yes, this is a place where someone can enter an arbitrary URI and and arbitrary bit of descriptive text into the datatracker. > > For individual submissions it seems sensible that editors of the > document can set/change the repository URI. > For WGs, I think it is Ok to leave this ability to WG chairs and ADs, > but I don't see much harm for allowing editors to do that. > > Best Regards, > Alexey > >> >>> >>>> Am I missing the point? >>>> >>>> RjS >>>> >>>> >>>> On 6/19/17 10:26 AM, Russ Housley wrote: >>>>> Which metadata is of interest? Is it just the information at the >>>>> top of the doc page (see >>>>> https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ >>>>> for an example)? Or, is som of the information that requires >>>>> additional button clicks also of interest? >>>>> >>>>> Russ >>>>> >>>>> >>>>>> On Jun 19, 2017, at 11:44 AM, Alexey Melnikov >>>>>> > wrote: >>>>>> >>>>>> >>>>>> I hope this would be easy to add. This just needs to be a URL. >>>>>> >>>>>> Begin forwarded message: >>>>>> >>>>>>> *From:* Martin Thomson >>>>>> > >>>>>>> *Date:* 12 June 2017 at 16:41:01 BST >>>>>>> *To:* Alexey Melnikov >>>>>> > >>>>>>> *Subject:* *Field for drafts* >>>>>>> >>>>>>> Please add a link to draft metadata so that we can point to the >>>>>>> github/source control for the draft. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> TOOLS-DEVELOPMENT mailing list >>>>> TOOLS-DEVELOPMENT@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/tools-development >>>>> >>>>> >>>> >>>> _________________________________________________ >>>> TOOLS-DEVELOPMENT mailing list >>>> TOOLS-DEVELOPMENT@ietf.org >>>> https://www.ietf.org/mailman/listinfo/tools-development >>> >>> >>> >>> _______________________________________________ >>> TOOLS-DEVELOPMENT mailing list >>> TOOLS-DEVELOPMENT@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-development >>> >> >> _________________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development > --------------B4039F4204EABCF83449A041 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit



On 6/19/17 12:37 PM, Alexey Melnikov wrote:
Hi Robert,

On Mon, Jun 19, 2017, at 06:23 PM, Robert Sparks wrote:

On 6/19/17 11:18 AM, Alexey Melnikov wrote:

On Mon, Jun 19, 2017, at 05:03 PM, Robert Sparks wrote:

I think this is asking that we have a section like "Additional URLs" for documents the same as we have for groups.

That is my understanding. It should be editable by WG Chairs/ADs/editors.
I'm not sure that editors should be in that set. Maybe for WG drafts, but for individual submissions, I expect it is too open.
This is a detail, but can you elaborate on your concern? Are you concerned about malicious URIs?
Yes, this is a place where someone can enter an arbitrary URI and and arbitrary bit of descriptive text into the datatracker.

For individual submissions it seems sensible that editors of the document can set/change the repository URI.
For WGs, I think it is Ok to leave this ability to WG chairs and ADs, but I don't see much harm for allowing editors to do that.

Best Regards,
Alexey



Am I missing the point?

RjS


On 6/19/17 10:26 AM, Russ Housley wrote:
Which metadata is of interest?  Is it just the information at the top of the doc page (see https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for an example)?  Or, is som of the information that requires additional button clicks also of interest?

Russ


On Jun 19, 2017, at 11:44 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:


I hope this would be easy to add. This just needs to be a URL.

Begin forwarded message:

From: Martin Thomson <martin.thomson@gmail.com>
Date: 12 June 2017 at 16:41:01 BST
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Field for drafts

Please add a link to draft metadata so that we can point to the
github/source control for the draft.



_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

_______________________________________________
TOOLS-DEVELOPMENT mailing list



_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

_______________________________________________
TOOLS-DEVELOPMENT mailing list


--------------B4039F4204EABCF83449A041-- From nobody Mon Jun 19 11:18:28 2017 Return-Path: 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 1A1871317C8 for ; Mon, 19 Jun 2017 11:18:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 TQiCpXRfvp_a for ; Mon, 19 Jun 2017 11:18:25 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F15A131589 for ; Mon, 19 Jun 2017 11:18:25 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:51977 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dN1Fo-0005ld-1x; Mon, 19 Jun 2017 11:18:24 -0700 To: Robert Sparks , tools-development@ietf.org, Alexey Melnikov References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> From: Henrik Levkowetz Message-ID: Date: Mon, 19 Jun 2017 20:18:15 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fhDsWD3QQgBOjVIbdAbe4om0hUAduXgPo" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: alexey.melnikov@isode.com, tools-development@ietf.org, rjsparks@nostrum.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 18:18:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fhDsWD3QQgBOjVIbdAbe4om0hUAduXgPo Content-Type: multipart/mixed; boundary="fq4dK5EQiP0atv7i2n8VPv0gSbvd7Iv2A"; protected-headers="v1" From: Henrik Levkowetz To: Robert Sparks , tools-development@ietf.org, Alexey Melnikov Message-ID: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> In-Reply-To: <6f4acf20-a774-ed39-2a18-af947d402d65@nostrum.com> --fq4dK5EQiP0atv7i2n8VPv0gSbvd7Iv2A Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2017-06-19 18:03, Robert Sparks wrote: > I think this is asking that we have a section like "Additional URLs" fo= r=20 > documents the same as we have for groups. >=20 > Am I missing the point? Sounds right to me. Adding this to the todo list for an upcoming release= =2E Henrik > RjS >=20 > On 6/19/17 10:26 AM, Russ Housley wrote: >> Which metadata is of interest? Is it just the information at the top = >> of the doc page (see=20 >> https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for=20 >> an example)? Or, is som of the information that requires additional=20 >> button clicks also of interest? >> >> Russ >> >> >>> On Jun 19, 2017, at 11:44 AM, Alexey Melnikov >> > wrote: >>> >>> I hope this would be easy to add. This just needs to be a URL. >>> >>> Begin forwarded message: >>> >>>> *From:* Martin Thomson >>> > >>>> *Date:* 12 June 2017 at 16:41:01 BST >>>> *To:* Alexey Melnikov >>> > >>>> *Subject:* *Field for drafts* >>>> >>>> Please add a link to draft metadata so that we can point to the >>>> github/source control for the draft. >> >> >> >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development >=20 >=20 >=20 >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development >=20 --fq4dK5EQiP0atv7i2n8VPv0gSbvd7Iv2A-- --fhDsWD3QQgBOjVIbdAbe4om0hUAduXgPo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZSBVnAAoJEE6bV0uPuxcaOJIQAK74PbClS0laNRfZP7ZBisjq 4CNtDShIAp5wzrGT715cSoBCOjSKR+JJieFAxjYKhDStjBjf11z0+2JMopXlysh8 /DO0aCCEuE8rqEggJ8LOHaL6/1sUZjQj8eqPRL2g9vsbsU7pH90BXei3zLoB/Sha Up0hAwnb3z0FiM5gEk6ukSOdtYwnCXjZoFM3wLnF29Wx0fDR4IhnVfP1GAv9WIlB bQarazeWqFys+//KWTb0vIhbtCAyCuQevmYY+TwCK3vBc17Qf4GG9Og9MSNk3xMJ B1D9SVn7HfqYB9dywFLmWYjX2Pjh15GwsadCwdXX0B30DqWSdMZ1MW7PIWk9OFoO U1J79usZDITlaJG9DNVZyp4BqHlWG4XI6fU5fAE0SNj9pmtAXvTBvOZx39jV3I7o Try0T/rpFwhF1p3ejxFKnNOTefVd56V8kDaJafVvb9tH4FYeqTwRLhw3sLcTPUJe B47TQhn+UfSQJU46mDH40F+QELDsn56WIbxcbRr0ZvQAI7IPd0n9NaBPZQWFw283 0jgPdZbvlmKCSRC9RF1vYcHt+OgjCmb315gSIeCEim65RKwKOkMszhB6/DjplLZ9 okdGaTBjiao9H4eUXom0zf3quXu9J6JxePNsLV7gKfYIlfgcdx4WXzl9lJsvGnZ1 kirROX9+ldQyv0a0SwyM =eWFI -----END PGP SIGNATURE----- --fhDsWD3QQgBOjVIbdAbe4om0hUAduXgPo-- From nobody Mon Jun 19 16:06:00 2017 Return-Path: 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 2A3161294E7 for ; Mon, 19 Jun 2017 16:05:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 vSuYMnQn0bMk for ; Mon, 19 Jun 2017 16:05:57 -0700 (PDT) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 17A151293DF for ; Mon, 19 Jun 2017 16:05:57 -0700 (PDT) Received: by mail-lf0-x22e.google.com with SMTP id m77so64244571lfe.0 for ; Mon, 19 Jun 2017 16:05:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fVNhJrDVKMHT6yfVDR9A4/rM0IOVu/aPrC/p0AW2Wv4=; b=f3NdbKbZ8eDlIYznIyRTSbxriKay5HF6l5wL7r+GJ7QbpSeusa1wo2iZgWUzo4BtPu IWTYt1l9ROgZTkpjGo9suaZOVqUSt0dq4rl7yiUKoIvJ7554pdtgeFFnrjHporAD7zPo yRN6Y/SH510UzIPWnmjHLQuhF9KLbAGoR41GQqnxixCiqmLm/+1aQ59FyisfBPD3JrTH RwMuCrqetvxYwvQJzSkVyrxl7rVqono3YOJKbFV0fVQROe/vRScQAJI/GW5JcVgUgt+k RkBBqQWeFe1+KeOiC9+pdF6meNBciYRounYKK9c9Gc1Xh2ETrOw4cmIfdYteEOqsNMpl N7Ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fVNhJrDVKMHT6yfVDR9A4/rM0IOVu/aPrC/p0AW2Wv4=; b=rILXkXN6kljt47GIPxlW4hZcbXRj29GrkPBJY9BIxwegarh/ucASr/yvTxdIyPXIXh OGrZs+FZIYQQYoqXmMjKgTTHymu30NQAqZfy7mQ/zKof1sz1NZ0+2xllpNv5lN8mvhp6 ZjfyQefTCvNxsDG0VWrGjZKTsWxvKAZko3VckBJ8kS5pZBMbUq1ZqvbdIuu0Lyc6uC3D 2nZuzClLCYQJQSRGyvsH+yvhmyTQwvmXNPBZyTcWIvbLWnGbtbfAb12nGsLwEVVqhGgB J9c6J3XfPpaiMpmoKLD/4lx64HSIZnTFAanCbNtgHF+LJoSXXWLqdblLUJmkQh8useIx dIow== X-Gm-Message-State: AKS2vOzcd/qiog54FxQbJreV9UeiWnH+Y71LTfh0URnL/0Ae+UQFwrhd wRp2dfiTQFnG2lkgTXVfp4tRqBXdIuJg X-Received: by 10.46.81.26 with SMTP id f26mr4833091ljb.33.1497913555185; Mon, 19 Jun 2017 16:05:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.78.17 with HTTP; Mon, 19 Jun 2017 16:05:54 -0700 (PDT) In-Reply-To: References: <5C23390E-386F-4DD5-B085-8875277F222D@fastmail.fm> From: Martin Thomson Date: Tue, 20 Jun 2017 09:05:54 +1000 Message-ID: To: Russ Housley Cc: Alexey Melnikov , IETF Tools Development Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Request for a datatracker change X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 23:05:59 -0000 It would be awesome if that page would link to https://github.com/martinthomson/postel-was-wrong I'm happy to provide that link in whatever way best suits, but ideally it would be automated or able to be automated (during draft submission, for instance). That's all. On 20 June 2017 at 01:26, Russ Housley wrote: > Which metadata is of interest? Is it just the information at the top of the > doc page (see > https://datatracker.ietf.org/doc/draft-thomson-postel-was-wrong/ for an > example)? Or, is som of the information that requires additional button > clicks also of interest? > > Russ > > > On Jun 19, 2017, at 11:44 AM, Alexey Melnikov > wrote: > > I hope this would be easy to add. This just needs to be a URL. > > Begin forwarded message: > > From: Martin Thomson > Date: 12 June 2017 at 16:41:01 BST > To: Alexey Melnikov > Subject: Field for drafts > > Please add a link to draft metadata so that we can point to the > github/source control for the draft. > > From nobody Fri Jun 23 18:41:38 2017 Return-Path: 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 D5A9F129B0A for ; Fri, 23 Jun 2017 18:41:36 -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 8Y9mWp4XnUzd for ; Fri, 23 Jun 2017 18:41:35 -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 1AB7112943C for ; Fri, 23 Jun 2017 18:41:35 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id AE77F1CA514; Fri, 23 Jun 2017 18:41:15 -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 2b1MctUKoj75; Fri, 23 Jun 2017 18:41:15 -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 81C0D1CA3B8; Fri, 23 Jun 2017 18:41:15 -0700 (PDT) From: Megan Ferguson Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Fri, 23 Jun 2017 18:41:34 -0700 Message-Id: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@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: Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 01:41:37 -0000 Hi Henrik, Input file: draft-ietf-bess-evpn-vpws-14 Version: id2xml 1.0.2 Issues: File not originally generated with XML, Copyright section title Files available:=20 = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.origi= nal=20 https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.txt = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3-rfcdi= ff.html Note - the last file is a diff highlighting the changes we made to the = original to attempt to parse,=20 not the output of xml2rfc (as we were not able to get an XML output) = based on your previous feedback. 1) On initial run, the main issue seemed to be the ToC; an XML file = could be created, but the ToC appeared as a=20 figure and all other text following was missing. We got the following error:=20 Parsing file draft-ietf-bess-evpn-vpws-14v3.xml ERROR: Unable to validate the XML document: = draft-ietf-bess-evpn-vpws-14v3.xml : Line 27: Element middle content does not follow the DTD, = expecting (section)+, got nothing. However, once we updated from "Copyright and License Notice" to just = "Copyright Notice=94, we got hung up on an error: Converting 'draft-ietf-bess-evpn-vpws-14v3.txt' draft-ietf-bess-evpn-vpws-14v3.txt(328): Warning: Unexpected title: = expected 'Table ...', found 'Figure 1: EVPN Layer 2 attributes extended community'. This = looks like a texttable that has been entered as a figure. The generated XML will = need adjustment. draft-ietf-bess-evpn-vpws-14v3.txt(602): Warning: Failed parsing a = reference: [I-D.ietf-evpn-overlay] Drake, J., "A Network Virtualization Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-07, (work in progress), December 2016. Failure converting draft-ietf-bess-evpn-vpws-14v3.txt:=20 Traceback (most recent call last): File "/usr/bin/id2xml", line 9, in load_entry_point('id2xml=3D=3D1.0.2', 'console_scripts', 'id2xml')() File "/usr/lib/python2.7/site-packages/id2xml/run.py", line 222, in = run xml =3D parser.parse_to_xml() File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 955, in = parse_to_xml doc =3D self.document() File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 981, in = document self.root.append(self.back()) File "", line 2, in back File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 559, in = dtrace ret =3D fn(self, *params,**kwargs) File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 2726, = in back self.read_authors_addresses() File "", line 2, in read_authors_addresses File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 559, in = dtrace ret =3D fn(self, *params,**kwargs) File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1710, = in read_authors_addresses assert not line or line.txt.strip() =3D=3D '=92 AssertionError Thank you. RFC Editor/mf From nobody Sat Jun 24 10:10:02 2017 Return-Path: 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 CDE4F127419 for ; Sat, 24 Jun 2017 10:10:00 -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] 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 2MNyM7WNdC3U for ; Sat, 24 Jun 2017 10:09:59 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C038C126CB6 for ; Sat, 24 Jun 2017 10:09:59 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:51361 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dOoZL-0005jk-AJ; Sat, 24 Jun 2017 10:09:59 -0700 To: Megan Ferguson References: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@amsl.com> Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <271d2299-013b-9238-a5d4-0f45d78b855f@levkowetz.com> Date: Sat, 24 Jun 2017 19:09:51 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@amsl.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="T2T4MrP5N1ISLMkTowtbAjiMV44fhQgp6" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-development@ietf.org, mferguson@amsl.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 17:10:01 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --T2T4MrP5N1ISLMkTowtbAjiMV44fhQgp6 Content-Type: multipart/mixed; boundary="3ia3T2F6wBIwOvtW92QrEiFJBKI2oOisQ"; protected-headers="v1" From: Henrik Levkowetz To: Megan Ferguson Cc: tools-development@ietf.org Message-ID: <271d2299-013b-9238-a5d4-0f45d78b855f@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml References: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@amsl.com> In-Reply-To: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@amsl.com> --3ia3T2F6wBIwOvtW92QrEiFJBKI2oOisQ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Megan, On 2017-06-24 03:41, Megan Ferguson wrote: > However, once we updated from "Copyright and License Notice" to just > "Copyright Notice=E2=80=9D, we got hung up on an error: Right. Fixed in my sources. The fix will be part of the next release. As a workaround till that is out, please insert a blank line in front of each the Email: lines in the Author's Addresses section. Thanks for the feedback :-) and best regards, Henrik --3ia3T2F6wBIwOvtW92QrEiFJBKI2oOisQ-- --T2T4MrP5N1ISLMkTowtbAjiMV44fhQgp6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZTpzfAAoJEE6bV0uPuxcaXmoQALEIE3SMnZnlf1vRrY9LMpcH Fk83CgS4syYJfGvTyTcVU/jm9HfRZ8fYcBTXBwEM1jam0fnP0A+xDIfzCZoOfYdb GzwQeYlSxsoed9HboYH9X7Wffxmn/SuYz1q/LVVS8VCVWPLObHq9bAjI2z++7zdG 1woBK66Zinjx2vccs1C8mNAbXwkRRDaBfEPVJBRr1xaLT+XajUyd5avu/J46Ddn5 mTYJExQWVaWdziGob3lVqG3Rh4Az3isx1uEfEI8tX6jyZbIomFYYMrJx3H75mb9i qb4ANCuKOlTgWyLHcN0uTV6sRhdmvSbLjLN+vC7tKhYcP8oDkWoFq0CgTwJa7L5P IRr/Q5hlJTTXQhs0Gd4CXlpLmEAz8wzbSNncBSZLFkNyUFKCbAtiW62KQj8ZocGm ohfCnueWwnyq7B8HOwvvVG2XLOad++CXOlbmlnUCEDRCGSMqXOJ/ftlbB8C1jm53 QVmiefHiB4UVechFpcsmbkyD1SRThVyFbBEhxKHdJW3pdyIXnQTedlk1sgwyvKe3 egqPlxQDmc89WMeM8giIlYlA7q0m0kWM0zyQ5hUc1CmEJBmDv/ROrHDOByZdogBT 4KKi/Av7/Oa19a+u6bHXJ4qvzL9jDeUtUZbUqcmbewJItyNKqFzcQaNQPO+DWxGq PQK3snLDgdig9PK/5IWt =LA5Y -----END PGP SIGNATURE----- --T2T4MrP5N1ISLMkTowtbAjiMV44fhQgp6-- From nobody Mon Jun 26 15:48:32 2017 Return-Path: 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 5AB9812702E for ; Mon, 26 Jun 2017 15:48: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 xl-kW0Ih6BlH for ; Mon, 26 Jun 2017 15:48:29 -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 229C71270A3 for ; Mon, 26 Jun 2017 15:48:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0E9B71CA55B; Mon, 26 Jun 2017 15:48:07 -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 yYsLO_yOSZAz; Mon, 26 Jun 2017 15:48:06 -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 CFF9F1CA554; Mon, 26 Jun 2017 15:48:06 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Megan Ferguson In-Reply-To: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@amsl.com> Date: Mon, 26 Jun 2017 15:48:27 -0700 Cc: tools-development@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <3698EF34-9661-413D-AC6B-3A0A8AF0BF56@amsl.com> References: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@amsl.com> To: henrik@levkowetz.com X-Mailer: Apple Mail (2.1878.6) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 22:48:31 -0000 Hi Henrik, Thank you for the workaround on this one. Here is the revisit: Input file: draft-ietf-bess-evpn-vpws-14 Version: id2xml 1.0.2 Issues: File not originally generated with XML, short title formation, = xrefs, indentation of lists, RFC reference entry Files available:=20 = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.origi= nal=20 https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.txt https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.xml = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3-rfcdi= ff.html 1) The =93short title=94 used in the running header seems like it = truncates the full title instead of=20 populating from the I-D running header? Original: VPWS support in EVPN=20 id2xml: Virtual Private Wire Service support in xml: <t><list style=3D"hanging" hangIndent=3D"-1"><t hangText=3D"Name">= Meaning <vspace blankLines=3D"0"/> <list style=3D"empty"><t> P If set to 1 in multihoming = single-active scenarios, it indicates that the advertising PE is the Primary PE. MUST be set to 1 for multihoming all-active scenarios by all active PE(s).</t> <t> B If set to 1 in multihoming single-active = scenarios, it indicates that the advertising PE is the Backup PE.</t> <t> C If set to 1, a Control word <xref = target=3D"RFC4448"/> MUST be present when sending EVPN packets to this PE. It is recommended to include the control word in the absence of Entropy = Label.</t> </list> </t> </list> </t> </list> </t> 4) The reference entry for RFC 6790 appears in its full form in the = References, while the rest appear as, e.g., &RFC4448;. <reference anchor=3D"RFC6790"><front> <title>The Use of Entropy Labels in MPLS Forwarding = Thank you. RFC Editor/mf On Jun 23, 2017, at 6:41 PM, Megan Ferguson wrote: > Hi Henrik, >=20 > Input file: draft-ietf-bess-evpn-vpws-14 > Version: id2xml 1.0.2 > Issues: File not originally generated with XML, Copyright section = title > Files available:=20 > = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.origi= nal=20 > = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.txt > = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3-rfcdi= ff.html >=20 > Note - the last file is a diff highlighting the changes we made to the = original to attempt to parse,=20 > not the output of xml2rfc (as we were not able to get an XML output) = based on your previous feedback. >=20 > 1) On initial run, the main issue seemed to be the ToC; an XML file = could be created, but the ToC appeared as a=20 > figure and all other text following was missing. >=20 > We got the following error:=20 >=20 > Parsing file draft-ietf-bess-evpn-vpws-14v3.xml > ERROR: Unable to validate the XML document: = draft-ietf-bess-evpn-vpws-14v3.xml > : Line 27: Element middle content does not follow the DTD, = expecting (section)+, got nothing. >=20 > However, once we updated from "Copyright and License Notice" to just = "Copyright Notice=94, we got hung up on an error: >=20 > Converting 'draft-ietf-bess-evpn-vpws-14v3.txt' >=20 > draft-ietf-bess-evpn-vpws-14v3.txt(328): Warning: Unexpected title: = expected 'Table ...', > found 'Figure 1: EVPN Layer 2 attributes extended community'. This = looks like a > texttable that has been entered as a figure. The generated XML will = need adjustment. >=20 > draft-ietf-bess-evpn-vpws-14v3.txt(602): Warning: Failed parsing a = reference: > [I-D.ietf-evpn-overlay] Drake, J., "A Network Virtualization > Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-07, > (work in progress), December 2016. > Failure converting draft-ietf-bess-evpn-vpws-14v3.txt:=20 > Traceback (most recent call last): > File "/usr/bin/id2xml", line 9, in > load_entry_point('id2xml=3D=3D1.0.2', 'console_scripts', = 'id2xml')() > File "/usr/lib/python2.7/site-packages/id2xml/run.py", line 222, in = run > xml =3D parser.parse_to_xml() > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 955, = in parse_to_xml > doc =3D self.document() > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 981, = in document > self.root.append(self.back()) > File "", line 2, in back > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 559, = in dtrace > ret =3D fn(self, *params,**kwargs) > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 2726, = in back > self.read_authors_addresses() > File "", line 2, in read_authors_addresses > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 559, = in dtrace > ret =3D fn(self, *params,**kwargs) > File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1710, = in read_authors_addresses > assert not line or line.txt.strip() =3D=3D '=92 > AssertionError >=20 >=20 > Thank you. >=20 > RFC Editor/mf >=20 From nobody Mon Jun 26 15:48:51 2017 Return-Path: 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 A655812702E for ; Mon, 26 Jun 2017 15:48:49 -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 K9_vS7zIIbek for ; Mon, 26 Jun 2017 15:48:47 -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 5A7F0126E3A for ; Mon, 26 Jun 2017 15:48:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 474451CA55C; Mon, 26 Jun 2017 15:48:25 -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 qPUUrOXKaFwf; Mon, 26 Jun 2017 15:48:25 -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 13FB71CA55B; Mon, 26 Jun 2017 15:48:25 -0700 (PDT) From: Megan Ferguson Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Mon, 26 Jun 2017 15:48:46 -0700 Message-Id: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 22:48:50 -0000 Hi Henrik, Input file: draft-ietf-bmwg-ipv6-tran-tech-benchmarking-08 Version: id2xml 1.0.2 Issues: File not originally generated with XML, table-to-figure, lists, = numbered sections after References Files available:=20 = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bmwg-ipv6-tran-tech-bench= marking-08v3.original = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bmwg-ipv6-tran-tech-bench= marking-08v3.txt = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bmwg-ipv6-tran-tech-bench= marking-08v3.xml = https://www.rfc-editor.org/rfc/v3test/draft-ietf-bmwg-ipv6-tran-tech-bench= marking-08v3-rfcdiff.html 1) The original includes a table that is turned into a figure (instead = of vice versa): Original: Table 1. IPv6 Transition Technologies Categories +---+--------------------+------------------------------------+ | | Generic category | IPv6 Transition Technology | +---+--------------------+------------------------------------+ | 1 | Dual-stack | Dual IP Layer Operations [RFC4213] | +---+--------------------+------------------------------------+ | 2 | Single translation | NAT64 [RFC6146], IVI [RFC6219] | +---+--------------------+------------------------------------+ | 3 | Double translation | 464XLAT [RFC6877], MAP-T [RFC7599] | +---+--------------------+------------------------------------+ | 4 | Encapsulation | DSLite[RFC6333], MAP-E [RFC7597] | | | | Lightweight 4over6 [RFC7596] | | | | 6RD [RFC5569], 6PE [RFC4798], 6VPE | | | | 6VPE [RFC4659] | +---+--------------------+------------------------------------+ id2xml output: Figure 1: IPv6 Transition Technologies Categories +---+--------------------+------------------------------------+ | | Generic category | IPv6 Transition Technology | +---+--------------------+------------------------------------+ | 1 | Dual-stack | Dual IP Layer Operations [RFC4213] | +---+--------------------+------------------------------------+ | 2 | Single translation | NAT64 [RFC6146], IVI [RFC6219] | +---+--------------------+------------------------------------+ | 3 | Double translation | 464XLAT [RFC6877], MAP-T [RFC7599] | +---+--------------------+------------------------------------+ | 4 | Encapsulation | DSLite[RFC6333], MAP-E [RFC7597] | | | | Lightweight 4over6 [RFC7596] | | | | 6RD [RFC5569], 6PE [RFC4798], 6VPE | | | | 6VPE [RFC4659] | +---+--------------------+=97=97=97=97=97=97=97=97=97=97=97=97=97=97= =97=97=97=97+ 2) FYI - It appears that the Acknowledgements section was removed =97 = probably because it appeared as=20 a numbered section after the references. 3) There is a bit of a spacing oddity after =93Throughput=94. This is = not highlighted in the diff. Original: 3. Terminology A number of terms used in this memo have been defined in other RFCs. Please refer to those RFCs for definitions, testing procedures and reporting formats. Throughput (Benchmark) - [RFC2544] Frame Loss Rate (Benchmark) - [RFC2544] Back-to-back Frames (Benchmark) - [RFC2544] System Recovery (Benchmark) - [RFC2544] Reset (Benchmark) - [RFC6201] Concurrent TCP Connection Capacity (Benchmark) - [RFC3511] Maximum TCP Connection Establishment Rate (Benchmark) - [RFC3511] id2xml output: 3. Terminology A number of terms used in this memo have been defined in other RFCs. Please refer to those RFCs for definitions, testing procedures and reporting formats. Throughput (Benchmark) - [RFC2544] Frame Loss Rate (Benchmark) - [RFC2544] Back-to-back Frames (Benchmark) - [RFC2544] System Recovery (Benchmark) - [RFC2544] Reset (Benchmark) - [RFC6201] Concurrent TCP Connection Capacity (Benchmark) - [RFC3511] Maximum TCP Connection Establishment Rate (Benchmark) - [RFC3511] 4) Numbering started up again with 1 instead of the expected 6: Original: The test traffic SHOULD follow the following steps. 1. Query for the AAAA record of a domain name (from client to DNS64 server) 2. Query for the AAAA record of the same domain name (from DNS64 server to authoritative DNS server) 3. Empty AAAA record answer (from authoritative DNS server to DNS64 server) 4. Query for the A record of the same domain name (from DNS64 server to authoritative DNS server) 5. Valid A record answer (from authoritative DNS server to DNS64 server) 6. Synthesized AAAA record answer (from DNS64 server to client) id2xml output: 1. Query for the AAAA record of a domain name (from client to DNS64 server) 2. Query for the AAAA record of the same domain name (from DNS64 server to authoritative DNS server) 3. Empty AAAA record answer (from authoritative DNS server to DNS64 server) 4. Query for the A record of the same domain name (from DNS64 server to authoritative DNS server) 5. Valid A record answer (from authoritative DNS server to DNS64 server) 1. Synthesized AAAA record answer (from DNS64 server to client) 5) This list is interesting as it would probably require the use of the = =93counter=94 mentioned at=20 https://xml2rfc.tools.ietf.org/xml2rfcFAQ.html#anchor23. It looks like id2xml turned it into artwork because there was no space = between the numbered item=20 and the following text. =20 If we update to add a space between the numbered item and the following = text, we get renumbering. =20 Not sure how id2xml could detect such a case. id2xml: Details and parameters: 1. Caching First, all the DNS queries MUST contain different domain names (or domain names MUST NOT be repeated before the cache of the DUT is exhausted). Then new tests MAY be executed with domain names, 20%, 40%, 60%, 80% and 100% of which are cached. We note that ensuring a record being cached requires repeating it both "late enough" after the first query to be already resolved and be present in the cache and "early enough" to be still present in the cache. 2. Existence of AAAA record First, all the DNS queries MUST contain domain names which do not have an AAAA record and have exactly one A record. xml: Details and parameters:
Thank you. RFC Editor/mf From nobody Thu Jun 29 12:49:34 2017 Return-Path: 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 56A84129B91 for ; Thu, 29 Jun 2017 12:49:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 aZ9Alg9x5eMw for ; Thu, 29 Jun 2017 12:49:29 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E269A129B8D for ; Thu, 29 Jun 2017 12:49:29 -0700 (PDT) Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:59334 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dQfRQ-0003uH-TC; Thu, 29 Jun 2017 12:49:29 -0700 To: Megan Ferguson References: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@amsl.com> <3698EF34-9661-413D-AC6B-3A0A8AF0BF56@amsl.com> Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <3197d002-e66a-3742-a76e-9ae630af9aec@levkowetz.com> Date: Thu, 29 Jun 2017 21:49:21 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <3698EF34-9661-413D-AC6B-3A0A8AF0BF56@amsl.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lMExmxSdvVhonnABWo54owbCXFDjswLpT" X-SA-Exim-Connect-IP: 79.136.43.30 X-SA-Exim-Rcpt-To: tools-development@ietf.org, mferguson@amsl.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2017 19:49:32 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --lMExmxSdvVhonnABWo54owbCXFDjswLpT Content-Type: multipart/mixed; boundary="d7vcHXudNU0wr49ELA8u0wxU8Hmaxaoml"; protected-headers="v1" From: Henrik Levkowetz To: Megan Ferguson Cc: tools-development@ietf.org Message-ID: <3197d002-e66a-3742-a76e-9ae630af9aec@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml References: <2C3D917A-27C3-43B1-BBCD-21E6D8552F79@amsl.com> <3698EF34-9661-413D-AC6B-3A0A8AF0BF56@amsl.com> In-Reply-To: <3698EF34-9661-413D-AC6B-3A0A8AF0BF56@amsl.com> --d7vcHXudNU0wr49ELA8u0wxU8Hmaxaoml Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Megan, On 2017-06-27 00:48, Megan Ferguson wrote: > Hi Henrik, >=20 > Thank you for the workaround on this one. Here is the revisit: >=20 > Input file: draft-ietf-bess-evpn-vpws-14 > Version: id2xml 1.0.2 > Issues: File not originally generated with XML, short title formation, = xrefs, indentation of lists, RFC reference entry > Files available:=20 > https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.or= iginal=20 > https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.tx= t > https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.xm= l > https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3-rf= cdiff.html >=20 > 1) The =E2=80=9Cshort title=E2=80=9D used in the running header seems l= ike it truncates the full title instead of=20 > populating from the I-D running header? >=20 > Original: > VPWS support in EVPN=20 >=20 > id2xml: > Virtual Private Wire Service support in Right. If no short title is recognized, the full title is truncated as needed. I've now improved the regular expression which permits recogniti= on of the format used in this draft. (The trouble was with the day of month= in the date in the header line). >=20 > xml: > Virtual Pri= vate Wire Service support=20 > in Ethernet VPN >=20 >=20 >=20 > 2) This document uses the lowercase =E2=80=9Cdefined in section x=E2=80= =9D vs. =E2=80=9Cdefined in Section x=E2=80=9D. These are not=20 > picked up as . Yees. I tried to accept lowercase 'section x' in the draft htmlization script some years ago, and that increased the incidence of false markup considerably. I can change this to accept also 'section' if you wish, but I would not advice doing so. Would you reflect on this, and let me know if I should change this or keep recognising only 'Section' ? >=20 >=20 > 3) This indentation is a bit different from the original. =20 >=20 > Original: > Name Meaning >=20 > P If set to 1 in multihoming single-active scenarios, it > indicates that the advertising PE is the Primary PE. > MUST be set to 1 for multihoming all-active scenarios by > all active PE(s). >=20 > B If set to 1 in multihoming single-active scenarios, it > indicates that the advertising PE is the Backup PE. >=20 > C If set to 1, a Control word [RFC4448] MUST be present > when sending EVPN packets to this PE. It is recommended to > include the control word in the absence of Entropy Label. Yes. This has the form of a list, but the 'P', 'B', and 'C' indications aren't recognized as list bullets, or item labels. I could replicate the text output by treating this as a figure instead, but that would make it harder for you to turn this into a list with style=3D'hanging' an= d the individual letters as hangText (which I think it should be marked up as. I'm wary of trying to actually recognize the single letters as hangText automatically, as I think it will lead to a lot of false list identifications elsewhere. >=20 > id2xml: >=20 > Name Meaning >=20 > P If set to 1 in multihoming single-active scenarios, it > indicates that the advertising PE is the Primary PE. MUST be > set to 1 for multihoming all-active scenarios by all active > PE(s). >=20 > B If set to 1 in multihoming single-active scenarios, it > indicates that the advertising PE is the Backup PE. >=20 > C If set to 1, a Control word [RFC4448] MUST be present when > sending EVPN packets to this PE. It is recommended to include= > the control word in the absence of Entropy Label. >=20 > xml: >=20 > > > Meaning > > P If set to 1 in multihoming single= -active scenarios, it > indicates that the advertising PE is the Primary PE. > MUST be set to 1 for multihoming all-active scenarios by > all active PE(s). >=20 > B If set to 1 in multihoming single-active scenarios, it > indicates that the advertising PE is the Backup PE. >=20 > C If set to 1, a Control word = MUST be present > when sending EVPN packets to this PE. It is recommended to > include the control word in the absence of Entropy Label. >=20 > > >=20 > > >=20 > > >=20 > 4) The reference entry for RFC 6790 appears in its full form in the Ref= erences, while the rest appear as, e.g., &RFC4448;. >=20 > > The Use of Entropy Labels in MPLS Forwarding > = > >=20 > > >=20 > > >=20 > > >=20 > > >=20 > > >=20 > Yes. It doesn't have any series info, which is what I've used as the tri= gger for recognizing RFCs and Internet-Drafts. I could look at the anchor tex= t if there is no series info, and try to do the right thing. Would you pre= fer that over manually adding the correct series info in the text version? Thank you for the feedback :-) Best regards, Henrik > Thank you. >=20 > RFC Editor/mf >=20 > On Jun 23, 2017, at 6:41 PM, Megan Ferguson wrote:= >=20 >> Hi Henrik, >>=20 >> Input file: draft-ietf-bess-evpn-vpws-14 >> Version: id2xml 1.0.2 >> Issues: File not originally generated with XML, Copyright section titl= e >> Files available:=20 >> https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.o= riginal=20 >> https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3.t= xt >> https://www.rfc-editor.org/rfc/v3test/draft-ietf-bess-evpn-vpws-14v3-r= fcdiff.html >>=20 >> Note - the last file is a diff highlighting the changes we made to the= original to attempt to parse,=20 >> not the output of xml2rfc (as we were not able to get an XML output) b= ased on your previous feedback. >>=20 >> 1) On initial run, the main issue seemed to be the ToC; an XML file co= uld be created, but the ToC appeared as a=20 >> figure and all other text following was missing. >>=20 >> We got the following error:=20 >>=20 >> Parsing file draft-ietf-bess-evpn-vpws-14v3.xml >> ERROR: Unable to validate the XML document: draft-ietf-bess-evpn-vpws-= 14v3.xml >> : Line 27: Element middle content does not follow the DTD, exp= ecting (section)+, got nothing. >>=20 >> However, once we updated from "Copyright and License Notice" to just "= Copyright Notice=E2=80=9D, we got hung up on an error: >>=20 >> Converting 'draft-ietf-bess-evpn-vpws-14v3.txt' >>=20 >> draft-ietf-bess-evpn-vpws-14v3.txt(328): Warning: Unexpected title: ex= pected 'Table ...', >> found 'Figure 1: EVPN Layer 2 attributes extended community'. This = looks like a >> texttable that has been entered as a figure. The generated XML will= need adjustment. >>=20 >> draft-ietf-bess-evpn-vpws-14v3.txt(602): Warning: Failed parsing a ref= erence: >> [I-D.ietf-evpn-overlay] Drake, J., "A Network Virtualization >> Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-07, >> (work in progress), December 2016. >> Failure converting draft-ietf-bess-evpn-vpws-14v3.txt:=20 >> Traceback (most recent call last): >> File "/usr/bin/id2xml", line 9, in >> load_entry_point('id2xml=3D=3D1.0.2', 'console_scripts', 'id2xml')(= ) >> File "/usr/lib/python2.7/site-packages/id2xml/run.py", line 222, in r= un >> xml =3D parser.parse_to_xml() >> File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 955, i= n parse_to_xml >> doc =3D self.document() >> File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 981, i= n document >> self.root.append(self.back()) >> File "", line 2, in back >> File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 559, i= n dtrace >> ret =3D fn(self, *params,**kwargs) >> File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 2726, = in back >> self.read_authors_addresses() >> File "", line 2, in read_authors_addresses >> File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 559, i= n dtrace >> ret =3D fn(self, *params,**kwargs) >> File "/usr/lib/python2.7/site-packages/id2xml/parser.py", line 1710, = in read_authors_addresses >> assert not line or line.txt.strip() =3D=3D '=E2=80=99 >> AssertionError >>=20 >>=20 >> Thank you. >>=20 >> RFC Editor/mf >>=20 >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development >=20 --d7vcHXudNU0wr49ELA8u0wxU8Hmaxaoml-- --lMExmxSdvVhonnABWo54owbCXFDjswLpT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZVVnBAAoJEE6bV0uPuxcakM8P/0T0j3J8jAHpVEBxxuiN02iz mSrUn3q5CdiF8pnnAvyOc9wgiCRTJJYdIc4L7jY2P+vHXTncobO+WIKkkYvcnEx/ /LvqHPvFUzL+bZGLSveU0yYhQYuEhXEu+vdNiep25+NlHK/YxuRT6KBNPcwXl6dD nPW8+uJfDLO1U22yzf1wPIXlaI0f35z8/AnMRk+jdtQ30GEpzsfSp3+Eq8Yk4dYi zA0qJE7UrnTp9ktwNP5fEqm+5OQKlSn6HHqu609b2O6RRrV+KNJiYjbUR7dbHqJt ORVPRrynuPSVKxc+hIjAAD0cYoWb33pfLLExKY1+Z86xd/r65MrWYAmuffQFxgPj AJfsIsOwYbZbvTNsFZD+OZRMTRKhbyFaOqZCntnovnjsEzXeyN+erpOvjgrjH5+s htLyfw5Q5oUqFbJ2Jh9pe7dt/mLV1kj8dWLgPsIwzJCtDh9sCzBu2F0xeQlnN9bO RIxRg4rRb0buEr6KukXa5nWTJreJzrcqyu5Tt7/A/7HUZj1bbTOnGvqJ6pkaXvbo +grbK0EdsNJeKo40iQjflAftD35CE3U5xAYtJqGeFZ0+njjK4FFJaoFDXIjMYcBi BYurVaUO+Uix+ci+/qAPhb9GCs4XpGnbnEJB3Lm9/pjkdv1Qz5maeWs+DbYB2qig qR40DC0doBwN6izYxdq8 =IqpN -----END PGP SIGNATURE----- --lMExmxSdvVhonnABWo54owbCXFDjswLpT--