Re: [rrg] belated msg: further description of the recommendation process

jnc@mercury.lcs.mit.edu (Noel Chiappa) Tue, 15 December 2009 14:55 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 4F5D93A6A2B for <rrg@core3.amsl.com>; Tue, 15 Dec 2009 06:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.401
X-Spam-Level:
X-Spam-Status: No, score=-6.401 tagged_above=-999 required=5 tests=[AWL=0.198, 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 9PosAKfJqby3 for <rrg@core3.amsl.com>; Tue, 15 Dec 2009 06:55:57 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id A89F23A6A6A for <rrg@irtf.org>; Tue, 15 Dec 2009 06:55:57 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 34F2A6BE58A; Tue, 15 Dec 2009 09:55:43 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20091215145543.34F2A6BE58A@mercury.lcs.mit.edu>
Date: Tue, 15 Dec 2009 09:55:43 -0500
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] belated msg: further description of the recommendation process
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: Tue, 15 Dec 2009 14:55:58 -0000

    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>

    >>> Also I feel it should support hierarchy, even if we don't need a
    >>> hierarchy from the start.

    > I was thinking about a hierarchy of namespaces

To help me understand how this would work, could you give an example?

    > Just make a couple of the basic data definitions recursive, and you've
    > got both hierarchies.

And an example of this too...

	Noel