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/[email protected]/
[address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Previous message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Next message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Baeza (Red y Sistemas TVT)
d.baeza at tvt-datos.es
Wed Oct 15 11:22:55 CEST 2014
Hi Steffan, El 13/10/2014 21:07, Sander Steffann escribió: > For example if running a closed network that interconnects with other organisations but not with the whole internet. For example a closed network between banks or municipalities that needs guaranteed globally unique addresses to avoid clashes with the networks of the connected organisations. The network itself is not connected to the internet but systems at the participating organisations probably are. Therefore you need globally unique addresses. Another example might be a car manufacturer that wants addresses for the internal networks of the cars they manufacture. You probably don't want your cars systems to be connected to the global internet. Having connectivity to some other systems (monitoring, fleet management etc) might be useful though. And those systems are connected to the internet so the cars need globally unique addresses that don't overlap with anything used on the internet or within the companies that run the remote systems. > > And these are just some things that I can think of now. There certainly will be others. We have a registry to make sure we hand out unique addresses to organisations so no clashes occur and so we know who is responsible for which addresses. Not to limit the kinds of networks and the way those networks are connected to each other. There isnt any other way of doing it? I mean: - Public and unique IP Space works for both, private and public networks. - Private and NOT unique Space only works for private networks. Since public and unique IP Space is the only one you can use for "whole internet" and we (not we as me, we as all LIRs/RIRs) are running out of v4 space. There is a little conflict as private networks can work with private space, but public ones cant. Do you know what I mean? Cheers, -- Daniel Baeza
- Previous message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Next message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]