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] Proposal for change to the IPv4 PI allocation policy
- Previous message (by thread): [address-policy-wg] Proposal for change to the IPv4 PI allocation policy
- Next message (by thread): [address-policy-wg] Proposal for change to the IPv4 PI allocation policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed Aug 23 16:28:19 CEST 2006
Hi,
On Wed, Aug 23, 2006 at 06:16:49PM +0000, Max Tulyev wrote:
> > PI *is* worse to debug if some targets can't be reached (if only because
> > you normally can't run traceroutes from inside customer PI networks).
>
> But what exactly (versus PA) is worse? Same ping and traceroute, same
> bgp debug, so on.
With PA, you can debug from *your* network - with customer's PI, you
can't (normally) run probes (traceroute, ping) from *their* IP addresses
- and if your PA works, but their PI is filtered, this makes it harder
to debug.
Furthermore, /24s tend to be damped more quickly and for longer times
than /16...
Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 94488
SpaceNet AG Mail: netmaster at Space.Net
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
D- 80807 Muenchen Fax : +49-89-32356-234
- Previous message (by thread): [address-policy-wg] Proposal for change to the IPv4 PI allocation policy
- Next message (by thread): [address-policy-wg] Proposal for change to the IPv4 PI allocation policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]