From ietfdbh@comcast.net Wed Jun 1 08:56:27 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFF85E07AF for ; Wed, 1 Jun 2011 08:56:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.416 X-Spam-Level: X-Spam-Status: No, score=-102.416 tagged_above=-999 required=5 tests=[AWL=0.183, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fi+tMBkA7Tg3 for ; Wed, 1 Jun 2011 08:56:24 -0700 (PDT) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id DEA7EE093D for ; Wed, 1 Jun 2011 08:52:56 -0700 (PDT) Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta13.westchester.pa.mail.comcast.net with comcast id qfdY1g0021c6gX85Dfsw5u; Wed, 01 Jun 2011 15:52:56 +0000 Received: from davidPC ([67.189.235.106]) by omta23.westchester.pa.mail.comcast.net with comcast id qfsu1g00R2JQnJT3jfsv4A; Wed, 01 Jun 2011 15:52:55 +0000 From: "David Harrington" To: "'IESG IESG'" , Date: Wed, 1 Jun 2011 11:52:53 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16776 Thread-Index: Acwgc/en6Kmr72uoTAari3nw8RHfrA== Subject: [Tools-discuss] session tool and area meetings X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 15:56:27 -0000 Hi, I don't seem to be able to request an area meeting via the session request tool. It would be nice if the tool recognized ADs as default chairs of area meetings. It would also be nice if the tool allowed ADs to request office hours. David Harrington Director, IETF Transport Area ietfdbh@comcast.net (preferred for ietf) dbharrington@huaweisymantec.com +1 603 828 1401 (cell) From dromasca@avaya.com Wed Jun 1 09:07:46 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFC4EE07A8; Wed, 1 Jun 2011 09:07:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.266 X-Spam-Level: X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DyVWCGgB41mb; Wed, 1 Jun 2011 09:07:46 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 4436DE05D3; Wed, 1 Jun 2011 09:07:46 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgsBANli5k2HCzI1/2dsb2JhbABNBpdQjlR3iHGjJQKbDYMxgm8ElTWKTQ X-IronPort-AV: E=Sophos;i="4.65,304,1304308800"; d="scan'208";a="282690345" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 01 Jun 2011 12:07:45 -0400 X-IronPort-AV: E=Sophos;i="4.65,304,1304308800"; d="scan'208";a="658455984" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 01 Jun 2011 12:07:45 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 1 Jun 2011 18:07:43 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: session tool and area meetings Thread-Index: Acwgc/en6Kmr72uoTAari3nw8RHfrAAAYZwQ References: From: "Romascanu, Dan (Dan)" To: "David Harrington" , "IESG IESG" , Subject: Re: [Tools-discuss] session tool and area meetings X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 16:07:46 -0000 > -----Original Message----- > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of > David Harrington > Sent: Wednesday, June 01, 2011 6:53 PM > To: 'IESG IESG'; tools-discuss@ietf.org > Subject: session tool and area meetings >=20 > Hi, >=20 > I don't seem to be able to request an area meeting via the session > request tool. > It would be nice if the tool recognized ADs as default chairs of area > meetings. [[DR]] I think it does. At least it offers me OPSAREA to schedule when I access the tool. Maybe something is wrong with you ... sorry, with your setting :-) >=20 > It would also be nice if the tool allowed ADs to request office hours. >=20 [[DR]] Do you mean - including the office hours in the agenda? We usually use the wiki to book the breakout room for this purpose, or ask the Secretariat to find us one if the breakout room is busy at the time we picked.=20 Dan =20 > David Harrington > Director, IETF Transport Area > ietfdbh@comcast.net (preferred for ietf) > dbharrington@huaweisymantec.com > +1 603 828 1401 (cell) From fred@cisco.com Wed Jun 1 17:40:19 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3247CE06A0; Wed, 1 Jun 2011 17:40:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.357 X-Spam-Level: X-Spam-Status: No, score=-110.357 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tn4tFodU1L+K; Wed, 1 Jun 2011 17:40:18 -0700 (PDT) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 65CD2E09A3; Wed, 1 Jun 2011 17:37:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1676; q=dns/txt; s=iport; t=1306975070; x=1308184670; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=X9hB7NbjpW4HHeotgD55T0+ZG2qR4tOoQO99tm8ENq4=; b=aE0PWs2xNyQSG17BDQetfY/yM6lv9/3mDZYX2lk3YEyyAaslqhIqAFkZ KPdaSfyON7rhFBukyIwO3KXnwoVZBJIgHT0tSW9m/GmsoVgyGTuzgA+6E xJcoZrfk82W5hNzZSoyB4hoheTIQJocUDw8O82/j4Wwsnr7+9J6IVbImb 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EANja5k2rRDoH/2dsb2JhbABTpjJ3iHGhH51khiAEhmaJcIRDiwk X-IronPort-AV: E=Sophos;i="4.65,306,1304294400"; d="scan'208";a="328240313" Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-3.cisco.com with ESMTP; 02 Jun 2011 00:37:50 +0000 Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p520biGN005760; Thu, 2 Jun 2011 00:37:49 GMT Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Wed, 01 Jun 2011 17:37:49 -0700 X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Wed, 01 Jun 2011 17:37:49 -0700 Mime-Version: 1.0 (Apple Message framework v1084) From: Fred Baker In-Reply-To: Date: Wed, 1 Jun 2011 17:37:34 -0700 Message-Id: <5665F391-69E8-467A-B5DE-561ABC14A44B@cisco.com> References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> <34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com> <4DDD64D6.1060800@levkowetz.com> <7462_1306357779_p4PL9cph011040_EABE5BCF-FFA9-47CE-BC5E-3AC2B0839FBE@cisco.com> <1306394510.32156.454.camel@destiny> <11CAF335-3DDF-4827-8A9D-883003061F96@vpnc.org> <07E811C5-5BA3-4A4C-BB6D-87E7466AF15D@cisco.com> <4DE5564C.10605@gmail.com> <7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> To: Ed Juskevicius X-Mailer: Apple Mail (2.1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: IETF WG Chairs , Henrik Levkowetz , Brian E Carpenter , Tools Team Discussion , Paul Hoffman Subject: Re: [Tools-discuss] [BOFCHAIRS] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 00:40:19 -0000 On Jun 1, 2011, at 5:02 PM, Ed Juskevicius wrote: > A WG Chair is aware of an I-D and has chosen to place the document in = a separate state in order to monitor it (for whatever reason). I-Ds in = this state are not (yet) WG documents in the sense that no formal = decision has been made by the WG Chair to call for the WG to adopt the = document. The WG Chair has chosen to put the I-D into this state, to = make it easier to keep track of it (for his or her own reasons). =46rom my perspective, this would be backwards. When a draft is = initially submitted by an individual to a working group = (draft-juskevicius-v6ops-who-knows...), I would hope that the working = group would start "watching" (eg, discussing) it. The outcome of that = discussion might be "we aren't interested", it might be to move quickly = to adopt it as a working group draft, and it might well be to think = about it a while. But I would expect an individual submission to start = out in the "WG is watching" (perhaps better "WG is discussing"?) state = and move from there to something else, perhaps "WG expresses a sense of = disgust" or whatever :-) =20 > Having postulated the above, I wonder if an I-D could (or should) be = able to be "watched" in more than one WG at time. If yes, then in how = many different WG should the same I-D be able to be in the "WG Chair is = Watching" state? If no, them what should be the criteria to determine = which WG Chair can place an I-D into this state?=20 I don't have an answer to that. It does happen that a draft is looked at = in multiple working groups; it generally doesn't have a wg name in its = filename.= From adam@nostrum.com Wed Jun 1 19:15:00 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B19AFE07F6 for ; Wed, 1 Jun 2011 19:15:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkJBdHN2Eost for ; Wed, 1 Jun 2011 19:15:00 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id C96F4E0679 for ; Wed, 1 Jun 2011 19:14:59 -0700 (PDT) Received: from hydra-3.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p522En6f084426 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 1 Jun 2011 21:14:50 -0500 (CDT) (envelope-from adam@nostrum.com) Message-ID: <4DE6F219.6050207@nostrum.com> Date: Wed, 01 Jun 2011 21:14:49 -0500 From: Adam Roach User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Ed Juskevicius References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> <34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com> <4DDD64D6.1060800@levkowetz.com> <7462_1306357779_p4PL9cph011040_EABE5BCF-FFA9-47CE-BC5E-3AC2B0839FBE@cisco.com> <1306394510.32156.454.camel@destiny> <11CAF335-3DDF-4827-8A9D-883003061F96@vpnc.org> <07E811C5-5BA3-4A4C-BB6D-87E7466AF15D@cisco.com> <4DE5564C.10605@gmail.com> <7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism) Cc: IETF WG Chairs , Tools Team Discussion , Paul Hoffman , Brian E Carpenter , Fred Baker , Henrik Levkowetz Subject: Re: [Tools-discuss] [BOFCHAIRS] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 02:15:00 -0000 On 6/1/11 19:02, Jun 1, Ed Juskevicius wrote: > Having postulated the above, I wonder if an I-D could (or should) be > able to be "watched" in more than one WG at time. Yes, yes, a million times yes. Consider draft-ietf-rohc-sigcomp-sip (ROHC and SIP), draft-ietf-sip-compression (ROHC and SIP), draft-ietf-sipping-sigcomp-dictionary (SIPPING and ROHC), draft-garcia-simple-presence-dictionary (SIMPLE and ROHC), and draft-ietf-sipcore-location-conveyance (SIPCORE and GEOPRIV). And those are just documents that I've personally been involved with (either as an author, a major contributor, or a document shepherd). I imagine there are documents that straddle GEOPRIV and ECRIT as well, but I'm not following those groups closely enough to cite specific ones. I would have to imagine that other areas have similar situations arise from time to time. In any case, we do quite occasionally produce documents that necessarily straddle working groups, in that they deal with the intersection of the technologies that those groups have been chartered to address. > If yes, then in how many different WG should the same I-D be able to > be in the "WG Chair is Watching" state? From a practical perspective, there *probably* won't ever be more than two groups watching at a time. From a tools perspective, I think it would be artificial to limit the number at all. It would be infuriating to be bitten by a tools limitation when and if the first legitimately three-group document comes floating along. So, if there is a hard limit, it should be >>2. /a From Ted.Lemon@nominum.com Wed Jun 1 20:07:34 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C457E081D; Wed, 1 Jun 2011 20:07:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.51 X-Spam-Level: X-Spam-Status: No, score=-106.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3CWX+sQqL1d8; Wed, 1 Jun 2011 20:07:33 -0700 (PDT) Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id CA1FAE06AA; Wed, 1 Jun 2011 20:07:28 -0700 (PDT) Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTeb+b8Fwv6hKpvdxwLHNEMQDQkKtVNqX@postini.com; Wed, 01 Jun 2011 20:07:29 PDT Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0863B1B861F; Wed, 1 Jun 2011 20:07:27 -0700 (PDT) Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EFD35190058; Wed, 1 Jun 2011 20:07:26 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com) Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 1 Jun 2011 20:07:26 -0700 MIME-Version: 1.0 (Apple Message framework v1227) Content-Type: text/plain; charset="iso-8859-1" From: Ted Lemon In-Reply-To: <4DE6F219.6050207@nostrum.com> Date: Wed, 1 Jun 2011 23:07:19 -0400 Content-Transfer-Encoding: quoted-printable Message-ID: References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> <34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com> <4DDD64D6.1060800@levkowetz.com> <7462_1306357779_p4PL9cph011040_EABE5BCF-FFA9-47CE-BC5E-3AC2B0839FBE@cisco.com> <1306394510.32156.454.camel@destiny> <11CAF335-3DDF-4827-8A9D-883003061F96@vpnc.org> <07E811C5-5BA3-4A4C-BB6D-87E7466AF15D@cisco.com> <4DE5564C.10605@gmail.com> <7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> <4DE6F219.6050207@nostrum.com> To: Adam Roach X-Mailer: Apple Mail (2.1227) Cc: IETF WG Chairs , Tools Team Discussion , Paul Hoffman , Brian E Carpenter , Ed Juskevicius , Henrik Levkowetz Subject: Re: [Tools-discuss] [BOFCHAIRS] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 03:07:34 -0000 Le Jun 1, 2011 =E0 10:14 PM, Adam Roach a =E9crit : > On 6/1/11 19:02, Jun 1, Ed Juskevicius wrote: >> Having postulated the above, I wonder if an I-D could (or should) be = able to be "watched" in more than one WG at time. >=20 > Yes, yes, a million times yes. Yup, this comes up in dhc a *lot*, because other working groups = typically generate dhcp options for the protocols they are working on, = and even when they realize that they need to liaise with the dhc working = group, the ball gets dropped and the document goes to the IESG without = final review from the dhc working group. It would help a lot even if = the only thing that changed was that the IETF last call notice went to = the working group mailing list. From scott.brim@gmail.com Thu Jun 2 04:11:35 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E14E06BF for ; Thu, 2 Jun 2011 04:11:35 -0700 (PDT) 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=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kv3kW0zpUeqf for ; Thu, 2 Jun 2011 04:11:31 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 99544E06C9 for ; Thu, 2 Jun 2011 04:11:31 -0700 (PDT) Received: by iyn15 with SMTP id 15so799238iyn.31 for ; Thu, 02 Jun 2011 04:11:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=FX30vYIrhobxL2jDfW/u3qKnUsKCO1CgFwYvmHGH//M=; b=BMOMBtYVyd84w4AIYgHfMbU9fcgqKITNaPUDJC2AWdJHgkfTyPg6hNK6BdO9jFck0e 5t7gRYAwrjHtY8tTYm/q8LcDqnlusjqf/rSQl0L0Usp3VTiACxgbu+7K7UObjaqx8F07 vLSEYh0/Zx41uaaVNzkqb67IxKX5QwhIL81p8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=gnFQdgXpQRsJ2qpoxN04Lq1CZUmgAWr8DxWC9a0hDTqiI+dav3uTJuaewTD4290Com 5j0jsF8T4kkMg9xPkTmZPnQn4AnVq+jJXSaR35zzKxgKjJobNtdhTcxWSNXZOZ1f4aF/ L88g7Mnapeq3nYjdKNHKtV1tZBpkXmaE+l0+U= Received: by 10.231.1.14 with SMTP id 14mr793940ibd.13.1307013091004; Thu, 02 Jun 2011 04:11:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.19.130 with HTTP; Thu, 2 Jun 2011 04:11:10 -0700 (PDT) In-Reply-To: <4DDD64D6.1060800@levkowetz.com> References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> <34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com> <4DDD64D6.1060800@levkowetz.com> From: Scott Brim Date: Thu, 2 Jun 2011 07:11:10 -0400 Message-ID: To: Henrik Levkowetz Content-Type: text/plain; charset=ISO-8859-1 Cc: Julien Laganier , Tools Team Discussion Subject: Re: [Tools-discuss] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 11:11:35 -0000 I just tried to add a 'call for adoption' at , specifying a time of 0 weeks, and got an internal server error. From ietfdbh@comcast.net Thu Jun 2 05:27:12 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE42E0969 for ; Thu, 2 Jun 2011 05:27:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.428 X-Spam-Level: X-Spam-Status: No, score=-102.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0SD-6q2+V0OW for ; Thu, 2 Jun 2011 05:27:11 -0700 (PDT) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED2EE093C for ; Thu, 2 Jun 2011 05:27:11 -0700 (PDT) Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta13.westchester.pa.mail.comcast.net with comcast id r0Lt1g0051YDfWL5D0TCAx; Thu, 02 Jun 2011 12:27:12 +0000 Received: from davidPC ([67.189.235.106]) by omta20.westchester.pa.mail.comcast.net with comcast id r0T61g01C2JQnJT3g0T8r7; Thu, 02 Jun 2011 12:27:09 +0000 From: "David Harrington" To: "'Donald Eastlake'" , "'Ed Juskevicius'" References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org><34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com><4DDD64D6.1060800@levkowetz.com><7462_1306357779_p4PL9cph011040_EABE5BCF-FFA9-47CE-BC5E-3AC2B0839FBE@cisco.com><1306394510.32156.454.camel@destiny><11CAF335-3DDF-4827-8A9D-883003061F96@vpnc.org><07E811C5-5BA3-4A4C-BB6D-87E7466AF15D@cisco.com><4DE5564C.10605@gmail.com><7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> In-Reply-To: Date: Thu, 2 Jun 2011 08:27:04 -0400 Message-ID: <20BC42D23FBE4B01A42E38D4DF7C0635@davidPC> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16776 Thread-Index: AcwgvTP89tgkvblSSDiehnaggL/O5AAYxJRg Cc: 'IETF WG Chairs' , 'Brian E Carpenter' , 'Henrik Levkowetz' , 'Tools Team Discussion' , 'Paul Hoffman' Subject: Re: [Tools-discuss] [BOFCHAIRS] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 12:27:12 -0000 I recommend it be possible to go from "Chair is Watching" to "ID Exists" (i.e., Chair is no longer watching)=20 dbh > -----Original Message----- > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On=20 > Behalf Of Donald Eastlake > Sent: Wednesday, June 01, 2011 8:37 PM > To: Ed Juskevicius > Cc: IETF WG Chairs; Henrik Levkowetz; Paul Hoffman; Tools=20 > Team Discussion; Brian E Carpenter > Subject: Re: [BOFCHAIRS] New datatracker release >=20 > I kind of think that a working group chair ought to be keeping an eye > on all of their WG drafts... But watching a document in another > working group or a non-wg document sound like it might be a useful > state. Presumably one effect would be that the WG chair would get > notice of changes in state for the draft. >=20 > Thanks, > Donald > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > =A0Donald E. Eastlake 3rd > =A0155 Beaver Street > =A0Milford, MA 01757 USA > =A0d3e3e3@gmail.com >=20 > On Wed, Jun 1, 2011 at 8:02 PM, Ed Juskevicius=20 > wrote: > > AD is Watching is defined as follows (Ref: RFC 6174, Appendix A): > > > > > > A.1.16. AD is Watching > > > > An AD is aware of the document and has chosen to place the=20 > document in a > > separate state in order to monitor it (for whatever=20 > reason).=A0 Documents in > > this state are not actively tracked by the IESG in the=20 > sense that no formal > > request has been made to publish or advance the document.=A0=20 > The AD has chosen > > to put the I-D into this state, to make it easier to keep=20 > track of (for his > > or her own reasons). > > > > > > If we were to propose a state called "WG Chair is=20 > Watching", then a first > > attempt at defining such WG state might be: > > > > > > WG Chair is Watching > > > > A WG Chair=A0is aware of=A0an I-D=A0and has chosen to place the=20 > document in a > > separate state in order to monitor it (for whatever=20 > reason).=A0 I-Ds in this > > state are not (yet) WG documents=A0in the sense that no=20 > formal=A0decision has > > been made by the WG Chair to call for the WG to adopt=A0the=20 > document.=A0 The WG > > Chair has chosen to=A0put the I-D into this state, to make it=20 > easier to keep > > track of it (for his or her own reasons). > > > > > > Having postulated the above, I=A0wonder if an I-D=A0=A0could (or=20 > should) be able > > to be "watched"=A0in more than one WG at time.=A0 If yes, then=20 > in how many > > different WG should the same I-D be able to be in the "WG=20 > Chair is Watching" > > state?=A0 If no, them what should be=A0the criteria to=20 > determine which WG Chair > > can place an I-D into this state? > > > > > > Regards, > > > > Ed > > > > > > > > > > On Tue, May 31, 2011 at 5:32 PM, Fred Baker wrote: > >> > >> On May 31, 2011, at 1:57 PM, Brian E Carpenter wrote: > >> > >> > We have "AD is watching", used as one step up from "I-D=20 > exists". Why not > >> > define "WG is watching"? > >> > >> wfm > >> > >> > =A0 Brian > >> > > >> > On 2011-05-27 04:54, Fred Baker wrote: > >> >> On May 26, 2011, at 8:32 AM, Paul Hoffman wrote: > >> >> > >> >>> Sure there is. Looking at Fred's WG, > >> >>> , I see many=20 > WG drafts in "I-D > >> >>> exists". > >> >> > >> >> That's not a "WG State". That's, if anything, an IESG=20 > state, or a > >> >> statement about the draft itself - it's not dead and it=20 > hasn't gone > >> >> anywhere. From a WG perspective, I think the question=20 > is "it claims, in its > >> >> moniker, to be an individual submission to ; what=20 > does think about > >> >> it?". From my perspective, there are three possible WG=20 > states there - the WG > >> >> is thinking about the individual submission to the=20 > working group, it has > >> >> decided to no longer think about it, or it is in the=20 > process of deciding > >> >> whether to make it a WG document; after that, it is of=20 > course a WG document > >> >> and has more states. > >> >> _______________________________________________ > >> >> BOFCHAIRS mailing list > >> >> BOFCHAIRS@ietf.org > >> >> https://www.ietf.org/mailman/listinfo/bofchairs > >> >> > >> > > > > >=20 From jhutz@cmu.edu Thu Jun 2 10:05:02 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5E36E07AD; Thu, 2 Jun 2011 10:05:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.556 X-Spam-Level: X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GLM8Cmiza5Rv; Thu, 2 Jun 2011 10:05:02 -0700 (PDT) Received: from smtp02.srv.cs.cmu.edu (SMTP02.SRV.CS.CMU.EDU [128.2.217.197]) by ietfa.amsl.com (Postfix) with ESMTP id 2300EE07A2; Thu, 2 Jun 2011 10:05:01 -0700 (PDT) Received: from [128.2.216.200] (DESTINY.PC.CS.CMU.EDU [128.2.216.200]) (authenticated bits=0) by smtp02.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id p52H4pdW027569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jun 2011 13:04:52 -0400 (EDT) From: Jeffrey Hutzelman To: Fred Baker In-Reply-To: <12476_1306975226_p520ePjA022501_5665F391-69E8-467A-B5DE-561ABC14A44B@cisco.com> References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> <34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com> <4DDD64D6.1060800@levkowetz.com> <7462_1306357779_p4PL9cph011040_EABE5BCF-FFA9-47CE-BC5E-3AC2B0839FBE@cisco.com> <1306394510.32156.454.camel@destiny> <11CAF335-3DDF-4827-8A9D-883003061F96@vpnc.org> <07E811C5-5BA3-4A4C-BB6D-87E7466AF15D@cisco.com> <4DE5564C.10605@gmail.com> <7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> <12476_1306975226_p520ePjA022501_5665F391-69E8-467A-B5DE-561ABC14A44B@cisco.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 02 Jun 2011 13:04:51 -0400 Message-ID: <1307034291.932.70.camel@destiny> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit X-Scanned-By: mimedefang-cmuscs on 128.2.217.197 Cc: IETF WG Chairs , Tools Team Discussion , Paul Hoffman , Henrik Levkowetz , Ed Juskevicius , Brian E Carpenter , jhutz@cmu.edu Subject: Re: [Tools-discuss] [BOFCHAIRS] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 17:05:03 -0000 On Wed, 2011-06-01 at 17:37 -0700, Fred Baker wrote: > On Jun 1, 2011, at 5:02 PM, Ed Juskevicius wrote: > > > A WG Chair is aware of an I-D and has chosen to place the document in > a separate state in order to monitor it (for whatever reason). I-Ds > in this state are not (yet) WG documents in the sense that no formal > decision has been made by the WG Chair to call for the WG to adopt the > document. The WG Chair has chosen to put the I-D into this state, to > make it easier to keep track of it (for his or her own reasons). > > From my perspective, this would be backwards. When a draft is initially > submitted by an individual to a working group > (draft-juskevicius-v6ops-who-knows...), I would hope that the working > group would start "watching" (eg, discussing) it. The outcome of that > discussion might be "we aren't interested", it might be to move > quickly to adopt it as a working group draft, and it might well be to > think about it a while. But I would expect an individual submission to > start out in the "WG is watching" (perhaps better "WG is discussing"?) I really wish people would stop conflating filenames with process. Anyone can submit any document they like with a name like draft-smith-foo-blah-blah. Of late, the submission process sometimes (but not always) requires that their name at least be smith. It certainly doesn't require that the foo WG or its chairs know anything about the document, be interested in considering it, or even that its content have anything to do with the foo WG. And, often documents go through several revisions before they are ready for a WG to consider them, especially in WGs that basically adopt only nearly-complete work. So no, I don't think a document should automatically move to "wg is discussing" just because it was submitted. On a separate note, I think we're now talking about two different possible new states. One is the "wg is discussing" state, which applies to a document that the WG has not (yet) adopted but which is being discussed, possibly in advance of a call for adoption. The other is the "WG Chair is Watching" state, which is an analogue to "AD is Watching". It lets a chair mark a document so it gets included in the list of things potentially relevant to the WG, but _without_ any process implication. This is key -- the whole point of having such a state is that it doesn't mean anything except to the person who set it. > state and move from there to something else, perhaps "WG expresses a > sense of disgust" or whatever :-) Sounds like a good name for an annotation on "Dead WG Document". > > > Having postulated the above, I wonder if an I-D could (or should) > be able to be "watched" in more than one WG at time. If yes, then in > how many different WG should the same I-D be able to be in the "WG > Chair is Watching" state? If no, them what should be the criteria to > determine which WG Chair can place an I-D into this state? > > I don't have an answer to that. It does happen that a draft is looked > at in multiple working groups; it generally doesn't have a wg name in > its filename. Again, I don't think filenames are relevant here. There is nothing in process that says that a WG can only consider documents that have its name in their filenames and, thankfully, nothing in the tools that enforces such a requirement. However, the current datatracker implementation does have the restriction that it can only represent a WG state for one WG per document. While this is fine for a document that's working its way through a working group, I think I agree with others that it would be useful for chairs of more than WG to be able to set the "WG Chair is Watching" state. And in fact, even when a document has been adopted by one WG, Ted and others have pointed out cases where it is desirable to indicate another WG's interest in the document. -- Jeff From turners@ieca.com Wed Jun 1 09:09:33 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C0CE05D3 for ; Wed, 1 Jun 2011 09:09:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.376 X-Spam-Level: X-Spam-Status: No, score=-102.376 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydh1N-fFBmyz for ; Wed, 1 Jun 2011 09:09:32 -0700 (PDT) Received: from nm2.bullet.mail.bf1.yahoo.com (nm2.bullet.mail.bf1.yahoo.com [98.139.212.161]) by ietfa.amsl.com (Postfix) with SMTP id 89951E07DC for ; Wed, 1 Jun 2011 09:09:32 -0700 (PDT) Received: from [98.139.212.150] by nm2.bullet.mail.bf1.yahoo.com with NNFMP; 01 Jun 2011 16:09:32 -0000 Received: from [98.139.212.192] by tm7.bullet.mail.bf1.yahoo.com with NNFMP; 01 Jun 2011 16:09:32 -0000 Received: from [127.0.0.1] by omp1001.mail.bf1.yahoo.com with NNFMP; 01 Jun 2011 16:09:32 -0000 X-Yahoo-Newman-Id: 110598.80765.bm@omp1001.mail.bf1.yahoo.com Received: (qmail 65072 invoked from network); 1 Jun 2011 16:09:31 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1306944571; bh=TDs4bkwCWlbvYpsJwgJuKCqJKHTLIj31DDtNfXMNPWc=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=1Sh0F/uMFMUdXDnpC4kNbg+qu/UfAp4OAa52sxreRJyh0qZqBh19v8KxM+wWZZdVKkg2A7OxX6YtMQInxcCggXrl7AJCtE6kgyOW4wOJaF72nIvcVPwAXvHirJZNttrAmYGUareUQkEZEUvwkHwawcoC9Kd7o+Z08UP8GVhFtek= Received: from thunderfish.local (turners@71.191.10.67 with plain) by smtp115.biz.mail.mud.yahoo.com with SMTP; 01 Jun 2011 09:09:27 -0700 PDT X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ X-YMail-OSG: QO1BmosVM1koRUWMYJD45BSbF1X7c4qPM4oWZJr.5SXB_nw oYfMpyp0gzLahR3NIHpmQYwIMZJ0Z.CM06BqkDTTcKDvMs9fJleZdR56XxDy a573lCSXJhv.TkYQtWK6vgfnEoCCgZMfYl8rqVz7MBVhzVt6vuK38KQuVUlD ExyrIEALih7AkSghdWhEo5jYabr06IldCVRUemByWeOjkjXdIdjRNNVHs5Gn 6JKr1_mckyYlrSwzqjMnaqQ67TsBewFekBc1dwOvvM_nLZsB0jorhK9g92hq m1BuV0yg3YhwvjLDS2Usm8lMWuWjjXwgFjr8Xi6IKF2Ey1k.cCOhSlS3HYni jMXsT81k.zRQM54mNju8J9N1ChQSa4Fdd30bynSt3cGtdWg_Z8PR1bQE- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4DE66430.1050109@ieca.com> Date: Wed, 01 Jun 2011 12:09:20 -0400 From: Sean Turner User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: David Harrington References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 14 Jun 2011 13:40:49 -0700 Cc: 'IESG IESG' , tools-discuss@ietf.org Subject: Re: [Tools-discuss] session tool and area meetings X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 16:09:33 -0000 I used it to request the saag slot. spt On 6/1/11 11:52 AM, David Harrington wrote: > Hi, > > I don't seem to be able to request an area meeting via the session > request tool. > It would be nice if the tool recognized ADs as default chairs of area > meetings. > > It would also be nice if the tool allowed ADs to request office hours. > > David Harrington > Director, IETF Transport Area > ietfdbh@comcast.net (preferred for ietf) > dbharrington@huaweisymantec.com > +1 603 828 1401 (cell) > > From edj.etc@gmail.com Wed Jun 1 17:04:37 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41E1DE06EB; Wed, 1 Jun 2011 17:04:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.598 X-Spam-Level: X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uhm9EAvuh32c; Wed, 1 Jun 2011 17:04:36 -0700 (PDT) Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4D6E08EF; Wed, 1 Jun 2011 17:02:45 -0700 (PDT) Received: by iwn39 with SMTP id 39so334766iwn.31 for ; Wed, 01 Jun 2011 17:02:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=vfQXUluoJp6gx6WCz+XGBYqzMAEtNbBrfynsfZLAtbY=; b=WOa23ypB12iO5aO8NW67xMUMDmRryAVrFRVoRDN777dcp43zNRAmf6E7R663Loa0o4 wEXpfYL3TF62F+OPFPpABfm264mZfjXdfiko8fJoQPW3RfAIfsJgf1XUPMuLQsE0rUDA QjsVVuGcyCKW99b9nyJZIurhdU1OCXQDdEugI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bcU2jjHdLmnePw2o4dvFT9YENGG2QOkgLr/9+YUR7k4PdIs2iyjzryv1dDyYey3AAO Mdbbu//us8ptt/UhQWjWIbDINlGPC5hjeC4UVXTlrb3kDnu0mUfqh5In9yJfv1IHnqer psBNU+b65ErkiRj+rczWU5i70ZpMrkmFwNKpM= MIME-Version: 1.0 Received: by 10.42.152.65 with SMTP id h1mr150896icw.337.1306972965034; Wed, 01 Jun 2011 17:02:45 -0700 (PDT) Received: by 10.42.240.133 with HTTP; Wed, 1 Jun 2011 17:02:44 -0700 (PDT) In-Reply-To: <7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> <34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com> <4DDD64D6.1060800@levkowetz.com> <7462_1306357779_p4PL9cph011040_EABE5BCF-FFA9-47CE-BC5E-3AC2B0839FBE@cisco.com> <1306394510.32156.454.camel@destiny> <11CAF335-3DDF-4827-8A9D-883003061F96@vpnc.org> <07E811C5-5BA3-4A4C-BB6D-87E7466AF15D@cisco.com> <4DE5564C.10605@gmail.com> <7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> Date: Wed, 1 Jun 2011 20:02:44 -0400 Message-ID: From: Ed Juskevicius To: Fred Baker , Brian E Carpenter Content-Type: multipart/alternative; boundary=90e6ba6e88924fdb4904a4af5bcd X-Mailman-Approved-At: Tue, 14 Jun 2011 13:40:49 -0700 Cc: IETF WG Chairs , Paul Hoffman , Tools Team Discussion , Henrik Levkowetz Subject: Re: [Tools-discuss] [BOFCHAIRS] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 00:04:37 -0000 --90e6ba6e88924fdb4904a4af5bcd Content-Type: text/plain; charset=ISO-8859-1 AD is Watching is defined as follows (Ref: RFC 6174, Appendix A): A.1.16. AD is Watching An AD is aware of the document and has chosen to place the document in a separate state in order to monitor it (for whatever reason). Documents in this state are not actively tracked by the IESG in the sense that no formal request has been made to publish or advance the document. The AD has chosen to put the I-D into this state, to make it easier to keep track of (for his or her own reasons). If we were to propose a state called "WG Chair is Watching", then a first attempt at defining such WG state might be: WG Chair is Watching A WG Chair is aware of an I-D and has chosen to place the document in a separate state in order to monitor it (for whatever reason). I-Ds in this state are not (yet) WG documents in the sense that no formal decision has been made by the WG Chair to call for the WG to adopt the document. The WG Chair has chosen to put the I-D into this state, to make it easier to keep track of it (for his or her own reasons). Having postulated the above, I wonder if an I-D could (or should) be able to be "watched" in more than one WG at time. If yes, then in how many different WG should the same I-D be able to be in the "WG Chair is Watching" state? If no, them what should be the criteria to determine which WG Chair can place an I-D into this state? Regards, Ed On Tue, May 31, 2011 at 5:32 PM, Fred Baker wrote: > > On May 31, 2011, at 1:57 PM, Brian E Carpenter wrote: > > > We have "AD is watching", used as one step up from "I-D exists". Why not > define "WG is watching"? > > wfm > > > Brian > > > > On 2011-05-27 04:54, Fred Baker wrote: > >> On May 26, 2011, at 8:32 AM, Paul Hoffman wrote: > >> > >>> Sure there is. Looking at Fred's WG, < > https://datatracker.ietf.org/wg/v6ops/>, I see many WG drafts in "I-D > exists". > >> > >> That's not a "WG State". That's, if anything, an IESG state, or a > statement about the draft itself - it's not dead and it hasn't gone > anywhere. From a WG perspective, I think the question is "it claims, in its > moniker, to be an individual submission to ; what does think about > it?". From my perspective, there are three possible WG states there - the WG > is thinking about the individual submission to the working group, it has > decided to no longer think about it, or it is in the process of deciding > whether to make it a WG document; after that, it is of course a WG document > and has more states. > >> _______________________________________________ > >> BOFCHAIRS mailing list > >> BOFCHAIRS@ietf.org > >> https://www.ietf.org/mailman/listinfo/bofchairs > >> > > --90e6ba6e88924fdb4904a4af5bcd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
AD is Watching is defined as follows (Ref: RFC 6174, Appendix A):
=A0

