[RAM] (no subject)

Lixia Zhang <lixia@CS.UCLA.EDU> Wed, 22 August 2007 19:24 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1INvoi-00011Y-2t; Wed, 22 Aug 2007 15:24:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1INvog-00011O-A6 for ram@iab.org; Wed, 22 Aug 2007 15:24:34 -0400
Received: from kiwi.cs.ucla.edu ([131.179.128.19]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INvoe-0002Df-PK for ram@iab.org; Wed, 22 Aug 2007 15:24:34 -0400
Received: from [131.179.33.100] (Cs-33-100.CS.UCLA.EDU [131.179.33.100]) by kiwi.cs.ucla.edu (8.13.8+Sun/8.13.8/UCLACS-6.0) with ESMTP id l7MJOT3R000569; Wed, 22 Aug 2007 12:24:29 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <8337AF64-9586-4265-8A92-0915457BF5C0@cs.ucla.edu>
Content-Transfer-Encoding: 7bit
From: Lixia Zhang <lixia@CS.UCLA.EDU>
Date: Wed, 22 Aug 2007 12:24:28 -0700
To: ram@iab.org
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 1.3 (+)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: IAB IAB <iab@ietf.org>
Subject: [RAM] (no subject)
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

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