Re: [rrg] RRG to hibernation

William Herrin <bill@herrin.us> Sat, 10 November 2012 13:42 UTC

Return-Path: <wherrin@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 0904E21F8587 for <rrg@ietfa.amsl.com>; Sat, 10 Nov 2012 05:42:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pu24RSA0y2lZ for <rrg@ietfa.amsl.com>; Sat, 10 Nov 2012 05:42:29 -0800 (PST)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by ietfa.amsl.com (Postfix) with ESMTP id 4248321F8529 for <rrg@irtf.org>; Sat, 10 Nov 2012 05:42:29 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id wc20so6196423obb.13 for <rrg@irtf.org>; Sat, 10 Nov 2012 05:42:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=JLgWbHRPEW8MuFbXiD/zMbEzuegC8LmIdlgRPSlvUDg=; b=lMLwELqBlfwuiyTZcKqZy/bEvu5Lmg/PP3YuJ6n/rPGQk8qAB5RhGN8N4hIvDa2xCY EX0ls9w+g7vn8QYGL+WizlCOU4WN62J0iux8vuJ/vzRXJDES8Wb/jrFcCAcgYiA70j4z RFgLLBIr9W1l00bIaagc4zWAwc34RJOmXCTg4UKMfpwotfLhCSXOzE2d4XPY3eCRkv8B fgmgcGvlwHNV3LvDGuXtCr7Scz7fQgIImErk+rTRf0UiXLFFTLib7qg2EUxyp+m7fpOj CV8uQ19Ql5ZKltcsxsmI8LKW+XSunXveZLWqyj1uAhoAIWahkw8Vy/MqgU8D+GuKdInP YQBw==
Received: by 10.60.14.6 with SMTP id l6mr10355278oec.87.1352554948716; Sat, 10 Nov 2012 05:42:28 -0800 (PST)
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.182.81.164 with HTTP; Sat, 10 Nov 2012 05:42:08 -0800 (PST)
In-Reply-To: <20121110032942.BD27018C113@mercury.lcs.mit.edu>
References: <20121110032942.BD27018C113@mercury.lcs.mit.edu>
From: William Herrin <bill@herrin.us>
Date: Sat, 10 Nov 2012 08:42:08 -0500
X-Google-Sender-Auth: uEdPuUguu7x-daXM3uPz9Hrq0I0
Message-ID: <CAP-guGVVtwWFayYfXaZ_1Fr9HNQaxUQ_WoRLLV6EhA8WC7rgBg@mail.gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: rrg@irtf.org
Subject: Re: [rrg] RRG to hibernation
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: Sat, 10 Nov 2012 13:42:34 -0000

On Fri, Nov 9, 2012 at 10:29 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>> From: Tony Li <tony.li@tony.li>

> We still have the same old kludgy BGP global routing system we always had,
> and _nothing_ has been proposed to improve/replace it.
>
>> The group has ... helped push the boundaries of routing farther
>> forward.
>
> Nonsense. It has produced no routing work at all.

Hi Noel,

I have a notion for a "routing" protocol which manages link changes
through dynamic readdressing and multiply addressing hosts. By and
large the addresses change so that the trivially aggregable routes
don't have to. Not just at the host level but all the way downstream
from the link change. Even bumps automatic resizing requirements
upstream so that over time any given router offers exactly one route
outward which automatically aggregates with the route its upstream
already holds.

It does require a new suite of transport protocols where layer 4 is as
loosely bound to layer 3 as layer 3 currently is to layer 2, along
with a new suite of APIs which don't expect the application layer to
manage remote addresses.

It's fresh. Might even be a genuinely new approach to routing. Are you
game to flesh it out and see how far we can run with it, even though
the odds of ever reaching deployment on an approach which requires us
to abandon TCP and UDP are not good?

Regards,
Bill Herrin


--
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004