nanog mailing list archives
rfc4271 ORIGIN/path of default route, should the value be 0 or 2?
From: Drew Weaver <drew.weaver () thenap com>
Date: Tue, 7 Jul 2020 13:27:55 +0000
Howdy, I am using a multi-vendor network and validating the inter-operability. When I announce a default route to a BGP peer using default-originate applied to the peer group/neighbor configuration: in vendor A that route is sent with ORIGIN 0 (internal) in vendor B that route is sent with ORIGIN 2 (Unknown) Downstream it looks like this: Network Next Hop Metric LocPrf Weight Path * i 0.0.0.0 192.168.27.1 100 0 ? *>i 192.168.25.1 0 100 0 i * i 192.168.27.2 100 0 ? I don't believe that it has a functionality impact but I would like to know which one you think follows the RFC more closely. https://tools.ietf.org/html/rfc4271 thanks, -Drew
Current thread:
- rfc4271 ORIGIN/path of default route, should the value be 0 or 2? Drew Weaver (Jul 07)
- Re: rfc4271 ORIGIN/path of default route, should the value be 0 or 2? Saku Ytti (Jul 07)
- Re: rfc4271 ORIGIN/path of default route, should the value be 0 or 2? Olivier Benghozi (Jul 07)
- RE: rfc4271 ORIGIN/path of default route, should the value be 0 or 2? Drew Weaver (Jul 07)
- Re: rfc4271 ORIGIN/path of default route, should the value be 0 or 2? Olivier Benghozi (Jul 07)
- Re: rfc4271 ORIGIN/path of default route, should the value be 0 or 2? Saku Ytti (Jul 07)