Return-Path: X-Original-To: quic-issues@ietfa.amsl.com Delivered-To: quic-issues@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52D34120074 for ; Sat, 22 Feb 2020 02:29:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.454 X-Spam-Level: X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com 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 NaXjkzGn2RS3 for ; Sat, 22 Feb 2020 02:29:20 -0800 (PST) Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8667F12006D for ; Sat, 22 Feb 2020 02:29:20 -0800 (PST) Date: Sat, 22 Feb 2020 02:29:19 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1582367359; bh=gQtGZZWSqOby7lkmmF/wil8+IDx/41LHsrqQJQpd0uY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mV5W1CbNCMQAAoCMpaQQLSGtkWp5nmCRM9OVB1uuAJp8thmkJignsx4sVuxVxvEKP NztFeNEXOKfY2fVGAzqyDS0L01Gym75zYiGGpXQexvHA5yBEn05QFS/cZllQEk0sqP A6lRYgF5QtpJ3WkV6HA4YiiJ+MhzREB5+intAp70= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] renamed max_packet_size to max_udp_size (#3473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5e51027f4892a_3e993fe7a7ccd96c125990"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Feb 2020 10:29:22 -0000 ----==_mimepart_5e51027f4892a_3e993fe7a7ccd96c125990 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I realize QUIC is fairly tied to UDP, notably in all transport text. But if you want to modify QUIC to run over a separate channel like over a bluetooth bus, would you then invent a new transport parameter for that, or would packet size be the right choice? If so, renaming to UDP might have some consequences. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/pull/3473#issuecomment-589941553 ----==_mimepart_5e51027f4892a_3e993fe7a7ccd96c125990 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I realize QUIC is fairly tied to UDP, notably in all transport text. But if you want to modify QUIC to run over a separate channel like over a bluetooth bus, would you then invent a new transport parameter for that, or would packet size be the right choice? If so, renaming to UDP might have some consequences.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

----==_mimepart_5e51027f4892a_3e993fe7a7ccd96c125990--