Document Action: 'Unmanaged Networks IPv6 Transition Scenarios' to Informational RFC

The IESG <iesg-secretary@ietf.org> Wed, 26 November 2003 22:41 UTC

Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01112 for <ietf-announce-web-archive@odin.ietf.org>; Wed, 26 Nov 2003 17:41:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AP7qg-0001Wh-Aa for ietf-announce-list@asgard.ietf.org; Wed, 26 Nov 2003 17:09:26 -0500
Received: from apache by asgard.ietf.org with local (Exim 4.14) id 1AP7nF-0001U5-77; Wed, 26 Nov 2003 17:05:53 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, v6ops@ops.ietf.org
Subject: Document Action: 'Unmanaged Networks IPv6 Transition Scenarios' to Informational RFC
Message-Id: <E1AP7nF-0001U5-77@asgard.ietf.org>
Date: Wed, 26 Nov 2003 17:05:53 -0500
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

The IESG has approved following document:

- 'Unmanaged Networks IPv6 Transition Scenarios '
   <draft-ietf-v6ops-unman-scenarios-03.txt> as an Informational RFC

This document is the product of the IPv6 Operations Working Group. 

The IESG contact person is Bert Wijnen.

RFC-Editor note:

- On page 2, please replace text

OLD:

   Between the subnet and the ISP access link is a gateway, which may
   or may not perform NAT and firewall functions. A key point of this
   configuration is that the gateway is typically not "managed". In
   most cases, it is a simple "appliance", which incorporates some
   static policies. However, there are many cases in which the gateway
   is procured and configured by the ISP, and there are also some
   common cases in which we find two gateways back to back, one managed
   by the ISP and the other added by the owner of the unmanaged
   network.

NEW:

    Between the subnet and the ISP access link is a gateway, which may or
    may not perform NAT and firewall functions. A key point of this
    configuration is that the gateway is typically not "managed". In most
    cases, it is a simple "appliance", which incorporates some static
    policies. There are many cases in which the gateway is procured and
    configured by the ISP.
                                                                            
  
    Note that there are also some cases in which we find two
    gateways back to back, one managed by the ISP and the other added by
    the owner of the unmanaged network. They are not covered in this memo
    because most of them either require some management, or the gateway
    added by the user can function as a L2 switch.