Jouni Korhonen | 1 Apr 12:58 2014
Picon

tools pages and issue tracker

Dear tools team,

One thing happened recently on the Dime WG tools page. We had a huge 
number of issues on a document draft-docdt-dime-ovli that was a WG (by 
mistake) document´.. Now that the document is finally gone, all the 
issues put into that are also "gone". I can find the open issues from 
the issue tracker and would like to re-assign them to the proper 
document. However, the real WG document in question is not known to the 
issue tracker so I cannot do that. The document I refer here is 
draft-ietf-dime-ovli.

- Jouni

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Daniel Kahn Gillmor | 29 Mar 02:13 2014
Picon

id-submission workflow e-mails should use https for confirmation link and URL and Htmlized

Hi there--

it looks like the submission of a new draft via
https://datatracker.ietf.org/submit/ creates a confirmation e-mail with
a link in http://datatracker.ietf.org/submit/status/NNNN/confirm/HASH --
this should probably be https://, not http://

also, the new version notification that arrives after confirmation
contains three URLs (URL, Status, Htmlized), all of which could be
https, but two of which use http (URL, Htmlized).

I don't know where in the workflow these templates are stored, but if
they can be changed to use https instead, that would be great.

Thanks for doing all the work to get IETF web systems set up with https!
I'm sure there will be more of these legacy http:// URLs but i figure we
can just clean them up as we find them.

Regards,

	--dkg

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
(Continue reading)

Tony Hansen | 12 Mar 16:38 2014
Picon

xml.resource.org is getting wrong cert

Today when going to xml.resource.org, I'm getting the certificate for 
*.tools.ietf.org

     Tony Hansen

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

"Martin J. Dürst" | 10 Mar 09:34 2014
Picon

Obsoleted by links on tools.ietf.org/html/rfc...

Dear IETF tools experts,

Very recently, https://tools.ietf.org/html/rfc7158 was obsoleted after 
less than one day of existence by https://tools.ietf.org/html/rfc7159, 
because the publication date on the former was one year off.

The RFC Editor fortunately was careful enough to say that RFC 7159 not 
only obsoletes RFC 7158, but also RFC 4627. Unfortunately, the version 
of RFC 4627 at tools.ietf.org/html only has "Obsoleted by: 7158", which 
makes (attentive) readers click two links to get to RFC 7159. This may 
be the result of some kind of caching effect, or there may be some logic 
behind this, although in the case at hand, this logic would be suboptimal.

I hope this can be fixed. Ideally, RFC 4627 should only say
"Obsoleted by: 7159", because the obsoletion of RFC 4627 in RFC 7158 has 
been obsoleted by RFC 7159, and because that's the only information 
relevant to any readers except historians of RFC publication blunders.

Regards,    Martin.

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

(Continue reading)

Dale R. Worley | 3 Mar 21:01 2014

IDNITS checker fails

While I was trying to check the nits on an Internet-Draft, I ran into
a strange failure of the on-line IDNITS checker.

To see it work:
Copy draft-ietf-salud-alert-info-urns-11.txt into a file of that name.
Go to http://www.ietf.org/tools/idnits/.
Use Browse to find the file, click "Check file".
Result is a nits report on the file.

To see it fail:
Copy draft-ietf-salud-alert-info-urns-11.txt into a file named
draft-ietf-salud-alert-info-urns-11, that is, omitting the extension
".txt".
Go to http://www.ietf.org/tools/idnits/.
Use Browse to find the file, click "Check file".
Result is the IDNITS tool submission form, that is, no report or error
message at all.

(This is with Firefox 27.0 running on Linux.)

Dale

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
(Continue reading)

Stephan Dahlmann | 22 Feb 16:15 2014
Picon

RFC PDF generator creates blank sites

Hi,

I hope this is the right address for this:

The generator for the PDF files (e.g. for RFCs) seems to be broken.
Every second page is a blank page, except for the page number and author.

Examples:
http://tools.ietf.org/pdf/rfc4193.pdf
http://tools.ietf.org/pdf/rfc2460.pdf
http://tools.ietf.org/pdf/rfc7045.pdf

It seems to be broken for about a week now, I have a PDF of RFC 7045 
that does not have this problem (it has full pages).
This really makes quoting RFCs with page numbers difficult :)

Best Regards
Stephan Dahlmann

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Aamer Akhter (aakhter | 3 Mar 11:42 2014
Picon

xml2rfc gui tool and windows CR vs just LF

Hello,

I've been playing around with the xml2rfc tool under a windows environment. 

I've noticed that the txt output from the tool uses  \r\r\n at the end of a line rather than the simple \n that
the web service on xml.resource.org does. 

Is there a reason why we want to keep this difference? 

aa

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Aamer Akhter (aakhter | 1 Mar 03:32 2014
Picon

http://xml.resource.org/cgi-bin/xml2rfc.cgi unresponsive

Hi Folks,

The xml2rfc service at:
	http://xml.resource.org/cgi-bin/xml2rfc.cgi

seems to be unresponsive. 

1. Is there an alternative?

2. Any ideas on when it might come back? 

3. For the local run, I'm looking for an updated 
	http://xml.resource.org/public/rfc/bibxml3.zip	
but same problem w/ the website etc.

Thoughts? 

aa

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Daniel Kahn Gillmor | 25 Feb 18:15 2014
Picon

xml2rfc failing against lxml 3.3.1

hi IETF tools and LXML folks --

The IETF's xml2rfc tool (tested with versions 2.4.5 and 2.4.3) is
failing for me when used with python's lxml module version 3.3.1.
for example:

======================================================================
ERROR: test_header_footer (__main__.WriterDraftTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test.py", line 264, in setUp
    self.parse('tests/input/draft_root.xml')
  File "./test.py", line 222, in parse
    self.xmlrfc = self.parser.parse()
  File "/home/dkg/src/xml2rfc/xml2rfc/xml2rfc/parser.py", line 408, in parse
    context.resolvers.add(caching_resolver)
AttributeError: 'lxml.etree.iterparse' object has no attribute 'resolvers'

This was not a problem when i used lxml 3.2.0.

I haven't dived deep into lxml yet, but looking in the upstream
changelog at https://github.com/lxml/lxml/blob/master/CHANGES.txt, i
see:

  * The externally useless class ``lxml.etree._BaseParser`` was removed
    from the module dict.

and lxml.etree._BaseParser does have a "resolvers" attribute.

So if i'm interpreting this right, either lxml upstream was mistaken
(Continue reading)

Eggert, Lars | 24 Feb 10:27 2014
Picon

giving myself different roles in the local ietfdb dump

Hi,

how can I give myself additional datatracker roles (e.g., secretariat) in my local database dump? Would be
handy to check functionality when making code changes.

Thanks,
Lars
--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Martin Thomson | 21 Feb 01:35 2014
Picon

Missing obsoleted link

RFC 4244 is obsoleted by RFC 7044.  This is in the datatracker, but
it's not showing on http://tools.ietf.org/html/rfc4244

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org


Gmane