<?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://comments.gmane.org/gmane.ietf.tools/1163"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1156"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1154"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1147"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1134"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1116"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1114"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1112"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1110"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1103"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1100"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1097"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1084"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1081"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1078"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1077"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1072"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1069"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1065"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.tools/1060"/>
      </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://comments.gmane.org/gmane.ietf.tools/1163">
    <title>internal software error (was: abnf extracting code?)</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1163</link>
    <description>Hi, repost, something is apparently broken again between the tools
list and Gmane... :-(

---------- Forwarded message ----------
From: Mail Delivery System &lt;MAILER-DAEMON&lt; at &gt;core3.amsl.com&gt;
Date: 2008/8/21
Subject: Undelivered Mail Returned to Sender
To: git-tools-discuss&lt; at &gt;m.gmane.org


This is the mail system at host core3.amsl.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                  The mail system

&lt;tools-discuss&lt; at &gt;core3.amsl.com&gt;: Command time limit exceeded:
   "/a/postconfirm/mailman post tools-discuss ietf.org"

Final-Recipient: rfc822; tools-discuss&lt; at &gt;core3.amsl.com
Original-Recipient: rfc822;tools-discuss&lt; at &gt;ietf.org
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; internal software error


---------- Forwarded message ----------
From: "Frank Elle</description>
    <dc:creator>Frank Ellermann</dc:creator>
    <dc:date>2008-08-22T02:51:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1156">
    <title>tools wg pages broken?</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1156</link>
    <description>I'm seeing the tools wg pages fail in a random fashion. For instance, if 
I access

I get the usual framing structure correctly, but the document frame 
contains just this:

"An error occurred at this point in the web-page generation. An error 
report has been sent to the webmaster. If this error isn't fixed within 
48 hours, please contact the web page author directly. "

However, curiously, this does not always happen. *Sometimes* I get the 
real thing.

Jari
</description>
    <dc:creator>Jari Arkko</dc:creator>
    <dc:date>2008-08-16T05:06:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1154">
    <title>abnf extracting code?</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1154</link>
    <description>Does anyone have some code that does a good job of extracting ABNF 
information from an RFC/I-D?

If we can find some code that does a decent job, an idea for 
tools.ietf.org would be

tools.ietf.org/abnf/RFC#

It would work just like tools.ietf.org/html/, but show the extracted 
ABNF code from the given RFC or I-D.

Tony Hansen
tony&lt; at &gt;att.com
</description>
    <dc:creator>Tony Hansen</dc:creator>
    <dc:date>2008-08-12T02:49:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1147">
    <title>Python code for extracting title from an RFC orDraft?</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1147</link>
    <description>Greetings again. I looked on the tools site and don't see any source 
code. I would love a tool that, given a draft or RFC, extracts the 
title from the top of the first page. (Extra points for pulling out 
the abstract). If I have to do it as "given the filename, look in 
1id-abstracts.txt or rfc-index.xml", that's fine, but I would like 
the code for that as well. No wheel-recreating, if not needed.

As a side note, it seems odd that the code y'all have created isn't 
on tools.ietf.org...

--Paul Hoffman, Director
--VPN Consortium
</description>
    <dc:creator>Paul Hoffman</dc:creator>
    <dc:date>2008-08-04T15:43:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1134">
    <title>IETF tools list issues (update)</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1134</link>
    <description>Hi, an updated list of issues from my POV:

* the RFC-I problem was fixed (= ietf.org unlisted),
  an update sent via GMaNe might be trapped in the
  moderation queue or in a meeting with Dave Null:
  &lt;http://article.gmane.org/gmane.discuss/11839&gt;

* various errata are still AWOL, for a complete list
  of 667 RFCs with reported errata as of 2008-07-08
  see &lt;g502oa$btu$1&lt; at &gt;ger.gmane.org&gt;, available in
  &lt;http://article.gmane.org/gmane.ietf.tools/1109&gt; 
  &lt;http://www.ietf.org/mail-archive/web/tools-discuss/current/msg01563.html&gt;

* the "challenge" wasn't identified as challenge by
  GMaNe, I'm not sure if that is a bug or a feature
  in practice.  Here is the "raw" challenge message:
  &lt;http://article.gmane.org/gmane.ietf.tools/1114/raw&gt;

  RFC 3834 issues in this "challenge":
  1 - The envelope sender address was the ordinary list
      address, the list bounce address might be better,
      see RFC 3834 chapter 3.3
  2 - There was no OPTIONAL (RFC 3834 chapter 3.1.8)
      Precedence: list (or similar) header</description>
    <dc:creator>Frank Ellermann</dc:creator>
    <dc:date>2008-07-19T18:47:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1116">
    <title>historic mailing list archives</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1116</link>
    <description>Hi,

the mailing list search engine I emailed about earlier (http://people.nokia.net/~lars/ietfsearch.html 
) only finds emails that are available in an HTML-ified archive  
(hypermail, mhonarc, pipermail, etc.)

Although most of our current mailing lists have such archives (esp.  
all the ones hosted on ietf.org), many historic working groups have  
archives that are only available in mbox format. If they are available  
at all - when I checked the screen scraped archive URLs on http://tools.ietf.org/wg/concluded 
  I was shocked how many are unvailable. It looks like we're in  
serious danger to loose some of our institutional memory.

So, I'm thinking about starting some concerted effort to collect and  
HTMLify the archives of historic IETF mailing lists. For example, I  
grabbed quite large number of them from http://gd.tuwien.ac.at/infosys/network/docs/ietf.org/concluded-wg-ietf-mail-archive/ 
, and I'm getting ready to convert them via mhonarc.

Questions:

   - do people think this is a worthwhile ef</description>
    <dc:creator>Lars Eggert</dc:creator>
    <dc:date>2008-07-18T08:18:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1114">
    <title>Confirm: tools-discuss&lt; at &gt;ietf.org:sP94UPSIBP7Q:FDBPoLtOgm-Owa1LJwzMrB62AE-3gq1dAIgsxA</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1114</link>
    <description>
Confirmation of list posting -- confirmation ID: sP94UPSIBP7Q

The ietf.org mailing-list server has received a list posting from 
git-tools-discuss&lt; at &gt;m.gmane.org to tools-discuss&lt; at &gt;ietf.org with the subject 
'Re: search engine for IETF mailing list archives'

As the sender address isn't subscribed to the list, and has not been
confirmed earlier, we have to request a confirmation of the address.
To confirm the address, send a message to tools-discuss&lt; at &gt;ietf.org,
with the same subject line as this message.

(Simply sending a 'reply' to this message should work from most email
interfaces, since that usually leaves the subject line in the right
form.  The reply's additional "Re:" is ok.)

If you do not wish your posting to the list to go through, simply
disregard this message.  Questions to postmaster&lt; at &gt;ietf.org.


</description>
    <dc:creator>tools-discuss&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2008-07-18T08:10:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1112">
    <title>Dublin code sprint?</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1112</link>
    <description>Hi,

I assume there will be a code sprint again in Dublin?

Lars
</description>
    <dc:creator>Lars Eggert</dc:creator>
    <dc:date>2008-07-16T14:24:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1110">
    <title>Incorrect Chair listed on IPPM page</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1110</link>
    <description>Hi Henrick and all,

I just noticed that the ippm wg page on the tools site
lists Guy Almes as chair! This was correct back in 1998
or so, but Guy hasn't been chair for a long time.

Henk and Matt are the current chairs.
:-)
Al
</description>
    <dc:creator>Al Morton</dc:creator>
    <dc:date>2008-07-15T19:48:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1103">
    <title>dailydose feed</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1103</link>
    <description>Hi, is anybody else using the dailydose feed ?
I'd prefer ?singlecolumn style URIs, compare
&lt;http://tools.ietf.org/dailydose/651.html&gt; vs.
&lt;http://tools.ietf.org/dailydose/651.html?singlecolumn&gt;

Of course a matter of taste, but when I want
the overdose I don't want the tools navbar.

Generally I like a decent link to a separate
page with all relevant links better than a
"navbar" wasting real estate in the browser
window and bandwidth, but that is obviously
a minority position, the whole WWW replaced
those pre-historic navframes by navbars. :-(

 Frank
</description>
    <dc:creator>Frank Ellermann</dc:creator>
    <dc:date>2008-06-21T08:49:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1100">
    <title>Errata</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1100</link>
    <description>Hi, the errata are not more in sync with the 
reported errata, is that as it should be ?

Examples:
&lt;http://tools.ietf.org/html/rfc3092&gt;, no link to
http://rfc-editor.org/errata_search.php?rfc=3092

&lt;http://tools.ietf.org/html/rfc3406&gt;, no link to
http://rfc-editor.org/errata_search.php?rfc=3406

 Frank
</description>
    <dc:creator>Frank Ellermann</dc:creator>
    <dc:date>2008-06-19T22:43:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1097">
    <title>ID Submission Tool: I-D Submitter Authentication</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1097</link>
    <description>Hi,

while submitting drafts this morning, it occurred to me that the current 
approach of authenticating the draft submission based on an HTTP GET 
request violates the GET safeness principle.

Any chance that this could be changed in the future to require a 
subsequent POST (via HTML form)?

BR, Julian
</description>
    <dc:creator>Julian Reschke</dc:creator>
    <dc:date>2008-06-17T08:59:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1084">
    <title>PDF conversion problem</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1084</link>
    <description>The txt to pdf conversion process has somehow failed for 
this draft:

http://tools.ietf.org/pdf/draft-ietf-pce-pcep-12.pdf

The txt version looks OK, so I can't immediately tell why
the PDF looks weird...

Best regards,
Pasi
</description>
    <dc:creator>Pasi.Eronen&lt; at &gt;nokia.com</dc:creator>
    <dc:date>2008-05-21T11:58:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1081">
    <title>Disconcerting behavior by rfcdiff</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1081</link>
    <description>I just ran rfcdiff (the web service version) on
draft-miyata-v6ops-trans-approach-00.txt and
draft-miyata-v6ops-trans-approach-01.txt

It apparently sees the second draft as an empty document. The reason
is that the draft starts thus:

Internet Engineering Task Force                                H. Miyata
Internet-Draft                                   Yokogawa Electric Corp.
Intended status: Informational                              May 14, 2007
Expires: October 24, 2008

It should be May 14, 2008 - when I patch that error, rfcdiff
works perfectly.

(Incidentally, idnits doesn't detect the 18 months expiry error, and the
ID submission process didn't either, but that's an issue for another list.)

    Brian
</description>
    <dc:creator>Brian E Carpenter</dc:creator>
    <dc:date>2008-05-21T03:04:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1078">
    <title>nits version  mismatch</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1078</link>
    <description>In a discussion of draft-ietf-l1vpn-basic-mode-04.txt for secdir, I 
reported that that the nit checker showed 7 nits.  Adrian Farrell said:


to which I replied:

   I looked at the page:
   http://www3.tools.ietf.org/wg/l1vpn/draft-ietf-l1vpn-basic-mode/
   which reports:


    2008-02-21 16:40 draft-ietf-l1vpn-basic-mode-04.txt
   [txt/plain]  [txt/pdf]  [nits]  [diff -from-03, wdiff, txt]
     (7 errors (**), 0 warnings (==), 0 comments (--).)

   Clicking on the nits link gets you to:
...


     ** Downref: Normative reference to an Unknown state RFC: RFC 3471

     ** Downref: Normative reference to an Unknown state RFC: RFC 3473

     ** Downref: Normative reference to an Unknown state RFC: RFC 3477

     ** Downref: Normative reference to an Unknown state RFC: RFC 4202

     ** Downref: Normative reference to an Unknown state RFC: RFC 4204

     ** Downref: Normative reference to an Unknown state RFC: RFC 4206

     ** Downref: Normative reference to an Unknown state RFC: RFC 4208


        Summary: </description>
    <dc:creator>Sandra Murphy</dc:creator>
    <dc:date>2008-05-15T21:02:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1077">
    <title>Text in RFC 3986 breaks RFC-HTML tool</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1077</link>
    <description>_______________________________________________
Tools-discuss mailing list
Tools-discuss&lt; at &gt;ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss
</description>
    <dc:creator>Jim Bell</dc:creator>
    <dc:date>2008-04-29T20:43:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1072">
    <title>xml version of 1id-abstracts.txt/1id-index.txt andall_id.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1072</link>
    <description>There was some discussion recently of having an xml version of the 
internet-drafts files 1id-*.txt and all_id.txt.

Moving this further along, I'd like to make concrete proposals for the 
schema for such files. First off, for 1id-abstract, the schema would be 
(I'm not an expert at DTDs, so forgive any errors here):

&lt;!ELEMENT internet-drafts (docs working-group-map)&gt;
   &lt;!ELEMENT docs (doc*)&gt;
     &lt;!ELEMENT doc (name, author, date, wg, file, abstract?)&gt;
       &lt;!ELEMENT name (#PCDATA)&gt;
       &lt;!ELEMENT author (#PCDATA)&gt;
       &lt;!ELEMENT date (#PCDATA)&gt;
       &lt;!ELEMENT wg (#PCDATA)&gt;
       &lt;!ELEMENT file (#PCDATA)&gt;
       &lt;!ELEMENT abstract (#PCDATA)&gt;
   &lt;!ELEMENT working-group-map (group*)&gt;
     &lt;!ELEMENT group (acronym, name)&gt;
       &lt;!ELEMENT acronym (#PCDATA)&gt;
       &lt;!ELEMENT name (#PCDATA)&gt;

Translation:
   &lt;internet-drafts&gt; contains &lt;docs&gt; and &lt;working-group-map&gt;
   &lt;docs&gt; contains 1 or more &lt;doc&gt;
   &lt;doc&gt; contains a &lt;name&gt;, &lt;author&gt;, &lt;date&gt;, &lt;wg&gt;, &lt;file&gt; and &lt;abstract&gt;
   The &lt;wg&gt; contains a workin</description>
    <dc:creator>Tony Hansen</dc:creator>
    <dc:date>2008-04-23T22:41:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1069">
    <title>I-D.ietf-eai-dsn</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1069</link>
    <description>Hi, &lt;http://tools.ietf.org/wg/eai/&gt; shows a tracker link for
&lt;http://tools.ietf.org/wg/eai/draft-ietf-eai-dsn/&gt;, but the
&lt;http://tools.ietf.org/html/draft-ietf-eai-dsn-06.txt&gt; page
doesn't.  

Trying to figure out what rfcmarkup does, this can't happen,
in &lt;http://tools.ietf.org/draft/draft-ietf-eai-dsn/now&gt; I
see a "docidnum", "docphase" doesn't begin with "ID-Exists":

Rfcmarkup 1.62 never run for this draft after the PubReq,
the old HTML page was apparently created by version 1.58.

Is the code calling rfcmarkup 1.62 also visible somewhere ?

 Frank
</description>
    <dc:creator>Frank Ellermann</dc:creator>
    <dc:date>2008-04-10T14:33:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1065">
    <title>rfc2xml alpha</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1065</link>
    <description>I recently got around to making something that takes RFC/I-D formatted
text and creates xml; with the help of Chris Newman. It is called
rfc2xml and it is available at
http://sourceforge.net/projects/rfc2xml/

It only creates the middle part of the I-D, and it doesn't do anything
fancy. But it does appear to get pretty good mileage.

I'd love it if interested IETF tools people could contribute and
ensure it is stable.

Please let me know how it works for you,

Ian Chakeres
</description>
    <dc:creator>Ian Chakeres</dc:creator>
    <dc:date>2008-03-27T11:12:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1060">
    <title>trac database locked</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1060</link>
    <description>trying to log into trac, I get:




--
Mark Nottingham     http://www.mnot.net/
</description>
    <dc:creator>Mark Nottingham</dc:creator>
    <dc:date>2008-03-25T11:24:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.tools/1049">
    <title>Request about the draft-xxx&lt; at &gt;tools.ietf.org maillists</title>
    <link>http://comments.gmane.org/gmane.ietf.tools/1049</link>
    <description>
I've been having problems where an author of a draft. say foo&lt; at &gt;bar.com,  
is not reading emails sent to draft-xxx email address. The issues  
seems to be that they are filtering in a way that expects foo&lt; at &gt;bar.com  
to be in the To or CC header. They point out that they did not know  
that needed to set up filters for every draft they write and don't  
want to do that.

I was wondering if we could do something like instead of setting the  
To line to draft-xxx, if we could set it to the list of authors and  
perhaps set the List-ID header to draft-xxx. I don't claim to have any  
idea of what email headers should be used in any given situation so I  
have no idea if this would make matters better or worse. But I think  
you see the problem I am getting at and perhaps someone knows if there  
is good way of resolving this.

Thanks, Cullen
</description>
    <dc:creator>Cullen Jennings</dc:creator>
    <dc:date>2008-03-22T16:29:51</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>
