Hi Brian, I was not referring only to IPv6 (which is bad not have it working in any case), but also to IPv4. It was not working for me in most of the meeting rooms, most of the time (today seems to be fine) and talking to many people, they had the same issue. I think is terrible that the quality of the network, instead of being improved with every meeting, seems to be going worst and worst, and this probably requires some serious measures, in my opinion. Regards, Jordi > De: Brian E Carpenter <brc@xxxxxxxxxxxxxx> > Organización: IBM > Responder a: <ietf-bounces@xxxxxxxx> > Fecha: Fri, 11 Mar 2005 16:31:39 +0100 > Para: "ietf@xxxxxxxx" <ietf@xxxxxxxx> > Asunto: Re: IETF62 Network and Terminal Room Information > > Jordi, I thought that Jim Martin's message under subject > "IETF62 Wireless Network Update" had already explained > what was happening (and IPv6 was a victim of those > circumstances). Of course this was very annoying and nobody > wants to see it happen again. > > In my experience the IPv4 network was working *most* of the time > after Monday, but there were roaming glitches. And if you > unintentionally associated with the hotel network, life became > more complicated. > > Brian > > > JORDI PALET MARTINEZ wrote: >> Hi, >> >> I will like to ask the responsible/s of setting up the IETF network to make >> sure that we don't have again, a situation like we had this week, when the >> network was not working most of the time, and no IPv6 available. > > <snip> > > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf