Yes, if required, maybe I can try to help, but my guess is still the problem
is not in the deployment, but in the equipment used.

Regards,
Jordi




> De: Joel Jaeggli <[EMAIL PROTECTED]>
> Responder a: <[EMAIL PROTECTED]>
> Fecha: Fri, 11 Mar 2005 08:25:10 -0800 (PST)
> Para: JORDI PALET MARTINEZ <[EMAIL PROTECTED]>
> CC: "ietf@ietf.org" <ietf@ietf.org>
> Asunto: Re:IETF62 Network and Terminal Room Information
> 
> On Fri, 11 Mar 2005, JORDI PALET MARTINEZ wrote:
> 
>> 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.
> 
> So we can expect to see your working in the noc in Paris?
> 
>> Regards,
>> Jordi
>> 
>> 
>> 
>> 
>>> De: Brian E Carpenter <[EMAIL PROTECTED]>
>>> Organización: IBM
>>> Responder a: <[EMAIL PROTECTED]>
>>> Fecha: Fri, 11 Mar 2005 16:31:39 +0100
>>> Para: "ietf@ietf.org" <ietf@ietf.org>
>>> 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@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/ietf
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>> 
> 
> -- 
> --------------------------------------------------------------------------
> Joel Jaeggli          Unix Consulting         [EMAIL PROTECTED]
> GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Reply via email to