<= span style=3D"mso-fareast-font-family: "Courier New";">A.1.16. AD is Watching

An AD is aware of the document and has chos= en to place the document in a separate state in order to monitor it (for whatever reason).<= span style=3D"mso-spacerun: yes;">=A0 Documents in this state are no= t actively tracked by the IESG in the sense that no formal request has been made to publish or advance the document.=A0 The AD has chosen to put the I-D into this state, to make it easier to keep track = of (for his or her own reasons).

=A0
If we were to propose a state called "= WG Chair is Watching", then a first attempt at defining such WG state = might be:
=A0

<= span style=3D"mso-fareast-font-family: "Courier New";">WG Chair is Watching

A WG Chair=A0is aware of=A0an I-D=A0= and has chosen to place the document in a separate state in order to monitor it (for whatever reason).<= span style=3D"mso-spacerun: yes;">=A0 I-Ds in this state are not (ye= t) WG documents=A0in the sense that no formal=A0decision has been made by t= he WG Chair to call for the WG to adopt=A0the document.=A0 The WG Chair has chosen to=A0put the I-D into this state, to make it easier to keep trac= k of it (for his or her own reasons).

=A0
Having postulated the above, I=A0wonder if = an I-D=A0=A0could (or should) be able to be "watched"=A0in more t= han one WG at time.=A0 If yes, then in how many different WG should the sam= e I-D be able to be in the "WG Chair is Watching" state?=A0 If no= , them what should be=A0the criteria to determine which WG Chair can place = an I-D into this state?=A0
=A0
=A0
Regards,
=A0
Ed=A0
=A0
=A0


