Thanks, but this is really not the solution. I notice that the placeholder for IETF 95 "Remote Participation" at http://www.ietf.org/ still is not associated with a link. On the meeting page (http://www.ietf.org/meeting/95/index.html), there is no information under "At a Glance", one has to figure out to look further, near the lower right corner of the top part of the page above all the impressive logos, to find a "Remote Participation" entry. There is an "info" link there that points to http://www.ietf.org/meeting/95/remote-participation.html, a page that probably contains all the relevant information or pointers to it if one is sufficiently experienced with the IETF to know how to read and interpret it, but I think it would be quite difficult for a newcomer. It points back to the Meetecho page, as does the Meetecho link from the meeting page, but one needs to know enough about Meetecho to know to go there. Similarly, under that slightly-hard-to-find "Remote Participation" heading, there is an entry for "Remote Participant List" but no hint of the new Remote Participant registration policy, much less a link to that page, which I'd expect to find either next to the "General" Registration entry or prominently featured under "Remote Participation", or, since it seems to be the standard registration page and this is a change from long-standing policy (see below) an indication on the IETF main and meetings pages that remote participants are expected to register. I note that the explanatory material at the top of the registration page (https://www.ietf.org/registration/ietf95/ietfreg.py) doesn't give a hint about no-fee remote participant registrations either -- the only hint is a "Registration Type" checkbox in the registration form itself. While I've been advocating for years that we establish a procedure for registering remote participants, at least those who expect to interact with the meeting rather than lurk on audio, this is a major policy change that I don't recall being discussed with the community to see if there is really consensus for it or at least to be sure that everyone is informed. If that discussion has occurred, could someone point me at it? If it has not, I hope to hear an adequate explanation from the IAOC and/or IESG about the new policy-making process that does not require community review. If we really want remote participants, especially those who are relatively new to the IETF, we really can, and should, do better than this. At least the "information hidden, need to be either an old hand or very persistent to find it" problem has come up many times before. best, john --On Wednesday, March 30, 2016 13:22 -0700 IETF Secretariat <ietf-secretariat@xxxxxxxx> wrote: > You may use Meetecho to participate in or just observe any > session being held in Buenos Aires. Here are the requirements > and details. > > 1. Individuals are required to register for the meeting to > observe or participate via Meetecho. - Individuals are > required to enter registration I.D and name when logging into > a session via Meetecho - The name must match that used to > register for the meeting - Please register even if you are > participating as part of remote hub - There is no cost to > register as a remote attendee. Register > here:http://ietf.org/meeting/register.html. > > 2. Participation includes the ability to transmit audio and > video via the Meetecho virtual queue. - The virtual queue > permits remote attendees to share audio and video if they > choose, see here for more information: > https://ietf95.conf.meetecho.com/index.php/UMPIRE_Project - > Anyone who thinks they may want to participate by transmitting > audio / video should perform the Meetecho self-test prior to > the start of the session: > http://ietf95.conf.meetecho.com/index.php/Self_Test > > 3. WG Chairs will control the virtual queue, unmuting and > muting of remote participants > > 4. The agenda for the WG sessions, as well as more detail on > how to use Meetecho to participate, can be found here: > https://ietf95.conf.meetecho.com/index.php/. > > _______________________________________________ > Recentattendees mailing list > Recentattendees@xxxxxxxx > https://www.ietf.org/mailman/listinfo/recentattendees