Re: [Anima] Multicast in the ACP?

Toerless Eckert <eckert@cisco.com> Thu, 23 April 2015 17:40 UTC

Return-Path: <eckert@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50D471B310A for <anima@ietfa.amsl.com>; Thu, 23 Apr 2015 10:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 g0QCFHlamuDt for <anima@ietfa.amsl.com>; Thu, 23 Apr 2015 10:39:58 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EDC31B30F9 for <anima@ietf.org>; Thu, 23 Apr 2015 10:39:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1034; q=dns/txt; s=iport; t=1429810772; x=1431020372; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=AkjITHuzYIQkzbqb0Opkja+Y1ey55saOzgAKZcJrBis=; b=kJbdr/1BlGlshbltczqnXfN2+TAIrdUOBPpnwgf9ZAeF1RK71pIr5vrC b76KXtat25U9TaOO2VeWdN52ZZrDaMQlJGF01YpRGzVynC2ABH2l5cQS+ itCHNpEc1zcSH7E7JEpEZzFfM+S7idaXo9HZC7dsO66HmvvTnPupmvb8/ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BtBAD/LTlV/40NJK1bgwxSXcYjCYFRhgQCgTY4FAEBAQEBAQGBCoQhAQEEOj8QCxgJJQ8FSYg+DcxnAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4s3hQQHgxeBFgWLVIl3hjMBgV6TbSNggzQegnUBAQE
X-IronPort-AV: E=Sophos;i="5.11,632,1422921600"; d="scan'208";a="143964313"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-6.cisco.com with ESMTP; 23 Apr 2015 17:39:22 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t3NHdL0d017122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Apr 2015 17:39:21 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t3NHdKKq014635; Thu, 23 Apr 2015 10:39:20 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t3NHdKCn014634; Thu, 23 Apr 2015 10:39:20 -0700
Date: Thu, 23 Apr 2015 10:39:20 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <20150423173920.GC11499@cisco.com>
References: <5536EE40.30705@gmail.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF22F5FE63@xmb-rcd-x14.cisco.com> <5537FFEF.9020308@gmail.com> <10795.1429737994@sandelman.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <10795.1429737994@sandelman.ca>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima/KrdfMs86tAUMu7oku16wQmAYh-c>
Cc: Anima WG <anima@ietf.org>
Subject: Re: [Anima] Multicast in the ACP?
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2015 17:40:00 -0000

[individual]

On Wed, Apr 22, 2015 at 05:26:34PM -0400, Michael Richardson wrote:
> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/
> describes a way to do multicast across that collection of links... that is if
> we can ever get it through the IESG.

MPL is flooding with sequence numbers for loop/duplicate avoidance.
It then uses Trickle for link transmission which also doing
link-level duplicate avoidance by sequence number (observing what
others have sent, do not send yourself again). Kinda like CSMA/SA
(Send Avoidance ;-)

If we have p2p secure associations between neighbors, there will
likely not be a lot of benefit for the Trickle part though, so
might end up having some amount of overdesign for what we need.

I also would prefer the idea of hop-by-hop reliable forwarding.
All this datagram multicasting across slow/unreliable networks
is IMHO a mistake. MPL could introduce that hop-by-hop reliability
i think it doesn't do it so far, and its reinventing reliability.

Toerless