[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IPv6 routing protocols

Subject: IPv6 routing protocols
From: iljitsch at muada.com (Iljitsch van Beijnum)
Date: Fri, 10 Jun 2011 12:27:24 +0200
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <BANLkTi=6BzU+N+9Br4WjvxVmJBKbRw_rTbpD4DNr=52POaMAKQ@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]>

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.

Follow-Ups:
- IPv6 routing protocols
  - From: iljitsch at muada.com (Iljitsch van Beijnum)

References:
- Cogent IPv6
  - From: bill at herrin.us (William Herrin)
- Cogent IPv6
  - From: owen at delong.com (Owen DeLong)
- Cogent IPv6
  - From: cra at WPI.EDU (Chuck Anderson)
- Cogent IPv6
  - From: sthaug at nethelp.no (sthaug at nethelp.no)
- Cogent IPv6
  - From: iljitsch at muada.com (Iljitsch van Beijnum)
- Cogent IPv6
  - From: nick at foobar.org (Nick Hilliard)
- Cogent IPv6
  - From: rps at maine.edu (Ray Soucy)
- Cogent IPv6
  - From: nick at foobar.org (Nick Hilliard)
- IPv6 routing protocols
  - From: iljitsch at muada.com (Iljitsch van Beijnum)
- IPv6 routing protocols
  - From: nick at foobar.org (Nick Hilliard)

Prev by Date: IPv6 routing protocols
Next by Date: IPv6 routing protocols
Previous by thread: IPv6 routing protocols
Next by thread: IPv6 routing protocols
Index(es):
- Date
- Thread