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]/
[address-policy-wg] Policy proposal: #gamma IPv6 InitialAllocation Criteria
- Previous message (by thread): [address-policy-wg] Policy proposal: #gamma IPv6 InitialAllocation Criteria
- Next message (by thread): [address-policy-wg] Policy proposal: #gamma IPv6 InitialAllocation Criteria
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Sun Apr 24 14:27:58 CEST 2005
On 24-apr-2005, at 13:34, Daniel Roesen wrote: > The filtering out there IS a problem. Yes, but it's getting better. > in general your AS_PATHs > for the more-specifics can get VERY long. So borderline is that you > have > worse to MUCH worse connectivity by announcing the more-specific than > via the aggregate, thanks to the filtering done out there. There are still people out there who announce everything to everyone over tunnels. It was much worse in the past but it's important that not only the people who do this are encouraged to stop, but also that the people who are feeding them cut their BGP feeds off if they don't. This is all BGP 101 so there is absolutely no reason for this to persist, people just have to flip the "test/production" switch on their IPv6 stuff in the "production" direction and take away peering privileges from well-meaning but clue-challenged amateurs.
- Previous message (by thread): [address-policy-wg] Policy proposal: #gamma IPv6 InitialAllocation Criteria
- Next message (by thread): [address-policy-wg] Policy proposal: #gamma IPv6 InitialAllocation Criteria
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]