[OPSEC] comment on 'draft-ietf-opsec-ipv6-implications-on-ipv4-nets'
"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 27 February 2013 18:31 UTC
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A362A21F89CB for <opsec@ietfa.amsl.com>; Wed, 27 Feb 2013 10:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level:
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599]
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 x6fG-xue-q8d for <opsec@ietfa.amsl.com>; Wed, 27 Feb 2013 10:31:54 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id C1CAD21F89B2 for <opsec@ietf.org>; Wed, 27 Feb 2013 10:31:54 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r1RIVsRe023508 for <opsec@ietf.org>; Wed, 27 Feb 2013 10:31:54 -0800
Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r1RIVrUd023496 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <opsec@ietf.org>; Wed, 27 Feb 2013 10:31:54 -0800
Received: from XCH-BLV-102.nw.nos.boeing.com (130.247.25.117) by XCH-NWHT-04.nw.nos.boeing.com (130.247.64.250) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 27 Feb 2013 10:31:53 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.245]) by XCH-BLV-102.nw.nos.boeing.com ([fe80::bcb7:c81b:3e8e:94c2%15]) with mapi id 14.02.0328.011; Wed, 27 Feb 2013 10:31:53 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "opsec@ietf.org" <opsec@ietf.org>
Thread-Topic: comment on 'draft-ietf-opsec-ipv6-implications-on-ipv4-nets'
Thread-Index: Ac4VGLawnms/XfNvRyuAsQEKPKG3yQ==
Date: Wed, 27 Feb 2013 18:31:53 +0000
Message-ID: <2134F8430051B64F815C691A62D9831801380F@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: No
Subject: [OPSEC] comment on 'draft-ietf-opsec-ipv6-implications-on-ipv4-nets'
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 18:31:55 -0000
Hi, In the latest draft version, Section 3.5 says: "As a result, blocking ISATAP by preventing hosts from successfully performing name resolution for the aforementioned names and/or by filtering packets with specific IPv4 destination addresses is both difficult and undesirable." I would like to understand this better. In particular, the ISATAP service is by design disabled by disabling name resolution for the name "isatap.domainname" and/or by disabling the ISATAP router advertisement service. Can you say why this would be difficult and undesirable? Thanks - Fred fred.l.templin@boeing.com
- [OPSEC] comment on 'draft-ietf-opsec-ipv6-implica… Templin, Fred L
- Re: [OPSEC] comment on 'draft-ietf-opsec-ipv6-imp… Fernando Gont
- Re: [OPSEC] comment on 'draft-ietf-opsec-ipv6-imp… Templin, Fred L