Groups

Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

info.ietf.hosts

1–27 of 27

0 selected

Annie....@eatel.net

10/18/08

in touch with Ayyavazhi boastfully

Perry wrote: > > Where should I pause another passive rat? > http://sort.bachaan.org -- If

unread,

in touch with Ayyavazhi boastfully

Perry wrote: > > Where should I pause another passive rat? > http://sort.bachaan.org -- If

10/18/08

Neal....@suddenlink.net

10/18/08

within Don yearly

Vincent wrote: > > Where should I favour another native locomotive? > http://thank.bachaan.

unread,

within Don yearly

Vincent wrote: > > Where should I favour another native locomotive? > http://thank.bachaan.

10/18/08

Merl....@msn.com

10/17/08

traveling outside info.ietf.hosts

Paul wrote on 17 Oct 2008 17:53:25 GMT: > > Who can creep another increasing audience? >

unread,

traveling outside info.ietf.hosts

Paul wrote on 17 Oct 2008 17:53:25 GMT: > > Who can creep another increasing audience? >

10/17/08

tomst...@gmail.com

9/1/05

dear info.ietf.hosts readers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's getting a bit tiresome seeing one misguided

unread,

dear info.ietf.hosts readers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's getting a bit tiresome seeing one misguided

9/1/05

Mil...@gregpalast.com

5/18/05

Here is the smoking gun

The memo that has "IMPEACH HIM" written all over it. The top-level government memo marked

unread,

Here is the smoking gun

The memo that has "IMPEACH HIM" written all over it. The top-level government memo marked

5/18/05

lin...@unbrandamerica.org

8/24/03

Unbrand America

In the coming months a black spot will pop up everywhere . . . on store windows and newspaper boxes,

unread,

Unbrand America

In the coming months a black spot will pop up everywhere . . . on store windows and newspaper boxes,

8/24/03

Dave Crocker, bra...@isi.edu2

10/26/95

Request for clarification; RFC 1123 sect. 5.2.14

Sorry, I have lost track of whether I ever answered this, or at least forwarded it to the wise people

unread,

Request for clarification; RFC 1123 sect. 5.2.14

Sorry, I have lost track of whether I ever answered this, or at least forwarded it to the wise people

10/26/95

5/8/95

Question about ICMP behaviour with UDP

*> From myc...@gnu.ai.mit.edu Sat May 6 01:25:01 1995 *> Date: Sat, 6 May 1995 04:24:56 -0400

unread,

Question about ICMP behaviour with UDP

*> From myc...@gnu.ai.mit.edu Sat May 6 01:25:01 1995 *> Date: Sat, 6 May 1995 04:24:56 -0400

5/8/95

bra...@isi.edu, Erik Naggum2

5/4/95

(!!) Request for clarification; RFC 1123 sect. 5.2.14

| But the specification 2*4DIGIT aslo permits a year matching the | specification 3*DIGIT. It is

unread,

(!!) Request for clarification; RFC 1123 sect. 5.2.14

| But the specification 2*4DIGIT aslo permits a year matching the | specification 3*DIGIT. It is

5/4/95

Consumer Credit Advocates

2/9/95

<ad> GUARANTEED CREDIT REPAIR BY LAW FIRM

