From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4180221F36D; Sun, 21 Dec 2014 12:27:13 -0800 (PST) Received: by mail-oi0-f45.google.com with SMTP id x69so7670842oia.4; Sun, 21 Dec 2014 12:27:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=MLpri3PT0FlgrlmLxhKtP9tGYPPaQ6BcDzZqlSwu8GQ=; b=mi9RlUK1sBrsSRRLa3SS+XVNW3BjjsyVPOhVb95mUBRHcv/SivwkhHfYgd3TB1GUYq 778cAs/JpyYcWeVGiIV/NEWY6Ppg1/VdcjEBhqr1EcFDWstzUW2/gUkca59DTsUkxmp1 1AdtlLqJaYt+kGzH2I2gPZrQUEFFFzcOuhESddnKlquNCpEAg0/Fy2tFCHOQojOHn8Kh 9UZu2be2CKBdqA9PXP5GZx1VKkdnQX4tRLYI7m33othmxpTHH9BtR9SZRUXJtyzxTuly jw7VzCU2JV6IHylGoFDyI887neHwTYwm94J23j/bXqYK/f8s2sCDTAiLY8Oabe56PA+g 1dFA== MIME-Version: 1.0 X-Received: by 10.60.52.72 with SMTP id r8mr11159695oeo.75.1419193632851; Sun, 21 Dec 2014 12:27:12 -0800 (PST) Received: by 10.202.169.209 with HTTP; Sun, 21 Dec 2014 12:27:12 -0800 (PST) In-Reply-To: <54972C0F.8090806@tomh.org> References: <54972C0F.8090806@tomh.org> Date: Sun, 21 Dec 2014 12:27:12 -0800 Message-ID: From: Dave Taht To: "codel@lists.bufferbloat.net" , bloat Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Codel] Fwd: [Ns-developers] ns-2.36 release candidate available for testing X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Dec 2014 20:27:42 -0000 I have not had time to test much of all the aqm and packet scheduling stuff that has landed in ns2 mainline, personally. Hopefully all of you out there using out of tree patches can try what has been mainlined to see what, if anything broke. Please direct replies and feedback at the ns-developers list, not here. ---------- Forwarded message ---------- From: Tom Henderson Date: Sun, Dec 21, 2014 at 12:22 PM Subject: [Ns-developers] ns-2.36 release candidate available for testing To: ns-developers list , "ns-users@isi.edu" Hi all, I'm preparing to release a new ns-2 version, numbered ns-2.36. There is a wiki page and an initial release candidate posted here: http://nsnam.isi.edu/nsnam/index.php/Roadmap The main differences between ns-2.35 and ns-2.36 are the following: * small fixes to the allinone 'install' script to build on current systems * a variety of changes to ns-2 source code and build scripts to compile on newer gcc and also clang-based systems * new AQM and cable system models, including CoDel, SFQCoDel, CoDel-DT, PIE, and DocsisLink * a Bonnmotion mobility example I would like to release this by the second half of January. There are a few open issues that might lead to some updates, including the RED issue I just mailed about; the currently open issues are listed on the wiki page. If you would like to suggest changes, or find problems with these release candidates, please let us know on the ns-developers mailing list, or contact me off list. Thanks, Tom --=20 Dave T=C3=A4ht thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks