Re: [rrg] Rebooting the RRG

Scott Brim <scott.brim@gmail.com> Fri, 15 November 2013 17:01 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 6072011E81CC for <rrg@ietfa.amsl.com>; Fri, 15 Nov 2013 09:01:42 -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 qDKFQQKNZCZs for <rrg@ietfa.amsl.com>; Fri, 15 Nov 2013 09:01:41 -0800 (PST)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id B74FB11E81B2 for <rrg@irtf.org>; Fri, 15 Nov 2013 09:01:41 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id wp4so4140038obc.35 for <rrg@irtf.org>; Fri, 15 Nov 2013 09:01:41 -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=QJcssFemogsHnIYidRvKmc4VtgAeEAM5ey5O1v43dEI=; b=B3f9wldITHQrO1dwmDiX8ntoN43B7pRlhpKO3nq6PNbySWkuST5XS4Ka1tJFwJeOXO yEiXr59Y+Xj2TxH2qz5Irw270YF1OtxYPVdcJOsSn1PsoD3dsfL4jCGUWO5bSilQP385 1bzJwQi1BIAkIDlH1QvNXbM0uBntapliELny5LLQXYVkj8QRGzY6CYzFkzI0cXWecIsO 1BlLAU5sXrwmfjP9ToDQGh/L+/H6z+BRsIZjm24Aq9+vMyLVF5vKvFQtULjQKaXE2ZnN K4Nm+t0pXwgOUVhhFeQOZuJYsNKo3SIICOkt7xPYxshjZkiCz1lHeLM81BBZPlxW7C4B VMoQ==
X-Received: by 10.182.104.130 with SMTP id ge2mr7882859obb.6.1384534901046; Fri, 15 Nov 2013 09:01:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 15 Nov 2013 09:01:20 -0800 (PST)
In-Reply-To: <FD7BEAB9-F967-4788-BBCA-6E06FBE585A8@tony.li>
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>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 15 Nov 2013 12:01:20 -0500
Message-ID: <CAPv4CP_tNAbE0MbY=kLPuNTdpnLkQ5ia7N=z_ibXfBqsVTXcAA@mail.gmail.com>
To: Tony Li <tony.li@tony.li>
Content-Type: multipart/alternative; boundary=089e0112cf10f4ca8d04eb3a26db
Cc: IRTF Routing RG <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 17:01:42 -0000

Tony, I didn't take this off-list yet since a small group hasn't
stabilized. I figure you'll say when.

I would be interested in exploring the scope of "routing" in the modern
Internet. The RRG "is chartered to explore routing and addressing problems
that are important to the development of the Internet but are not yet
mature enough for engineering work within the IETF". I know we've always
meant IP routing and addressing, but there is a lot more "routing" going
on. For example,

  - multi-layer routing (using information from multiple layers)
  - research in SDN routing
  - explore the many things BGP is used for, for new meanings of "routing"
  - ICN (information-centric networking)

Routing in ICNs is full of ideas, some of them repeating what we went
through with IP, e.g. Dave Mills's dynamic hierarchical routing (I don't
recall exactly what he called it). I haven't seen two-byte PIP come back
from the dead but I wouldn't be surprised. ICNRG meets regularly at IETFs
and SigComm. A couple of joint meetings to argue about routing would be
quite interesting.

Then there are IoT, DTN, satellite, and other self-assembled meshes - all
possibly interrelated.

Finally, routing for privacy. We have lots of efforts to distribute traffic
to avoid surveillance. How could routing contribute? This might build on
BGP multiple paths, or maybe source-asserted trees.

That's all I have right now.

Scott