<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.ietf.tools">
    <title>gmane.ietf.tools</title>
    <link>http://blog.gmane.org/gmane.ietf.tools</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1231"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1230"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1229"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1228"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1227"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1226"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1225"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1223"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1222"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1221"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1220"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1219"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1218"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1217"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1216"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1215"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1214"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1213"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1212"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.tools/1211"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1231">
    <title>i-d submission tool bug report</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1231</link>
    <description>(Bcc to ietf-action)

I would like to report a problem. A draft that has a long list of 
"Updates: " RFCs in the header will fail the metadata recognition 
process. Using XML2RFC, this works:

&lt;rfc ipr="full3978" docName="draft-arkko-arp-iana-rules-05" 
category="std" 
updates="826,951,1044,1329,2131,2132,2176,2225,2834,2835,3315,4338,4361,4701"&gt;

this does not:

&lt;rfc ipr="full3978" docName="draft-arkko-arp-iana-rules-05" 
category="std" updates="826, 951, 1044, 1329, 2131, 2132, 2176, 2225, 
2834, 2835, 3315, 4338, 4361, 4701"&gt;

That is, a header like this is not found well-formed, and the system 
complains about a missing date:

Network Working Group                                           J. Arkko
Internet-Draft                                                  Ericsson
Updates: 826, 951, 1044, 1329,                              C. Pignataro
2131, 2132, 2176, 2225, 2834,                              Cisco Systems
2835, 3315, 4338, 4361, 4701                            December 2, 2008
(if approved)
Intended status: Standards Track
Expires: June 5, 2009


  IANA Allocation Guidelines for the Address Resolution Protocol (ARP)
                     draft-arkko-arp-iana-rules-05

Status of this Memo

....
</description>
    <dc:creator>Jari Arkko</dc:creator>
    <dc:date>2008-12-01T22:09:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1230">
    <title>Re: Tools for displaying I-Ds and RFCs on ebookreaders</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1230</link>
    <description>
