Re: [Idr] Questions over draft-retana-idr-bgp-quic-01
Yingzhen Qu <yingzhen.ietf@gmail.com> Tue, 14 March 2023 00:01 UTC
Return-Path: <yingzhen.ietf@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F37C3C13AE38 for <idr@ietfa.amsl.com>; Mon, 13 Mar 2023 17:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mPLqIEfeFnSE for <idr@ietfa.amsl.com>; Mon, 13 Mar 2023 17:01:41 -0700 (PDT)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04EFDC169516 for <idr@ietf.org>; Mon, 13 Mar 2023 17:01:24 -0700 (PDT)
Received: by mail-ua1-x92f.google.com with SMTP id s23so9453082uae.5 for <idr@ietf.org>; Mon, 13 Mar 2023 17:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678752083; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=u0y9uMaOZPMxBHHRxkcMfdZUYcjOimC+f3n4pKflq+g=; b=HkfvmeeDsirphU0N3mb5W1n6wCFJiZLFXxH7vGG3n170zzDcwEpd22WcuMVkv/Er0n jmdwqLkw0AFOU/2Cs2koalAcpQb+7rkon+GlpQLy8l9wis1rOzHXfgnj0SXbxOunFvk2 RYkdI9n126YF5uJOqfm7jWDlN5eRmbHxo5veqZ6gE93SsxvnAKwZJmd65HnQRM7EKlEu e2XEKXRq15I3Kvkq1Q8oQGfH5HJhCyV08+AI+u/7eFo/Pq8Bh3DpUqkGyMRoYHW7R/Sq zNLiaY3aUvqRCoTxRFGjABOP2ue+yq1UrpQRrO+WkS3A+wawPtT7ADa5TTXWbyZyHV3Z keig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678752083; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=u0y9uMaOZPMxBHHRxkcMfdZUYcjOimC+f3n4pKflq+g=; b=o/q8xOqQaEHXBDK9XWWhjZ1o6xrMmNHo+3YvV9VDsQovorKF34xGvXjaVkm0sb5L5D y4oUEj/akWvuxzMmAHpFe6Yhbkd8W98FmEmk1zmkEotiwysNNWP/txVGfuCw8agpyhrA lfvBKfnIZgw0VMwQ2UJX2Kvj+XtUaWBp2QtuSNHZXTEb/GeAEOfNBnIUYZv3U8PH+jWs NK5FrIFut0/WMUUUlevro4PyYsfRLYc2Fxw5j8J5fCAl+riHiDPG5leW4Ru+gTuQ+czP 2100JGyDKURLCLHRIPvL36W+bfqTIAGVOyT7DEvgXuo7ImEDPw+oQZy+gjq7JpERiRPA EkUQ==
X-Gm-Message-State: AO0yUKXlg5NFLhEL2Zn3Yqh8XRf/DJm/GIYbB/rX08bnOMg7dTI/zSPR fvXn5kjzx3DgNj15ePQv7HXyi8Kt0W5iHB6f+GM0rdtaZH2Y
X-Google-Smtp-Source: AK7set8U5/J6GHGKhK3jafLkAQMtFXLHZJZJMyGHWU1KpXScrdgRTtY7Dbc6pIdMacCE8Qnq5Pge2g6NYwF2/w2J9Ag=
X-Received: by 2002:a05:6122:70e:b0:432:1d0:b211 with SMTP id 14-20020a056122070e00b0043201d0b211mr2858104vki.0.1678752083618; Mon, 13 Mar 2023 17:01:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAL=9YSUKo4XOuBAXORqt58EmduEB5vPGN=0Zzw5bTaEdoDJfJg@mail.gmail.com> <7766AAAE-FC16-4824-8D58-1566EAC8E0A0@puck.nether.net> <etPan.640fa151.1c60c79b.245@futurewei.com>
In-Reply-To: <etPan.640fa151.1c60c79b.245@futurewei.com>
From: Yingzhen Qu <yingzhen.ietf@gmail.com>
Date: Mon, 13 Mar 2023 17:01:12 -0700
Message-ID: <CABY-gOMtf-LVzSxeYWzCr78oQk6rXf73nrgBeEzOn-R9AH8Lbw@mail.gmail.com>
To: Alvaro Retana <alvaro.retana@futurewei.com>
Cc: Ben Cox <ben=40benjojo.co.uk@dmarc.ietf.org>, Jared Mauch <jared@puck.nether.net>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009c31c205f6d0ed20"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/e5MCxAKuNX-BJvB10DkWnfuwBCA>
Subject: Re: [Idr] Questions over draft-retana-idr-bgp-quic-01
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Mar 2023 00:01:44 -0000
As Alvaro mentioned, we're still at the very early stage of this project, and there is still a lot of work to be done. One of the key areas we're focusing on is exploring the benefits and challenges of using BGP over QUIC. There are several advantages of using QUIC for BGP, including its ability to support multiple streams over a single connection. This allows one stream to be reset without impacting other streams. Additionally, the stream prioritization feature of QUIC can help us manage traffic more effectively, ensuring that high-priority BGP traffic is given the resources it needs to be transmitted quickly and reliably. However, there are also some challenges to consider when using BGP over QUIC. For example, since TLS 1.3 is integrated into QUIC, this improves security and also makes it more difficult for network administrators to monitor and troubleshoot network traffic. Additionally, the complex nature of the protocol could require more resources to maintain and debug. Despite these challenges, we believe that the benefits of using BGP over QUIC are significant enough. While we acknowledge that there is still a lot of work to be done, we'd like the community to be aware of this work and get interested, and send questions and comments. Thanks, Yingzhen On Mon, Mar 13, 2023 at 3:19 PM Alvaro Retana <alvaro.retana@futurewei.com> wrote: > On March 13, 2023 at 12:56:48 PM, Jared Mauch wrote: > > > Hi! > > > ... > > I have my own concerns about the lack of stability within QUIC standards > here > > as well. We often see TCP sessions up for several years carrying BGP > data, > > and most of the QUIC stuff is extremely short lived, while a 7 year+ TCP > > (BGP) session isn’t as unusual as one might think. > > Yes, this is definitely new territory! > > The QUIC experts tell us they don't see an obvious red flag, but we do > need to keep in mind that the initial QUIC use case is HTTP/3 -- as you > mention. There are some features, like 0-RTT data exchange, that may not > be applicable to a long-lived session like BGP. > > Any potential transition will not be overnight. ;-) > > > Alvaro. > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr >
- [Idr] Questions over draft-retana-idr-bgp-quic-01 Ben Cox
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Jared Mauch
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Alvaro Retana
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Alvaro Retana
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Yingzhen Qu
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Claudio Jeker
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Gert Doering
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Robert Raszuk
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Gyan Mishra
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Claudio Jeker
- Re: [Idr] Questions over draft-retana-idr-bgp-qui… Claudio Jeker