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] suggestions from the list about IPv6 sub-assignment clarification
- Previous message (by thread): [address-policy-wg] suggestions from the list about IPv6 sub-assignment clarification
- Next message (by thread): [address-policy-wg] suggestions from the list about IPv6 sub-assignment clarification
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kai 'wusel' Siering
wusel+ml at uu.org
Thu Jan 17 15:09:49 CET 2019
Am 17. Januar 2019 14:21:38 MEZ schrieb JORDI PALET MARTINEZ via address-policy-wg <address-policy-wg at ripe.net>: >I think this must be allowed, even if static/persistent, because I may need a service company coming to my network with their own devices, for example, installing IP video-cameras for surveillance. It doesn't make sense that they can't use my addresses, because that increase the complexity of the infrastructure, etc., even may force to have different networks. Nicely constructed, but ... usually you will not have them come to your site, let them install their gear out of blue sky, and just leave. You'll have some kind of contractual relationship in place to have them do something for you, making the devices part of your network for the time being, so assigning them PIv6 addresses is ok (they are part of End User's infrastructure at that time — if you are the receiving End User of the PIv6 in question). Regards, -kai
- Previous message (by thread): [address-policy-wg] suggestions from the list about IPv6 sub-assignment clarification
- Next message (by thread): [address-policy-wg] suggestions from the list about IPv6 sub-assignment clarification
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]