--On Thursday, March 31, 2016 11:23 -0700 Dave Crocker <dhc@xxxxxxxxxxxx> wrote: > On 3/31/2016 11:15 AM, John C Klensin wrote: >> I notice that the placeholder for IETF 95 "Remote >> Participation" athttp://www.ietf.org/ still is not >> associated with a link. On the meeting page >> (http://www.ietf.org/meeting/95/index.html), > ... > > > Yes, there are some hiccups in some of the pages. > > However I latched onto the directive that remote participants > need to register and, after searching and finding the problems > you cited, decided to try to register. There I found that I > could choose 'remote participation' as a class of registration > and everything else was normal, except that it didn't charge > me. Yes, I found that too (and mentioned it in my note). My concern (independent of concerns about how the decisions were made) is that you and I are about as experienced IETF old hands (complete with appropriately-colored beards) as members of any group of people around here. A newcomer who can be easily discouraged (rather than one who is exceptionally persistent and determined) might well just give up instead. I presume (and hope) that is not the behavior we want to encourage. It really wouldn't take much effort to put a few sentences on the meeting page (and either on the IETF home page or at the top of the registration one) to say something like 'The IETF is now requiring that remote participants register for the meeting using the normal registration process but checking the new "Remote Participant" category. Doing so will give such participants access to various capabilities including the Meetecho remote conferencing system.'. I'm just having trouble understanding why it apparently didn't occur to anyone to do that whether you and I can figure out how to navigate the system or not. john