=A0
On Tue, May 31, 2011 at 5:32 PM, Fred Baker <fred@cisco.com> wrote:

On May 31, 2011, at 1:57 PM, Brian E Carpenter wrote:

> We have "AD is watching", used as one step up from "I-D= exists". Why not define "WG is watching"?

wfm

> =A0 Brian
>
> On 2011-05-27 04:54, Fred Baker wrote:
>> On May 26, 2011, at 8:32 AM, Paul Hoffman wrote:
>>
>>> Sure there is. Looking at Fred's WG, <https://datatracker.iet= f.org/wg/v6ops/>, I see many WG drafts in "I-D exists". >>
>> That's not a "WG State". That's, if anything, an= IESG state, or a statement about the draft itself - it's not dead and = it hasn't gone anywhere. From a WG perspective, I think the question is= "it claims, in its moniker, to be an individual submission to <wg&= gt;; what does <wg> think about it?". From my perspective, there= are three possible WG states there - the WG is thinking about the individu= al submission to the working group, it has decided to no longer think about= it, or it is in the process of deciding whether to make it a WG document; = after that, it is of course a WG document and has more states.
>> _______________________________________________
>> BOFCHAIRS mailing list
>> BOFCHAIRS@ietf.org
>> https://www.ietf.org/mailman/listinfo/bofchairs
>>


