[ranger] BOF situation with Ranger

Jari Arkko <jari.arkko@piuha.net> Mon, 09 February 2009 11:33 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ranger@core3.amsl.com
Delivered-To: ranger@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F06A3A6B68 for <ranger@core3.amsl.com>; Mon, 9 Feb 2009 03:33:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level:
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.277, 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 74+r0+4wuL+U for <ranger@core3.amsl.com>; Mon, 9 Feb 2009 03:33:18 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 8E6413A6A05 for <ranger@ietf.org>; Mon, 9 Feb 2009 03:33:18 -0800 (PST)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id A2CE719870C; Mon, 9 Feb 2009 13:33:22 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 6A5261986E4; Mon, 9 Feb 2009 13:33:22 +0200 (EET)
Message-ID: <49901439.6010709@piuha.net>
Date: Mon, 09 Feb 2009 13:32:09 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: ranger@ietf.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: "W. Mark Townsley" <townsley@cisco.com>
Subject: [ranger] BOF situation with Ranger
X-BeenThere: ranger@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing and Addressing in Next-Generation EnteRprises <ranger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ranger>, <mailto:ranger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ranger>
List-Post: <mailto:ranger@ietf.org>
List-Help: <mailto:ranger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ranger>, <mailto:ranger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2009 11:33:19 -0000

Fred and others,

The ADs have decided to not approve the RANGER BOF at this time. This 
decision is mainly due to the observation that we already have quite a 
bit of routing and addressing related work in the IETF/IRTF: the routing 
research group, the proposed LISP BOF, many of the arguments for the 
proposed 6AI BOF relate to address independence as well, etc. When 
looking at all of these efforts, there was far less discussion and 
general interest on RANGER than the other ones. On the other hand, the 
proposal was submitted a bit late so I at least did not have time to 
read all the material and I presume others may have had the same problem.

IETF work generally starts when there's a technical issue that can be 
solved _and_ there is wide-spread community interest in solving it in a 
particular way. I suspect we will see many future efforts in this space 
-- but for any effort to make sense, there has to be that community that 
is interested in discussing it. I would also like to offer the 
possibility of independent submissions to the RFC Editor or AD sponsored 
individual submission RFCs through the IETF. These might be useful for 
folks who want to document something which does not warrant an entire 
IETF WG.

Also, Fred and I have been talking off-list about a possible INT-AREA 
presentation around SEAL. Stay tuned.

Jari