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]/
[ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Previous message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Next message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Riccardo Losselli
riccardo at e4a.it
Tue Feb 2 18:34:28 CET 2010
Hi, i must say i second Gert and Jan their position against the use of NAT, for pretty much the same stated reasons. Apart from all the tecnical details of what will work/not work/possible not work, and any personal position about the good and the bad of NATting, please note that enabling NAT on the meeting network would be against the currently running laws of at least one of the country hosting one of the next RIPE meetings: Italy (for any of you interested on it it's art. 6, comma 5, d.lgs 109/2008) Which, roughly translated, states that starting from march 21 2009 "any access provider, providing public connectivity (which means connecting people to the Internet), must ensure effective avalability and unicity of ip addresses assigned to the end user. Which means that if you want to comply to the law you MUST assign a public ip address to any user you connect (and by the way if you give internet access on public locations you should also be able to track down the identity of each single user that has connected, including a copy of an ID document or some other allowed certain identification methods). No need to comment on that law, no one here in Italy really likes it at all, but that's it, up to now, and at least until next december 31st we do have to live with it. I think the chances of network abuses during a RIPE meeting are quite low, but i really would avoid seeing a RIPE meeting pushing, even if indirectly and unwanted, some unlawful behaviour. Thanks, Ricky
- Previous message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Next message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]