--90e6ba6e88924fdb4904a4af5bcd-- From d3e3e3@gmail.com Wed Jun 1 17:37:02 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D17BEE0964; Wed, 1 Jun 2011 17:37:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.691 X-Spam-Level: X-Spam-Status: No, score=-104.691 tagged_above=-999 required=5 tests=[AWL=-1.092, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A12yTQJpiW1U; Wed, 1 Jun 2011 17:37:02 -0700 (PDT) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id BC04DE0961; Wed, 1 Jun 2011 17:37:01 -0700 (PDT) Received: by yxk30 with SMTP id 30so187809yxk.31 for ; Wed, 01 Jun 2011 17:37:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=ydVtyKe79v9owwDuAfU25mrjNeX67RCPi+NA6bIV8nA=; b=n+llvpXA349oMp0zo6AOFCwio9C3rWSJ4W4OS5JA/djveWLvN4MWybgf6wTc0K8Uxb 6HEz+dPy8wU4acZITjc3kLaTaHg4NHoUO304JSY9Egg1DMIqIeYaqLGz2/HI7HypdLuT 5HTrKLB65OiwoeSk6yboQPj+/saVaTQo3D4gk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=qriqkMOK6TXVe5CaiHvgocCIcKiDIFh+bwKWVoFlRCn3pcM2F9kUbnRF+I/xCFd9ap pGkg3T33ofbAMM+CKoX19/wkiThmMV3YdqzYQGWv+ALD2E3RMn8akx386ZpniKW9Lp4x bc87FghtEZxc37FIZ+vPkyE3PIJpvzGo+fP9c= Received: by 10.151.84.2 with SMTP id m2mr151947ybl.100.1306975021067; Wed, 01 Jun 2011 17:37:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.10.8 with HTTP; Wed, 1 Jun 2011 17:36:41 -0700 (PDT) In-Reply-To: References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> <34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com> <4DDD64D6.1060800@levkowetz.com> <7462_1306357779_p4PL9cph011040_EABE5BCF-FFA9-47CE-BC5E-3AC2B0839FBE@cisco.com> <1306394510.32156.454.camel@destiny> <11CAF335-3DDF-4827-8A9D-883003061F96@vpnc.org> <07E811C5-5BA3-4A4C-BB6D-87E7466AF15D@cisco.com> <4DE5564C.10605@gmail.com> <7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> From: Donald Eastlake Date: Wed, 1 Jun 2011 20:36:41 -0400 Message-ID: To: Ed Juskevicius Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 14 Jun 2011 13:40:49 -0700 Cc: IETF WG Chairs , Tools Team Discussion , Paul Hoffman , Brian E Carpenter , Fred Baker , Henrik Levkowetz Subject: Re: [Tools-discuss] [BOFCHAIRS] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 00:37:02 -0000 I kind of think that a working group chair ought to be keeping an eye on all of their WG drafts... But watching a document in another working group or a non-wg document sound like it might be a useful state. Presumably one effect would be that the WG chair would get notice of changes in state for the draft. Thanks, Donald =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D =A0Donald E. Eastlake 3rd =A0155 Beaver Street =A0Milford, MA 01757 USA =A0d3e3e3@gmail.com On Wed, Jun 1, 2011 at 8:02 PM, Ed Juskevicius wrote: > AD is Watching is defined as follows (Ref: RFC 6174, Appendix A): > > > A.1.16. AD is Watching > > An AD is aware of the document and has chosen to place the document in a > separate state in order to monitor it (for whatever reason).=A0 Documents= in > this state are not actively tracked by the IESG in the sense that no form= al > request has been made to publish or advance the document.=A0 The AD has c= hosen > to put the I-D into this state, to make it easier to keep track of (for h= is > or her own reasons). > > > If we were to propose a state called "WG Chair is Watching", then a first > attempt at defining such WG state might be: > > > WG Chair is Watching > > A WG Chair=A0is aware of=A0an I-D=A0and has chosen to place the document = in a > separate state in order to monitor it (for whatever reason).=A0 I-Ds in t= his > state are not (yet) WG documents=A0in the sense that no formal=A0decision= has > been made by the WG Chair to call for the WG to adopt=A0the document.=A0 = The WG > Chair has chosen to=A0put the I-D into this state, to make it easier to k= eep > track of it (for his or her own reasons). > > > Having postulated the above, I=A0wonder if an I-D=A0=A0could (or should) = be able > to be "watched"=A0in more than one WG at time.=A0 If yes, then in how man= y > different WG should the same I-D be able to be in the "WG Chair is Watchi= ng" > state?=A0 If no, them what should be=A0the criteria to determine which WG= Chair > can place an I-D into this state? > > > Regards, > > Ed > > > > > On Tue, May 31, 2011 at 5:32 PM, Fred Baker wrote: >> >> On May 31, 2011, at 1:57 PM, Brian E Carpenter wrote: >> >> > We have "AD is watching", used as one step up from "I-D exists". Why n= ot >> > define "WG is watching"? >> >> wfm >> >> > =A0 Brian >> > >> > On 2011-05-27 04:54, Fred Baker wrote: >> >> On May 26, 2011, at 8:32 AM, Paul Hoffman wrote: >> >> >> >>> Sure there is. Looking at Fred's WG, >> >>> , I see many WG drafts in "I= -D >> >>> exists". >> >> >> >> That's not a "WG State". That's, if anything, an IESG state, or a >> >> statement about the draft itself - it's not dead and it hasn't gone >> >> anywhere. From a WG perspective, I think the question is "it claims, = in its >> >> moniker, to be an individual submission to ; what does think= about >> >> it?". From my perspective, there are three possible WG states there -= the WG >> >> is thinking about the individual submission to the working group, it = has >> >> decided to no longer think about it, or it is in the process of decid= ing >> >> whether to make it a WG document; after that, it is of course a WG do= cument >> >> and has more states. >> >> _______________________________________________ >> >> BOFCHAIRS mailing list >> >> BOFCHAIRS@ietf.org >> >> https://www.ietf.org/mailman/listinfo/bofchairs >> >> >> > > From edj.etc@gmail.com Thu Jun 2 05:40:24 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C9BE0A04; Thu, 2 Jun 2011 05:40:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.271 X-Spam-Level: X-Spam-Status: No, score=-101.271 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avMd9hCXZ+KN; Thu, 2 Jun 2011 05:40:23 -0700 (PDT) Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 747FBE0A01; Thu, 2 Jun 2011 05:40:23 -0700 (PDT) Received: by yic13 with SMTP id 13so407592yic.31 for ; Thu, 02 Jun 2011 05:40:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:x-rim-org-msg-ref-id:message-id :content-transfer-encoding:reply-to:x-priority:references :in-reply-to:sensitivity:importance:subject:to:cc:from:date :content-type:mime-version; bh=uYgDHUf0rCSovBV0MpDuK3eSRhYapcWCczS2EkovN6g=; b=qfY/JP95rrgEjvmNZdDJjymqdNjaaomLXilKPA7RITqjtJyz9IYxgHQNTXY15+WRPM XBoI+bmJK7BKPlewh9+yhtMZ9r+5+0Fq461f7SOgf3yc1kO0Ok7cS4ItcoJKSscGJTQf tDY2XVy2adMKH1dhtDsGr2ALkHpBHAHwagRT0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-rim-org-msg-ref-id:message-id:content-transfer-encoding:reply-to :x-priority:references:in-reply-to:sensitivity:importance:subject:to :cc:from:date:content-type:mime-version; b=U5PK2J2n7/ylJl8oparW1x5N9D+q/3SCOMGUIAEg8MCFwOgXSp7okRR+oFY0lbAXMZ +6EbYftrTrBe2gyFb1KZG1Q93y6L/6aHgURBC8J6CRIUoo166DyBj3grqj2zYTJl5oOg MD/VmH+ff2JwJYB5hoVPhs7jjZfYJgr1afaoo= Received: by 10.150.194.16 with SMTP id r16mr585663ybf.369.1307018421305; Thu, 02 Jun 2011 05:40:21 -0700 (PDT) Received: from 172.29.195.212 (bda-74-82-80-222.bis6.us.blackberry.com [74.82.80.222]) by mx.google.com with ESMTPS id f13sm210912ybi.18.2011.06.02.05.40.19 (version=SSLv3 cipher=OTHER); Thu, 02 Jun 2011 05:40:20 -0700 (PDT) X-rim-org-msg-ref-id: 175026967 Message-ID: <175026967-1307018418-cardhu_decombobulator_blackberry.rim.net-1699877571-@b5.c2.bise6.blackberry> Content-Transfer-Encoding: base64 X-Priority: Normal References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org><34C5B72C-5BED-495B-87FB-7682A1CFD894@cisco.com><4DDD64D6.1060800@levkowetz.com><7462_1306357779_p4PL9cph011040_EABE5BCF-FFA9-47CE-BC5E-3AC2B0839FBE@cisco.com><1306394510.32156.454.camel@destiny><11CAF335-3DDF-4827-8A9D-883003061F96@vpnc.org><07E811C5-5BA3-4A4C-BB6D-87E7466AF15D@cisco.com><4DE5564C.10605@gmail.com><7FE56379-DA10-4837-8D96-F67B22BD5A30@cisco.com> <20BC42D23FBE4B01A42E38D4DF7C0635@davidPC> In-Reply-To: <20BC42D23FBE4B01A42E38D4DF7C0635@davidPC> Sensitivity: Normal Importance: Normal To: "David Harrington" , "'Donald Eastlake'" From: edj.etc@gmail.com Date: Thu, 2 Jun 2011 12:40:14 +0000 Content-Type: text/plain; charset="Windows-1252" MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 14 Jun 2011 13:40:49 -0700 Cc: 'IETF WG Chairs' , 'Brian E Carpenter' , 'Henrik Levkowetz' , 'Tools Team Discussion' , 'Paul Hoffman' Subject: Re: [Tools-discuss] [BOFCHAIRS] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: edj.etc@gmail.com List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 12:40:24 -0000 VGhlIHN0YXR1cyB0byBiZSBkaXNwbGF5ZWQgKGJ5IHRoZSBEYXRhdHJhY2tlcikgaW4gc3VjaCBh IGNhc2UgbmVlZHMgYSBmZXcgImlmL3RoZW4iIHRlc3RzLg0KDQpJZiBhbiBJLUQgaXMgYmVpbmcg d2F0Y2hlZCBieSBqdXN0IG9uZSBXRyBDaGFpciwgdGhlbiBPSy4NCg0KSWYgYW4gSS1EIGlzIGJl aW5nIHdhdGNoZWQgYnkgdHdvIFdHcyBhbmQgb25lIGxvc2VzIGludGVyZXN0IGluIHRoZSBkcmFm dCwgdGhlcmUgZG9lcyBuZWVkIHRvIGJlIHNvbWUgd2F5IHRvIGluZGljYXRlIHRoaXMgY2hhbmdl IGluIHRoZSBzdGF0dXMgLi4uIGJ1dCB0aGUgc3RhdGUgb2YgdGhlIGRyYWZ0IGNhbid0IHJldmVy dCBiYWNrIHRvIGp1c3QgIkktRCBFeGlzdHMiIGlmIHRoZSBkb2N1bWVudCBoYXMgc29tZSBzdGF0 ZSBpbiBhbm90aGVyIFdHLiANCg0KQ3JlYXRpbmcgYSAiKGluc2VydCBXRyBhY3JvbnltIGhlcmUp IENoYWlyIGlzIE5vIExvbmdlciBXYXRjaGluZyIgc3RhdGUgbWlnaHQgd29yay4NCg0KUmVnYXJk cywNCg0KRWQgDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiAiRGF2aWQgSGFy cmluZ3RvbiIgPGlldGZkYmhAY29tY2FzdC5uZXQ+DQpEYXRlOiBUaHUsIDIgSnVuIDIwMTEgMDg6 Mjc6MDQgDQpUbzogJ0RvbmFsZCBFYXN0bGFrZSc8ZDNlM2UzQGdtYWlsLmNvbT47ICdFZCBKdXNr ZXZpY2l1cyc8ZWRqLmV0Y0BnbWFpbC5jb20+DQpDYzogJ0lFVEYgV0cgQ2hhaXJzJzx3Z2NoYWly c0BpZXRmLm9yZz47ICdIZW5yaWsgTGV2a293ZXR6JzxoZW5yaWtAbGV2a293ZXR6LmNvbT47ICdQ YXVsIEhvZmZtYW4nPHBhdWwuaG9mZm1hbkB2cG5jLm9yZz47ICdUb29scyBUZWFtIERpc2N1c3Np b24nPHRvb2xzLWRpc2N1c3NAaWV0Zi5vcmc+OyAnQnJpYW4gRSBDYXJwZW50ZXInPGJyaWFuLmUu Y2FycGVudGVyQGdtYWlsLmNvbT4NClN1YmplY3Q6IFJFOiBbQk9GQ0hBSVJTXSBOZXcgZGF0YXRy YWNrZXIgcmVsZWFzZQ0KDQpJIHJlY29tbWVuZCBpdCBiZSBwb3NzaWJsZSB0byBnbyBmcm9tICJD aGFpciBpcyBXYXRjaGluZyIgdG8gIklEDQpFeGlzdHMiIChpLmUuLCBDaGFpciBpcyBubyBsb25n ZXIgd2F0Y2hpbmcpIA0KDQpkYmgNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBG cm9tOiBpZXNnLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXNnLWJvdW5jZXNAaWV0Zi5vcmdd IE9uIA0KPiBCZWhhbGYgT2YgRG9uYWxkIEVhc3RsYWtlDQo+IFNlbnQ6IFdlZG5lc2RheSwgSnVu ZSAwMSwgMjAxMSA4OjM3IFBNDQo+IFRvOiBFZCBKdXNrZXZpY2l1cw0KPiBDYzogSUVURiBXRyBD aGFpcnM7IEhlbnJpayBMZXZrb3dldHo7IFBhdWwgSG9mZm1hbjsgVG9vbHMgDQo+IFRlYW0gRGlz Y3Vzc2lvbjsgQnJpYW4gRSBDYXJwZW50ZXINCj4gU3ViamVjdDogUmU6IFtCT0ZDSEFJUlNdIE5l dyBkYXRhdHJhY2tlciByZWxlYXNlDQo+IA0KPiBJIGtpbmQgb2YgdGhpbmsgdGhhdCBhIHdvcmtp bmcgZ3JvdXAgY2hhaXIgb3VnaHQgdG8gYmUga2VlcGluZyBhbg0KZXllDQo+IG9uIGFsbCBvZiB0 aGVpciBXRyBkcmFmdHMuLi4gQnV0IHdhdGNoaW5nIGEgZG9jdW1lbnQgaW4gYW5vdGhlcg0KPiB3 b3JraW5nIGdyb3VwIG9yIGEgbm9uLXdnIGRvY3VtZW50IHNvdW5kIGxpa2UgaXQgbWlnaHQgYmUg YSB1c2VmdWwNCj4gc3RhdGUuIFByZXN1bWFibHkgb25lIGVmZmVjdCB3b3VsZCBiZSB0aGF0IHRo ZSBXRyBjaGFpciB3b3VsZCBnZXQNCj4gbm90aWNlIG9mIGNoYW5nZXMgaW4gc3RhdGUgZm9yIHRo ZSBkcmFmdC4NCj4gDQo+IFRoYW5rcywNCj4gRG9uYWxkDQo+ID09PT09PT09PT09PT09PT09PT09 PT09PT09PT09DQo+IKBEb25hbGQgRS4gRWFzdGxha2UgM3JkDQo+IKAxNTUgQmVhdmVyIFN0cmVl dA0KPiCgTWlsZm9yZCwgTUEgMDE3NTcgVVNBDQo+IKBkM2UzZTNAZ21haWwuY29tDQo+IA0KPiBP biBXZWQsIEp1biAxLCAyMDExIGF0IDg6MDIgUE0sIEVkIEp1c2tldmljaXVzIA0KPiA8ZWRqLmV0 Y0BnbWFpbC5jb20+IHdyb3RlOg0KPiA+IEFEIGlzIFdhdGNoaW5nIGlzIGRlZmluZWQgYXMgZm9s bG93cyAoUmVmOiBSRkMgNjE3NCwgQXBwZW5kaXggQSk6DQo+ID4NCj4gPg0KPiA+IEEuMS4xNi4g QUQgaXMgV2F0Y2hpbmcNCj4gPg0KPiA+IEFuIEFEIGlzIGF3YXJlIG9mIHRoZSBkb2N1bWVudCBh bmQgaGFzIGNob3NlbiB0byBwbGFjZSB0aGUgDQo+IGRvY3VtZW50IGluIGENCj4gPiBzZXBhcmF0 ZSBzdGF0ZSBpbiBvcmRlciB0byBtb25pdG9yIGl0IChmb3Igd2hhdGV2ZXIgDQo+IHJlYXNvbiku oCBEb2N1bWVudHMgaW4NCj4gPiB0aGlzIHN0YXRlIGFyZSBub3QgYWN0aXZlbHkgdHJhY2tlZCBi eSB0aGUgSUVTRyBpbiB0aGUgDQo+IHNlbnNlIHRoYXQgbm8gZm9ybWFsDQo+ID4gcmVxdWVzdCBo YXMgYmVlbiBtYWRlIHRvIHB1Ymxpc2ggb3IgYWR2YW5jZSB0aGUgZG9jdW1lbnQuoCANCj4gVGhl IEFEIGhhcyBjaG9zZW4NCj4gPiB0byBwdXQgdGhlIEktRCBpbnRvIHRoaXMgc3RhdGUsIHRvIG1h a2UgaXQgZWFzaWVyIHRvIGtlZXAgDQo+IHRyYWNrIG9mIChmb3IgaGlzDQo+ID4gb3IgaGVyIG93 biByZWFzb25zKS4NCj4gPg0KPiA+DQo+ID4gSWYgd2Ugd2VyZSB0byBwcm9wb3NlIGEgc3RhdGUg Y2FsbGVkICJXRyBDaGFpciBpcyANCj4gV2F0Y2hpbmciLCB0aGVuIGEgZmlyc3QNCj4gPiBhdHRl bXB0IGF0IGRlZmluaW5nIHN1Y2ggV0cgc3RhdGUgbWlnaHQgYmU6DQo+ID4NCj4gPg0KPiA+IFdH IENoYWlyIGlzIFdhdGNoaW5nDQo+ID4NCj4gPiBBIFdHIENoYWlyoGlzIGF3YXJlIG9moGFuIEkt RKBhbmQgaGFzIGNob3NlbiB0byBwbGFjZSB0aGUgDQo+IGRvY3VtZW50IGluIGENCj4gPiBzZXBh cmF0ZSBzdGF0ZSBpbiBvcmRlciB0byBtb25pdG9yIGl0IChmb3Igd2hhdGV2ZXIgDQo+IHJlYXNv bikuoCBJLURzIGluIHRoaXMNCj4gPiBzdGF0ZSBhcmUgbm90ICh5ZXQpIFdHIGRvY3VtZW50c6Bp biB0aGUgc2Vuc2UgdGhhdCBubyANCj4gZm9ybWFsoGRlY2lzaW9uIGhhcw0KPiA+IGJlZW4gbWFk ZSBieSB0aGUgV0cgQ2hhaXIgdG8gY2FsbCBmb3IgdGhlIFdHIHRvIGFkb3B0oHRoZSANCj4gZG9j dW1lbnQuoCBUaGUgV0cNCj4gPiBDaGFpciBoYXMgY2hvc2VuIHRvoHB1dCB0aGUgSS1EIGludG8g dGhpcyBzdGF0ZSwgdG8gbWFrZSBpdCANCj4gZWFzaWVyIHRvIGtlZXANCj4gPiB0cmFjayBvZiBp dCAoZm9yIGhpcyBvciBoZXIgb3duIHJlYXNvbnMpLg0KPiA+DQo+ID4NCj4gPiBIYXZpbmcgcG9z dHVsYXRlZCB0aGUgYWJvdmUsIEmgd29uZGVyIGlmIGFuIEktRKCgY291bGQgKG9yIA0KPiBzaG91 bGQpIGJlIGFibGUNCj4gPiB0byBiZSAid2F0Y2hlZCKgaW4gbW9yZSB0aGFuIG9uZSBXRyBhdCB0 aW1lLqAgSWYgeWVzLCB0aGVuIA0KPiBpbiBob3cgbWFueQ0KPiA+IGRpZmZlcmVudCBXRyBzaG91 bGQgdGhlIHNhbWUgSS1EIGJlIGFibGUgdG8gYmUgaW4gdGhlICJXRyANCj4gQ2hhaXIgaXMgV2F0 Y2hpbmciDQo+ID4gc3RhdGU/oCBJZiBubywgdGhlbSB3aGF0IHNob3VsZCBiZaB0aGUgY3JpdGVy aWEgdG8gDQo+IGRldGVybWluZSB3aGljaCBXRyBDaGFpcg0KPiA+IGNhbiBwbGFjZSBhbiBJLUQg aW50byB0aGlzIHN0YXRlPw0KPiA+DQo+ID4NCj4gPiBSZWdhcmRzLA0KPiA+DQo+ID4gRWQNCj4g Pg0KPiA+DQo+ID4NCj4gPg0KPiA+IE9uIFR1ZSwgTWF5IDMxLCAyMDExIGF0IDU6MzIgUE0sIEZy ZWQgQmFrZXIgPGZyZWRAY2lzY28uY29tPg0Kd3JvdGU6DQo+ID4+DQo+ID4+IE9uIE1heSAzMSwg MjAxMSwgYXQgMTo1NyBQTSwgQnJpYW4gRSBDYXJwZW50ZXIgd3JvdGU6DQo+ID4+DQo+ID4+ID4g V2UgaGF2ZSAiQUQgaXMgd2F0Y2hpbmciLCB1c2VkIGFzIG9uZSBzdGVwIHVwIGZyb20gIkktRCAN Cj4gZXhpc3RzIi4gV2h5IG5vdA0KPiA+PiA+IGRlZmluZSAiV0cgaXMgd2F0Y2hpbmciPw0KPiA+ Pg0KPiA+PiB3Zm0NCj4gPj4NCj4gPj4gPiCgIEJyaWFuDQo+ID4+ID4NCj4gPj4gPiBPbiAyMDEx LTA1LTI3IDA0OjU0LCBGcmVkIEJha2VyIHdyb3RlOg0KPiA+PiA+PiBPbiBNYXkgMjYsIDIwMTEs IGF0IDg6MzIgQU0sIFBhdWwgSG9mZm1hbiB3cm90ZToNCj4gPj4gPj4NCj4gPj4gPj4+IFN1cmUg dGhlcmUgaXMuIExvb2tpbmcgYXQgRnJlZCdzIFdHLA0KPiA+PiA+Pj4gPGh0dHBzOi8vZGF0YXRy YWNrZXIuaWV0Zi5vcmcvd2cvdjZvcHMvPiwgSSBzZWUgbWFueSANCj4gV0cgZHJhZnRzIGluICJJ LUQNCj4gPj4gPj4+IGV4aXN0cyIuDQo+ID4+ID4+DQo+ID4+ID4+IFRoYXQncyBub3QgYSAiV0cg U3RhdGUiLiBUaGF0J3MsIGlmIGFueXRoaW5nLCBhbiBJRVNHIA0KPiBzdGF0ZSwgb3IgYQ0KPiA+ PiA+PiBzdGF0ZW1lbnQgYWJvdXQgdGhlIGRyYWZ0IGl0c2VsZiAtIGl0J3Mgbm90IGRlYWQgYW5k IGl0IA0KPiBoYXNuJ3QgZ29uZQ0KPiA+PiA+PiBhbnl3aGVyZS4gRnJvbSBhIFdHIHBlcnNwZWN0 aXZlLCBJIHRoaW5rIHRoZSBxdWVzdGlvbiANCj4gaXMgIml0IGNsYWltcywgaW4gaXRzDQo+ID4+ ID4+IG1vbmlrZXIsIHRvIGJlIGFuIGluZGl2aWR1YWwgc3VibWlzc2lvbiB0byA8d2c+OyB3aGF0 IA0KPiBkb2VzIDx3Zz4gdGhpbmsgYWJvdXQNCj4gPj4gPj4gaXQ/Ii4gRnJvbSBteSBwZXJzcGVj dGl2ZSwgdGhlcmUgYXJlIHRocmVlIHBvc3NpYmxlIFdHIA0KPiBzdGF0ZXMgdGhlcmUgLSB0aGUg V0cNCj4gPj4gPj4gaXMgdGhpbmtpbmcgYWJvdXQgdGhlIGluZGl2aWR1YWwgc3VibWlzc2lvbiB0 byB0aGUgDQo+IHdvcmtpbmcgZ3JvdXAsIGl0IGhhcw0KPiA+PiA+PiBkZWNpZGVkIHRvIG5vIGxv bmdlciB0aGluayBhYm91dCBpdCwgb3IgaXQgaXMgaW4gdGhlIA0KPiBwcm9jZXNzIG9mIGRlY2lk aW5nDQo+ID4+ID4+IHdoZXRoZXIgdG8gbWFrZSBpdCBhIFdHIGRvY3VtZW50OyBhZnRlciB0aGF0 LCBpdCBpcyBvZiANCj4gY291cnNlIGEgV0cgZG9jdW1lbnQNCj4gPj4gPj4gYW5kIGhhcyBtb3Jl IHN0YXRlcy4NCj4gPj4gPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXw0KPiA+PiA+PiBCT0ZDSEFJUlMgbWFpbGluZyBsaXN0DQo+ID4+ID4+IEJPRkNIQUlS U0BpZXRmLm9yZw0KPiA+PiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv L2JvZmNoYWlycw0KPiA+PiA+Pg0KPiA+Pg0KPiA+DQo+ID4NCj4gDQoNCg== From gonzalo.camarillo@ericsson.com Thu Jun 2 08:48:33 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F2EEE0804; Thu, 2 Jun 2011 08:48:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.578 X-Spam-Level: X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1cBMju2Nge4; Thu, 2 Jun 2011 08:48:32 -0700 (PDT) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 4D9EAE07DD; Thu, 2 Jun 2011 08:48:31 -0700 (PDT) X-AuditID: c1b4fb3d-b7c17ae00000262e-c4-4de7b0ce277c Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 6E.D3.09774.EC0B7ED4; Thu, 2 Jun 2011 17:48:30 +0200 (CEST) Received: from [131.160.126.133] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.137.0; Thu, 2 Jun 2011 17:48:30 +0200 Message-ID: <4DE7B0CC.1050508@ericsson.com> Date: Thu, 2 Jun 2011 18:48:28 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: Sean Turner References: <4DE66430.1050109@ieca.com> In-Reply-To: <4DE66430.1050109@ieca.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAA== X-Mailman-Approved-At: Tue, 14 Jun 2011 13:40:49 -0700 Cc: David Harrington , 'IESG IESG' , "tools-discuss@ietf.org" Subject: Re: [Tools-discuss] session tool and area meetings X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 15:48:33 -0000 I used it to request a RAI area meeting. Cheers, Gonzalo On 01/06/2011 7:09 PM, Sean Turner wrote: > I used it to request the saag slot. > > spt > > On 6/1/11 11:52 AM, David Harrington wrote: >> Hi, >> >> I don't seem to be able to request an area meeting via the session >> request tool. >> It would be nice if the tool recognized ADs as default chairs of area >> meetings. >> >> It would also be nice if the tool allowed ADs to request office hours. >> >> David Harrington >> Director, IETF Transport Area >> ietfdbh@comcast.net (preferred for ietf) >> dbharrington@huaweisymantec.com >> +1 603 828 1401 (cell) >> >> > From kingstonsmiler@gmail.com Tue Jun 14 01:44:23 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFB311E808D for ; Tue, 14 Jun 2011 01:44:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxzzpYXIvVB6 for ; Tue, 14 Jun 2011 01:44:22 -0700 (PDT) Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5D28811E8082 for ; Tue, 14 Jun 2011 01:44:22 -0700 (PDT) Received: by wwa36 with SMTP id 36so3756166wwa.13 for ; Tue, 14 Jun 2011 01:44:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=jc21tg+NVd9rwZQQZRn0WOq9KKXYS+q3EVIDYcOI1yw=; b=rj9p3FUPRFIWZGUTB1SWh2I35L2LNoc2GCpglb0jzHcrBuZaNC9+CBN5OFWsI0EjY/ qixgyW78aJdR5TP/jQ6saa+m32XNjPKkmtM4XJ5G80FRavPqx1UrMXeoGDEihUvnmivB AwiOVeBePJaifERbcndRqPOysMgnmbf5SOj9U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=BKri4lsFzCZlC5R77bXuaWErPNgFFzZFbRXqAvPEZ7nVWJV3wPjATocBeFwjtEPDLm xkI/SWQ7nYMYhAsAH6WYwER8lp+HSEfoBOMsCN5jWBnzlkaPK5vDXbG7GIP968b9J5oz crJfp0slqsSjZJbYNtcm7aE5QpgHAm7NkS+pg= MIME-Version: 1.0 Received: by 10.216.241.132 with SMTP id g4mr6709261wer.9.1308041061406; Tue, 14 Jun 2011 01:44:21 -0700 (PDT) Received: by 10.216.20.136 with HTTP; Tue, 14 Jun 2011 01:44:21 -0700 (PDT) Date: Tue, 14 Jun 2011 14:14:21 +0530 Message-ID: From: Kingston Smiler To: tools-discuss@ietf.org Content-Type: multipart/alternative; boundary=e0cb4e43d1b9d1177e04a5a80ac6 X-Mailman-Approved-At: Tue, 14 Jun 2011 13:40:49 -0700 Subject: [Tools-discuss] The Draft Dependency Graph for MPLS is empty X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2011 08:44:23 -0000 --e0cb4e43d1b9d1177e04a5a80ac6 Content-Type: text/plain; charset=ISO-8859-1 Hi All, The Draft Dependency Graph for MPLS is empty. It's been empty for past 15 day. Can someone please let me know is there any issue in the tool. The file size of mpls.pdf in this link is 0. http://www.fenron.net/~fenner/ietf/deps/viz/mpls.pdf Regards, S. Kingston Smiler. Draft dependency graphs --e0cb4e43d1b9d1177e04a5a80ac6 Content-Type: text/html; charset=ISO-8859-1 Hi All,

The Draft Dependency Graph for MPLS is empty. It's been empty for past 15 day. Can someone please let me know is there any issue in the
tool.

The file size of mpls.pdf in this link is 0.

http://www.fenron.net/~fenner/ietf/deps/viz/mpls.pdf

Regards,
S. Kingston Smiler.
Draft dependency graphs --e0cb4e43d1b9d1177e04a5a80ac6-- From nico@cryptonector.com Fri Jun 24 12:01:50 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A2411E818F for ; Fri, 24 Jun 2011 12:01:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.777 X-Spam-Level: X-Spam-Status: No, score=-2.777 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bz1zSoaXeskb for ; Fri, 24 Jun 2011 12:01:49 -0700 (PDT) Received: from homiemail-a70.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id 5A05111E81E7 for ; Fri, 24 Jun 2011 12:01:03 -0700 (PDT) Received: from homiemail-a70.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTP id 275CC768059 for ; Fri, 24 Jun 2011 12:01:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :date:message-id:subject:from:to:content-type; q=dns; s= cryptonector.com; b=mLKLsH5CTKtY4ZwmC/fMMblL95r++jonjTdt4Vl48F8j 9B3rBuq9X6RyZ9BCIvKs3GQMFnpsEKa20L9pfjr9w/suv5i1ODLyTD1kaUFjJWC5 BC4yiMITrBgKgvnXGCyRy64Q09Z6kSx59BXohul/Dj9WikJ7ZRy1YzujuU7g0+g= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:date:message-id:subject:from:to:content-type; s= cryptonector.com; bh=FVv7k1juNzDZy/mAh6V6oOwXWPI=; b=rAXHzqkmlSG H9iqGHyDJcnG4N1RZNFgQtdcDn1iCNAw45T7a4uI88W7Ovxy5FS86TB213bWe/mW D4jWR5V+nR5Sm9JVVAxy5QlCQyrJYmRT5+cpuvES5noiakoSFIUd8wBRZX5MNjkW tToAeRx5skcg7qgZEvVuAiAJ5cEq39NE= Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTPSA id 17BFA768056 for ; Fri, 24 Jun 2011 12:01:03 -0700 (PDT) Received: by pwj5 with SMTP id 5so2131396pwj.31 for ; Fri, 24 Jun 2011 12:01:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.33.8 with SMTP id n8mr441416pbi.207.1308942062779; Fri, 24 Jun 2011 12:01:02 -0700 (PDT) Received: by 10.68.41.167 with HTTP; Fri, 24 Jun 2011 12:01:02 -0700 (PDT) Date: Fri, 24 Jun 2011 14:01:02 -0500 Message-ID: From: Nico Williams To: Tools Team Discussion Content-Type: text/plain; charset=UTF-8 Subject: [Tools-discuss] Mailman posting option: allow posts by subscribers to other IETF lists? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2011 19:01:50 -0000 It'd be nice to have an option to allow posts to an IETF list by non-subscribers who are subscribers to other lists. I can't be subscribing to every IETF list that happens to be relevant enough to me for a few days or weeks to want to post on it... Nico -- From jouni.korhonen@nsn.com Wed Jun 15 01:53:31 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 953ED11E8094; Wed, 15 Jun 2011 01:53:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeccrZE3iL3f; Wed, 15 Jun 2011 01:53:30 -0700 (PDT) Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 700C211E8074; Wed, 15 Jun 2011 01:53:30 -0700 (PDT) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p5F8rOSp022355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Jun 2011 10:53:24 +0200 Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p5F8rHIW011894; Wed, 15 Jun 2011 10:53:23 +0200 Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 15 Jun 2011 10:33:01 +0200 Received: from 10.144.17.4 ([10.144.17.4]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server demuexc023.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Wed, 15 Jun 2011 08:32:57 +0000 User-Agent: Microsoft-Entourage/12.29.0.110113 Date: Wed, 15 Jun 2011 11:32:50 +0300 From: Jouni Korhonen To: Message-ID: Thread-Topic: New datatracker release Thread-Index: AcwrNs+28P0o9CBu+0KzFU5SzlCQ4A== In-Reply-To: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 15 Jun 2011 08:33:01.0675 (UTC) FILETIME=[D6AC5BB0:01CC2B36] X-Mailman-Approved-At: Tue, 28 Jun 2011 13:20:09 -0700 Cc: wg-chair Subject: Re: [Tools-discuss] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2011 08:53:31 -0000 Hi, The datatracker view does not seem to list expired WG drafts, whereas Tools WG page does. I would prefer to see them so I could mark some I-Ds 'dead'.. When entering the document view, the top of page navigation bar disappears (which has Documents|Charter|Manage workflow|..). You get that back when entering either to "Change draft writeup" or to "Change draft shepherd". - Jouni On 5/25/11 8:14 PM, "ext IETF Chair" wrote: > We have now deployed new features in the IETF Datatracker (which you can find > at http://datatracker.ietf.org/) that provide support for display and > management of working group document status according to RFC 6174 and RFC > 6175. > > The WG Chairs can assign states to WG Internet-Drafts: > - WG Document > - Parked WG Document > - Dead WG Document > - In WG Last Call > - Waiting for WG Chair Go-Ahead > - WG Consensus: Waiting for Writeup > - Submitted to IESG for Publication > > A subset of these states will be set automatically for WG documents by the > system if no action is taken by the WG Chairs. You can see the new states on > the WG document summary pages in the datatracker, see for instance > http://datatracker.ietf.org/wg/v6ops/ > > The new datatracker release also provides support for showing and assigning > shepherds for WG Internet-Drafts, for recording proto write-ups for WG > Internet-Drafts, for defining a custom document workflow for a WG, and more. > > We hope these new datatracker features will provide more information about the > state and progress of WG documents for all IETF participants. We hope these > new datatracker features will also provide tools for WG Chairs that make it > easier to manage WG documents. > > Thanks, > Russ > From amalis@gmail.com Thu Jun 16 01:32:01 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB98D11E807B; Thu, 16 Jun 2011 01:32:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7tcBkhRmwVH4; Thu, 16 Jun 2011 01:32:01 -0700 (PDT) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 07D6511E80FC; Thu, 16 Jun 2011 01:32:00 -0700 (PDT) Received: by qwc23 with SMTP id 23so901410qwc.31 for ; Thu, 16 Jun 2011 01:32:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=viZVh6Yw6aaHhOOa1NBy34VP5TgsfZM4x9fUlVgRYjc=; b=w31O6D/5+9voBpN8HUxCz9OCxhsGiEC6CwH4Gfjd2FgPabXn1CgbsH1mP5Qwy2qnKI e0q0X37/3w85sRdPDLtOovCYD8Sv2eSRNQgcCToeWCQR2qS7z9w1g+QwbX3hjGeT0CBt uRT2D+HeI0PqNV5Cbktu6KW9HarY7yDtgE3I4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=hTUobxl6puo+y2yZhbhgoxGpnEI+nMUVJOtgWXWrJE/YSZ7AqOLHyfconD8MVIqWJ1 L3AQBbu+45DXlz5xlXMSeqsojj4tgsoDvJeyNT6PmqgT7ntUWQ43pD82AdeD4zGM+il4 6a3J7d2dbIXabQOslqZZAicbszzcW9OlMdn9M= Received: by 10.229.251.13 with SMTP id mq13mr506886qcb.36.1308213119198; Thu, 16 Jun 2011 01:31:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.190.3 with HTTP; Thu, 16 Jun 2011 01:31:39 -0700 (PDT) In-Reply-To: References: <7911C644-E2A3-4BF8-842A-1DB1A4450E69@ietf.org> From: "Andrew G. Malis" Date: Thu, 16 Jun 2011 04:31:39 -0400 Message-ID: To: Jouni Korhonen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 28 Jun 2011 13:20:09 -0700 Cc: wg-chair , tools-discuss@ietf.org Subject: Re: [Tools-discuss] New datatracker release X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2011 08:32:01 -0000 I agree - I had to use the tools page to clean up the status of the expired WG drafts. Cheers, Andy On Wed, Jun 15, 2011 at 4:32 AM, Jouni Korhonen wr= ote: > Hi, > > The datatracker view does not seem to list expired WG drafts, whereas Too= ls > WG page does. I would prefer to see them so I could mark some I-Ds 'dead'= .. > > When entering the document view, the top of page navigation bar disappear= s > (which has Documents|Charter|Manage workflow|..). You get that back when > entering either to "Change draft writeup" =A0or to "Change draft shepherd= ". > > - Jouni > > > On 5/25/11 8:14 PM, "ext IETF Chair" wrote: > >> We have now deployed new features in the IETF Datatracker (which you can= find >> at http://datatracker.ietf.org/) that provide support for display and >> management of working group document status according to RFC 6174 and RF= C >> 6175. >> >> The WG Chairs can assign states to WG Internet-Drafts: >> =A0- =A0WG Document >> =A0- =A0Parked WG Document >> =A0- =A0Dead WG Document >> =A0- =A0In WG Last Call >> =A0- =A0Waiting for WG Chair Go-Ahead >> =A0- =A0WG Consensus: Waiting for Writeup >> =A0- =A0Submitted to IESG for Publication >> >> A subset of these states will be set automatically for WG documents by t= he >> system if no action is taken by the WG Chairs. =A0You can see the new st= ates on >> the WG document summary pages in the datatracker, see for instance >> http://datatracker.ietf.org/wg/v6ops/ >> >> The new datatracker release also provides support for showing and assign= ing >> shepherds for WG Internet-Drafts, for recording proto write-ups for WG >> Internet-Drafts, for defining a custom document workflow for a WG, and m= ore. >> >> We hope these new datatracker features will provide more information abo= ut the >> state and progress of WG documents for all IETF participants. We hope th= ese >> new datatracker features will also provide tools for WG Chairs that make= it >> easier to manage WG documents. >> >> Thanks, >> Russ >> > > From mcr@sandelman.ca Tue Jun 28 08:16:12 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 063DB21F863A; Tue, 28 Jun 2011 08:16:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.954 X-Spam-Level: X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ik6j27qb3o86; Tue, 28 Jun 2011 08:16:11 -0700 (PDT) Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 30C3E21F862E; Tue, 28 Jun 2011 08:16:11 -0700 (PDT) Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id CEC793404A; Tue, 28 Jun 2011 11:16:08 -0400 (EDT) Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 5952F98AC2; Tue, 28 Jun 2011 11:16:11 -0400 (EDT) From: Michael Richardson To: Marc Petit-Huguenin In-Reply-To: <4E08DEA7.1040105@acm.org> References: <4E08DEA7.1040105@acm.org> X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13534.1309274149.1@marajade.sandelman.ca> Date: Tue, 28 Jun 2011 11:16:11 -0400 Message-ID: <13607.1309274171@marajade.sandelman.ca> Sender: mcr@sandelman.ca X-Mailman-Approved-At: Tue, 28 Jun 2011 13:20:09 -0700 Cc: tools-discuss@ietf.org, 81attendees@ietf.org Subject: Re: [Tools-discuss] [81attendees] Android app for IETF 81 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 15:16:12 -0000 >>>>> "Marc" == Marc Petit-Huguenin writes: Marc> I was complaining to my friend Isabelle Dalmasso that there Marc> was no easy tool to manage a customized agenda during the IETF Marc> meeting so she wrote an Android app doing exactly this. You Marc> can install it from the Android Market, by using this URL or Marc> the attached QR code: Thanks for this, I'm installing it. As for the API, the tools folks were making ICS files available with the schedule before. I wonder if that isn't more than enough API to solve the problem? Given the restrictions on what you can get, will you get updates on room or time changes? I noticed for 80, that the generation of the ical feed was either gone or not obvious. As a frequent remote participant, I also wouldn't mind if this app could find the appropriate audio channel for me, and... well... play it... and also... join the jabber room :-) -- ] He who is tired of Weird Al is tired of life! | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[ Kyoto Plus: watch the video then sign the petition. From mcr@sandelman.ca Tue Jun 28 08:18:34 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29B4321F863C; Tue, 28 Jun 2011 08:18:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.935 X-Spam-Level: X-Spam-Status: No, score=-0.935 tagged_above=-999 required=5 tests=[AWL=1.020, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzauBGfwzCLj; Tue, 28 Jun 2011 08:18:33 -0700 (PDT) Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id CA7D521F863A; Tue, 28 Jun 2011 08:18:33 -0700 (PDT) Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id CB2563404A; Tue, 28 Jun 2011 11:18:31 -0400 (EDT) Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 59D2C98AC2; Tue, 28 Jun 2011 11:18:34 -0400 (EDT) From: Michael Richardson To: 81attendees@ietf.org, tools-discuss@ietf.org In-Reply-To: <4E08DEA7.1040105@acm.org> References: <4E08DEA7.1040105@acm.org> X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13534.1309274149.1@marajade.sandelman.ca> Date: Tue, 28 Jun 2011 11:18:34 -0400 Message-ID: <13943.1309274314@marajade.sandelman.ca> Sender: mcr@sandelman.ca X-Mailman-Approved-At: Tue, 28 Jun 2011 13:20:09 -0700 Subject: Re: [Tools-discuss] [81attendees] Android app for IETF 81 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 15:18:34 -0000 > I noticed for 80, that the generation of the ical feed was either gone > or not obvious. Well, it's at: http://trac.tools.ietf.org/agenda/81/calendar I think that the link on the left eluded me, because there was a link from http://trac.tools.ietf.org/agenda/81/ before to it. -- ] He who is tired of Weird Al is tired of life! | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[ Kyoto Plus: watch the video then sign the petition. From paul@xelerance.com Tue Jun 28 08:40:01 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8691721F851F; Tue, 28 Jun 2011 08:40:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.3 X-Spam-Level: X-Spam-Status: No, score=-5.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OG8H6Gy7vntJ; Tue, 28 Jun 2011 08:40:00 -0700 (PDT) Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC7F11E80B4; Tue, 28 Jun 2011 08:40:00 -0700 (PDT) Received: from newtla.xelerance.com (newtla.xelerance.com [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by newtla.xelerance.com (Postfix) with ESMTP id C856DC658; Tue, 28 Jun 2011 11:39:57 -0400 (EDT) Date: Tue, 28 Jun 2011 11:39:57 -0400 (EDT) From: Paul Wouters To: Michael Richardson In-Reply-To: <13607.1309274171@marajade.sandelman.ca> Message-ID: References: <4E08DEA7.1040105@acm.org> <13607.1309274171@marajade.sandelman.ca> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 28 Jun 2011 13:20:09 -0700 Cc: Marc Petit-Huguenin , 81attendees@ietf.org, tools-discuss@ietf.org Subject: Re: [Tools-discuss] [81attendees] Android app for IETF 81 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 15:40:01 -0000 On Tue, 28 Jun 2011, Michael Richardson wrote: > Thanks for this, I'm installing it. > > As for the API, the tools folks were making ICS files available > with the schedule before. I wonder if that isn't more than enough API > to solve the problem? > Given the restrictions on what you can get, will you get updates on room > or time changes? > > I noticed for 80, that the generation of the ical feed was either gone > or not obvious. > > > As a frequent remote participant, I also wouldn't mind if this app > could find the appropriate audio channel for me, and... well... play > it... and also... join the jabber room :-) A mobile website would be even better then a specific platform app. and don't forget the stream of inline #ietfXX :) Paul From tjc@ecs.soton.ac.uk Tue Jun 28 08:44:10 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DACA11E813D; Tue, 28 Jun 2011 08:44:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id laBw1x4R62Jt; Tue, 28 Jun 2011 08:44:09 -0700 (PDT) Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id DB12811E8119; Tue, 28 Jun 2011 08:44:01 -0700 (PDT) Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5SFhtLB032312; Tue, 28 Jun 2011 16:43:55 +0100 X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p5SFhtLB032312 DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1309275835; bh=f+gHK5eEJkZ222mHE7NjuJpDR98=; h=References:In-Reply-To:Mime-Version:From:Subject:Date:To; b=z9+LueTbYY4Rc168vWAWdg2PJAyxWnBU4HmWUVjnzzurtDbLVqTpZ2v0757HS3YPA AMyR/Qpxo8fBQnEQ7WePhYc0EelyJAwjpw48h21HEzVCRTEv3SDX0m/ixkhQKo2tVb zdCygigVsrTA53DrOVPAY1kR4Qn9+eAVENOmBosM= Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from with ESMTP id n5RGhs0366101298Su ret-id none; Tue, 28 Jun 2011 16:43:55 +0100 Received: from [IPv6:2001:630:d0:f103::c0:ffee] ([IPv6:2001:630:d0:f103::c0:ffee]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5SFhnWJ024825 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Jun 2011 16:43:49 +0100 References: <4E08DEA7.1040105@acm.org> <13607.1309274171@marajade.sandelman.ca> <6B3780E2-2331-4B4D-AED4-D24571CA0442@ecs.soton.ac.uk> In-Reply-To: Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Message-ID: Content-Transfer-Encoding: quoted-printable From: Tim Chown Date: Tue, 28 Jun 2011 16:43:49 +0100 To: 81attendees@ietf.org, tools-discuss@ietf.org X-Mailer: Apple Mail (2.1084) X-ECS-MailScanner: Found to be clean, Found to be clean X-smtpf-Report: sid=n5RGhs036610129800; tid=n5RGhs0366101298Su; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0 X-ECS-MailScanner-Information: Please contact the ISP for more information X-ECS-MailScanner-ID: p5SFhtLB032312 X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk X-Mailman-Approved-At: Tue, 28 Jun 2011 13:20:09 -0700 Subject: Re: [Tools-discuss] [81attendees] Android app for IETF 81 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 15:44:10 -0000 On 28 Jun 2011, at 16:39, Paul Wouters wrote: > On Tue, 28 Jun 2011, Michael Richardson wrote: >=20 >> Thanks for this, I'm installing it. >>=20 >> As for the API, the tools folks were making ICS files available >> with the schedule before. I wonder if that isn't more than enough = API >> to solve the problem? >> Given the restrictions on what you can get, will you get updates on = room >> or time changes? >>=20 >> I noticed for 80, that the generation of the ical feed was either = gone >> or not obvious. >>=20 >> As a frequent remote participant, I also wouldn't mind if this app >> could find the appropriate audio channel for me, and... well... play >> it... and also... join the jabber room :-) >=20 > A mobile website would be even better then a specific platform app. >=20 > and don't forget the stream of inline #ietfXX :) Providing the meeting data as open data (RDF) would be ideal... or is = that the case already? Tim= From petithug@acm.org Tue Jun 28 09:31:41 2011 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB6F311E808C; Tue, 28 Jun 2011 09:31:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GmF52JSLbB8k; Tue, 28 Jun 2011 09:31:41 -0700 (PDT) Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA4511E8110; Tue, 28 Jun 2011 09:31:30 -0700 (PDT) Received: from [IPv6:2001:55c:4c15:5f80:213:d4ff:fe04:3e08] (unknown [IPv6:2001:55c:4c15:5f80:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 3F378226E9; Tue, 28 Jun 2011 18:30:56 +0200 (CEST) Message-ID: <4E0A01D9.7040702@acm.org> Date: Tue, 28 Jun 2011 09:31:21 -0700 From: Marc Petit-Huguenin User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Iceowl/1.0b2 Icedove/3.1.11 MIME-Version: 1.0 To: Michael Richardson References: <4E08DEA7.1040105@acm.org> <13607.1309274171@marajade.sandelman.ca> In-Reply-To: <13607.1309274171@marajade.sandelman.ca> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 28 Jun 2011 13:20:08 -0700 Cc: tools-discuss@ietf.org, 81attendees@ietf.org Subject: Re: [Tools-discuss] [81attendees] Android app for IETF 81 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 16:31:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/28/2011 08:16 AM, Michael Richardson wrote: >>>>>> "Marc" == Marc Petit-Huguenin writes: > Marc> I was complaining to my friend Isabelle Dalmasso that there > Marc> was no easy tool to manage a customized agenda during the IETF > Marc> meeting so she wrote an Android app doing exactly this. You > Marc> can install it from the Android Market, by using this URL or > Marc> the attached QR code: > > Thanks for this, I'm installing it. > > As for the API, the tools folks were making ICS files available > with the schedule before. I wonder if that isn't more than enough API > to solve the problem? > Given the restrictions on what you can get, will you get updates on room > or time changes? > > I noticed for 80, that the generation of the ical feed was either gone > or not obvious. > > > As a frequent remote participant, I also wouldn't mind if this app > could find the appropriate audio channel for me, and... well... play > it... and also... join the jabber room :-) Yes, and it is not just for remote participants. On the last meeting I wanted to see one specific presentation in one session but had to be in another session at the same time. By listening to the stream I could have switched rooms for just the duration of this presentation. - -- Marc Petit-Huguenin Personal email: marc@petit-huguenin.org Professional email: petithug@acm.org Blog: http://blog.marc.petit-huguenin.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk4KAdcACgkQ9RoMZyVa61cAeACfaHDZqfMRixSymNZiskb3gWPW 3V4An2OX7EwpwyIWyBYe3AsJvVA2AsWG =AlwV -----END PGP SIGNATURE-----