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/ipv6-wg@ripe.net/
[ipv6-wg] Hijacking unused address space for a private infrastructure - any legal consequences?
- Previous message (by thread): [ipv6-wg] Hijacking unused address space for a private infrastructure - any legal consequences?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Thu Feb 24 16:09:49 CET 2022
Hi Eduard, I think we need to first understand that addresses aren't a property. If you get allocated or assigned resources by a RIR, they do not belong to you, you just have a yearly license to use them, and (typically) while the need is justified. Similarly, they aren't an IANA property, it is just the central registry that allocates the to the 5 RIRs. By the way, obtaining any prefix length, from any RIR, if justified is not difficult. And that justification for IPv6 is not usually a problem. If there are cases where the actual policy doesn't work, in any RIR (most of them have basically the same text), we should work in improving the policy. I'm not really sure legally something can be done ... Saludos, Jordi @jordipalet El 24/2/22 15:01, "ipv6-wg en nombre de Vasilenko Eduard via ipv6-wg" <ipv6-wg-bounces at ripe.net en nombre de ipv6-wg at ripe.net> escribió: Hi all, Could somebody speak on the legal consequences of hijacking unused address space? Imagine the situation that some vendor would push many Carriers to use FC/8 by cutting a rather big block out of it (/28 for each Carrier). This address space should have a registry. It is an IANA property till then. But: 1. Nobody is using it - nobody would be hurt. 2. This prefix would be excluded from the Internet (by routing and filtering) 3. FC/8 is assumed to be used for the closed domain (the purpose of usage is very similar). Just nobody decided how exactly. Maybe /28 is not how IANA and IETF would want to split it in the future. People could ask "why not GUA"? The answer is: it is difficult to get yet another /28 GUA from RIR just for the infrastructure. /28 goal has the technical roots by itself. It is the sort of technical solution. Could such LIR/Carrier have any pressure from any RIR or IANA itself? Is any restriction in the LIR agreement? Any legal consequences? (that would push for renumbering). Of course, I am aware what may happen if Carrier would need to connect infrastructure with different Carrier or Cloud Provider Without proper random prefix generation and registry to guarantee uniqueness. The technical side is very clear for me. I am just very ignorant on the legal side. Disclaimer: This question is not related to Huawei, not at all. Eduard -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
- Previous message (by thread): [ipv6-wg] Hijacking unused address space for a private infrastructure - any legal consequences?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]