Re: [pim] RFC 4541 - 224.0.0.*

Stig Venaas <stig@venaas.com> Thu, 08 November 2018 09:10 UTC

Return-Path: <stig@venaas.com>
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 B1857130E46 for <pim@ietfa.amsl.com>; Thu, 8 Nov 2018 01:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=venaas-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2AL1R4bSe3B for <pim@ietfa.amsl.com>; Thu, 8 Nov 2018 01:10:43 -0800 (PST)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04A79130DEB for <pim@ietf.org>; Thu, 8 Nov 2018 01:10:43 -0800 (PST)
Received: by mail-ed1-x52d.google.com with SMTP id n19-v6so15706172edq.11 for <pim@ietf.org>; Thu, 08 Nov 2018 01:10:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=4Y28yC6I8fD2mFyxBATUTx7jlxgf5B7Ll5tpoGuQ8aA=; b=ZHhKVtO62cKBO1CcL4jlTMnVXpt02jx0AY+Hwsw+Fc1a//M/k5GPQIZKV/diBBPFdP pZrlkB9NdfEIpGzUrCKqRFbvkXIZo9iNPA4daRX3ATEgrMiFEpNprBumTtXA9jaRim5S bYxWgg68zWGuV8s8kCoo37qm82ygo2kmdweX1ttjcGglKszDFpo/va9XQkV9CVRPVrqG 2TXOkwPMbdqiN+W9kbhP06ikhvFqPrfNMphHIebfsfqFFXHZ+j6AIBWD5tjQcAiSfDTb xY0i2rCoh5XociFwaGOI4HZuqh0DSwnHO1CyANgv5kBc8OJ+9q5yw175AJFhzg+x9CNV 5b/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=4Y28yC6I8fD2mFyxBATUTx7jlxgf5B7Ll5tpoGuQ8aA=; b=aG/x5c/Qooforwyy0cnsc1dr7LP+UHXxKrdz67WdhPAS0dERMX+quCo/cO+ddU2fhA ETnqMiZ/MSu4lC715J6/NC1jyR2NT/im4tJcf9a1Ca6qglZZquWpWzYQR0oudBDOZRse xEu2+psGgP7IkbH7GsG4xWbQQhZP4E+NC/fDdG+jfgni1+2EZO2/ndRCrwCnqXpAZ3Nk 9jC71Zy9DF6UvTD9bp1gGZJA56j4wACbr447oyyY11dUMiImK4zUy+Y8T8pMwLanj0Z2 jPBK/5S0ZeZ1czj6LQyTKV/uo0O9krpF5E734eCcms1iiyH6U3c0Ya8dZQIujzHModoD HNYw==
X-Gm-Message-State: AGRZ1gKfGLcf/CaM6bYea/QF4rjBr8RjmYMiW2vQxXpl/ekRvULvLWGv pFRkpZq67qJGm/CMNqIviwjqfWVSYDHGPxV1VMBYY6jHYwem2g==
X-Google-Smtp-Source: AJdET5fMmzVloaAr4h0SVb/BHWDCzcZ+CAuU7hPDtEyAGwL5KzbSTY5Hv8T+0LnxLZDbqUFDdwYetxmE2DI/uP2K3h8=
X-Received: by 2002:a50:84a9:: with SMTP id 38-v6mr3154464edq.32.1541668241441; Thu, 08 Nov 2018 01:10:41 -0800 (PST)
MIME-Version: 1.0
References: <4228986f516a48a3840838b0c2bb1c6f@BLRX13MDC414.AMER.DELL.COM> <CAHANBtJ17EjjchmzUjbpDrnPYsSp=+smrS4bnv+BEtPjMnViug@mail.gmail.com> <f627989da6c04780b9b8c2acdf793a13@BLRX13MDC414.AMER.DELL.COM>
In-Reply-To: <f627989da6c04780b9b8c2acdf793a13@BLRX13MDC414.AMER.DELL.COM>
From: Stig Venaas <stig@venaas.com>
Date: Thu, 08 Nov 2018 01:10:29 -0800
Message-ID: <CAHANBtK-3nnHOoOb6dy6bd=TbZAVoFcnniV10p3u65ooOP0aZg@mail.gmail.com>
To: Ganesh.ChennimalaiSa@dell.com
Cc: pim@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/Kq6dOofi4V96YuCOYPlfbbxbpP8>
Subject: Re: [pim] RFC 4541 - 224.0.0.*
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Nov 2018 09:10:46 -0000

Hi

OK, I think I understand. Isn't it a problem if a protocol expects to
be able to receive before sending though? If you look at
https://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml#multicast-addresses-1
you will see that there are quite a few different protocols, it is
difficult to say how all of them behave. Also, we don't know how
future protocols might behave.

Also, I hope you aren't assuming that a router/host that wants to
receive for a specific group, would be sending messages to the same
group address. There could be client-server link-local protocols that
don't work that way.

Stig

On Thu, Nov 8, 2018 at 12:40 AM <Ganesh.ChennimalaiSa@dell.com> wrote:
>
> Hi Stig,
>
> I understand the point. My question is: when all protocols are chatty we theoretically can use an alternate mechanism to learn their existence and forward only to group members. For instance OSPF is chatty and OSPF PDUs can be forwarded only within OSPF routers by leveraging its chatty nature. But when we have passive listeners in a link-local group, there is no opportunity for the network to know about the existence of such receivers.
>
> Do we have passive receivers (or protocols) in this 224.0.0.* range ?
>
> regs
> Ganesh
>
> -----Original Message-----
> From: pim <pim-bounces@ietf.org> On Behalf Of Stig Venaas
> Sent: Thursday, November 8, 2018 1:58 PM
> To: ChennimalaiSankaran, Ganesh
> Cc: pim@ietf.org
> Subject: Re: [pim] RFC 4541 - 224.0.0.*
>
>
> [EXTERNAL EMAIL]
> Please report any suspicious attachments, links, or requests for sensitive information.
>
>
> Hi
>
> The problem is that many stacks don't send IGMP reports for link-local
> groups, making the assumption that only routers need to know about
> membership, and link-local groups are not routed. Hence, you cannot
> rely on IGMP to determine which ports have interested receivers.
>
> Stig
>
> On Sun, Nov 4, 2018 at 4:55 PM <Ganesh.ChennimalaiSa@dell.com> wrote:
> >
> > Hi,
> >
> >
> >
> > Looking at RFC4541 and specifically the discussion 2..1.2 (2) on data forwarding rules. It says
> >
> >
> >
> > “Packets with a destination IP (DIP) address in the 224.0.0.X range
> >
> >       which are not IGMP must be forwarded on all ports.”
> >
> >
> >
> > As I see, there may not be explicit joins in this range and looking at IANA registry most protocols look chatty.
> >
> >
> >
> > Are there any groups with silent listeners that use this range ?
> >
> >
> >
> > regs
> >
> > Ganesh
> >
> >
> >
> > _______________________________________________
> > pim mailing list
> > pim@ietf.org
> > https://www.ietf.org/mailman/listinfo/pim
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim