[Int-area] Intdir early review of draft-ietf-intarea-gue-06
Charles Perkins <charliep@computer.org> Fri, 01 March 2019 03:00 UTC
Return-Path: <charliep@computer.org>
X-Original-To: int-area@ietf.org
Delivered-To: int-area@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BE935131154; Thu, 28 Feb 2019 19:00:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Charles Perkins <charliep@computer.org>
To: int-dir@ietf.org
Cc: draft-ietf-intarea-gue.all@ietf.org, int-area@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.92.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155140924774.28748.6386974495312667803@ietfa.amsl.com>
Date: Thu, 28 Feb 2019 19:00:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/9k6QKsfb5WatzWflzBZfiLRLjNs>
Subject: [Int-area] Intdir early review of draft-ietf-intarea-gue-06
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 01 Mar 2019 03:00:48 -0000
Reviewer: Charles Perkins Review result: Almost Ready This document needs an applicability statement which includes the assumptions and the reasons it might be useful. Deliverability needs to be expanded. Reasons why middleboxes would be unlikely inspect GUE fields might be included. For instance, the discussion in second paragraph of 5.11.1 belongs in the applicability statement. It should also be explained why arbitrary GUE extensions are less likely to be filtered out compared to IPv6 destination options. ============================================== The document assumes close familiarity with deployment scenarios that seem to be characterized by acronyms such as RSS, aRFS, TSO, LRO, etc. While I am pretty familiar with a lot of encapsulation techniques, I had to study the meaning of these acronyms. If it is intended to effectively restrict the intended audience, that is O.K., but otherwise more background is needed along with relevant citations. ============================================== [GUEEXTENS] is cited in a way that places a normative dependency on [GUEEXTENS]. So, [GUEEXTENS] belongs in the Normative References. ============================================== I have a large number of specific comments which I will post shortly in the form of a rfcdiff-generated file.
- [Int-area] Intdir early review of draft-ietf-inta… Charles Perkins
- Re: [Int-area] Intdir early review of draft-ietf-… Charlie Perkins
- Re: [Int-area] Intdir early review of draft-ietf-… Tom Herbert