Re: [Int-area] I-D Action: draft-ietf-intarea-gre-ipv6-11.txt

Tom Herbert <tom@herbertland.com> Fri, 07 August 2015 17:04 UTC

Return-Path: <tom@herbertland.com>
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 4C8E31B3041 for <int-area@ietfa.amsl.com>; Fri, 7 Aug 2015 10:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 5f0vobKxbJNm for <int-area@ietfa.amsl.com>; Fri, 7 Aug 2015 10:04:21 -0700 (PDT)
Received: from mail-io0-f175.google.com (mail-io0-f175.google.com [209.85.223.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C94981A8823 for <int-area@ietf.org>; Fri, 7 Aug 2015 10:04:19 -0700 (PDT)
Received: by iodb91 with SMTP id b91so57689592iod.1 for <int-area@ietf.org>; Fri, 07 Aug 2015 10:04:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=QKgHVNYk3bvIxEB5rTdtlOb2DEB9xEcIq9yjBuuc+QE=; b=kR+JtdcDyQpA4HTa4FavokUqPog2PfLSqz5hosO1W1gonJvCA7YGzhmuAZLjhF5WQH txxzeegkDF1bshGWZhdBBEBfDLNwVTAHmRRGttm0nRApzeNmASun73tRZISE6UZ+ejvG 5Z2MA/lAxQi1xoPdnKdf2bBmr8jH9XuKM4sa32mGSSKQXa4a8Lu1kaPqfLCM4225HWeh uLgkFoTBF3C0HOX+NnLuiv6nbbOQc96HmxGHOl3r/Z5tL+n2He2+y+8Vp5qfKqvPYdw7 0R//LJhI9tvHhTYQcauh5zzF3RKwkQ1SDpr5IE2whQztfnj/Wg4T/E7/JKUkD3XoaGes 5UMg==
X-Gm-Message-State: ALoCoQmWFX0R4pRfdBX7oVTxkhRPAN8mIjOsBly7bsvt/WQSAXkKMRWFJriqa7pFtByqya9iBVZN
MIME-Version: 1.0
X-Received: by 10.107.170.77 with SMTP id t74mr10092678ioe.107.1438967059222; Fri, 07 Aug 2015 10:04:19 -0700 (PDT)
Received: by 10.107.200.195 with HTTP; Fri, 7 Aug 2015 10:04:19 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831832ED51E9@XCH-BLV-504.nw.nos.boeing.com>
References: <20150720050935.12080.86522.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831832ED51E9@XCH-BLV-504.nw.nos.boeing.com>
Date: Fri, 07 Aug 2015 10:04:19 -0700
Message-ID: <CALx6S36otezy0D_ft=uCMWQx3MY+Rd9+ypn2A1WWxJsrVhnJTQ@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-area/Q-21L9AhheAB10Nwi2sfzI-JkJA>
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-gre-ipv6-11.txt
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 07 Aug 2015 17:04:23 -0000

On Mon, Aug 3, 2015 at 9:07 AM, Templin, Fred L
<Fred.L.Templin@boeing.com> wrote:
> I have a comment on this draft. In Section 3.2, it says:
>
>   "However, a GRE ingress node can verify tunnel capabilities by sending
>    a 1280-byte IPv6 packet addressed to itself through the tunnel under test."
>
> This text is missing the point that the GRE ingress is only the source of
> the delivery packet and is *not* the source of the payload packet.
> This means that, if the 1280-byte probe packets take a different path
> than the data packets, then the probes can fail to detect paths where
> the MTU is insufficient.
>
> In order to fix this, the GRE ingress would need to make all delivery
> packets look the same to the network whether they carry probes
> or data packets. This means that the procedures specified in  RFC2983
> (diffserv and tunnels) and RFC6438 (flow label and tunnels) MUST be
> disabled if the 1280 byte probing recommendation of this draft is
> followed. By disabled, I mean set the DSCP and flow label in the
> delivery header to 0. The draft can either say this and cite the RFCs,
> or remove the recommendation for probing with 1280 byte probes.
>
Fred,

I don't think your fix is sufficient. There are already deployed
devices that will parse the inner GRE headers to perform ECMP.
Generally, we can never guarantee that any two packets will follow the
same path through a multi-path network, and simultaneously testing all
possible paths is a known hard problem.

Tom

> Thanks - Fred
> fred.l.templin@boeing.com
>
>> -----Original Message-----
>> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
>> Sent: Sunday, July 19, 2015 10:10 PM
>> To: i-d-announce@ietf.org
>> Cc: int-area@ietf.org
>> Subject: I-D Action: draft-ietf-intarea-gre-ipv6-11.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>  This draft is a work item of the Internet Area Working Group Working Group of the IETF.
>>
>>         Title           : IPv6 Support for Generic Routing Encapsulation (GRE)
>>         Authors         : Carlos Pignataro
>>                           Ron Bonica
>>                           Suresh Krishnan
>>       Filename        : draft-ietf-intarea-gre-ipv6-11.txt
>>       Pages           : 10
>>       Date            : 2015-07-19
>>
>> Abstract:
>>    Generic Routing Encapsulation (GRE) can be used to carry any network-
>>    layer payload protocol over any network-layer delivery protocol.  GRE
>>    procedures are specified for IPv4, used as either the payload or
>>    delivery protocol.  However, GRE procedures are not specified for
>>    IPv6.
>>
>>    This document specifies GRE procedures for IPv6, used as either the
>>    payload or delivery protocol.  It updates the GRE specification, RFC
>>    2784.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-intarea-gre-ipv6/
>>
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-intarea-gre-ipv6-11
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-intarea-gre-ipv6-11
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area