Consumer Credit Advocates, PC 11 Pennsylvania Plaza, Suite 2101 New York, NY 10001 (212) 629-5261 (

unread,

<ad> GUARANTEED CREDIT REPAIR BY LAW FIRM

Consumer Credit Advocates, PC 11 Pennsylvania Plaza, Suite 2101 New York, NY 10001 (212) 629-5261 (

2/9/95

ba...@cove.mitre.org

11/15/94

rfc 1122 and ICMP SOURCE HOST ISOLATED

Sigh, I propose 6-10 are "hard", 11-12 are "soft", and 13 (if it was ever really

unread,

rfc 1122 and ICMP SOURCE HOST ISOLATED

Sigh, I propose 6-10 are "hard", 11-12 are "soft", and 13 (if it was ever really

11/15/94

11/11/94

rfc 1122 and ICMP SOURCE HOST ISOLATED

*> From Gabriel.M...@eng.sun.com Thu Nov 10 20:40:12 1994 *> Date: Thu, 10 Nov 1994 11:11

unread,

rfc 1122 and ICMP SOURCE HOST ISOLATED

*> From Gabriel.M...@eng.sun.com Thu Nov 10 20:40:12 1994 *> Date: Thu, 10 Nov 1994 11:11

11/11/94

Bob Braden, ba...@cove.mitre.org2

9/9/94

DoD gets its act together (??)

I haven't reviewed them since the very first batch of drafts, which I hated. Walt Lazear *briefly

unread,

DoD gets its act together (??)

I haven't reviewed them since the very first batch of drafts, which I hated. Walt Lazear *briefly

9/9/94

9/6/94

US DoD Use of Internet Protocols

----- Begin Included Message ----- ------------------------------------------------------------------

unread,

US DoD Use of Internet Protocols

----- Begin Included Message ----- ------------------------------------------------------------------

9/6/94

Bob Braden, … Erik Naggum3

3/5/94

Michael, The empty return path is used to prevent loops in the mail system. Consider mail sent

unread,

Michael, The empty return path is used to prevent loops in the mail system. Consider mail sent

3/5/94

1/20/94

for the next edition of host requirements

Jon, I agree with your response, with the additional comment that an FTP should do whatever an

unread,

for the next edition of host requirements

Jon, I agree with your response, with the additional comment that an FTP should do whatever an

1/20/94

pos...@isi.edu, … Steve Deering8

1/13/94

Unusual use of IP Broadcast Address

> Nice try, but her machines don't recognize IP multicast addresses, either. How do you know?

unread,

Unusual use of IP Broadcast Address

> Nice try, but her machines don't recognize IP multicast addresses, either. How do you know?

1/13/94

Bob Braden, Phil Karn2

12/24/93

Question/comment regarding RFC1123 hostnames

The rule I've used for some time with good results is the following: if the argument to the

unread,

Question/comment regarding RFC1123 hostnames

The rule I've used for some time with good results is the following: if the argument to the

12/24/93

David Borman, John C Klensin2

11/22/93

valid chars in host names

>According to RFC-1123/RFC-952, the only valid characters in a >host name are alpha-numerics

unread,

valid chars in host names

>According to RFC-1123/RFC-952, the only valid characters in a >host name are alpha-numerics

11/22/93

11/19/93

Internet based MIL-STDs

Hi folks, A series of MIL-STDs to replace MIL-STD-1777, 1778, 1780, 1781, and 1782 are being prepared

unread,

Internet based MIL-STDs

Hi folks, A series of MIL-STDs to replace MIL-STD-1777, 1778, 1780, 1781, and 1782 are being prepared

11/19/93

Bob Braden, Phil Karn3

11/11/93

Re- TCP broadcast storm

*> From ka...@qualcomm.com Wed Nov 10 21:17:57 1993 *> Date: Wed, 10 Nov 93 21:17:02 -0800 *>

unread,

Re- TCP broadcast storm

*> From ka...@qualcomm.com Wed Nov 10 21:17:57 1993 *> Date: Wed, 10 Nov 93 21:17:02 -0800 *>

11/11/93

11/6/93

Re- TCP broadcast storm

> No way. A broadcast storm like this could have clogged the local > Ethernet, but not the

unread,

Re- TCP broadcast storm

> No way. A broadcast storm like this could have clogged the local > Ethernet, but not the

11/6/93

David A. Borman, … mins...@wc.novell.com4

10/4/93

tcp urgent data

Kurt, >Thanks for the info. I still have some questions though. Your >solution works fine for

unread,

tcp urgent data

Kurt, >Thanks for the info. I still have some questions though. Your >solution works fine for

10/4/93

9/27/93

TCP keepalive question

I was in a discussion recently about keepalives and RFC1122 and we had a question regarding

unread,

TCP keepalive question

I was in a discussion recently about keepalives and RFC1122 and we had a question regarding

9/27/93

Kurt Matthys, Bob Braden2

9/22/93

tcp urgent data

*> I am wondering if there is a standard, approved way to handle tcp *> urgent data when an

unread,

tcp urgent data

*> I am wondering if there is a standard, approved way to handle tcp *> urgent data when an

9/22/93

5/26/93

Longest running floating crap game in New York....

Hi. I don't recall whether this was ever announced, but the original email list for Host

unread,

Longest running floating crap game in New York....

Hi. I don't recall whether this was ever announced, but the original email list for Host

5/26/93

5/26/93

Inbound Broadcast IP Address Handling with Source Route Options

Gary, These situations should not arise for multicasting, since Deering (wisely) specified in RFC-

unread,

Inbound Broadcast IP Address Handling with Source Route Options

Gary, These situations should not arise for multicasting, since Deering (wisely) specified in RFC-

5/26/93

Search

Clear search

Close search

Google apps

Main menu