Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking IPv6 extension headers? (Episode 1000 and counting) (Linux DoS)
Michael McBride <michael.mcbride@futurewei.com> Thu, 18 May 2023 18:35 UTC
Return-Path: <michael.mcbride@futurewei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79938C15198E; Thu, 18 May 2023 11:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fu_Hxv-K2sJf; Thu, 18 May 2023 11:35:53 -0700 (PDT)
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on20716.outbound.protection.outlook.com [IPv6:2a01:111:f400:7e89::716]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03DBFC151719; Thu, 18 May 2023 11:35:52 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ix+qO1M1oSs+6ZBz7ltrn1ylw3wQYoPXPW4O+drs52pqq4eN1s/u+aS6HfYH6IBS/jWDOfJJFR8STNDUZKYlIC4K+DA1HxAUHOA4OXwlXJH8uJt2l52Pzy+qFVo/E61srJ/G1RU1k6v4FD8fpd84EAMhajzZJsxCJwdnXCH43VLHRWH07RlYCcb53MQGt5cfB06O9+2tfETjufIY+N5RD6zN4uhyODLwYFkwwGYeizu0dHi2JYxdZUWChHMrjzkoyGQoVu28yWsIuVMpwiGnbxKUzi/pCaAz4WuEPPPSvFFzAw+TRIgiuOb/nc70dlebfvHZ+0d+yGD1z2vRQg8mDg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=jJzAIRB2iaAZ1/1Kh+5cEjCRiIg9j2OWPlCGAejVyRI=; b=Q3PC6H0qz02llQA4vj5qdtcQ30reF8F41sPmddNV0U5P6BKZch/gs57F/DqsvHsMtT0Bl51zeIirjJ+56zKUwew9F26XlHO6j4DXCkSi2VqHQHB/ifoDq7qgwFSv8YUEQArqusSXVu9CnGf0IJE52pDqtBd2RP9k/jVKNwT3GMLd+z9adCCZEvI9m2OEy0bmR/f0BrZXHfr8I4iOzU3xhebM5BdFSjaDkSSqcAM8FI0dtiN5WH0JlDQBHRflIQpQz5hRpV0oFO+8BryfK76VYoO0S/CgAxKO7vWzo1YZn49ETpEGJMPXR+3cgIav6NS9jFOTFFoTqR58tdwPiZWrPw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jJzAIRB2iaAZ1/1Kh+5cEjCRiIg9j2OWPlCGAejVyRI=; b=XGOZ1H7S/H69i7TE2cqi/JPGju2H/rCxgMMVQXCuoVSbGeOHIrRDZsZyn7GbX7mitjxEDZ2W7bcoxPjDlhwgdOAJXcMEOE2L14nBxN/Z4tDW2yhPr5hmVRFsjpncr0wJ8SqqnhOMMUmG7nWly/4SEMsogKcI+ta2Q4VvnW2DUyc=
Received: from SJ0PR13MB5739.namprd13.prod.outlook.com (2603:10b6:a03:40b::13) by MN2PR13MB3973.namprd13.prod.outlook.com (2603:10b6:208:267::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.19; Thu, 18 May 2023 18:35:47 +0000
Received: from SJ0PR13MB5739.namprd13.prod.outlook.com ([fe80::1d92:74cd:6f84:7f61]) by SJ0PR13MB5739.namprd13.prod.outlook.com ([fe80::1d92:74cd:6f84:7f61%6]) with mapi id 15.20.6387.030; Thu, 18 May 2023 18:35:47 +0000
From: Michael McBride <michael.mcbride@futurewei.com>
To: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>, Tom Herbert <tom=40herbertland.com@dmarc.ietf.org>, Nick Buraglio <buraglio@forwardingplane.net>
CC: Andrew Campling <andrew.campling@419.consulting>, Fernando Gont <fgont@si6networks.com>, V6 Ops List <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>, opsec WG <opsec@ietf.org>
Thread-Topic: [IPv6] [v6ops] [OPSEC] Why folks are blocking IPv6 extension headers? (Episode 1000 and counting) (Linux DoS)
Thread-Index: AQHZiZiMDtUZezA4iUujSOnCFwK2Bq9gWj5w
Date: Thu, 18 May 2023 18:35:46 +0000
Message-ID: <SJ0PR13MB573966E1832783D92C9C0F09F47F9@SJ0PR13MB5739.namprd13.prod.outlook.com>
References: <11087a11-476c-5fb8-2ede-e1b3b6e95e48@si6networks.com> <CALx6S343f_FPXVxuZuXB4j=nY-SuTEYrnxb3O5OQ3fv5uPwT8g@mail.gmail.com> <CAN-Dau1pTVr6ak9rc9x7irg+aLhq0N8_WOyySqx5Syt74HMX=g@mail.gmail.com> <a087b963-1e12-66bf-b93e-5190ce09914b@si6networks.com> <CWXP265MB515321A0E0A91CD66260C26CC27F9@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM> <CALx6S35py1b6EyS3UeT8JvgwN-w8wBtprCn9OJSCS-nvfQ_L-A@mail.gmail.com> <CAGB08_djDtrFRY37ZTH_draGLTxM3vO7bMfT6YyyKFrTH_Tx5w@mail.gmail.com> <1200504588.3592661.1684421597958@mail.yahoo.com>
In-Reply-To: <1200504588.3592661.1684421597958@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=futurewei.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SJ0PR13MB5739:EE_|MN2PR13MB3973:EE_
x-ms-office365-filtering-correlation-id: f2b12328-bd6c-4330-3d3c-08db57ceb230
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: f2uzrURsPooDs6NDtDjsQTo8c8tj+E3P+Il2OOgb04pt9QuYYfAPTE6LrSDDW/M+arQmDyB5+VvSsuOEIAPHgKvKWr2bobNk5yt1+UMkS6mKGOFadis60VtXazT8dS3ooCV8a045Ay5ramRruWKZVzSQ98+EZRNKQNoEtMyAA9L3Dr8HCzput1Eu/+msUvYuMtD0Rq3kHsvIHe2c9kA74t0/Q8fqP7s4fwJmr5xjHa6xTLypQksUy9yGJMxMjCP6FjBOVkZf1P4BFeUtqu6KdRiQYliH4svFWUxyqam371BxAm3MoBlgajbfdiwGxU769GEPWF+xlF3WU0p+In42EELwzPr5pYhF6chkSVCCuvjZMO30lIjioDyj3LYKlBghOEE2v+6XXxRq0JWcjjpBTqEVoHRdebn6Iz0C1rYngya15cAdTcqBquoM8fTcnMZIFVrVe1WELNxcJ8K+PUngTa1qx5Gx8CunypaSNqNKT87NWVXZoTSVWDb3Aou0Ogc+Eo71jwzHat0N3amw11dilsXyeMqCck1f+eZcIFbYKzXoOds4MeaMsZ6TyXizud0UXvUjhgMTGB7RI9/KZhKjJFepSSlVQU1GEwztTSlmSo39BvP9rlmrmlHoBk6fxEI0pcJMHrxrPbPi1i6bSRY294+NBoNySpH20xBy7euPAZgjk2gU7GWDR7IEThBgOmY7eOQx+fSUH+5JJGxd2Noavg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SJ0PR13MB5739.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230028)(4636009)(396003)(366004)(39850400004)(346002)(136003)(376002)(451199021)(2906002)(316002)(478600001)(52536014)(41300700001)(4326008)(8676002)(8936002)(54906003)(110136005)(5660300002)(66899021)(71200400001)(66446008)(66556008)(66946007)(76116006)(64756008)(66476007)(7696005)(53546011)(966005)(9686003)(6506007)(26005)(38100700002)(186003)(55016003)(122000001)(83380400001)(38070700005)(40140700001)(166002)(86362001)(33656002)(221023011); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: A/fNdiXudWQooHljUkKqL+/sn1unpl1d/Qs3JlqNsO7R6PFlXGSyWPzoR4T5CZHk8Ohpu0i1cud9tzy7V46Hnn0mPxC/G3KAPLAIE9DFXhziq0L2QJI7YD1l0IhREUj1eBxWT6Hq6MzXxG1SCuCU21unG0iq3KLVX61WygSHKvQvuFEvWhHJlwWEuzejxqSyp8zPWHyjnWx4wABpxN4ZtGK4/ZHXDiQq0IFmuBplN04X7yVpJJqNB8BWMpbOOGsYvvXmYjHFEB+r0uZLZjD108HRPU/GUdqVqgCmeWhKzS78rfOFIanL8/BUcwd3v8bbqd0BxJqwFhe0YQ8OiX/n3EQx9PEqVr+eO/TAYxzd0gJBNnli7X98HT0Gf4iLf26vnJ80PVuSfo9S5sbGA/d6PAS01TZDLdf1vuml8eIlb1mKCCQRbWV5FEgWl/ApsCgVTWQ6gqWCdwpb7X4ulQwpQwjTQHHLKinuI3nWb3b2/+7p09yltfVLsb58oizILt9Ewtb5Yvqh4VYLB7bfuobPdnNvMQvp8WPGTdsnuRX37cs3k4TW3bnUImE4OMmFlDoNcn1CFi4LElM73Bms17pFhJM9Z8TMCoAK/1ATq2cuw7oF5wq7qNT6Wq21HKHHcPpRKYc40SgN5kPwCCZhACIbxsFT/Yfr5GYz3iVKrdXcnkF7fpk/S3r7UKb5VkJ+OGQqQA68LEo2vfKixigKtV89YUgaA/aSRGTnAWhIOuypfQFbuxBb2XrShvDB8BGCf0bEzI/iHTCoqx2pb26jO9+BmHGP2c5gVybFjMIPofWZlSGQ5RA75xP2+tMqpMCimpoPvohFi2wJF/DDqcjtPgCIJIA3dU5H+dzq2zE+OZyRVpxB7hmXL/0GJjaHuIU27+nfSmODANuoSWNI+coHOr4hxLPp5tJuT/sTcKg/tsZLt8xxcuQRcXwbJqaNWsRi4mWRUR1VkItYjTxYYGyoj9oBkMQJDhNbQxxN4uExZV/EP+yYZJ9t7wJ3e4l2W+XmsN4aVrtLNTzRlhn36SdHho2A0CNY7jMYn3IXBlCQvBBYoGQCGLph39b0kDxkAxqRxUgyYfva2nYBfEPvAGcX62+1cJVBwy78nk9tCkEC/THVJCrovYYDjTvhyQVyQMmSPQ9AdRfFmmh3N9HTJI1miF5sDigBdNAM4FGItKfWOZn2DuA0s83YOyJhMOO6YdX8L6DFl5z9c+2Y7EZp+EEWYNRiS3tvnQO65kRAh0JNSZToIjUN2Mv8gg11nonkpj5yOCnT/YexAdup+f66HnLs0pmGeEcHivQQKROMbbT1yzrPbWgP3ipWi2Rnp5hqOZux+GMqCTJIcukLuwa0fWyVF7QT+nxRgD8l6Om/EuD2ZB16U8ODF3HewookhJ/6yEbn+BW4pUpoaIRmOCF6VCB0oypp5ITA91WflYi6rJXE4Xwtjk96l2/s+Lmb2tzlFUXA95KhnPocqsTB+9cJSoYG2lww/U6j6w7pmHyxpzyZmhE+qMEmwcUc/h3FUU1sB3ZRHLZEnkW4MQ1ASVl7OuVbexJAjMYBKEMi3Soys/KKOcGvcSu5ffLZpXWPSPFfOLZjQ32V
Content-Type: multipart/alternative; boundary="_000_SJ0PR13MB573966E1832783D92C9C0F09F47F9SJ0PR13MB5739namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SJ0PR13MB5739.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f2b12328-bd6c-4330-3d3c-08db57ceb230
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2023 18:35:46.7306 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3kRY1hzM6Iex9YEL2iSxipatPhupyvVCbOVbQ+JF8NubUuK+LxDGiRkNUGBY40xKocyQy7TqnoBC0YqYTdD1yg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3973
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/VM1askduXY4tZY7VcmI0HtyT2H0>
Subject: Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking IPv6 extension headers? (Episode 1000 and counting) (Linux DoS)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 May 2023 18:35:57 -0000
> I think a use cases document is a great idea! Although, IMHO one of the points of extension headers is that they can be used to extend the protocol for purposes which we cannot think of today! +1 to a EH use case document. Some of us, for instance, have been trying to standardize a bitstring in an EH. It would be good to at least document as a use case. thanks, mike Thanks, Nalini Elkins CEO and Founder Inside Products, Inc. www.insidethestack.com<http://www.insidethestack.com/> (831) 659-8360 On Thursday, May 18, 2023 at 07:49:50 AM PDT, Nick Buraglio <buraglio@forwardingplane.net<mailto:buraglio@forwardingplane.net>> wrote: Is there any document that details the current operational best practices or explains the EH options and use cases in a succinct document? I didn't find one (although I did not look terribly hard). If not, that sounds like an opportunity to work through them and create one, perhaps? Nalani has a deep dive study here https://www.ietf.org/archive/id/draft-elkins-v6ops-eh-deepdive-fw-01.html and https://datatracker.ietf.org/doc/draft-elkins-v6ops-eh-deepdive-cdn/ but I wasn't able to find a list with some use cases akin to the ND considerations draft here https://datatracker.ietf.org/doc/draft-ietf-v6ops-nd-considerations/ RFC7045 has a decent, and RFC2460 explains what they are but neither really have use cases. nb On Thu, May 18, 2023 at 9:33 AM Tom Herbert <tom=40herbertland.com@dmarc.ietf.org<mailto:40herbertland.com@dmarc.ietf.org>> wrote: On Thu, May 18, 2023 at 7:24 AM Andrew Campling <andrew.campling@419.consulting<mailto:andrew.campling@419.consulting>> wrote: > > I wonder if part of the issue here is that insufficient attention is being given to operational security matters and too much weight is given to privacy in protocol development, irrespective of the security implications (which is of course ultimately detrimental to security anyway)? Andrew, There is work being done to address the protocol "bugs" of extension headers. See 6man-hbh-processing and 6man-eh-limits for instance. Tom > > Andrew > > > From: OPSEC <opsec-bounces@ietf.org<mailto:opsec-bounces@ietf.org>> on behalf of Fernando Gont <fgont@si6networks.com<mailto:fgont@si6networks.com>> > Sent: Thursday, May 18, 2023 2:19 pm > To: David Farmer <farmer@umn.edu<mailto:farmer@umn.edu>>; Tom Herbert <tom=40herbertland.com@dmarc.ietf.org<mailto:40herbertland.com@dmarc.ietf.org>> > Cc: 6man@ietf.org<mailto:6man@ietf.org> <6man@ietf.org<mailto:6man@ietf.org>>; V6 Ops List <v6ops@ietf.org<mailto:v6ops@ietf.org>>; opsec WG <opsec@ietf.org<mailto:opsec@ietf.org>> > Subject: Re: [OPSEC] [IPv6] Why folks are blocking IPv6 extension headers? (Episode 1000 and counting) (Linux DoS) > > Hi, David, > > On 18/5/23 02:14, David Farmer wrote: > > > > > > On Wed, May 17, 2023 at 13:57 Tom Herbert > > <tom=40herbertland.com@dmarc.ietf.org<mailto:40herbertland.com@dmarc.ietf.org> > > <mailto:40herbertland.com@dmarc.ietf.org<mailto:40herbertland.com@dmarc.ietf.org>>> wrote: > [...] > > > > Maximum security is rarely the objective, I by no means have maximum > > security at my home. However, I don’t live in the country where some > > people still don’t even lock there doors. I live in a a city, I have > > decent deadbolt locks and I use them. > > > [....] > > > > So, I’m not really happy with the all or nothing approach the two of you > > seem to be offering for IPv6 extension headers, is there something in > > between? If not, then maybe that is what we need to be working towards. > > FWIW, I[m not arguing for a blank "block all", but rather "just allow > the ones you really need" -- which is a no brainer. The list you need > is, maybe Frag and, say, IPsec at the global level? (from the pov of > most orgs). > > (yeah... HbH and the like are mostly fine for the local link (e.g. MLD). > > Thanks, > -- > Fernando Gont > SI6 Networks > e-mail: fgont@si6networks.com<mailto:fgont@si6networks.com> > PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494 > > _______________________________________________ > OPSEC mailing list > OPSEC@ietf.org<mailto:OPSEC@ietf.org> > https://www.ietf.org/mailman/listinfo/opsec _______________________________________________ v6ops mailing list v6ops@ietf.org<mailto:v6ops@ietf.org> https://www.ietf.org/mailman/listinfo/v6ops _______________________________________________ v6ops mailing list v6ops@ietf.org<mailto:v6ops@ietf.org> https://www.ietf.org/mailman/listinfo/v6ops
- [IPv6] Why folks are blocking IPv6 extension head… Fernando Gont
- Re: [IPv6] Why folks are blocking IPv6 extension … Tom Herbert
- Re: [IPv6] Why folks are blocking IPv6 extension … Ted Lemon
- Re: [IPv6] Why folks are blocking IPv6 extension … David Farmer
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… nalini.elkins@insidethestack.com
- Re: [IPv6] Why folks are blocking IPv6 extension … Jen Linkova
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Vasilenko Eduard
- Re: [IPv6] Why folks are blocking IPv6 extension … Fernando Gont
- Re: [IPv6] Why folks are blocking IPv6 extension … Fernando Gont
- Re: [IPv6] Why folks are blocking IPv6 extension … Tom Herbert
- Re: [IPv6] [OPSEC] Why folks are blocking IPv6 ex… Andrew Campling
- Re: [IPv6] [OPSEC] Why folks are blocking IPv6 ex… Andrew Campling
- Re: [IPv6] Why folks are blocking IPv6 extension … Tom Herbert
- Re: [IPv6] [OPSEC] Why folks are blocking IPv6 ex… Tom Herbert
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Nick Buraglio
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… nalini.elkins@insidethestack.com
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Dale W. Carder
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Nick Buraglio
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Nick Buraglio
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Ackermann, Michael
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Xipengxiao
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Michael McBride
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Ackermann, Michael
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Fernando Gont
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Brian E Carpenter
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Ole Troan
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Haisheng Yu
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Andrew Campling
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Bob Natale
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Tom Herbert
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Ole Troan
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… nalini.elkins@insidethestack.com
- Re: [IPv6] [EXT] Re: [OPSEC] [v6ops] Why folks ar… Bob Natale
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… David Farmer
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… nalini.elkins@insidethestack.com
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Tom Herbert
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Michael Richardson
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Ole Trøan
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… nalini.elkins@insidethestack.com
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… David Farmer
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Ole Troan
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Tom Herbert
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Fernando Gont
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… nalini.elkins@insidethestack.com
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Tom Herbert
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… nalini.elkins@insidethestack.com
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Ole Troan
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Fernando Gont
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Fernando Gont
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Tom Herbert
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Tom Herbert
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Brian E Carpenter
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… Michael Richardson
- Re: [IPv6] [OPSEC] [v6ops] Why folks are blocking… Brian E Carpenter
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Brian E Carpenter
- Re: [IPv6] [v6ops] Why folks are blocking IPv6 ex… hsyu
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Fernando Gont
- Re: [IPv6] [EXTERNAL] Re: [v6ops] [OPSEC] Why fol… Manfredi (US), Albert E
- Re: [IPv6] [EXTERNAL] Re: [v6ops] [OPSEC] Why fol… Fernando Gont
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Arnaud Taddei
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Vasilenko Eduard
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Arnaud Taddei
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Vasilenko Eduard
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Arnaud Taddei
- Re: [IPv6] [v6ops] [OPSEC] [EXTERNAL] Re: Why fol… nalini.elkins@insidethestack.com
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Tom Herbert
- Re: [IPv6] [v6ops] [OPSEC] [EXTERNAL] Re: Why fol… Tom Herbert
- Re: [IPv6] [v6ops] [OPSEC] [EXTERNAL] Re: Why fol… nalini.elkins@insidethestack.com
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Manfredi (US), Albert E
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Tom Herbert
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Brian E Carpenter
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Manfredi (US), Albert E
- Re: [IPv6] [OPSEC] [v6ops] [EXTERNAL] Re: Why fol… Bob Natale
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Haisheng Yu
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Warren Kumari
- Re: [IPv6] [OPSEC] [v6ops] [EXTERNAL] Re: Why fol… Ole Troan
- Re: [IPv6] [OPSEC] [v6ops] [EXTERNAL] Re: Why fol… Warren Kumari
- Re: [IPv6] [OPSEC] [v6ops] [EXTERNAL] Re: Why fol… Andrew Campling
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Fernando Gont
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Fernando Gont
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Fernando Gont
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Fernando Gont
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Tom Herbert
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Tom Herbert
- Re: [IPv6] [OPSEC] [v6ops] [EXTERNAL] Re: Why fol… Tom Herbert
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Fernando Gont
- Re: [IPv6] [v6ops] [OPSEC] [EXTERNAL] Re: Why fol… Clark Gaylord
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Tom Herbert
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Fernando Gont
- Re: [IPv6] [EXTERNAL] Re: [v6ops] [OPSEC] Why fol… Manfredi (US), Albert E
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Brian E Carpenter
- Re: [IPv6] [OPSEC] [v6ops] [EXTERNAL] Re: Why fol… Brian E Carpenter
- Re: [IPv6] [EXTERNAL] Re: [v6ops] [OPSEC] Why fol… Tom Herbert
- Re: [IPv6] [EXTERNAL] Re: [v6ops] [OPSEC] Why fol… Manfredi (US), Albert E
- Re: [IPv6] [v6ops] [EXTERNAL] Re: [OPSEC] Why fol… Andrew Alston
- Re: [IPv6] [EXTERNAL] Re: [v6ops] [OPSEC] Why fol… Tom Herbert
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Andrew Campling
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Tom Herbert
- Re: [IPv6] [v6ops] [OPSEC] Why folks are blocking… Dirk Trossen
- Re: [IPv6] [EXTERNAL] Re: [v6ops] [OPSEC] Why fol… Mike Simpson
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Haisheng Yu
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Nick Hilliard
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Fernando Gont
- Re: [IPv6] [OPSEC] [EXTERNAL] Re: [v6ops] Why fol… Bob Natale