From btns-bounces@ietf.org Wed Aug 13 03:21:06 2008 Return-Path: X-Original-To: btns-archive-1@ietf.org Delivered-To: ietfarch-btns-archive-1@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EAAC3A6CBA; Wed, 13 Aug 2008 03:21:06 -0700 (PDT) X-Original-To: btns@core3.amsl.com Delivered-To: btns@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 030433A6C9F for ; Wed, 13 Aug 2008 03:21:05 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4mC1p9A5i7A for ; Wed, 13 Aug 2008 03:21:04 -0700 (PDT) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by core3.amsl.com (Postfix) with ESMTP id BF14B3A691D for ; Wed, 13 Aug 2008 03:21:03 -0700 (PDT) Received: by nf-out-0910.google.com with SMTP id b11so987548nfh.39 for ; Wed, 13 Aug 2008 03:20:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:to:subject:date:user-agent :mime-version:content-type:content-transfer-encoding :content-disposition:message-id:from; bh=abRy16bULMpFu8vdM4SY2aoff1MAHY8ZBmU6ZJFhTJE=; b=NalrN5/7Tx1gTMGtVX7Fe9lle4NrAahOPadwg5kHRHFo/BVcFWU91ZZSkuJ1Ac5L1b 7wzTj7nPB3BaMNn8U37kBTbPfRtz9WiULCE+cJnlbfAsWQ/lfcqdDZ5Y0w94fILx5Ck5 4d+V4ikOfbZh4Tazv1+ltUBUaI19/qSf2IrQ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=to:subject:date:user-agent:mime-version:content-type :content-transfer-encoding:content-disposition:message-id:from; b=UaoODmS9AIV2y+Ee0tiQTJf6t+4QXoa7LJJ2IqKj5AFteMzUqBGM4WQCaHs4CrQWJj c3iR5z4CIFBBSYzLTYIg/jPef+Zz/w4KiRvwQZS7ppFnNSK2w5wzv1/Wr+2O7c117P9M Xw2dh6JWaBFqX71bpeQbk8M5TR2m1sbYRsDKw= Received: by 10.102.228.2 with SMTP id a2mr7966336muh.79.1218622853480; Wed, 13 Aug 2008 03:20:53 -0700 (PDT) Received: from klee.local ( [212.119.9.178]) by mx.google.com with ESMTPS id e8sm283211muf.0.2008.08.13.03.20.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 13 Aug 2008 03:20:52 -0700 (PDT) To: mext@ietf.org, btns@ietf.org Date: Wed, 13 Aug 2008 12:21:17 +0200 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200808131221.18409.julien.laganier.IETF@googlemail.com> From: Julien Laganier Subject: [btns] FW: Third Nomcom 2008-9 Call for Volunteers! X-BeenThere: btns@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Better-Than-Nothing-Security Working Group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: btns-bounces@ietf.org Errors-To: btns-bounces@ietf.org Folks, The NomCom chair has requested WG chairs to forward to their WG mailing = list this call for NomCom volunteers. = There are currently 91 volunteers whose qualifications have been = confirmed by the secretariat. However, the more volunteers the better, = thus we need more volunteers! You have until August 18th, 2008 as = stated below. If you are eligible to volunteer, please consider doing so as the NomCom = plays a leading part in choosing the leadership of the IETF. Thanks, --julien From: NomCom Chair To: IETF Announcement list Subject: Third Nomcom 2008-9 Call for Volunteers! Once again, the IETF nominating process has begun, and the community (and I) need your help. =A0The IETF Nominating Committee appoints folks to fill the open slots on the IAOC, the IAB, and the IESG. =A0The people who do that are 10 folks selected randomly from the pool of volunteers. To make this work well for the community, we need people to volunteer. Lots of people. =A0Please! Volunteers must have attended 3 of the past 5 IETF meetings. =A0As defined by RFC 3777, that is 3 of the past 5 meetings as of the time this announcement goes out to start the solicitation. If you qualify, and are willing to forgo appointment to any of the positions for which the nominating committee is responsible, please volunteer. =A0Details on the nominating process can be found in RFC 3777. Below is the list of people and posts whose terms end with the March 2009 IETF meeting, and whose positions therefore the nominating committee is responsible for: IAOC: Jonne Soininen IAB: Loa Andersson Barry Leiba Kurtis Lindqvist Danny McPherson Dave Thaler Lixia Zhang IESG: IETF and IESG Chair: Russ Housley Applications Area (app): Chris Newman Internet Area (int): Mark Townsley Operations and Management Area (ops): Ronald Bonica Real-time Applications and Infrastructure Area (rai): =A0 =A0 =A0Jon Peterson Routing Area (rtg): David Ward Security Area (sec): Tim Polk Transport Area (tsv): Lars Eggert Before volunteering, please think about whether you want to be considered for one of the above positions instead. =A0If you are willing to volunteer, please send email before 5:00 pm EDT (2100 UTC/GMT) August 18, 2008 (otherwise, please read on) Please send email to me using the following skeleton: To: jmh@joelhalpern.com Subject: Nomcom 2008-9 Volunteer Body: =A0// As you enter in the IETF Registration Form, =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0// First/Given name followed by Last= /Family Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0// typically what goes in the Compan= y field =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0// =A0in the IETF Registration Form [] =A0// =A0 =A0 =A0 =A0 // For confirmation if selected Please expect an email response from me within 1-2 days stating whether you are qualified or not. =A0If you don't receive anything, please re-send your email with the tag (duplicate) in the subject line. During the IETF meeting in Dublin, responses will be somewhat slower, due to both my activities at the meeting and the secretariat's many activities in support of the meeting. =A0 I will try to send out at least a prompt confirmation that your email volunteering has been received. Not convinced yet? =A0Please consider that nomcom members play an important role in shaping the leadership of the IETF. =A0If you are a people person, you will enjoy meeting many of the active contributors to the IETF. =A0If you prefer instead to read a lot of email, well, we have that too. =A0Being a nomcom member is also an important responsibility: it requires adherence to confidentiality rules and some time commitment from the members. =A0The term of this nomcom will begin in early September this year. =A0We will be talking with folks at the Minneapolis IETF (if you are there. =A0It is not mandatory that all nomcom members come to the meeting.) =A0I hope to wrap up our primary selection work by mid-December, and we must complete our selection work by mid-January. We will be collecting requirements from the community, as well as talking to candidates and to community members about candidates. There will be weekly conference calls to ensure progress. Nomcom members are selected following a publicly verifiable random selection method specified in RFC 3797. For the nomcom to work as it should, the pool from which the volunteers are chosen should be as large as possible. The more people who volunteer, the better chance we have of choosing a random yet representative cross section of the IETF population. Ensuring the leadership of the IETF is fair and balanced and comprised of those who can lead the IETF in the right direction is an important responsibility that rests on the IETF participants at large. Volunteering for the nomcom is a good way of contributing in that direction. =A0So please volunteer! I will be publishing a more thorough and precise target timetable, as well as details of the randomness seeds to be used for the RFC 3797 selection process within the next few days. Thank you, and I hope to hear from you, Joel M. Halpern jmh@joelhalpern.com nomcom-chair@ietf.org _______________________________________________ btns mailing list btns@ietf.org https://www.ietf.org/mailman/listinfo/btns From btns-bounces@ietf.org Fri Aug 29 05:48:52 2008 Return-Path: X-Original-To: btns-archive-1@ietf.org Delivered-To: ietfarch-btns-archive-1@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A646B3A69DD; Fri, 29 Aug 2008 05:48:52 -0700 (PDT) X-Original-To: btns@core3.amsl.com Delivered-To: btns@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C901B3A6967 for ; Fri, 29 Aug 2008 05:48:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.327 X-Spam-Level: X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[AWL=-0.587, BAYES_20=-0.74] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DApRYtAlCXCx for ; Fri, 29 Aug 2008 05:48:50 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by core3.amsl.com (Postfix) with ESMTP id 56B9A3A6896 for ; Fri, 29 Aug 2008 05:48:50 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id d23so499012fga.41 for ; Fri, 29 Aug 2008 05:48:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:to:subject:date:user-agent :mime-version:content-type:content-transfer-encoding :content-disposition:message-id:from; bh=x9OUu0OxW6vZmf7RvkXj09IgJDx7HwvQ13vc8iANj3s=; b=KTxah3BlDgMmB9HvM7UOoOAlLDC3+mIMiosUbpPNkH/6KkON1Tj4sc3i2h12/d1r9K LjgANytniEUEZQ4gnla9iBhjPX9Ulg9l+WM/RlHEGIzOtCmVLn+w1ds0OASdbZmkEiV3 q2mIv7jZlHtydNCT07HssdnokmkNGw03RMX28= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=to:subject:date:user-agent:mime-version:content-type :content-transfer-encoding:content-disposition:message-id:from; b=Q+1ordmhyWMrvo4Cial1PlKqrK4/ajq+evmLuuT54Q2IPtJF6UItfxWhPl1cLPLgG+ HL8fKKRZMXap6Sht7TpwPsJX899GJwd5UZiWGhw1fgkAqHZenyytrTlcmFiLuQ58GknX 8Bv3hoW/zRNNFAJRkWdFhtV3KxhbKZ76rM8XM= Received: by 10.180.254.18 with SMTP id b18mr3234264bki.43.1220014121709; Fri, 29 Aug 2008 05:48:41 -0700 (PDT) Received: from klee.local ( [212.119.9.178]) by mx.google.com with ESMTPS id 13sm2170797fks.6.2008.08.29.05.48.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 29 Aug 2008 05:48:41 -0700 (PDT) To: mext@ietf.org, btns@ietf.org Date: Fri, 29 Aug 2008 14:48:39 +0200 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200808291448.39689.julien.laganier.IETF@googlemail.com> From: Julien Laganier Subject: [btns] New co-chair email address X-BeenThere: btns@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Better-Than-Nothing-Security Working Group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: btns-bounces@ietf.org Errors-To: btns-bounces@ietf.org Folks, Due to the impossibility to resolve issues (such as nearly random bouncing of emails) with my email provider I'm switching my IETF "business" to a new email account. Please use to contact me from now on. (I'll of course still be checking mail sent to my old address julien.IETF@laposte.net) --julien _______________________________________________ btns mailing list btns@ietf.org https://www.ietf.org/mailman/listinfo/btns