Re: US DoD and IPv6

TJ <trejrco@gmail.com> Fri, 01 October 2010 15:38 UTC

Return-Path: <trejrco@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 023723A6DA8 for <ietf@core3.amsl.com>; Fri, 1 Oct 2010 08:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHiSaxU2tTz9 for <ietf@core3.amsl.com>; Fri, 1 Oct 2010 08:38:11 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id EE3A93A6E82 for <ietf@ietf.org>; Fri, 1 Oct 2010 08:38:10 -0700 (PDT)
Received: by iwn3 with SMTP id 3so4751823iwn.31 for <ietf@ietf.org>; Fri, 01 Oct 2010 08:38:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:reply-to :in-reply-to:references:from:date:message-id:subject:to:content-type; bh=O6irzt9/iV/DKZl5RsoL4oILgMZEY4y0jBxr9ZMjrTY=; b=gp0mDRDhVOCnk5vv7rWBNlAjCNGsyj4//orY9fP9AFH+cZucNvUSQZGDrjzLexNV4k zpZwkiwv0vvYxlPUZsrbNxgFpwSUcj8SNQ2z2lw/0ihGV2yqWidPa3hFI60BzetTtb7Q k8hrxKLB0idva5zPQXoiuLfLZsE/M+hiC8TVQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; b=N0nkYCR1CD0+g35JLVv7VnojzkXJRHL05lbBGXOLgzeW6f5k1QwTZ9m0doVK1wAxpX pxra8NynWx0WsKRv8bVZT+ZOUegtY+JMnsHGiHRm0Q6q0DQnblUlLrXL/Nb7lnbqUnHA X4UOR5vGStWnSvYUNLeWm7WTDQpqB4nV6rnnU=
Received: by 10.231.11.13 with SMTP id r13mr4631999ibr.137.1285947516644; Fri, 01 Oct 2010 08:38:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.1.29 with HTTP; Fri, 1 Oct 2010 08:38:13 -0700 (PDT)
In-Reply-To: <0BB22978-4F50-4E79-B04A-6C138C208FA0@gmail.com>
References: <0BB22978-4F50-4E79-B04A-6C138C208FA0@gmail.com>
From: TJ <trejrco@gmail.com>
Date: Fri, 01 Oct 2010 11:38:13 -0400
Message-ID: <AANLkTi=j2dz=PXurqp+Ofr625T+jX9jQ3FjeiJsqcDuq@mail.gmail.com>
Subject: Re: US DoD and IPv6
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="0022152d622def162f04918ffca7"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 15:38:12 -0000

>
> A bit before then, Thomas Narten wrote:
> > There are DoD networks where IPv6 is running today,
> > and there certainly are networks where it is not.
>
> The quote above seems very precisely phrased,
> and as an accidental result seems a bit misleading.
>
> It appears to refer to the Defense Research & Engineering Network
> (DREN), which is widely reported to be dual-stack IPv4 and IPv6.
> [e.g. see Ron Broersma's slides from the Google IPv6 Implementer's
> Workshop]
>
> However, the trade press and other public sources consistently
> indicate the DoD considers DREN to be "experimental" or "research",
> rather than "operational" (at least for the DoD meaning of the
> word 'operational').
>
> One also consistently reads that the actual operational DoD backbone
> (i.e. DISA's GIG-BE network) is IPv4 only, in part for security
> reasons and in part for lack of any business case to do otherwise,
> and that all other DoD "operational" networks are also IPv4 only.
>
>
The DoD is forbidden from running native IPv6 operationally, per the STIGs
and MO guidelines.  MO1 and 2 get some IPv6 in place, in tunnels across the
GIG ... MO3 will be the first step in native/operational IPv6, not even
signed yet IIRC.


/TJ