help
_
ÍøÉ϶©»¨È«¹úËÍ http://shopping.263.net/category12.htm
ÊýÂë²úÆ·£¬ÜöÝÍÕ¹Âô http://shopping.263.net/category21.htm
Hello,
X-Mailer: Internet Mail Service (5.5.2653.19) represents a service within
Microsoft Exchange Server 5.5 that is responsible for all Internet services.
Regards,
Jeremy McGowan
Systems Consultant, MCSE, CCDA, CCNA, CSSP, Master TCP/IP Administrator, A+,
Network +
atec|group
Technology In
> From: "J. Noel Chiappa" <[EMAIL PROTECTED]>
> ...
> X-Mailer: Internet Mail Service (5.5.2653.19)
>
> Anyone know whose email software this is? ...
After my previous modest proposals that the IETF list reject all
messages displaying "Mailer: Internet Mail Service" stigmata,
I was told th
%
% On the way here, the flight attendant insisted that I turn off my Palm Pilot.
%
% Do they make people turn off hearing aids?
%
% d/
%
Nope, nor oxygen.
--
--bill
Mailing list information for follow up to the MIDTAX BOF that took
place today:
Post: [EMAIL PROTECTED]
(Un)Subscribe: [EMAIL PROTECTED]
Archive:yes, but web access not yet available
Apologies for spamming the whole IETF list with this, we goofed and
didn't have this informati
At 09:11 PM 3/19/2001, RL 'Bob' Morgan wrote:
>On the plane last night, flying in to Minneapolis:
>
>"We're now starting our descent, please return your tray tables and seat
>backs to their upright and locked position, and turn off any electronic
>equipment."
>
>2 minutes later:
>
>"People! We re
On the plane last night, flying in to Minneapolis:
"We're now starting our descent, please return your tray tables and seat
backs to their upright and locked position, and turn off any electronic
equipment."
2 minutes later:
"People! We really need you to turn those laptops off NOW ..."
- R
So, my message to the IETF list produced the usual cascade of "Out-Of-Office
Autoreply" messages, fromn people I've never heard of, and who *certainly*
weren't in the "To:" or "Cc:" fields of the header.
I'm going to withhold the names of the guilty (they were all from completely
different compa
> From: "Mike O'Dell" <[EMAIL PROTECTED]>
> the distinction is often based on the namespace used for making the
> forwarding decision
> the term "router" is *usually* applied to a device which is examining
> an L3 token ... a switch is usually examining a token other than an I
There has been some concern over the scope of the IETF sub-IP effort. This
is an attempt to help clarify the view of the IESG on a number of issues.
RFC 2026 defines the Internet as:
"a loosely-organized international collaboration of
autonomous, interconnected
networks, supp
At 12:12 19/03/2001 -0500, Garrett Wollman wrote:
><<[EMAIL PROTECTED]> said:
>
> > That's my reason to use the TTL decrement; if someone shows me a device
> > where a packet comes in on one interface with a certain TTL, and it comes
> > out on another interface with a lower TTL but no other signi
At 10:43 19/03/2001 -0500, Dan Kolis wrote:
>Grretings,
>Some few days ago I posted a question for an opinion, perhaps it was too
>long? The question is: in the RFC framework would a specification for
>barcode / machine symbols to URLS be too far afield of ietf mandates?
Yes, it would be too far
> "Garrett" == Garrett Wollman <[EMAIL PROTECTED]> writes:
>> That's my reason to use the TTL decrement; if someone shows me a device
>> where a packet comes in on one interface with a certain TTL, and it comes
>> out on another interface with a lower TTL but no other significan
< said:
> That's my reason to use the TTL decrement; if someone shows me a device
> where a packet comes in on one interface with a certain TTL, and it comes
> out on another interface with a lower TTL but no other significant changes,
> I call it a router.
Except that I can now show you a ``
really^100 sorry again for spamming. I got no response from NOC guys
yet.
the following 3 wireless basestations are configured no to bridge
ethernet-layer multicast, preventing IPv6 from working across them.
please turn on ethernet-layer multicast bridging
Grretings,
Some few days ago I posted a question for an opinion, perhaps it was too
long? The question is: in the RFC framework would a specification for
barcode / machine symbols to URLS be too far afield of ietf mandates? There
are some DNS like issues, but not too many.
I'm a little surprised
Due to the conflict between interest in the MULTI6 and HIP sessions, HIP
and NAT have switch time slots.
So now NAT is at 1415 hours in Salon G
and HIP is at 1545 hours also in Salon G
Hope this works for more people than the other arrangement
< said:
> note: I have not yet found anything that allows me to tell the difference
> between a switch and something that is not a switch. That is one reason why
> I prefer to avoid the term.
Hmmm. I always thought that the definition of ``switch'' in a packet
context was fairly well-understo
Monday, March 19, 2001, 11:21:44 AM,
[EMAIL PROTECTED] (Internet Draft Submission Manager) wrote:
IDSM> Greetings,
IDSM> We are sorry, but the cut-off for Internet-Draft submissions was Friday,
IDSM> March 2, 2000 at 5pm ET. Your submission will not be retained (i.e. you
IDSM> need to resubmit)
19 matches
Mail list logo