From glen@amsl.com Mon Nov 8 17:20:28 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE5493A691A; Mon, 8 Nov 2010 17:20:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Get7Fd3ZV5kr; Mon, 8 Nov 2010 17:20:27 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id DE8B83A689D; Mon, 8 Nov 2010 17:20:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id E9942E08C2; Mon, 8 Nov 2010 17:20:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7CAdijP5jQC7; Mon, 8 Nov 2010 17:20:50 -0800 (PST) Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id 9FA6BE076A; Mon, 8 Nov 2010 17:20:50 -0800 (PST) Message-ID: <4CD8A1EA.2050109@amsl.com> Date: Mon, 08 Nov 2010 17:20:42 -0800 From: Glen Barney Organization: AMS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Henrik Levkowetz , "codesprints@ietf.org" , tools-development@ietf.org, tools-team@ietf.org X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [TOOLS-DEVELOPMENT] Problem with I-D Announcements / Recent Datatracker Update X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 01:20:28 -0000 Tools Team - Please forgive the crossposting, but this is urgent. We are getting reports that I-D-Announcements are not going out correctly to the list. One complainant indicated that the MIME headers were going out malformed. Other evidence suggests that some digest readers are getting the digests, but individual list subscribers are getting no mail, or blank mail, or invalid mail. The old ID Submission Tool uses "NextPart" as a MIME boundary, which is obviously very bad... but it has been doing that for the past 3+ years with no problem. Mailman has also been correctly handling those things for several years, also with no problem. The only thing which has changed in the processing chain recently is that the Django Datatracker is now handling the processing of "Send Scheduled Announcements" via this cron job: */15 * * * * /a/www/ietf-datatracker/web/ietf/bin/send-scheduled-mail all We implemented that change during the upload blackout before the IETF meeting; all announcements since uploading reopened yesterday appear to be problematic. This is the reason I'm contacting these lists. If someone could have a look at this quickly, and determine what needs to be fixed, that would be very helpful. Thank you, Glen From glen@amsl.com Mon Nov 8 17:54:44 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E8C33A6928; Mon, 8 Nov 2010 17:54:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 0vcn5Cp7Vj7h; Mon, 8 Nov 2010 17:54:43 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id E8AB13A6898; Mon, 8 Nov 2010 17:54:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 45FFDE08C2; Mon, 8 Nov 2010 17:43:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEo3DWjrt8pe; Mon, 8 Nov 2010 17:43:51 -0800 (PST) Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id E8C93E0834; Mon, 8 Nov 2010 17:43:50 -0800 (PST) Message-ID: <4CD8A74E.8050609@amsl.com> Date: Mon, 08 Nov 2010 17:43:42 -0800 From: Glen Barney Organization: AMS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Henrik Levkowetz , "codesprints@ietf.org" , tools-development@ietf.org, tools-team@ietf.org X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [TOOLS-DEVELOPMENT] Details Re: Problem with I-D Announcements / Recent Datatracker Update X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 01:54:44 -0000 Further analysis shows that the I-D-Announcements, which are being sent through the datatracker, are having their Content-type header case-squashed. So the MIME boundary used by the current IDST is "NextPart". But the headers going out since we started using the datatracker sender are squashed to "nextpart". As a result, the NextPart boundaries are not being recognized, and the message is going out with incorrect formatting. More to follow! Glen From glen@amsl.com Mon Nov 8 17:57:27 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD6A63A68EF; Mon, 8 Nov 2010 17:57:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 fNvokZvrZK3W; Mon, 8 Nov 2010 17:57:27 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 2E8513A6862; Mon, 8 Nov 2010 17:57:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 4FCACE08C2; Mon, 8 Nov 2010 17:57:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I08Y+1EzgOFp; Mon, 8 Nov 2010 17:57:50 -0800 (PST) Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id F28B5E08C1; Mon, 8 Nov 2010 17:57:49 -0800 (PST) Message-ID: <4CD8AA95.3010409@amsl.com> Date: Mon, 08 Nov 2010 17:57:41 -0800 From: Glen Barney Organization: AMS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Henrik Levkowetz , "codesprints@ietf.org" , tools-development@ietf.org, tools-team@ietf.org References: <4CD8A74E.8050609@amsl.com> In-Reply-To: <4CD8A74E.8050609@amsl.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [TOOLS-DEVELOPMENT] [IETF] Re: Details Re: Problem with I-D Announcements / Recent Datatracker Update Update X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 01:57:28 -0000 Let's try that again, shall we? Thunderbird preselected the wrong address. On 11/8/2010 5:43 PM, Glen Barney wrote: > Further analysis shows that the I-D-Announcements, which are being sent > through the datatracker, are having their Content-type header case-squashed. As an emergency fix attempt, I have patched this file: ietf-datatracker/web/ietf/announcements/send_scheduled.py I am going to monitor the next transmissions to see if this fixes anything. More to follow, Glen From rdroms.ietf@gmail.com Fri Oct 29 09:07:14 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDC413A6405; Fri, 29 Oct 2010 09:07:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.479 X-Spam-Level: X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, 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 NA3lb9xWQxdW; Fri, 29 Oct 2010 09:07:13 -0700 (PDT) Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id EBF0F3A63C9; Fri, 29 Oct 2010 09:07:08 -0700 (PDT) Received: by gwb15 with SMTP id 15so2254024gwb.31 for ; Fri, 29 Oct 2010 09:09:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=bzOvjZn6J2oy9/79wpIptnf9S1fh/8EsPYCfJ1pluWI=; b=upKwfRKSwr3KQr0dgw2kU5FBZx05FnRxYoYWizZYlbsx/Eckj0UbPhu1SaPqguPQ/U ntKn0cCmAEdWRFYpPd4QD0x/4ZmML+IJHmVCjVifaj5evPHdTNQINGsdqhK9ycRVe0Hz oT5D0LgRjOcPxkWWZe4g1b2euBuvOau07gQ1M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=OcoWU+KVWzkt+n4WzNNUA83rfQCUvkcnm0+9m4/RkSTt5XlS2CpUyHX8qp/g3qImWR KMBc3JM+xytbAVVVsoS8pZJX74crHiF9tk1NSy/yb6+iRNfWhxo+3pMBLIB6sl1pgobz n3bpObmf1muNWq/NCrgYJuPvygu/egzHWKofM= Received: by 10.42.119.147 with SMTP id b19mr3953640icr.259.1288368542523; Fri, 29 Oct 2010 09:09:02 -0700 (PDT) Received: from bxb-rdroms-8712.cisco.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id p30sm891301vcf.2.2010.10.29.09.09.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 29 Oct 2010 09:09:01 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Ralph Droms In-Reply-To: <4CCAE766.2060603@piuha.net> Date: Fri, 29 Oct 2010 12:08:58 -0400 Content-Transfer-Encoding: 7bit Message-Id: <5BDDE902-6C0D-484E-B90C-80D3F8C58B26@gmail.com> References: <43E157B3-2E40-42BD-93B6-83017977120B@nostrum.com> <4CCAE766.2060603@piuha.net> To: Robert Sparks X-Mailer: Apple Mail (2.1081) X-Mailman-Approved-At: Mon, 08 Nov 2010 18:15:22 -0800 Cc: The IESG , Jari Arkko , "Polk, William T." , tools-development@ietf.org, Adrian Farrel Subject: Re: [TOOLS-DEVELOPMENT] Does anyone else find it hard tracking Discuss discussions? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 16:07:14 -0000 +1 to 3b - Ralph On Oct 29, 2010, at 11:25 AM 10/29/10, Jari Arkko wrote: > 3 > > or 3b: "DISCUSS: draft-foo (Jari)" > From glen@amsl.com Mon Nov 8 18:10:54 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A6083A6911; Mon, 8 Nov 2010 18:10:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 RFBsmI+l2j5s; Mon, 8 Nov 2010 18:10:53 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 5C23A3A6A09; Mon, 8 Nov 2010 18:10:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 81229E08C2; Mon, 8 Nov 2010 18:11:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YCRRT88IOBKz; Mon, 8 Nov 2010 18:11:16 -0800 (PST) Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id 39BFEE0834; Mon, 8 Nov 2010 18:11:16 -0800 (PST) Message-ID: <4CD8ADBB.8060909@amsl.com> Date: Mon, 08 Nov 2010 18:11:07 -0800 From: Glen Barney Organization: AMS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: ietf-announce@ietf.org, i-d-announce@ietf.org X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 08 Nov 2010 18:15:22 -0800 Subject: [TOOLS-DEVELOPMENT] Draft Announcement Service Restored X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 02:10:54 -0000 All - I have been unable to contact the Tools Team (they are probably all in sessions right now!), so I put in a very unorthodox live patch to the live datatracker, and that appears to have fixed the problem with broken announcements. To ensure that everyone receives everything, I am going to requeue all the draft announcements that went out today. I will continue to monitor this, and will send a report to the tools team to let them know what I did. Thank you all for your patience with this matter. Glen Glen Barney IT Director AMS (IETF Secretariat) From glen@amsl.com Mon Nov 8 18:31:59 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50CF528C18B; Mon, 8 Nov 2010 18:31:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 MJBdgl-uGnje; Mon, 8 Nov 2010 18:31:38 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 1F26728C126; Mon, 8 Nov 2010 18:31:14 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 05836E08C1; Mon, 8 Nov 2010 18:31:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k5Heia3LhIi5; Mon, 8 Nov 2010 18:31:36 -0800 (PST) Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id A8442E0834; Mon, 8 Nov 2010 18:31:36 -0800 (PST) Message-ID: <4CD8B280.9060404@amsl.com> Date: Mon, 08 Nov 2010 18:31:28 -0800 From: Glen Barney Organization: AMS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "codesprints@ietf.org" , Russ Housley , Henrik Levkowetz , tools-development@ietf.org, tools-team@ietf.org X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [TOOLS-DEVELOPMENT] Datatracker Patch Report X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 02:31:59 -0000 All - An emergency patch has been applied to the live datatracker. This is a report on that patch. We received reports today that Internet Draft announcements were not being received by people. Specifically, many people in regular single-message-delivery mode were not receiving the email; however, digest readers were receiving it. One person reported that MIME headers appeared to be malformed. Nothing had changed on the AMS end since this was working. The old ID Submission Tool was not modified (except for a reopening-time patch, which was not related), and mailman, postfix, and other MTA chain tools were not modified. What had changed, however, was that we were now processing scheduled announcements through the datatracker. I attempted to find Henrik, but he was unavailable. I did reach Robert Sparks, but he had not been involved in this change. I investigated backup copies of the messages on the server. I found that the Content-type header was being squashed to lowercase. This was causing the IDST "NextPart" boundary to be squashed in the header to "nextpart". This, in turn, was causing many MTAs (and MUAs) to fail to receive and/or parse the message because of the malformed headers and MIME structure. Armed with this information I dove into the datatracker code. I traced things down to the following file: web/ietf/announcements/send_scheduled.py Line 16 said this: content_type = announcement.content_type.lower() I changed it to this: content_type = announcement.content_type That was to fix the squashing, but I also noticed that later code depended on that squashing: Line 20 said this: elif 'multipart' in content_type: Since the IDST injects records into the database with a Content Type of "Multipart/Mixed" (instead of "multipart/mixed"), I changed it to this: elif 'ultipart' in content_type: (I just removed the "M" from the test). These two changes allowed I-D announcements to go through and be processed and received correctly. I then went in and requeued all the sent mail in the database from November 1 onward, and all those messages did subsequently get processed correctly. Doubtless someone will want to go in and do a cleaner correction for this problem - I was acting without Henrik's guidance on an emergency basis, just to get those announcements fixed and flowing again. Hopefully this information will facilitate a fix for the next update. Sorry if I treaded on toes here but as I'm sure you understand, "In an emergency, anything goes." Please let me know if further information is needed. Thanks, Glen From tony@att.com Mon Nov 8 19:06:17 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 731863A6930; Mon, 8 Nov 2010 19:06:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.422 X-Spam-Level: X-Spam-Status: No, score=-106.422 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 fTrtnWOJFRgH; Mon, 8 Nov 2010 19:06:16 -0800 (PST) Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 3218328C28C; Mon, 8 Nov 2010 19:05:59 -0800 (PST) X-VirusChecked: Checked X-Env-Sender: tony@att.com X-Msg-Ref: server-13.tower-161.messagelabs.com!1289271978!30507518!1 X-StarScan-Version: 6.2.9; banners=-,-,- X-Originating-IP: [144.160.20.145] Received: (qmail 10146 invoked from network); 9 Nov 2010 03:06:19 -0000 Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-13.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Nov 2010 03:06:19 -0000 Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oA936aPs019242; Mon, 8 Nov 2010 22:06:37 -0500 Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oA936VN3019201; Mon, 8 Nov 2010 22:06:31 -0500 Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oA936Cc3024556; Mon, 8 Nov 2010 22:06:13 -0500 Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oA9368lW024449; Mon, 8 Nov 2010 22:06:08 -0500 Received: from [135.70.148.82] (vpn-135-70-148-82.vpn.mwst.att.com[135.70.148.82]) by maillennium.att.com (mailgw1) with ESMTP id <20101109030605gw1004lkp6e> (Authid: tony); Tue, 9 Nov 2010 03:06:07 +0000 X-Originating-IP: [135.70.148.82] Message-ID: <4CD8BA99.3040907@att.com> Date: Mon, 08 Nov 2010 22:06:01 -0500 From: Tony Hansen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Glen Barney References: <4CD8B280.9060404@amsl.com> In-Reply-To: <4CD8B280.9060404@amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 08 Nov 2010 19:08:21 -0800 Cc: tools-team@ietf.org, Henrik Levkowetz , "codesprints@ietf.org" , tools-development@ietf.org Subject: Re: [TOOLS-DEVELOPMENT] [codesprints] Datatracker Patch Report X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 03:06:17 -0000 On 11/8/2010 9:31 PM, Glen Barney wrote: > ... What had changed, however, was that we were now processing scheduled > announcements through the datatracker. I attempted to find Henrik, but > he was unavailable. I did reach Robert Sparks, but he had not been > involved in this change. I'm not sure who was involved in that change.Armed with this information I dove into the datatracker code. > I traced things down to the following file: > > web/ietf/announcements/send_scheduled.py > > Line 16 said this: > content_type = announcement.content_type.lower() > > I changed it to this: > content_type = announcement.content_type > > That was to fix the squashing, but I also noticed that later code > depended on that squashing: > > Line 20 said this: > elif 'multipart' in content_type: > > Since the IDST injects records into the database with a Content Type of > "Multipart/Mixed" (instead of "multipart/mixed"), I changed it to this: > elif 'ultipart' in content_type: > > (I just removed the "M" from the test). Your fix appears totally correct. Nit: I'm wondering if a better fix would be elif 'multipart/' in content_type.lower() > These two changes allowed I-D announcements to go through and be > processed and received correctly. I then went in and requeued all the > sent mail in the database from November 1 onward, and all those messages > did subsequently get processed correctly. > > Doubtless someone will want to go in and do a cleaner correction for > this problem - I was acting without Henrik's guidance on an emergency > basis, just to get those announcements fixed and flowing again. > > Hopefully this information will facilitate a fix for the next update. > Sorry if I treaded on toes here but as I'm sure you understand, "In an > emergency, anything goes." Please let me know if further information is > needed. Thanks for tracking the problem down Glen. Tony From glen@amsl.com Mon Nov 8 19:30:24 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8216628C1B8; Mon, 8 Nov 2010 19:30:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 LszW7SSOXmNX; Mon, 8 Nov 2010 19:30:23 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id CF2E928C1A5; Mon, 8 Nov 2010 19:30:22 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 11D5CE08C2; Mon, 8 Nov 2010 19:30:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DW4rx0v36FFY; Mon, 8 Nov 2010 19:30:45 -0800 (PST) Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id A6D27E076A; Mon, 8 Nov 2010 19:30:45 -0800 (PST) Message-ID: <4CD8C05C.5090407@amsl.com> Date: Mon, 08 Nov 2010 19:30:36 -0800 From: Glen Barney Organization: AMS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Tony Hansen References: <4CD8B280.9060404@amsl.com> <4CD8BA99.3040907@att.com> In-Reply-To: <4CD8BA99.3040907@att.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: tools-team@ietf.org, Henrik Levkowetz , "codesprints@ietf.org" , tools-development@ietf.org Subject: Re: [TOOLS-DEVELOPMENT] [codesprints] Datatracker Patch Report X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 03:30:24 -0000 On 11/8/2010 7:06 PM, Tony Hansen wrote: > Your fix appears totally correct. Nit: I'm wondering if a better fix > would be > elif 'multipart/' in content_type.lower() I like that one better, yes. I'll let Henrik figure out what he wants to do with that. :-) Now that it's working, I don't want to touch it. :-) > Thanks for tracking the problem down Glen. > Tony And thank you for the check! :-) Glen From henrik@levkowetz.com Mon Nov 8 22:24:06 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9C8F3A6875; Mon, 8 Nov 2010 22:24:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.543 X-Spam-Level: X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 I7tVgmdLpg+7; Mon, 8 Nov 2010 22:24:04 -0800 (PST) Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 6C1363A6874; Mon, 8 Nov 2010 22:24:04 -0800 (PST) Received: from [2001:df8:0:96:21b:63ff:fecd:4021] (port=56071) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1PFhcg-0007Hd-5V; Tue, 09 Nov 2010 07:24:04 +0100 Message-ID: <4CD8E8FD.8060402@levkowetz.com> Date: Tue, 09 Nov 2010 14:23:57 +0800 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: Glen Barney References: <4CD8A1EA.2050109@amsl.com> In-Reply-To: <4CD8A1EA.2050109@amsl.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:df8:0:96:21b:63ff:fecd:4021 X-SA-Exim-Rcpt-To: glen@amsl.com, codesprints@ietf.org, tools-development@ietf.org, tools-team@ietf.org, housley@vigilsec.com, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org) Cc: tools-team@ietf.org, tools-development@ietf.org, "codesprints@ietf.org" Subject: Re: [TOOLS-DEVELOPMENT] Problem with I-D Announcements / Recent Datatracker Update X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 06:24:07 -0000 Hi Glen, I'll start looking at this at once. Best, Henrik On 2010-11-09 09:20 Glen Barney said the following: > Tools Team - > > Please forgive the crossposting, but this is urgent. > > We are getting reports that I-D-Announcements are not going out > correctly to the list. > > One complainant indicated that the MIME headers were going out > malformed. Other evidence suggests that some digest readers are getting > the digests, but individual list subscribers are getting no mail, or > blank mail, or invalid mail. > > The old ID Submission Tool uses "NextPart" as a MIME boundary, which is > obviously very bad... but it has been doing that for the past 3+ years > with no problem. > > Mailman has also been correctly handling those things for several years, > also with no problem. > > The only thing which has changed in the processing chain recently is > that the Django Datatracker is now handling the processing of "Send > Scheduled Announcements" via this cron job: > > */15 * * * * /a/www/ietf-datatracker/web/ietf/bin/send-scheduled-mail all > > We implemented that change during the upload blackout before the IETF > meeting; all announcements since uploading reopened yesterday appear to > be problematic. > > This is the reason I'm contacting these lists. If someone could have a > look at this quickly, and determine what needs to be fixed, that would > be very helpful. > > Thank you, > Glen > > From jo@netlab.tkk.fi Fri Nov 12 06:44:16 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AB0E3A6941 for ; Fri, 12 Nov 2010 06:44:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.799 X-Spam-Level: X-Spam-Status: No, score=-4.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_23=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_MED=-4] 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 ZsL97+Tm2JxP for ; Fri, 12 Nov 2010 06:44:09 -0800 (PST) Received: from smtp-3.hut.fi (smtp-3.hut.fi [130.233.228.93]) by core3.amsl.com (Postfix) with ESMTP id 38D223A682B for ; Fri, 12 Nov 2010 06:44:07 -0800 (PST) Received: from localhost (katosiko.hut.fi [130.233.228.115]) by smtp-3.hut.fi (8.13.6/8.12.10) with ESMTP id oACEidNE026997; Fri, 12 Nov 2010 16:44:39 +0200 Received: from smtp-3.hut.fi ([130.233.228.93]) by localhost (katosiko.hut.fi [130.233.228.115]) (amavisd-new, port 10024) with LMTP id 01497-411; Fri, 12 Nov 2010 16:44:39 +0200 (EET) Received: from smtp.netlab.hut.fi (luuri.netlab.hut.fi [130.233.154.177]) by smtp-3.hut.fi (8.13.6/8.12.10) with ESMTP id oACEiXdD026988; Fri, 12 Nov 2010 16:44:33 +0200 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id 2E1301E120; Fri, 12 Nov 2010 16:44:33 +0200 (EET) X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id q4oHPebr+KR1; Fri, 12 Nov 2010 16:44:28 +0200 (EET) Received: from joerg-otts-macbook.local (a91-154-97-129.elisa-laajakaista.fi [91.154.97.129]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id 61BD01E1D5; Fri, 12 Nov 2010 16:44:26 +0200 (EET) Message-ID: <4CDD426D.5070903@netlab.tkk.fi> Date: Fri, 12 Nov 2010 15:34:37 +0200 From: Joerg Ott User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: tools-development@ietf.org Content-Type: multipart/mixed; boundary="------------030902000800050803010808" X-TKK-Virus-Scanned: by amavisd-new-2.1.2-hutcc at katosiko.hut.fi X-Mailman-Approved-At: Fri, 12 Nov 2010 14:26:57 -0800 Cc: Varun Singh , "igor.curcio@nokia.com" Subject: [TOOLS-DEVELOPMENT] Author recognition in I-D submissions X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2010 14:44:16 -0000 This is a multi-part message in MIME format. --------------030902000800050803010808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I am having trouble with the automated author detection in the I-D submission system. Quite often, only two names get recognized (out of three, in this case). I am attaching one Internet Draft that had this problem two days ago. Varun Singh and myself were recognized as authors, Igor Curcio was not. Thanks, Joerg --------------030902000800050803010808 Content-Type: text/plain; name="draft-ott-avt-rtcp-xt-discard-metrics-02.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="draft-ott-avt-rtcp-xt-discard-metrics-02.txt" AVT Working Group J. Ott Internet-Draft Aalto University Intended status: Standards Track I. Curcio Expires: May 15, 2011 Nokia Research Center V. Singh Aalto University November 11, 2010 Real-time Transport Control Protocol Extension Report for Run Length Encoding of Discarded Packets draft-ott-avt-rtcp-xt-discard-metrics-02.txt Abstract The Real-time Transport Control Protocol (RTCP) is used in conjunction with the Real-time Transport Protocol (RTP) in to provide a variety of short-term and long-term reception statistics. The available reporting may include aggregate information across longer periods of time as well as individual packet reporting. This document specifies a per-packet report metric capturing individual packets discarded from the jitter buffer after successful reception. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on May 15, 2011. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of Ott, et al. Expires May 15, 2011 [Page 1] Internet-Draft RTCP XR Discard RLE November 2010 publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. XR Discard RLE Report Block . . . . . . . . . . . . . . . . . 4 4. XR Bytes Discarded Report Block . . . . . . . . . . . . . . . 5 5. Protocol Operation . . . . . . . . . . . . . . . . . . . . . . 6 5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 7 5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . . 7 6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 8.1. XR Report Block Registration . . . . . . . . . . . . . . . 8 8.2. SDP Parameter Registration . . . . . . . . . . . . . . . . 9 8.3. Contact information for IANA registrations . . . . . . . . 9 9. Normative References . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Ott, et al. Expires May 15, 2011 [Page 2] Internet-Draft RTCP XR Discard RLE November 2010 1. Introduction RTP [RFC3550] provides a transport for real-time media flows such as audio and video together with the RTP control porotocl which provides periodic feedback about the media streams received in a specific duration. In addition, RTCP can be used for timely feedback about individual events to report (e.g., packet loss) [RFC4585]. Both long-term and short-term feedback enable a sender to adapt its media transmission and/or encoding dynamically to the observed path characteristics. RFC3611 [RFC3611] defines RTCP eXtension Reports as a detailed reporting framework to provide more than just the coarse RR statistics. The detailed reporting may enable a sender to react more appropriately to the observed networking conditions as these can be characterized better, albeit at the expense of extra overhead. Among many other fields, RFC3611 specifies the Loss RLE block which define runs of packets received and lost with the granularity of individual packets. This can help both error recovery and path loss characterization. In addition to lost packets, RFC 3611 defines the notion of "discarded" packets: packets that were received but dropped from the jitter buffer because they were either too early (for buffering) or too late (for playout). This metric is part of the VoIP metrics report block even though it is not just applicable to audio: it is specified as the fraction of discarded packets since the beginning of the session. See section 4.7.1 of RFC3611 [RFC3611]. Recently proposed extensions to the XR reporting suggest enhancing this discard metric: o Reporting the number of discarded packets during either the last reporting interval or since the beginning of the session, as indicated by a flag in the suggested XR report [I-D.ietf-avt-rtcp-xr-discard]. o Reporting gaps and bursts of discarded packets during the last reporting interval or cumulatively since the beginning of the session [I-D.ietf-avt-rtcp-xr-burst-gap-discard]. However, none of these metrics allow a receiver to report precisely which packets were discarded. While this information could in theory be derived from high-frequency reporting on the number of discarded packets or from the gap/burst report, these two mechanisms do not appear feasible: The former would require an unduly high amount of reporting which still might not be sufficient due to the non- deterministic scheduling of RTCP packets. The latter incur significant complexity and reporting overhead and might still not deliver the desired accurary. Ott, et al. Expires May 15, 2011 [Page 3] Internet-Draft RTCP XR Discard RLE November 2010 This document defines a discard report block following the idea of the run-length encoding applied for lost and received packets in RFC3611. Complementary to or instead of the indication which packets were lost, an XR block is defined to indicate the number of bytes lost, per interval or for the duration of the session, similar to other XR report blocks. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119] and indicate requirement levels for compliant implementations. The terminology defined in RTP [RFC3550] and in the extensions for XR reporting [RFC3611] applies. 3. XR Discard RLE Report Block The XR Discard RLE report block uses the same format as specified for the loss and duplicate report blocks in RFC3611 [RFC3611]. Figure Figure 1 recaps the packet format. The fields "BT", "T", "block length", "SSRC of source", "begin_seq", and "end_seq" SHALL have the same semantics and representation as defined in RFC3611. The "chunks" encoding the run length SHALL have the same representation as in RFC3611, but encode discarded packets. Ott, et al. Expires May 15, 2011 [Page 4] Internet-Draft RTCP XR Discard RLE November 2010 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=DRLE |rsvd |E| T | block length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | begin_seq | end_seq | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | chunk 1 | chunk 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : ... : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | chunk n-1 | chunk n | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: XR Discard Report Block The 'E' bit is introduced to distinguish between packets discarded due to early arrival and those discarded due to late arrival. The 'E' bit MUST be set to '1' if the chunks represent packets discarded due to too early arrival and MUST be set to '0' otherwise. In case both early and late discarded packets shall be reported, two Discard RLE report blocks MUST be included; their sequence number range MAY overlap, but individual packets MUST only be reported as either early or late. Packets reported in both MUST be considered as discarded without further information available, packets reported in neither are considered to be properly received and not discarded. Discard RLE Report Blocks SHOULD be sent in conjunction with an RTCP RR as a compound RTCP packet. Editor's node: is it acceptable to use one of the 'reserved' bits for this purpose or should two block types be used? 4. XR Bytes Discarded Report Block The XR Bytes Discarded report block uses the following format which follows the model of the framework for performance metric development [I-D.ietf-pmol-metrics-framework]. Ott, et al. Expires May 15, 2011 [Page 5] Internet-Draft RTCP XR Discard RLE November 2010 0 1 2 3 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=BDR |I|E| resv | block length=2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | number of bytes discarded | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2: XR Bytes Discarded Report Block The Interval Metric flag (I) (1 bit) is used to indicate whether the Post-Repair Loss metric is an Interval or a Cumulative metric, that is, whether the reported value applies to the most recent measurement interval duration between successive metrics reports (I=1) (the Interval Duration) or to the accumulation period characteristic of cumulative measurements (I=0) (the Cumulative Duration). Numerical values for both these intervals are provided in the Measurement Identifier block referenced by the tag field below. The 'E' bit is introduced to distinguish between packets discarded due to early arrival and those discarded due to late arrival. The 'E' bit MUST be set to '1' if the chunks represent packets discarded due to too early arrival and MUST be set to '0' otherwise. In case both early and late discarded packets shall be reported, two Bytes Discarded report blocks MUST be included. The 'number of bytes discarded' is a 32-bit unsigned integer value indicating the total number of bytes discarded (I=0) or the number of bytes discarded since the last RTCP XR Bytes Discarded block was sent. Bytes Discarded Report Blocks SHOULD be sent in conjunction with an RTCP RR as a compound RTCP packet. Editor's note: is it acceptable to use one of the 'reserved' bits for this purpose or should two block types be used? 5. Protocol Operation This section describes the behavior of the reporting (= receiver) RTP node and the sender RTP node. Ott, et al. Expires May 15, 2011 [Page 6] Internet-Draft RTCP XR Discard RLE November 2010 5.1. Reporting Node (Receiver) Transmission of RTCP XR Discard RLE Reports is up to the discretion of the receiver, as is the reporting granularity. However, it is RECOMMENDED that the receiver signals all discarded packets using the method defined in this document. If all packets over a reporting period were lost, the receiver MAY use the Discard Report Block [I-D.ietf-avt-rtcp-xr-discard] instead. In case of limited available reporting bandwidth, it is up to the receiver whether or not to include RTCP XR Discard RLE reports or not. The receiver MAY send the Discard RLE Reports as part of the regularly scheduled RTCP packets as per RFC3550. It MAY also include Discard RLE Reports in immediate or early feedback packets as per RFC4585. 5.2. Media Sender The media sender MUST be prepared to operate without receiving any Discard RLE reports. If Discard RLE reports are generated by the receiver, the sender cannot rely on all these reports being received, nor can the sender rely on a regular generation pattern from the receiver side. However, if the sender receives any RTCP reports but no Discard RLE report blocks and is aware that the receiver supports Discard RLE report blocks, it MAY assume that no packets were discarded at the receiver. 6. SDP signaling The report blocks specified in this document define extensions to RTCP XR reporting. Whether or not this specific extended report is sent is left to the discretion of the receiver. Its presence may enable better operation of the sender since more detailed information is available. Not providing this information will make the sender rely on other RTCP report metrics. A participant of a media session MAY use SDP to signal its support for this attribute. In this case, the RTCP XR attribute as defined in RFC3611 [RFC3611] MUST be used. The SDP RFC4566 [RFC4566] attribute 'xr-format' defined in RFC3611 is augmented as described in the following to indicate the discard metric. Ott, et al. Expires May 15, 2011 [Page 7] Internet-Draft RTCP XR Discard RLE November 2010 rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF ; defined in [RFC3611] xr-format =/ xr-discard-rle / xr-discard-bytes xr-discard-rle = "discard-rle" xr-discard-bytes = "discard-bytes" The literal 'discard-rle' MUST be used to indicate support for the Discard RLE Report Block defined in section Section 3, the literal 'discard-bytes' to indicate support for the Bytes Discarded Report Block defined in section Section 4 For signaling support for the discard metric, the rules defined in RFC3611 apply. Generally, senders and receivers SHOULD indicate this capability if they support this metric and would like to use it in the specific media session being signaled. The receiver MAY decide not to send discard information unless it knows about the sender's support to save on RTCP reporting bandwidth. A participant in a media session MAY use the two report blocks specified in this document without any explicit (SDP) signaling. 7. Security Considerations The security considerations of RFC3550, RFC3611, and RFC4585 apply. Since this document offers only a more precide reporting for an already existing metric, no further security implications are foreseen. 8. IANA Considerations New block types for RTCP XR are subject to IANA registration. For general guidelines on IANA considerations for RTCP XR, refer to RFC3611 [RFC3611]. 8.1. XR Report Block Registration This document extends the IANA "RTCP XR Block Type Registry" by two new values: DRLE and DBR. [Note to RFC Editor: please replace DRLE and DBR with the IANA provided RTCP XR block type for this block here and in the diagrams above.] Ott, et al. Expires May 15, 2011 [Page 8] Internet-Draft RTCP XR Discard RLE November 2010 8.2. SDP Parameter Registration This document registers two new parameters for the Session Description Protocol (SDP), "discard-rle" and "discard-bytes", in the "RTCP XR SDP Parameters Registry". 8.3. Contact information for IANA registrations Joerg Ott (jo@comnet.tkk.fi) Aalto University Comnet, Otakaari 5A, 02150 Espoo, Finland. 9. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003. [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video Conferences with Minimal Control", STD 65, RFC 3551, July 2003. [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, July 2006. [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006. [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control Protocol Extended Reports (RTCP XR)", RFC 3611, November 2003. [I-D.ietf-avt-rtcpssm] Ott, J. and J. Chesterfield, "RTCP Extensions for Single- Source Multicast Sessions with Unicast Feedback", draft-ietf-avt-rtcpssm-19 (work in progress), November 2009. [I-D.ietf-avt-rtcp-xr-discard] Hunt, G. and A. Clark, "RTCP XR Report Block for Discard metric Reporting", draft-ietf-avt-rtcp-xr-discard-02 (work in progress), May 2009. Ott, et al. Expires May 15, 2011 [Page 9] Internet-Draft RTCP XR Discard RLE November 2010 [I-D.ietf-avt-rtcp-xr-burst-gap-discard] Hunt, G. and A. Clark, "RTCP XR Report Block for Burst/Gap Discard metric Reporting", draft-ietf-avt-rtcp-xr-burst-gap-discard-02 (work in progress), May 2009. [I-D.ietf-pmol-metrics-framework] Clark, A. and B. Claise, "Guidelines for Considering New Performance Metric Development", draft-ietf-pmol-metrics-framework-05 (work in progress), October 2010. Authors' Addresses Joerg Ott Aalto University Otakaari 5 A Espoo, FIN 02150 Finland Email: jo@comnet.tkk.fi Igor D.D. Curcio Nokia Research Center P.O. Box 1000 (Visiokatu 1) Tampere, FIN 33721 Finland Email: igor.curcio (at) nokia.com Varun Singh Aalto University Otakaari 5 A Espoo, FIN 02150 Finland Email: varun@comnet.tkk.fi Ott, et al. Expires May 15, 2011 [Page 10] --------------030902000800050803010808-- From julian.reschke@gmx.de Sat Nov 13 01:24:16 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 18AA73A6AE5 for ; Sat, 13 Nov 2010 01:24:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.416 X-Spam-Level: X-Spam-Status: No, score=-105.416 tagged_above=-999 required=5 tests=[AWL=-3.417, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, 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 xRDYnAFI32dU for ; Sat, 13 Nov 2010 01:24:15 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id EAD4C3A6AC2 for ; Sat, 13 Nov 2010 01:24:14 -0800 (PST) Received: (qmail invoked by alias); 13 Nov 2010 09:24:48 -0000 Received: from p508FA1FD.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.161.253] by mail.gmx.net (mp009) with SMTP; 13 Nov 2010 10:24:48 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1+7SX4iv9i77cY+vps9ugJkr9Hu6gKhAuDcvVxKZn Wy6h8XLi5CYQ4C Message-ID: <4CDE5953.4010706@gmx.de> Date: Sat, 13 Nov 2010 10:24:35 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Joerg Ott References: <4CDD426D.5070903@netlab.tkk.fi> In-Reply-To: <4CDD426D.5070903@netlab.tkk.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: Varun Singh , "igor.curcio@nokia.com" , tools-development@ietf.org Subject: Re: [TOOLS-DEVELOPMENT] Author recognition in I-D submissions X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2010 09:24:16 -0000 On 12.11.2010 14:34, Joerg Ott wrote: > Hi, > > I am having trouble with the automated author detection in > the I-D submission system. Quite often, only two names get > recognized (out of three, in this case). > ... To those you'll be working on revising this code... Please seriously consider to use the XML source when present (just run it through xml2rfc to see whether it matches the TXT submission), it'y way more reliable than parsing the plain text. Best regards, Julian From rjsparks@nostrum.com Sat Nov 13 06:49:45 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F1493A6BB5 for ; Sat, 13 Nov 2010 06:49:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.467 X-Spam-Level: X-Spam-Status: No, score=-101.467 tagged_above=-999 required=5 tests=[AWL=-1.133, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, SARE_RECV_SPAM_DOMN0b=1.666, SPF_PASS=-0.001, 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 buu03wy6epKP for ; Sat, 13 Nov 2010 06:49:34 -0800 (PST) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id A4E113A6BAF for ; Sat, 13 Nov 2010 06:49:33 -0800 (PST) Received: from [192.168.1.91] (218-166-10-229.dynamic.hinet.net [218.166.10.229]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id oADEo1iH085194 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 13 Nov 2010 08:50:04 -0600 (CST) (envelope-from rjsparks@nostrum.com) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Robert Sparks In-Reply-To: <4CDE5953.4010706@gmx.de> Date: Sat, 13 Nov 2010 22:49:58 +0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4CDD426D.5070903@netlab.tkk.fi> <4CDE5953.4010706@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.1081) Received-SPF: pass (nostrum.com: 218.166.10.229 is authenticated by a trusted mechanism) Cc: Varun Singh , "igor.curcio@nokia.com" , tools-development@ietf.org, Joerg Ott Subject: Re: [TOOLS-DEVELOPMENT] Author recognition in I-D submissions X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2010 14:49:45 -0000 Hi Julian - Do you have the time/interest to scan the contents of the repository now = to see if there are any instances of xml not rendering txt (or at least not matching authors)? If there aren't any... RjS On Nov 13, 2010, at 5:24 PM, Julian Reschke wrote: > On 12.11.2010 14:34, Joerg Ott wrote: >> Hi, >>=20 >> I am having trouble with the automated author detection in >> the I-D submission system. Quite often, only two names get >> recognized (out of three, in this case). >> ... >=20 > To those you'll be working on revising this code... >=20 > Please seriously consider to use the XML source when present (just run = it through xml2rfc to see whether it matches the TXT submission), it'y = way more reliable than parsing the plain text. >=20 > Best regards, Julian > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From julian.reschke@gmx.de Sat Nov 13 07:31:26 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EDF23A686D for ; Sat, 13 Nov 2010 07:31:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.487 X-Spam-Level: X-Spam-Status: No, score=-105.487 tagged_above=-999 required=5 tests=[AWL=-2.888, BAYES_00=-2.599, 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 Qqa5XLWsLpk6 for ; Sat, 13 Nov 2010 07:31:25 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 41A693A6941 for ; Sat, 13 Nov 2010 07:31:23 -0800 (PST) Received: (qmail invoked by alias); 13 Nov 2010 15:31:58 -0000 Received: from p508FA1FD.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.161.253] by mail.gmx.net (mp037) with SMTP; 13 Nov 2010 16:31:58 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX18AWoEVpfgAMpYkjTItt6rP/iv4g9hOo1UkS0ZdQG vGSvH8BFL9pk23 Message-ID: <4CDEAF61.6070900@gmx.de> Date: Sat, 13 Nov 2010 16:31:45 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Robert Sparks References: <4CDD426D.5070903@netlab.tkk.fi> <4CDE5953.4010706@gmx.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: Varun Singh , "igor.curcio@nokia.com" , tools-development@ietf.org, Joerg Ott Subject: Re: [TOOLS-DEVELOPMENT] Author recognition in I-D submissions X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2010 15:31:26 -0000 On 13.11.2010 15:49, Robert Sparks wrote: > Hi Julian - > > Do you have the time/interest to scan the contents of the repository now to see if there are any > instances of xml not rendering txt (or at least not matching authors)? > If there aren't any... > ... I could write a quick script that extract author information from the XML versions. Do we have something we could diff the output against? Best regards, Julian From housley@vigilsec.com Mon Nov 15 10:31:43 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2EF328C1E7 for ; Mon, 15 Nov 2010 10:31:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 ooI6NWpr1KkC for ; Mon, 15 Nov 2010 10:31:37 -0800 (PST) Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 5DB5028C1B2 for ; Mon, 15 Nov 2010 10:31:34 -0800 (PST) Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 0DDD79A47C6 for ; Mon, 15 Nov 2010 13:32:27 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id eoTDWbvBr564 for ; Mon, 15 Nov 2010 13:32:09 -0500 (EST) Received: from [172.30.1.77] (unknown [12.230.88.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C191F9A47BE for ; Mon, 15 Nov 2010 13:32:24 -0500 (EST) Message-ID: <4CE17CCA.1020405@vigilsec.com> Date: Mon, 15 Nov 2010 13:32:42 -0500 From: Russ Housley User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: IETF Tools Development X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [TOOLS-DEVELOPMENT] Fwd: Re: I-D Action:draft-ietf-karp-crypto-key-table-00.txt X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 18:31:44 -0000 Hopefully, this is easy to fix. Russ -------- Original Message -------- Subject: Re: I-D Action:draft-ietf-karp-crypto-key-table-00.txt Date: Sat, 13 Nov 2010 21:19:06 -0800 From: bill manning To: internet-drafts@ietf.org, Russ Housley CC: bill manning , Ray Pelletier , RFC Interest hi kids... sometime in the recent past, a change occured wherein the MIME mail attachment dropped the text of the ID. now its just 85 bytes of stuff - no ID at all. Can the error be corrected? Either re-attach the ID to the message as indicated in the body of the email (and has been standard practice for more than a decade), or modify the body of the mail to reflect the new reality. --bill On 13November2010Saturday, at 20:45, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Keying and Authentication for Routing Protocols Working Group of the IETF. > > > Title : Database of Long-Lived Symmetric Cryptographic Keys > Author(s) : R. Housley, T. Polk > Filename : draft-ietf-karp-crypto-key-table-00.txt > Pages : 8 > Date : 2010-11-13 > > This document specifies the information contained in a database of > long-lived cryptographic keys used by many different security > protocols. The database design supports both manual and automated > key management. In many instances, the security protocols do not > directly use the long-lived key, but rather a key derivation function > is used to derive a short-lived key from a long-lived key. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-karp-crypto-key-table-00.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt From housley@vigilsec.com Tue Nov 16 08:21:40 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31F973A6D68 for ; Tue, 16 Nov 2010 08:21:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 ANnft2N98z4M for ; Tue, 16 Nov 2010 08:21:38 -0800 (PST) Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id CFB153A6CC1 for ; Tue, 16 Nov 2010 08:21:37 -0800 (PST) Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 364A89A4783; Tue, 16 Nov 2010 11:22:28 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id yhOhS3dY2Dxl; Tue, 16 Nov 2010 11:22:19 -0500 (EST) Received: from [192.168.2.102] (pool-96-231-58-190.washdc.fios.verizon.net [96.231.58.190]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4BBD39A4744; Tue, 16 Nov 2010 11:22:27 -0500 (EST) Message-ID: <4CE2AFDB.3050203@vigilsec.com> Date: Tue, 16 Nov 2010 11:22:51 -0500 From: Russ Housley User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Henrik Levkowetz References: <20101116085005.1789.39841.idtracker@localhost> In-Reply-To: <20101116085005.1789.39841.idtracker@localhost> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Gonzalo Camarillo's on draft-ietf-mediactrl-ivr-control-package-09 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 16:21:40 -0000 Henrik: Clearing a DISCUSS position seems to generate a very odd message. I hope it is easy to make it do something less obscure. Russ On 16/11/2010 10:50 AM, Gonzalo Camarillo wrote: > Gonzalo Camarillo has entered the following ballot position for > draft-ietf-mediactrl-ivr-control-package-09. > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > From rjsparks@nostrum.com Tue Nov 16 08:26:54 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7C6E3A6D68 for ; Tue, 16 Nov 2010 08:26:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.2 X-Spam-Level: X-Spam-Status: No, score=-101.2 tagged_above=-999 required=5 tests=[AWL=-0.267, BAYES_00=-2.599, SARE_RECV_SPAM_DOMN0b=1.666, 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 c8BXiGa6luxE for ; Tue, 16 Nov 2010 08:26:54 -0800 (PST) Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by core3.amsl.com (Postfix) with ESMTP id A2AF33A6CC3 for ; Tue, 16 Nov 2010 08:26:52 -0800 (PST) Received: from [192.168.1.91] (218-166-12-69.dynamic.hinet.net [218.166.12.69]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id oAGGQG8x036550 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Nov 2010 10:26:19 -0600 (CST) (envelope-from rjsparks@nostrum.com) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Robert Sparks In-Reply-To: <4CE2AFDB.3050203@vigilsec.com> Date: Wed, 17 Nov 2010 00:26:15 +0800 Content-Transfer-Encoding: quoted-printable Message-Id: <990542D4-35E5-4B2D-A872-202EE56134FE@nostrum.com> References: <20101116085005.1789.39841.idtracker@localhost> <4CE2AFDB.3050203@vigilsec.com> To: Russ Housley X-Mailer: Apple Mail (2.1081) Received-SPF: pass (nostrum.com: 218.166.12.69 is authenticated by a trusted mechanism) Cc: Henrik Levkowetz , IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Gonzalo Camarillo's on draft-ietf-mediactrl-ivr-control-package-09 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 16:26:54 -0000 I've already addressed this in a branch that should get merged into the = next release. RjS On Nov 17, 2010, at 12:22 AM, Russ Housley wrote: > Henrik: >=20 > Clearing a DISCUSS position seems to generate a very odd message. I > hope it is easy to make it do something less obscure. >=20 > Russ >=20 > On 16/11/2010 10:50 AM, Gonzalo Camarillo wrote: >> Gonzalo Camarillo has entered the following ballot position for >> draft-ietf-mediactrl-ivr-control-package-09. >>=20 >> When responding, please keep the subject line intact and reply to all >> email addresses included in the To and CC lines. (Feel free to cut = this >> introductory paragraph, however.) >>=20 >> Please refer to = http://www.ietf.org/iesg/statement/discuss-criteria.html >> for more information about IESG DISCUSS and COMMENT positions. >>=20 >>=20 >>=20 >=20 >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From henrik@levkowetz.com Tue Nov 16 09:38:35 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDB5C3A6CD2 for ; Tue, 16 Nov 2010 09:38:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.224 X-Spam-Level: X-Spam-Status: No, score=-102.224 tagged_above=-999 required=5 tests=[AWL=0.375, BAYES_00=-2.599, 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 lw17vW-797kl for ; Tue, 16 Nov 2010 09:38:34 -0800 (PST) Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id B496B3A6CAF for ; Tue, 16 Nov 2010 09:38:34 -0800 (PST) Received: from 90-230-136-60-no45.tbcn.telia.com ([90.230.136.60]:54475 helo=[192.168.1.65]) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1PIPUQ-0000TU-9X; Tue, 16 Nov 2010 18:38:42 +0100 Message-ID: <4CE2C19C.2030502@levkowetz.com> Date: Tue, 16 Nov 2010 18:38:36 +0100 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5 MIME-Version: 1.0 To: Robert Sparks References: <20101116085005.1789.39841.idtracker@localhost> <4CE2AFDB.3050203@vigilsec.com> <990542D4-35E5-4B2D-A872-202EE56134FE@nostrum.com> In-Reply-To: <990542D4-35E5-4B2D-A872-202EE56134FE@nostrum.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 90.230.136.60 X-SA-Exim-Rcpt-To: rjsparks@nostrum.com, housley@vigilsec.com, tools-development@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org) Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Gonzalo Camarillo's on draft-ietf-mediactrl-ivr-control-package-09 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 17:38:35 -0000 Hi Russ, Robert, I hope to merge and release tomorrow. Best, Henrik On 2010-11-16 17:26 Robert Sparks said the following: > I've already addressed this in a branch that should get merged into the next release. > > RjS > > On Nov 17, 2010, at 12:22 AM, Russ Housley wrote: > >> Henrik: >> >> Clearing a DISCUSS position seems to generate a very odd message. I >> hope it is easy to make it do something less obscure. >> >> Russ >> >> On 16/11/2010 10:50 AM, Gonzalo Camarillo wrote: >>> Gonzalo Camarillo has entered the following ballot position for >>> draft-ietf-mediactrl-ivr-control-package-09. >>> >>> When responding, please keep the subject line intact and reply to all >>> email addresses included in the To and CC lines. (Feel free to cut this >>> introductory paragraph, however.) >>> >>> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html >>> for more information about IESG DISCUSS and COMMENT positions. >>> >>> >>> >> >> >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development > > From housley@vigilsec.com Tue Nov 16 09:40:51 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 531723A6CAF; Tue, 16 Nov 2010 09:40:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 E7e1AL-6uaTl; Tue, 16 Nov 2010 09:40:50 -0800 (PST) Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 8669A3A6CDE; Tue, 16 Nov 2010 09:40:50 -0800 (PST) Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 6066A9A47C1; Tue, 16 Nov 2010 12:41:54 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id aCchKF0QY6Kv; Tue, 16 Nov 2010 12:41:25 -0500 (EST) Received: from [192.168.2.102] (pool-96-231-58-190.washdc.fios.verizon.net [96.231.58.190]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id B3EBE9A47C0; Tue, 16 Nov 2010 12:41:53 -0500 (EST) Message-ID: <4CE2C26E.7060907@vigilsec.com> Date: Tue, 16 Nov 2010 12:42:06 -0500 From: Russ Housley User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Henrik Levkowetz X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: webtools@ietf.org, IETF Tools Development Subject: [TOOLS-DEVELOPMENT] Liaison Tool Bug X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 17:40:51 -0000 https://datatracker.ietf.org/liaison/882/ This page works with Firefox, but generates an error with IE. The error says: Internal Server Error. The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there was an error in a script used to generate the requested page. Please contact webtools@ietf.org. From housley@vigilsec.com Wed Nov 17 07:53:35 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1171728C0D7 for ; Wed, 17 Nov 2010 07:53:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 UEoGxtndaMBb for ; Wed, 17 Nov 2010 07:53:33 -0800 (PST) Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id B36E53A6931 for ; Wed, 17 Nov 2010 07:53:33 -0800 (PST) Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 2A4A69A474B; Wed, 17 Nov 2010 10:54:41 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id RCjnqwe7QKIL; Wed, 17 Nov 2010 10:54:06 -0500 (EST) Received: from [192.168.2.102] (pool-96-231-58-190.washdc.fios.verizon.net [96.231.58.190]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1F0BE9A4727; Wed, 17 Nov 2010 10:54:40 -0500 (EST) Message-ID: <4CE3FAAA.9010701@vigilsec.com> Date: Wed, 17 Nov 2010 10:54:18 -0500 From: Russ Housley User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: IETF Tools Development X-Priority: 1 (Highest) X-Enigmail-Version: 1.1.1 Content-Type: multipart/alternative; boundary="------------010502040709000907010308" Subject: [TOOLS-DEVELOPMENT] WebEx Info for Tools Management Call X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: housley@vigilsec.com List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 15:53:35 -0000 This is a multi-part message in MIME format. --------------010502040709000907010308 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello , Please join my meeting that is currently in progress. Topic: Tools Management Date: Wednesday, November 17, 2010 Time: 10:52 am, Eastern Standard Time (New York, GMT-05:00) Meeting Number: 965 492 778 Meeting Password: (This meeting does not require a password.) ------------------------------------------------------- To join the online meeting (Now from the Apple iPhone (R) too!) ------------------------------------------------------- 1. Go to https://workgreen.webex.com/workgreen/e.php?AT=MI&EventID=148938432&UID=0&RT=MiMxMQ%3D%3D 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: (This meeting does not require a password.) 4. Click "Join". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://workgreen.webex.com/workgreen/e.php?AT=MI&EventID=148938432&UID=0&ORT=MiMxMQ%3D%3D ------------------------------------------------------- To join the audio conference only ------------------------------------------------------- To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code. Call-in toll-free number (US/Canada): 1-866-699-3239 Call-in toll number (US/Canada): 1-408-792-6300 Global call-in numbers: https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&ED=148938432&tollFree=1 Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf Access code:965 492 778 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://workgreen.webex.com/workgreen/mc 2. On the left navigation bar, click "Support". You can contact me at: housley@vigilsec.com 1-703-435-1775 Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. --------------010502040709000907010308 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello ,

Please join my meeting that is currently in progress.

Topic: Tools Management
Date: Wednesday, November 17, 2010
Time: 10:52 am, Eastern Standard Time (New York, GMT-05:00)
Meeting Number: 965 492 778
Meeting Password: (This meeting does not require a password.)


-------------------------------------------------------
To join the online meeting (Now from the Apple iPhone (R) too!)
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/e.php?AT=MI&EventID=148938432&UID=0&RT=MiMxMQ%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting does not require a password.)
4. Click "Join".
5. Follow the instructions that appear on your screen.

To view in other time zones or languages, please click the link:
https://workgreen.webex.com/workgreen/e.php?AT=MI&EventID=148938432&UID=0&ORT=MiMxMQ%3D%3D

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): 1-866-699-3239
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers: https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=MC&ED=148938432&tollFree=1
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

Access code:965 492 778

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://workgreen.webex.com/workgreen/mc
2. On the left navigation bar, click "Support".

You can contact me at:
housley@vigilsec.com
1-703-435-1775

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com



IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.

--------------010502040709000907010308-- From conte@isoc.org Wed Nov 17 08:45:53 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BAE128C0D7 for ; Wed, 17 Nov 2010 08:45:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.265 X-Spam-Level: X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 oEn8cL8hv-Ub for ; Wed, 17 Nov 2010 08:45:52 -0800 (PST) Received: from smtp124.dfw.emailsrvr.com (smtp124.dfw.emailsrvr.com [67.192.241.124]) by core3.amsl.com (Postfix) with ESMTP id 7ABAD28C0D8 for ; Wed, 17 Nov 2010 08:45:51 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 6555C2A81E1 for ; Wed, 17 Nov 2010 11:46:37 -0500 (EST) X-Virus-Scanned: OK Received: by smtp2.relay.dfw1a.emailsrvr.com (Authenticated sender: conte-AT-isoc.org) with ESMTPSA id 199B22A8165 for ; Wed, 17 Nov 2010 11:46:37 -0500 (EST) From: Steve Conte Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 17 Nov 2010 08:46:36 -0800 Message-Id: To: tools-development@ietf.org Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Subject: [TOOLS-DEVELOPMENT] Tools Call: 17 November 2010 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 16:45:53 -0000 Hi All, Here is the notes from today's call. As always, any errors contained = are more than likely my own. Steve ------ Tools Call - 17 November 2010 Attendees: Russ Housley Henrik Lebkowitz Steve Conte Julian Reschke 0 - Bash the Agenda 1 - Sprint Logistics Other than food issues, was there anything else that needs addressing = for future sprints? HL - No SC - No=20 RH to speak to Marcia about how to address future 2 - xml2rfc RH - Tony put a day in and finished xml2rfc (working late). Someone = recommended that it be deployed as experimental release. =20 JR - proposals weren't looked at prior to changes, so application isn't = working as=20 expected. Also while introducing changes to new boilerplate, the old = boilerplates=20 were broken. So there's more work to do before it's ready for = production. Next steps: Tony is traveling, but should be online by end of week. = Will need to decide vocabulary changes for boilerplate. Approx. 1-2 hours when Tony returns = to fix. RH - needs to wrap up discussion for architecture rewrite. Some people = felt that=20 pagination is important. Pagination is also dependant on device being = read (ie, via kindle, epub, etc) use IDIQ or go broader to make next changes? Discussion about using NROF (?) or html HL: Not a Django thing, but would probably be good as Python. Suggests = polling of relevant tools folks. JR doesn't have experience in python so no = opinion=20 RH to raise this to IAOC and ask for their thoughts. 3 - List discussions More and more messages from people to the tools-development list instead = of tools-discuss. Would be better to use tools-discuss list for general discussions so = list manager setup should be changed slightly to suggest non-list members to start at = tools-discuss and=20 moderate list Need Ray (admin for tools-dev) to make necessary changes ----- Steve Conte conte@isoc.org From housley@vigilsec.com Wed Nov 17 11:00:46 2010 Return-Path: X-Original-To: tools-development@core3.amsl.com Delivered-To: tools-development@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9C5C3A6976 for ; Wed, 17 Nov 2010 11:00:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 kX2gP7k7Tv6i for ; Wed, 17 Nov 2010 11:00:46 -0800 (PST) Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id DFE423A6965 for ; Wed, 17 Nov 2010 11:00:45 -0800 (PST) Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9C8AF9A47C5 for ; Wed, 17 Nov 2010 14:01:58 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id XyEg3i7EBYbR for ; Wed, 17 Nov 2010 14:01:18 -0500 (EST) Received: from [192.168.2.102] (pool-96-231-58-190.washdc.fios.verizon.net [96.231.58.190]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 24E129A47C1 for ; Wed, 17 Nov 2010 14:01:57 -0500 (EST) Message-ID: <4CE4268B.1070705@vigilsec.com> Date: Wed, 17 Nov 2010 14:01:31 -0500 From: Russ Housley User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: tools-development@ietf.org References: In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [TOOLS-DEVELOPMENT] Tools Call: 17 November 2010 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 19:00:46 -0000 NROF --> nroff On 11/17/2010 11:46 AM, Steve Conte wrote: > Hi All, > > Here is the notes from today's call. As always, any errors contained are more than likely my own. > > Steve > > ------ > > Tools Call - 17 November 2010 > > Attendees: > > Russ Housley > Henrik Lebkowitz > Steve Conte > Julian Reschke > > 0 - Bash the Agenda > > > 1 - Sprint Logistics > > Other than food issues, was there anything else that needs addressing for future sprints? > > HL - No > SC - No > RH to speak to Marcia about how to address future > > > 2 - xml2rfc > > RH - Tony put a day in and finished xml2rfc (working late). Someone recommended that it > be deployed as experimental release. > > JR - proposals weren't looked at prior to changes, so application isn't working as > expected. Also while introducing changes to new boilerplate, the old boilerplates > were broken. So there's more work to do before it's ready for production. > > Next steps: Tony is traveling, but should be online by end of week. Will need to decide > vocabulary changes for boilerplate. Approx. 1-2 hours when Tony returns to fix. > > RH - needs to wrap up discussion for architecture rewrite. Some people felt that > pagination is important. Pagination is also dependant on device being read (ie, via > kindle, epub, etc) > > use IDIQ or go broader to make next changes? > > Discussion about using NROF (?) or html > > HL: Not a Django thing, but would probably be good as Python. Suggests polling of > relevant tools folks. JR doesn't have experience in python so no opinion > > RH to raise this to IAOC and ask for their thoughts. > > > 3 - List discussions > > More and more messages from people to the tools-development list instead of tools-discuss. > Would be better to use tools-discuss list for general discussions so list manager setup > should be changed slightly to suggest non-list members to start at tools-discuss and > moderate list > > Need Ray (admin for tools-dev) to make necessary changes > > > ----- > Steve Conte > conte@isoc.org > > > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development >