Re: Mailing List Filters

Lars,

It's very simple for us to note your email address as an exception to this
rule, and we have done so now. In fact, because we realized that this might
be an issue for some community members, we created a form for people to let
us know if they had difficulty sending email, see here:
http://www.ietf.org/contactform.html (this is accessible from the
Secretariat contact area of the website)

Hopefully your problem should be resolved, but please let me know if you
experience any further difficulties.

Regards,
Alexa

On 10/1/08 1:28 PM, "Lars Eggert" <lars.eggert <at> nokia.com> wrote:

> On 2008-6-5, at 18:03, ext Alexa Morris wrote:
>> If you are curious to know what spam rules we are reinstating on Monday,
>> they are:
> ...
>> Rule B. This rule does a reverse lookup on the client's IP address, and
>> makes sure that we can identify it as being IN-REV'ed by someone.
> 
> FYI, this rule B has just bit me, because I don't have access to the
> reverse DNS zone of my IPv6 block, and I turned on IPv6 for sendmail.
> Is there some way around this?
> 
> (CC'ing the tools folks, because I think someone has hit the same
> issue recently.)

permission error in trac

I tried to set a default state for issues and got:

--
Mark Nottingham     http://www.mnot.net/

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

minor problem with dhc WG issues tracker

It seems the dhc WG issues tracker sends announcements to  
dhc <at> ietf.org, while the official mailing list for the dhc WG is dhcwg <at> ietf.org 
.

Is there a configuration knob I can use to fix that issue?

- Ralph

Nits (was: I-D ACTION:draft-ietf-avt-seed-srtp-04.txt)

<Internet-Drafts <at> ietf.org> wrote:

> Author(s) : I. Property
> Filename : draft-ietf-avt-seed-srtp-04.txt
> Pages : 12
> Date : 2008-9-4

Something for Bill or one of the famous code sprints...

> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-seed-srtp-04.txt

...still no link to the rfcmarkup version, but clearly
the five authors S. Yoon, J. Kim, H. Kim, H. Jeong,
and Y. Won don't include "I. Property" 

######################################################
Unrelated, I forgot to report it, in one of the last
daily overdoses two new "narrative minutes" went to
the same page.  Checking what's going on I found that
the source page got it wrong, three narrative minutes,
but only one link:

<http://www.ietf.org/IESG/iesg-narrative.shtml>

The two missing narrative minutes exist, but they did
not get their links on this page.

 Frank

draft name changes

just for the suggestion box, I'm sure it overfloweth...

for the IETF Documents tool, consider adding a link when a draft name 
changes (e.g. an individual draft is adopted as a working group item), 
similar to the link from a draft to its publication as an RFC.  It would 
be nice to see that 
http://tools.ietf.org/html/draft-vandevelde-v6ops-ra-guard-01 didn't 
just expire, but lived on as 
http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard-00 for example.

--

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz <at> sri.com 

internal software error (was: abnf extracting code?)

Hi, repost, something is apparently broken again between the tools
list and Gmane... 

---------- Forwarded message ----------
From: Mail Delivery System <MAILER-DAEMON <at> core3.amsl.com>
Date: 2008/8/21
Subject: Undelivered Mail Returned to Sender
To: git-tools-discuss <at> 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

<tools-discuss <at> core3.amsl.com>: Command time limit exceeded:
   "/a/postconfirm/mailman post tools-discuss ietf.org"

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

tools wg pages broken?

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

abnf extracting code?

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 <at> att.com

Python code for extracting title from an RFC or Draft?

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

Re: Errata

Hi Frank,

On 2008-07-08 16:59 Frank Ellermann said the following:

...
> Maybe something on your side lost the errata-urls,
> I add a complete list as of today (667 RFCs) below.
...

I believe I've fixed the problem on the tools servers,
and errata annotations should be correct again.  If you
notice any http://tools.ietf.org/html/rfcXXXX which doesn't
have an Errata link, but should have, please let me know.

Best,

	Henrik

IETF tools list issues (update)

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:
  <http://article.gmane.org/gmane.discuss/11839>

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

* 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:
  <http://article.gmane.org/gmane.ietf.tools/1114/raw>

  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 field
  3 - There was no RECOMMENDED (3.1.7) Auto-Submitted
      header field 
  4 - There were no RECOMMENDED (3.1.6) References and
      In-Reply-To header fields with the Message-ID of
      the challenged article, IMO that would be good
  5 - There was no OPTIONAL (3.1.5) Auto: subject tag