Re: [RAM] Different approaches for different protocols

jnc@mercury.lcs.mit.edu (Noel Chiappa) Fri, 21 December 2007 03:19 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5YQR-0002M0-Is; Thu, 20 Dec 2007 22:19:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5YQP-0002Ll-8m for ram@iab.org; Thu, 20 Dec 2007 22:19:49 -0500
Received: from mercury.lcs.mit.edu ([18.26.0.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5YQN-0002yb-4d for ram@iab.org; Thu, 20 Dec 2007 22:19:49 -0500
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 85FAC872ED; Thu, 20 Dec 2007 22:19:46 -0500 (EST)
To: ram@iab.org
Subject: Re: [RAM] Different approaches for different protocols
Message-Id: <20071221031946.85FAC872ED@mercury.lcs.mit.edu>
Date: Thu, 20 Dec 2007 22:19:46 -0500
From: jnc@mercury.lcs.mit.edu
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

    > From: RJ Atkinson <rja@extremenetworks.com>

    > (A) I'd encourage keeping your concepts (1) and (2) separate, in
    > separate drafts and ideally with separate names, at least for now.
    > (B) Separately, modularity and clean architecture would argue for
    > keeping the mapping database structure separately specified from any
    > other bits of protocol design.
    > ...
    > keeping things separate and modular seems beneficial all around for
    > now.

Not just for now - it's even more valuable in the long run.

Modularity is your friend when it comes to archiectural lifetime.

	Noel

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram