[address-policy-wg] IPv6 assignment for the RIPE meetingnetwork

Perhaps an even better, even more IPv6'ish solution would be something like
Network Mobility (NEMO)?

And, not to cross threads (reference BEHAVE WG) or start fires, but another
option would be to use ULA addresses internally and translate (NAT66) them
to PA space onsite as needed ...


(Not saying either option is ideal / great ... but if the others options are
to be treated as super-special or to do lots of extra work, the alternatives
above sound more palatable)


/TJ ... just an uninvolved observer :)

>-----Original Message-----
>From: address-policy-wg-admin at ripe.net [mailto:address-policy-wg-
>admin at ripe.net] On Behalf Of Elisa Jasinska
>Sent: Tuesday, December 02, 2008 11:18 AM
>To: address-policy-wg at ripe.net
>Subject: Re: [address-policy-wg] IPv6 assignment for the RIPE
meetingnetwork
>
>I can only second Niels here. While organizing conferences and events
>with network infrastructure myself, I can tell that it is a hassle to
>re-arrange temporary PI every time... so I do see the incentive. But why
>should the NCC be a special case and no one else?
>
>Cheers, Elisa
>
>--
>Elisa Jasinska - AMS-IX NOC
>http://www.ams-ix.net/