Re: [v6ops] Operational Guidance for IPv6 Deployment in IPv4 Sitesusing ISATAP

"John Mann (ITS)" <john.mann@monash.edu> Tue, 24 May 2011 23:45 UTC

Return-Path: <john.mann@monash.edu>
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 177BCE06AC for <v6ops@ietfa.amsl.com>; Tue, 24 May 2011 16:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.576
X-Spam-Level:
X-Spam-Status: No, score=-5.576 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 kn3kVP9IiLRP for <v6ops@ietfa.amsl.com>; Tue, 24 May 2011 16:45:23 -0700 (PDT)
Received: from na3sys009aog115.obsmtp.com (na3sys009aog115.obsmtp.com [74.125.149.238]) by ietfa.amsl.com (Postfix) with ESMTP id 905E1E064E for <v6ops@ietf.org>; Tue, 24 May 2011 16:45:22 -0700 (PDT)
Received: from mail-vx0-f181.google.com ([209.85.220.181]) (using TLSv1) by na3sys009aob115.postini.com ([74.125.148.12]) with SMTP ID DSNKTdxDEgQ8Vjl5KwD9W82s4NE3yQQPpQ0O@postini.com; Tue, 24 May 2011 16:45:22 PDT
Received: by vxb39 with SMTP id 39so6620192vxb.40 for <v6ops@ietf.org>; Tue, 24 May 2011 16:45:21 -0700 (PDT)
Received: by 10.52.176.98 with SMTP id ch2mr6157616vdc.51.1306280721236; Tue, 24 May 2011 16:45:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.164.132 with HTTP; Tue, 24 May 2011 16:45:01 -0700 (PDT)
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C6A6C96A3@XCH-NW-01V.nw.nos.boeing.com>
References: <E1829B60731D1740BB7A0626B4FAF0A65C6A6C9302@XCH-NW-01V.nw.nos.boeing.com> <BANLkTinz_RRL11zTTBc6f8uGkDf-Qwe7vw@mail.gmail.com> <E1829B60731D1740BB7A0626B4FAF0A65C6A6C96A3@XCH-NW-01V.nw.nos.boeing.com>
From: "John Mann (ITS)" <john.mann@monash.edu>
Date: Wed, 25 May 2011 09:45:01 +1000
Message-ID: <BANLkTin5uQvncwJY0HoTiN1xO0u+w0R7xQ@mail.gmail.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: multipart/alternative; boundary="20cf3071cecc5dc40804a40e2ef3"
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 23:45:24 -0000

Fred,

OK, if I have this right, something like ...

IRON [RFC6179], RANGER [RFC5720], VET [RFC5558] and SEAL [RFC5320]
are dual-protocol IPv4 and IPv6 overlay technologies that could be used
instead of ISATAP to
enable IPv6 services.

or ... protocol agnostic overlay technologies ...

Thanks,
    John


On 25 May 2011 08:07, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:

>  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
>
>  ------------------------------
> *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> 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
>>
>> -----Original Message-----
>> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
>> On Behalf Of internet-drafts@ietf.org
>> Sent: Monday, May 23, 2011 12:59 PM
>> To: 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
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft<https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft>directories:
>> http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>
>