RE: Re(4): [67ATTENDEES] IETF 67 Network goes down at 12:00

"Tom Alexander" <tom@veriwave.com> Wed, 15 November 2006 03:12 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkBCm-0003Vf-Nj; Tue, 14 Nov 2006 22:12:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkBCl-0003VZ-HA for 67attendees@ietf.org; Tue, 14 Nov 2006 22:12:51 -0500
Received: from mail.veriwave.com ([64.1.198.186] helo=cia.veriwave.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkBCj-0007no-2C for 67attendees@ietf.org; Tue, 14 Nov 2006 22:12:51 -0500
Received: from TomD600 (67.110.80.10.ptr.us.xo.net [67.110.80.10]) (authenticated bits=0) by cia.veriwave.com (8.12.11.20060308/8.12.8) with ESMTP id kAF3BimX014493 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 14 Nov 2006 19:11:49 -0800
Message-Id: <200611150311.kAF3BimX014493@cia.veriwave.com>
From: Tom Alexander <tom@veriwave.com>
To: 'Markus Stenberg' <mstenber@cisco.com>, 'Tim Chown' <tjc@ecs.soton.ac.uk>
Subject: RE: Re(4): [67ATTENDEES] IETF 67 Network goes down at 12:00
Date: Tue, 14 Nov 2006 19:11:55 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccIVMIY0wjTjFoQSlevspNt4m2HKwAC0hjA
In-Reply-To: <874pt11p9c.fsf@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: 67attendees@ietf.org
X-BeenThere: 67attendees@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF 67 Attendess <67attendees.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/67attendees>, <mailto:67attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/67attendees>
List-Post: <mailto:67attendees@ietf.org>
List-Help: <mailto:67attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/67attendees>, <mailto:67attendees-request@ietf.org?subject=subscribe>
Errors-To: 67attendees-bounces@ietf.org

The legal set of 5 GHz channel frequencies assigned for 802.11 WLAN
operations in Japan are completely disjoint from those in the USA. These
frequency assignments are not under the control of the vendor, or even the
IEEE, but are made by the Ministry of Internal Affairs and Communications in
Japan, and the Federal Communications Commission in the USA.

As the 5 GHz band is not assigned to WLANs on a primary basis, but shared
with other country-specific services such as satellite downlinks and
microwave landing systems, it is not surprising that different countries
have different regulations concerning this band. I think vendors are
prohibited from allowing their customers to switch frequency sets at will -
that is, a laptop sold in Japan is only allowed to see the Japanese
frequency set. Otherwise, a consumer device could wind up causing serious
interference to licensed services, even though inadvertent.

Just one of the many interesting wireless pitfalls ...

- Tom A.


-----Original Message-----
From: Markus Stenberg [mailto:mstenber@cisco.com] 
Sent: Tuesday, November 14, 2006 5:18 PM
To: Tim Chown
Cc: 67attendees@ietf.org
Subject: Re: Re(4): [67ATTENDEES] IETF 67 Network goes down at 12:00

Tim Chown <tjc@ecs.soton.ac.uk> writes:
> I have an older Mac and a newer Thinkpad.  The Thinkpad supports a/b/g,
> and while the interface for media selection is rather clunky, it does
> work very well.    
>
> Is there any feeling for what IETF events will support in the future?
> I hope the 11a/b/g support continues, and you don't listen to Jobs :)

I'm hoping the 11a goes away, if it leads to more b/g coverage (unlikely,
considering they're probably provided by the same access points, but I live
in hope).

Why is that? I have a Japanese 11a/b/g both in my Thinkpad and Panasonic
laptops. Unfortunately, it seems that some moron's been in charge when the
frequency sets for 11a were chosen (or I'm a moron), as I can't see the 11a
networks in IETFs at all. I _suspect_ it is our good friend region-coding
that is acting up - apparently both of my laptops subscribe to the ZZJ
(Japan) frequency set according to the Intel driver in Linux, and
unfortunately I can't change that while travelling.

Wireless hardware for fixed operations? sigh..

And as a side note.. 67th IETF was the first one where I maintained network
connectivity throughout the plenaries, good job!

Cheers,

-Markus

_______________________________________________
67ATTENDEES mailing list
67ATTENDEES@ietf.org
https://www1.ietf.org/mailman/listinfo/67attendees


_______________________________________________
67ATTENDEES mailing list
67ATTENDEES@ietf.org
https://www1.ietf.org/mailman/listinfo/67attendees