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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 07 August 2015 16:44 UTC

Return-Path: <Fred.L.Templin@boeing.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 A56131A1AB8; Fri, 7 Aug 2015 09:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 lOzhoigjHVax; Fri, 7 Aug 2015 09:44:32 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (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 E841D1A1A96; Fri, 7 Aug 2015 09:44:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t77GiX1v012509; Fri, 7 Aug 2015 09:44:33 -0700
Received: from XCH-PHX-410.sw.nos.boeing.com (xch-phx-410.sw.nos.boeing.com [10.57.37.41]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t77GiOTg012298 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 7 Aug 2015 09:44:24 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.231]) by XCH-PHX-410.sw.nos.boeing.com ([169.254.10.48]) with mapi id 14.03.0235.001; Fri, 7 Aug 2015 09:44:22 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: The IESG <iesg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: I-D Action: draft-ietf-intarea-gre-ipv6-11.txt
Thread-Index: AQHQwqpZw9NZwERqrkiak9lnq7ne8J36fOYggAGKRqCABNOjkA==
Date: Fri, 07 Aug 2015 16:44:21 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832ED8851@XCH-BLV-504.nw.nos.boeing.com>
References: <20150720050935.12080.86522.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831832ED51E9@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: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-area/hjOIVn1WJo02Vy4d8EsXE5YMDOs>
Cc: "draft-ietf-intarea-gre-ipv6.ad@ietf.org" <draft-ietf-intarea-gre-ipv6.ad@ietf.org>, "draft-ietf-intarea-gre-ipv6@ietf.org" <draft-ietf-intarea-gre-ipv6@ietf.org>, "draft-ietf-intarea-gre-ipv6.shepherd@ietf.org" <draft-ietf-intarea-gre-ipv6.shepherd@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@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 16:44:34 -0000

Hi, this comment has not been acknowledged nor addressed. Please acknowledge
and address.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Templin, Fred L
> Sent: Monday, August 03, 2015 9:07 AM
> To: int-area@ietf.org
> Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-gre-ipv6-11.txt
> 
> 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.
> 
> 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