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] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
- Previous message (by thread): [address-policy-wg] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
- Next message (by thread): [address-policy-wg] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
poty at iiat.ru
poty at iiat.ru
Mon Jun 1 14:24:52 CEST 2009
> -----Original Message----- > From: address-policy-wg-admin at ripe.net [mailto:address-policy-wg- > admin at ripe.net] On Behalf Of michael.dillon at bt.com > Sent: Monday, June 01, 2009 3:30 PM > To: address-policy-wg at ripe.net > Subject: RE: [address-policy-wg] RE: Private address space in IPv4 and > IPv6 [was something irrelevantly titled] ... > People who make addressing policy, don't often think about ACLs > and firewall rules, but they are at least as important as > routing. If the Radianz network operates with globally unique > IP addresses, then the subscribers can be confident that any > ACLs blocking Radianz traffic from the Internet will never cause > a problem for real Internet traffic. Globally unique addresses > are required to have reliable ACLs in enterprise LANs. Administrative requirements never was an argument in the allocation/assignments. > Note that these types of traffic controls (ACLs) can be used > in other scenarios. Network X could announce their addresses > to some neighbour ASes in country A, and those ASes might > not announce the routes to international peers. They might > also implement ACLs so that no traffic can flow to > international peers. Network X would still be on the Internet > and their customers in country A would be happy that they > can browse all kinds of sites on the Internet in country A. > They could even send email internationally because it would > be relayed by the ASes with international peering agreements. > > Is Network X on the Internet? Is the Radianz network on the > Internet? There is a simple answer. If your address block is interacting with at least one announced prefix, then you should have globally unique addresses, otherwise - not. > > Addressing policy would be just as complex as today if RIPE > agreed that the scope for RIPE-NCC allocations should be > restricted to "the Internet". There is no point in making > such a change, and people who are ignorant of history need > to take the time and learn about the history of the Internet, > of IANA and of RIPE. Don't point to the history, because there was many changes in history. But POLICY of the RIPE NCC mean the scope - the Internet. Otherwise RIPE NCC should police any private IP-network in the world, even if the network doesn't want to be policed in any way, because does not leave several square meters of an office. Misha, derzi jazyk za zubami, i ne perehodi na lichnosti.
- Previous message (by thread): [address-policy-wg] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
- Next message (by thread): [address-policy-wg] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]