Re: [Tools-discuss] bounces from tools.ietf.org

Fred Baker <fred@cisco.com> Thu, 30 July 2009 11:39 UTC

Return-Path: <fred@cisco.com>
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A472D3A6950; Thu, 30 Jul 2009 04:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.132
X-Spam-Level:
X-Spam-Status: No, score=-110.132 tagged_above=-999 required=5 tests=[AWL=0.467, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqtpSb2Lgfa4; Thu, 30 Jul 2009 04:39:17 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id ED2253A6C60; Thu, 30 Jul 2009 04:38:43 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AncAAKojcUqQ/uCLe2dsb2JhbACBUpcGgTUWJAaeYYgnkCUFgiyBZYFO
X-IronPort-AV: E=Sophos;i="4.43,295,1246838400"; d="scan'208";a="46135883"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 30 Jul 2009 11:38:43 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6UBcfLt031965; Thu, 30 Jul 2009 13:38:41 +0200
Received: from dhcp-56c8.meeting.ietf.org (dhcp-10-61-102-132.cisco.com [10.61.102.132]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6UBcfPo005044; Thu, 30 Jul 2009 11:38:41 GMT
Message-Id: <C2C6908B-899B-48D8-BADC-D0EB2C406A05@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
In-Reply-To: <4A718384.1030107@levkowetz.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 30 Jul 2009 13:38:40 +0200
References: <7D36EA2D-F46D-4419-B536-A08D94417944@cisco.com> <4A718384.1030107@levkowetz.com>
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12111; t=1248953921; x=1249817921; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20[Tools-discuss]=20bounces=20from=20tool s.ietf.org |Sender:=20; bh=pwoHBvw4OpSCqX1fwrZSA/mFunlTWoPr3JQZ+10cKgg=; b=ofdsY+yrNSYjqhjQgRb3EPD3N9yEVcdwnHPbXDq+PCM1uK5p7RwQWzNyPu Eupq+Suk1Ys9S7V/xzIDcWwtOrWO1ZrjzbxOKDE1dAe0YEmpCbIqrWdTHTn1 LuvGWRaB/L;
Authentication-Results: ams-dkim-2; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: ietf-action@ietf.org, tools-discuss@ietf.org
Subject: Re: [Tools-discuss] bounces from tools.ietf.org
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2009 11:39:18 -0000

Thanks. Case closed.

On Jul 30, 2009, at 1:27 PM, Henrik Levkowetz wrote:

> Hi Fred,
>
> With the IETF website reorganization, the 1wg-summary.txt file
> (www.ietf.org/ietf/1wg-summary.txt) which lists the ADs and Chairs
> of the various WGs stopped being updated.  I discovered this
> yesterday, and switched over to an equivalent page which
> fortunately had been completed during the code sprint Saturday.
>
> Unfortunately, there were formatting differences between the old
> and new files, which caused the extraction of chair and AD information
> to the alias list to partially fail, which caused the delivery failure
> you forwarded.  I've fixed this now.
>
> Sorry for the service interruption.
>
>
> Regards,
>
> 	Henrik
>
>
> On 2009-07-30 11:37 Fred Baker said the following:
>> I must be missing something. Is tools.ietf.org offline?
>>
>> Begin forwarded message:
>>
>>> From: "Mail Delivery System" <MAILER-DAEMON@ams-iport-1.cisco.com>
>>> Date: July 30, 2009 11:35:17 AM GMT+02:00
>>> To: fred@cisco.com
>>> Subject: Delivery Status Notification (Failure)
>>>
>>> The following message to <v6ops-ads@tools.ietf.org> was  
>>> undeliverable.
>>> The reason for the problem:
>>> 5.1.0 - Unknown address error 550-'Unrouteable address'
>>> Reporting-MTA: dns; ams-iport-1.cisco.com
>>>
>>> Final-Recipient: rfc822;v6ops-ads@tools.ietf.org
>>> Action: failed
>>> Status: 5.0.0 (permanent failure)
>>> Remote-MTA: dns; [64.170.98.42]
>>> Diagnostic-Code: smtp; 5.1.0 - Unknown address error
>>> 550-'Unrouteable address' (delivery attempts: 0)
>>>
>>> From: Fred Baker <fred@cisco.com>
>>> Date: July 30, 2009 11:35:08 AM GMT+02:00
>>> To: Ralph Droms <rdroms@cisco.com>, draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org
>>> , draft-donley-ipv6-cpe-rtr-use-cases-and-reqs@tools.ietf.org, Jean-
>>> Francois Mule <jf.mule@cablelabs.com>, Barbara Stark
>>> <bs7652@att.com>, Ole Troan <ot@cisco.com>, Mark Townsley <townsley@cisco.com
>>>> , Kurt Erik Lindqvist <kurtis@kurtis.pp.se>, Heather Kirksey <hkirksey@motive.com
>>>>
>>> Cc: v6ops-ads@tools.ietf.org, 6man Chairs <6man-
>>> chairs@tools.ietf.org>, 6man-ads@tools.ietf.org
>>> Subject: Working out the CPE Router Draft or Drafts
>>>
>>>
>>> I'd like to arrange a webex session (Cisco gives me the use of that
>>> for free) to discuss the direction of the CPE router draft(s). The
>>> folks on the CC line are welcome but not a target audience; I really
>>> would like the authors, or at least the principal authors, involved.
>>>
>>> In the WG meeting, we discussed a "phase I" and a "phase II". In
>>> part, my purpose here is to come to an initial triage - what do we
>>> want in a phase I document (one that is non-controversial, answers
>>> at least some important questions, and can be advanced in November),
>>> and what (which may be a subset or superset of what remains) do we
>>> want in a phase II document? I also want to come to some simple
>>> agreements on the content of phase I - if we have things that are
>>> not well understood but can be quickly sorted out, let's do so.
>>>
>>> The author team I would like to have on the phase I draft includes
>>> one person from the present author team, one person from the Donley
>>> draft, and one person from BBF. From various discussions, this seems
>>> to come down to Wes Beebee, Chris Donley, and Ole Troan. Does anyone
>>> have heartburn with that? I would like a commitment from the members
>>> of the team to be present in Hiroshima and if necessary the meeting
>>> in Anaheim next spring. http://www.ietf.org/meeting/upcoming.html
>>>
>>> I understand that there is also some desire to have other drafts
>>> running in parallel, perhaps describing use cases. I'm open to that;
>>> I think we need to describe the most common use cases in an appendix
>>> or appendices in the draft, but see no reason to not have other
>>> documents describing other use cases. MY one request is that they be
>>> written with the knowledge of the author team and in such a manner
>>> that exposes requirements or gives practical guidance about how to
>>> use the CPE router that the WG document describes. I'll send those
>>> along not as working group drafts but as informational drafts
>>> friendly to the WG draft.
>>>
>>> My question is: what time works? Would you be so kind as to update http://doodle.com/ay9aax3xsru4q6t6
>>> with what works for you, and I will pick a time/date?
>>>
>>>
>> Begin forwarded message:
>>
>>> From: "Mail Delivery System" <MAILER-DAEMON@ams-iport-1.cisco.com>
>>> Date: July 30, 2009 11:35:17 AM GMT+02:00
>>> To: fred@cisco.com
>>> Subject: Delivery Status Notification (Failure)
>>>
>>> The following message to <6man-ads@tools.ietf.org> was  
>>> undeliverable.
>>> The reason for the problem:
>>> 5.1.0 - Unknown address error 550-'Unrouteable address'
>>> Reporting-MTA: dns; ams-iport-1.cisco.com
>>>
>>> Final-Recipient: rfc822;6man-ads@tools.ietf.org
>>> Action: failed
>>> Status: 5.0.0 (permanent failure)
>>> Remote-MTA: dns; [64.170.98.42]
>>> Diagnostic-Code: smtp; 5.1.0 - Unknown address error
>>> 550-'Unrouteable address' (delivery attempts: 0)
>>>
>>> From: Fred Baker <fred@cisco.com>
>>> Date: July 30, 2009 11:35:08 AM GMT+02:00
>>> To: Ralph Droms <rdroms@cisco.com>, draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org
>>> , draft-donley-ipv6-cpe-rtr-use-cases-and-reqs@tools.ietf.org, Jean-
>>> Francois Mule <jf.mule@cablelabs.com>, Barbara Stark
>>> <bs7652@att.com>, Ole Troan <ot@cisco.com>, Mark Townsley <townsley@cisco.com
>>>> , Kurt Erik Lindqvist <kurtis@kurtis.pp.se>, Heather Kirksey <hkirksey@motive.com
>>>>
>>> Cc: v6ops-ads@tools.ietf.org, 6man Chairs <6man-
>>> chairs@tools.ietf.org>, 6man-ads@tools.ietf.org
>>> Subject: Working out the CPE Router Draft or Drafts
>>>
>>>
>>> I'd like to arrange a webex session (Cisco gives me the use of that
>>> for free) to discuss the direction of the CPE router draft(s). The
>>> folks on the CC line are welcome but not a target audience; I really
>>> would like the authors, or at least the principal authors, involved.
>>>
>>> In the WG meeting, we discussed a "phase I" and a "phase II". In
>>> part, my purpose here is to come to an initial triage - what do we
>>> want in a phase I document (one that is non-controversial, answers
>>> at least some important questions, and can be advanced in November),
>>> and what (which may be a subset or superset of what remains) do we
>>> want in a phase II document? I also want to come to some simple
>>> agreements on the content of phase I - if we have things that are
>>> not well understood but can be quickly sorted out, let's do so.
>>>
>>> The author team I would like to have on the phase I draft includes
>>> one person from the present author team, one person from the Donley
>>> draft, and one person from BBF. From various discussions, this seems
>>> to come down to Wes Beebee, Chris Donley, and Ole Troan. Does anyone
>>> have heartburn with that? I would like a commitment from the members
>>> of the team to be present in Hiroshima and if necessary the meeting
>>> in Anaheim next spring. http://www.ietf.org/meeting/upcoming.html
>>>
>>> I understand that there is also some desire to have other drafts
>>> running in parallel, perhaps describing use cases. I'm open to that;
>>> I think we need to describe the most common use cases in an appendix
>>> or appendices in the draft, but see no reason to not have other
>>> documents describing other use cases. MY one request is that they be
>>> written with the knowledge of the author team and in such a manner
>>> that exposes requirements or gives practical guidance about how to
>>> use the CPE router that the WG document describes. I'll send those
>>> along not as working group drafts but as informational drafts
>>> friendly to the WG draft.
>>>
>>> My question is: what time works? Would you be so kind as to update http://doodle.com/ay9aax3xsru4q6t6
>>> with what works for you, and I will pick a time/date?
>>>
>>>
>> Begin forwarded message:
>>
>>> From: "Mail Delivery System" <MAILER-DAEMON@ams-iport-1.cisco.com>
>>> Date: July 30, 2009 11:35:17 AM GMT+02:00
>>> To: fred@cisco.com
>>> Subject: Delivery Status Notification (Failure)
>>>
>>> The following message to <6man-chairs@tools.ietf.org> was
>>> undeliverable.
>>> The reason for the problem:
>>> 5.1.0 - Unknown address error 550-'Unrouteable address'
>>> Reporting-MTA: dns; ams-iport-1.cisco.com
>>>
>>> Final-Recipient: rfc822;6man-chairs@tools.ietf.org
>>> Action: failed
>>> Status: 5.0.0 (permanent failure)
>>> Remote-MTA: dns; [64.170.98.42]
>>> Diagnostic-Code: smtp; 5.1.0 - Unknown address error
>>> 550-'Unrouteable address' (delivery attempts: 0)
>>>
>>> From: Fred Baker <fred@cisco.com>
>>> Date: July 30, 2009 11:35:08 AM GMT+02:00
>>> To: Ralph Droms <rdroms@cisco.com>, draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org
>>> , draft-donley-ipv6-cpe-rtr-use-cases-and-reqs@tools.ietf.org, Jean-
>>> Francois Mule <jf.mule@cablelabs.com>, Barbara Stark
>>> <bs7652@att.com>, Ole Troan <ot@cisco.com>, Mark Townsley <townsley@cisco.com
>>>> , Kurt Erik Lindqvist <kurtis@kurtis.pp.se>, Heather Kirksey <hkirksey@motive.com
>>>>
>>> Cc: v6ops-ads@tools.ietf.org, 6man Chairs <6man-
>>> chairs@tools.ietf.org>, 6man-ads@tools.ietf.org
>>> Subject: Working out the CPE Router Draft or Drafts
>>>
>>>
>>> I'd like to arrange a webex session (Cisco gives me the use of that
>>> for free) to discuss the direction of the CPE router draft(s). The
>>> folks on the CC line are welcome but not a target audience; I really
>>> would like the authors, or at least the principal authors, involved.
>>>
>>> In the WG meeting, we discussed a "phase I" and a "phase II". In
>>> part, my purpose here is to come to an initial triage - what do we
>>> want in a phase I document (one that is non-controversial, answers
>>> at least some important questions, and can be advanced in November),
>>> and what (which may be a subset or superset of what remains) do we
>>> want in a phase II document? I also want to come to some simple
>>> agreements on the content of phase I - if we have things that are
>>> not well understood but can be quickly sorted out, let's do so.
>>>
>>> The author team I would like to have on the phase I draft includes
>>> one person from the present author team, one person from the Donley
>>> draft, and one person from BBF. From various discussions, this seems
>>> to come down to Wes Beebee, Chris Donley, and Ole Troan. Does anyone
>>> have heartburn with that? I would like a commitment from the members
>>> of the team to be present in Hiroshima and if necessary the meeting
>>> in Anaheim next spring. http://www.ietf.org/meeting/upcoming.html
>>>
>>> I understand that there is also some desire to have other drafts
>>> running in parallel, perhaps describing use cases. I'm open to that;
>>> I think we need to describe the most common use cases in an appendix
>>> or appendices in the draft, but see no reason to not have other
>>> documents describing other use cases. MY one request is that they be
>>> written with the knowledge of the author team and in such a manner
>>> that exposes requirements or gives practical guidance about how to
>>> use the CPE router that the WG document describes. I'll send those
>>> along not as working group drafts but as informational drafts
>>> friendly to the WG draft.
>>>
>>> My question is: what time works? Would you be so kind as to update http://doodle.com/ay9aax3xsru4q6t6
>>> with what works for you, and I will pick a time/date?
>>>
>>>
>>
>> _______________________________________________
>> Tools-discuss mailing list
>> Tools-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss