[ipv6-wg at ripe.net] IPv6 Webcast

Hi Jeroen et all,

 "Jeroen Massar" <jeroen at unfix.org> writes:
 * -----BEGIN PGP SIGNED MESSAGE-----

<snip>
 * 
 * BTW I wonder if the RIPE webmaster could either: directly store
 * a ripe meetings url as:
 * http://www.ripe.net/ripe/meetings/ripe-46/webcast.html
 * or directly as:
 * http://www.ripe.net/ripe/meetings/archive/ripe-46/webcast.html
 * 
 * BTW I wonder what the idea is of moving it to archive after next
 * week or somewhere as it is pretty clear that the current one
 * is the last one etc. also a simple redirect under eg 
 * /ripe/meetings/current/ and /ripe/meetings/previous/ could
 * help out there saving us from retyping this message then as
 * all of the 'current' url's get invalidated in the mailarchives.
 * Which is something quite unfortunate. Note that there is a w3c
 * tip about this on their site.

We used the "archive" and "current" in the URL up to and including
ripe-44 (this was legacy, I don't really know the reason). However
this URI scheme created really long URL's, for example presentations,
and was breaking bookmarks and referral links when everything was
moved from 'current' to 'archive' (like you said).

Since ripe-45 we stick with the
http://www.ripe.net/ripe/meetings/ripe-$<number> URI scheme.

Pre-ripe-45 meetings are still available under the 'archive' section.
Redirects have been set up for a number of meetings, which link
current/index.html to archive/index.html.

Kind Regards,

Jeroen Bet
RIPE NCC Webmaster

 * 
 * Greets,
 *  Jeroen
 * 
 * -----BEGIN PGP SIGNATURE-----
 * Version: Unfix PGP for Outlook Alpha 13 Int.
 * Comment: Jeroen Massar / jeroen at unfix.org / http://unfix.org/~jeroen/
 * 
 * iQA/AwUBP1Z9xymqKFIzPnwjEQJ+EACgiJNM8OkqKEYMx9iwXIh8rTN027EAoL07
 * RUSuZ2RDreBuvZBpF7YkJyd9
 * =pB4y
 * -----END PGP SIGNATURE-----
 *