IETF Logo Mail Archive

[Sidrops] Re: Parent CA publication server in draft-ietf-sidrops-publication-server-bcp

Tim Bruijnzeels <tbruijnzeels@ripe.net> Tue, 30 July 2024 08:37 UTC

Return-Path: <tbruijnzeels@ripe.net>
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 66D1FC14F6AB for <sidrops@ietfa.amsl.com>; Tue, 30 Jul 2024 01:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ripe.net
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 2Lt7ijjnxQ98 for <sidrops@ietfa.amsl.com>; Tue, 30 Jul 2024 01:37:42 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 914DBC14F689 for <sidrops@ietf.org>; Tue, 30 Jul 2024 01:37:42 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a7aa086b077so373334366b.0 for <sidrops@ietf.org>; Tue, 30 Jul 2024 01:37:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ripe.net; s=google1; t=1722328660; x=1722933460; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=2dI05qGKDQwgbSEx4mcYcH1zXCUsoMj1Yf20lVrB0/g=; b=VmlP+OWOB8GO0NPq5qqdftBfbw3173oky/BCjdZ7Jgo0JvxVeMuGctrYkA8vrTt5sg FpIktRlaNe0NSNRm6K38n4E5OJEKlMUH5AcIbkQUVWWiEwT1o1FYtxya0dtvcUk2+mjI BRzZWYH7NLE3v1jd39wRdxRaZyU9z2a1fSLAxL4io/oXbl5d4DKYu2TLHsKnNewfsKrE cZXff6H9ib4nOtdZ5fiB7CFsrnTiY7U51tvfv4gA6ceYkvvIvvjDBo31TAHZ9/6/Vq1B uOmBYa4qSwc5nDXZdn32V/SenATw1eZtQbwPvLjK+PYNqKVnf6PUOsV+zYQFsbal/AxK dWOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722328660; x=1722933460; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=2dI05qGKDQwgbSEx4mcYcH1zXCUsoMj1Yf20lVrB0/g=; b=Bv+suaL9F9zlDDe7XJ17x0p3OLXg00WFrKSAg6BXqUBArI94zxk8IiKX1AWmkX4XrW oH5C4XznT988M0Q8Vf25qyZb6Jyv5sdFwlmlpLRnh9bqIIuXYqYuh4Uo+NMjV5iME9hr tUia8dlrZ7VXigxqHVuCob0X+rglVJc21eeJTR9+U7U5hLbDHEtygx4yh93Wd+wmab88 XJYpKWqL+hKetcLIR+VKUmxKrIXRRNUjM1Xkqsz5nBUHXMdl+k6vlL0Ek8gBnhSvp8N6 5+COkDaf0DoVFB4B4nu3XCn5qP8G39luuOsKn5cLSmcp6k62mJ+z6mZkLMJmHKVUJAhY NA2Q==
X-Gm-Message-State: AOJu0YyXGIweIg3TRuIZhcpLd3FvdoZH5ldL50008dYR+QRaggVWOhgF 62d5yybloD0LAQRFdpHiTIcqRNrxRcgCu5GwyhKifQOGhVLKbAWyVn9kadGDiBA=
X-Google-Smtp-Source: AGHT+IGWzr5ByR2yhXg+a042sneIzO2harpBmeVh/pRTa2A8NE1pumMhTW87Gqu4+OC+L1+lNsdiXw==
X-Received: by 2002:a17:907:e89:b0:a77:d85c:86f5 with SMTP id a640c23a62f3a-a7d401361f3mr486785966b.53.1722328659944; Tue, 30 Jul 2024 01:37:39 -0700 (PDT)
Received: from smtpclient.apple (2a02-a46d-1a37-0-15ce-31b6-cb18-fac3.fixed6.kpn.net. [2a02:a46d:1a37:0:15ce:31b6:cb18:fac3]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a7acad411a6sm607103266b.117.2024.07.30.01.37.39 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jul 2024 01:37:39 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Tim Bruijnzeels <tbruijnzeels@ripe.net>
In-Reply-To: <CAMEWqGvDOvJ5vGs1jiMG_bc4C1r37v5J=KAHeaeOkBiMg7NOEg@mail.gmail.com>
Date: Tue, 30 Jul 2024 10:37:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <698D0399-F0B4-4457-92DC-119BCCF0BB9A@ripe.net>
References: <CAMEWqGvnYaeQsUssPDyGYSQ7OJmN7YiosrSDEVuZNcsGk1BaCA@mail.gmail.com> <47F1CF1C-39E4-46A4-8D93-EA4EFA35B305@ripe.net> <CAMEWqGvDOvJ5vGs1jiMG_bc4C1r37v5J=KAHeaeOkBiMg7NOEg@mail.gmail.com>
To: Q Misell <q@as207960.net>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: YICOFAX3DL3GE2Z4SLKUK54MJGVIOOZO
X-Message-ID-Hash: YICOFAX3DL3GE2Z4SLKUK54MJGVIOOZO
X-MailFrom: tbruijnzeels@ripe.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: SIDR Operations WG <sidrops@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Sidrops] Re: Parent CA publication server in draft-ietf-sidrops-publication-server-bcp
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/KyeAQ63Vjm4PWTqqlLBtxSU8R2Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

Hi Q,

> On 30 Jul 2024, at 10:00, Q Misell <q@as207960.net> wrote:
> 
> > This is what is implemented at RIPE NCC.
> 
> I discovered this a few weeks ago, and the hard-coded 10 child limit. Unfortunately, I have more than 10 customers so that doesn't work for me either.

Perhaps not for this list, but since it was brought up here: we use a hardcoded limit to keep this from exploding. It was intended as a ’soft quota’ warning, but I realise that the UI does not communicate this clearly.

That said, you can contact us one on one and then we can see if this limit can be stretched for you.

> I intend to write my own implementation of the publication proxy, as the APNIC implementation doesn't really suit my environment, and also to provide another independent implementation. I'll let the list know how that goes.

That is useful work in any case.

Tim

v2.46.0 | Report a Bug | By Email | System Status