[Int-area] Alissa Cooper's Discuss on draft-ietf-intarea-frag-fragile-15: (with DISCUSS and COMMENT)
Alissa Cooper via Datatracker <noreply@ietf.org> Tue, 06 August 2019 20:30 UTC
Return-Path: <noreply@ietf.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 D8B2B1202E1; Tue, 6 Aug 2019 13:30:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-intarea-frag-fragile@ietf.org, Joel Halpern <joel.halpern@ericsson.com>, Joel Halpern <jmh@joelhalpern.com>, intarea-chairs@ietf.org, jmh@joelhalpern.com, int-area@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <156512344887.27340.5761295053779083959.idtracker@ietfa.amsl.com>
Date: Tue, 06 Aug 2019 13:30:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/ZDGCHeWsbFadmL8p9YGBFVv5n90>
Subject: [Int-area] Alissa Cooper's Discuss on draft-ietf-intarea-frag-fragile-15: (with DISCUSS and COMMENT)
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: Tue, 06 Aug 2019 20:30:49 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-intarea-frag-fragile-15: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Thanks for writing this document. Section 6.1 says: "Developers MAY develop new protocols or applications that rely on IP fragmentation if the protocol or application is to be run only in environments where IP fragmentation is known to be supported." I'm wondering if there should be a bit more nuance here to make the recommendation clearer. Do we think there is a case where an application protocol developed in the IETF will be known to only run in environments where fragmentation is supported? If we don't think developing such a protocol would be in scope for the IETF, then I'm wondering if that case should be called out explicitly with a stronger normative requirement. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Section 3.8.2: If there is any chance we think this situation might improve before this RFC-to-be gets obsoleted one day, I might suggest: s/The security policy described above is implemented incorrectly on many consumer CPE routers./The security policy described above has been implemented incorrectly on many consumer CPE routers./ Section 3.9: s/Another recent study/Another study/
- [Int-area] Alissa Cooper's Discuss on draft-ietf-… Alissa Cooper via Datatracker
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Tom Herbert
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Alissa Cooper
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Joel M. Halpern
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Brian E Carpenter
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Joel M. Halpern
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Joe Touch
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Fernando Gont
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Brian E Carpenter
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Tom Herbert
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Fernando Gont
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Fernando Gont
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Joe Touch
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Fernando Gont
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Joe Touch
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Ron Bonica
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Fernando Gont
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Ron Bonica
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Alvaro Retana
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Tom Herbert
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Ron Bonica
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Joel Halpern
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Joe Touch
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Ron Bonica
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Joe Touch
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Bob Hinden
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Fernando Gont