[v6ops] FW: ISATAP Operational Guidance
"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 04 June 2013 17:23 UTC
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169E121F9B35 for <v6ops@ietfa.amsl.com>; Tue, 4 Jun 2013 10:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.284
X-Spam-Level:
X-Spam-Status: No, score=-6.284 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvGVzvYaAkzB for <v6ops@ietfa.amsl.com>; Tue, 4 Jun 2013 10:23:27 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB3721F9CD7 for <v6ops@ietf.org>; Tue, 4 Jun 2013 08:39:49 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r54Fdb1M031089 for <v6ops@ietf.org>; Tue, 4 Jun 2013 08:39:37 -0700
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r54FdbFa031084 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <v6ops@ietf.org>; Tue, 4 Jun 2013 08:39:37 -0700
Received: from XCH-BLV-207.nw.nos.boeing.com (10.57.37.63) by XCH-NWHT-02.nw.nos.boeing.com (130.247.70.248) with Microsoft SMTP Server (TLS) id 8.3.297.1; Tue, 4 Jun 2013 08:39:37 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-BLV-207.nw.nos.boeing.com ([169.254.7.162]) with mapi id 14.02.0328.011; Tue, 4 Jun 2013 08:39:36 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: ISATAP Operational Guidance
Thread-Index: AQHOXkM1cisG4pPmVkaNg2jUvvoAqpklssAg
Date: Tue, 04 Jun 2013 15:39:36 +0000
Message-ID: <2134F8430051B64F815C691A62D98318097B2D@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Subject: [v6ops] FW: ISATAP Operational Guidance
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2013 17:23:32 -0000
Hello, There are millions of hosts in operational deployment today with ISATAP enabled by default. Those hosts try to enable ISATAP when there is no native IPv6 available, but administrative action is required to activate the service within the site. RFC 6964 now provides "Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)" (see below). It takes no position on whether the service should be activated, but provides guidance to administrators who are considering its use. The document is therefore offered to the community as an informational resource. Fred fred.l.templin@boeing.com -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org Sent: Friday, May 31, 2013 2:08 PM To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Subject: RFC 6964 on Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) A new Request for Comments is now available in online RFC libraries. RFC 6964 Title: Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Author: F. Templin Status: Informational Stream: Independent Date: May 2013 Mailbox: fltemplin@acm.org Pages: 20 Characters: 49568 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-templin-v6ops-isops-19.txt URL: http://www.rfc-editor.org/rfc/rfc6964.txt Many end-user sites in the Internet today still have predominantly IPv4 internal infrastructures. These sites range in size from small home/office networks to large corporate enterprise networks, but share the commonality that IPv4 provides satisfactory internal routing and addressing services for most applications. As more and more IPv6-only services are deployed, however, end-user devices within such sites will increasingly require at least basic IPv6 functionality. This document therefore provides operational guidance for deployment of IPv6 within predominantly IPv4 sites using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP). INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC
- [v6ops] FW: ISATAP Operational Guidance Templin, Fred L