Re: [multipathtcp] [Technical Errata Reported] RFC6824 (3578)
Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Thu, 04 April 2013 06:29 UTC
Return-Path: <nishida@sfc.wide.ad.jp>
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 68E3A21F9420 for <multipathtcp@ietfa.amsl.com>; Wed, 3 Apr 2013 23:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level:
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nOkAQjU8pvkP for <multipathtcp@ietfa.amsl.com>; Wed, 3 Apr 2013 23:28:59 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3E121F92CD for <multipathtcp@ietf.org>; Wed, 3 Apr 2013 23:28:58 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id AD5542780CA for <multipathtcp@ietf.org>; Thu, 4 Apr 2013 15:28:57 +0900 (JST)
Received: by mail-ob0-f170.google.com with SMTP id uy19so36051obc.29 for <multipathtcp@ietf.org>; Wed, 03 Apr 2013 23:28:56 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.172.84 with SMTP id ba20mr3128116oec.10.1365056936199; Wed, 03 Apr 2013 23:28:56 -0700 (PDT)
Received: by 10.76.28.103 with HTTP; Wed, 3 Apr 2013 23:28:56 -0700 (PDT)
In-Reply-To: <20130401161148.CA1FAB1E003@rfc-editor.org>
References: <20130401161148.CA1FAB1E003@rfc-editor.org>
Date: Wed, 03 Apr 2013 23:28:56 -0700
Message-ID: <CAO249yfChaVv90ad3Brvt4wFb6voWXBQfquf8CUE+ZgHi3=q-Q@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="bcaec55408acc7cebc04d98315a8"
Cc: costin.raiciu@cs.pub.ro, alanford@cisco.com, multipathtcp <multipathtcp@ietf.org>, Mark Handley <m.handley@cs.ucl.ac.uk>, rfc@wgdfq.01.apr.2013.kasperd.net
Subject: Re: [multipathtcp] [Technical Errata Reported] RFC6824 (3578)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 04 Apr 2013 06:29:00 -0000
Hello, I believe that this errta is correct. But, the type should be editorial since this is nothing more than an editorial mistake. I think we'll need confirmation from authors to proceed this. Thanks, -- Yoshifumi On Mon, Apr 1, 2013 at 9:11 AM, RFC Errata System <rfc-editor@rfc-editor.org > wrote: > The following errata report has been submitted for RFC6824, > "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=6824&eid=3578 > > -------------------------------------- > Type: Technical > Reported by: Kasper Dupont <rfc@wgdfq.01.apr.2013.kasperd.net> > > Section: 3.1 > > Original Text > ------------- > Note that new subflows MUST NOT be established (using > > the process documented in Section 3.2) until a Digital Signature > > Standard (DSS) option has been successfully received across the path > > (as documented in Section 3.3). > > > > Corrected Text > -------------- > Note that new subflows MUST NOT be established (using > > the process documented in Section 3.2) until a Data Sequence > > Signal (DSS) option has been successfully received across the path > > (as documented in Section 3.3). > > > > Notes > ----- > In this document DSS is indicated as short for both "Digital Signature > Standard" and "Data Sequence Signal". I guess the reference to "Digital > Signature Standard" was a mistake. > > Instructions: > ------------- > This errata 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 (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC6824 (draft-ietf-mptcp-multiaddressed-12) > -------------------------------------- > Title : TCP Extensions for Multipath Operation with Multiple > Addresses > Publication Date : January 2013 > Author(s) : A. Ford, C. Raiciu, M. Handley, O. Bonaventure > Category : EXPERIMENTAL > Source : Multipath TCP > Area : Transport > Stream : IETF > Verifying Party : IESG >
- [multipathtcp] [Technical Errata Reported] RFC682… RFC Errata System
- Re: [multipathtcp] [Technical Errata Reported] RF… Yoshifumi Nishida