Re: [v6ops] Operational Guidance for IPv6 Deployment in IPv4 Sitesusing ISATAP
"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 24 May 2011 22:07 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 0435CE07C4 for <v6ops@ietfa.amsl.com>; Tue, 24 May 2011 15:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level:
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DuAnwzzPC0WD for <v6ops@ietfa.amsl.com>; Tue, 24 May 2011 15:07:07 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id 01ACFE07A7 for <v6ops@ietf.org>; Tue, 24 May 2011 15:07:06 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p4OM74QU005528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 24 May 2011 17:07:04 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p4OM73SD004972; Tue, 24 May 2011 17:07:03 -0500 (CDT)
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p4OM72wa004937 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 24 May 2011 17:07:03 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-03.nw.nos.boeing.com ([130.247.71.23]) with mapi; Tue, 24 May 2011 15:07:02 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "John Mann (ITS)" <john.mann@monash.edu>
Date: Tue, 24 May 2011 15:07:00 -0700
Thread-Topic: [v6ops] Operational Guidance for IPv6 Deployment in IPv4 Sitesusing ISATAP
Thread-Index: AcwaV0yNvktUcb7/Rnax1zqxY2DNSQABryzg
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6A6C96A3@XCH-NW-01V.nw.nos.boeing.com>
References: <E1829B60731D1740BB7A0626B4FAF0A65C6A6C9302@XCH-NW-01V.nw.nos.boeing.com> <BANLkTinz_RRL11zTTBc6f8uGkDf-Qwe7vw@mail.gmail.com>
In-Reply-To: <BANLkTinz_RRL11zTTBc6f8uGkDf-Qwe7vw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_E1829B60731D1740BB7A0626B4FAF0A65C6A6C96A3XCHNW01Vnwnos_"
MIME-Version: 1.0
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Operational Guidance for IPv6 Deployment in IPv4 Sitesusing ISATAP
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, 24 May 2011 22:07:08 -0000
Hi John, Please believe me when I say that it is not a round-about way of praising myself - quite to the contrary, I was trying to be respectful of others. These technologies are however alternative approaches that could be used in the same use cases as ISATAP, and I have also co-authored a RANGER Scenarios document [RFC6139] that shows how this is true. Perhaps it would be acceptable to just list the technologies under Alternative Approaches, but delete the non-technical phrasing that caught your attention? Thanks - Fred fred.l.templin@boeing.com<mailto:fred.l.templin@boeing.com> ________________________________ From: John Mann (ITS) [mailto:john.mann@monash.edu] Sent: Tuesday, May 24, 2011 2:12 PM To: Templin, Fred L Cc: v6ops@ietf.org Subject: Re: [v6ops] Operational Guidance for IPv6 Deployment in IPv4 Sitesusing ISATAP Fred, I like ISATAP and your draft. But I'm not sure about --- 9. Alternative Approaches ... IRON [RFC6179], RANGER [RFC5720], VET [RFC5558] and SEAL [RFC5320] are a tribute to those in all walks of life who serve with dignity and honor for the benefit of others. --- a) it seems out of place in that it doesn't discuss the method used or service provided by these protocols. b) is it a round-about way of praising yourself in that you are the author of those protocols, and of this draft? ====== Also in http://tools.ietf.org/html/draft-templin-v6ops-isops-05#section-9 the text "[RFC4554]" doesn't web-link to http://tools.ietf.org/html/rfc4554 But I can't tell if this is a original markup problem, or draft->html converter problem. Thanks, John On 24 May 2011 07:16, Templin, Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote: Folks, I am done tweaking this document now. Would appreciate input, especially from those who have expressed interest in ISATAP over the past several weeks. Thanks - Fred fred.l.templin@boeing.com<mailto:fred.l.templin@boeing.com> -----Original Message----- From: i-d-announce-bounces@ietf.org<mailto:i-d-announce-bounces@ietf.org> [mailto:i-d-announce-bounces@ietf.org<mailto:i-d-announce-bounces@ietf.org>] On Behalf Of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> Sent: Monday, May 23, 2011 12:59 PM To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org> Subject: I-D Action: draft-templin-v6ops-isops-05.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Operational Guidance for IPv6 Deployment in IPv4 Sites using ISATAP Author(s) : Fred L. Templin Filename : draft-templin-v6ops-isops-05.txt Pages : 26 Date : 2011-05-23 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 continues to provide satisfactory internal routing and addressing services for most applications. As more and more IPv6-only services are deployed in the Internet, however, end user devices within such sites will increasingly require at least basic IPv6 functionality for external access. It is also expected that more and more IPv6-only devices will be deployed within the site over time. This document therefore provides operational guidance for deployment of IPv6 within predominantly IPv4 sites using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-templin-v6ops-isops-05.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-templin-v6ops-isops-05.txt _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org> https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt _______________________________________________ v6ops mailing list v6ops@ietf.org<mailto:v6ops@ietf.org> https://www.ietf.org/mailman/listinfo/v6ops
- [v6ops] Operational Guidance for IPv6 Deployment … Templin, Fred L
- Re: [v6ops] Operational Guidance for IPv6 Deploym… John Mann (ITS)
- Re: [v6ops] Operational Guidance for IPv6 Deploym… Templin, Fred L
- Re: [v6ops] Operational Guidance for IPv6 Deploym… John Mann (ITS)
- Re: [v6ops] Operational Guidance for IPv6 Deploym… Templin, Fred L