Re: IPP> regarding "ipp:" (I spoke too soon...)
Keith Moore <moore@cs.utk.edu> Fri, 03 July 1998 19:11 UTC
Delivery-Date: Fri, 03 Jul 1998 15:11:38 -0400
Return-Path: ipp-owner@pwg.org
Received: from cnri.reston.va.us (ns [132.151.1.1])
by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA28328
for <ietf-archive@ietf.org>; Fri, 3 Jul 1998 15:11:38 -0400 (EDT)
Received: from lists.underscore.com (uscore-1.mv.com [199.125.85.30])
by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA25512
for <ietf-archive@cnri.reston.va.us>; Fri, 3 Jul 1998 15:13:57 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com
(8.7.5/8.7.3) with SMTP id PAA08678 for <ietf-archive@cnri.reston.va.us>;
Fri, 3 Jul 1998 15:11:36 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Fri, 3 Jul 1998 15:07:29 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id
OAA08031 for ipp-outgoing; Fri, 3 Jul 1998 14:58:43 -0400 (EDT)
Message-Id: <199807031857.OAA18419@spot.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Jay Martin <jkm@underscore.com>
cc: Keith Moore <moore@cs.utk.edu>, Carl-Uno Manros <manros@cp10.es.xerox.com>,
Scott Isaacson <SISAACSON@novell.com>, paf@swip.net,
paulmo@microsoft.com, ipp@pwg.org, moore@cs.utk.edu
Subject: Re: IPP> regarding "ipp:" (I spoke too soon...)
In-reply-to: Your message of "Fri, 03 Jul 1998 14:31:54 EDT."
<359D239A.1CE7D493@underscore.com>
Date: Fri, 03 Jul 1998 14:57:06 -0400
Sender: owner-ipp@pwg.org
> Sorry, but what is a "NAT box" ? Network address translator. It's a kind of IP router that changes the source or destination address, or the source or destination port, as the packets pass through. A popular kind of NAT box is one that provides the illusion of Internet access to a private IP network, mapping one or more external IP addresses to a number of private IP addresses. Such boxes do not necessarily provide a one-to-one mapping between an internal IP address and the one that appears on the global Internet. So they sometimes change the port number, as well as the address, to avoid conflicts between multiple hosts using the same external address and the same port. And the mappings between external and internal addresses may be dynamically assigned and change from time to time. What this means is that a client or server's notion of the IP address or port used in the conversation, may not be the same as the server or client's view from the other end of the connection. Pure NAT boxes break a number of protocols that, for one reason or another, depend on the client and server sharing the same notion of endpoint identifiers. So real NAT boxes tend to perform not only IP-level translation, but serve as translating proxies for a number of higher level protocols. NATs thus share many characteristics as firewalls, and often these functions are combined in one box. But NAT boxes are more evil (from an application protocol designer's point-of-view) than firewalls that don't do NAT. Lots of us hate these things, but for a variety of reasons including scarcity of IP address space, and commodity pricing of dialup accounts limited to one IP address, they're widely deployed. Keith
- IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- RE: IPP> regarding "ipp:" (I spoke too soon...) Paul Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- RE: IPP> regarding "ipp:" (I spoke too soon...) Paul Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- Re: IPP> regarding "ipp:" (I spoke too soon...) Tom Hastings
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Scott Isaacson
- RE: IPP> regarding "ipp:" (I spoke too soon...) Josh Cohen
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- Re: IPP> regarding "ipp:" (I spoke too soon...) Scott Lawrence
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Randy Turner
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- Re: IPP> regarding "ipp:" (I spoke too soon...) Robert Herriot
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- RE: IPP> regarding "ipp:" (I spoke too soon...) Josh Cohen
- Re: IPP> regarding "ipp:" (I spoke too soon...) Jay Martin
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Tom Hastings
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Tom Hastings
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Keith Moore
- IPP> clarification needed re: "ipp:" proposal Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) papowell
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Tom Hastings
- RE: IPP> regarding "ipp:" (I spoke too soon...) Ron Bergman
- IPP> On clarifying the proposal for a new IPP sch… Tom Hastings
- IPP> Re: On clarifying the proposal for a new IPP… Keith Moore
- Re: IPP> Re: On clarifying the proposal for a new… Carl-Uno Manros