[RAM] RAM list is closing

Dow Street <dow.street@linquest.com> Thu, 10 July 2008 10:30 UTC

Return-Path: <ram-bounces@ietf.org>
X-Original-To: ram-archive@optimus.ietf.org
Delivered-To: ietfarch-ram-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 029873A6986; Thu, 10 Jul 2008 03:30:48 -0700 (PDT)
X-Original-To: ram@core3.amsl.com
Delivered-To: ram@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 5375E3A6849 for <ram@core3.amsl.com>; Thu, 10 Jul 2008 03:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
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 ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id E0+MFih9gwUN for <ram@core3.amsl.com>; Thu, 10 Jul 2008 03:30:46 -0700 (PDT)
Received: from smtp150.iad.emailsrvr.com (smtp150.iad.emailsrvr.com []) by core3.amsl.com (Postfix) with ESMTP id 549F13A67AB for <ram@ietf.org>; Thu, 10 Jul 2008 03:30:46 -0700 (PDT)
Received: from relay5.relay.iad.emailsrvr.com (localhost []) by relay5.relay.iad.emailsrvr.com (SMTP Server) with ESMTP id B2E706D8924 for <ram@ietf.org>; Thu, 10 Jul 2008 06:30:59 -0400 (EDT)
Received: by relay5.relay.iad.emailsrvr.com (Authenticated sender: dow.street-AT-linquest.com) with ESMTP id A08D36D87ED for <ram@ietf.org>; Thu, 10 Jul 2008 06:30:59 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v753.1)
References: <38801DC5-DD45-47FB-BA76-929EED17B047@linquest.com>
Message-Id: <3266255D-C1E8-4B2B-A38A-FD2DB359021B@linquest.com>
From: Dow Street <dow.street@linquest.com>
Date: Thu, 10 Jul 2008 06:30:58 -0400
To: ram@ietf.org
X-Mailer: Apple Mail (2.753.1)
Subject: [RAM] RAM list is closing
X-BeenThere: ram@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ram>
List-Post: <mailto:ram@ietf.org>
List-Help: <mailto:ram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ram-bounces@ietf.org
Errors-To: ram-bounces@ietf.org

Dear RAM list participants,

Last year a decision was made to move the discussion of new routing  
and addressing architectures from the RAM mailing list to the RRG  
mailing list.  At that point, the RAM list entered something of a  
dormant phase, with its ongoing utility to be evaluated over time.   
Lixia's email below provides additional background.

Based on the very low level of list activity since then, the IAB has  
determined that the RAM list is no longer needed and intends to close  
the list in the near future.  List participants are directed to the  
RRG mailing list for any follow-on discussions of new routing and  
addressing architectures.  The architecture-discuss list is also  
available for related architecture topics that fall outside of RRG  
scope.  Information about architecture-discuss can be found at  

The IAB intends to maintain a publicly accessible archive for RAM.

for the IAB,

Dow Street
IAB Exec Dir

On Aug 22, 2007, at 12:24 PM, Lixia Zhang wrote:

> Dear RAM list participants,
> As you all know, currently we have routing and addressing architecture
> discussions going on two separate mailing lists, RAM and RRG. This is
> solely a consequence of past events: RAM list was created November  
> last
> year following the IAB workshop on routing and addressing.  RRG was
> rechartered March this year to explore new routing architectures and
> protocols; since then RRG list has been carrying active discussions
> towards that goal. As RRG co-chairs, Tony Li and I would welcome  
> all the
> related discussions occurring on the RRG list.  However because RAM  
> list
> started earlier, a big part of the discussions have continued on  
> RAM list.
> Wearing my RAM list moderator hat, and with the agreement of the  
> IAB, I
> would like to urge the community to move all the discussions around a
> new routing and addressing architecture research to RRG mailing  
> list (To
> subscribe RRG list, send mail to rrg-request@psg.com with the word
> "subscribe" in the body of your email).
> The IAB plans to review, over time, whether the RAM list then  
> continues
> to serve a useful function -- i.e., whether there are routing &
> addressing topics worthy of discussion that belong neither in the RRG
> discussions nor in any other existing IETF mailing list venue.  Please
> feel free to help identify those topics and discussions. Other related
> IETF WGs include IDR and GROW at this time, and new venues may be
> created as results from the RRG or elsewhere reach status where
> standardization can begin.
> Lixia (with multiple hats on)
> _______________________________________________
> RAM mailing list
> RAM@iab.org
> https://www1.ietf.org/mailman/listinfo/ram

RAM mailing list