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

Xuxiaohu <xuxiaohu@huawei.com> Wed, 06 May 2015 02:46 UTC

Return-Path: <xuxiaohu@huawei.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 EF8B61B2A4C; Tue, 5 May 2015 19:46:40 -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 oUcOKyjmMR4h; Tue, 5 May 2015 19:46:39 -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 755631B2A49; Tue, 5 May 2015 19:46:38 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BVS04898; Wed, 06 May 2015 02:46:36 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 6 May 2015 03:46:36 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Wed, 6 May 2015 10:46:32 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Joe Touch <touch@isi.edu>, Tom Herbert <tom@herbertland.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
Thread-Topic: [trill] Fwd: Mail regarding draft-ietf-trill-over-ip
Thread-Index: AQHQhDAYoLZIFwke90qEGncpXxc1v51nAPgAgAQl8XCAAFTXgIABIiUAgABaUYCAABwmAIAAAU+AgAAUpQCAAAMpgIAABfSAgAAF9wCAAAGigIAAC4GAgAAB94CAAPvFMA==
Date: Wed, 6 May 2015 02:46:32 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0832ABC2@NKGEML512-MBS.china.huawei.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> <2134F8430051B64F815C691A62D9831832E5AC5F@XCH-BLV-504.nw.nos.boeing.com> <CALx6S35nHEMvaSNis_uPQ6t4rm2NSzFN2Jzoo8WaXj04RdH3NQ@mail.gmail.com> <55491B47.4060400@isi.edu> <55491CED.5070505@isi.edu>
In-Reply-To: <55491CED.5070505@isi.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/A1kmFqmkhUsUrpEaZq14tkurPAM>
Cc: Donald Eastlake <d3e3e3@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, "trill@ietf.org" <trill@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: Wed, 06 May 2015 02:46:41 -0000


> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Wednesday, May 06, 2015 3:42 AM
> To: Tom Herbert; Templin, Fred L
> Cc: Xuxiaohu; Donald Eastlake; trill@ietf.org; 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 12:34 PM, Joe Touch wrote:
> >> Or just define a simple version translation as part of encapsulation.
> >> > So for IPv8:
> >> >
> >> > 0x1000->0x0101 on encapsulation
> >> > 0x0101->0x1000 on decapsualtion
> > And what happens to 0x0101 WHEN it shows up?
> >
> > You need more patterns than you have because IP is allowed to use any
> > of them.
> 
> FWIW, you're essentially arguing for bit-stuffing, i.e., if a pattern you think will
> be common shows up, don't stuff, and if something else shows up, then do.
> 
> That works only if you do true stuffing, e.g.,:
> 
> 	0x01** = uncompressed
> (might as well add 0x11** and 0x10** to that)
> 	0x00** = compressed
> 
> But then if 0x0000, 0x0001, 0x0010 or 0x0011 show up, you need to decide
> how to represent them - they CANNOT be uncompressed without at least two
> more bits somewhere else that indicates they're uncompressed and their value.
> 
> So now your GUE methods are very sensitive to IP version numbers, which IMO
> defeats the "G" in the name. Never mind how this complicates hardware when

Agree. As I had mentioned to Tom in private, I do believe the additional capability of GUE (e.g., fragmentation) would be much useful in some network environments. However, since GUE is intended to be a generic UDP encapsulation approach, we'd better design it as generic and future-proof as possible from the beginning, specifically speaking, without being deeply influenced by a particular GUE payload type. If both foo-in-GUE (foo could be NSH, TRILL...) and foo-in-UDP (i.e., a compact version of foo-in-GUE) are needed someday, could you still achieve the same effect as that for IP-in-UDP (as a compact IP-in-GUE) and IP-in-GUE?

Best regards,
Xiaohu

> (not if) other IP versions are used (for whatever reason).
> 
> Joe
> 
>