IETF Logo Mail Archive

RE: Border Router term (was: [Autoconf] new version draft-ietf-autoconf-statement-02 (pre-release))

"Teco Boot" <teco@inf-net.nl> Fri, 16 November 2007 14:26 UTC

Return-path: <autoconf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1It28w-0006BW-2u; Fri, 16 Nov 2007 09:26:02 -0500
Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1It28u-00069p-VZ for autoconf-confirm+ok@megatron.ietf.org; Fri, 16 Nov 2007 09:26:00 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1It28u-000682-LN for autoconf@ietf.org; Fri, 16 Nov 2007 09:26:00 -0500
Received: from hpsmtp-eml14.kpnxchange.com ([213.75.38.114]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1It28t-0003UY-TM for autoconf@ietf.org; Fri, 16 Nov 2007 09:26:00 -0500
Received: from hpsmtp-eml09.kpnxchange.com ([213.75.38.109]) by hpsmtp-eml14.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Nov 2007 15:25:58 +0100
Received: from M90Teco ([86.83.9.22]) by hpsmtp-eml09.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Nov 2007 15:25:58 +0100
From: Teco Boot <teco@inf-net.nl>
To: 'Alexandru Petrescu' <alexandru.petrescu@gmail.com>
References: <Ps3sNn2nwRLn.cZMN23JV@outbound.mailhop.org> <7.0.0.16.2.20071116130938.05163c18@ie.niigata-u.ac.jp> <008001c82838$50f37030$f2da5090$@nl> <473D7CAC.9040806@inria.fr> <00c001c82856$bba57360$32f05a20$@nl> <473DA174.6050600@gmail.com>
In-Reply-To: <473DA174.6050600@gmail.com>
Subject: RE: Border Router term (was: [Autoconf] new version draft-ietf-autoconf-statement-02 (pre-release))
Date: Fri, 16 Nov 2007 15:25:45 +0100
Message-ID: <00cd01c8285c$9353bce0$b9fb36a0$@nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcgoWHZ6abSvV7BTSAesk5QTZZ4eeQAAzT9A
Content-Language: nl
X-OriginalArrivalTime: 16 Nov 2007 14:25:58.0574 (UTC) FILETIME=[9B2F74E0:01C8285C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: autoconf@ietf.org, 'Emmanuel Baccelli' <Emmanuel.Baccelli@inria.fr>
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
Errors-To: autoconf-bounces@ietf.org

> Do we have an RFC definition of the Border Router term?  I know of Area
> BR (ABR in ospf) and  ASBR (Autonomous System Border Router).  But is
> there a short English  "Border Router" term defined in an RFC? (don't
> direct me to manufacturer manuals or Wikipedia in German :-)
> 
> If yes then let's reuse.  If not then let's define.
I don't speak German very well, I'm Dutch;-)

Border Router (BR)
      A border router participates in multiple routing domains, and
      often multiple routing protocols.  A BR defines the border between
      its multiple routing domains.  A BR is responsible for presenting
      a consistent picture of the nodes reachable through itself to each
      routing domain.  A BR determines the routing information to
      propagate between different routing domains.
http://www.ietf.org/internet-drafts/draft-ietf-autoconf-manetarch-07.txt
Print this and put it under your pillow;-)
Tomorrow (or next week) I expect no questions anymore, where answers can be
found in this document.

Cheers, Teco





_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www1.ietf.org/mailman/listinfo/autoconf

v2.23.0 | Report a Bug | By Email