I just did some googling, and it appears that an XHTML document *can* be 
an epub document (didn't have the energy to look at the details). So you 
may want to test the XHTML variant that rfc2629.xslt can produce, for 
instance &lt;http://greenbytes.de/tech/webdav/rfc2616.xhtml&gt;.

BR, Julian
</description>
    <dc:creator>Julian Reschke</dc:creator>
    <dc:date>2008-11-26T16:27:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1229">
    <title>Re: Tools for displaying I-Ds and RFCs onebookreaders</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1229</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Julian Reschke wrote:

Have you tried (on a Windows box):

open in Wordpad
print to pdf
use calibre to convert pdf too .lrf/.epub

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkktdMYACgkQE5f5cImnZrthwwCg8od6xNZl8rhc2ArI6JmAL9ph
7OMAn3uXDV6RyoLsNu9G+Q3J3c+zRUai
=oD6x
-----END PGP SIGNATURE-----
</description>
    <dc:creator>Joe Touch</dc:creator>
    <dc:date>2008-11-26T16:09:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1228">
    <title>Re: Tools for displaying I-Ds and RFCs on ebookreaders</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1228</link>
    <description>
Out of curiosity: which kind of HTML did you try? As provided by 
tools.ietf.org/html, as produced by xml2rfc.tcl, produces by 
rfc2629.xslt (example: &lt;http://greenbytes.de/tech/webdav/rfc2616.html&gt;)?

BR, Julian
</description>
    <dc:creator>Julian Reschke</dc:creator>
    <dc:date>2008-11-26T13:51:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1227">
    <title>Re: extracting mail addresses (Was: [Fwd: Mail delivery failed: returning message to sender])</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1227</link>
    <description>Hi Stephen,

On 2008-11-25 18:44 Stephen Farrell said the following:

I think I've traced down the source of this, and a fix should
be forthcoming.

Thanks for reporting it :-)


Henrik
</description>
    <dc:creator>Henrik Levkowetz</dc:creator>
    <dc:date>2008-11-26T13:33:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1226">
    <title>Re: Replaced-by information</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1226</link>
    <description>
On 26 nov 2008, at 12.56, Henrik Levkowetz wrote:


Thanks!

    paf
</description>
    <dc:creator>Patrik Fältström</dc:creator>
    <dc:date>2008-11-26T12:19:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1225">
    <title>Tools for displaying I-Ds and RFCs on ebook readers</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1225</link>
    <description>Does anyone know of tools which can format RFCs and I-Ds to be easily
readable on ebook readers? I am specifically looking for something that
worlks for the sony e-reader. This displays text, but the screen is not
as wide as the rfc, and so lines get wrapped and the documents are a
real mess. PDFs are no better. The native formats for the platform are
sony's .lrf, and .epub. There are tools (calibre, for example) which
convert html, pdf etc to these formats, but nothing works well with the
specifics of rfcs. In the end, something xml-based seems most sensible.
Any ideas gratefully received
Howard Green
</description>
    <dc:creator>Howard Green</dc:creator>
    <dc:date>2008-11-24T21:38:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1223">
    <title>Re: Replaced-by information</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1223</link>
    <description>

On 2008-11-26 11:46 Henrik Levkowetz said the following:
...

The reason this relationship wasn't generated for the tools pages is that
there is an additional test for validity of the relationship which ensures
that the replaced draft is older than the replacement; however in the case
above, the draft-ietf-idnabis-tables-00.txt is missing from the draft
repository, so the file date test fails.

I've now scrounged a copy of the -00 draft from 
  http://stupid.domain.name/ietf/draft-ietf-idnabis-tables-00.txt .

The replaced-by relationship for this particular draft should be synthesized
correctly now, and the status page for idnabis should show the relationship.



Henrik
</description>
    <dc:creator>Henrik Levkowetz</dc:creator>
    <dc:date>2008-11-26T11:56:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1222">
    <title>Re: Replaced-by information</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1222</link>
    <description>

On 2008-11-26 08:20 Lars Eggert said the following:


Hmm.  This is still odd, because even if the replaced-by relationships
aren't in the official database, I synthetize replaced-by relationships
for the WG pages in a manner very similar to what Lars' script does, and
the drafts in relationship 

  draft-faltstrom-idnabis-tables REPLACED BY draft-ietf-idnabis-tables

has names which should make this replacement appear in the tools pages...


Investigating.



Henrik
</description>
    <dc:creator>Henrik Levkowetz</dc:creator>
    <dc:date>2008-11-26T10:46:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1221">
    <title>Re: Replaced-by information</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1221</link>
    <description>

This would be even better, but it obviously requires that we have 
the authentication+authorization system deployed and working...

Since I came late to the code sprint on Saturday, I didn't see
this part of the code -- how ready is it?

(Once it's deployed and working, there are some IESG-only pages 
that I could convert to Django, too...)

Best regards,
Pasi
</description>
    <dc:creator>Pasi.Eronen&lt; at &gt;nokia.com</dc:creator>
    <dc:date>2008-11-26T10:35:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1220">
    <title>Re: Replaced-by information</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1220</link>
    <description>Hi Pasi, all,

On 2008-11-26 07:54 Pasi.Eronen&lt; at &gt;nokia.com said the following:

Actually, what I had in mind in order to add this information manually
was to add a page where WG chairs could add the replaced-by information
for drafts related to their working groups to the IETF database directly;
obviating the need to run this through the secretariat.


And that's clearly desirable.


Best,

Henrik
</description>
    <dc:creator>Henrik Levkowetz</dc:creator>
    <dc:date>2008-11-26T10:23:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1219">
    <title>Re: Replaced-by information (was: Extendingcalendar features...and some other things)</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1219</link>
    <description>_______________________________________________
Tools-discuss mailing list
Tools-discuss&lt; at &gt;ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss
</description>
    <dc:creator>Lars Eggert</dc:creator>
    <dc:date>2008-11-26T07:20:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1218">
    <title>Re: Replaced-by information (was: Extendingcalendarfeatures...and some other things)</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1218</link>
    <description>

Ah, the link was missing some context -- it's the output from Lars's
script which tries to find (using file name heuristics) replaced-by
information that's *missing* from the database.

Or in other words: it's a reminder to WG chairs that they should
review their WG's part, and if the information is correct, ask the
secretariat to update the database (the script isn't always right, 
so manual review is needed).

Best regards,
Pasi
</description>
    <dc:creator>Pasi.Eronen&lt; at &gt;nokia.com</dc:creator>
    <dc:date>2008-11-26T07:18:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1217">
    <title>Re: Replaced-by information (was: Extendingcalendar features...and some other things)</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1217</link>
    <description>On 26 nov 2008, at 07.54, &lt;Pasi.Eronen&lt; at &gt;nokia.com&gt;  
&lt;Pasi.Eronen&lt; at &gt;nokia.com&gt; wrote:


But on this page I see:

draft-faltstrom-idnabis-tables REPLACED BY draft-ietf-idnabis-tables

This is though not reflected on the tools page for IDNABIS wg.

http://tools.ietf.org/wg/idnabis/

Foo?

    paf
</description>
    <dc:creator>Patrik Fältström</dc:creator>
    <dc:date>2008-11-26T06:57:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1216">
    <title>Re: Replaced-by information (was: Extendingcalendar features...and some other things)</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1216</link>
    <description>On 26 nov 2008, at 07.54, &lt;Pasi.Eronen&lt; at &gt;nokia.com&gt;  
&lt;Pasi.Eronen&lt; at &gt;nokia.com&gt; wrote:


Ok, thanks!

    paf
</description>
    <dc:creator>Patrik Fältström</dc:creator>
    <dc:date>2008-11-26T06:55:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1215">
    <title>Replaced-by information (was: Extending calendarfeatures...and some other things)</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1215</link>
    <description>

If you're going to manually add missing replaced-by information, the
best way to do it is emailing ietf-action&lt; at &gt;ietf.org; they'll add it to
the IETF database. I regularly do this for my WGs, based on reminders
the Lars sends out:

http://www.ietf.org/mail-archive/web/wgchairs/current/msg06375.html

This way, the information is visible in the official datatracker page
(not just tools.ietf.org), and gets used by various other tools (like
IPR disclosure search, Daily Dose of IETF, etc.).

Best regards,
Pasi
</description>
    <dc:creator>Pasi.Eronen&lt; at &gt;nokia.com</dc:creator>
    <dc:date>2008-11-26T06:54:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1214">
    <title>Re: Extending calendar features...and some otherthings</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1214</link>
    <description>

Let me take this up with ISOC and ICANN.

We need these calendar things I think.

    Patrik
</description>
    <dc:creator>Patrik Fältström</dc:creator>
    <dc:date>2008-11-24T14:34:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1213">
    <title>Documents etc on wg page (no longer discussionabout calendars)</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1213</link>
    <description>

Excellent.

I think I would like to be able to create:

- Relationships that the IETF database does not have
- Links to "related documents that do NOT have wg status", i.e. other  
I-D's
- Links to "other web pages that might be of interest"

With those, I would kill my page asap.

    Patrik
</description>
    <dc:creator>Patrik Fältström</dc:creator>
    <dc:date>2008-11-24T14:33:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1212">
    <title>Re: Extending calendar features...and some other things</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1212</link>
    <description>_______________________________________________
Tools-discuss mailing list
Tools-discuss&lt; at &gt;ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss
</description>
    <dc:creator>Henrik Levkowetz</dc:creator>
    <dc:date>2008-11-24T11:55:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1211">
    <title>Re: Extending calendar features...and some other things</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1211</link>
    <description>Resending...

On 2008-11-23 01:37 Patrik Fältström said the following:
...

The iCal feed is (as mentioned in my previous response) almost entirely
automatic, except for setting up the right timezone information and fixing
typos.


Agreed.


Yes.  But maybe the current tool is ripe for an update...


Henrik
</description>
    <dc:creator>Henrik Levkowetz</dc:creator>
    <dc:date>2008-11-24T11:53:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.tools/1210">
    <title>Re: Extending calendar features...and some other things</title>
    <link>http://permalink.gmane.org/gmane.ietf.tools/1210</link>
    <description>_______________________________________________
Tools-discuss mailing list
Tools-discuss&lt; at &gt;ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss
</description>
    <dc:creator>Henrik Levkowetz</dc:creator>
    <dc:date>2008-11-24T11:51:27</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.tools">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.tools</link>
  </textinput>
</rdf:RDF>
