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/address-policy-wg@ripe.net/
[address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Geoff Huston
gih at apnic.net
Wed May 10 00:30:53 CEST 2006
At 05:28 AM 11/05/2006, Nick Hilliard wrote: >David Conrad wrote: >>How do you believe folks will do traffic engineering? > >This is an interesting point which occurred to me as I was writing my last >email. Outside as-path prepending, I don't have a good answer. And of course there are more specifics to play with as well, as well as AS sets and AS Path poisioning, as well as BGP communities of course. Playing with the routing system to attempt to achieve local optimizations at the expense of the global system is a well understood conventional path here. Geoff
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]