Re: NATs as firewalls

To: Paul Hoffman <paul.hoffman at vpnc.org>
Subject: Re: NATs as firewalls
From: Eliot Lear <lear at cisco.com>
Date: Thu, 01 Mar 2007 17:52:45 +0100
Authentication-results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass (s ig from cisco.com/amsdkim2001 verified; );
Cc: ietf at ietf.org
Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=209; t=1172767970; x=1173631970; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20NATs=20as=20firewalls |Sender:=20; bh=HeBt7BLcQf//QVLnKMQX6+qFNakKRQbKiD3ECnZ+U8A=; b=Gx1FQOF1GAKXvSnUkjcXMawegQXWskSp5f2FaOK0wjwej+cjJb373Nn6FGjf26fMZtXktZ3V SawM17Fz4A4Rqmnr/gF/QpQN+8Nv5lRCLfdfP83BWNqjuTV4yk1w7O50;
In-reply-to: <p0624088dc20ca7f426d1@[10.20.30.108]>
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF-Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
References: <198A730C2044DE4A96749D13E167AD3701147914@MOU1WNEXMB04.vcorp.ad.vrsn.com> <tslk5y25jcw.fsf@cz.mit.edu> <45E691DD.6060107@cisco.com> <p0624088dc20ca7f426d1@[10.20.30.108]>
User-agent: Thunderbird 2.0b2 (Macintosh/20070116)

Paul,

Without going down the NAThole my real intent here is simply to motivate people who think they're bad to please look at the management complexities of renumbering. I know I am looking.

Eliot

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

References:
- RE: Last Call: draft-ietf-v6ops-natpt-to-historic (Reasons to Move NAT-PT to Historic Status) to Informational RFC
  - From: Hallam-Baker, Phillip
- Re: Last Call: draft-ietf-v6ops-natpt-to-historic (Reasons to Move NAT-PT to Historic Status) to Informational RFC
  - From: Sam Hartman
- Re: Last Call: draft-ietf-v6ops-natpt-to-historic (Reasons to Move NAT-PT to Historic Status) to Informational RFC
  - From: Eliot Lear
- NATs as firewalls
  - From: Paul Hoffman

Prev by Date: NATs as firewalls
Next by Date: Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP
Previous by thread: NATs as firewalls
Next by thread: Re: NATs as firewalls
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: NATs as firewalls

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.