At 07:43 AM 7/14/2002 +0859, Masataka Ohta wrote:
>it is a problem of a plain old telephone system so called 3G.
the point is well taken, and is what we decided on the train as well.
even if WorldCom enters chapter 11, I am confident that UUNET and the MAE Systems will
continue to operate
normally.
vint
At 01:45 AM 7/14/2002 +0100, Rob Evans wrote:
>This is decidedly off-topic for this list, but the current Worldcom
>transit is both backed up by another provider and only te
Directions:
Exit Pacifico on Level 2, same level as the lobby of the Intercontinental
hotel. Turn LEFT, go across the bridge and enter the Queens Shopping Mall.
Look to your RIGHT just as you enter the mall. You will see a large
picture of the concert hall (with the organ) on the wall. Go downs
-BEGIN PGP SIGNED MESSAGE-
For the fourth time in 7 years, I've been unable to attend an IETF in
person. For many years now I've been trying to establish a tunnel with anyone.
I have plenty of IPv4, IPv6, IPsec and my team has regular conference calls
using unicast'ed H.323 over IPs
On Sun, 14 Jul 2002, Ole J. Jacobsen wrote:
> ...
> Program etc at www.organdemo.info.
Just for some IETF relevance, it is perhaps worthy of note that (at least
for my browser), the page displayed for
http://www.organdemo.info./
is entirely different from the page displayed for
http://ww
The IETF 54 broadcast information and the archive of broadcast sessions
(none yet) is up now at the following location:
http://videolab.uoregon.edu/events/ietf/ietf54.html
the broadcast schedule is at:
http://www.ietf.org/meetings/multicast_54.html
thanks
joelja
--
There will be a PGP Key Signing meeting at the 54th IETF in Yokohama.
The key signing will be held Wednesday evening immediately after the
plenary in Room 411/412.
If you wish to have your key signed, please SEND IT AHEAD OF TIME to
[EMAIL PROTECTED] PLEASE PUT THE STRING "PGPKEY" in the subject
Oops, I should know better than trying to put punctuation in URLs.
Sorry, it is: http://www.organdemo.info
The "Click here" etc.
Ole
Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office of the CTO, Cisco Systems
Tel: +1 408-527-8972
GSM: +1 415-370-4628
E-mail: [EMAIL P
Hi folks:
Having looked at the schedule, let's hold Dead Companies day on Thursday.
Thanks
Craig
E-mail: [EMAIL PROTECTED] or [EMAIL PROTECTED]
Can anyone point me towards a reference of
Dave Clark [allegedly] saying "don't do
anything in a protocol that you wouldn't
do to Mars"?
(Never mind that TCP isn't likely to actually
be used to Mars...)
Thanks,
-tjs
joe touch and crew, please turn it off
Jul 15 13:01:45 roam /kernel: arp: unknown hardware address format (0x0800)
Randy Bush wrote:
> joe touch and crew, please turn it off
>
> Jul 15 13:01:45 roam /kernel: arp: unknown hardware address format (0x0800)
As I said at 10:30, and will repeat, this is the result of an arp cache
that hasn't been flushed. An arp cache that we don't control, most
likely on a ro
>> joe touch and crew, please turn it off
>> Jul 15 13:01:45 roam /kernel: arp: unknown hardware address format (0x0800)
> As I said at 10:30, and will repeat, this is the result of an arp cache
> that hasn't been flushed. An arp cache that we don't control, most
> likely on a router that has de
Randy Bush wrote:
>>>joe touch and crew, please turn it off
>>>Jul 15 13:01:45 roam /kernel: arp: unknown hardware address format (0x0800)
>>
>>As I said at 10:30, and will repeat, this is the result of an arp cache
>>that hasn't been flushed. An arp cache that we don't control, most
>>likely
> We did (at 9:30am, minutes after the problem was detected). It didn't go
> away. Now be an engineer and show us a trace.
a bit hard when it is broken arp packets
Jul 15 11:47:27 roam /kernel: arp: unknown hardware address format (0x0800)
Jul 15 11:47:27 roam /kernel: arp: unknown hardware add
Randy Bush wrote:
>>We did (at 9:30am, minutes after the problem was detected). It didn't go
>>away. Now be an engineer and show us a trace.
>
> a bit hard when it is broken arp packets
>
> Jul 15 11:47:27 roam /kernel: arp: unknown hardware address format (0x0800)
> Jul 15 11:47:27 roam /ker
Somebody is running a number of ad-hoc nodes (or one chameleon-style node) in
the 802.11b airspace of the IETF meeting. This is bad enough as it is not
coordinated with the site's frequency plan. It is even worse when at least one
of the nodes uses the SSID "IETF", which causes all Macs (and
17 matches
Mail list logo
