Re: [rrg] London

heinerhummel@aol.com Sun, 12 January 2014 17:41 UTC

Return-Path: <heinerhummel@aol.com>
X-Original-To: rrg@ietfa.amsl.com
Delivered-To: rrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEC7D1ADFC3 for <rrg@ietfa.amsl.com>; Sun, 12 Jan 2014 09:41:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.263
X-Spam-Level:
X-Spam-Status: No, score=0.263 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78EeY0yYr_Fm for <rrg@ietfa.amsl.com>; Sun, 12 Jan 2014 09:41:06 -0800 (PST)
Received: from omr-m04.mx.aol.com (omr-m04.mx.aol.com [64.12.143.78]) by ietfa.amsl.com (Postfix) with ESMTP id 2142D1ADFA0 for <rrg@irtf.org>; Sun, 12 Jan 2014 09:41:06 -0800 (PST)
Received: from mtaomg-mcc01.mx.aol.com (mtaomg-mcc01.mx.aol.com [172.26.253.85]) by omr-m04.mx.aol.com (Outbound Mail Relay) with ESMTP id 46A8D70001D57; Sun, 12 Jan 2014 12:40:55 -0500 (EST)
Received: from core-dqa003a.r1000.mail.aol.com (core-dqa003.r1000.mail.aol.com [172.29.211.201]) by mtaomg-mcc01.mx.aol.com (OMAG/Core Interface) with ESMTP id CC980380000C9; Sun, 12 Jan 2014 12:40:54 -0500 (EST)
To: lars@netapp.com
X-MB-Message-Source: WebUI
Received: from 178.26.195.50 by webmail-m276.sysops.aol.com (64.12.145.243) with HTTP (WebMailUI); Sun, 12 Jan 2014 12:40:54 -0500
MIME-Version: 1.0
From: heinerhummel@aol.com
X-MB-Message-Type: User
Content-Type: multipart/alternative; boundary="--------MB_8D0DDD493FF397D_17E4_1270F0_webmail-m276.sysops.aol.com"
X-Mailer: Webmail 38252-STANDARD
Message-Id: <8D0DDD493F352A2-17E4-54879@webmail-m276.sysops.aol.com>
X-Originating-IP: [178.26.195.50]
Date: Sun, 12 Jan 2014 12:40:54 -0500 (EST)
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1389548455; bh=RV4S/dzZENGzv7YFDbfCsLvCMYi1eJbxvfCnjuX5uP8=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=QW4Nrc9qz6Q/wauAVMephB1MRYFfgUyJr0d+WEUnvFyXvWhiJ1PWKHSnSsdNyVfF2 b0g7B6HxsvCdYIpX5pyuYN6a/OYd8uGJBrq/3KuX388I1DDSgehsLY3OdkfmYAPiQE PBXqHcjPMfAReJx78Z6RBalWBxOVUwHYB9FSIKCo=
x-aol-sid: 3039ac1afd5552d2d3a65d47
Cc: rrg@irtf.org
Subject: Re: [rrg] London
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/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, 12 Jan 2014 17:41:08 -0000

Sounds good to me.


Myself, I have already tabled my suggestions and did refer to a respective academic publishment  (see my email from 30th Nov.).


Heiner



-----Urspr√ľngliche Mitteilung----- 
Von: Eggert, Lars <lars@netapp.com>;
An: Heiner Hummel <heinerhummel@aol.com>;
Cc: Tony Li <tony.li@tony.li>;; IRTF Routing RG <rrg@irtf.org>;
Verschickt: So, 12 Jan 2014 8:39 am
Betreff: Re: [rrg] London


Hi,

On 2014-1-11, at 21:24, Heiner Hummel <heinerhummel@aol.com>; wrote:
> Given that the IESG doesn't care about IPv4 anymore

so even if that were true, what the IESG cares for should have little impact on 
what an IRTF research group is looking into.

I thought Tony's email was spot-on. If the RRG wants to remain chartered, it 
needs to become active again and identify some topics that it wants to 
investigate. Looking at what's been published by academics in the recent past 
seems a useful exercise in order to find some of those topics.

And the group needs a core set of participants that are willing to put in the 
energy to make some successful meetings happen, by re-energizing the broader 
routing community and by inviting folks that have interesting things to present 
to show up to do so.

Lars