IETF Logo Mail Archive

Re: [rrg] Rebooting the RRG

Scott Brim <scott.brim@gmail.com> Fri, 15 November 2013 15:54 UTC

Return-Path: <scott.brim@gmail.com>
X-Original-To: rrg@ietfa.amsl.com
Delivered-To: rrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A20E11E81E4 for <rrg@ietfa.amsl.com>; Fri, 15 Nov 2013 07:54:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o3lZCvf4L-GD for <rrg@ietfa.amsl.com>; Fri, 15 Nov 2013 07:54:57 -0800 (PST)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id CA90211E81EC for <rrg@irtf.org>; Fri, 15 Nov 2013 07:52:22 -0800 (PST)
Received: by mail-ob0-f170.google.com with SMTP id gq1so4044493obb.15 for <rrg@irtf.org>; Fri, 15 Nov 2013 07:52:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=f3HupHQBBdcM0Mt7hJwPZaCHppT+AXy+w4aiW25HWkg=; b=WsS9yYFlR+IgPNL4D7M4WD5pmkNiDNavhwWEfB/kq75Ax2izy6nrW+0qMaZ2i7fAgY 7wsVnRZ7p5O5ZN2Gj2x1/t5XbqgOcdYpnxDjDn9y9ustFo6LOvpuJuc/ls6eYkDhqEFe qFLe6mM/86tijoQcgVgE12COgpzgNcf4wWIFUXfZdScZYAhbDgCqm/mjOVSix69Vhsq8 IZvwudEzMZtWLrKvBHZ2mMw/nv0jltLQ/+xHSWH945+jMSHy111pwfYNGibRJuGpJAeC 53PRO+IOrmgZiTjezbQVrXEgBNVyFdgPD/PMo1EdJixdFU+/nAt31pFcdWkJet8VfRCb zCag==
X-Received: by 10.60.43.169 with SMTP id x9mr1266675oel.88.1384530737876; Fri, 15 Nov 2013 07:52:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 15 Nov 2013 07:51:57 -0800 (PST)
In-Reply-To: <B3E59CCB-BA8B-4335-8610-4EF9A48B694E@riw.us>
References: <5B131180-FA93-4A05-B3BE-3A23767EBD9D@netapp.com> <CAPv4CP_xs0Ki4Ada-CrBQftwtSfWVEK8gxohKTHEMHAEHP9s_A@mail.gmail.com> <CAG4d1rcXJzOC=tTqbCUK7i7a62vbiEyC9UCWLi0XvsXv8fW4qQ@mail.gmail.com> <FD7BEAB9-F967-4788-BBCA-6E06FBE585A8@tony.li> <B3E59CCB-BA8B-4335-8610-4EF9A48B694E@riw.us>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 15 Nov 2013 10:51:57 -0500
Message-ID: <CAPv4CP_6q3C-xMTPcNPMtgR6hEzfjQQE7sJmeCf0U415Gi=bNA@mail.gmail.com>
To: Russ White <russw@riw.us>
Content-Type: multipart/alternative; boundary="001a11330a00cfd6d404eb392e87"
Cc: "rrg@irtf.org" <rrg@irtf.org>
Subject: Re: [rrg] Rebooting the RRG
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.12
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: Fri, 15 Nov 2013 15:54:58 -0000

On Fri, Nov 15, 2013 at 10:24 AM, Russ White <russw@riw.us> wrote:

>
> Some things of interest might be the intersection of naming and routing,
> or the problems around centralizing control planes (though this might be
> more aligned with sdnrg). Maybe something around network programmability?


I'm composing a short list but I just want to nip one thing in the bud: We
can cede id/loc separation to SDNRG. Let them thrash with it for a while.
 We have spent a lot of time on it in RRG and other fora over the years,
and the conclusion is pretty clear: id/loc separation is not a _routing_
problem. Rather, it's a problem that identity-related functions take
location-related information and use it inappropriately. For example it's
not routing's fault, or problem, if some identification function uses an
IPv4 address as an identifier.

So this time, let's stick to routing problems. Russ suggests the
intersection of naming and routing. That could be a great topic if what is
meant is mechanisms for mapping from names to routing information and/or
forwarding information (network interface, path, nexthop etc.). I would
enjoy exploring routing in ICN (information-centric networking). Lixia can
explain how NDN has solved the whole problem :-).

More soon.

Thanks ... Scott

v2.23.0 | Report a Bug | By Email