Re: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03
Tom Herbert <tom@herbertland.com> Wed, 01 June 2016 23:57 UTC
Return-Path: <tom@herbertland.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B219F12D573 for <int-area@ietfa.amsl.com>; Wed, 1 Jun 2016 16:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 O4XNVHMBn_qZ for <int-area@ietfa.amsl.com>; Wed, 1 Jun 2016 16:57:15 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC36212D125 for <int-area@ietf.org>; Wed, 1 Jun 2016 16:57:15 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id i127so37839349ita.1 for <int-area@ietf.org>; Wed, 01 Jun 2016 16:57:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=nIvjDx+qZm6etHnPyTP62O7KH+onb0qLCZEUb4MTS1E=; b=nJvnyWicrHosJ9Aqzg9Xg3CMDNN3Hjg6NKVrJJ+7XTy8XenIODuHy55olE5ngEuthj gshob77hn1QRn44h+4/N67+2HN1/+w4RIOYg/H3c807LZXvnkkNFaOAIQZ1nfWPEfReF Hc14QlfkFax0cJcMpQs4NjjhzctrA/gwdm1ufoxka+BrtEeGsq08anspLUWt3yUj55k9 hNzDIeuvE28/HBoREED2CUMnvwjLs4UcTWVHLxt4L65M9Lz3jbjMfwphFhezohQTsBox FWXHt0conjA/RZSGTQjB09pgmFDUD/Swub9A0GGhQ8fyT98LdR0a7NsrY+3crBX3GLrB 1UrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=nIvjDx+qZm6etHnPyTP62O7KH+onb0qLCZEUb4MTS1E=; b=VqEg0XZPX1Tb8hbkmHrhDIKxKSFzRfqDL5OuGsG02H9jRE80CnIuFDSuo0TYvtxk2j omiHvzD5EttDGS5jyJ7+MfsmpnwlNoF4ku7yrZpFRCqLTK9HT1zEyeYNotMW1/eXCRXZ hNzc7DrzMgKZJ9iC03c9MLMknZtp5qfm9vJDBVG601eM/PTPOdxIM/Xtp54ozlNaW9OU Dx5rG8SLB4uib8M5SdI5jYcQnMDhlIa9hVh0BS/u7iSmhTaHHMhZt0fmzTTw7MhUpkPr O0xrP9Z2t3uuvxF5s5xu8cdxPWscwSUykQeuX5ac66NmOx6ZyYY4J3BeNqwe2B0wV6dj aoQg==
X-Gm-Message-State: ALyK8tIoRSd6CLMQ9VSDGe83/vGz06ZV9g4MuIi3ay5EVFhh5GIjm7DqbcquSVPCoijRjEjTizgvYq8UVOFM7Q==
MIME-Version: 1.0
X-Received: by 10.36.80.4 with SMTP id m4mr598923itb.37.1464825434946; Wed, 01 Jun 2016 16:57:14 -0700 (PDT)
Received: by 10.107.44.203 with HTTP; Wed, 1 Jun 2016 16:57:14 -0700 (PDT)
In-Reply-To: <574F7170.2050407@isi.edu>
References: <E83B905A-FF6D-4996-B71A-7921DE4B133B@ericsson.com> <BFC09F5C-D6DF-4B6B-AA95-03919B9F09FB@cisco.com> <573E2A0E.1060609@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D54EB60@NKGEML515-MBX.china.huawei.com> <573F453C.5060908@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D554B73@NKGEML515-MBS.china.huawei.com> <5743303C.5040109@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55514C@NKGEML515-MBS.china.huawei.com> <5743DD16.3050506@isi.edu> <e523724c-cffd-784d-0147-aa64c2787727@bogus.com> <574C8288.7080804@isi.edu> <bd97158e-b6f1-5e55-af9a-07eca2660479@gmail.com> <574DAECA.4050504@isi.edu> <1f6335981e714befab009d45ecb99ee4@XCH15-05-05.nw.nos.boeing.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D55A571@NKGEML515-MBS.china.huawei.com> <79d394e71ee349cca666aa3c8b60ad3b@XCH15-05-05.nw.nos.boeing.com> <574F7170.2050407@isi.edu>
Date: Wed, 01 Jun 2016 16:57:14 -0700
Message-ID: <CALx6S36Jotc1KSJs8YzA3-JUX_9s5i7eg24kVnuv6UYtYJKt8A@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-area/J-WtfGAI3cXQHTsEUPSu7v3_epg>
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] Call for adoption of draft-xu-intarea-ip-in-udp-03
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Jun 2016 23:57:18 -0000
On Wed, Jun 1, 2016 at 4:36 PM, Joe Touch <touch@isi.edu> wrote: > > > On 6/1/2016 3:50 PM, Templin, Fred L wrote: >> Any tunnel that traverses a 1280 link has to fragment, but instead of outer fragmentation >> it should use tunnel fragmentation which is something I have been advocating for a very >> long time. The tunnel egress should configure at least a 2KB reassembly buffer size. > > If the only layer you have that fragments is the outermost IP, that's > where you MUST do it. > > Sure, if you can fragment at an intermediate "transport" layer inside of > IP, that's also an option. I'm not sure why it should be preferred > except for the flaws of current equipment in supporting standards, though. > We defined fragmentation option in GUE (draft-herbert-gue-fragmentation-02). The listed benefits are: o A 32 bit identifier can be defined to avoid issues of the 16 bit Identification in IPv4. o Encapsulation mechanisms for security and identification such as virtual network identifiers can be applied to each segment. o This allows the possibility of using alternate fragmentation and reassembly algorithms (e.g. fragmentation with Forward Error Correction). o Fragmentation is transparent to the underlying network so it is unlikely that fragmented packet will be unconditionally dropped as might happen with IP fragmentation. We should probably add that all fragments will have the same outer addresses and UDP ports in the encapsulation so it is likely that all the fragments will follow the same path. Security means that we can cover fragmentation information with checksum or stronger integrity checks. This option probably only makes use of fragmentation a little more palatable, but doesn't change the fact that it's better to avoid having to fragment in the first place if at all possible ;-). Tom > Joe > > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://www.ietf.org/mailman/listinfo/int-area
- Re: [Int-area] Call for adoption of draft-xu-inta… Wassim Haddad
- Re: [Int-area] [tsvwg] Is it feasible to perform … Joe Touch
- [Int-area] Call for adoption of draft-xu-intarea-… Wassim Haddad
- Re: [Int-area] Call for adoption of draft-xu-inta… Fred Baker (fred)
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Brian E Carpenter
- Re: [Int-area] Call for adoption of draft-xu-inta… Carlos Pignataro (cpignata)
- Re: [Int-area] Call for adoption of draft-xu-inta… Brian E Carpenter
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Alexandre Petrescu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Ted Lemon
- Re: [Int-area] Call for adoption of draft-xu-inta… Black, David
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- [Int-area] Is it feasible to perform fragmentatio… Xuxiaohu
- Re: [Int-area] [Softwires] Is it feasible to perf… otroan
- Re: [Int-area] Is it feasible to perform fragment… Tom Herbert
- Re: [Int-area] [lisp] [Softwires] Is it feasible … Xuxiaohu
- Re: [Int-area] Is it feasible to perform fragment… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Carlos Pignataro (cpignata)
- Re: [Int-area] Call for adoption of draft-xu-inta… joel jaeggli
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Carlos Pignataro (cpignata)
- Re: [Int-area] Is it feasible to perform fragment… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Brian E Carpenter
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Black, David
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Brian E Carpenter
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Brian E Carpenter
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Brian E Carpenter
- Re: [Int-area] Call for adoption of draft-xu-inta… Templin, Fred L
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Tom Herbert
- Re: [Int-area] Call for adoption of draft-xu-inta… Joe Touch
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] Call for adoption of draft-xu-inta… Xuxiaohu
- Re: [Int-area] [nvo3] [Softwires] Is it feasible … Joe Touch
- Re: [Int-area] [nvo3] [Softwires] Is it feasible … Templin, Fred L
- Re: [Int-area] [nvo3] [Softwires] Is it feasible … Xuxiaohu
- Re: [Int-area] [nvo3] [Softwires] Is it feasible … Joe Touch
- Re: [Int-area] [nvo3] [Softwires] Is it feasible … Xuxiaohu
- Re: [Int-area] [Softwires] [nvo3] Is it feasible … Rémi Després
- Re: [Int-area] [nvo3] [Softwires] Is it feasible … Templin, Fred L
- Re: [Int-area] [nvo3] [Softwires] Is it feasible … Tom Herbert
- Re: [Int-area] [tsvwg] [nvo3] [Softwires] Is it f… Templin, Fred L
- Re: [Int-area] [tsvwg] Is it feasible to perform … Lloyd Wood
- Re: [Int-area] [nvo3] [tsvwg] Is it feasible to p… Saumya Dikshit (sadikshi)
- Re: [Int-area] [tsvwg] Is it feasible to perform … Tom Herbert