From: Theo Honohan <theoh@chiark.greenend.org.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IL and NAT
Date: Sat, 18 Nov 2000 19:00:32 +0000 [thread overview]
Message-ID: <E13xDE0-0004ne-00@chiark.greenend.org.uk> (raw)
In-Reply-To: Your message of "Sat, 18 Nov 2000 18:42:05." <E13xCv7-000E0k-0X@anchor-post-33.mail.demon.net>
nigel@9fs.org wrote:
>
> Before we are too down on NAT implementations, there is a distinction
> between NAT and NAPT, according to various RFCs and associated
> documents.
Yes, quite. I didn't mean to be "down on" simple NAT implementations;
OTOH, I do still think it's a fair to say that you need to do both NAT
and NAPT to be a viable product, these days.
next prev parent reply other threads:[~2000-11-18 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 18:42 nigel
2000-11-18 19:00 ` Theo Honohan [this message]
2000-11-18 19:24 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2000-11-18 14:04 presotto
2000-11-18 6:32 anothy
2000-11-18 3:21 geoff
2000-11-18 13:53 ` Theo Honohan
2000-11-18 0:17 geoff
2000-11-18 0:50 ` Christopher Nielsen
2000-11-18 1:19 ` Boyd Roberts
2000-11-18 3:02 ` Scott Schwartz
[not found] <cnielsen@pobox.com>
2000-11-17 23:48 ` Christopher Nielsen
2000-11-17 23:56 ` Scott Schwartz
2000-11-18 14:20 ` Steve Kilbane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E13xDE0-0004ne-00@chiark.greenend.org.uk \
--to=theoh@chiark.greenend.org.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).