This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] New on RIPE Labs: New Architecture Model for K-root Local Instances
- Previous message (by thread): [dns-wg] New on RIPE Labs: New Architecture Model for K-root Local Instances
- Next message (by thread): [dns-wg] New on RIPE Labs: New Architecture Model for K-root Local Instances
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Thu Mar 12 03:40:31 CET 2015
hi mirjam, romeo, et alia, this looke cool, and lighter weight. but a few questions as usual. > In the new model, the K-root hosted node will only peer with one > party, the local host, and the local host is responsible for further > propagation of the K-root prefix[1] does this add an as hop, or are you hiding in the host's asn, or using a private (and thus stripped) asn? and can you explain the motivation for radically reducing the bgp out-degree? > 1/ For an old-style local node, the anycast prefix was advertised with > the "no-export" community string set, in order to limit the scope of > the prefix propagation. This is no longer the case in the new design. are you intending the node actually propagate globally, or hoping the one bgp peer adds NO_EXPORT? randy
- Previous message (by thread): [dns-wg] New on RIPE Labs: New Architecture Model for K-root Local Instances
- Next message (by thread): [dns-wg] New on RIPE Labs: New Architecture Model for K-root Local Instances
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]