Re: [Int-area] Kathleen Moriarty's Discuss on draft-ietf-intarea-gre-mtu-04: (with DISCUSS)

Ronald Bonica <rbonica@juniper.net> Thu, 14 May 2015 03:39 UTC

Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 228111B32E8; Wed, 13 May 2015 20:39:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level:
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BRrMBD4PQl3d; Wed, 13 May 2015 20:39:36 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0797.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::797]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78F7F1B32E5; Wed, 13 May 2015 20:39:27 -0700 (PDT)
Received: from CY1PR05MB1996.namprd05.prod.outlook.com (25.162.216.30) by CY1PR05MB1946.namprd05.prod.outlook.com (25.162.216.16) with Microsoft SMTP Server (TLS) id 15.1.160.19; Thu, 14 May 2015 03:39:07 +0000
Received: from CY1PR05MB1994.namprd05.prod.outlook.com (25.162.216.28) by CY1PR05MB1996.namprd05.prod.outlook.com (25.162.216.30) with Microsoft SMTP Server (TLS) id 15.1.154.19; Thu, 14 May 2015 03:39:06 +0000
Received: from CY1PR05MB1994.namprd05.prod.outlook.com ([25.162.216.28]) by CY1PR05MB1994.namprd05.prod.outlook.com ([25.162.216.28]) with mapi id 15.01.0154.018; Thu, 14 May 2015 03:39:06 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>, The IESG <iesg@ietf.org>
Thread-Topic: Kathleen Moriarty's Discuss on draft-ietf-intarea-gre-mtu-04: (with DISCUSS)
Thread-Index: AQHQjeuraQWLl4q6nUqMr+wRYH60Tp16zpYQ
Date: Thu, 14 May 2015 03:39:05 +0000
Message-ID: <CY1PR05MB1994819D2EC000754D69ACFDAED80@CY1PR05MB1994.namprd05.prod.outlook.com>
References: <20150514021405.29892.21704.idtracker@ietfa.amsl.com>
In-Reply-To: <20150514021405.29892.21704.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-originating-ip: [66.129.241.14]
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:CY1PR05MB1996; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:CY1PR05MB1946;
x-microsoft-antispam-prvs: <CY1PR05MB1996700F069CEF017789E5A7AED80@CY1PR05MB1996.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:CY1PR05MB1996; BCL:0; PCL:0; RULEID:; SRVR:CY1PR05MB1996;
x-forefront-prvs: 0576145E86
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(51704005)(57704003)(13464003)(377454003)(52044002)(106116001)(2900100001)(2950100001)(15975445007)(102836002)(62966003)(77156002)(40100003)(122556002)(19580405001)(19580395003)(5001960100002)(5001770100001)(74316001)(76576001)(92566002)(189998001)(230783001)(87936001)(2656002)(50986999)(54356999)(76176999)(66066001)(86362001)(46102003)(33656002)(99286002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR05MB1996; H:CY1PR05MB1994.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 May 2015 03:39:05.7938 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR05MB1996
X-OriginatorOrg: juniper.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-area/F7Cfi17c-wrMIpNKSZZxZ53fq2k>
Cc: "draft-ietf-intarea-gre-mtu@ietf.org" <draft-ietf-intarea-gre-mtu@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "draft-ietf-intarea-gre-mtu.ad@ietf.org" <draft-ietf-intarea-gre-mtu.ad@ietf.org>, "draft-ietf-intarea-gre-mtu.shepherd@ietf.org" <draft-ietf-intarea-gre-mtu.shepherd@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Subject: Re: [Int-area] Kathleen Moriarty's Discuss on draft-ietf-intarea-gre-mtu-04: (with DISCUSS)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2015 03:39:39 -0000

Kathleen,

AFAIK, most IP stacks include code that detects fragmentation overlap attacks. (Do I have that right?)

So, reassembly attacks shouldn't be effective whether reassembly is performed at the GRE egress or the ultimate destination.

If reassembly is performed at the ultimate destination, the two endpoints might be alerted. However, if reassembly is performed at the GRE ingress, the endpoints might never be alerted.

Should we add a paragraph about this in Section 5 (Security Considerations). Or is this just another type of DoS attack, which we have already mentioned?

                                                                                                        Ron


> -----Original Message-----
> From: Kathleen Moriarty [mailto:Kathleen.Moriarty.ietf@gmail.com]
> Sent: Wednesday, May 13, 2015 10:14 PM
> To: The IESG
> Cc: draft-ietf-intarea-gre-mtu@ietf.org; draft-ietf-intarea-gre-
> mtu.ad@ietf.org; suresh.krishnan@ericsson.com; draft-ietf-intarea-gre-
> mtu.shepherd@ietf.org; intarea-chairs@ietf.org; int-area@ietf.org
> Subject: Kathleen Moriarty's Discuss on draft-ietf-intarea-gre-mtu-04: (with
> DISCUSS)
> 
> Kathleen Moriarty has entered the following ballot position for
> draft-ietf-intarea-gre-mtu-04: Discuss
> 
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-intarea-gre-mtu/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Thanks for your work on this draft, I have a question I'd like to discuss to see
> if another security consideration needs to be added.  This should be very
> quick to resolve.
> 
> Do we need to worry about fragmentation overlap attacks when packets are
> reassembled?  I see that you would not have to worry about it in cases
> where fragmentation is handled at a different layer as is the case with some
> of the methods as it might be addressed at that layer.  Or does it not matter
> as the reassembled packets would be forwarded and the device
> reassembling wouldn't be processing the payload where an exploit could
> avoid detection?
> 
> 
>