Re: [Int-area] comment on draft-ietf-intarea-gre-ipv6

Lucy yong <lucy.yong@huawei.com> Sun, 08 March 2015 17:05 UTC

Return-Path: <lucy.yong@huawei.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 A21581A004A for <int-area@ietfa.amsl.com>; Sun, 8 Mar 2015 10:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.511
X-Spam-Level:
X-Spam-Status: No, score=-1.511 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 g-ZoD_N7uC8a for <int-area@ietfa.amsl.com>; Sun, 8 Mar 2015 10:05:13 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 614C81A003B for <int-area@ietf.org>; Sun, 8 Mar 2015 10:05:12 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTK20385; Sun, 08 Mar 2015 17:05:09 +0000 (GMT)
Received: from DFWEML702-CHM.china.huawei.com (10.193.5.72) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 8 Mar 2015 17:05:08 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml702-chm ([10.193.5.72]) with mapi id 14.03.0158.001; Sun, 8 Mar 2015 10:04:59 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] comment on draft-ietf-intarea-gre-ipv6
Thread-Index: AdBXbdfY1u3rjZCDS1GBQOYYyX4bpAAET6LQAD8AzmAAUTgpQA==
Date: Sun, 08 Mar 2015 17:04:59 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D4545D18D@dfweml701-chm>
References: <CO1PR05MB442AAF3B29AE72283B8B5C0AE1F0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D4545C68A@dfweml701-chm> <2134F8430051B64F815C691A62D9831832E13D92@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832E13D92@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: [10.47.153.88]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-area/evDZ2Sv-UpRblRsRVO4FrNi4WLE>
Subject: Re: [Int-area] comment on draft-ietf-intarea-gre-ipv6
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: Sun, 08 Mar 2015 17:05:14 -0000

Hi Templin,


> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Lucy 
> yong
> Sent: Thursday, March 05, 2015 12:09 PM
> To: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] comment on draft-ietf-intarea-gre-ipv6
> 
> Hi Ron,
> 
> RFC2784 has this statement: See [RFC1122] for requirements relating to the
>    delivery of packets over IPv4 networks.
> Does this apply to over IPv6 networks?
> 
> Since IPv6 header does not have checksum, if a packet is mis-delivered 
> to GRE decapsulator, will that cause a concern? This is not a concern when IPv4 network is the delivery network.

In terms of header integrity checks, they are very much in the same boat as RFC2473.
But, somehow that got standardized.
[Lucy] RFC2473 is about IPv6 in IPv6, i.e., IPv6 as a delivery network for IPv6 traffic. Since IPv6 packets and upper layer applications have to follow RFC2460, i.e., protect the misdelivery and corruption, so that is OK if there is only such kind of tunnel in IPv6. GRE-in-IPv6 is deferent. They can't be in the same boat. If there are various network protocols that are tunneled over a same IPv6 network, it will have a problem due to packet misdelivery and corruption. IMO: the draft needs to document these.

Thanks,
Lucy 

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

> Thanks,
> Lucy
> 
> 
> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Thursday, March 05, 2015 11:57 AM
> To: int-area@ietf.org; Lucy yong
> Subject: RE: [Int-area] comment on draft-ietf-intarea-gre-ipv6
> 
> Hi Lucy,
> 
> The goal of this draft is *not* to prove the GRE behaves identically 
> with IPv6 as it does with IPv4. In fact, its goal is to point out the differences.
> 
> Can you think of any differences between the two GRE environments that we have failed to point out?
> 
>                                                                                                        
> Ron
> 
> 
> >
> > Message: 1
> > Date: Wed, 4 Mar 2015 15:25:54 +0000
> > From: Lucy yong <lucy.yong@huawei.com>
> > To: "int-area@ietf.org" <int-area@ietf.org>
> > Subject: [Int-area] comment on draft-ietf-intarea-gre-ipv6
> > Message-ID: <2691CE0099834E4A9C5044EEC662BB9D4545BB21@dfweml701-
> > chm>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Hi,
> >
> > If this draft is to document the protocol of gre in IPv6 exact same 
> > as of gre in
> > IPv4 and update rfc2784, IMHO, it should point out the gre 
> > application behavior differences in IPv4 network and IPv6 network. 
> > The exact same protocol does not mean the same behavior for an 
> > application since IPv4 and
> > IPv6 networks have different behaviors such as header checksum.
> >
> > Thanks,
> > Lucy
> >
> >
> >
> >
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area