an Kohn [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 26, 2000 7:37 PM
To: Taylor, Johnny; Donald E. Eastlake 3rd; [EMAIL PROTECTED]
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
I certainly hope you're joking.
If not, I can say definitively that this is certainly not Teledesic
Eastlake 3rd; [EMAIL PROTECTED]
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
All,
I have seen a lot of different people bash WAP over the past two days.
However, I
am a firm believer that WAP will become what IP is to us today. When you
relate the
technologies of today and th
nning [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 10, 2893 4:44 PM
To: Steve Deering
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
%
% At 4:16 PM -0400 6/21/00, Brijesh Kumar
--
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Mark Atwood
Sent: Wednesday, June 21, 2000 5:09 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; 'Taylor, Johnny'; 'Donald E. Eastlake 3rd';
[EMAIL PROTECTED]
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Re
Probably, there is some universe out there made of AnTi-Matter and where
anti-packets are mostly routed using anti-IP, or in other words...ATM.
:)
On Thu, 22 Jun 2000, Brijesh Kumar wrote:
>
> Chuck writes,
>
> > It's my understanding that disturbances in The Force
> > were actually routed
> > Bill Manning wrote:
> >
> > > And the draft on IP over seismic waves is due any day now.
> >
> > Security Considerations: since the most effective way to generate seismic
> > waves is with a nuclear device, users of this protocol can expect to be
> > secured by their governments for
nice call
--john
> -Original Message-
> From: Brijesh Kumar [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 22, 2000 3:18 PM
> To: 'Chuck Kaekel'; [EMAIL PROTECTED]
> Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
>
>
>
> Chuck
Chuck writes,
> It's my understanding that disturbances in The Force
> were actually routed using an ancient precursor to IP.
>
I don't know about it, but the myth goes that ET communicated with his
folks using IP :-). The captured packet trace is
"UndecodableDatalink:IPheader:TCPheader:"ET go
It's my understanding that disturbances in The Force
were actually routed using an ancient precursor to IP.
C_
At 09:57 AM 6/22/00 -0500, Matt Crawford wrote:
>> Did the IESG depricate IP over Avian Carrier when I blinked?
>> And the draft on IP over seismic waves is due any day n
> I have seen a lot of different people bash WAP over the past two days.
> However, I am a firm believer that WAP will become what IP is to us today.
How nice to have firm belief-systems. What I write here are only my personal
opinions.
I posted Rohit's tour of the tangle when I was at Nokia Res
>Consider the possibilities of a neutrino beam -- no media costs and
>lower latency than direct point-to-point fiber.
I think IP over Human Alpha Waves (IP-HAW) might be promising, too.
RGF
Robert G. Ferrell
Who goeth without humor goeth unarmed.
==
> Did the IESG depricate IP over Avian Carrier when I blinked?
> And the draft on IP over seismic waves is due any day now.
Consider the possibilities of a neutrino beam -- no media costs and
lower latency than direct point-to-point fiber.
http://www-numi.fnal.gov:8875/overview/overv
From: John Stracke <[EMAIL PROTECTED]>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Thu, 22 Jun 2000 09:03:12 -0400
> Bill Manning wrote:
>
> > And the draft on IP over seismic waves is due any day now.
>
> Security Considerations: sinc
Bill Manning wrote:
> And the draft on IP over seismic waves is due any day now.
Security Considerations: since the most effective way to generate seismic
waves is with a nuclear device, users of this protocol can expect to be
secured by their governments for a very long time.
--
/=
From: Patrik Fältström <[EMAIL PROTECTED]>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Thu, 22 Jun 2000 14:02:56 +0200
> At 13.37 +0200 00-06-22, Magnus Danielson wrote:
> > > 1926 An Experimental Encapsulation of IP Datagrams on Top of ATM. J.
&g
At 13.37 +0200 00-06-22, Magnus Danielson wrote:
> > 1926 An Experimental Encapsulation of IP Datagrams on Top of ATM. J.
>>Eriksson. April 1996. (Format: TXT=2969 bytes) (Status:
>>INFORMATIONAL)
>
>I still havent found a working implementation of this. Any references?
>Did the c
At 18.23 -0700 00-06-21, Bill Manning wrote:
> Did the IESG depricate IP over Avian Carrier when I blinked?
> And the draft on IP over seismic waves is due any day now.
Don't forget
1926 An Experimental Encapsulation of IP Datagrams on Top of ATM. J.
Eriksson. April 1996. (Form
>> WAP's goal is not to replace IP, but mediate between non-IP wireless
>> devices, and existing IP based wire line applications.
> So then obvious the Right Thing is to put an IP stack on each of those
> devices. Then such "mediation" is unnecessary.
but there may not be enough room in the 640k
%
% At 4:16 PM -0400 6/21/00, Brijesh Kumar wrote:
% >WAP's goal is not to replace IP, but mediate between non-IP wireless
% >devices, and existing IP based wire line applications.
%
% There are no "IP based wire line applications". Applications based on IP
% don't depend on, or know, or care t
At 4:16 PM -0400 6/21/00, Brijesh Kumar wrote:
>WAP's goal is not to replace IP, but mediate between non-IP wireless
>devices, and existing IP based wire line applications.
There are no "IP based wire line applications". Applications based on IP
don't depend on, or know, or care that their packe
"Brijesh Kumar" <[EMAIL PROTECTED]> writes:
>
> WAP's goal is not to replace IP, but mediate between non-IP wireless
> devices, and existing IP based wire line applications.
So then obvious the Right Thing is to put an IP stack on each of those
devices. Then such "mediation" is unnecessary.
--
> > WAP might evolve into something more useful, but I don't see
> > how it will replace IP in any sense.
>
> One is an architecture for supporting application on diverse wireless
> systems, and other is a network layer packet transport mechanism. Two
> aren't even comparable.
the two are comper
Brijesh Kumar wrote:
> The size of display has nothing to do
> with it.
Ah, so that's why WAP uses standard HTML?
--
/\
|John Stracke| http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==
Keith Moore writes:
> -Original Message-
>
>
> WAP might evolve into something more useful, but I don't see
> how it will
> replace IP in any sense.
One is an architecture for supporting application on diverse wireless
systems, and other is a network layer packet transport mechanism. Tw
> I have seen a lot of different people bash WAP over the past two days.
> However, I am a firm believer that WAP will become what IP is to us today.
WAP might evolve into something more useful, but I don't see how it will
replace IP in any sense. WAP as it currently exists isn't a solution
to
ailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 21, 2000 7:31 AM
To: [EMAIL PROTECTED]
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.
Donald
From: Magnus Danielson <[EMAIL PROTECTED]>
To: [EM
ne 21, 2000 7:31 AM
To: [EMAIL PROTECTED]
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.
Donald
From: Magnus Danielson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL P
From: "Donald E. Eastlake 3rd" <[EMAIL PROTECTED]>
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Wed, 21 Jun 2000 07:31:06 -0400
> See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.
For once people could spend some
so, don't say "end-to-end".
>>
>> > If you want, it is still possible to "reconstruct" a true end-to-end
>> > IP service by tunneling it through a NAT with something vaguely
>> > resembling mobile IP.
>>
>> You can have IP
29 matches
Mail list logo
