EBGP over unnumbered serial lines

Radha Gowda <rxg@proteon.com> Thu, 28 September 1995 17:25 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13812; 28 Sep 95 13:25 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13808; 28 Sep 95 13:25 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa15932; 28 Sep 95 13:25 EDT
Received: by interlock.ans.net id AA43175 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Thu, 28 Sep 1995 13:16:25 -0400
Message-Id: <199509281716.AA43175@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Thu, 28 Sep 1995 13:16:25 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Thu, 28 Sep 1995 13:16:25 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Radha Gowda <rxg@proteon.com>
Subject: EBGP over unnumbered serial lines
To: bgp@ans.net
Date: Thu, 28 Sep 1995 13:16:21 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL22]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 823

Here is Yakov's response to my question on whether it makes sense to
support external BGP over unnumbered serial lines.  Yakov suggested
that we bring this issue up in the mailing list.  All comments are 
welcome.

> I think that the "same subnet" restriction is mostly intended to
> make sure that the external neighbors are one hop away from each 
> other (on a common Data Link subnetwork). I think the key question
> you need to answer is what you are going to put in the NEXT_HOP attribute,
> and whether what you'll put in the NEXT_HOP attribute would cause
> any problems to the neighbor (when the neighbor receive a route with
> this attribute).  I suspect (but I am not sure), that there
> may be some problems associated with what you put in the NEXT_HOP
> when you have serial line with unnumbered interfaces.