Re: [rrg] Recommendation and what happens next
Tony Li <tony.li@tony.li> Sun, 07 March 2010 05:32 UTC
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8294A3A9073 for <rrg@core3.amsl.com>; Sat, 6 Mar 2010 21:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.858
X-Spam-Level:
X-Spam-Status: No, score=-1.858 tagged_above=-999 required=5 tests=[AWL=0.741, 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 wLdeDxgUJyln for <rrg@core3.amsl.com>; Sat, 6 Mar 2010 21:32:03 -0800 (PST)
Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by core3.amsl.com (Postfix) with ESMTP id 6D9473A9115 for <rrg@irtf.org>; Sat, 6 Mar 2010 21:32:03 -0800 (PST)
Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta12.emeryville.ca.mail.comcast.net with comcast id q5Mq1d0030EPchoAC5Y77l; Sun, 07 Mar 2010 05:32:07 +0000
Received: from [192.168.0.113] ([24.6.155.154]) by omta01.emeryville.ca.mail.comcast.net with comcast id q5Y41d0043L8a8Q8M5Y53D; Sun, 07 Mar 2010 05:32:07 +0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Sat, 06 Mar 2010 21:32:02 -0800
From: Tony Li <tony.li@tony.li>
To: Robin Whittle <rw@firstpr.com.au>, RRG <rrg@irtf.org>
Message-ID: <C7B87A52.4ED8%tony.li@tony.li>
Thread-Topic: Recommendation and what happens next
Thread-Index: Acq9t4O3K8odomp5IEatTvHfp3Yz3w==
In-Reply-To: <4B931291.3040905@firstpr.com.au>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Lixia Zhang <lixia@CS.UCLA.EDU>
Subject: Re: [rrg] Recommendation and what happens next
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 05:32:04 -0000
Hi Robin, > Maybe I missed something on the mailing list, but I only just > realised from the agenda of the next meeting: > > http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGagendaAnaheim > > that the Recommendation is to be discussed all day then. As always, the agenda will not be final until the meeting starts. And sometimes not even then. ;-) > Can you explain what happens next? No. ;-) ;-) ;-) What I would like to have happen next is nothing but fantasy. What I expect will happen will look like: - Some initial discussion - Presentation of the recommendation - Feedback afterwards > Is the Recommendation to be discussed on the mailing list between > now and the meeting? Will it be discussed after the meeting, and > if so for how long? Yes, folks are welcome to discuss the recommendation on the mailing list between now and the meeting. Yes, it will undoubtedly be discussed after the meeting, probably for several years. ;-) > Do you judge consensus regarding the Recommendation at the meeting > or on the list? Given the lack of consensus that we have seen so far, there's not going to even be a call for consensus. > Is there an absolute deadline for finalising the RRG Report? Not that I know of. Of course, if we take too long, the IRTF Chair may step in. > What happens once it is finalised? I understand the IESG will > consider it. Will the question of what to do next - which, if > any, architectures are to be developed in the IETF - be discussed > on the IETF list and/or the RRG list? > > I assume the RRG itself will continue, at least in the form of an > email list, until the IESG's decision. The IESG is free to do whatever it likes with the recommendation. My guess is that there will be cursing involved. ;-) Eventually however, I would expect that the IESG would open a WG in the routing area to pursue this. Where the discussions occur, if any, is up to the IESG. I would expect that the RRG would continue on and address other routing research issues. The RRG has been a standing group for some time and has looked at numerous issues. This is only the latest work item. Other obvious things that may be taken up: prevention of micro-loops, multi-party routing in mobile networks, etc. I would expect that the next work item would be under new leadership, more appropriate to the subject matter. Tony
- [rrg] FW: I-D Action:draft-irtf-rrg-recommendatio… Tony Li
- [rrg] Recommendation and what happens next Robin Whittle
- Re: [rrg] FW: I-D Action:draft-irtf-rrg-recommend… Robin Whittle
- Re: [rrg] Recommendation and what happens next Tony Li
- Re: [rrg] FW: I-D Action:draft-irtf-rrg-recommend… Tony Li
- Re: [rrg] FW: I-D Action:draft-irtf-rrg-recommend… Robin Whittle
- Re: [rrg] Recommendation and what happens next Robin Whittle
- Re: [rrg] FW: I-D Action:draft-irtf-rrg-recommend… Tony Li
- Re: [rrg] Recommendation and what happens next Tony Li
- Re: [rrg] Recommendation and what happens next Brian E Carpenter
- Re: [rrg] Recommendation and what happens next Tony Li
- [rrg] Why won't supporters of Loc/ID Separation (… Robin Whittle
- Re: [rrg] Recommendation and what happens next Robin Whittle
- Re: [rrg] Why won't supporters of Loc/ID Separati… Tony Li
- Re: [rrg] Recommendation and what happens next Tony Li
- Re: [rrg] Recommendation and what happens next Robin Whittle
- Re: [rrg] Why won't supporters of Loc/ID Separati… Robin Whittle
- Re: [rrg] Recommendation and what happens next Russ White
- Re: [rrg] Recommendation and what happens next Templin, Fred L
- Re: [rrg] Recommendation and what happens next Templin, Fred L
- [rrg] IRON-RANGER scalability and support for pac… Robin Whittle
- Re: [rrg] IRON-RANGER scalability and support for… Templin, Fred L
- Re: [rrg] Recommendation and what happens next Tony Li
- Re: [rrg] Why won't supporters of Loc/ID Separati… Tony Li
- Re: [rrg] Recommendation and what happens next Brian E Carpenter
- Re: [rrg] Recommendation and what happens next Scott Brim
- Re: [rrg] Recommendation and what happens next Templin, Fred L
- Re: [rrg] IRON-RANGER scalability and support for… Robin Whittle
- Re: [rrg] Recommendation and what happens next Robin Whittle
- Re: [rrg] Recommendation and what happens next Tony Li
- Re: [rrg] Recommendation and what happens next Robin Whittle
- Re: [rrg] Recommendation and what happens next Robin Whittle
- Re: [rrg] Recommendation and what happens next Scott Brim
- Re: [rrg] Why won't supporters of Loc/ID Separati… Scott Brim
- Re: [rrg] Why won't supporters of Loc/ID Separati… Robin Whittle
- Re: [rrg] IRON-RANGER scalability and support for… Templin, Fred L
- Re: [rrg] Recommendation and what happens next Templin, Fred L
- Re: [rrg] Why won't supporters of Loc/ID Separati… Templin, Fred L
- Re: [rrg] Recommendation and what happens next Scott Brim
- Re: [rrg] IRON-RANGER scalability and support for… Robin Whittle
- Re: [rrg] IRON-RANGER scalability and support for… Templin, Fred L
- Re: [rrg] IRON-RANGER scalability and support for… Robin Whittle
- Re: [rrg] IRON-RANGER scalability and support for… Templin, Fred L
- Re: [rrg] IRON-RANGER scalability and support for… Robin Whittle
- Re: [rrg] IRON-RANGER scalability and support for… Templin, Fred L
- Re: [rrg] IRON-RANGER scalability and support for… Robin Whittle
- Re: [rrg] IRON-RANGER scalability and support for… Templin, Fred L
- Re: [rrg] IRON-RANGER scalability and support for… Robin Whittle
- Re: [rrg] IRON-RANGER scalability and support for… Templin, Fred L
- Re: [rrg] IRON-RANGER scalability and support for… Robin Whittle
- Re: [rrg] IRON-RANGER scalability and support for… Templin, Fred L
- [rrg] Comments on 'draft-whittle-ivip-arch' Templin, Fred L
- Re: [rrg] Comments on 'draft-whittle-ivip-arch' Robin Whittle
- Re: [rrg] Comments on 'draft-whittle-ivip-arch' Robin Whittle