IETF Logo Mail Archive

Re: [rrg] Paul Jakma's blog article

jnc@mercury.lcs.mit.edu (Noel Chiappa) Sat, 13 February 2010 03:16 UTC

Return-Path: <jnc@mercury.lcs.mit.edu>
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 A4E123A7939 for <rrg@core3.amsl.com>; Fri, 12 Feb 2010 19:16:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.439
X-Spam-Level:
X-Spam-Status: No, score=-6.439 tagged_above=-999 required=5 tests=[AWL=0.160, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 CMYYDupAKQp7 for <rrg@core3.amsl.com>; Fri, 12 Feb 2010 19:16:56 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 6B89A3A763B for <rrg@irtf.org>; Fri, 12 Feb 2010 19:16:56 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1CA3F6BE57B; Fri, 12 Feb 2010 22:18:15 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20100213031816.1CA3F6BE57B@mercury.lcs.mit.edu>
Date: Fri, 12 Feb 2010 22:18:15 -0500
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] Paul Jakma's blog article
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: Sat, 13 Feb 2010 03:16:58 -0000

    > From: Robin Whittle <rw@firstpr.com.au>

    > the LISP team will soon be turning to a DNS-based global mapping
    > resolution system

Ah, not quite: an alternative will be available, and design on it is
continuing, but any decision on actually switching to it will require wide
consultion, among people who are actually working on, and deploying, LISP.
I.e. the design process, and the deployment process, are not coupled.

	Noel

v2.23.0 | Report a Bug | By Email