From nobody Sun Feb 1 07:21:18 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67CCC1A8A3D for ; Sun, 1 Feb 2015 07:21:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.901 X-Spam-Level: X-Spam-Status: No, score=-103.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HXD1sHDuD5Go for ; Sun, 1 Feb 2015 07:21:14 -0800 (PST) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0691.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:691]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E9441A8A1F for ; Sun, 1 Feb 2015 07:21:14 -0800 (PST) Received: from [192.168.0.13] (72.237.59.193) by BN1PR06MB230.namprd06.prod.outlook.com (10.242.215.140) with Microsoft SMTP Server (TLS) id 15.1.75.20; Sun, 1 Feb 2015 15:20:50 +0000 Content-Type: multipart/alternative; boundary="Apple-Mail=_444B42EE-6123-4AD3-9E57-67D21AEF66C8" MIME-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Ray Pelletier X-Mail-Calendar-Part: Yes Date: Sun, 1 Feb 2015 10:22:04 -0500 Message-ID: <40FBAF1A-2920-4953-B174-E507D389501A@isoc.org> References: <815142808.377.1422803432053.JavaMail.nobody@jsj2tc407.webex.com> To: IETF Tools Development X-Mailer: Apple Mail (2.1993) X-Originating-IP: [72.237.59.193] X-ClientProxiedBy: BN3PR09CA0001.namprd09.prod.outlook.com (25.160.111.139) To BN1PR06MB230.namprd06.prod.outlook.com (10.242.215.140) Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR06MB230; X-Exchange-Antispam-Report-CFA: BCL:0;PCL:0;RULEID:;SRVR:BN1PR06MB230; X-Forefront-PRVS: 04740D25F1 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(377454003)(51704005)(243025005)(86362001)(575784001)(77096005)(84326002)(82746002)(42186005)(40100003)(69556001)(229853001)(15395725005)(19580395003)(15975445007)(19580405001)(122386002)(83716003)(1720100001)(117156001)(92566002)(76176999)(50986999)(512954002)(46102003)(19617315012)(33656002)(57306001)(16799955002)(110136001)(66066001)(50226001)(16601075003)(62966003)(77156002)(36756003)(568964001)(7059030)(24704002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN1PR06MB230; H:[192.168.0.13]; FPR:; SPF:None; MLV:sfv; LANG:en; X-Exchange-Antispam-Report-CFA: BCL:0;PCL:0;RULEID:;SRVR:BN1PR06MB230; X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Feb 2015 15:20:50.7225 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR06MB230 Archived-At: Cc: Michele Gehrke Subject: [TOOLS-DEVELOPMENT] Tools Call 3 Feb: Agenda & WebEx Details X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2015 15:21:17 -0000 --Apple-Mail=_444B42EE-6123-4AD3-9E57-67D21AEF66C8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" Tools Call Agenda -- 3 February 2015 at 13:00 Eastern 1. Datatracker Projects - Expected Datatracker Releases -- Robert and Henrik -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan = - Liaison Tool improvements -- Robert - Agenda Tool enhancements -- Robert - Performance improvements -- Henrik - Review Tracking -- Robert - Facelift -- Robert 2. Community & Other Projects - Present a directory view of active, archived, and unknown I-Ds = -- AMS - IETF Website Makeover -- Joe and Greg 3. RFC Services Projects - xml2rfc bug fixes -- Alice and Henrik - DOI -- Alice and Heather - RFC Editor Website Makeover -- Alice and Heather - RFC Format-related SOWs -- Robert - RSE's Design Team -- Heather 4. Transition of Mission Critical Tools - Moving mail aliases to ietf.org and link them to = datatracker database - Moving issue trackers and wikis for IETF WGs on ietf.org = 5. Server Infrastructure - VM Architecture for Servers -- AMS - iCal servers -- AMS - IMAP access to the email archives -- Robert 6. IDIQ Contractors - RFP for more IDIQ contractors -- Ray 7. Parking Lot - Test Coverage -- Henrik - Mentor Support Tool -- AMS - Automatic stats and reporting RFP -- Heather - Reflecting very old I-Ds and old author information in the = datatracker -- Robert 8. AOB > Begin forwarded message: >=20 > Date: February 1, 2015 at 10:10:32 AM EST > From: Ray Pelletier > Reply-To: > To: > Subject: (Forward to others) WebEx meeting invitation: Tools Cmte >=20 > You can forward this invitation to others. > Hello, > Ray Pelletier invites you to join this WebEx meeting. > =20 > Tools Cmte > Tuesday, February 3, 2015 > 1:00 pm | Eastern Standard Time (New York, GMT-05:00) | 1 hr > =20 > Join WebEx meeting = > Meeting number: 828 882 447 > =20 > Join by phone > 1-877-668-4490 Call-in toll-free number (US/Canada) > 1-408-792-6300 Call-in toll number (US/Canada) > Access code: 828 882 447 > Global call-in numbers = | Toll-free calling restrictions = > =20 > Add this meeting = to your calendar. > =20 > Can't join the meeting? Contact support. = > =20 > IMPORTANT NOTICE: Please note that this WebEx service allows audio and = other information sent during the session to be recorded, which may be = discoverable in a legal matter. By joining this session, you = automatically consent to such recordings. If you do not consent to being = recorded, discuss your concerns with the host or do not join the = session. --Apple-Mail=_444B42EE-6123-4AD3-9E57-67D21AEF66C8 Content-Type: multipart/mixed; boundary="Apple-Mail=_7367B16B-F9CB-49FF-8CC7-C5DCF574FD2D" --Apple-Mail=_7367B16B-F9CB-49FF-8CC7-C5DCF574FD2D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" Tools Call Agenda -- 3 February 2015 at 13:00 Eastern

1. Datatracker Projects
  - Expected Datatracker Releases -- Robert and = Henrik
    -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan
  - Liaison Tool improvements -- Robert
  - Agenda Tool enhancements -- Robert
  - Performance improvements -- Henrik
  - Review Tracking -- Robert
  - Facelift -- Robert

2. Community & Other Projects
  - = Present a directory view of active, archived, and unknown I-Ds -- AMS
  - IETF Website Makeover -- Joe and Greg

3. RFC Services Projects
  - xml2rfc bug fixes -- Alice and Henrik
  - DOI -- Alice and Heather
  - RFC Editor Website Makeover -- Alice and = Heather
  - RFC Format-related SOWs -- Robert
  - RSE's Design Team -- Heather

4. Transition of Mission Critical Tools
  - Moving mail aliases to ietf.org and link them to datatracker = database
  - Moving issue trackers and wikis for = IETF WGs on ietf.org

5. Server Infrastructure
  - VM = Architecture for Servers -- AMS
  - iCal servers = -- AMS
  - IMAP access to the email archives -- = Robert

6. IDIQ Contractors
  - RFP for more IDIQ contractors -- Ray

7. Parking Lot
  - = Test Coverage -- Henrik
  - Mentor Support Tool = -- AMS
  - Automatic stats and reporting RFP -- = Heather
  - Reflecting very old I-Ds and old = author information in the datatracker -- Robert

8. AOB

Begin forwarded = message:

Date: = February 1, 2015 at 10:10:32 AM = EST
From: = Ray Pelletier <messenger@webex.com>
Reply-To: = <rpelletier@isoc.org>
Subject: = (Forward to = others) WebEx meeting invitation: Tools Cmte

You can forward this = invitation to others.
Hello,
Ray Pelletier invites you to join this WebEx meeting.
 
= Tools Cmte
Tuesday, February 3, 2015
1:00 pm  |  Eastern Standard Time (New = York, GMT-05:00)  |  1 hr
 
= = Join WebEx meeting =
= Meeting number: 828 882 447
=09
 
Join by phone
1-877-668-4490 Call-in = toll-free number (US/Canada)
1-408-792-6300 Call-in = toll number (US/Canada)
Access code: 828 882 447
Global call-in numbers  |  Toll-free calling restrictions
 
Add this meeting to your = calendar.
 
Can't join the meeting? Contact support.
 
= IMPORTANT NOTICE: Please note that this WebEx service allows audio and = other information sent during the session to be recorded, which may be = discoverable in a legal matter. By joining this session, you = automatically consent to such recordings. If you do not consent to being = recorded, discuss your concerns with the host or do not join the = session.
= --Apple-Mail=_7367B16B-F9CB-49FF-8CC7-C5DCF574FD2D Content-Disposition: attachment; filename="WebEx_Meeting.ics" Content-Type: text/calendar; name="WebEx_Meeting.ics" Content-Transfer-Encoding: quoted-printable BEGIN:VCALENDAR=0APRODID:-//Microsoft=20Corporation//Outlook=2010.0=20= MIMEDIR//EN=0AVERSION:2.0=0AMETHOD:REQUEST=0ABEGIN:VTIMEZONE=0A= TZID:Eastern=20Time=0ABEGIN:STANDARD=0ADTSTART:20131101T020000=0A= RRULE:FREQ=3DYEARLY;INTERVAL=3D1;BYDAY=3D1SU;BYMONTH=3D11=0A= TZOFFSETFROM:-0400=0ATZOFFSETTO:-0500=0ATZNAME:Standard=20Time=0A= END:STANDARD=0ABEGIN:DAYLIGHT=0ADTSTART:20130301T020000=0A= RRULE:FREQ=3DYEARLY;INTERVAL=3D1;BYDAY=3D2SU;BYMONTH=3D3=0A= TZOFFSETFROM:-0500=0ATZOFFSETTO:-0400=0ATZNAME:Daylight=20Savings=20Time=0A= END:DAYLIGHT=0AEND:VTIMEZONE=0ABEGIN:VEVENT=0AATTENDEE;CN=3D"Ray=20= Pelletier";ROLE=3DREQ-PARTICIPANT;RSVP=3DTRUE:MAILTO:rpelletier@isoc.org=0A= ORGANIZER;CN=3D"Ray=20Pelletier":MAILTO:rpelletier@isoc.org=0A= DTSTART;TZID=3D"Eastern=20Time":20150203T130000=0ADTEND;TZID=3D"Eastern=20= Time":20150203T140000=0ALOCATION:https://workgreen.webex.com/workgreen=0A= TRANSP:OPAQUE=0ASEQUENCE:1422803431=0A= UID:5e6f3ea1-06b9-436b-8d06-7c8ad1cb1cc7=0ADTSTAMP:20150203T180000Z=0A= DESCRIPTION:\n\n\nJOIN=20WEBEX=20= MEETING\nhttps://workgreen.webex.com/workgreen/j.php?MTID=3Dmb928aa2454e0b= df9be007ccaf375193f\nMeeting=20number:=20828=20882=20447\n\n\nJOIN=20BY=20= PHONE\n1-877-668-4490=20Call-in=20toll-free=20number=20(US/Canada)=20= \n1-408-792-6300=20Call-in=20toll=20number=20(US/Canada)\nAccess=20code:=20= 828=20882=20447\n\nGlobal=20call-in=20= numbers:\nhttps://workgreen.webex.com/workgreen/globalcallin.php?serviceTy= pe=3DMC&ED=3D296313192&tollFree=3D1\n\nToll-free=20dialing=20= restrictions:=20= \nhttp://www.webex.com/pdf/tollfree_restrictions.pdf\n\n\n\nCan't=20join=20= the=20meeting?=20Contact=20support=20= here:\nhttps://workgreen.webex.com/workgreen/mc\n\n\nIMPORTANT=20NOTICE:=20= Please=20note=20that=20this=20WebEx=20service=20allows=20audio=20and=20= other=20information=20sent=20during=20the=20session=20to=20be=20= recorded,=20which=20may=20be=20discoverable=20in=20a=20legal=20matter.=20= By=20joining=20this=20session,=20you=20automatically=20consent=20to=20= such=20recordings.=20If=20you=20do=20not=20consent=20to=20being=20= recorded,=20discuss=20your=20concerns=20with=20the=20host=20or=20do=20= not=20join=20the=20session.\n=0AX-ALT-DESC;FMTTYPE=3Dtext/html:=09 
=20=09=09Join=20WebEx=20meeting=09=09=09=09=09=09= =09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09
=09=09=09=09=09=09Meeting=20number:=09=09=09=09=09= =09=09=09=09=09=09828=20882=20447=09=09=09=09=09=
=09=09=09=09=09 
 
Join=20by=20phone =20
1-877-668-4490 Call-in=20toll-free=20= number=20(US/Canada) =20
1-408-792-6300 Call-in=20toll=20= number=20(US/Canada) =20
Access=20code:=20828=20882=20= 447 =20
Global=20call-in=20numbers  |  Toll-free=20calling=20= restrictions=20 =20


=09 
=09= =09=09=09=09= Can't=20join=20the=20meeting?=09=09Contact=20support.=09=  
 
IMPORTANT=20NOTICE:=20Please=20note=20that=20this=20WebEx=20= service=20allows=20audio=20and=20other=20information=20sent=20during=20= the=20session=20to=20be=20recorded,=20which=20may=20be=20discoverable=20= in=20a=20legal=20matter.=20By=20joining=20this=20session,=20you=20= automatically=20consent=20to=20such=20recordings.=20If=20you=20do=20not=20= consent=20to=20being=20recorded,=20discuss=20your=20concerns=20with=20= the=20host=20or=20do=20not=20join=20the=20session.=0A= SUMMARY:Tools=20Cmte=0APRIORITY:5=0ACLASS:PUBLIC=0ABEGIN:VALARM=0A= TRIGGER:-PT5M=0AACTION:DISPLAY=0ADESCRIPTION:Reminder=0AEND:VALARM=0A= END:VEVENT=0AEND:VCALENDAR=0A= --Apple-Mail=_7367B16B-F9CB-49FF-8CC7-C5DCF574FD2D Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="us-ascii"

--Apple-Mail=_7367B16B-F9CB-49FF-8CC7-C5DCF574FD2D-- --Apple-Mail=_444B42EE-6123-4AD3-9E57-67D21AEF66C8-- From nobody Mon Feb 2 17:29:43 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 635AC1A1EF9 for ; Mon, 2 Feb 2015 17:29:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.011 X-Spam-Level: X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MEKDpYgwwyd for ; Mon, 2 Feb 2015 17:29:38 -0800 (PST) Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF4941A1A5A for ; Mon, 2 Feb 2015 17:29:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1422926978; x=1454462978; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=73bZY5fblyBBGlUPGyU50Un6RK+DnD14XcxzkCs7F1I=; b=AbwVR7w+CoZ2NWftEp/GJgawhhgkw+cMKtG8PBBuEbFVDdjzpwE7+vZL /NyIxwKgDPCaVwbtnjSCCwa/tW798DT0GvpniumI36a775vTU52mNZiID nyvAyap2v/xKLKFydg0fTGRdzJiXvsNk5NP5OPHJyUVs3PqE/FVfc+W5/ M=; X-IronPort-AV: E=McAfee;i="5600,1067,7700"; a="83377104" Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Feb 2015 17:29:37 -0800 X-IronPort-AV: E=Sophos;i="5.09,509,1418112000"; d="scan'208";a="897202721" Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 02 Feb 2015 17:29:36 -0800 Received: from resnick2.qualcomm.com (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.995.29; Mon, 2 Feb 2015 17:29:35 -0800 Message-ID: <54D0247E.1030807@qti.qualcomm.com> Date: Mon, 2 Feb 2015 19:29:34 -0600 From: Pete Resnick User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4 MIME-Version: 1.0 To: Russ Housley References: In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: NASANEXM01D.na.qualcomm.com (10.85.0.84) To NASANEXM01F.na.qualcomm.com (10.85.0.32) Archived-At: Cc: IETF Tools Development , Joe Hildebrand Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 3 February 2015 at 13:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2015 01:29:40 -0000 Late regrets. :-( pr On 1/31/15 9:56 AM, Russ Housley wrote: > Tools Call Agenda -- 3 February 2015 at 13:00 Eastern > > 1. Datatracker Projects > - Expected Datatracker Releases -- Robert and Henrik > -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan > - Liaison Tool improvements -- Robert > - Agenda Tool enhancements -- Robert > - Performance improvements -- Henrik > - Review Tracking -- Robert > - Facelift -- Robert > > 2. Community& Other Projects > - Present a directory view of active, archived, and unknown I-Ds -- AMS > - IETF Website Makeover -- Joe and Greg > > 3. RFC Services Projects > - xml2rfc bug fixes -- Alice and Henrik > - DOI -- Alice and Heather > - RFC Editor Website Makeover -- Alice and Heather > - RFC Format-related SOWs -- Robert > - RSE's Design Team -- Heather > > 4. Transition of Mission Critical Tools > - Moving mail aliases to ietf.org and link them to datatracker database > - Moving issue trackers and wikis for IETF WGs on ietf.org > > 5. Server Infrastructure > - VM Architecture for Servers -- AMS > - iCal servers -- AMS > - IMAP access to the email archives -- Robert > > 6. IDIQ Contractors > - RFP for more IDIQ contractors -- Ray > > 7. Parking Lot > - Test Coverage -- Henrik > - Mentor Support Tool -- AMS > - Automatic stats and reporting RFP -- Heather > - Reflecting very old I-Ds and old author information in the datatracker -- Robert > > 8. AOB > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development > -- Pete Resnick Qualcomm Technologies, Inc. - +1 (858)651-4478 From nobody Tue Feb 3 08:26:11 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 609621A8AF6; Tue, 27 Jan 2015 13:25:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p4T3I_C7giBp; Tue, 27 Jan 2015 13:25:03 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1386D1A8AEA; Tue, 27 Jan 2015 13:25:03 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Administrative Director To: IETF Announcement List X-Test-IDTracker: no X-IETF-IDTracker: 5.10.1.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150127212503.7313.27896.idtracker@ietfa.amsl.com> Date: Tue, 27 Jan 2015 13:25:03 -0800 Archived-At: X-Mailman-Approved-At: Tue, 03 Feb 2015 08:26:09 -0800 Subject: [TOOLS-DEVELOPMENT] Contract Awards January 2015 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2015 21:25:04 -0000 The IAOC is pleased to announce the following contracts have been awarded and executed. 1. IETF Website Revamp to Torchbox Ltd. Joe Hildebrand is the PM for the project. SOW: https://iaoc.ietf.org/documents/IETF-Website-SOW-02.pdf 2. RFC Editor Digital Objects Identifier Project to Standcore. The RFC Series Editor, Heather Flanagan, is the PM. SOW: https://iaoc.ietf.org/documents/DOI-Processing-Draft-SOW.pdf 3. RFC Editor Website Revamp to AMS. The RFC Series Editor, Heather Flanagan, is the PM. Sow: https://iaoc.ietf.org/documents/RFC-Website-SOW-3Sep14.pdf In addition: 1. There is a Reguest for Information for identifying fonts for use with PDF RFCs. See: https://iaoc.ietf.org/documents/RFCPDFFontsRFI.pdf 2. There is a Request for Proposals pending seeking Software Development firms to enter into a Master Service Agreement for doing tools development work over a three year period. In the past the IETF had several contractors doing this work. See: https://iaoc.ietf.org/documents/Software-Development-IDIQ-RFP- 7Jan15.pdf Ray Pelletier IETF Administrative Director From nobody Tue Feb 3 08:26:13 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04ED51A1A06; Tue, 3 Feb 2015 07:52:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.6 X-Spam-Level: X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mcBcbTJ6yzPs; Tue, 3 Feb 2015 07:52:17 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 48A161A1A00; Tue, 3 Feb 2015 07:52:17 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: IETF Administrative Director To: IETF Announcement List X-Test-IDTracker: no X-IETF-IDTracker: 5.10.1.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150203155217.2391.76679.idtracker@ietfa.amsl.com> Date: Tue, 03 Feb 2015 07:52:17 -0800 Archived-At: X-Mailman-Approved-At: Tue, 03 Feb 2015 08:26:09 -0800 Subject: [TOOLS-DEVELOPMENT] =?utf-8?q?Proposed_IETF_Websites=E2=80=99_Pri?= =?utf-8?q?vacy_Policy=3B_Community_Input_Requested?= X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2015 15:52:18 -0000 The IAOC would like community input on a proposed IETF websites’ Privacy Policy. We are required by California law (and good net citizenship) to have an accurate privacy policy on our websites. Counsel have reviewed this statement for compliance with US and EU privacy regulations. The policy discusses the following: a. Information collected b. What’s done with the information c. Information accessible to the public d. Cookies and other tracking technologies e. Participant database f. Security g. Links h. Discussion groups i. Children j. Compliance k. Consent and changes to this policy The proposed Privacy Policy is located here: The IAOC will consider all comments received by 17 February 2015. Thanks. Scott Bradner Chair IAOC Legal Committee From nobody Thu Feb 5 09:52:25 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B9D01A03A0 for ; Thu, 5 Feb 2015 09:52:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.5 X-Spam-Level: X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WkJwEl5yCXzE for ; Thu, 5 Feb 2015 09:52:21 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 075EF1A1A67 for ; Thu, 5 Feb 2015 09:52:20 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id F2F691E5A20; Thu, 5 Feb 2015 09:51:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7v1dHYAuYZnG; Thu, 5 Feb 2015 09:51:54 -0800 (PST) Received: from Heathers-MacBook-Pro.local (unknown [98.125.214.233]) by c8a.amsl.com (Postfix) with ESMTPSA id 8B6F61E5A1F; Thu, 5 Feb 2015 09:51:54 -0800 (PST) Message-ID: <54D3ADD1.2070800@rfc-editor.org> Date: Thu, 05 Feb 2015 09:52:17 -0800 From: "Heather Flanagan (RFC Series Editor)" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: rsoc@iab.com, IETF Tools Development Content-Type: multipart/alternative; boundary="------------090703040109000001030001" Archived-At: Subject: [TOOLS-DEVELOPMENT] Report: RFI - Fonts for PDF RFCs X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 17:52:24 -0000 This is a multi-part message in MIME format. --------------090703040109000001030001 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, The comment period for the font RFI has closed, and while we did not get many responses, the input received was mostly useful. In particular, we now have more information on what fonts are available via an open source license from Adobe [1], additional pointers to consider Noto [2] as well as Roboto [3], Open Sans [4], and Skolar [5], and that the requirement for a monospace font with broad Unicode support is going to be a problem.= One suggestion received included a suggestion that we find a professional document designer to help with the layout and typefaces. I have no information on how much that would cost, so I have sent out some very unofficial queries to see if I can get an idea of whether this is remotely within our means. It may be that we can combine this with a CSS developer for the HTML format, though I have no more information to provide at this moment on whether that's a viable idea or not. I'll keep pursuing that idea, but separately from the font issue (for now - these may merge back together in the future). Back to the question of fonts, however, based on the input received, I think the Noto font family will be the best option. It gives us a wide range of Unicode support and was designed to work together across the different scripts. The only gap here is the lack of a monospace font within this family. The other fonts mentioned--the Adobe fonts, Roboto, and Open Sans--are all more significantly limited in their scripts than Noto is. Adobe has a monospace font option (Source Code Pro) but it is limited to Latin 4 (aka Western European) script support. There are several possible next steps, in estimated order of cost (lowest to highest): 1. Change the new format requirements to limit all code examples, ASCII artwork, or anything else that requires a fixed-width font to only use ASCII characters or Latin 4 characters and use Adobe's Source Code Pro. 2. Find someone at Google to see what it would take to get monospace variants for Noto that covers as many font families as possible. 3. Pay for the development of monospace typeface that would include at least the most expected use cases for non-Latin characters in RFCs (Asian scripts) as well as the Latin 3 and 4 (Eastern and Western European) scripts. I'd rather not do option 3 if we can avoid it. I don't think the (probable) expense is worth the effort if other options are available.=20 Option 1 is something we can fall back on if all else fails (for now) but this doesn't have to be a permanent choice. It can be what we do for now, and we can change this when fonts become available. I think that's the right place to start. And while we have that as our default, we can talk to the fine folks at Google (does anyone have a good contact within the Noto project?) about a set of monospace variants. Discussion and other opinions are welcome. Please let me know if you have any questions! - -Heather [1] https://github.com/adobe-fonts/ [2] http://www.google.com/get/noto , http://en.wikipedia.org/wiki/Noto_fo= nts [3] http://www.google.com/fonts/specimen/Roboto , http://en.wikipedia.org/wiki/Roboto [4] http://www.google.com/fonts/specimen/Open+Sans [5] https://www.rosettatype.com/Skolar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJU063RAAoJEER/xjINbZoGGxcIAIN9SnB3JyPbp0zhnSbeiah0 5hFgGsdwB1EUSHXmwe2AX6dSl3R7iWQVQptw0Pney5XoCq0RkzfckSj0Kon/otBG cePCcUmcf0/Cdv8PGax0k+7kDbQ1xFtTSHgODWc/SjlsIHooQomxH6fyyRAmQuJb g5v/qMNynAI81NZSF/GhEOp2yw4QC24D+STHvOzHQI07nCNf0UIg/aW9+5y/c196 dN4zqF52ncqjKj45m7Wx4F/UtNUatwyWfUwYDrf5AKf3IVpm1gI6C8Zldr2+sQ7i q7WXECrtGDm2qBMTeLe8ZKc3sahX9ApjCU6WW4EG0IC1L1M/tW6XpZZ0BBMV/+o=3D =3D2sis -----END PGP SIGNATURE----- --------------090703040109000001030001 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

The comment period for the font RFI has closed, and while we did not get many responses, the input received was mostly useful.  In particular, we now have more information on what fonts are available via an open source license from Adobe [1], additional pointers to consider Noto [2] as well as Roboto [3], Open Sans [4], and Skolar [5], and that the requirement for a monospace font with broad Unicode support is going to be a problem.

One suggestion received included a suggestion that we find a professional document designer to help with the layout and typefaces.  I have no information on how much that would cost, so I have sent out some very unofficial queries to see if I can get an idea of whether this is remotely within our means.  It may be that we can combine this with a CSS developer for the HTML format, though I have no more information to provide at this moment on whether that's a viable idea or not.  I'll keep pursuing that idea, but separately from the font issue (for now - these may merge back together in the future).

Back to the question of fonts, however, based on the input received, I think the Noto font family will be the best option.  It gives us a wide range of Unicode support and was designed to work together across the different scripts.  The only gap here is the lack of a monospace font within this family.  The other fonts mentioned--the Adobe fonts, Roboto, and Open Sans--are all more significantly limited in their scripts than Noto is.  Adobe has a monospace font option (Source Code Pro) but it is limited to Latin 4 (aka Western European) script support.

There are several possible next steps, in estimated order of cost (lowest to highest):

1. Change the new format requirements to limit all code examples, ASCII artwork, or anything else that requires a fixed-width font to only use ASCII characters or Latin 4 characters and use Adobe's  Source Code Pro.
2. Find someone at Google to see what it would take to get monospace variants for Noto that covers as many font families as possible.
3. Pay for the development of monospace typeface that would include at least the most expected use cases for non-Latin characters in RFCs (Asian scripts) as well as the Latin 3 and 4 (Eastern and Western European) scripts.

I'd rather not do option 3 if we can avoid it.  I don't think the (probable) expense is worth the effort if other options are available.  Option 1 is something we can fall back on if all else fails (for now) but this doesn't have to be a permanent choice.  It can be what we do for now, and we can change this when fonts become available.  I think that's the right place to start.  And while we have that as our default, we can talk to the fine folks at Google (does anyone have a good contact within the Noto project?) about a set of monospace variants.

Discussion and other opinions are welcome.  Please let me know if you have any questions!

- -Heather


[1] https://github.com/adobe-fonts/
[2] http://www.google.com/get/noto , http://en.wikipedia.org/wiki/Noto_fonts
[3] http://www.google.com/fonts/specimen/Roboto , http://en.wikipedia.org/wiki/Roboto
[4] http://www.google.com/fonts/specimen/Open+Sans
[5] https://www.rosettatype.com/Skolar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJU063RAAoJEER/xjINbZoGGxcIAIN9SnB3JyPbp0zhnSbeiah0
5hFgGsdwB1EUSHXmwe2AX6dSl3R7iWQVQptw0Pney5XoCq0RkzfckSj0Kon/otBG
cePCcUmcf0/Cdv8PGax0k+7kDbQ1xFtTSHgODWc/SjlsIHooQomxH6fyyRAmQuJb
g5v/qMNynAI81NZSF/GhEOp2yw4QC24D+STHvOzHQI07nCNf0UIg/aW9+5y/c196
dN4zqF52ncqjKj45m7Wx4F/UtNUatwyWfUwYDrf5AKf3IVpm1gI6C8Zldr2+sQ7i
q7WXECrtGDm2qBMTeLe8ZKc3sahX9ApjCU6WW4EG0IC1L1M/tW6XpZZ0BBMV/+o=
=2sis
-----END PGP SIGNATURE-----

--------------090703040109000001030001-- From nobody Thu Feb 5 09:58:23 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3C81A8A27 for ; Thu, 5 Feb 2015 09:58:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YR5FQHlGxM1z for ; Thu, 5 Feb 2015 09:58:19 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id C497F1A8A0D for ; Thu, 5 Feb 2015 09:58:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id BA0ED1E5A23; Thu, 5 Feb 2015 09:57:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxAHyEpg24BQ; Thu, 5 Feb 2015 09:57:54 -0800 (PST) Received: from Heathers-MacBook-Pro.local (unknown [98.125.214.233]) by c8a.amsl.com (Postfix) with ESMTPSA id 7804F1E5A20; Thu, 5 Feb 2015 09:57:54 -0800 (PST) Message-ID: <54D3AF3A.6080503@rfc-editor.org> Date: Thu, 05 Feb 2015 09:58:18 -0800 From: "Heather Flanagan (RFC Series Editor)" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: rsoc@iab.org, IETF Tools Development Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Subject: [TOOLS-DEVELOPMENT] Report: RFI - Fonts for PDF RFCs X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 17:58:21 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (fixed RSOC address) Hello all, The comment period for the font RFI has closed, and while we did not get many responses, the input received was mostly useful. In particular, we now have more information on what fonts are available via an open source license from Adobe [1], additional pointers to consider Noto [2] as well as Roboto [3], Open Sans [4], and Skolar [5], and that the requirement for a monospace font with broad Unicode support is going to be a problem. One suggestion received included a suggestion that we find a professional document designer to help with the layout and typefaces. I have no information on how much that would cost, so I have sent out some very unofficial queries to see if I can get an idea of whether this is remotely within our means. It may be that we can combine this with a CSS developer for the HTML format, though I have no more information to provide at this moment on whether that's a viable idea or not. I'll keep pursuing that idea, but separately from the font issue (for now - these may merge back together in the future). Back to the question of fonts, however, based on the input received, I think the Noto font family will be the best option. It gives us a wide range of Unicode support and was designed to work together across the different scripts. The only gap here is the lack of a monospace font within this family. The other fonts mentioned--the Adobe fonts, Roboto, and Open Sans--are all more significantly limited in their scripts than Noto is. Adobe has a monospace font option (Source Code Pro) but it is limited to Latin 4 (aka Western European) script support. There are several possible next steps, in estimated order of cost (lowest to highest): 1. Change the new format requirements to limit all code examples, ASCII artwork, or anything else that requires a fixed-width font to only use ASCII characters or Latin 4 characters and use Adobe's Source Code Pro. 2. Find someone at Google to see what it would take to get monospace variants for Noto that covers as many font families as possible. 3. Pay for the development of monospace typeface that would include at least the most expected use cases for non-Latin characters in RFCs (Asian scripts) as well as the Latin 3 and 4 (Eastern and Western European) scripts. I'd rather not do option 3 if we can avoid it. I don't think the (probable) expense is worth the effort if other options are available. Option 1 is something we can fall back on if all else fails (for now) but this doesn't have to be a permanent choice. It can be what we do for now, and we can change this when fonts become available. I think that's the right place to start. And while we have that as our default, we can talk to the fine folks at Google (does anyone have a good contact within the Noto project?) about a set of monospace variants. Discussion and other opinions are welcome. Please let me know if you have any questions! - -Heather [1] https://github.com/adobe-fonts/ [2] http://www.google.com/get/noto , http://en.wikipedia.org/wiki/Noto_fonts [3] http://www.google.com/fonts/specimen/Roboto , http://en.wikipedia.org/wiki/Roboto [4] http://www.google.com/fonts/specimen/Open+Sans [5] https://www.rosettatype.com/Skolar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJU0686AAoJEER/xjINbZoGu2cIAKh32MqRhVW/uPeWtDWIMnXA /mteW8AYBZplLl8h3jAiARTx6oEy8/HgNw6MGAFNLcCsWOuB0Oleb3Paw5pMS4HK 95MzfIl35DSnuopaIwMvdzKR4fr3NiQmhPgt5OJ6WeYpkYRS+Rq8rXH6p25DdfMg EqTcMilcON2/mX4u+BnP9ISV7abBc01lAhLypLOXDnjCFA1GMqKtquLJZ6xUpQqL or0vvP0FhO/OHk9WmS7hPI7q0/iKd03s3gPAOl5TjmOj+RYOObpxRzen/CzPsO7I rpEPAAQdvwzwPDiOv+eBnZsJqkxVPz7u4ibu8BZjQSZlwN0Av0EEt6xppgHtUtc= =n1zO -----END PGP SIGNATURE----- From nobody Thu Feb 5 10:43:11 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 971BB1A1BC7 for ; Thu, 5 Feb 2015 10:43:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.25 X-Spam-Level: X-Spam-Status: No, score=-100.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, USER_IN_WHITELIST=-100] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fXp_mJkn6RFm for ; Thu, 5 Feb 2015 10:43:06 -0800 (PST) Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id AAA191A8A4F for ; Thu, 5 Feb 2015 10:43:05 -0800 (PST) Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 6F1F69A4049 for ; Thu, 5 Feb 2015 13:42:55 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id vzr3mB2XFrrC for ; Thu, 5 Feb 2015 13:42:48 -0500 (EST) Received: from [172.16.14.115] (unknown [101.100.166.2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 15F569A41D6 for ; Thu, 5 Feb 2015 13:42:14 -0500 (EST) From: Russ Housley Content-Type: multipart/alternative; boundary=Apple-Mail-278-262109061 Date: Wed, 4 Feb 2015 20:07:03 -0500 References: <4398.1422979069@sandelman.ca> To: IETF Tools Development Message-Id: <95401BFB-E8F7-48B1-BB00-D9D8892C7876@vigilsec.com> Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) Archived-At: Subject: [TOOLS-DEVELOPMENT] Fwd: DMARC for IETF lists X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 18:43:07 -0000 --Apple-Mail-278-262109061 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Thoughts? Begin forwarded message: > From: Michael Richardson > Date: February 3, 2015 10:57:49 AM EST > To: iesg@ietf.org > Subject: DMARC for IETF lists >=20 >=20 > Just after the DMARC occured, I asked what the IETF as an = *organization* was > going to do. The DMARC situation has significantly affected the = ability of > the NOMCOM to communicate, forcing us to introduce mailman into what > previously was a much lighter weight (which you should read: fewer = opportunities > for accidental confidentiality disclosures) /etc/aliases reflector. >=20 > In the late summer/fall, I was told that the the DMARC WG suggest = something, > and I should wait. Are we approaching a point where we might be ready = for > running code? It seems that we need this across the board. >=20 > {BTW: I don't have a problem with rejecting all email to lists with = p=3Dreject.} >=20 >=20 >=20 > From: Daniel Kahn Gillmor > Date: February 3, 2015 10:07:29 AM EST > To: "Eggert\, Lars" , "tools-discuss\@ietf.org" = > Cc: David Leon Gil > Subject: Re: [Tools-discuss] DMARC >=20 >=20 > On Tue 2015-02-03 06:04:28 -0500, Eggert, Lars wrote: >> Begin forwarded message: >>> PS. Sending via Gmail because the CFRG mailing list software = attempts >>> to forge @yahoo-inc.com FROM addresses. And >>> Yahoo sets a DMARC p=3Dreject. Could a list admin please configure = the >>> IRTF listserv to not blatantly violate the IETF DMARC standard? >>=20 >> Forwarding from CFRG. IIRC there is nothing that can be done, but = forwarded just in case. >=20 > = http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-wha= t-should-senders >=20 > suggests: >=20 >>> If you are a mailing list owner, what should you do? >>>=20 >>> Mailing lists are a special case of sending mail on behalf of >>> individuals. The most common option is to use the mailing list=92s >>> address instead of the sender=92s on the From: line. This will = change >>> the reply behavior. Some mailing lists also choose to act as pure >>> forwarders and resend the mail without breaking DKIM signatures. As >>> of this publication, no common mailing list packages provide >>> straightforward configuration options that produce DMARC >>> compatibility, although Mailman has relevant features starting in >>> 2.1.16. If you are a developer of mailing list software and would >>> like help adding features to allow participants from domains with >>> DMARC p=3Dreject, please contact us at dmarc-help@yahoo-inc.com. >=20 > mailman's "relevant features" don't appear to provide many good > alternatives, even if we're running a newer version: >=20 > = http://wiki.list.org/DOC/What%20can%20I%20do%20about%20members%20being%20u= nsubscribed%20by%20bounces%20of%20Yahoo%20user%27s%20posts%20for%20DMARC%2= 0policy%20reasons%3F >=20 > But in 2.1.18, there is a dmarc_moderaction_action configuration = value: >=20 > http://wiki.list.org/DEV/DMARC >=20 > If we're running that version or later, i recommend setting > dmarc_moderaction_action to "Munge From". >=20 > --dkg >=20 > --=20 > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please reports datatracker.ietf.org bugs at = http://tools.ietf.org/tools/ietfdb > Please reports tools.ietf.org bugs at = http://tools.ietf.org/tools/issues or > send email to webmaster@tools.ietf.org >=20 >=20 --Apple-Mail-278-262109061 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
From: Michael Richardson = <mcr@sandelman.ca>
=
Date: February 3, 2015 = 10:57:49 AM EST
Subject: DMARC for IETF = lists


Just after the DMARC occured, I asked = what the IETF as an *organization* was
going to do.  The DMARC = situation has significantly affected the ability of
the NOMCOM to = communicate, forcing us to introduce mailman into what
previously was = a much lighter weight (which you should read: fewer opportunities
for = accidental confidentiality disclosures) /etc/aliases = reflector.

In the late summer/fall, I was told that the the DMARC = WG suggest something,
and I should wait.  Are we approaching a = point where we might be ready for
running code?  It seems that = we need this across the board.

{BTW: I don't have a problem with = rejecting all email to lists with p=3Dreject.}



From: = Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Date: February 3, 2015 10:07:29 AM EST
To: = "Eggert\, Lars" <lars@netapp.com>, = "tools-discuss\@ietf.org" <tools-discuss@ietf.org>
<= /span>
Cc: David Leon Gil <coruus@gmail.com>
=
Subject: = Re: [Tools-discuss] = DMARC


On Tue 2015-02-03 06:04:28 -0500, = Eggert, Lars wrote:
Begin forwarded = message:
PS. Sending via Gmail because the CFRG mailing list = software attempts
to forge @yahoo-inc.com <http://yahoo-inc.com/> FROM = addresses. And
Yahoo sets a DMARC p=3Dreject. = Could a list admin please configure = the
IRTF listserv to not blatantly violate the IETF DMARC = standard?

Forwarding from = CFRG. IIRC there is nothing that can be done, but forwarded just in = case.

http://yahoomail.tumblr.com/post/82426900353/yah= oo-dmarc-policy-change-what-should-senders

suggests:

If you are a mailing = list owner, what should you do?

Mailing lists are a special case = of sending mail on behalf of
individuals. The most common = option is to use the mailing = list=92s
address instead of the sender=92s = on the From: line. This will = change
the reply behavior. Some mailing lists also choose to act = as pure
forwarders and resend the mail without breaking DKIM = signatures. As
of this publication, no common = mailing list packages provide
straightforward configuration = options that produce DMARC
compatibility, although Mailman = has relevant features starting = in
2.1.16. If you are a developer of mailing list software = and would
like help adding features to = allow participants from domains = with
DMARC p=3Dreject, please contact us at dmarc-help@yahoo-inc.com.
=

mailman's "relevant features" don't appear = to provide many good
alternatives, even if we're running a newer = version:

http://wiki.list.org/DOC/What%20can%20I%20do= %20about%20members%20being%20unsubscribed%20by%20bounces%20of%20Yahoo%20us= er%27s%20posts%20for%20DMARC%20policy%20reasons%3F

But in = 2.1.18, there is a dmarc_moderaction_action configuration value:

=  http://wiki.list.org/DEV/DMARC

If we're running that = version or later, i recommend setting
dmarc_moderaction_action to = "Munge From".

=         --dkg

-- =
Tools-discuss mailing = list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/to= ols-discuss

Please reports datatracker.ietf.org bugs at = http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs = at http://tools.ietf.org/tools/issues or
send email to = webmaster@tools.ietf.org



= --Apple-Mail-278-262109061-- From nobody Thu Feb 5 11:12:16 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9856E1A8A1B for ; Thu, 5 Feb 2015 10:37:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.01 X-Spam-Level: X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80WkNy2PL4Vw for ; Thu, 5 Feb 2015 10:37:11 -0800 (PST) Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 67BBC1A8A09 for ; Thu, 5 Feb 2015 10:37:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1423161430; d=isode.com; s=selector; i=@isode.com; bh=C6EPbv4s4DSvuM09zPwKJjtrOu5QmVW+EzOiuIiM/dk=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=LhLF0S8sHbBcnNnpjLAt1LRWKoTUKJlvPSL+yHY/3bwtSwSedypMdZU/vl5RQIwhfcFN5O daXoCZxoi/tpiSf1MYFHqU+irwcfq+acPxpVHnps0c7Bx62yolYSNDpD64rzmLkaMYFbtn eUcSzvaWKNtSNbraSzUGXqM+634UHn0=; Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id ; Thu, 5 Feb 2015 18:37:10 +0000 Message-ID: <54D3B836.6050407@isode.com> Date: Thu, 05 Feb 2015 18:36:38 +0000 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 To: "Heather Flanagan (RFC Series Editor)" , rsoc@iab.org, IETF Tools Development References: <54D3AF3A.6080503@rfc-editor.org> In-Reply-To: <54D3AF3A.6080503@rfc-editor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: X-Mailman-Approved-At: Thu, 05 Feb 2015 11:12:12 -0800 Subject: Re: [TOOLS-DEVELOPMENT] [Rsoc] Report: RFI - Fonts for PDF RFCs X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 18:37:13 -0000 On 05/02/2015 17:58, Heather Flanagan (RFC Series Editor) wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > (fixed RSOC address) > > Hello all, > > The comment period for the font RFI has closed, and while we did not get > many responses, the input received was mostly useful. In particular, we > now have more information on what fonts are available via an open source > license from Adobe [1], additional pointers to consider Noto [2] as well > as Roboto [3], Open Sans [4], and Skolar [5], and that the requirement > for a monospace font with broad Unicode support is going to be a problem. > > One suggestion received included a suggestion that we find a > professional document designer to help with the layout and typefaces. I > have no information on how much that would cost, so I have sent out some > very unofficial queries to see if I can get an idea of whether this is > remotely within our means. It may be that we can combine this with a > CSS developer for the HTML format, though I have no more information to > provide at this moment on whether that's a viable idea or not. I'll > keep pursuing that idea, but separately from the font issue (for now - > these may merge back together in the future). > > Back to the question of fonts, however, based on the input received, I > think the Noto font family will be the best option. It gives us a wide > range of Unicode support and was designed to work together across the > different scripts. The only gap here is the lack of a monospace font > within this family. The other fonts mentioned--the Adobe fonts, Roboto, > and Open Sans--are all more significantly limited in their scripts than > Noto is. Adobe has a monospace font option (Source Code Pro) but it is > limited to Latin 4 (aka Western European) script support. > > There are several possible next steps, in estimated order of cost > (lowest to highest): > > 1. Change the new format requirements to limit all code examples, ASCII > artwork, or anything else that requires a fixed-width font to only use > ASCII characters or Latin 4 characters and use Adobe's Source Code Pro. > 2. Find someone at Google to see what it would take to get monospace > variants for Noto that covers as many font families as possible. > 3. Pay for the development of monospace typeface that would include at > least the most expected use cases for non-Latin characters in RFCs > (Asian scripts) as well as the Latin 3 and 4 (Eastern and Western > European) scripts. > > I'd rather not do option 3 if we can avoid it. I don't think the > (probable) expense is worth the effort if other options are available. > Option 1 is something we can fall back on if all else fails (for now) > but this doesn't have to be a permanent choice. It can be what we do > for now, and we can change this when fonts become available. I think > that's the right place to start. Your plan looks good to me. > And while we have that as our default, > we can talk to the fine folks at Google (does anyone have a good contact > within the Noto project?) about a set of monospace variants. I don't know of any, but there are some Google people who are active in IETF (Harald Alvestrand and Ted Hardie) who might be able to help you find the right people. From nobody Thu Feb 5 11:21:55 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E53B31A8A87 for ; Thu, 5 Feb 2015 11:21:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.902 X-Spam-Level: X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=unavailable Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwn65V0qYfC0 for ; Thu, 5 Feb 2015 11:21:42 -0800 (PST) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0071.outbound.protection.outlook.com [65.55.169.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD2AD1A8A8E for ; Thu, 5 Feb 2015 11:21:41 -0800 (PST) Received: from [192.168.0.13] (72.237.59.193) by CO1PR06MB238.namprd06.prod.outlook.com (10.242.166.144) with Microsoft SMTP Server (TLS) id 15.1.75.20; Thu, 5 Feb 2015 19:21:29 +0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Ray Pelletier In-Reply-To: <54D3B836.6050407@isode.com> Date: Thu, 5 Feb 2015 14:22:46 -0500 Content-Transfer-Encoding: quoted-printable Message-ID: <11F96F2A-9685-40A4-BAE3-C1DD8FE5C15F@isoc.org> References: <54D3AF3A.6080503@rfc-editor.org> <54D3B836.6050407@isode.com> To: Alexey Melnikov X-Mailer: Apple Mail (2.2070.6) X-Originating-IP: [72.237.59.193] X-ClientProxiedBy: BY1PR0201CA0037.namprd02.prod.outlook.com (25.160.191.175) To CO1PR06MB238.namprd06.prod.outlook.com (10.242.166.144) Authentication-Results: isode.com; dkim=none (message not signed) header.d=none; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:CO1PR06MB238; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:CO1PR06MB238; X-Forefront-PRVS: 0478C23FE0 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(6049001)(51704005)(377454003)(479174004)(19580405001)(23726002)(82746002)(19580395003)(83716003)(110136001)(122386002)(66066001)(50466002)(40100003)(47776003)(50986999)(76176999)(46406003)(57306001)(33656002)(86362001)(92566002)(50226001)(97756001)(42186005)(77096005)(15975445007)(46102003)(117156001)(36756003)(87976001)(77156002)(62966003)(2950100001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR06MB238; H:[192.168.0.13]; FPR:; SPF:None; MLV:sfv; LANG:en; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:CO1PR06MB238; X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Feb 2015 19:21:29.2175 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR06MB238 Archived-At: Cc: rsoc@iab.org, IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] [Rsoc] Report: RFI - Fonts for PDF RFCs X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 19:21:43 -0000 > On Feb 5, 2015, at 1:36 PM, Alexey Melnikov = wrote: >=20 >=20 > On 05/02/2015 17:58, Heather Flanagan (RFC Series Editor) wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >>=20 >>=20 >> (fixed RSOC address) >>=20 >> I'd rather not do option 3 if we can avoid it. I don't think the >> (probable) expense is worth the effort if other options are = available. >> Option 1 is something we can fall back on if all else fails (for now) >> but this doesn't have to be a permanent choice. It can be what we do >> for now, and we can change this when fonts become available. I think >> that's the right place to start. > Your plan looks good to me. >> And while we have that as our default, >> we can talk to the fine folks at Google (does anyone have a good = contact >> within the Noto project?) about a set of monospace variants. > I don't know of any, but there are some Google people who are active = in IETF (Harald Alvestrand and Ted Hardie) who might be able to help you = find the right people. As well as Warren Kumari and Vint Cerf. Google has a vested interest in maintaining and expanding Noto as needed = and=20 likely would consider monospace needs. Ray >=20 > _______________________________________________ > Rsoc mailing list > Rsoc@iab.org > https://www.iab.org/mailman/listinfo/rsoc From nobody Mon Feb 9 14:28:57 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2201A1A48 for ; Mon, 9 Feb 2015 13:55:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.588 X-Spam-Level: X-Spam-Status: No, score=-103.588 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=unavailable Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ucFD3jSe9pos for ; Mon, 9 Feb 2015 13:55:06 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id F30961A6EF2 for ; Mon, 9 Feb 2015 13:55:05 -0800 (PST) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 60BC51E5A1B for ; Mon, 9 Feb 2015 13:54:24 -0800 (PST) Received: from mail-qa0-f50.google.com (mail-qa0-f50.google.com [209.85.216.50]) by c8a.amsl.com (Postfix) with ESMTPSA id 3208C1E5A1E for ; Mon, 9 Feb 2015 13:54:24 -0800 (PST) Received: by mail-qa0-f50.google.com with SMTP id f12so4882924qad.9 for ; Mon, 09 Feb 2015 13:55:03 -0800 (PST) X-Received: by 10.140.35.240 with SMTP id n103mr43236247qgn.11.1423518903859; Mon, 09 Feb 2015 13:55:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.96.189.3 with HTTP; Mon, 9 Feb 2015 13:54:43 -0800 (PST) From: Glen Date: Mon, 9 Feb 2015 13:54:43 -0800 Message-ID: To: ietf@ietf.org, ietf-announce@ietf.org, IAOC , IESG , IAB , wgchairs@ietf.org Content-Type: multipart/alternative; boundary=001a11c04006988184050eaed2c6 Archived-At: X-Mailman-Approved-At: Mon, 09 Feb 2015 14:02:02 -0800 Subject: [TOOLS-DEVELOPMENT] IETF Scheduled Maintenance Outage X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: glen@amsl.com List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 21:55:11 -0000 --001a11c04006988184050eaed2c6 Content-Type: text/plain; charset=UTF-8 Dear IETF - We are planning to conduct a planned maintenance outage on Monday, February 16, beginning at 1PM PST (4PM EST, 9PM GMT). This outage will allow us to upgrade the memory in the primary IETF production server from 32GB to 128GB. The memory on the backup IETF server in Orlando has already been upgraded, and based on that experience it is expected that the upgrade to the primary server in Sunnyvale should take less than 30 minutes. During the outage, the primary IETF website will continue to be served by CloudFlare without interruption. List traffic will be delayed, but list messages will not be lost. The Datatracker, Mailman, the archive tool, Jabber, RSYNC, and FTP will be offline and unavailable. We feel that this memory upgrade will bring significant speed and performance improvements to the IETF's operations, and that it is important to complete this upgrade as soon as we are able. Please let me know if you have any questions, and thank you for your support and patience as we work to improve the IETF infrastructure. Glen Glen Barney IT Director AMS (IETF Secretariat) --001a11c04006988184050eaed2c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dear IETF -

We are planning to= conduct a=20 planned=20 maintenance outage on Monday, February 16, beginning at 1PM PST (4PM=20 EST, 9PM GMT).=C2=A0=C2=A0=20 This outage will allow us to upgrade the memory in the primary IETF=20 production server from 32GB to 128GB.=C2=A0 The memory on the backup IETF server in= =20 Orlando has already been upgraded, and based on that experience it is=20 expected that the upgrade to the primary server in Sunnyvale should take less than 30 minutes.

During the outage, the primary IETF website will continue to be served by CloudFlare without interruption.=C2= =A0 List traffic will be delayed, but list messages will not be lost.=C2=A0 Th= e=20 Datatracker, Mailman, the archive tool, Jabber, RSYNC, and FTP will be=20 offline and unavailable.=C2=A0

We feel that this memory upgrade wil= l bring significant speed and performance improvements to the=20 IETF's operations, and that it is important to complete this upgrade as= =20 soon as we are able.=C2=A0

Please let me know if you have any= =20 questions, and thank you for your support and patience as we work to=20 improve the IETF infrastructure.

Glen
Glen Barney
IT Dir= ector
AMS (IETF Secretariat)
--001a11c04006988184050eaed2c6-- From nobody Tue Feb 10 08:37:22 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40A791A1AA8 for ; Tue, 10 Feb 2015 08:37:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wcDd3GtkCFQ4 for ; Tue, 10 Feb 2015 08:37:10 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4A7A1A1AAF for ; Tue, 10 Feb 2015 08:37:07 -0800 (PST) Received: from unnumerable.local (pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id t1AGb6eY092132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 10 Feb 2015 10:37:07 -0600 (CST) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228] claimed to be unnumerable.local Message-ID: <54DA33AE.4040308@nostrum.com> Date: Tue, 10 Feb 2015 10:37:02 -0600 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: IETF Tools Development Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 16:37:13 -0000 On the last tools call, Matt reported that the issue with editing/deleting events on calendars had been addressed, and we asked for a round of testing with Ray and the secretariat. Do we have any conclusions from that testing yet? A few meetings before that, we identified that some work was needed to automate the creation and maintenance of the configuration before creating calendars for a large number of entities (such as for every working group). Has any progress been made on that? RjS From nobody Tue Feb 10 08:52:11 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DCD41A908C for ; Tue, 10 Feb 2015 08:52:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7hiabGAE0bBF for ; Tue, 10 Feb 2015 08:52:07 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA251A90CA for ; Tue, 10 Feb 2015 08:48:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A67C91E5A29; Tue, 10 Feb 2015 08:48:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tKhxKrbY93Rk; Tue, 10 Feb 2015 08:48:04 -0800 (PST) Received: from [IPv6:2601:9:3400:c69:6975:7162:8a95:cabf] (unknown [IPv6:2601:9:3400:c69:6975:7162:8a95:cabf]) by c8a.amsl.com (Postfix) with ESMTPA id 82F9A1E5A28; Tue, 10 Feb 2015 08:48:04 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Alexa Morris In-Reply-To: <54DA33AE.4040308@nostrum.com> Date: Tue, 10 Feb 2015 08:48:48 -0800 Content-Transfer-Encoding: quoted-printable Sendlaterdate: Tue, 10 Feb 2015 08:48:48 -0800 Message-Id: References: <54DA33AE.4040308@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.1878.6) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 16:52:09 -0000 Robert, I am not completely sure where things stand with Ray and the calendar = testing =97 last I heard he was still experiencing issues. I can tell = you that last Friday, Matt, Amy, Cindy and I spent some time testing the = features out on three different versions of Calendar, and we discovered = that there were some issues (with what CalDav does to the =93default" = calendar) in version 4.04. Other versions we tested worked well. It=92s = easy enough to upgrade Cindy and Amy (who were running 4.04) but it=92s = something that we need to keep in mind if/when we deploy this more = widely. What that also made us realize is that we need to expand our testing, = and this week we plan to try this out in the Windows environment. If the = CalDav software proves to be particularly fickle, we may need to = reexamine whether it=92s the right path forward.=20 Alexa On Feb 10, 2015, at 8:37 AM, Robert Sparks wrote: > On the last tools call, Matt reported that the issue with = editing/deleting events on calendars had been addressed, and we asked = for a round of testing with Ray and the secretariat. Do we have any = conclusions from that testing yet? >=20 > A few meetings before that, we identified that some work was needed to = automate the creation and maintenance of the configuration before = creating calendars for a large number of entities (such as for every = working group). Has any progress been made on that? >=20 > RjS >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development >=20 ---------- Alexa Morris / Executive Director / IETF 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 Phone: +1.510.492.4089 / Fax: +1.510.492.4001 Email: amorris@amsl.com Managed by Association Management Solutions (AMS) Forum Management, Meeting and Event Planning www.amsl.com From nobody Tue Feb 10 09:19:07 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8C41A913D for ; Tue, 10 Feb 2015 09:19:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhz1VzSDdXUR for ; Tue, 10 Feb 2015 09:19:03 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87AF31A9108 for ; Tue, 10 Feb 2015 09:18:23 -0800 (PST) Received: from unnumerable.local (pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id t1AHIMJ2095480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 10 Feb 2015 11:18:23 -0600 (CST) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228] claimed to be unnumerable.local Message-ID: <54DA3D59.9020206@nostrum.com> Date: Tue, 10 Feb 2015 11:18:17 -0600 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: IETF Tools Development Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [TOOLS-DEVELOPMENT] Serious question: Can we turn off FTP? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 17:19:04 -0000 All - While Henrik and I are working on normalizing how we expose things over http, rsync, and ftp, it occurs to me that this is a good time to challenge if we really need to continue providing ftp access to the things we're exposing. We are going to make sure everything that can currently be retrieved via ftp is available through both http and rsync. It would make maintaining the various archives simpler (the ftp daemon we're using puts some hard constraints on how we organize things on disk. Modern rsync and http daemons are far more flexible.) Scott - I expect you to be more sensitive to this than most. Would you be willing to convert the things you currently have using ftp to use rsync? RjS From nobody Tue Feb 10 09:37:12 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7231A1AE7 for ; Tue, 10 Feb 2015 09:37:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.897 X-Spam-Level: X-Spam-Status: No, score=0.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XoxFIyekMZoO for ; Tue, 10 Feb 2015 09:37:06 -0800 (PST) Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id E852A1A1A90 for ; Tue, 10 Feb 2015 09:36:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 417D212B7353; Tue, 10 Feb 2015 12:36:58 -0500 (EST) X-Virus-Scanned: amavisd-new at sobco.com Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TvF9La7bJ-b; Tue, 10 Feb 2015 12:36:57 -0500 (EST) Received: from [172.19.248.34] (unknown [64.88.227.134]) by sobco.sobco.com (Postfix) with ESMTPSA id 7929E12B7349; Tue, 10 Feb 2015 12:36:53 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: "Scott O. Bradner" In-Reply-To: <54DA3D59.9020206@nostrum.com> Date: Tue, 10 Feb 2015 12:36:22 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <03CC90C9-BA16-4CAB-A424-12AAE9B54037@sobco.com> References: <54DA3D59.9020206@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.2070.6) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Serious question: Can we turn off FTP? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 17:37:07 -0000 I could try - but the ftp url is rather well known so it would not be = just me with the new =E2=80=98all-id=E2=80=99 repository I could try rsync - = before I am not sure that it would have done what I want (to get all IDs)=20 do we have, or can we get, stats to see how much the ftp access is used? Scott > On Feb 10, 2015, at 12:18 PM, Robert Sparks = wrote: >=20 > All - >=20 > While Henrik and I are working on normalizing how we expose things = over http, rsync, and ftp, it occurs to me that this is a good time to = challenge if we really need to continue providing ftp access to the = things we're exposing. >=20 > We are going to make sure everything that can currently be retrieved = via ftp is available through both http and rsync. >=20 > It would make maintaining the various archives simpler (the ftp daemon = we're using puts some hard constraints on how we organize things on = disk. Modern rsync and http daemons are far more flexible.) >=20 > Scott - I expect you to be more sensitive to this than most. Would you = be willing to convert the things you currently have using ftp to use = rsync? >=20 > RjS >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Tue Feb 10 09:37:46 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F80F1A1A90 for ; Tue, 10 Feb 2015 09:37:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.81 X-Spam-Level: X-Spam-Status: No, score=-2.81 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-1tQe9LoyBR for ; Tue, 10 Feb 2015 09:37:40 -0800 (PST) Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FBE21A1A63 for ; Tue, 10 Feb 2015 09:37:40 -0800 (PST) Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-7.2.4-2) over TLS secured channel with ESMTP id 2e14ad45.0.892169.00-2266.2518596.nbfkord-smmo06.seg.att.com (envelope-from ); Tue, 10 Feb 2015 17:37:40 +0000 (UTC) X-MXL-Hash: 54da41e47457a227-30a06546c09fbfd81ddd77137fe17068adf065f3 Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1AHbbKv029427 for ; Tue, 10 Feb 2015 12:37:37 -0500 Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1AHbSjn029253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 10 Feb 2015 12:37:30 -0500 Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi132.aldc.att.com (RSA Interceptor) for ; Tue, 10 Feb 2015 17:37:16 GMT Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1AHbGUp019261 for ; Tue, 10 Feb 2015 12:37:16 -0500 Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1AHbAAX018914 for ; Tue, 10 Feb 2015 12:37:10 -0500 Received: from azcdtl01sb226e.itservices.sbc.com (azcdtl01sb226e.itservices.sbc.com?[135.110.240.193](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20150210173709gw1000ce96e>; Tue, 10 Feb 2015 17:37:10 +0000 X-Originating-IP: [135.110.240.193] Message-ID: <54DA41C5.5000606@att.com> Date: Tue, 10 Feb 2015 12:37:09 -0500 From: Tony Hansen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: IETF Tools Development References: <54DA3D59.9020206@nostrum.com> In-Reply-To: <54DA3D59.9020206@nostrum.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-RSA-Inspected: yes X-RSA-Classifications: public X-AnalysisOut: [v=2.0 cv=ApVZKpBP c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a] X-AnalysisOut: [=mJp9S24oyUUA:10 a=6IHl18L4XdkA:10 a=BLceEmwcHowA:10 a=N65] X-AnalysisOut: [9UExz7-8A:10 a=zQP7CpKOAAAA:8 a=0HtSIViG9nkA:10 a=G_pQWaml] X-AnalysisOut: [cestYZsZsOUA:9 a=pILNOxqGKmIA:10] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)] X-MAIL-FROM: X-SOURCE-IP: [144.160.229.23] Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Serious question: Can we turn off FTP? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 17:37:42 -0000 On 2/10/15 12:18 PM, Robert Sparks wrote: > All - > > While Henrik and I are working on normalizing how we expose things > over http, rsync, and ftp, it occurs to me that this is a good time to > challenge if we really need to continue providing ftp access to the > things we're exposing. > > We are going to make sure everything that can currently be retrieved > via ftp is available through both http and rsync. > > It would make maintaining the various archives simpler (the ftp daemon > we're using puts some hard constraints on how we organize things on > disk. Modern rsync and http daemons are far more flexible.) > > Scott - I expect you to be more sensitive to this than most. Would you > be willing to convert the things you currently have using ftp to use > rsync? An argument against: For my automated scripts, I tend to use rsync these days. However, when I'm looking manually, I still use FTP. HTTP is a virtual layer that may or may not map into the actual files, and may or may not (usually not) let you get lists of the files that are available. However, FTP gives you direct access to the file structure itself. Tony From nobody Tue Feb 10 09:50:32 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 049481A1A17 for ; Tue, 10 Feb 2015 09:50:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pFRqHbtOEkMR for ; Tue, 10 Feb 2015 09:50:28 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F8441A1ABE for ; Tue, 10 Feb 2015 09:50:28 -0800 (PST) Received: from unnumerable.local (pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id t1AHoR5B097907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 10 Feb 2015 11:50:27 -0600 (CST) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228] claimed to be unnumerable.local Message-ID: <54DA44DE.2090608@nostrum.com> Date: Tue, 10 Feb 2015 11:50:22 -0600 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: tools-development@ietf.org References: <54DA3D59.9020206@nostrum.com> <54DA41C5.5000606@att.com> In-Reply-To: <54DA41C5.5000606@att.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Serious question: Can we turn off FTP? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 17:50:30 -0000 On 2/10/15 11:37 AM, Tony Hansen wrote: > On 2/10/15 12:18 PM, Robert Sparks wrote: >> All - >> >> While Henrik and I are working on normalizing how we expose things >> over http, rsync, and ftp, it occurs to me that this is a good time >> to challenge if we really need to continue providing ftp access to >> the things we're exposing. >> >> We are going to make sure everything that can currently be retrieved >> via ftp is available through both http and rsync. >> >> It would make maintaining the various archives simpler (the ftp >> daemon we're using puts some hard constraints on how we organize >> things on disk. Modern rsync and http daemons are far more flexible.) >> >> Scott - I expect you to be more sensitive to this than most. Would >> you be willing to convert the things you currently have using ftp to >> use rsync? > > An argument against: > > For my automated scripts, I tend to use rsync these days. However, > when I'm looking manually, I still use FTP. HTTP is a virtual layer > that may or may not map into the actual files, and may or may not > (usually not) let you get lists of the files that are available. > However, FTP gives you direct access to the file structure itself. If we made sure http provided this index would it fulfill the need? > > Tony > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Tue Feb 10 10:41:21 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 427EF1A1B8F for ; Tue, 10 Feb 2015 10:41:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.211 X-Spam-Level: X-Spam-Status: No, score=-6.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYxLOr3Wc-yd for ; Tue, 10 Feb 2015 10:41:10 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB391A1BC6 for ; Tue, 10 Feb 2015 10:40:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 1421B1E5A1E; Tue, 10 Feb 2015 10:40:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WINQjQ7snU07; Tue, 10 Feb 2015 10:40:07 -0800 (PST) Received: from [192.168.0.10] (68-204-56-146.res.bhn.net [68.204.56.146]) by c8a.amsl.com (Postfix) with ESMTPA id B8E031E5A13; Tue, 10 Feb 2015 10:40:06 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Matt Larson In-Reply-To: <54DA33AE.4040308@nostrum.com> Date: Tue, 10 Feb 2015 13:40:51 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> References: <54DA33AE.4040308@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.2070.6) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 18:41:15 -0000 > On Feb 10, 2015, at 11:37 AM, Robert Sparks = wrote: >=20 > On the last tools call, Matt reported that the issue with = editing/deleting events on calendars had been addressed, and we asked = for a round of testing with Ray and the secretariat. Do we have any = conclusions from that testing yet? Hi Robert, We are still testing. My last report from Ray was that his last = calendar item change attempt worked, which was a major step forward. We = are still working with Cindy and Amy to to further testing with the IAB = and IESG calendars. As that has progressed, we have discovered an issue = with the version of Apple's iCal they are running (4.0.4). That = version, for some reason, assigns every .ics invitation they receive to = the IAB calendar and will not allow them to change the calendar = assignment. Alexa and I, on later versions of Apple iCal, do not = experience this issue. As Alexa noted in her response, we are also going to be doing testing = with other clients under Mac OS and other operating systems. We want to = make sure there is a reasonable selection of clients which will work = with the server installation. > A few meetings before that, we identified that some work was needed to = automate the creation and maintenance of the configuration before = creating calendars for a large number of entities (such as for every = working group). Has any progress been made on that? I have not examined this in detail yet, as I want to make sure we have a = viable server package in place first. =20 Matt ------------------------------------------- Matthew Larson, Asst. IT Director Association Management Solutions Forum Management, Meeting and Event Planning 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 http://www.amsl.com From nobody Tue Feb 10 12:56:24 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 419CE1A1BFB for ; Tue, 10 Feb 2015 12:56:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9sdXGCahTHTq for ; Tue, 10 Feb 2015 12:56:14 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 996191A1C02 for ; Tue, 10 Feb 2015 12:56:14 -0800 (PST) Received: from unnumerable.local (pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id t1AKuCGk012439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 Feb 2015 14:56:13 -0600 (CST) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228] claimed to be unnumerable.local Message-ID: <54DA7068.1020004@nostrum.com> Date: Tue, 10 Feb 2015 14:56:08 -0600 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "Scott O. Bradner" References: <54DA3D59.9020206@nostrum.com> <03CC90C9-BA16-4CAB-A424-12AAE9B54037@sobco.com> In-Reply-To: <03CC90C9-BA16-4CAB-A424-12AAE9B54037@sobco.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Serious question: Can we turn off FTP? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 20:56:18 -0000 On 2/10/15 11:36 AM, Scott O. Bradner wrote: > I could try - but the ftp url is rather well known so it would not be just me > > with the new ‘all-id’ repository I could try rsync - before I am not sure that it would have done what I want (to > get all IDs) > > do we have, or can we get, stats to see how much the ftp access is used? AFAICT, we have logs that go back about a week. In the last week it's averaged about 4200 transfers/day, from about 1000 different endpoints. It looks like the vast majority of the ftp accesses are to the rfc and draft archives. There's a lot of bot activity in there (about 5% is googlebot), but there's stuff that doesn't look bot-like. RjS > > Scott > >> On Feb 10, 2015, at 12:18 PM, Robert Sparks wrote: >> >> All - >> >> While Henrik and I are working on normalizing how we expose things over http, rsync, and ftp, it occurs to me that this is a good time to challenge if we really need to continue providing ftp access to the things we're exposing. >> >> We are going to make sure everything that can currently be retrieved via ftp is available through both http and rsync. >> >> It would make maintaining the various archives simpler (the ftp daemon we're using puts some hard constraints on how we organize things on disk. Modern rsync and http daemons are far more flexible.) >> >> Scott - I expect you to be more sensitive to this than most. Would you be willing to convert the things you currently have using ftp to use rsync? >> >> RjS >> >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development From nobody Tue Feb 10 13:15:50 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3668F1A1BEA for ; Tue, 10 Feb 2015 13:15:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id moaoPvnoUe6R for ; Tue, 10 Feb 2015 13:15:37 -0800 (PST) Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E66F41A01F4 for ; Tue, 10 Feb 2015 13:15:36 -0800 (PST) Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-7.2.4-2) over TLS secured channel with ESMTP id 8f47ad45.0.1072798.00-2337.2997366.nbfkord-smmo06.seg.att.com (envelope-from ); Tue, 10 Feb 2015 21:15:36 +0000 (UTC) X-MXL-Hash: 54da74f83d5b1772-0c453aa3ba96bcfb5aa17b0d03f2e6385093669a Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1ALFZQv027019 for ; Tue, 10 Feb 2015 16:15:35 -0500 Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1ALFWG3026987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 10 Feb 2015 16:15:33 -0500 Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi131.aldc.att.com (RSA Interceptor) for ; Tue, 10 Feb 2015 21:15:18 GMT Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1ALFIqP012106 for ; Tue, 10 Feb 2015 16:15:18 -0500 Received: from dns.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1ALFB5A011156 for ; Tue, 10 Feb 2015 16:15:11 -0500 Received: from tonys-macbook-pro.local (unknown[135.110.240.140](untrusted sender)) by maillennium.att.com (mailgw1) with ESMTP id <20150210211510gw1000ce9he>; Tue, 10 Feb 2015 21:15:11 +0000 X-Originating-IP: [135.110.240.140] Message-ID: <54DA74DC.3020402@att.com> Date: Tue, 10 Feb 2015 16:15:08 -0500 From: Tony Hansen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: tools-development@ietf.org References: <54DA3D59.9020206@nostrum.com> <54DA41C5.5000606@att.com> <54DA44DE.2090608@nostrum.com> In-Reply-To: <54DA44DE.2090608@nostrum.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-RSA-Inspected: yes X-RSA-Classifications: public X-AnalysisOut: [v=2.0 cv=ApVZKpBP c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a] X-AnalysisOut: [=mJp9S24oyUUA:10 a=AbuM1IKGh0sA:10 a=BLceEmwcHowA:10 a=N65] X-AnalysisOut: [9UExz7-8A:10 a=zQP7CpKOAAAA:8 a=0HtSIViG9nkA:10 a=FI9R2qFx] X-AnalysisOut: [adPpjbFAU68A:9 a=pILNOxqGKmIA:10] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)] X-MAIL-FROM: X-SOURCE-IP: [144.160.229.23] Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Serious question: Can we turn off FTP? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 21:15:42 -0000 On 2/10/15 12:50 PM, Robert Sparks wrote: > > On 2/10/15 11:37 AM, Tony Hansen wrote: >> An argument against: >> >> For my automated scripts, I tend to use rsync these days. However, >> when I'm looking manually, I still use FTP. HTTP is a virtual layer >> that may or may not map into the actual files, and may or may not >> (usually not) let you get lists of the files that are available. >> However, FTP gives you direct access to the file structure itself. > If we made sure http provided this index would it fulfill the need? Possibly. Probably. Why not put up an http link .../files that points at the top of what is the current ftp tree and has indexing available? Then we could try it. You might even set up an FTP banner that's displayed when a user connects to the FTP server that advertises that alternate http access point. Tony Hansen From nobody Tue Feb 10 13:20:50 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B35E51A040B for ; Tue, 10 Feb 2015 13:20:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.232 X-Spam-Level: X-Spam-Status: No, score=0.232 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9SnMOh55rR1X for ; Tue, 10 Feb 2015 13:20:34 -0800 (PST) Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) by ietfa.amsl.com (Postfix) with SMTP id 634FC1A1A2E for ; Tue, 10 Feb 2015 13:20:00 -0800 (PST) Received: (qmail 8822 invoked by uid 0); 10 Feb 2015 21:19:59 -0000 Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy2.mail.unifiedlayer.com with SMTP; 10 Feb 2015 21:19:59 -0000 Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with id qlJd1p00D2SSUrH01lKZPN; Tue, 10 Feb 2015 14:19:36 -0700 X-Authority-Analysis: v=2.1 cv=NPZGpSKg c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=hUXq7yzdp1YA:10 a=N659UExz7-8A:10 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=0HtSIViG9nkA:10 a=-zVcu1j2prZp41y-H24A:9 a=pILNOxqGKmIA:10 a=xKRVBG_H5voA:10 a=x2ZUorHGiagA:10 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=nJ2YE/FIpIG0i4Q9R/TIuIJhGPnOE/kn4rxa7maz89c=; b=rXwZp91zo8VXHumcYyLyCzex6hMs/QJ6tI9q2gWkIsoZvqI8ywkB/tg5MopkJCFDH9KY5zX4/wUoDIFBHBqHWJ7UQrMQ2IkzvmY7gY/5lju0Jf3hcpWedGj3veNioha0; Received: from box313.bluehost.com ([69.89.31.113]:32806 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.82) (envelope-from ) id 1YLFhT-0005dW-Cl; Tue, 10 Feb 2015 11:38:19 -0700 Message-ID: <54DA5018.70007@labn.net> Date: Tue, 10 Feb 2015 13:38:16 -0500 From: Lou Berger User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Robert Sparks References: <54DA3D59.9020206@nostrum.com> In-Reply-To: <54DA3D59.9020206@nostrum.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net} Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Serious question: Can we turn off FTP? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 21:20:35 -0000 [warning: new lurker on list!] On 02/10/2015 12:18 PM, Robert Sparks wrote: > > While Henrik and I are working on normalizing how we expose things over > http, rsync, and ftp, it occurs to me that this is a good time to > challenge if we really need to continue providing ftp access to the > things we're exposing. What do the logs show in terms of current usage? BTW I was one of the FTP users until ~1 year ago when I switched my scripts to rsync... Lou From nobody Tue Feb 10 21:49:08 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2C11A7006 for ; Tue, 10 Feb 2015 21:49:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.9 X-Spam-Level: X-Spam-Status: No, score=-103.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qzwwGp_tXv2n for ; Tue, 10 Feb 2015 21:49:02 -0800 (PST) Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC831A1BAE for ; Tue, 10 Feb 2015 21:49:01 -0800 (PST) Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id CCAB49A400D; Wed, 11 Feb 2015 00:48:50 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id sWLWRN48VT+k; Wed, 11 Feb 2015 00:48:27 -0500 (EST) Received: from [10.196.207.51] (30-193.icannmeeting.org [199.91.193.30]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id E40F49A4009; Wed, 11 Feb 2015 00:48:25 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Russ Housley In-Reply-To: <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> Date: Wed, 11 Feb 2015 00:48:10 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> To: Matt Larson X-Mailer: Apple Mail (2.1085) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 05:49:05 -0000 I'd really like to announce WG calendars before Dallas. It seems to me = that an issue with one version of one client is not a reason to delay = deployment and announcement. Russ On Feb 10, 2015, at 1:40 PM, Matt Larson wrote: >> On Feb 10, 2015, at 11:37 AM, Robert Sparks = wrote: >>=20 >> On the last tools call, Matt reported that the issue with = editing/deleting events on calendars had been addressed, and we asked = for a round of testing with Ray and the secretariat. Do we have any = conclusions from that testing yet? >=20 > Hi Robert, >=20 > We are still testing. My last report from Ray was that his last = calendar item change attempt worked, which was a major step forward. We = are still working with Cindy and Amy to to further testing with the IAB = and IESG calendars. As that has progressed, we have discovered an issue = with the version of Apple's iCal they are running (4.0.4). That = version, for some reason, assigns every .ics invitation they receive to = the IAB calendar and will not allow them to change the calendar = assignment. Alexa and I, on later versions of Apple iCal, do not = experience this issue. >=20 > As Alexa noted in her response, we are also going to be doing testing = with other clients under Mac OS and other operating systems. We want to = make sure there is a reasonable selection of clients which will work = with the server installation. >=20 >=20 >> A few meetings before that, we identified that some work was needed = to automate the creation and maintenance of the configuration before = creating calendars for a large number of entities (such as for every = working group). Has any progress been made on that? >=20 > I have not examined this in detail yet, as I want to make sure we have = a viable server package in place first. =20 >=20 > Matt >=20 > ------------------------------------------- > Matthew Larson, Asst. IT Director > Association Management Solutions > Forum Management, Meeting and Event Planning > 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 > http://www.amsl.com >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Wed Feb 11 00:28:44 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7101F1A0075 for ; Wed, 11 Feb 2015 00:28:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QmSexNVv9L5B for ; Wed, 11 Feb 2015 00:28:38 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FD651A870C for ; Wed, 11 Feb 2015 00:28:38 -0800 (PST) Received: from [192.168.2.175] ([93.217.119.132]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MaE4a-1Y1jwi0tlA-00JtSj; Wed, 11 Feb 2015 09:28:28 +0100 Message-ID: <54DB12A9.4000106@gmx.de> Date: Wed, 11 Feb 2015 09:28:25 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Robert Sparks , tools-development@ietf.org References: <54DA3D59.9020206@nostrum.com> <54DA41C5.5000606@att.com> <54DA44DE.2090608@nostrum.com> In-Reply-To: <54DA44DE.2090608@nostrum.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:2rS5TqhnB1u88dTERwZHlzesH1BECTBbNwmC/WP/1ORneZTDovh vyz8+VT5mlAwbl+oo9WZmpHyemkrmUc31yAvf9pW7S4STEJLngoC8n0KlQmm+MDtdv2BQym rtxfzoM+/fj81O8IEJTUfXLF+tiy73GR30lLRtUTTF1VUYROFmNYNNDZIjeaC2j9NfKOFCc vT2+SDVe0VSVnumDz93rw== X-UI-Out-Filterresults: notjunk:1; Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Serious question: Can we turn off FTP? X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 08:28:40 -0000 On 2015-02-10 18:50, Robert Sparks wrote: >> An argument against: >> >> For my automated scripts, I tend to use rsync these days. However, >> when I'm looking manually, I still use FTP. HTTP is a virtual layer >> that may or may not map into the actual files, and may or may not >> (usually not) let you get lists of the files that are available. >> However, FTP gives you direct access to the file structure itself. > If we made sure http provided this index would it fulfill the need? Or turn on WebDAV (read-only)? Best regards, Julian From nobody Wed Feb 11 13:50:52 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E961A6F02 for ; Wed, 11 Feb 2015 13:50:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.911 X-Spam-Level: X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OoYrJ_nZcSuD for ; Wed, 11 Feb 2015 13:50:48 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 938DB1A1BC6 for ; Wed, 11 Feb 2015 13:50:48 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id DE7611E5A25; Wed, 11 Feb 2015 13:49:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oz56XeSF1aCv; Wed, 11 Feb 2015 13:49:58 -0800 (PST) Received: from [192.168.0.10] (68-204-56-146.res.bhn.net [68.204.56.146]) by c8a.amsl.com (Postfix) with ESMTPA id 8DF521E5A1F; Wed, 11 Feb 2015 13:49:58 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Matt Larson In-Reply-To: Date: Wed, 11 Feb 2015 16:50:47 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> To: Russ Housley X-Mailer: Apple Mail (2.2070.6) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 21:50:51 -0000 Hi all, We are in the process of getting Amy and Cindy either upgraded, or set = up with some alternative calendar client software, so that they can = continue operational testing with the IAB and IESG calendars on the = CAVDav server. Meanwhile, I would like to suggest that we identify a couple of working = groups that might be interested in using the calendar server to include = as test groups, so that we can see how the server is going to do with a = wider user base. Can you suggest a few working groups whose chairs = might be interested in testing this out for us with their groups? In the meantime, I will be working on code for creating calendar = accounts in bulk, so that our clerical staff doesn't have to create them = all. (I plan to look at the possibility of automatic integration with = the Datatracker when I can spend some time with the Tools Team, = hopefully at the Dallas meeting.) I'll keep you all informed as to my progress over the next couple of = days! Matt > On Feb 11, 2015, at 12:48 AM, Russ Housley = wrote: >=20 > I'd really like to announce WG calendars before Dallas. It seems to = me that an issue with one version of one client is not a reason to delay = deployment and announcement. >=20 > Russ >=20 >=20 > On Feb 10, 2015, at 1:40 PM, Matt Larson wrote: >=20 >>> On Feb 10, 2015, at 11:37 AM, Robert Sparks = wrote: >>>=20 >>> On the last tools call, Matt reported that the issue with = editing/deleting events on calendars had been addressed, and we asked = for a round of testing with Ray and the secretariat. Do we have any = conclusions from that testing yet? >>=20 >> Hi Robert, >>=20 >> We are still testing. My last report from Ray was that his last = calendar item change attempt worked, which was a major step forward. We = are still working with Cindy and Amy to to further testing with the IAB = and IESG calendars. As that has progressed, we have discovered an issue = with the version of Apple's iCal they are running (4.0.4). That = version, for some reason, assigns every .ics invitation they receive to = the IAB calendar and will not allow them to change the calendar = assignment. Alexa and I, on later versions of Apple iCal, do not = experience this issue. >>=20 >> As Alexa noted in her response, we are also going to be doing testing = with other clients under Mac OS and other operating systems. We want to = make sure there is a reasonable selection of clients which will work = with the server installation. >>=20 >>=20 >>> A few meetings before that, we identified that some work was needed = to automate the creation and maintenance of the configuration before = creating calendars for a large number of entities (such as for every = working group). Has any progress been made on that? >>=20 >> I have not examined this in detail yet, as I want to make sure we = have a viable server package in place first. =20 >>=20 >> Matt >>=20 >> ------------------------------------------- >> Matthew Larson, Asst. IT Director >> Association Management Solutions >> Forum Management, Meeting and Event Planning >> 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 >> http://www.amsl.com >>=20 >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development >=20 ------------------------------------------- Matthew Larson, Asst. IT Director Association Management Solutions Forum Management, Meeting and Event Planning 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 http://www.amsl.com From nobody Wed Feb 11 15:09:35 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7119B1A8953 for ; Wed, 11 Feb 2015 15:09:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.122 X-Spam-Level: X-Spam-Status: No, score=0.122 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_BIZ=0.288, IP_NOT_FRIENDLY=0.334] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MtqIu2wl2Psr for ; Wed, 11 Feb 2015 15:09:07 -0800 (PST) Received: from newdragon.webhostserver.biz (newdragon.webhostserver.biz [69.25.136.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D670A1A8941 for ; Wed, 11 Feb 2015 15:08:41 -0800 (PST) Received: from localhost ([::1]:36981 helo=[127.0.0.1]) by newdragon.webhostserver.biz with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from ) id 1YLgOe-0001Fh-Vd; Thu, 12 Feb 2015 02:08:41 +0300 Message-ID: <54DBE0F7.6060109@labn.net> Date: Wed, 11 Feb 2015 18:08:39 -0500 From: Lou Berger User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Matt Larson References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> In-Reply-To: <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - newdragon.webhostserver.biz X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - labn.net X-Get-Message-Sender-Via: newdragon.webhostserver.biz: authenticated_id: lberger@blabn.com X-Source: X-Source-Args: X-Source-Dir: Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: lberger@labn.net List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 23:09:11 -0000 On 02/11/2015 04:50 PM, Matt Larson wrote: > Meanwhile, I would like to suggest that we identify a couple of > working groups that might be interested in using the calendar server > to include as test groups, so that we can see how the server is going > to do with a wider user base. Can you suggest a few working groups > whose chairs might be interested in testing this out for us with > their groups? Don't know if this has been covered before/discussed. What about having a calendar that shows all interims as a test case? I also bet that Sue Hares would be interested/willing. Lou From nobody Wed Feb 11 15:40:11 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 561B81A1A70 for ; Wed, 11 Feb 2015 15:40:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4 X-Spam-Level: X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFeE3-_6JmI6 for ; Wed, 11 Feb 2015 15:40:05 -0800 (PST) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2B281A1A48 for ; Wed, 11 Feb 2015 15:40:04 -0800 (PST) Received: by mail-ob0-f182.google.com with SMTP id nt9so6487671obb.13 for ; Wed, 11 Feb 2015 15:40:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=P3b+PBHGAQNreIt0sOyZJSaZ+eO5GRvsnN7Du+7tRdM=; b=qLrKOW9siQkaw/vqu/HdDNQDNBD63CDFiCdAg+25nJfpx+T3Y2AENa6ykDbK3DZ1W2 y993x4ZIeq0cOAqL4Dda8LBOeatxPAYUcY3fSZktlYdqrRPUDSb44IZXz/Znrsxrg3gk i723KJOWNJP6FMUwTtKVvxksnonljLa48KYGISmckJgW2Q7OwHkUH8pECbexJrrVsrBq h7TXHr+oPz7QXmyHR2Bst5x0Bd0RC1TbeXZjH5q2s3bkFvu8amc1K9hKYtAgc/PoEI45 cLc4zAmQtrt1eO3+NwDzJMRHp1EqFd6pwrOlRb3I/3imajrYxzN6FGPXyAG9iVmrb1ct zVwA== X-Received: by 10.202.77.75 with SMTP id a72mr675088oib.49.1423698004067; Wed, 11 Feb 2015 15:40:04 -0800 (PST) Received: from [10.5.2.168] ([61.8.205.5]) by mx.google.com with ESMTPSA id k9sm1224984obh.0.2015.02.11.15.40.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Feb 2015 15:40:02 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_59192958-375B-4759-93F2-0826C48FC12E"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b4 From: Bob Hinden In-Reply-To: <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> Date: Thu, 12 Feb 2015 07:39:45 +0800 Message-Id: References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> To: Matt Larson X-Mailer: Apple Mail (2.2070.6) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 23:40:08 -0000 --Apple-Mail=_59192958-375B-4759-93F2-0826C48FC12E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Matt, > On Feb 12, 2015, at 5:50 AM, Matt Larson wrote: >=20 > Hi all, >=20 > We are in the process of getting Amy and Cindy either upgraded, or set = up with some alternative calendar client software, so that they can = continue operational testing with the IAB and IESG calendars on the = CAVDav server. What versions of iCal and MacOS work and don=E2=80=99t work. >=20 > Meanwhile, I would like to suggest that we identify a couple of = working groups that might be interested in using the calendar server to = include as test groups, so that we can see how the server is going to do = with a wider user base. Can you suggest a few working groups whose = chairs might be interested in testing this out for us with their groups? I need to check with my co-chair, but I will volunteer 6MAN. Thanks, Bob >=20 > In the meantime, I will be working on code for creating calendar = accounts in bulk, so that our clerical staff doesn't have to create them = all. (I plan to look at the possibility of automatic integration with = the Datatracker when I can spend some time with the Tools Team, = hopefully at the Dallas meeting.) >=20 > I'll keep you all informed as to my progress over the next couple of = days! >=20 > Matt >=20 >> On Feb 11, 2015, at 12:48 AM, Russ Housley = wrote: >>=20 >> I'd really like to announce WG calendars before Dallas. It seems to = me that an issue with one version of one client is not a reason to delay = deployment and announcement. >>=20 >> Russ >>=20 >>=20 >> On Feb 10, 2015, at 1:40 PM, Matt Larson wrote: >>=20 >>>> On Feb 10, 2015, at 11:37 AM, Robert Sparks = wrote: >>>>=20 >>>> On the last tools call, Matt reported that the issue with = editing/deleting events on calendars had been addressed, and we asked = for a round of testing with Ray and the secretariat. Do we have any = conclusions from that testing yet? >>>=20 >>> Hi Robert, >>>=20 >>> We are still testing. My last report from Ray was that his last = calendar item change attempt worked, which was a major step forward. We = are still working with Cindy and Amy to to further testing with the IAB = and IESG calendars. As that has progressed, we have discovered an issue = with the version of Apple's iCal they are running (4.0.4). That = version, for some reason, assigns every .ics invitation they receive to = the IAB calendar and will not allow them to change the calendar = assignment. Alexa and I, on later versions of Apple iCal, do not = experience this issue. >>>=20 >>> As Alexa noted in her response, we are also going to be doing = testing with other clients under Mac OS and other operating systems. We = want to make sure there is a reasonable selection of clients which will = work with the server installation. >>>=20 >>>=20 >>>> A few meetings before that, we identified that some work was needed = to automate the creation and maintenance of the configuration before = creating calendars for a large number of entities (such as for every = working group). Has any progress been made on that? >>>=20 >>> I have not examined this in detail yet, as I want to make sure we = have a viable server package in place first. >>>=20 >>> Matt >>>=20 >>> ------------------------------------------- >>> Matthew Larson, Asst. IT Director >>> Association Management Solutions >>> Forum Management, Meeting and Event Planning >>> 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 >>> http://www.amsl.com >>>=20 >>> _______________________________________________ >>> TOOLS-DEVELOPMENT mailing list >>> TOOLS-DEVELOPMENT@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-development >>=20 >=20 > ------------------------------------------- > Matthew Larson, Asst. IT Director > Association Management Solutions > Forum Management, Meeting and Event Planning > 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 > http://www.amsl.com >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development --Apple-Mail=_59192958-375B-4759-93F2-0826C48FC12E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJU2+hBAAoJEK7rdBF357uoeuEIAKEUHci/RlVzCg8Ga/h5bLMk o4bGeA/uF0YujwO4wp47oVcF9ZzsU9ATZSz/h+4U8LJ8fe6bsczfNvdL2ZiXyecw v5+Llf4+gnTUlAGlufAKVh9Bgpnz0lAfIh7hxKIs2VyTCL0nM/dAyqV82amMRniG dQr/IB8SSgg76kFknMd5Rr2Vn2EEac+BiZiyxD0j/n2f3YcrAlGFhQtRgbQ2i4oe 4voHEHYAdlu8GQ+KTUHhpZlJOboHU8mTbJlRqq5gm8u4nijkcPuB87LU7exPOiMc sBttABzlomFubcaDPH8l4kKd953Y6LlmSqwqeYrS15Cs2WkyuH9vUmlax9SxxYk= =22AP -----END PGP SIGNATURE----- --Apple-Mail=_59192958-375B-4759-93F2-0826C48FC12E-- From nobody Wed Feb 11 16:32:56 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 137BA1A874E for ; Wed, 11 Feb 2015 16:32:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.9 X-Spam-Level: X-Spam-Status: No, score=-103.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KPg8ad_VkGPS for ; Wed, 11 Feb 2015 16:32:50 -0800 (PST) Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 16E661A874B for ; Wed, 11 Feb 2015 16:32:50 -0800 (PST) Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 3F3809A401B; Wed, 11 Feb 2015 19:32:39 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id sHH+CUYG+nCR; Wed, 11 Feb 2015 19:32:17 -0500 (EST) Received: from [10.196.213.217] (97-195.icannmeeting.org [199.91.195.97]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 92E259A4021; Wed, 11 Feb 2015 19:32:16 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Russ Housley In-Reply-To: <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> Date: Wed, 11 Feb 2015 19:32:01 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <0B114501-4979-47A2-8348-1871E46FF287@vigilsec.com> References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> To: Matt Larson X-Mailer: Apple Mail (2.1085) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 00:32:53 -0000 Robert Sparks and myself as STIR WG Chairs Sean Turner as TLS WG and RTCWEB WG Chair Heather Flanagan for RFC Editor-related calendars On Feb 11, 2015, at 4:50 PM, Matt Larson wrote: > Hi all, >=20 > We are in the process of getting Amy and Cindy either upgraded, or set = up with some alternative calendar client software, so that they can = continue operational testing with the IAB and IESG calendars on the = CAVDav server. >=20 > Meanwhile, I would like to suggest that we identify a couple of = working groups that might be interested in using the calendar server to = include as test groups, so that we can see how the server is going to do = with a wider user base. Can you suggest a few working groups whose = chairs might be interested in testing this out for us with their groups? >=20 > In the meantime, I will be working on code for creating calendar = accounts in bulk, so that our clerical staff doesn't have to create them = all. (I plan to look at the possibility of automatic integration with = the Datatracker when I can spend some time with the Tools Team, = hopefully at the Dallas meeting.) >=20 > I'll keep you all informed as to my progress over the next couple of = days! >=20 > Matt >=20 >> On Feb 11, 2015, at 12:48 AM, Russ Housley = wrote: >>=20 >> I'd really like to announce WG calendars before Dallas. It seems to = me that an issue with one version of one client is not a reason to delay = deployment and announcement. >>=20 >> Russ >>=20 >>=20 >> On Feb 10, 2015, at 1:40 PM, Matt Larson wrote: >>=20 >>>> On Feb 10, 2015, at 11:37 AM, Robert Sparks = wrote: >>>>=20 >>>> On the last tools call, Matt reported that the issue with = editing/deleting events on calendars had been addressed, and we asked = for a round of testing with Ray and the secretariat. Do we have any = conclusions from that testing yet? >>>=20 >>> Hi Robert, >>>=20 >>> We are still testing. My last report from Ray was that his last = calendar item change attempt worked, which was a major step forward. We = are still working with Cindy and Amy to to further testing with the IAB = and IESG calendars. As that has progressed, we have discovered an issue = with the version of Apple's iCal they are running (4.0.4). That = version, for some reason, assigns every .ics invitation they receive to = the IAB calendar and will not allow them to change the calendar = assignment. Alexa and I, on later versions of Apple iCal, do not = experience this issue. >>>=20 >>> As Alexa noted in her response, we are also going to be doing = testing with other clients under Mac OS and other operating systems. We = want to make sure there is a reasonable selection of clients which will = work with the server installation. >>>=20 >>>=20 >>>> A few meetings before that, we identified that some work was needed = to automate the creation and maintenance of the configuration before = creating calendars for a large number of entities (such as for every = working group). Has any progress been made on that? >>>=20 >>> I have not examined this in detail yet, as I want to make sure we = have a viable server package in place first. =20 >>>=20 >>> Matt >>>=20 >>> ------------------------------------------- >>> Matthew Larson, Asst. IT Director >>> Association Management Solutions >>> Forum Management, Meeting and Event Planning >>> 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 >>> http://www.amsl.com >>>=20 >>> _______________________________________________ >>> TOOLS-DEVELOPMENT mailing list >>> TOOLS-DEVELOPMENT@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-development >>=20 >=20 > ------------------------------------------- > Matthew Larson, Asst. IT Director > Association Management Solutions > Forum Management, Meeting and Event Planning > 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 > http://www.amsl.com >=20 From nobody Wed Feb 11 17:55:17 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA8501A8A14 for ; Wed, 11 Feb 2015 17:55:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h2SGNuU_5phy for ; Wed, 11 Feb 2015 17:55:11 -0800 (PST) Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 810A01A8A10 for ; Wed, 11 Feb 2015 17:55:11 -0800 (PST) Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 222CA9A4020; Wed, 11 Feb 2015 20:55:01 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id H95RtNSAHtvx; Wed, 11 Feb 2015 20:54:39 -0500 (EST) Received: from [5.5.33.238] (vpn.snozzages.com [204.42.252.17]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4B7289A4019; Wed, 11 Feb 2015 20:54:37 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Russ Housley In-Reply-To: <54DBE0F7.6060109@labn.net> Date: Wed, 11 Feb 2015 20:54:22 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> <54DBE0F7.6060109@labn.net> To: lberger@labn.net X-Mailer: Apple Mail (2.1085) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 01:55:14 -0000 Lou: We are working on a system where each WG will have an iCal managed by = the WG Chairs. Russ On Feb 11, 2015, at 6:08 PM, Lou Berger wrote: > On 02/11/2015 04:50 PM, Matt Larson wrote: >> Meanwhile, I would like to suggest that we identify a couple of >> working groups that might be interested in using the calendar server >> to include as test groups, so that we can see how the server is going >> to do with a wider user base. Can you suggest a few working groups >> whose chairs might be interested in testing this out for us with >> their groups? >=20 > Don't know if this has been covered before/discussed. What about = having > a calendar that shows all interims as a test case? >=20 > I also bet that Sue Hares would be = interested/willing. >=20 >=20 > Lou >=20 >=20 >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Wed Feb 11 18:11:06 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFE7B1A1BAA for ; Wed, 11 Feb 2015 18:10:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.667 X-Spam-Level: X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNhkrUAzruSK for ; Wed, 11 Feb 2015 18:10:49 -0800 (PST) Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) by ietfa.amsl.com (Postfix) with SMTP id 446061A1B60 for ; Wed, 11 Feb 2015 18:10:49 -0800 (PST) Received: (qmail 23856 invoked by uid 0); 12 Feb 2015 02:10:48 -0000 Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy2.mail.unifiedlayer.com with SMTP; 12 Feb 2015 02:10:48 -0000 Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with id rEAi1p00f2SSUrH01EAl3l; Wed, 11 Feb 2015 19:10:47 -0700 X-Authority-Analysis: v=2.1 cv=NPZGpSKg c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=Vhvw94NMJWsA:10 a=N659UExz7-8A:10 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=0HtSIViG9nkA:10 a=1sjgXBK7AAAA:8 a=48vgC7mUAAAA:8 a=3LGMvwkv18kf6eK3sEwA:9 a=pILNOxqGKmIA:10 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=I+5qdV8D4JytsaXvjiGAvQn+tAxJWFwSfXd3NaRS9Vk=; b=1k+zbiB8N5uzA/c6W6VZlxh/kBaQK3dWuQzbG9k0MgB9y3soCWjyQqAWWSkscqF8/newp4FcHttCo9X9jw19buTT9rnJueIre4BCJQLEPeYqaFNGVnuDjHdJWcXQZH9Z; Received: from box313.bluehost.com ([69.89.31.113]:45057 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.82) (envelope-from ) id 1YLjEo-0002pO-KO; Wed, 11 Feb 2015 19:10:42 -0700 Message-ID: <54DC0B95.8000305@labn.net> Date: Wed, 11 Feb 2015 21:10:29 -0500 From: Lou Berger User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Russ Housley References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> <54DBE0F7.6060109@labn.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net} Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 02:10:52 -0000 Russ, I did get that I was suggesting something slightly off topic. If you start thinking through some of the user-side scaling issues, I think you might reach the suggestion that I came up with. (I.e., do I really want/need a calendar for each of the ~7 WGs I track/participate in, no but something that allows me to easily see across WGs, say their interims, now that would be really helpful and replace something I'm doing now manually...) But feature creep is always a risk, so I accept that my suggestion is out of scope. It'll be interesting to see how / if the per -WG icals work out.... Thanks, Lou On 2/11/2015 8:54 PM, Russ Housley wrote: > Lou: > > We are working on a system where each WG will have an iCal managed by the WG Chairs. > > Russ > > > On Feb 11, 2015, at 6:08 PM, Lou Berger wrote: > >> On 02/11/2015 04:50 PM, Matt Larson wrote: >>> Meanwhile, I would like to suggest that we identify a couple of >>> working groups that might be interested in using the calendar server >>> to include as test groups, so that we can see how the server is going >>> to do with a wider user base. Can you suggest a few working groups >>> whose chairs might be interested in testing this out for us with >>> their groups? >> Don't know if this has been covered before/discussed. What about having >> a calendar that shows all interims as a test case? >> >> I also bet that Sue Hares would be interested/willing. >> >> >> Lou >> >> >> >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development > From nobody Wed Feb 11 18:17:19 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 466061A8A60 for ; Wed, 11 Feb 2015 18:17:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6D9SfbN5WUa for ; Wed, 11 Feb 2015 18:17:12 -0800 (PST) Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id C13441A8A5A for ; Wed, 11 Feb 2015 18:17:12 -0800 (PST) Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 4638A9A4022; Wed, 11 Feb 2015 21:17:02 -0500 (EST) X-Virus-Scanned: amavisd-new at smetech.net Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id Rf2yfFIZ6lR8; Wed, 11 Feb 2015 21:16:41 -0500 (EST) Received: from [5.5.33.238] (vpn.snozzages.com [204.42.252.17]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id AE65E9A4019; Wed, 11 Feb 2015 21:16:38 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Russ Housley In-Reply-To: <54DC0B95.8000305@labn.net> Date: Wed, 11 Feb 2015 21:16:18 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> <54DBE0F7.6060109@labn.net> <54DC0B95.8000305@labn.net> To: Lou Berger X-Mailer: Apple Mail (2.1085) Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 02:17:15 -0000 I'd like to see this proceed, and get some experience with it. We all = have our crystal balls about the next steps ... Russ On Feb 11, 2015, at 9:10 PM, Lou Berger wrote: > Russ, >=20 > I did get that I was suggesting something slightly off topic. If you > start thinking through some of the user-side scaling issues, I think = you > might reach the suggestion that I came up with. (I.e., do I really > want/need a calendar for each of the ~7 WGs I track/participate in, no > but something that allows me to easily see across WGs, say their > interims, now that would be really helpful and replace something I'm > doing now manually...) >=20 > But feature creep is always a risk, so I accept that my suggestion is > out of scope. It'll be interesting to see how / if the per -WG icals > work out.... >=20 > Thanks, > Lou >=20 > On 2/11/2015 8:54 PM, Russ Housley wrote: >> Lou: >>=20 >> We are working on a system where each WG will have an iCal managed by = the WG Chairs. >>=20 >> Russ >>=20 >>=20 >> On Feb 11, 2015, at 6:08 PM, Lou Berger wrote: >>=20 >>> On 02/11/2015 04:50 PM, Matt Larson wrote: >>>> Meanwhile, I would like to suggest that we identify a couple of >>>> working groups that might be interested in using the calendar = server >>>> to include as test groups, so that we can see how the server is = going >>>> to do with a wider user base. Can you suggest a few working groups >>>> whose chairs might be interested in testing this out for us with >>>> their groups? >>> Don't know if this has been covered before/discussed. What about = having >>> a calendar that shows all interims as a test case? >>>=20 >>> I also bet that Sue Hares would be = interested/willing. >>>=20 >>>=20 >>> Lou >>>=20 >>>=20 >>>=20 >>> _______________________________________________ >>> TOOLS-DEVELOPMENT mailing list >>> TOOLS-DEVELOPMENT@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-development >>=20 >=20 >=20 From nobody Thu Feb 12 05:41:04 2015 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A5E1A1A87 for ; Thu, 12 Feb 2015 05:41:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.902 X-Spam-Level: X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 757xkM2AaHAH for ; Thu, 12 Feb 2015 05:40:59 -0800 (PST) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0075.outbound.protection.outlook.com [207.46.100.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C4281A1A42 for ; Thu, 12 Feb 2015 05:40:59 -0800 (PST) Received: from [192.168.0.14] (72.237.59.193) by BN1PR06MB229.namprd06.prod.outlook.com (10.242.215.141) with Microsoft SMTP Server (TLS) id 15.1.87.18; Thu, 12 Feb 2015 13:40:57 +0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 (1.0) From: Ray Pelletier X-Mailer: iPhone Mail (12B466) In-Reply-To: Date: Thu, 12 Feb 2015 08:40:53 -0500 Content-Transfer-Encoding: quoted-printable Message-ID: <11E985E7-560F-4FA8-A2CD-4A7FED33574F@isoc.org> References: <54DA33AE.4040308@nostrum.com> <363B7D7F-FBBF-4875-A602-07091B81D0EC@amsl.com> <5636CAA8-2EBA-472B-87FF-6EAB1A8EDF65@amsl.com> <54DBE0F7.6060109@labn.net> <54DC0B95.8000305@labn.net> To: Russ Housley X-Originating-IP: [72.237.59.193] X-ClientProxiedBy: BLUPR11CA0052.namprd11.prod.outlook.com (10.141.30.20) To BN1PR06MB229.namprd06.prod.outlook.com (10.242.215.141) Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR06MB229; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:BN1PR06MB229; X-Forefront-PRVS: 0485417665 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(6049001)(164054003)(479174004)(51704005)(377454003)(24454002)(50986999)(76176999)(50226001)(15975445007)(47776003)(77096005)(62966003)(77156002)(50466002)(42186005)(23726002)(33656002)(36756003)(46102003)(110306001)(2950100001)(93886004)(92566002)(117156001)(82746002)(83716003)(40100003)(86362001)(46406003)(19580395003)(19580405001)(122386002)(66066001)(110136001)(87976001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN1PR06MB229; H:[192.168.0.14]; FPR:; SPF:None; MLV:sfv; LANG:en; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:BN1PR06MB229; X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Feb 2015 13:40:57.8307 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR06MB229 Archived-At: Cc: IETF Tools Development Subject: Re: [TOOLS-DEVELOPMENT] Question on the status of calendaring X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 13:41:02 -0000 All Wouldn't it be possible to roll up all the WG calendar entries into a Master= WG Calendar? Surely individuals could subscribe to any WG calendars they follow? Ray > On Feb 11, 2015, at 9:16 PM, Russ Housley wrote: >=20 > I'd like to see this proceed, and get some experience with it. We all hav= e our crystal balls about the next steps ... >=20 > Russ >=20 >=20 >> On Feb 11, 2015, at 9:10 PM, Lou Berger wrote: >>=20 >> Russ, >>=20 >> I did get that I was suggesting something slightly off topic. If you >> start thinking through some of the user-side scaling issues, I think you >> might reach the suggestion that I came up with. (I.e., do I really >> want/need a calendar for each of the ~7 WGs I track/participate in, no >> but something that allows me to easily see across WGs, say their >> interims, now that would be really helpful and replace something I'm >> doing now manually...) >>=20 >> But feature creep is always a risk, so I accept that my suggestion is >> out of scope. It'll be interesting to see how / if the per -WG icals >> work out.... >>=20 >> Thanks, >> Lou >>=20 >>> On 2/11/2015 8:54 PM, Russ Housley wrote: >>> Lou: >>>=20 >>> We are working on a system where each WG will have an iCal managed by th= e WG Chairs. >>>=20 >>> Russ >>>=20 >>>=20 >>>> On Feb 11, 2015, at 6:08 PM, Lou Berger wrote: >>>>=20 >>>>> On 02/11/2015 04:50 PM, Matt Larson wrote: >>>>> Meanwhile, I would like to suggest that we identify a couple of >>>>> working groups that might be interested in using the calendar server >>>>> to include as test groups, so that we can see how the server is going >>>>> to do with a wider user base. Can you suggest a few working groups >>>>> whose chairs might be interested in testing this out for us with >>>>> their groups? >>>> Don't know if this has been covered before/discussed. What about havin= g >>>> a calendar that shows all interims as a test case? >>>>=20 >>>> I also bet that Sue Hares would be interested/willing= . >>>>=20 >>>>=20 >>>> Lou >>>>=20 >>>>=20 >>>>=20 >>>> _______________________________________________ >>>> TOOLS-DEVELOPMENT mailing list >>>> TOOLS-DEVELOPMENT@ietf.org >>>> https://www.ietf.org/mailman/listinfo/tools-development >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development