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] 2008-05 New Draft Documents Published (Anycasting Assignments for TLDs and Tier 0/1 ENUM)
- Previous message (by thread): [address-policy-wg] 2008-05 New Draft Documents Published (Anycasting Assignments for TLDs and Tier 0/1 ENUM)
- Next message (by thread): [address-policy-wg] 2008-05 New Draft Documents Published (Anycasting Assignments for TLDs and Tier 0/1 ENUM)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Wed Apr 22 11:38:11 CEST 2009
* B. C.: >> This proposal does not allow for a local/global node split. Is >> this a problem? > > I don't think it is a problem I don't believe the policy should > refer to any type/implementation of Anycast. If you assign a /24 instead of a /23, you rule out certain implementations. You can't reliably run cross-AS local nodes with a single /24 because a preferred, non-exported prefix typically suppresses announcements of the prefix---even if a non-preferred prefix exists which could be announced. -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- Previous message (by thread): [address-policy-wg] 2008-05 New Draft Documents Published (Anycasting Assignments for TLDs and Tier 0/1 ENUM)
- Next message (by thread): [address-policy-wg] 2008-05 New Draft Documents Published (Anycasting Assignments for TLDs and Tier 0/1 ENUM)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]