Re: [trill] Fwd: Mail regarding draft-ietf-trill-over-ip

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 05 May 2015 18:47 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E5F41A87EC; Tue, 5 May 2015 11:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 dBjcRvRkfLqx; Tue, 5 May 2015 11:47:39 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 D72B71A873E; Tue, 5 May 2015 11:47:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t45IlZag022360; Tue, 5 May 2015 11:47:35 -0700
Received: from XCH-BLV-108.nw.nos.boeing.com (xch-blv-108.nw.nos.boeing.com [130.247.25.137]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t45IlVU7022338 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 5 May 2015 11:47:31 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.120]) by XCH-BLV-108.nw.nos.boeing.com ([169.254.13.118]) with mapi id 14.03.0235.001; Tue, 5 May 2015 11:47:31 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, Xuxiaohu <xuxiaohu@huawei.com>, Donald Eastlake <d3e3e3@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] Fwd: Mail regarding draft-ietf-trill-over-ip
Thread-Index: AQHQhDAejJGxDIiBx0S2BZ0ZWLGtWJ1nAPgAgAQl8XCAAFTXgIABIiUAgADgFUCAAJHXAP//i4BggACKdAD//4xEMIAAfNmA//+PG6A=
Date: Tue, 05 May 2015 18:47:30 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E5AC5F@XCH-BLV-504.nw.nos.boeing.com>
References: <4552F0907735844E9204A62BBDD325E76ABADC85@nkgeml512-mbx.china.huawei.com> <CAF4+nEHSGYa+1DHzwee+RNgkXfZra_Pa9706vqpTGJV71SmDaw@mail.gmail.com> <CAF4+nEFcUL2ieQKCm98_0XxfrrAR0M11irVFfOfqa=92OM1V=A@mail.gmail.com> <5543D870.6080108@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0832A468@NKGEML512-MBS.china.huawei.com> <55479A6D.2040403@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0832A7B7@NKGEML512-MBS.china.huawei.com> <2134F8430051B64F815C691A62D9831832E5A834@XCH-BLV-504.nw.nos.boeing.com> <5548F132.7050704@isi.edu> <2134F8430051B64F815C691A62D9831832E5A90F@XCH-BLV-504.nw.nos.boeing.com> <5549039C.2020709@isi.edu> <2134F8430051B64F815C691A62D9831832E5ABBE@XCH-BLV-504.nw.nos.boeing.com> <55490B41.2000207@isi.edu>
In-Reply-To: <55490B41.2000207@isi.edu>
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/trill/cLR714ye89-OjQRH7Tgx-f3lUa0>
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [trill] Fwd: Mail regarding draft-ietf-trill-over-ip
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2015 18:47:41 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, May 05, 2015 11:26 AM
> To: Templin, Fred L; Xuxiaohu; Donald Eastlake; trill@ietf.org
> Cc: nvo3@ietf.org; int-area@ietf.org; sfc@ietf.org
> Subject: Re: [trill] Fwd: Mail regarding draft-ietf-trill-over-ip
> 
> 
> 
> On 5/5/2015 11:04 AM, Templin, Fred L wrote:
> > Hi Joe,
> >
> >> -----Original Message-----
> >> From: Joe Touch [mailto:touch@isi.edu]
> >> Sent: Tuesday, May 05, 2015 10:54 AM
> >> To: Templin, Fred L; Xuxiaohu; Donald Eastlake; trill@ietf.org
> >> Cc: nvo3@ietf.org; int-area@ietf.org; sfc@ietf.org
> >> Subject: Re: [trill] Fwd: Mail regarding draft-ietf-trill-over-ip
> >>
> >>
> >>
> >> On 5/5/2015 9:39 AM, Templin, Fred L wrote:
> >>> Hi Joe,
> >> ..
> >>>> IP in UDP adds only port numbers and an Internet checksum.
> >>>>
> >>>> That doesn't address fragmentation; if outer fragmentation is assumed,
> >>>> IPv4 needs to be rate-limited to avoid ID collisions and the Internet
> >>>> checksum is insufficient to correct those collisions.
> >>>
> >>> Right - that is why we have GUE. But, when these functions are not
> >>> needed GUE can perform header compression and the result looks
> >>> exactly like IP in UDP.
> >>
> >> That seems impossible.
> >
> > Not impossible - Tom Herbert provided the solution:
> >
> > http://www.ietf.org/mail-archive/web/int-area/current/msg04593.html
> 
> That is allocating bits (or bit patterns) from the IP header.
> 
> The solution provided - to check for 0x01 - is incorrect. IP can have
> versions that include 0x10 and 0x11.

The version field in both IPv4 and IPv6 have that bit set to 1. If GUE
then deems that bit to indicate "direct IP encapsulation, then there
is no need for a GUE header of length greater than 0.

You may say that future IP protocol versions might not have that bit
set in the version field. But, the version bits for IPv4 and IPv6 will
never change (by definition) and we do not see a new IP protocol
version replacing IPv4 or IPv6 on the near-term horizon.

Even if a new IP protocol version emerged with the "direct IP
encapsulation" bit set to 0, that version can still be accommodated
by GUE. It's just that direct encapsulation cannot be used and a
non-zero-length GUE header is needed.

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

> The only solution would be to say that if the first three bits were 0,
> then it's not an IP packet - but that would require reassigning 0x0000
> and 0x0001 for GUE purposes.
> 
> Although that's possible, I don't see why we would allocate IP versions
> to GUE message types.
> 
> Joe