IETF Logo Mail Archive

Re: Last Call for draft-ietf-rolc-apr-00.txt

Steve Deering <deering@parc.xerox.com> Thu, 26 October 1995 00:46 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22286; 25 Oct 95 20:46 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa22282; 25 Oct 95 20:46 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id UAA20410; Wed, 25 Oct 1995 20:09:54 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id UAA02097 for rolc-out; Wed, 25 Oct 1995 20:18:57 -0400
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id UAA02088 for <rolc@nexen.com>; Wed, 25 Oct 1995 20:18:54 -0400
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id UAA20388 for <rolc@nexen.com>; Wed, 25 Oct 1995 20:07:34 -0400
Received: from digit.parc.xerox.com ([13.2.117.114]) by alpha.xerox.com with SMTP id <14842(3)>; Wed, 25 Oct 1995 17:14:23 PDT
Received: from localhost by digit.parc.xerox.com with SMTP id <75270>; Wed, 25 Oct 1995 17:14:14 -0700
To: curtis@ans.net
Cc: rolc@nexen.com, deering@parc.xerox.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
In-reply-to: curtis's message of Wed, 25 Oct 95 15:08:24 -0800. <199510252208.SAA18653@brookfield.ans.net>
Date: Wed, 25 Oct 1995 17:14:05 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Deering <deering@parc.xerox.com>
Message-Id: <95Oct25.171414pdt.75270@digit.parc.xerox.com>
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

> We need a term which defines the region for which cut-through or
> direct connection is possible.  The term NBMA network fits well but
> the term is defined as something that doesn't support broadcast so a
> another term is wanted (maybe not needed, but wanted).

I don't know if this helps, but in IPv6, we have adopted the term "link" for
any instance of a layer (IP - 1) service.  This terminology is based on the
traditional usage by (some) IP people of the term "link layer" for whatever
is below IP.  It is a synonym for the OSI folks call a "subnetwork".  Here's
our definition:

   link        - a communication facility or medium over which nodes can
                 communicate at the link layer, i.e., the layer
                 immediately below IPv6.  Examples are Ethernets (simple
                 or bridged); PPP links; X.25, Frame Relay, or ATM
                 networks; and internet (or higher) layer "tunnels",
                 such as tunnels over IPv4 or IPv6 itself.

Steve

v2.8.7 | Report a Bug | By Email