Fwd: New Version Notification for draft-huitema-quic-mpath-option-00.txt
Christian Huitema <huitema@huitema.net> Wed, 21 October 2020 06:47 UTC
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB333A10F6 for <quic@ietfa.amsl.com>; Tue, 20 Oct 2020 23:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_FAIL=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 CuTTggPLUxrJ for <quic@ietfa.amsl.com>; Tue, 20 Oct 2020 23:47:35 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 83E623A10F4 for <quic@ietf.org>; Tue, 20 Oct 2020 23:47:35 -0700 (PDT)
Received: from xse143.mail2web.com ([66.113.196.143] helo=xse.mail2web.com) by mx17.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1kV7u6-0006xD-5q for quic@ietf.org; Wed, 21 Oct 2020 08:47:31 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 4CGLdh6158z6NQD for <quic@ietf.org>; Tue, 20 Oct 2020 23:47:20 -0700 (PDT)
Received: from [10.5.2.17] (helo=xmail07.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1kV7u4-0001O1-NC for quic@ietf.org; Tue, 20 Oct 2020 23:47:20 -0700
Received: (qmail 13059 invoked from network); 21 Oct 2020 06:47:20 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.43.139]) (envelope-sender <huitema@huitema.net>) by xmail07.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 21 Oct 2020 06:47:20 -0000
Subject: Fwd: New Version Notification for draft-huitema-quic-mpath-option-00.txt
References: <160326253400.20910.8654872719030557418@ietfa.amsl.com>
To: IETF QUIC WG <quic@ietf.org>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
X-Forwarded-Message-Id: <160326253400.20910.8654872719030557418@ietfa.amsl.com>
Message-ID: <52e333d9-bb61-c583-6fa4-94a1222ea68a@huitema.net>
Date: Tue, 20 Oct 2020 23:47:18 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <160326253400.20910.8654872719030557418@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------8D242744E7113F811ABF36DC"
Content-Language: en-US
X-Originating-IP: 66.113.196.143
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.143/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.143/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: ham
X-Spampanel-Outgoing-Evidence: Combined (0.05)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0acxlbLX9+ibl6ixChE10xOpSDasLI4SayDByyq9LIhVahDtD5Bk6ayZ 1X+z8G63lETNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59fvf+s65jR1oDwHaz3V8g2akU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+5hmwN8D4LrepG7AX8WNwY8Mm/JD3cPBOX47Hg3FEpDo46jSvfpO+1kZkomjtjB6X7/nuj3 koRhn2BlE7dXoT0pGVmhMAaQ/AfCRwRe7yHm5oY+NYmsSGn+svMubxnbgm1cr18FZBEPC2/c16Xd 7sC9aC4xteE1WLqGS9YoqrsZ2DyteN0e+ECCv9/f+GPymkgDVo7QBKA4MctKq4ifYPcXFRL2K3LA EfDXVOdt7wDbusYnuEVWSxKMHbU0zkNM3EElFDaoLuOPKc8gc82pKfhB7T02ZXdoQxMs//iOE4Fl hiCv9TR+UxzLZWL8hwGBjhoI3W+YcuHfP5PkZb5A+wE5qGdpH54Oa3V8I76VOEvlwLCanpZsarZa LIRpEqA8mZHZVaS002A2thbKLofb0Nwgtfoapc8NbVS5i8lbJzijTT36NkHZLFzvuBwDhZoecMpX dU571qBU/d2sq9m7FB7HPW4jgDvJzTWb1FxoOGAe+2kvZ+pWP1s35neRYWMQUWZErSs0X3oyoTc8 j/o7qulxr9t25/8dtISTNVVgaBEPoGre/hsBBxzR0ZxLcHZ9dOhJlI07iaZFiXhMO8RiD70foE2X cPU5SpbecWjAsOOMlQEH5tktsnhMr4gG+2qXrJ3e12Y/M3FzrV9BUQgy8RwS9R/2gMGq0KWAzmMf +ibVDpdplkxcBm4XM6d7s4Bx3w1WbaUe4g0kgaInvdEp64qlVpe//bVkg87Xe61e30HXuSERbInM iTBIUBbQ/Dy6Ip4D1rnEhdYtY/lMQX5s39oH5ijcGdSK77ViXbmzTYWgl82XucjoLWQ7++7jcUS/ T5w=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Q8LpREyiUmQFgcnoU_J-QiLEbFg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 06:47:37 -0000
Since everybody seems intent on discussing Multipath, I just wrote this short draft that presents a minimalist design for adding Multipath support to QUIC. Basically, it puts the onus entirely on the sender. The receiver side would just require support for a couple of management frames to explicitly abandon or promote a path. The sender will have to track the relation between packet number and path, possibly manage ranges of packet numbers, manage the per-path congestion control, update the packet loss detection to take path delays into account, and of course chose an algorithm for scheduling packets to paths. -- Christian Huitema -------- Forwarded Message -------- Subject: New Version Notification for draft-huitema-quic-mpath-option-00.txt Date: Tue, 20 Oct 2020 23:42:14 -0700 From: internet-drafts@ietf.org To: Christian Huitema <huitema@huitema.net> A new version of I-D, draft-huitema-quic-mpath-option-00.txt has been successfully submitted by Christian Huitema and posted to the IETF repository. Name: draft-huitema-quic-mpath-option Revision: 00 Title: QUIC Multipath Negotiation Option Document date: 2020-10-20 Group: Individual Submission Pages: 8 URL: https://www.ietf.org/archive/id/draft-huitema-quic-mpath-option-00.txt Status: https://datatracker.ietf.org/doc/draft-huitema-quic-mpath-option/ Htmlized: https://datatracker.ietf.org/doc/html/draft-huitema-quic-mpath-option Htmlized: https://tools.ietf.org/html/draft-huitema-quic-mpath-option-00 Abstract: The initial version of QUIC provides support for path migration. In this draft, we argue that there is a very small distance between supporting path migration and supporting simulatneous traffic on multipath. Instead of using an implicit algorithm to discard unused paths, we propose a simple option to allow explicit management of active and inactive paths. Once paths are explicitly managed, pretty much all other requirements for multipath support can be met by appropriate algorithms for scheduling transmissions on specific paths. These algorithms can be implemented on the sender side, and do not require specific extensions, except maybe a measurement of one way delays. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
- Fwd: New Version Notification for draft-huitema-q… Christian Huitema
- Re: New Version Notification for draft-huitema-qu… Martin Duke