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

Joe Touch <touch@isi.edu> Tue, 05 May 2015 19:30 UTC

Return-Path: <touch@isi.edu>
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 C51981A87BD; Tue, 5 May 2015 12:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 x0ibCGa_o6J4; Tue, 5 May 2015 12:30:56 -0700 (PDT)
Received: from mail-b.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA7321A873D; Tue, 5 May 2015 12:30:38 -0700 (PDT)
Received: from [169.228.177.133] ([169.228.177.133]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t45JTSHG004607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 5 May 2015 12:29:37 -0700 (PDT)
Message-ID: <55491A18.6080309@isi.edu>
Date: Tue, 05 May 2015 12:29:28 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Tom Herbert <tom@herbertland.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> <CALx6S36mkn6jR-CTDJAcUjp3xB4TkHYpw3_kA865rWzdzNsMgw@mail.gmail.com>
In-Reply-To: <CALx6S36mkn6jR-CTDJAcUjp3xB4TkHYpw3_kA865rWzdzNsMgw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/2I-Fs_YCtIPszbVC8VYRP3sLAJ8>
Cc: "int-area@ietf.org" <int-area@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "trill@ietf.org" <trill@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>, Xuxiaohu <xuxiaohu@huawei.com>
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 19:30:57 -0000


On 5/5/2015 11:45 AM, Tom Herbert wrote:
>> > The solution provided - to check for 0x01 - is incorrect. IP can have
>> > versions that include 0x10 and 0x11.
>> >
> It is correct as we defined it-- this is a solution to support direct
> encapsulation of only IPv4 and IPv6. This optimizes encapsulation
> those two IP protocols, and does not effect encapsulation of other
> protocols (including new versions of IP) using the GUE and header and
> protocol field. Whether this optimization is worth it is a fair
> question, but if this obviates the need for a separate port number in
> UDP-IP maybe it would be.
> 
>> > 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.
>> >
> We're not proposing that at all.

Then the solution is incorrect. As noted above, if you don't know you
"own" the patterns, you don't know you can use them to indicate
"non-compressed GUE header" because they are valid uncompressed IP packets.

A field you don't reserve isn't yours to assume.

Joe