IETF Logo Mail Archive

Re: [Sidrops] Publication Point -> RP synchronization in bandwidth constrained environments (note for RRDP v2)

Christopher Morrow <christopher.morrow@gmail.com> Tue, 30 May 2023 19:22 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8D9C1782B5 for <sidrops@ietfa.amsl.com>; Tue, 30 May 2023 12:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 hgXQObYbuHuG for <sidrops@ietfa.amsl.com>; Tue, 30 May 2023 12:22:04 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 B7FE6C151982 for <sidrops@ietf.org>; Tue, 30 May 2023 12:21:31 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id ca18e2360f4ac-774924b7c4dso352540639f.1 for <sidrops@ietf.org>; Tue, 30 May 2023 12:21:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685474491; x=1688066491; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ui1P1bqD4LkuXHEXnAKNI9dqFDDOkU00vpX1VbmzCvA=; b=KOQzmEY/WH9rchRb3JKoy+bHvG0/0s/So11YWFYtZdxYRdhdIhLo+SkpknJL6Vpbcs F+XgBxuW7pNbyoWy6ZWZDnCWj7b3B1rkOscrys/Z62OHlmwiOUnloVjOKFKMvIjX9Sfl nN1BW4H9IL2xSEZdNVAcmOtA09n4yhvKlFuWn4ZLDmdPw53KARp3UMNiTfeUnGvvRX+L obKWMxI1cOS4ayfZ6dcybaTAN2pRJx1ruzRuzBpZ6BsNcxL8L6UlJ9Wtgvp6tj8nQBXA j/3tz9reTaeb5ruspKDgFRCU2j+DYZ5ZTvp6aAC68jAj2qM7HZUo2IoNIWy0+BEBDYt+ VRtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685474491; x=1688066491; h=content-transfer-encoding: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=ui1P1bqD4LkuXHEXnAKNI9dqFDDOkU00vpX1VbmzCvA=; b=D/cVbr9AwYVkduijJI7Q8ctDA/idD8zhB+OuMDea+0FAsTQeAs73RNW3bGVP3Mtc18 zcBvK89f5WnN8RFzsln7eOkIh1rhqFqf0TT6e5x/VluT3YdfOtW67IGiT8c2pwvbrPX1 6RahhblJ+bTD9LPQ3IfwmF+WNFu+CrHkC/gs7GJhNp+uc9TYNc4VY/Pee2Eyp0X9gARa KE0HXri8yIbh8x6IIgzuPS1x6i+fy6I/bLv+OOcBNSNGmnzKrgu5j5EQWFW4UrBEY6Xf dQzscB1osQFUqikX/j9Rk+f9Zjpp2UmVcgT0HPYnZfeb9HlM5oQfvNEyCMAaeNz66jYX V+5A==
X-Gm-Message-State: AC+VfDyNlGC0tUUi2LGOtcXM804VUKO5fULQ61lYAYDGKedNAQXlKZGW WcDI5bfJPIr4EYcIgVN9+gtF7mxp8+qzAuRov4Y=
X-Google-Smtp-Source: ACHHUZ4UiJuaZt4cEp5+l5OfUNvgRNBIFbXjTS60wsdNFOND21botlcSGjdZdaa2pjAolMd05FtxuAmO0n1OGut1oHk=
X-Received: by 2002:a5e:a903:0:b0:76c:62ab:5d96 with SMTP id c3-20020a5ea903000000b0076c62ab5d96mr2348034iod.19.1685474490443; Tue, 30 May 2023 12:21:30 -0700 (PDT)
MIME-Version: 1.0
References: <ZHYYt77xdtrkNV1a@snel>
In-Reply-To: <ZHYYt77xdtrkNV1a@snel>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Tue, 30 May 2023 15:21:19 -0400
Message-ID: <CAL9jLabBTWYS7B-_uyeq_e8DeqMiWXSg7bE0Tv2O31n2MX=Vsg@mail.gmail.com>
To: Job Snijders <job=40fastly.com@dmarc.ietf.org>
Cc: sidrops@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/cA1pUUoZhabXJnHn4jsvfjgQ74c>
Subject: Re: [Sidrops] Publication Point -> RP synchronization in bandwidth constrained environments (note for RRDP v2)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 May 2023 19:22:04 -0000

On Tue, May 30, 2023 at 11:39 AM Job Snijders
<job=40fastly.com@dmarc.ietf.org> wrote:
>
> Dear all,
>
> I wanted to share a note that if work ever starts on RRDP v2, that
> design team should consider conservation of bandwidth a priority.
>
> Recently one of the RIRs ran into a network congestion issue noticable
> on intercontinental transfers: their 36 megabyte RRDP snapshot was being
> served at a rate of ~ 25 kilobytes per second, and worse the TCP
> connections often timed out.
>

wait, I thought the reason (one of the reasons) that rrdp was great was it
was cacheable and all of this would be behind CDNs?

v2.23.0 | Report a Bug | By Email