[routing-wg] May a tier1 transit change bgp origin attribute?
- Previous message (by thread): [routing-wg] [db-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
- Next message (by thread): [routing-wg] May a tier1 transit change bgp origin attribute?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Harald Michl
harald.michl at univie.ac.at
Fri Dec 13 20:31:39 CET 2013
Dear WG, We (ACOnet, the Austrian NREN, AS1853) do have several upstreams. More or less per random we detected that one of them delivers prefixes with a different route origin parameter (IGP instead of incomplete) than others. This obviously has a big influence in the BGP best-path selection. After asking why this is the case we learned from them: On 28.11.13 10:32, support at xxx.com wrote:> > Hi Harald, > > The XXX standard route map sets origin IGP as standard across all > customer learned routes... Now we are currently debating with them whether this is ok or not. We are arguing that the origin is an attribute that _only_ the originating AS can set and that transit providers _must not_ change that. Especially on (not even cheap) paid upstream connections from a tier1. Now we would be interested what the routing-community thinks about that. Are we picky or do they breaching best current practices? Has anyone else (had) the same issues? Any feedback is appreciated. Cheers, Harald -- Harald Michl <harald.michl at univie.ac.at> Vienna University - ACOnet www.ACO.net - VIX www.VIX.at Universitaetsstrasse 7, A-1010 Vienna, Austria, Europe Tel: +43 1 4277 - 14078 (Fax: - 814078) HM3550-RIPE
- Previous message (by thread): [routing-wg] [db-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
- Next message (by thread): [routing-wg] May a tier1 transit change bgp origin attribute?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]