[multipathtcp] [Editorial Errata Reported] RFC6181 (4857)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 09 November 2016 13:35 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2ED129871 for <multipathtcp@ietfa.amsl.com>; Wed, 9 Nov 2016 05:35:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level:
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 s5hO6ED0167h for <multipathtcp@ietfa.amsl.com>; Wed, 9 Nov 2016 05:35:11 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E2E512986D for <multipathtcp@ietf.org>; Wed, 9 Nov 2016 05:35:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 307E8B81283; Wed, 9 Nov 2016 05:35:11 -0800 (PST)
To: marcelo@it.uc3m.es, spencerdawkins.ietf@gmail.com, ietf@kuehlewind.net, philip.eardley@bt.com, nishida@sfc.wide.ad.jp
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20161109133511.307E8B81283@rfc-editor.org>
Date: Wed, 09 Nov 2016 05:35:11 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/qd5NwW2CrapCPeRhQyos8E59pqY>
Cc: multipathtcp@ietf.org, rfc-editor@rfc-editor.org, tobias.seel@gmail.com
Subject: [multipathtcp] [Editorial Errata Reported] RFC6181 (4857)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2016 13:35:12 -0000
The following errata report has been submitted for RFC6181, "Threat Analysis for TCP Extensions for Multipath Operation with Multiple Addresses". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6181&eid=4857 -------------------------------------- Type: Editorial Reported by: Tobias Seel <tobias.seel@gmail.com> Section: 5 Original Text ------------- The attacker can do that by pretending that the path between IPA and IPT is congested but that the path between IPS and IPT is not. Corrected Text -------------- The attacker can do that by pretending that the path between IPA and IPS is congested but that the path between IPS and IPT is not. Notes ----- The attacker wants to pretend that the path between IPA and the Source is congested. There is no relevant path between IPA and IPT which has to be congested. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6181 (draft-ietf-mptcp-threat-08) -------------------------------------- Title : Threat Analysis for TCP Extensions for Multipath Operation with Multiple Addresses Publication Date : March 2011 Author(s) : M. Bagnulo Category : INFORMATIONAL Source : Multipath TCP Area : Transport Stream : IETF Verifying Party : IESG
- [multipathtcp] [Editorial Errata Reported] RFC618… RFC Errata System