-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2004-11-08, at 14.28, Bill Manning wrote:
That's inconsistent with the published policy.
No. See above.
When there is an inconsistency, you can't fix it by adding more data.
You need to remove/change something. The fact that the information
necessary to do route filtering is present in 5 locations and
policies are created in 4 places doesn't help.
it is important to remember that neither the IETF nor the RIR can
manage/conserve the entries in anyones routing/forwarding tables.
The IETF (imho) should confine itself to protocol work, The RIRs
should confine themselves to being wise stewards of the addressing
resources, and the ISPs need to worry about the operational
coordination of routing... such is not the perview of either the
IETF, the IANA task,
or the RIRs. ....
Well, the RIRs will actually hand out address-space explicitly saying
they make no guarantees for routability. If you apply for IPv4 PI space
and can only justify the equivalence of a /26 you will get a /26.
- - kurtis -
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1
iQA/AwUBQY+7pKarNKXTPFCVEQJR0wCgyMC5UjkqSGsXcH+zkedq5LKhrEcAn2PE
Y0VTL6bNO9myWgKDKy4vExuK
=PhUx
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf