IETF Logo Mail Archive

[pim] Ooops: Re: PIM call for adoption of draft-eckert-pim-rfc1112bis

Toerless Eckert <tte@cs.fau.de> Thu, 06 July 2023 17:58 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 97413C13AE47; Thu, 6 Jul 2023 10:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.646
X-Spam-Level:
X-Spam-Status: No, score=-6.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 i4uN0SUr8sMl; Thu, 6 Jul 2023 10:58:49 -0700 (PDT)
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 2CFC3C13AE2A; Thu, 6 Jul 2023 10:58:49 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff: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 4QxkmP2SKkznkTQ; Thu, 6 Jul 2023 19:58:45 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4QxkmP23Q9zkwMX; Thu, 6 Jul 2023 19:58:45 +0200 (CEST)
Date: Thu, 06 Jul 2023 19:58:45 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: pim@ietf.org
Cc: pim-chairs@ietf.org
Message-ID: <ZKcA1XL0jNkWS2el@faui48e.informatik.uni-erlangen.de>
References: <ZKcAcCJDNUmjpUfT@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <ZKcAcCJDNUmjpUfT@faui48e.informatik.uni-erlangen.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/gnPEJHyWE7Z4ACrlo6TybyVnE9E>
Subject: [pim] Ooops: Re: PIM call for adoption of draft-eckert-pim-rfc1112bis
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2023 17:58:51 -0000

The subject should have something like "please, ?" or the like.
Obviously i am not in a position to call for adoption. Sorry for the inaccurate subject..

*sigh*.

On Thu, Jul 06, 2023 at 07:57:04PM +0200, Toerless Eckert wrote:
> Dear PIM WG, Chairs
> 
> At IETF116 i presented this draft and think it received good WG interest, the
> chairs suggestested we might want to do an adoption call before IETF117. So
> hereby sending this email reminding of this draft.
> 
> Quick summary why ?
> 
> RFC1112bis IMHO would complete our IGMP/MLD update process, which othrerwise is
> hopefully progrssing nicely with RFC3810bis, RFC3376bis and RFC3228bis going into
> IETF/IESG review.
> 
> What is RFC1112bis - summary:
> 
> RFC1112 defines "IP Multicast (ASM)" service (for IPv4 only) - AND IGMPv1
> 
> We need to retire IGMPv1:
>    RFC1112bis removes the IGMPv1 text.
>    We can then make RFC1112 and hence IGMPv1 historic and therefore retire IGMPv1
>    Because of RFC1112bis, this will not retire the ASM service model which is 
>    then defined via RFC1112bis.
> 
> We want to declare IP Multicast (ASM) service to also apply to IPv6
>    There is no other document currently doing all this.
>    So RFC1112bis has all the changes to talk about IP and IPv6.
> 
> Thats pretty much the changes summary. Threre are details of course,
> 
> Hope we can get this also done in short time in the WG.
> 
> Thanks so much
>     Toerless
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

v2.23.0 | Report a Bug | By Email