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] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Previous message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Next message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Tue Apr 21 16:54:50 CEST 2009
* Peter Koch: > During recent discussion within the IETF, but also on other occasions > in the past, it appeared that a single /24 is often not enough to > support instructive examples. This may include more complex network > designs, or the use of addresses for DNS name servers, where good > practice (see RFC 2182, BCP 16) suggests topological diversity. Uhm? Thanks to CIDR and IGPs supporting VLSMs, it's possible to have topological diversity within a /24. -- 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] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Next message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]