[IPv6] Review feedback requested: draft-ietf-pim-rfc1112bis

Toerless Eckert <tte@cs.fau.de> Mon, 04 March 2024 22:39 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822C1C18DB88 for <ipv6@ietfa.amsl.com>; Mon, 4 Mar 2024 14:39:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 cWpLmYdtnVBO for <ipv6@ietfa.amsl.com>; Mon, 4 Mar 2024 14:39:22 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.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 68991C18DB86 for <ipv6@ietf.org>; Mon, 4 Mar 2024 14:39:17 -0800 (PST)
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)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4TpYXL36s5znkKl for <ipv6@ietf.org>; Mon, 4 Mar 2024 23:39:14 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4TpYXL2HLMzkn1d; Mon, 4 Mar 2024 23:39:14 +0100 (CET)
Date: Mon, 04 Mar 2024 23:39:14 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: ipv6@ietf.org
Message-ID: <ZeZNkgtrVqbe09wv@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mLLVilSeNEOhKP6du4JzRFf6jdE>
Subject: [IPv6] Review feedback requested: draft-ietf-pim-rfc1112bis
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2024 22:39:24 -0000

Dear IPv6 colleagues

I would hereby like to ask you to provide review feedback for subject draft (rfc1112bis) which is in PIM-WG.

RFC1112 is the original spec from 1989 for the extension to IP for the IP Multicast Host Stack,
including the IGMP protocol.

We never wrote such a spec for IPv6. Instead a couple of on-the-wire pieces for IPv6
where brought in via other RFCs. So i've often run across customers asking how to do IP multicast
with IP6, and the answer was "read rfc1112 and thinkit said IPv4 instead of IP".

This draft now attempts to close the gap by making the text apply to both IPv4 and IPv6.
The textual changes relating to IPv6 are hopefully quite small, but i woud appreciate
a lot if some IPv6 experts would check them out:

https://author-tools.ietf.org/diff?doc_1=rfc1112&doc_2=draft-ietf-pim-rfc1112bis-00

look for IPv6. Feedback ideally to pim@ietf.org, unless you think ipv6@ietf.org is better suited.

There are two other reasons for this draft, one is to retire/remove the obsolete IPv4 IGMPv1
protocol (rfc1112 being full internet standard making that obsolete protocol also full standard...),
the other was to add the ASM/SSM terminology and add references to the respective
RFCs for that (which of course applies to IPv6 as much as IPv4).

Thanks a lot!
    Toerless