[pim] pim: slotq for rfc1112bis ? (IANA)
Toerless Eckert <tte@cs.fau.de> Sat, 20 July 2024 15:48 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E220DC14F6E4; Sat, 20 Jul 2024 08:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 W4f358ckidzX; Sat, 20 Jul 2024 08:48:30 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D80AC14F698; Sat, 20 Jul 2024 08:48:28 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4WR9tb1ZHxznkpD; Sat, 20 Jul 2024 17:48:23 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4WR9tb0bdzzkvkx; Sat, 20 Jul 2024 17:48:23 +0200 (CEST)
Date: Sat, 20 Jul 2024 17:48:23 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: pim-chairs@ietf.org
Message-ID: <ZpvcRxTm8H9FlBpB@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Message-ID-Hash: RMPGSDQVSBBV667FWBRHXGMXDI53Y3ZH
X-Message-ID-Hash: RMPGSDQVSBBV667FWBRHXGMXDI53Y3ZH
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pim.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: pim@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [pim] pim: slotq for rfc1112bis ? (IANA)
List-Id: Protocol Independent Multicast <pim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/-ul22ntAqW0tRTzugSurzBEjqh4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Owner: <mailto:pim-owner@ietf.org>
List-Post: <mailto:pim@ietf.org>
List-Subscribe: <mailto:pim-join@ietf.org>
List-Unsubscribe: <mailto:pim-leave@ietf.org>
Dear PIM chairs
I just got reply from IANA re. 1112bis, and it turns out, rfc1112 is in quite
a few registries. So i will add an IANA section accordingly before wednesday,
and if there is still a way to squeeze this at the end, then i'm happy
to talk about it at the mike.
This was overlooked by me because rfc1112 predates the process
of IANA considerations by 1000 RFCs (first RFC with IANA considerations
of RFCs having IANA considerations is rfc2207).
Cheers
toerless
- [pim] pim: slotq for rfc1112bis ? (IANA) Toerless Eckert