Document Action: Architectural Implications of NAT to Informational
The IESG <iesg-secretary@ietf.org> Wed, 20 September 2000 13:03 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21512; Wed, 20 Sep 2000 09:03:36 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA13254 for ietf-123-outbound.10@ietf.org; Wed, 20 Sep 2000 08:55:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA12568 for <all-ietf@loki.ietf.org>; Wed, 20 Sep 2000 07:14:02 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18285; Wed, 20 Sep 2000 07:14:01 -0400 (EDT)
Message-Id: <200009201114.HAA18285@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>, IANA <iana@iana.org>
Cc: Internet Architecture Board <iab@isi.edu>
From: The IESG <iesg-secretary@ietf.org>
Subject: Document Action: Architectural Implications of NAT to Informational
Date: Wed, 20 Sep 2000 07:14:01 -0400
Sender: scoya@cnri.reston.va.us
The IESG has approved the Internet-Draft 'Architectural Implications of
NAT' <draft-iab-nat-implications-09.txt> as an Informational RFC. This
document is the product of the Internet Architecture Board.
The IESG contact person is Fred Baker.
Note to RFC Editor:
On page 10, 3rd para, change SNMPv3 to SNMP as follows:
From:
the application (ie: create an application gateway). This may not be
possible for all applications (such as IP based authentication in
SNMPv3), and even with application gateways in the path it may be
To:
the application (ie: create an application gateway). This may not be
possible for all applications (such as IP based authentication in
SNMP), and even with application gateways in the path it may be
Also, on page 11, in the bulleted list, please change:
From:
- NATs invalidate the authentication mechanism of SNMPv3.
To:
- NATs complicate or may even invalidate authentication mechanisms
of SNMPv3