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] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
- Previous message (by thread): [address-policy-wg] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
- Next message (by thread): [address-policy-wg] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Max Tulyev
president at ukraine.su
Tue Nov 25 23:07:30 CET 2008
Nick Hilliard wrote: > - while a requirement for multihoming is useful, it should be made clear > during implementation that this is not necessarily a requirement for > multihoming using ASNs and BGP on the public Internet (however we care to > define that term). Private interconnection to third parties is also a > fully legitimate justification for assignment of provider independent > number resources. I also saw a lot of cases when PI announced via upstream's ASN, not via user's one. I think, it is OK and it is not against multihoming, as this ASN is multihomed of course. -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- Previous message (by thread): [address-policy-wg] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
- Next message (by thread): [address-policy-wg] Revised 2006-01 set back to Discussion Phase (Provider Independent (PI) IPv6 Assignments for End User Organisations)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]