Re: [lisp] Short name for DFZ?

jnc@mercury.lcs.mit.edu (Noel Chiappa) Tue, 22 October 2013 15:43 UTC

Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 171E211E84C6 for <lisp@ietfa.amsl.com>; Tue, 22 Oct 2013 08:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.411
X-Spam-Level:
X-Spam-Status: No, score=-6.411 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Z=0.259]
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 kWGu63SFtU4z for <lisp@ietfa.amsl.com>; Tue, 22 Oct 2013 08:43:27 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id CC92721E8089 for <lisp@ietf.org>; Tue, 22 Oct 2013 08:43:18 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id D944218C1ED; Tue, 22 Oct 2013 11:43:17 -0400 (EDT)
To: lisp@ietf.org
Message-Id: <20131022154317.D944218C1ED@mercury.lcs.mit.edu>
Date: Tue, 22 Oct 2013 11:43:17 -0400
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [lisp] Short name for DFZ?
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2013 15:43:32 -0000

    > From: Sharon Barkai <Sharon@Contextream.com>

    > Underlay ?

I suspect that's not optimal because the place I used the term the most was
in talking about LISP's possible future impact on routing in the DFZ - i.e.
the interaction between LISP and DFZ routing. So using a term that would tend
to lead to thinking about it as some sort of amorphous blob 'down there' is
probably not optimal....

But it rurns out that it's no longer urgent to find an alternative, since
it turns out most uses of 'DFZ' where in that section that got exiled to
another document.


    > From: Scott Brim <scott.brim@gmail.com>

    > The DFZ != "core". I would just clearly define it and use the acronym.

    > From: Roger Jorgensen <rogerj@gmail.com>

    > I would say define the term DFZ and add some context to it .. It is the
    > most used understanding of the "core" of Internet. Even not technical
    > people mostly get it.

Well, I don't recall exactly who wanted to get rid of it, or why - it was at
the interim. I do have this vague recollection that the people there were
agreeable to removing it.

I personally agree with the points that both of you make (that 'DFZ' has a
specific technical meaning - and the one I expressly wanted to talk about -
that I'm not sure is captured by 'core', although they are roughly
equivalent), but...

	Noel