RIPE 51 Remote Feedback

During RIPE 51, the RIPE NCC will be collecting feedback from participants watching the webcast who are unable to attend the RIPE Meeting. The mediums used for this are irc and jabber.

Please note that feedback submitted through IRC/Jabber will be archived and made available on the RIPE 51 section of www.ripe.net.

IRC (Internet Relay Chat) is an implementation of RFC1459 / RFC2812 . To connect to the RIPE Meeting IRC network, please point your client at one of the servers listed below as appropriate. You may choose any nickname, as long as it does not conflict with an existing or reserved nickname.

• irc.ripemtg.ripe.net - For RIPE Meeting Attendees only.
• irc.ripe.net - For people not physically attending the RIPE Meeting.

To join a specific channel, the usual command is '/join #channel-name' . (See below for the channel name for each of the sessions.)

Any IRC client may be used with this service. The NCC knows that the following clients will work:

• ircii - Unix
• mirc - Windows
• xchat - Unix
• gaim - Unix/Windows

Jabber is a set of streaming XML protocols and technologies that is being worked on by the Jabber Software Foundation and the IETF XMPP group.

There is one server for all users, being:

• jabber.ripe.net

You will need to register your preferred handle in the form 'yourname@jabber.ripe.net'.

To join a specific room, you will need to 'Join Group Chat' (or something equivalent) with:

• Group/Room: room name
• Server: conference.ripe.net

(See below for the room name for each of the sessions).

IMPORTANT: The RIPE Jabber server is not SSL-enabled. If you are using SSL for your current Jabber account, you may not be able to connect to the group chat rooms. Either disable SSL in your client (not recommended due to password exposure issues), or create an account as mentioned above.

Various clients exist (not all have been tested), such as:

• Exodus - Windows
• Gaim - Windows/Unix
• Psi - Windows/Unix/Mac
• Trillian - Windows
• Gabber - Unix
• Tkabber - Unix
• Nitro - Mac

Room / Channel Name for Sessions

Irrespective of which interface you use, each named 'room' or 'channel' listed below will be connected with its matching equivalent on the other interface. The names reflect the shortened form of the Working Group session:

• anti-spam
• ap - Address Policy WG
• db - Database WG
• dns - DNS WG
• eix - European Internet eXchanges WG
• eof - European Operators Forum
• enum - ENUM WG
• ipv6 - IPv6 WG
• routing - Routing WG
• plenary - Plenary
• services - RIPE NCC Services WG
• tt - Test Traffic WG

All of the above rooms/channels will be recorded by the RIPE NCC. There is also a virtual 'hallway' room:

• hallway

Questions

Please e-mail: <ops@ripe.net> . To give any assistance, we will need the following details:

• OS
• Client
• IP address at the time
• Possibly a traceroute to the appropriate server