IETF Logo Mail Archive

Re: [Int-area] Document shepherd comments on 'draft-ietf-intarea-gue-05'

Joe Touch <touch@strayalpha.com> Sat, 01 September 2018 18:02 UTC

Return-Path: <touch@strayalpha.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 C4155130E25 for <int-area@ietfa.amsl.com>; Sat, 1 Sep 2018 11:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 KBoCuI3qyEie for <int-area@ietfa.amsl.com>; Sat, 1 Sep 2018 11:02:42 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 DB84312F295 for <Int-area@ietf.org>; Sat, 1 Sep 2018 11:02:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ka+pCbckCyPBRqYAfIDSZF3OwcrOz5U3fegwCEg9yR0=; b=hppJ6ubJGlJM6P9c0Swu7+bQt YMF96NyBmfYEfOYzZWNUcgQ2Ib7W1hj24GirKcwrG6MrxRfewUDlw7aZE+HPvExpqgWZqiBl5M16J wPaP3Gywt/SP8ptrVxFT0Eu4nEvMoK8d0a4CT99mtakIF555OLlPHHxKY814PlItHrShY7fmGJU4m c4CXphE3AAAq53rTPSwBcLd90ZLjOg/JtmRD/BAQcYLbJp13zlFVKFMHORz8P7Ltlko1UM6c4ILLX ptyiatj2fNFyFa0tYYUBt9u2z6zuPOb2aW/Nz76LZcCTFSOH32m/8T6idpNiKUSGpB1qlSmt3o8Vd PfRwekT7w==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:63499 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <touch@strayalpha.com>) id 1fwAEJ-000RSu-De; Sat, 01 Sep 2018 14:02:40 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_D881512C-2711-4E8F-BBEF-892F7BBB0A23"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <CALx6S359UhJuMVGZqb2GmyY23-R9NCtYcXHsk-LhhRJOEXPMhw@mail.gmail.com>
Date: Sat, 1 Sep 2018 11:02:36 -0700
Cc: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, "Int-area@ietf.org" <Int-area@ietf.org>
Message-Id: <2CDF8546-74DC-464E-91D3-FE58DA615620@strayalpha.com>
References: <f1cf017dec464a8c8d2cd0dc3e6d60db@XCH15-06-08.nw.nos.boeing.com> <CALx6S378juGPjuM0eB=tG8GizJ+5tnY8n6Zr+buKvY=469KbeA@mail.gmail.com> <b3bdd6ff7ec94dbda572a49eb1e019d8@XCH15-06-08.nw.nos.boeing.com> <5f0785d6-3a3e-6df7-9b82-989fd4f78219@strayalpha.com> <CALx6S359UhJuMVGZqb2GmyY23-R9NCtYcXHsk-LhhRJOEXPMhw@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/vMXXcAZX4EhiVzRrt5oHk0f6Aqk>
Subject: Re: [Int-area] Document shepherd comments on 'draft-ietf-intarea-gue-05'
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.27
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: Sat, 01 Sep 2018 18:02:45 -0000


> On Sep 1, 2018, at 11:00 AM, Tom Herbert <tom@herbertland.com> wrote:
> 
>> FWIW, IP fragmentation copies the IP header in each fragment because that
>> field is part of the context for the ID field; i.e., ID MUST be unique
>> within src/dst/proto. If fragments had a different proto field, it would
>> undermine that context.
>> 
> Hi Joe,
> 
> The GUE fragmentation option includes a orig-proto field to hold the
> protocol of the reassembled packet. That needs to be matched in all
> fragments along with srd/dst and ID, Also the protocol field in the
> GUE header of the first fragment must also match. So the ID space is
> basically defined the same way as IP fragmentation.

Understood - I was explaining why IP couldn’t use “no next proto” in the next proto field.

Joe

v2.2.0 | Report a Bug | By Email