[141660] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: IPv6 routing protocols

daemon@ATHENA.MIT.EDU (Iljitsch van Beijnum)
Fri Jun 10 06:28:16 2011

From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4DF1F006.3010501@foobar.org>
Date: Fri, 10 Jun 2011 12:27:24 +0200
To: Nick Hilliard <nick@foobar.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On 10 jun 2011, at 12:20, Nick Hilliard wrote:

[nothing to support his earlier claim]

>> And it still carries link local next hop
>> addresses.

> it's a bit more subtle than that - it depends on how the underlying =
router operating system handles next-hop resolution and how you =
configure your BGP.

It doesn't depend.

RFC 4760:

   An UPDATE message that carries the MP_REACH_NLRI MUST also carry the
   ORIGIN and the AS_PATH attributes (both in EBGP and in IBGP
   exchanges).  Moreover, in IBGP exchanges such a message MUST also
   carry the LOCAL_PREF attribute.=


home help back first fref pref prev next nref lref last post