From d3e3e3@gmail.com Tue Jul 2 08:55:51 2013 Return-Path: X-Original-To: pppext@ietfa.amsl.com Delivered-To: pppext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D843821F9EB7 for ; Tue, 2 Jul 2013 08:55:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aC-iNLlhOEL for ; Tue, 2 Jul 2013 08:55:51 -0700 (PDT) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 34EC121F9EB6 for ; Tue, 2 Jul 2013 08:55:51 -0700 (PDT) Received: by mail-ob0-f177.google.com with SMTP id ta17so5707361obb.8 for ; Tue, 02 Jul 2013 08:55:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=jDG1GeagIaUZGX4H6nDci0Vix1X4RTykv9h6o2zYOag=; b=DeZM27cIgVkSevbBrLhVNqOLNl6Lm0vLC5Zgpv3JazeAxKD8MrOXNClooNy4JV4tdC H7qx7nP0+11BGU4xmpouw3b0vTDYr/1m75sRec7tif46qo3Kralh4CciPapeFy0X8zD2 OeHbHKx9gJp6Nu3Bq8jpkAw0N3hYUt6egrkTcwFp96yO5Urby2cVowIoN7QdbEh/epBI GOz/PzdZ0xVuXkl/a7PRnfTroOu4NzJhDE67a0MZrLLR4aRqPqiHyJ3XVUSMOwkgSNpX p8W+Ref2KtIz5uq8tKJmBBuE5n6iDDYjtx5LSnwWAxQ4Ly+O58QeeMi1B2jnrU7mRVHY lttw== X-Received: by 10.182.125.70 with SMTP id mo6mr12164157obb.105.1372780550675; Tue, 02 Jul 2013 08:55:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.73.106 with HTTP; Tue, 2 Jul 2013 08:55:30 -0700 (PDT) In-Reply-To: <20130701234030.24738.41427.idtracker@ietfa.amsl.com> References: <20130701234030.24738.41427.idtracker@ietfa.amsl.com> From: Donald Eastlake Date: Tue, 2 Jul 2013 11:55:30 -0400 Message-ID: To: IETF PPP Extensions Content-Type: text/plain; charset=ISO-8859-1 Subject: [Pppext] Fwd: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 15:55:52 -0000 In case you missed it, the Nomcom is still looking for volunteers for the pool. Please consider submitting your name. You can send a message to nomcom-chair-2013@ietf.org to do so. Some background about the nomcom is at https://www.ietf.org/nomcom/. Thanks, Donald ============================= Donald E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com ---------- Forwarded message ---------- From: NomCom Chair 2013 Date: Mon, Jul 1, 2013 at 7:40 PM Subject: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers To: IETF Announcement List Cc: IETF Discuss Hi, everyone, We are short of our goal of 200 volunteers for the upcoming nomcom. Please do volunteer. Our publicly verifiable random algorithm has fully adequate entropy for a flood of volunteers - more names, more names, more names, more brains --- er, oops, not yet a zombie. The more volunteers we get, the better chance we have of choosing a random yet representative cross section of the IETF. Respond to this challenge and strengthen our statistical significance just by hitting Reply (but not Reply-All, please). Oh, first, please do check the official information: The IETF nominating committee (nomcom) process for 2013-14 is under way. The IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB, and the IESG. Ten voting members for the nomcom are selected in a verifiably random way from a pool of volunteers. The details of the selection and operation of the nomcom can be found in RFCs 3777, 5078, 5633, 5680, and 6859. Four of those RFCs (3777, 5633, 5680 and 6859) comprise BCP 10. We will also reference RFC 3797. Volunteers must have attended 3 of the past 5 IETF meetings. As specified in RFC 3777, that means three out of the five past meetings up to the time this email announcement goes out to start the solicitation of volunteers. The five meetings out of which you must have attended three are IETF 82, 83, 84, 85, 86. If you qualify, reply to this email and volunteer. The list of people and posts whose terms end with the March 2014 IETF meeting, and thus the positions for which this nomcom is responsible, are IAOC: Chris Griffiths IAB: Bernard Aboba Marc Blanchet Ross Callon Eliot Lear Hannes Tschofenig IESG: Barry Leiba (Applications) Brian Haberman (Internet) Benoit Claise (Operations and Management) Gonzalo Camarillo (RAI) Stewart Bryant (Routing) Sean Turner (Security) Martin Stiemerling (Transport) The primary activity for this nomcom will begin in July 2013 and should be completed in January 2014. Being a nomcom member will require some time commitment - there will be interviews with candidates at meetings, regularly scheduled conference calls to ensure progress, collection and review of requirements from the commitment, review of candidate questionnaires and of community feedback. A more detailed timetable for the nomcom tasks will appear soon. Please respond to this email before 23:59 EDT (UTC -4 hours) July 04, 2013. In the body include: 1. your Given Name as you enter it when you register for the IETF 2. your Family Name as you enter it when you register for the IETF 3. your current primary affilation (the information you enter into the Company field) 4. any/all email addresses you've used to register for IETF meetings 5. which email address you prefer 6. your phone number (for our use in confirming you if selected). On July 05, 2013 there will be an announcement of validated volunteers. If you haven't received an acknowledgement message from me to your email (indicating that you are or are not eligible) and you do not see your name in the July 05 list, contact me AS SOON AS POSSIBLE, on or before July 06. Looking forward to adding your name to the "hat" very soon, Allison Allison Mankin Nomcom Chair 2013-2014 From carlsonj@workingcode.com Mon Jul 15 05:05:30 2013 Return-Path: X-Original-To: pppext@ietfa.amsl.com Delivered-To: pppext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5E4B11E80E8 for ; Mon, 15 Jul 2013 05:05:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ATrLfP5h5Y37 for ; Mon, 15 Jul 2013 05:05:26 -0700 (PDT) Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by ietfa.amsl.com (Postfix) with ESMTP id B803511E80E6 for ; Mon, 15 Jul 2013 05:05:21 -0700 (PDT) Received: from [10.50.25.120] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id r6FC5KMS000236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 15 Jul 2013 08:05:20 -0400 (EDT) Message-ID: <51E3E580.7000304@workingcode.com> Date: Mon, 15 Jul 2013 08:05:20 -0400 From: James Carlson User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: pppext@ietf.org References: <51B4428A.8070009@gmail.com> In-Reply-To: <51B4428A.8070009@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: carlson; whitelist Subject: Re: [Pppext] Advancing PPP RFCs to Standard, updating Security X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 12:05:30 -0000 On 06/09/13 04:53, William Allen Simpson wrote: > But the WG mailing list isn't online any more. So any newer > implementation would likely have troubles. That's probably more > important than merely updating document status. Is there any chance > to get the old UCDavis and Merit archives back online? My archived copies of the UCDavis and Merit ietf-ppp archives (January 1990 through October 2004) is here: http://www.workingcode.com/ppp-archives/ ftp://ftp.workingcode.com/pub/ppp-archives/ We switched to the ietf.org servers in February 2004, so those last few months aren't too helpful. The ftp server is smart enough to make archives, so if you fetch "ppp-archives.tar.gz" or "ppp-archives.tar.bz2", it'll do the right thing. As a bonus, it includes May through October 1993 of the ppp-comp list. I don't know if more of those exist somewhere else. The IETF archives seem to overlap some of this history and (of course) include the bits since 2004: ftp://ftp.ietf.org/ietf-mail-archive/ietf/ I haven't looked into it to try to figure out why the file sizes are so different. I don't know where the pre-2004 files in the IETF archives came from, but mine were downloaded from Merit before they shut the servers down. -- James Carlson 42.703N 71.076W From william.allen.simpson@gmail.com Mon Jul 15 15:22:04 2013 Return-Path: X-Original-To: pppext@ietfa.amsl.com Delivered-To: pppext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0CD121E818F for ; Mon, 15 Jul 2013 15:22:04 -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=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08Wp0MWJvawd for ; Mon, 15 Jul 2013 15:22:04 -0700 (PDT) Received: from mail-qe0-x22e.google.com (mail-qe0-x22e.google.com [IPv6:2607:f8b0:400d:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2978821E8193 for ; Mon, 15 Jul 2013 15:21:54 -0700 (PDT) Received: by mail-qe0-f46.google.com with SMTP id nd7so6731036qeb.5 for ; Mon, 15 Jul 2013 15:21:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ZwSuk7mU8N45dbHxeJi+bqX1XkSveES1bAsOpWhqmr0=; b=nYDy0rsryY09BR4naxKNFv/mgieMHEyh92qBZhrrzApkphlyKghWTtcEx9ULjXypE0 KUQpn5dFZ9AiEq6+nCBuzWkYXdipEVxRltRZcm9nzvm7015rZbdgibm9Ch5/RHb8JUHC C3OoBhYQuBBpR/XWknBdWOKKAf4Lzws1mgcNzWl/mIuW7cRya7C+8d6Wn1KIi17Ns3t3 KjRy1qCe43bwbx+8izfwZ/HIGnrz0LyjsNDbJDLGso341Dosy1ld1lkDibF36tt9FVpW J5QFa2/8iHlWBGJZUsW+ZPzx8W44HaIZfFsv/5zT4x0H8JYjqVTnMF9gPGMGZ578lDN2 s8TQ== X-Received: by 10.229.103.69 with SMTP id j5mr11139738qco.27.1373926913549; Mon, 15 Jul 2013 15:21:53 -0700 (PDT) Received: from wastrel.home.lan (d192-24-251-5.try.wideopenwest.com. [24.192.5.251]) by mx.google.com with ESMTPSA id s8sm517670qat.4.2013.07.15.15.21.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Jul 2013 15:21:52 -0700 (PDT) Message-ID: <51E475FF.30906@gmail.com> Date: Mon, 15 Jul 2013 18:21:51 -0400 From: William Allen Simpson User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: pppext@ietf.org References: <51B4428A.8070009@gmail.com> <51E3E580.7000304@workingcode.com> In-Reply-To: <51E3E580.7000304@workingcode.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Pppext] Advancing PPP RFCs to Standard, updating Security X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 22:22:05 -0000 On 7/15/13 8:05 AM, James Carlson wrote: > I haven't looked into it to try to figure out why the file sizes are so > different. I don't know where the pre-2004 files in the IETF archives > came from, but mine were downloaded from Merit before they shut the > servers down. > I also have copies. If somebody puts me in contact with the appropriate IETF person, I'll hand compare all the disparate file sizes and make a canonical version for the archives. That may be boring, but I'm not attending IETF in Germany -- so it can be my contribution. ;-) I was looking at stuff the past week or so, and there are a lot of widely implemented Proposed Standards that haven't made it to STD 51 yet. From william.allen.simpson@gmail.com Mon Jul 15 15:31:30 2013 Return-Path: X-Original-To: pppext@ietfa.amsl.com Delivered-To: pppext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6676411E81B0 for ; Mon, 15 Jul 2013 15:31:28 -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=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lBwCv7xxOjA for ; Mon, 15 Jul 2013 15:31:26 -0700 (PDT) Received: from mail-qe0-x230.google.com (mail-qe0-x230.google.com [IPv6:2607:f8b0:400d:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 53A8911E8178 for ; Mon, 15 Jul 2013 15:31:20 -0700 (PDT) Received: by mail-qe0-f48.google.com with SMTP id 2so6699987qea.7 for ; Mon, 15 Jul 2013 15:31:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=4op/p4wuZNCiMPYBYtCRh3QPVoZv9hSlwRTE+i9g54U=; b=DKRVHkDaR/Kvv6lf4ASPRnxK53Nyq/aEzzbHC3P1dFHVxRJTp+taPu/+/nfziqy8XE L02/Ha3lc0LRFlTUAZZaaNGb/tVt0CX2z4qwQGxF9VoNUdS9YdNYsurI2JaODP+J3JnC hn9kTGqtZigcp6JnJJ9gQzHtesyAKc5BckalQ/aVX6thPI1oUqFoLaN7S/mKJsYWB2YV b6tpqUpNkyjvoglEkv/JO4NDgogD5J+riZZrcLUJJGMCJaz50XYd3hibW4PZjWmAzNbI VCCbHa9gZbNFNmpWXWp7sQaYBtTx/BufK58gdlz75iLS9sjEUi53vJ/0o1fzIG/Bl9L9 26tQ== X-Received: by 10.49.71.141 with SMTP id v13mr53625992qeu.36.1373927479088; Mon, 15 Jul 2013 15:31:19 -0700 (PDT) Received: from wastrel.home.lan (d192-24-251-5.try.wideopenwest.com. [24.192.5.251]) by mx.google.com with ESMTPSA id w2sm58279342qec.8.2013.07.15.15.31.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Jul 2013 15:31:18 -0700 (PDT) Message-ID: <51E47835.1000004@gmail.com> Date: Mon, 15 Jul 2013 18:31:17 -0400 From: William Allen Simpson User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: pppext@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Pppext] draft-simpson-ppp-arc4-00.txt X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 22:31:31 -0000 Here's the reason that I was looking at archives. This is old stuff, reformatted and updated a little. Probably needs some more work. But with the wide-scale link snooping in the news -- as so many of us predicted 20+ years ago -- it's time to at least experiment. ARCFOUR has code already to go in routers. We need some implementation feedback from vendors, but this could get out the door pretty quickly. I was working on a Salsa variant, too, but then found out about his ChaCha successor, and so never made up my mind on which to document. Please talk about this in Germany. We'll also be discussing at Usenix Security. I also have an old session key negotiation draft lying around. This would all be better with nice PFS random keys.... === A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : The PPP ARCFOUR Encryption Protocol Author(s) : William Allen Simpson Filename : draft-simpson-ppp-arc4-00.txt Pages : 9 Date : 2013-07-15 Abstract: The Point-to-Point Protocol (PPP) [RFC1661] provides a standard method for transporting multi-protocol datagrams over point-to-point links. The PPP Encryption Control Protocol (ECP) [RFC1968] provides a method to negotiate and utilize encryption protocols over PPP encapsulated links. This document described the use of the ARCFOUR algorithm for encrypting PPP encapsulated packets. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-simpson-ppp-arc4 There's also a htmlized version available at: http://tools.ietf.org/html/draft-simpson-ppp-arc4-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/