
From nobody Tue Jul  1 11:08:52 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A56E1B2883; Tue,  1 Jul 2014 11:08:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_61=0.6, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 NIjGrU-Xqh5Z; Tue,  1 Jul 2014 11:08:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABBA1B2880; Tue,  1 Jul 2014 11:08:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5937C180095; Tue,  1 Jul 2014 11:08:21 -0700 (PDT)
To: ramakrishnadtv@infosys.com, fenner@research.att.com, M.Handley@cs.ucl.ac.uk, holbrook@arastra.com, kouvelas@cisco.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140701180821.5937C180095@rfc-editor.org>
Date: Tue,  1 Jul 2014 11:08:21 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/pA-P_cVlSigp-28As64yEmJCtG0
Cc: akatlas@juniper.net, iesg@ietf.org, pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] [Errata Held for Document Update] RFC4601 (4027)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 01 Jul 2014 18:08:37 -0000

The following errata report has been held for document update 
for RFC4601, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4601&eid=4027

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Ramakrishna DTV <ramakrishnadtv@infosys.com>
Date Reported: 2014-06-26
Held by: Alia Atlas (IESG)

Section: 4.8.2

Original Text
-------------
     if( iif == RPF_interface(S) AND UpstreamJPState(S,G) == Joined ) {
         oiflist = inherited_olist(S,G)
     } else if( iif is in inherited_olist(S,G) ) {
         send Assert(S,G) on iif
     }

     oiflist = oiflist (-) iif
     forward packet on all interfaces in oiflist


Corrected Text
--------------
     oiflist = NULL

     if( iif == RPF_interface(S) AND UpstreamJPState(S,G) == Joined ) {
         oiflist = inherited_olist(S,G)
     } else if( iif is in inherited_olist(S,G) ) {
         send Assert(S,G) on iif
     }

     oiflist = oiflist (-) iif
     forward packet on all interfaces in oiflist


Notes
-----
The followng line is missing:

    oiflist = NULL

Without this, it may lead to accessing uninitialized variable
oiflist. This line is present in Section 4.2 from which the simplified
SSM specific pseudo code is derived.

--------------------------------------
RFC4601 (draft-ietf-pim-sm-v2-new-12)
--------------------------------------
Title               : Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
Publication Date    : August 2006
Author(s)           : B. Fenner, M. Handley, H. Holbrook, I. Kouvelas
Category            : PROPOSED STANDARD
Source              : Protocol Independent Multicast
Area                : Routing
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Jul  3 11:39:01 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E9B21B2B31; Thu,  3 Jul 2014 11:38:54 -0700 (PDT)
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] 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 B_TN1JNH_LOe; Thu,  3 Jul 2014 11:38:49 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 041241B29E2; Thu,  3 Jul 2014 11:38:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140703183849.12417.79578.idtracker@ietfa.amsl.com>
Date: Thu, 03 Jul 2014 11:38:49 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/L5ykxMtlJZpZ-1K1tahZi3zYnjM
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-source-discovery-bsr-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 03 Jul 2014 18:38:54 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

        Title           : PIM flooding mechanism and source discovery
        Authors         : IJsbrand Wijnands
                          Stig Venaas
                          Michael Brig
	Filename        : draft-ietf-pim-source-discovery-bsr-01.txt
	Pages           : 10
	Date            : 2014-07-03

Abstract:
   PIM Sparse-Mode uses a Rendezvous Point (RP) and shared trees to
   forward multicast packets to Last Hop Routers (LHR).  After the first
   packet is received by the LHR, the source of the multicast stream is
   learned and the Shortest Path Tree (SPT) can be joined.  This draft
   proposes a solution to support PIM Sparse Mode (SM) without the need
   for PIM registers, RPs or shared trees.  Multicast source information
   is flooded throughout the multicast domain using a new generic PIM
   flooding mechanism.  This mechanism is defined in this document, and
   is modeled after the PIM Bootstrap Router protocol.  By removing the
   need for RPs and shared trees, the PIM-SM procedures are simplified,
   improving router operations, management and making the protocol more
   robust.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-source-discovery-bsr/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-source-discovery-bsr-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-pim-source-discovery-bsr-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jul  3 15:41:41 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C741B286C; Thu,  3 Jul 2014 15:41:37 -0700 (PDT)
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] 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 3XSK_IFRGL89; Thu,  3 Jul 2014 15:41:36 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 016371A063F; Thu,  3 Jul 2014 15:41:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140703224136.32137.46152.idtracker@ietfa.amsl.com>
Date: Thu, 03 Jul 2014 15:41:36 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/OknW9NL1mn-mPWB_UCoh17V8kO4
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-drlb-05.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 03 Jul 2014 22:41:37 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

        Title           : PIM Designated Router Load Balancing
        Authors         : Yiqun Cai
                          Sri Vallepalli
                          Heidi Ou
                          Andy Green
	Filename        : draft-ietf-pim-drlb-05.txt
	Pages           : 15
	Date            : 2014-07-03

Abstract:
   On a multi-access network, one of the PIM routers is elected as a
   Designated Router (DR).  On the last hop network, the PIM DR is
   responsible for tracking local multicast listeners and forwarding
   traffic to these listeners if the group is operating in PIM-SM.  In
   this document, we propose a modification to the PIM-SM protocol that
   allows more than one of these last hop routers to be selected so that
   the forwarding load can be distributed among these routers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-drlb/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-drlb-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-pim-drlb-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Jul  9 09:53:16 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA5381A0331 for <pim@ietfa.amsl.com>; Wed,  9 Jul 2014 09:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.003
X-Spam-Level: 
X-Spam-Status: No, score=-0.003 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 B5I5UmtoOcEE for <pim@ietfa.amsl.com>; Wed,  9 Jul 2014 09:53:13 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2::152:127]) by ietfa.amsl.com (Postfix) with ESMTP id AE3081A009E for <pim@ietf.org>; Wed,  9 Jul 2014 09:53:13 -0700 (PDT)
Received: from [10.154.36.242] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id C128C8160 for <pim@ietf.org>; Wed,  9 Jul 2014 18:53:11 +0200 (CEST)
Message-ID: <53BD7370.5080609@venaas.com>
Date: Wed, 09 Jul 2014 09:53:04 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: pim@ietf.org
References: <53026471.5020402@venaas.com>
In-Reply-To: <53026471.5020402@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/sTeuuestMOgDLeV_1rIhGsvMYY0
Subject: [pim] Request for Toronto agenda items
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Jul 2014 16:53:15 -0000

If you would like a slot on the pim agenda for Toronto, please email
Mike and me with your request ASAP. Note that you can email us both
by using the pim-chairs@tools.ietf.org address.

Stig



From nobody Tue Jul 15 15:05:58 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6E71B2791 for <pim@ietfa.amsl.com>; Tue, 15 Jul 2014 15:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 PI-gVAbpoYLh for <pim@ietfa.amsl.com>; Tue, 15 Jul 2014 15:05:46 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2::152:127]) by ietfa.amsl.com (Postfix) with ESMTP id 93C921B278B for <pim@ietf.org>; Tue, 15 Jul 2014 15:05:46 -0700 (PDT)
Received: from [IPv6:2001:420:c0c8:1003::303] (unknown [IPv6:2001:420:c0c8:1003::303]) by ufisa.uninett.no (Postfix) with ESMTPSA id 791B081EC for <pim@ietf.org>; Wed, 16 Jul 2014 00:05:44 +0200 (CEST)
Message-ID: <53C5A5B5.6000706@venaas.com>
Date: Tue, 15 Jul 2014 15:05:41 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: pim@ietf.org
References: <53026471.5020402@venaas.com> <53BD7370.5080609@venaas.com>
In-Reply-To: <53BD7370.5080609@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/MGhgfBVa3xQa30BLktMZaN4pTp4
Subject: Re: [pim] Request for Toronto agenda items
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 15 Jul 2014 22:05:53 -0000

Hi

On 7/9/2014 9:53 AM, Stig Venaas wrote:
> If you would like a slot on the pim agenda for Toronto, please email
> Mike and me with your request ASAP. Note that you can email us both
> by using the pim-chairs@tools.ietf.org address.

Here is the agenda we have so far. Anyone else want to be on the
agenda? Bill Atwood's exact topic should be decided tomorrow I hope.

Stig

Title                                            Presenter   Minutes
====================================================================
WG Status                                        Chairs         20
   Status of drafts

draft-ietf-pim-source-discovery-bsr-01           S. Venaas      20

"Authenticated IGMP", exact topic TBD            B. Atwood      30

Rechartering discussion                          Chairs         20

> Stig
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From nobody Wed Jul 16 15:38:15 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 011601A0389 for <pim@ietfa.amsl.com>; Wed, 16 Jul 2014 15:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 lnrFcky41hbl for <pim@ietfa.amsl.com>; Wed, 16 Jul 2014 15:38:10 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2::152:127]) by ietfa.amsl.com (Postfix) with ESMTP id B10FD1A0384 for <pim@ietf.org>; Wed, 16 Jul 2014 15:38:10 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:bdc0:6cf8:1731:fece] (unknown [IPv6:2001:420:301:1004:bdc0:6cf8:1731:fece]) by ufisa.uninett.no (Postfix) with ESMTPSA id 0769D823F for <pim@ietf.org>; Thu, 17 Jul 2014 00:38:08 +0200 (CEST)
Message-ID: <53C6FECF.8010704@venaas.com>
Date: Wed, 16 Jul 2014 15:38:07 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: pim@ietf.org
References: <53026471.5020402@venaas.com> <53BD7370.5080609@venaas.com> <53C5A5B5.6000706@venaas.com>
In-Reply-To: <53C5A5B5.6000706@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/OkI958UnkYPUjiaC60FKKnvkKJQ
Subject: Re: [pim] Request for Toronto agenda items
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Jul 2014 22:38:14 -0000

Hi

On 7/15/2014 3:05 PM, Stig Venaas wrote:
> Hi
>
> On 7/9/2014 9:53 AM, Stig Venaas wrote:
>> If you would like a slot on the pim agenda for Toronto, please email
>> Mike and me with your request ASAP. Note that you can email us both
>> by using the pim-chairs@tools.ietf.org address.
>
> Here is the agenda we have so far. Anyone else want to be on the
> agenda? Bill Atwood's exact topic should be decided tomorrow I hope.

It has now been revised slightly. See
https://datatracker.ietf.org/meeting/90/agenda/pim/
for the latest updates.

Stig

> Stig
>
> Title                                            Presenter   Minutes
> ====================================================================
> WG Status                                        Chairs         20
>    Status of drafts
>
> draft-ietf-pim-source-discovery-bsr-01           S. Venaas      20
>
> "Authenticated IGMP", exact topic TBD            B. Atwood      30
>
> Rechartering discussion                          Chairs         20
>
>> Stig
>>
>>
>> _______________________________________________
>> 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


From nobody Mon Jul 21 08:51:36 2014
Return-Path: <william.atwood@concordia.ca>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEC4C1A008D for <pim@ietfa.amsl.com>; Mon, 21 Jul 2014 08:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.236
X-Spam-Level: 
X-Spam-Status: No, score=-1.236 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no
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 yUPirA6yvuPw for <pim@ietfa.amsl.com>; Mon, 21 Jul 2014 08:51:31 -0700 (PDT)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.92]) by ietfa.amsl.com (Postfix) with ESMTP id 986E91A026A for <pim@ietf.org>; Mon, 21 Jul 2014 08:51:23 -0700 (PDT)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id s6LFpJYU004749 for <pim@ietf.org>; Mon, 21 Jul 2014 11:51:20 -0400
Message-ID: <53CD36FA.7030509@concordia.ca>
Date: Mon, 21 Jul 2014 11:51:22 -0400
From: William Atwood <william.atwood@concordia.ca>
Organization: Concordia University, Montreal
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: pim@ietf.org
References: <20140721154520.17114.78305.idtracker@ietfa.amsl.com>
In-Reply-To: <20140721154520.17114.78305.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140721154520.17114.78305.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2014/07/21 11:51:20 EDT
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/UcTc2HsWJPnJ_r0TTy-ywh_o6Uo
Subject: [pim] Fwd: New Version Notification for draft-atwood-pim-gsam-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 21 Jul 2014 15:51:34 -0000

Group Security Association Management (GSAM) Protocol is used for key
and SPI management for Secure IGMP and Secure MLD.

This will be presented at the PIM WG meeting on Tuesday afternoon.

  Bill


-------- Original Message --------
Subject: New Version Notification for draft-atwood-pim-gsam-00.txt
Date: Mon, 21 Jul 2014 08:45:20 -0700
From: <internet-drafts@ietf.org>
To: William Atwood <william.atwood@concordia.ca>, Bing Li
<leebingice@gmail.com>, "william.atwood@concordia.ca"
<william.atwood@concordia.ca>, Bing Li <leebingice@gmail.com>


A new version of I-D, draft-atwood-pim-gsam-00.txt
has been successfully submitted by William Atwood and posted to the
IETF repository.

Name:		draft-atwood-pim-gsam
Revision:	00
Title:		Group Security Association Management Protocol
Document date:	2014-07-21
Group:		Individual Submission
Pages:		15
URL:
http://www.ietf.org/internet-drafts/draft-atwood-pim-gsam-00.txt
Status:         https://datatracker.ietf.org/doc/draft-atwood-pim-gsam/
Htmlized:       http://tools.ietf.org/html/draft-atwood-pim-gsam-00


Abstract:
   This document specifies a Group Security Association Management
   (GSAM) protocol, which manages the IPsec Group Security Associations
   that are used to protect some packets of Secure IGMP (SIGMP) and
   Secure MLD (SMLD).  In GSAM, one router is elected as the group
   controller / key server to create group security associations for all
   the interesting secure groups and distribute them to authorized users
   and other routers.





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat




From nobody Mon Jul 21 13:12:04 2014
Return-Path: <sami.biz.email@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754251A01E8 for <pim@ietfa.amsl.com>; Mon, 21 Jul 2014 13:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 aBbwqLPTtGEK for <pim@ietfa.amsl.com>; Mon, 21 Jul 2014 13:11:57 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7C3B1A008D for <pim@ietf.org>; Mon, 21 Jul 2014 13:11:51 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id n3so4830334wiv.0 for <pim@ietf.org>; Mon, 21 Jul 2014 13:11:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=cDG5rYQH01itiZ3vwSJ8fxexLp/lkOxnA7VbHzWHNdM=; b=FF1nHam6OY3PBXMkjAVmAapJkqVXQvEAlBT6tFzQi67zBBxZrNVHr9wFIJyGG0e5eH Pr1IuG2gHP6VQBwngJ8MRYWiDHpPWFE5tdELQUwxxSB1QGIo1mKPffr6Vu/WO+aNSt1h tp7beag/BRUr6HuZHhDrVdTy/LKe7LwUhRvmNPfqiv54Yuz+/4Na201ohELkqJotbK54 1owApJ+m7JQhtzzKehjRkYirHaeMP6ehbm1h16oW2XXrFOF7D++/PeXgDNJs2ehlrdzR DM+P/Et9E4oDgvlPph1uADU4jd3J8ApaI6quutJDXmOqs06VqpNKPG8+OsZ+HDJeF6Ke asyw==
X-Received: by 10.180.35.34 with SMTP id e2mr7925095wij.12.1405973510401; Mon, 21 Jul 2014 13:11:50 -0700 (PDT)
Received: from [192.168.1.4] ([178.253.53.171]) by mx.google.com with ESMTPSA id h3sm40037740wjn.10.2014.07.21.13.11.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jul 2014 13:11:49 -0700 (PDT)
Message-ID: <53CD8213.2080401@gmail.com>
Date: Tue, 22 Jul 2014 00:41:47 +0330
From: saeed sami <sami.biz.email@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: pim@ietf.org, pim-chairs@tools.ietf.org
References: <mailman.220.1405796477.29336.pim@ietf.org>
In-Reply-To: <mailman.220.1405796477.29336.pim@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/hXU59VA04Z33B6IJ2DlJF8zRjyc
Subject: Re: [pim] Request for Toronto agenda items
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 21 Jul 2014 20:12:02 -0000

Hello.
I will appreciate if the draft-sami-pim-ng is introduced again in 
Toronto meeting. and i hope this time it
attracts the interest of other WG experts to review it.
it will be updated soon with Bidirectional-pim integration unique to 
Pim-NG which allows the use of redundant Roots and brings automation in 
domains using bidirectional logic.
Thanks .
Sincerely
Saeed Sami
On 07/19/2014 10:31 Ø¨.Ø¸, pim-request@ietf.org wrote:
> Request for Toronto agenda items


From nobody Tue Jul 22 18:51:31 2014
Return-Path: <hermin.anggawijaya@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18AD41A0151 for <pim@ietfa.amsl.com>; Tue, 22 Jul 2014 18:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 F4WoBHq-aPJI for <pim@ietfa.amsl.com>; Tue, 22 Jul 2014 18:51:29 -0700 (PDT)
Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00FF91A0114 for <pim@ietf.org>; Tue, 22 Jul 2014 18:51:28 -0700 (PDT)
Received: by mail-vc0-f180.google.com with SMTP id ij19so919209vcb.25 for <pim@ietf.org>; Tue, 22 Jul 2014 18:51:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=GclDBbWVD3sUuyYfY1jiHKCgasKskmwTiwpNxfaALGA=; b=Ll3Uho/kJwY1CHDx90o1W1JSD+vfglJGZymFX12P2GaGt4s3XaqGmEdnsdbN3PNaS5 6s6A3e2UiNfulLw53qwfC8CBTj6FUAF7v9/9VlXmCBOqEklwFB8X2NI/SRLno59dcOZc 79rPhlpMvFfkxC7OUjiO1DjWhO4MzA/XNJvMzp8/I0ZvlB8yAmNfborYwMSmV45NnNoE ybmXTC1Cdy6fPV7SB0o8+JI23tquKnFbY8vMXp+E5SxCyjhOU++GnJvSDCls9b866jkT 62NjL6xOOsLCDGGisbd2dIJK3ph6p41S0uATfcK0geophTag48lPqPzmWBUtwk4nMfkt cItg==
MIME-Version: 1.0
X-Received: by 10.52.163.169 with SMTP id yj9mr788946vdb.94.1406080287767; Tue, 22 Jul 2014 18:51:27 -0700 (PDT)
Received: by 10.58.45.133 with HTTP; Tue, 22 Jul 2014 18:51:27 -0700 (PDT)
Date: Wed, 23 Jul 2014 13:51:27 +1200
Message-ID: <CAJgsEzX7+TO5=U__0D+8BfEZE6OZO-husTfjpCdsXPiTR+AwGA@mail.gmail.com>
From: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>
To: pim@ietf.org
Content-Type: multipart/alternative; boundary=001a11c1a2201401aa04fed29485
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/dcz8mEYh32s9y9WcyvzwYsLsoBI
Subject: [pim] comment on draft-ietf-pim-source-discovery-bsr
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 01:51:30 -0000

--001a11c1a2201401aa04fed29485
Content-Type: text/plain; charset=ISO-8859-1

Would the draft benefit by allowing static (S,G, Holdtime) tuples to be
configured at the FHR ? this way (listeners or) LHRs can send (S,G) joins
before the first packet of real data is sent (and the SPTs from LHR to FHR
are primed), thus allowing listeners that need first data packet to receive
it properly. And if this can be included, maybe we need a way of marking
the (S,G,Ht) as static config in the flooded source list.

Of course I realise that the first packet issue can also be solved at the
application layer, by  sources to send priming 'data' packets, but that's
another story.

I think the scenario is not unrealistic, since source addresses do not
change that often and chances are the FHR is managed by the same admin
managing the data sources ?

cheers

Angga

--001a11c1a2201401aa04fed29485
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Would the draft benefit by allowing static (S,G, Hold=
time) tuples to be configured at the FHR ? this way (listeners or) LHRs can=
 send (S,G) joins before the first packet of real data is sent (and the SPT=
s from LHR to FHR are primed), thus allowing listeners that need first data=
 packet to receive it properly. And if this can be included, maybe we need =
a way of marking the (S,G,Ht) as static config in the flooded source list.<=
br>
<br></div><div>Of course I realise that the first packet issue can also be =
solved at the application layer, by=A0 sources to send priming &#39;data&#3=
9; packets, but that&#39;s another story.<br><br></div><div>I think the sce=
nario is not unrealistic, since source addresses do not change that often a=
nd chances are the FHR is managed by the same admin managing the data sourc=
es ?<br>
</div><div><br></div><div>cheers<br><br>Angga<br><br></div></div>

--001a11c1a2201401aa04fed29485--


From nobody Wed Jul 23 03:00:32 2014
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D16541A038B; Wed, 23 Jul 2014 03:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.395
X-Spam-Level: 
X-Spam-Status: No, score=-13.395 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 Pt2d7vMUcy7F; Wed, 23 Jul 2014 03:00:27 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ECBB1A035F; Wed, 23 Jul 2014 03:00:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2220; q=dns/txt; s=iport; t=1406109628; x=1407319228; h=date:from:to:cc:subject:message-id:mime-version; bh=S78y0w3pSOfOxG3e9wAuTYRlfcXRiO3tpuM2YXtWv9I=; b=fEHc+zBnTvDxOeWcALpdvbmFbomXSblAjE7SkyUGqhSM4IklFJDLHSZF BCCEtE3KSXFjkeTF/3ZTe5TxA1x6t4un0tSlmj9AIc9TwdXRee/41RhlZ pJS+cnqymprP/UhYeTJZUn7Vdbw9B1DhzItVcNeu5BA00YxXzUyMU9iHB Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0eAL6Gz1OtJV2U/2dsb2JhbABZgw7QTA9/FnaERD88NAV3iCe/GhePSx2EMAWKZpA/AZQ0g2Yd
X-IronPort-AV: E=Sophos;i="5.01,716,1400025600"; d="scan'208";a="342184556"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-5.cisco.com with ESMTP; 23 Jul 2014 10:00:27 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s6NA0Pvl016698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2014 10:00:26 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 s6NA0Kj4015171; Wed, 23 Jul 2014 03:00:25 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id s6NA0Jq5015169; Wed, 23 Jul 2014 03:00:19 -0700
Date: Wed, 23 Jul 2014 03:00:19 -0700
From: Toerless Eckert <eckert@cisco.com>
To: manet@ietf.org
Message-ID: <20140723100019.GK24330@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.2i
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/LYrFDHn2YDYPdZOTr5h8NnqWUjE
Cc: pim@ietf.org
Subject: [pim] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 10:00:32 -0000

Having not followed Manet for a couple of years, and sat in yesterdays
meeting, where there was a question about multicast,  some questions and
comments:

(1) It sounded to me as if every MANET solution support IP multicast
flooding, but thats pretty much it ? What for example would
be the solution for flooding when you use eg: OSPF with Manet
extensions ? SMF ?

(2) There seemed to be some interest in working on BTF (Metter Than
Flooding) IP multicast protocols (a), but also (b) some concerns about
work overload that this might result in for manet.

(2a) Is there any write down of use cases in Manet that require
such BTF IP multicast services with manet ? If yes, please provide
pointers, if not, i'd suggest that is the first thing to write down.

I got the understanding that eg: the evolution from SA (situation
awareness == very low bitrate) as the prime use case to also
voice/video group communication is such a typical use case for BTF 
multicast, but without it being written down and prioritized, it is
IMHO premature to proceed on protocol work.

And there is a lot more than just prioritization of work to get
from the use cases details. For example, since 2000, we do have
in the IETF two IP multicast service models. The traditional
group-join one, we now call ASM (Any Source Multicast), and
SSM, where the application has to know the source IP address,
and includes it in IGMP membership reports. SSM simplifies
BTF solutions drastical. It also increases security (not
attacks by unwanted sources). So the use case analysis needs to
vet whether SSM is an appropriate service or not for the use
case.

(2b) The routing ADs seem to be running around trying to do
load-balancing of work across WGs, so it might be feasible to
proceed with eg: protocol work for manet compatible IP multicast
in the IP Multicast WG (currently called PIM). From what i
could glean from Alias statements yesterday in PIM WG, they
where primarily thinking of bringing MPLS multicast over to the
Multicast WG, but i think one may want to consider Manet
multicast as well. Nevertheless, see (2a), use-cases should
IMHO be really owned by Manet-WG itself.

Cheers
    Toerless


From nobody Wed Jul 23 03:34:26 2014
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B596C1A03E0; Wed, 23 Jul 2014 03:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.395
X-Spam-Level: 
X-Spam-Status: No, score=-13.395 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 cMNQ4IeFl0MJ; Wed, 23 Jul 2014 03:34:17 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30E701A03DF; Wed, 23 Jul 2014 03:34:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3241; q=dns/txt; s=iport; t=1406111657; x=1407321257; h=date:from:to:cc:subject:message-id:mime-version; bh=vzqpCXTmNKCej3YWej1g+b6LkvFfmAkYK6bReRyXfZI=; b=TbxCHJcVZFT+Xuw7KREspBvPrP5Drqjd1ewMXmBrIl1C0PS8T0NQ7q6C vn/ylV9OF5pwPxJnFAWFTRl6RhjaxCohu7U/G4wQA+GOuRsiGqFt5N0Wj fC8+8IUhK4XjImfWdZ8pQCgkVGV9VZ4P3MLTDgS6FU+zKzsKbOVN98MlE E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsseAC2Pz1OtJA2N/2dsb2JhbABZgw6BKc8mD38WdoREPy0PNAU1JxuIJ78wF456AQFPhE0FimaQPwGUNINmHS+BDA
X-IronPort-AV: E=Sophos;i="5.01,716,1400025600"; d="scan'208";a="341991753"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-1.cisco.com with ESMTP; 23 Jul 2014 10:34:16 +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 s6NAYFcr016805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2014 10:34:16 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 s6NAYFij016321; Wed, 23 Jul 2014 03:34:15 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id s6NAYEEJ016320; Wed, 23 Jul 2014 03:34:14 -0700
Date: Wed, 23 Jul 2014 03:34:14 -0700
From: Toerless Eckert <eckert@cisco.com>
To: manet@ietf.org
Message-ID: <20140723103414.GM24330@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.2i
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/s1hJ8IQ6QBBZxWLewFYoiv1uWW4
Cc: pim@ietf.org
Subject: [pim] manet: draft-gerla-manet-odmrp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 10:34:21 -0000

Sorry, resending with correct recipients.

Some comments on subject draft, and maybe take this mail
also as helpfull to decide if/how PIM WG could help with Manet 
groups multicast interest:

(A) Nice simple looking IP multicast protocol. This is how
simple i remember the first versions of PIM to be, 20 years ago,
before proliferation, success and generations of implementers
eyeballs beat all necessary bug-fixes, oversight amendments and
optimizations into the current PIM RFCs. Now having said this:
The current PIM RFC 4601 is like C++ vs. Java: Remove 80%
from it and you have PIM-SSM, which is relevant here.

(B) Fundamentally, ODMRP is what PIM-SSM + draft-ietf-pim-source-discovery-bsr (SD-Draft)
with IMHO three main differences:

1) ODMRP does rely on some pre-existing flooding mechanism (eg: SMF)
for messages indicating what (S,G) are actively sending traffic.
(called "join request" in ODMRP, called SG mapping in SD-draft).

2) PIM-SSM (like all other variants of PIM) maintains an OIF-list
(Outgoing Interface list) to which received multicast packets are
replicated, and it eliminates loops/duplicate packets via
RPF-check. ODMRP proposes to transmit the packet to all interfaces,
(even though it could build an OIF list from received "join reply"),
and it uses duplicate packet detection instead of RPF check.

3) ODMRP uses "join reply" acknowledgements sent from the up
to the downstream router to detect unidirectional adjacencies,
and proposes to then use an ad-on draft (gerla-manet-odmrp-asym)
to make that work.

I think that these differences hardly justify inventing a new protocol
and going through all the trouble of (A). Instead i would strongly
suggest to consider adopting the solution worked on in PIM and
modify it accordingly:

- If existing MANET networks have working flooding solutions,
  they should of course be useable by the solution. SD-Draft
  was brought into IETF for networks that do not have any (like
  pretty much all non-MANET networks i know of).

- RPF-check vs duplicate-elimination and OIF-list vs
  all-interface-forwarding might be justified differences
  based on whether the interfaces is MANET or not. Aka: This
  doesn't have to be a network wide protocol behavior, but could
  be IIF/OIF-link properties of PIM - therefore also allowing very
  easily a mixed network with MANET and non-MANET parts. Instead of
  having to figure out how to interconnect PIM with a MANET
  specific protocol (interconnecting multicast protocols is always
  a pain).

  And of course, i think there should be more review if these two
  choices are actually the best for MANET. I understand some reasons
  why they are good, but i also have some more concerns there. I think 
  this shouldn't be too tough to work out.

- Unidirectional link support seems like an extension anyhow,
  we had done some work in products for non-MANET networks, i
  don't quite remember what made it through the IETF and what
  stayed in proprietary features, so i'll comment on this later.

Cheers
    Toerless


-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From nobody Wed Jul 23 04:00:28 2014
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 321691A0422; Wed, 23 Jul 2014 04:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 kSMzmGuVjGSu; Wed, 23 Jul 2014 03:59:53 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8974E1A0453; Wed, 23 Jul 2014 03:59:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1202; q=dns/txt; s=iport; t=1406113193; x=1407322793; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=NKYVQnKMzKzUJ34R9v1/L+MOqGcoto0pM1j+QRb1iXU=; b=ac+/VH+IuvJBdELfuuZ4v0FQnhWg/x11IjH1b015UZV5ujAEk8Ac+Fg+ ix8e71nmlDF5qracFIlHVEAQGtOuUcMvCszoHfmSIJxr5/nVrhL6mBNf2 CH8XkYA1dxzrdAzqe62ZieMbUly84i4+kxlwp8N2PnKmCLrthgXXtMDC5 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAJ6Uz1OtJV2T/2dsb2JhbABZgw6BKc8oAYENFnaEBAEBBDo/EAsOCgklDwVJExuIJ781F49LB4MugRgBBIpmkD8BlDSDZh0v
X-IronPort-AV: E=Sophos;i="5.01,716,1400025600"; d="scan'208";a="342197062"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-5.cisco.com with ESMTP; 23 Jul 2014 10:59:53 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s6NAxq5x015004 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2014 10:59:52 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 s6NAxpfZ017190; Wed, 23 Jul 2014 03:59:51 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id s6NAxpni017189; Wed, 23 Jul 2014 03:59:51 -0700
Date: Wed, 23 Jul 2014 03:59:51 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Henning Rogge <hrogge@gmail.com>
Message-ID: <20140723105951.GA17023@cisco.com>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/dxylp0NPWLDW5e5KCQMxMo2d5lw
Cc: MANET IETF <manet@ietf.org>, pim@ietf.org
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 11:00:03 -0000

Thanks, Henning,

I understand the partial-mesh properties of manet L2 subnets,
when i said flooding i was asking across a Manet L2 domain.

Also: what kernel ?

On Wed, Jul 23, 2014 at 12:36:50PM +0200, Henning Rogge wrote:
> On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrote:
> > Having not followed Manet for a couple of years, and sat in yesterdays
> > meeting, where there was a question about multicast,  some questions and
> > comments:
> >
> > (1) It sounded to me as if every MANET solution support IP multicast
> > flooding, but thats pretty much it ? What for example would
> > be the solution for flooding when you use eg: OSPF with Manet
> > extensions ? SMF ?
> 
> I think one main difference with MANET is that you have a
> non-transitive network... just because that you can hear someone on
> interface X does not mean all your neighbors on interface X can hear
> this station.
> 
> This means that multicast packets coming in through an interface
> typically have to be retransmitted through the same interface again.
> 
> I don't even know if there is any kind of kernel support for this kind
> of forwarding.
> 
> Henning Rogge


From nobody Wed Jul 23 05:00:47 2014
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58C6B1A0AF7; Wed, 23 Jul 2014 05:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 Vt1qb5Y33L_c; Wed, 23 Jul 2014 05:00:37 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AB131A066C; Wed, 23 Jul 2014 05:00:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3660; q=dns/txt; s=iport; t=1406116837; x=1407326437; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=dLFGn66ekIXeLSUv09UasRKjqsAJAb43jeaUcPkbtMQ=; b=jsjI6vh71tQsIgkeffVQ0VyRZjMNXk088jjaZzyf1x8Pk5FtMLJx5MBF 3TKsJ9gYTfdRAVVYaU3Kq5l6KLYHl6D7MG4ajvotmv+44iyXh8sc9ePiD BE/Y5y6UaK5baT+Wg6uwFlI/Dk0W1XUEH3etdYAFKj/lLsFxZ/Lh0a1cN M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFALeiz1OtJA2D/2dsb2JhbABZgw5SV8deCodFAYEOFnaEAwEBAQMBAQEBLwEiGQMIBQcECxEBAwEBAQkeBw8FEx8DBg4TG4gfCA2/NxeOaQoHAQlCBQcGgyiBGAWKZ4NCjQMBlECDaB0vgQMGAxc
X-IronPort-AV: E=Sophos;i="5.01,716,1400025600"; d="scan'208";a="342225788"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP; 23 Jul 2014 12:00:35 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s6NC0Yuc019315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2014 12:00:34 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 s6NC0XnF023670; Wed, 23 Jul 2014 05:00:33 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id s6NC0XYv023669; Wed, 23 Jul 2014 05:00:33 -0700
Date: Wed, 23 Jul 2014 05:00:33 -0700
From: Toerless Eckert <eckert@cisco.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Message-ID: <20140723120033.GB17023@cisco.com>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CFE435@GLKXM0002V.GREENLNK.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CFE435@GLKXM0002V.GREENLNK.net>
User-Agent: Mutt/1.4.2.2i
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/hYKcXlEwFBT5mIXtKpVuXU12XDw
Cc: MANET IETF <manet@ietf.org>, Henning Rogge <hrogge@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 12:00:43 -0000

On Wed, Jul 23, 2014 at 11:13:59AM +0000, Dearlove, Christopher (UK) wrote:
> They can't always be retransmitted through the same interface, you may need to use other interface(s) to reach the intended destinations.
> 
> When flooding (as SMF) you would naturally flood through all interfaces.

Well, "natural" flooding outside of MANET wold not send back to the
receiving interface. In Manet this seems to be necessary if the radio does
not do that for you.

> If building a tree you need to ensure the tree has bidirectional branches.

Well, i thought unidirectional link adjacencies are potentially important to
support. Likewise asymmetric links.

Cheers
    Toerless

> -- 
> Christopher Dearlove
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
> 
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
> 
> 
> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Henning Rogge
> Sent: 23 July 2014 11:37
> To: Toerless Eckert
> Cc: MANET IETF; pim@ietf.org
> Subject: Re: [manet] manet: IP multicast comments
> 
> ----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
> Consider carefully whether you should click on any links, open any attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.
> --------------------------------------------------------
> 
> On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrote:
> > Having not followed Manet for a couple of years, and sat in yesterdays 
> > meeting, where there was a question about multicast,  some questions 
> > and
> > comments:
> >
> > (1) It sounded to me as if every MANET solution support IP multicast 
> > flooding, but thats pretty much it ? What for example would be the 
> > solution for flooding when you use eg: OSPF with Manet extensions ? 
> > SMF ?
> 
> I think one main difference with MANET is that you have a non-transitive network... just because that you can hear someone on interface X does not mean all your neighbors on interface X can hear this station.
> 
> This means that multicast packets coming in through an interface typically have to be retransmitted through the same interface again.
> 
> I don't even know if there is any kind of kernel support for this kind of forwarding.
> 
> Henning Rogge
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
> 
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
> 

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From nobody Wed Jul 23 05:28:32 2014
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61D961B27D3; Wed, 23 Jul 2014 05:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.016
X-Spam-Level: 
X-Spam-Status: No, score=-13.016 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FAKE_REPLY_C=1.486, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 pu4OY5B7qlO1; Wed, 23 Jul 2014 05:28:29 -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 C65A31A0B05; Wed, 23 Jul 2014 05:28:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1643; q=dns/txt; s=iport; t=1406118509; x=1407328109; h=date:from:to:cc:subject:message-id:mime-version: in-reply-to; bh=2g9wT8+k/Zu7l+wpumdXhaphlwfX/rZKuhvjQZI/aaU=; b=lIdp9NxdKDpSB8FawkOdGw5W54N510lj9zv9NkeqXld2WfqwUE0ylLfG Xz641Il8+uB4iVx9lQodM0BHjBj4VPhDnh44ueTWRgkgVFH1NNv40FMAD t+IHNqqmh+nNzeHdxiwuSM2IwWnCU3DIyAxOUo4og+/GnP17nXFjjqzQt E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAG2pz1OtJA2H/2dsb2JhbABZgw6BKc8tAYELFnaEAwEBAQMBOj8FFhIGCTQFNRQTiDoIv14XjnoBAU8Hgy6BGAWKZ5BFAZRAg2gdL4EM
X-IronPort-AV: E=Sophos;i="5.01,717,1400025600"; d="scan'208";a="63304529"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-6.cisco.com with ESMTP; 23 Jul 2014 12:28:28 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s6NCSRD3014686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2014 12:28:28 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 s6NCSRox025652; Wed, 23 Jul 2014 05:28:27 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id s6NCSQdu025651; Wed, 23 Jul 2014 05:28:26 -0700
Date: Wed, 23 Jul 2014 05:28:26 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Message-ID: <20140723122826.GC17023@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADnDZ8-yD63UGsCoAC+4BwAB48NErR9DJV4+Nja-xN=hVTqU2w@mail.gmail.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/LO3ddgBcFugM8-X1C2MGdBTzAz4
Cc: manet@ietf.org, pim@ietf.org
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 12:28:30 -0000

On Wed, Jul 23, 2014 at 01:54:03PM +0200, Abdussalam Baryun wrote:
> On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrote:
> 
> >
> > (2b) The routing ADs seem to be running around trying to do
> > load-balancing of work across WGs, so it might be feasible to
> > proceed with eg: protocol work for manet compatible IP multicast
> > in the IP Multicast WG (currently called PIM). From what i
> > could glean from Alias statements yesterday in PIM WG, they
> > where primarily thinking of bringing MPLS multicast over to the
> > Multicast WG, but i think one may want to consider Manet
> > multicast as well. Nevertheless, see (2a), use-cases should
> > IMHO be really owned by Manet-WG itself.
> >
> The multicast routings in MANET is very different than PIM and MPLS.

Can you remember if that reasoning was ever brought before PIM WG ?

> They  have very very different use cases.

Adio/Video conferencing ? Sensoric (telemtry) data flooding ?
I'd be surprised if the use cases turn out to be justifying difference
in architecture. If at all, its the mobility.

> So I support that the WG works on manet
> multicast protocols after finishing unicast protocols. As we can now start
> working on a proactive multicast protocol as we finished OLSRv2. Reactive
> multicast should not be started/adopted until we do our AODVv2.

Any specific reasons to go first with a proactive protocol ?

Btw: It would really be good as i said in anothrer mail to evaluate
the applicability of SSM to the use cases because that allows for the
most simple proactive tree building.

Cheers
    Toerless


From nobody Wed Jul 23 05:38:38 2014
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DAB91B278C; Wed, 23 Jul 2014 05:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 3s9VUg2AanSB; Wed, 23 Jul 2014 05:38:32 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03F711B278B; Wed, 23 Jul 2014 05:38:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4454; q=dns/txt; s=iport; t=1406119112; x=1407328712; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=Y8BkgiCyMvybZYdLxIJmFwSDpazXS5t+ndlyrp7Ksiw=; b=beUMir1hjw1DIbD3jzyk2qs5Mgeun6kNqeyEnEiyOTYjgajpDxLIoECc 9DH/Doz3NDtx0Sx5lHaRFDs+sR5X3mQ6kR31964SQ9H/vfyVCgDCd/ra4 jBumWQZUDjYo+0pKEtwwAKkYNqWwg3IUaEMdUeHI9XFvxFBNhvZvjJuBd Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAFOrz1OtJA2B/2dsb2JhbABZgw5SV8deCodFAYELFnaEAwEBAQMBAQEBLwEiGQMIDAQLEQEDAQEBCR4HDwUTHwMGDhOIOggNv1QXjmkKBgIBCEIFBwaDKIEYBYpnkEUBlECDaB0vgQM
X-IronPort-AV: E=Sophos;i="5.01,717,1400025600"; d="scan'208";a="342014894"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-1.cisco.com with ESMTP; 23 Jul 2014 12:38:16 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s6NCcFNK022301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2014 12:38:15 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 s6NCcDET026186; Wed, 23 Jul 2014 05:38:14 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id s6NCcDNF026185; Wed, 23 Jul 2014 05:38:13 -0700
Date: Wed, 23 Jul 2014 05:38:13 -0700
From: Toerless Eckert <eckert@cisco.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Message-ID: <20140723123813.GD17023@cisco.com>
References: <CADnDZ8-yD63UGsCoAC+4BwAB48NErR9DJV4+Nja-xN=hVTqU2w@mail.gmail.com> <20140723122826.GC17023@cisco.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D00506@GLKXM0002V.GREENLNK.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D00506@GLKXM0002V.GREENLNK.net>
User-Agent: Mutt/1.4.2.2i
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/JsaIgdsRRFp7_gKsdc8WNdbI2PY
Cc: "manet@ietf.org" <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 12:38:34 -0000

On Wed, Jul 23, 2014 at 12:35:02PM +0000, Dearlove, Christopher (UK) wrote:
> It depends on whether one views multicast as something special to be done after unicast, or something different. In the former case, as we have a unicast proactive protocol but not a reactive protocol, doing proactive multicast first makes sense. In the latter case, not necessarily. Though there may be an argument that the proactive network is ready - and the unicast routing protocol has information to exploit.

Thats an engineerings "reuse of code" argument.

I was more thinking of use-case requirements. Reactive protocols tend to
have problems delivering first packets reliably unless you go through
additional hoops. Proactive protocols have problems avoiding unnecessary
state and therefore have possible negative scaling impacts to the applications.

Toerless

> -- 
> Christopher Dearlove
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
> 
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
> 
> 
> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Toerless Eckert
> Sent: 23 July 2014 13:28
> To: Abdussalam Baryun
> Cc: manet@ietf.org; pim@ietf.org
> Subject: Re: [manet] manet: IP multicast comments
> 
> ----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
> Consider carefully whether you should click on any links, open any attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.
> --------------------------------------------------------
> 
> On Wed, Jul 23, 2014 at 01:54:03PM +0200, Abdussalam Baryun wrote:
> > On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrote:
> > 
> > >
> > > (2b) The routing ADs seem to be running around trying to do 
> > > load-balancing of work across WGs, so it might be feasible to 
> > > proceed with eg: protocol work for manet compatible IP multicast in 
> > > the IP Multicast WG (currently called PIM). From what i could glean 
> > > from Alias statements yesterday in PIM WG, they where primarily 
> > > thinking of bringing MPLS multicast over to the Multicast WG, but i 
> > > think one may want to consider Manet multicast as well. 
> > > Nevertheless, see (2a), use-cases should IMHO be really owned by 
> > > Manet-WG itself.
> > >
> > The multicast routings in MANET is very different than PIM and MPLS.
> 
> Can you remember if that reasoning was ever brought before PIM WG ?
> 
> > They  have very very different use cases.
> 
> Adio/Video conferencing ? Sensoric (telemtry) data flooding ?
> I'd be surprised if the use cases turn out to be justifying difference in architecture. If at all, its the mobility.
> 
> > So I support that the WG works on manet multicast protocols after 
> > finishing unicast protocols. As we can now start working on a 
> > proactive multicast protocol as we finished OLSRv2. Reactive multicast 
> > should not be started/adopted until we do our AODVv2.
> 
> Any specific reasons to go first with a proactive protocol ?
> 
> Btw: It would really be good as i said in anothrer mail to evaluate the applicability of SSM to the use cases because that allows for the most simple proactive tree building.
> 
> Cheers
>     Toerless
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
> 
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************


From nobody Wed Jul 23 06:11:20 2014
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D64191B28BE; Wed, 23 Jul 2014 06:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 ljD6YxMPaAAv; Wed, 23 Jul 2014 06:11:05 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE2E01B28AF; Wed, 23 Jul 2014 06:11:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7288; q=dns/txt; s=iport; t=1406121064; x=1407330664; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=Co+cHA9O4BlbqfM3ggh3O4FdyYF/p3DAe664W/PKWYY=; b=iViR6YQDTobsAzQuAlQrq4nrACl7oUXWT1kXaSABFricUIOTk7RZ6GW1 d/r8irBNu3peQyAVKRkomiLyz+7MulaN+5aOMJGjC/SOpJOOFrdh62QnY FxRVODXJFwT3F04TTrmlWoXUfeHQPikgdEdSBETsOV3tLswbUvomdKis3 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAAm0z1OtJV2P/2dsb2JhbABZgw5SV8dfCodFAYELFnaEAwEBAQMBAQEBLwEiGQMIBQcECxEBAwEBAQkeBw8FEx8DBg4TiDoIDb9rF45pCgYCAQhCBQcGgyiBGAWKZ5BFAZRAg2gdL4ED
X-IronPort-AV: E=Sophos;i="5.01,717,1400025600"; d="scan'208";a="63325439"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-7.cisco.com with ESMTP; 23 Jul 2014 13:10:58 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s6NDAvBm013426 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2014 13:10:57 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 s6NDAuZJ028067; Wed, 23 Jul 2014 06:10:56 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id s6NDAua7028041; Wed, 23 Jul 2014 06:10:56 -0700
Date: Wed, 23 Jul 2014 06:10:56 -0700
From: Toerless Eckert <eckert@cisco.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Message-ID: <20140723131056.GE17023@cisco.com>
References: <CADnDZ8-yD63UGsCoAC+4BwAB48NErR9DJV4+Nja-xN=hVTqU2w@mail.gmail.com> <20140723122826.GC17023@cisco.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D00506@GLKXM0002V.GREENLNK.net> <20140723123813.GD17023@cisco.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D0254F@GLKXM0002V.GREENLNK.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D0254F@GLKXM0002V.GREENLNK.net>
User-Agent: Mutt/1.4.2.2i
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/IGhxk8iNQV3vb06yL8qjaoUccpQ
Cc: "manet@ietf.org" <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 13:11:15 -0000

On Wed, Jul 23, 2014 at 12:56:51PM +0000, Dearlove, Christopher (UK) wrote:
> I think that was more than a reuse of code argument, and if that's all you think it was, you've missed the point that it's about what networks might already exist.

Well, i read: If one views multicast as something special to be done after unicast,
and unicast is proactive, then doing proactive multicast first makes sense. You
didn't say whether this meant specs or deployment ;-)

Be that as it may: In non-manet networks, we always only had proactive unicast,
but that didn't stop us to do reactive and proactive multicast protocols, so i am
not sure what deploymnet or spec benefits i could have with that reasoning - unless
of course the multicast protocol is directly an extension of the unicast protocol.
That was the line of thinking up until 1994 when folks figured it doesn't make a
lot of sense trying to counterfit multicast into every IGP.

> But on your points, if there's already a proactive unicast protocol, you've already committed to much of the state. I also wouldn't call it unnecessary state, if it were unnecessary it wouldn't be collected. It's more a necessary evil to achieve your other objectives.

I as just talking about multicast state, not unicast state. Outside of
Manet, there are not a lot of folks interested in reactive unicast routing.

Cheers
    toerless

> -- 
> Christopher Dearlove
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
> 
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
> 
> 
> -----Original Message-----
> From: Toerless Eckert [mailto:eckert@cisco.com] 
> Sent: 23 July 2014 13:38
> To: Dearlove, Christopher (UK)
> Cc: Abdussalam Baryun; manet@ietf.org; pim@ietf.org
> Subject: Re: [manet] manet: IP multicast comments
> 
> ----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
> Consider carefully whether you should click on any links, open any attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.
> --------------------------------------------------------
> 
> On Wed, Jul 23, 2014 at 12:35:02PM +0000, Dearlove, Christopher (UK) wrote:
> > It depends on whether one views multicast as something special to be done after unicast, or something different. In the former case, as we have a unicast proactive protocol but not a reactive protocol, doing proactive multicast first makes sense. In the latter case, not necessarily. Though there may be an argument that the proactive network is ready - and the unicast routing protocol has information to exploit.
> 
> Thats an engineerings "reuse of code" argument.
> 
> I was more thinking of use-case requirements. Reactive protocols tend to have problems delivering first packets reliably unless you go through additional hoops. Proactive protocols have problems avoiding unnecessary state and therefore have possible negative scaling impacts to the applications.
> 
> Toerless
> 
> > --
> > Christopher Dearlove
> > Senior Principal Engineer, Information Assurance Group Communications, 
> > Networks and Image Analysis Capability BAE Systems Advanced Technology 
> > Centre West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> > Tel: +44 1245 242194 |  Fax: +44 1245 242124 
> > chris.dearlove@baesystems.com | http://www.baesystems.com
> > 
> > BAE Systems (Operations) Limited
> > Registered Office: Warwick House, PO Box 87, Farnborough Aerospace 
> > Centre, Farnborough, Hants, GU14 6YU, UK Registered in England & Wales 
> > No: 1996687
> > 
> > 
> > -----Original Message-----
> > From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Toerless 
> > Eckert
> > Sent: 23 July 2014 13:28
> > To: Abdussalam Baryun
> > Cc: manet@ietf.org; pim@ietf.org
> > Subject: Re: [manet] manet: IP multicast comments
> > 
> > ----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
> > Consider carefully whether you should click on any links, open any attachments or reply.
> > Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.
> > --------------------------------------------------------
> > 
> > On Wed, Jul 23, 2014 at 01:54:03PM +0200, Abdussalam Baryun wrote:
> > > On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrote:
> > > 
> > > >
> > > > (2b) The routing ADs seem to be running around trying to do 
> > > > load-balancing of work across WGs, so it might be feasible to 
> > > > proceed with eg: protocol work for manet compatible IP multicast 
> > > > in the IP Multicast WG (currently called PIM). From what i could 
> > > > glean from Alias statements yesterday in PIM WG, they where 
> > > > primarily thinking of bringing MPLS multicast over to the 
> > > > Multicast WG, but i think one may want to consider Manet multicast as well.
> > > > Nevertheless, see (2a), use-cases should IMHO be really owned by 
> > > > Manet-WG itself.
> > > >
> > > The multicast routings in MANET is very different than PIM and MPLS.
> > 
> > Can you remember if that reasoning was ever brought before PIM WG ?
> > 
> > > They  have very very different use cases.
> > 
> > Adio/Video conferencing ? Sensoric (telemtry) data flooding ?
> > I'd be surprised if the use cases turn out to be justifying difference in architecture. If at all, its the mobility.
> > 
> > > So I support that the WG works on manet multicast protocols after 
> > > finishing unicast protocols. As we can now start working on a 
> > > proactive multicast protocol as we finished OLSRv2. Reactive 
> > > multicast should not be started/adopted until we do our AODVv2.
> > 
> > Any specific reasons to go first with a proactive protocol ?
> > 
> > Btw: It would really be good as i said in anothrer mail to evaluate the applicability of SSM to the use cases because that allows for the most simple proactive tree building.
> > 
> > Cheers
> >     Toerless
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www.ietf.org/mailman/listinfo/manet
> > 
> > ********************************************************************
> > This email and any attachments are confidential to the intended 
> > recipient and may also be privileged. If you are not the intended 
> > recipient please delete it from your system and notify the sender.
> > You should not copy it or use it for any purpose nor disclose or 
> > distribute its contents to any other person.
> > ********************************************************************


From nobody Wed Jul 23 08:02:54 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32ECC1B28CF for <pim@ietfa.amsl.com>; Wed, 23 Jul 2014 08:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 qJoBdT0HMWo3 for <pim@ietfa.amsl.com>; Wed, 23 Jul 2014 08:02:49 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2::152:127]) by ietfa.amsl.com (Postfix) with ESMTP id AC4101B2862 for <pim@ietf.org>; Wed, 23 Jul 2014 08:02:49 -0700 (PDT)
Received: from [192.168.4.92] (69-165-189-130.dsl.teksavvy.com [69.165.189.130]) by ufisa.uninett.no (Postfix) with ESMTPSA id BFC6B80FC; Wed, 23 Jul 2014 17:02:47 +0200 (CEST)
Message-ID: <53CFCE94.2070705@venaas.com>
Date: Wed, 23 Jul 2014 08:02:44 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>, pim@ietf.org
References: <CAJgsEzX7+TO5=U__0D+8BfEZE6OZO-husTfjpCdsXPiTR+AwGA@mail.gmail.com>
In-Reply-To: <CAJgsEzX7+TO5=U__0D+8BfEZE6OZO-husTfjpCdsXPiTR+AwGA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/ly4GwFEQODbFT_N5DO2RyKyEHa8
Subject: Re: [pim] comment on draft-ietf-pim-source-discovery-bsr
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 15:02:52 -0000

Hi

On 7/22/2014 6:51 PM, Hermin Anggawijaya wrote:
> Would the draft benefit by allowing static (S,G, Holdtime) tuples to be
> configured at the FHR ? this way (listeners or) LHRs can send (S,G)
> joins before the first packet of real data is sent (and the SPTs from
> LHR to FHR are primed), thus allowing listeners that need first data
> packet to receive it properly. And if this can be included, maybe we
> need a way of marking the (S,G,Ht) as static config in the flooded
> source list.
>
> Of course I realise that the first packet issue can also be solved at
> the application layer, by  sources to send priming 'data' packets, but
> that's another story.
>
> I think the scenario is not unrealistic, since source addresses do not
> change that often and chances are the FHR is managed by the same admin
> managing the data sources ?

Thanks. Yes, that is a good point. We should mention that, and I might
also add this for the prototype implementation. It becomes a bit like
SSM mapping that some people configure then, except I agree it is better
to manage it at the first hop where the source actually is located.

Note that another option mentioned in the draft is to make use of
http://tools.ietf.org/html/draft-ietf-magma-msnip-06
but that requires host support for allowing an application to indicate
it wants to be a source.

Stig


> cheers
>
> Angga
>
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>


From nobody Thu Jul 24 12:05:42 2014
Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83EC61B2876; Wed, 23 Jul 2014 06:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.896
X-Spam-Level: 
X-Spam-Status: No, score=0.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no
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 OgOcSuBgBJkH; Wed, 23 Jul 2014 06:01:48 -0700 (PDT)
Received: from mail.tropicalstormsoftware.com (unknown [188.94.42.120]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CD881B2849; Wed, 23 Jul 2014 06:01:47 -0700 (PDT)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Wed, 23 Jul 2014 14:01:20 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Toerless Eckert <eckert@cisco.com>, "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Thread-Topic: [manet] manet: IP multicast comments
Thread-Index: AQHPplz4o8Gmx9Baj0uSrTWxqBdk+putfBqAgAAJnACAAAHYAIAAAOSAgAAV1hI=
Date: Wed, 23 Jul 2014 12:56:22 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801148DA64A@tss-server1.home.tropicalstormsoftware.com>
References: <CADnDZ8-yD63UGsCoAC+4BwAB48NErR9DJV4+Nja-xN=hVTqU2w@mail.gmail.com> <20140723122826.GC17023@cisco.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D00506@GLKXM0002V.GREENLNK.net>, <20140723123813.GD17023@cisco.com>
In-Reply-To: <20140723123813.GD17023@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/8ia_RDB9qMu3XOLty0lcIjnz8aM
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:34 -0700
Cc: "manet@ietf.org" <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 13:01:49 -0000

Toerless, et.al.,=0A=
=0A=
I think you might be talking yourself into writing an informational draft o=
n 'MANET considerations for multicast in reference to the existing state of=
 the art'.=0A=
=0A=
I think we are all agreeing that PIM has done some very good work that thos=
e of us in MANET are not aware of, but, as others have pointed out, the MAN=
ET group believe there are specific considerations for multicast in MANETs.=
=0A=
=0A=
I think analysis in this area is very necessary, before we start reinventin=
g each other's work.  Then it's just up to the AD's whether this happens in=
 MANET or PIM.=0A=
=0A=
Regards,=0A=
Rick Taylor=0A=
________________________________________=0A=
From: manet [manet-bounces@ietf.org] on behalf of Toerless Eckert [eckert@c=
isco.com]=0A=
Sent: 23 July 2014 13:38=0A=
To: Dearlove, Christopher (UK)=0A=
Cc: manet@ietf.org; pim@ietf.org=0A=
Subject: Re: [manet] manet: IP multicast comments=0A=
=0A=
On Wed, Jul 23, 2014 at 12:35:02PM +0000, Dearlove, Christopher (UK) wrote:=
=0A=
> It depends on whether one views multicast as something special to be done=
 after unicast, or something different. In the former case, as we have a un=
icast proactive protocol but not a reactive protocol, doing proactive multi=
cast first makes sense. In the latter case, not necessarily. Though there m=
ay be an argument that the proactive network is ready - and the unicast rou=
ting protocol has information to exploit.=0A=
=0A=
Thats an engineerings "reuse of code" argument.=0A=
=0A=
I was more thinking of use-case requirements. Reactive protocols tend to=0A=
have problems delivering first packets reliably unless you go through=0A=
additional hoops. Proactive protocols have problems avoiding unnecessary=0A=
state and therefore have possible negative scaling impacts to the applicati=
ons.=0A=
=0A=
Toerless=0A=
=0A=
> --=0A=
> Christopher Dearlove=0A=
> Senior Principal Engineer, Information Assurance Group=0A=
> Communications, Networks and Image Analysis Capability=0A=
> BAE Systems Advanced Technology Centre=0A=
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK=0A=
> Tel: +44 1245 242194 |  Fax: +44 1245 242124=0A=
> chris.dearlove@baesystems.com | http://www.baesystems.com=0A=
>=0A=
> BAE Systems (Operations) Limited=0A=
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
, Farnborough, Hants, GU14 6YU, UK=0A=
> Registered in England & Wales No: 1996687=0A=
>=0A=
>=0A=
> -----Original Message-----=0A=
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Toerless Eckert=
=0A=
> Sent: 23 July 2014 13:28=0A=
> To: Abdussalam Baryun=0A=
> Cc: manet@ietf.org; pim@ietf.org=0A=
> Subject: Re: [manet] manet: IP multicast comments=0A=
>=0A=
> ----------------------! WARNING ! ---------------------- This message ori=
ginates from outside our organisation, either from an external partner or f=
rom the internet.=0A=
> Consider carefully whether you should click on any links, open any attach=
ments or reply.=0A=
> Follow the 'Report Suspicious Emails' link on IT matters for instructions=
 on reporting suspicious email messages.=0A=
> --------------------------------------------------------=0A=
>=0A=
> On Wed, Jul 23, 2014 at 01:54:03PM +0200, Abdussalam Baryun wrote:=0A=
> > On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wr=
ote:=0A=
> >=0A=
> > >=0A=
> > > (2b) The routing ADs seem to be running around trying to do=0A=
> > > load-balancing of work across WGs, so it might be feasible to=0A=
> > > proceed with eg: protocol work for manet compatible IP multicast in=
=0A=
> > > the IP Multicast WG (currently called PIM). From what i could glean=
=0A=
> > > from Alias statements yesterday in PIM WG, they where primarily=0A=
> > > thinking of bringing MPLS multicast over to the Multicast WG, but i=
=0A=
> > > think one may want to consider Manet multicast as well.=0A=
> > > Nevertheless, see (2a), use-cases should IMHO be really owned by=0A=
> > > Manet-WG itself.=0A=
> > >=0A=
> > The multicast routings in MANET is very different than PIM and MPLS.=0A=
>=0A=
> Can you remember if that reasoning was ever brought before PIM WG ?=0A=
>=0A=
> > They  have very very different use cases.=0A=
>=0A=
> Adio/Video conferencing ? Sensoric (telemtry) data flooding ?=0A=
> I'd be surprised if the use cases turn out to be justifying difference in=
 architecture. If at all, its the mobility.=0A=
>=0A=
> > So I support that the WG works on manet multicast protocols after=0A=
> > finishing unicast protocols. As we can now start working on a=0A=
> > proactive multicast protocol as we finished OLSRv2. Reactive multicast=
=0A=
> > should not be started/adopted until we do our AODVv2.=0A=
>=0A=
> Any specific reasons to go first with a proactive protocol ?=0A=
>=0A=
> Btw: It would really be good as i said in anothrer mail to evaluate the a=
pplicability of SSM to the use cases because that allows for the most simpl=
e proactive tree building.=0A=
>=0A=
> Cheers=0A=
>     Toerless=0A=
>=0A=
> _______________________________________________=0A=
> manet mailing list=0A=
> manet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/manet=0A=
>=0A=
> ********************************************************************=0A=
> This email and any attachments are confidential to the intended=0A=
> recipient and may also be privileged. If you are not the intended=0A=
> recipient please delete it from your system and notify the sender.=0A=
> You should not copy it or use it for any purpose nor disclose or=0A=
> distribute its contents to any other person.=0A=
> ********************************************************************=0A=
=0A=
_______________________________________________=0A=
manet mailing list=0A=
manet@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/manet=0A=


From nobody Thu Jul 24 12:05:43 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1AC91A0303; Wed, 23 Jul 2014 03:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 eeieI38qotaP; Wed, 23 Jul 2014 03:37:11 -0700 (PDT)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A328C1A0030; Wed, 23 Jul 2014 03:37:11 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id j15so981638qaq.25 for <multiple recipients>; Wed, 23 Jul 2014 03:37:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RBobF0C4o9Sb/5IQIP6X+UXdvRSbgPKrnWxr+RM2Kg8=; b=aEluA9lbCU27rsfbl8aK8jN5aQOmgUK8LHsn9wi9f3XlaIgr9/R8xMEMRsi9IjMpqO gWrJ4bBExtWJJdyK5hSfFJQUz6EdbA1tv0pE6IF8mS2pJrUFmvoV0zORbw8oNKPhxa5T bSCeo3r9ZQrjP4TcDdP+bcEfGxF2kMW/Hpc4FkR1DyEb5zLJV0k8szLVODoJxNviFqqq tDAuDT4XizUhv5p7DYpd5cTtru7DWQ49BHwfkmHRKOQ7JgmE1oL2f9BrMO1XYS+HjnMl dJ0p9TjTrAfWOwA78mjxM/pmwwoi/8V+DWgaQ0155Fx3Z2c/+lq+MfzRpcOBdg82S2Wd sn+Q==
X-Received: by 10.224.96.137 with SMTP id h9mr574903qan.96.1406111830891; Wed, 23 Jul 2014 03:37:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.44.18 with HTTP; Wed, 23 Jul 2014 03:36:50 -0700 (PDT)
In-Reply-To: <20140723100019.GK24330@cisco.com>
References: <20140723100019.GK24330@cisco.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 23 Jul 2014 12:36:50 +0200
Message-ID: <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com>
To: Toerless Eckert <eckert@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/0LwYsE1luHYMqXLiHdO1Eozzy14
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:36 -0700
Cc: MANET IETF <manet@ietf.org>, pim@ietf.org
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 10:37:15 -0000

On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrote:
> Having not followed Manet for a couple of years, and sat in yesterdays
> meeting, where there was a question about multicast,  some questions and
> comments:
>
> (1) It sounded to me as if every MANET solution support IP multicast
> flooding, but thats pretty much it ? What for example would
> be the solution for flooding when you use eg: OSPF with Manet
> extensions ? SMF ?

I think one main difference with MANET is that you have a
non-transitive network... just because that you can hear someone on
interface X does not mean all your neighbors on interface X can hear
this station.

This means that multicast packets coming in through an interface
typically have to be retransmitted through the same interface again.

I don't even know if there is any kind of kernel support for this kind
of forwarding.

Henning Rogge


From nobody Thu Jul 24 12:05:45 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DDA61A01DC; Wed, 23 Jul 2014 04:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 QcM0wD8tr65l; Wed, 23 Jul 2014 04:03:06 -0700 (PDT)
Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EE801A0123; Wed, 23 Jul 2014 04:03:06 -0700 (PDT)
Received: by mail-qg0-f41.google.com with SMTP id q107so1166505qgd.28 for <multiple recipients>; Wed, 23 Jul 2014 04:03:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GZuMtXUYV/uBu1JND8AOv0ANrvU5fQqHjNgrf3fW9OU=; b=ig3usp+T4cjPjmwEHymfbursbBuWEqhtUAVzh0MaBOzHui4Byu20VBid2Z47FLDjTz yZir3LlPJyCcldRXouJqJJTDAh7RjQYUIXDR0UtquIEb9CGzE0x6oLaw8XImiEbikxv1 jEu7Kwo8mHtr4YzUMFXP6ebHEbe02LukrJOqWgi7mVdivuhadTX8EvEl3wGooo1EH757 9aRzHd4M2ZfGqMsBto5K7BmKoSkg3kblO6ykFuRmXBhO13DEGB5usO5albo0zPDMpfz2 43UshswSyiiY4DwRMTSJo76u0AVEoF2FtIPfPsr8rhjlvCbKHl4MPWPI7JmGogFLiB1+ U8SA==
X-Received: by 10.224.96.137 with SMTP id h9mr819463qan.96.1406113384236; Wed, 23 Jul 2014 04:03:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.44.18 with HTTP; Wed, 23 Jul 2014 04:02:44 -0700 (PDT)
In-Reply-To: <20140723105951.GA17023@cisco.com>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com> <20140723105951.GA17023@cisco.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 23 Jul 2014 13:02:44 +0200
Message-ID: <CAGnRvuoQsue2x3ZsDR2=Ch96XjmM3sYBW63_pdRmXxuh1qTYww@mail.gmail.com>
To: Toerless Eckert <eckert@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/Um76z1Cd8qPMKeRxqh6Dc6-cYww
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:36 -0700
Cc: MANET IETF <manet@ietf.org>, pim@ietf.org
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 11:03:12 -0000

On Wed, Jul 23, 2014 at 12:59 PM, Toerless Eckert <eckert@cisco.com> wrote:
> Also: what kernel ?

let me rephrase this to "Operation system support"...

Henning Rogge


From nobody Thu Jul 24 12:05:46 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B14A1A02EC; Wed, 23 Jul 2014 04:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.103
X-Spam-Level: 
X-Spam-Status: No, score=-4.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] 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 3Adc1kTlOYdZ; Wed, 23 Jul 2014 04:13:54 -0700 (PDT)
Received: from ukmta1.baesystems.com (unknown [20.133.0.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AAC21A0028; Wed, 23 Jul 2014 04:13:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,716,1400022000"; d="scan'208";a="460119525"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 23 Jul 2014 12:13:52 +0100
X-IronPort-AV: E=Sophos;i="5.01,716,1400022000"; d="scan'208";a="58749758"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 23 Jul 2014 12:13:59 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.210]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0174.001; Wed, 23 Jul 2014 12:14:00 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Henning Rogge <hrogge@gmail.com>, Toerless Eckert <eckert@cisco.com>
Thread-Topic: [manet] manet: IP multicast comments
Thread-Index: AQHPplz80GmLKmbrSk6wiZoicSy84ZutZocAgAAaRdA=
Date: Wed, 23 Jul 2014 11:13:59 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CFE435@GLKXM0002V.GREENLNK.net>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com>
In-Reply-To: <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/4P5CLvsz-bFCCXAnKb2jIsMT1w4
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:35 -0700
Cc: MANET IETF <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 11:13:56 -0000

They can't always be retransmitted through the same interface, you may need=
 to use other interface(s) to reach the intended destinations.

When flooding (as SMF) you would naturally flood through all interfaces. If=
 building a tree you need to ensure the tree has bidirectional branches.

-- =

Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Henning Rogge
Sent: 23 July 2014 11:37
To: Toerless Eckert
Cc: MANET IETF; pim@ietf.org
Subject: Re: [manet] manet: IP multicast comments

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrote:
> Having not followed Manet for a couple of years, and sat in yesterdays =

> meeting, where there was a question about multicast,  some questions =

> and
> comments:
>
> (1) It sounded to me as if every MANET solution support IP multicast =

> flooding, but thats pretty much it ? What for example would be the =

> solution for flooding when you use eg: OSPF with Manet extensions ? =

> SMF ?

I think one main difference with MANET is that you have a non-transitive ne=
twork... just because that you can hear someone on interface X does not mea=
n all your neighbors on interface X can hear this station.

This means that multicast packets coming in through an interface typically =
have to be retransmitted through the same interface again.

I don't even know if there is any kind of kernel support for this kind of f=
orwarding.

Henning Rogge

_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From nobody Thu Jul 24 12:05:47 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FBF51A009E; Wed, 23 Jul 2014 04:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 vX3I_kez2bnM; Wed, 23 Jul 2014 04:54:06 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF0DE1A008C; Wed, 23 Jul 2014 04:54:05 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id x13so1047216wgg.7 for <multiple recipients>; Wed, 23 Jul 2014 04:54:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cEAn4nj4ickosFjzqv+1dHf3WsD9uEsslzsfP10Nq8M=; b=FyEp/pFB+np56OjPI036Ei4ef2DOyP4i7lgQUC/EosvtA55Bdtg/TBX9WsQi/JhmKN JWMYFWCOLKhvGdJT5AlYCP74P9140L+VLVwSRM0knveUbFghTTWIq50RCrmTl8CvIxpn 11jklEj4vNysScBRI2Z4EgUzuuFbGzXt8GxZA7qjeuGdOrcD+OqZ/s2j2v3F+Rvl3jlG b7Gxda9BvMinNMyCqJs7JuDonCgDID8Q1SqnDJbcR8QVoN/wisOYgV7FvznWWz6UlvyT y/0A8nlAwltpger5biJQj4xyv9rJjl815q96dxt2pfn1IzVALyC8432zEa7DVLNVmqse +SjQ==
MIME-Version: 1.0
X-Received: by 10.180.81.103 with SMTP id z7mr23830325wix.23.1406116444096; Wed, 23 Jul 2014 04:54:04 -0700 (PDT)
Received: by 10.180.102.7 with HTTP; Wed, 23 Jul 2014 04:54:03 -0700 (PDT)
In-Reply-To: <20140723100019.GK24330@cisco.com>
References: <20140723100019.GK24330@cisco.com>
Date: Wed, 23 Jul 2014 13:54:03 +0200
Message-ID: <CADnDZ8-yD63UGsCoAC+4BwAB48NErR9DJV4+Nja-xN=hVTqU2w@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Toerless Eckert <eckert@cisco.com>
Content-Type: multipart/alternative; boundary=f46d044288cc29cf3604fedaffbe
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/RwtCzTo9p6sYK1IDTLoJhgOw25o
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:36 -0700
Cc: manet@ietf.org, pim@ietf.org
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 11:54:07 -0000

--f46d044288cc29cf3604fedaffbe
Content-Type: text/plain; charset=UTF-8

On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrote:

>
> (2b) The routing ADs seem to be running around trying to do
> load-balancing of work across WGs, so it might be feasible to
> proceed with eg: protocol work for manet compatible IP multicast
> in the IP Multicast WG (currently called PIM). From what i
> could glean from Alias statements yesterday in PIM WG, they
> where primarily thinking of bringing MPLS multicast over to the
> Multicast WG, but i think one may want to consider Manet
> multicast as well. Nevertheless, see (2a), use-cases should
> IMHO be really owned by Manet-WG itself.
>
The multicast routings in MANET is very different than PIM and MPLS. They
have very very different use cases. So I support that the WG works on manet
multicast protocols after finishing unicast protocols. As we can now start
working on a proactive multicast protocol as we finished OLSRv2. Reactive
multicast should not be started/adopted until we do our AODVv2.

AB

--f46d044288cc29cf3604fedaffbe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>=C2=A0</div>
<div class=3D"gmail_quote">On Wed, Jul 23, 2014 at 12:00 PM, Toerless Ecker=
t <span dir=3D"ltr">&lt;<a href=3D"mailto:eckert@cisco.com" target=3D"_blan=
k">eckert@cisco.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote"><br>(2b) The routing ADs seem to be r=
unning around trying to do<br>load-balancing of work across WGs, so it migh=
t be feasible to<br>
proceed with eg: protocol work for manet compatible IP multicast<br>in the =
IP Multicast WG (currently called PIM). From what i<br>could glean from Ali=
as statements yesterday in PIM WG, they<br>where primarily thinking of brin=
ging MPLS multicast over to the<br>
Multicast WG, but i think one may want to consider Manet<br>multicast as we=
ll. Nevertheless, see (2a), use-cases should<br>IMHO be really owned by Man=
et-WG itself.<br></blockquote>
<div>The multicast routings=C2=A0in MANET is very different than PIM and MP=
LS. They have very very different use cases. So I support that the WG works=
 on manet multicast protocols after finishing unicast protocols. As we can =
now start working on a proactive=C2=A0multicast protocol as we finished OLS=
Rv2. Reactive multicast should not be started/adopted until we do our AODVv=
2.</div>

<div>=C2=A0</div>
<div>AB=C2=A0</div>
<div>=C2=A0</div></div></div>

--f46d044288cc29cf3604fedaffbe--


From nobody Thu Jul 24 12:05:48 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B96E1A0AFE; Wed, 23 Jul 2014 05:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 pVXTuSdmyQuU; Wed, 23 Jul 2014 05:27:00 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 007B41A01D5; Wed, 23 Jul 2014 05:26:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,717,1400022000"; d="scan'208";a="388789007"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 23 Jul 2014 13:26:58 +0100
X-IronPort-AV: E=Sophos;i="5.01,717,1400022000"; d="scan'208";a="65785970"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasodc005.greenlnk.net with ESMTP; 23 Jul 2014 13:27:06 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.210]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.03.0174.001; Wed, 23 Jul 2014 13:27:05 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Toerless Eckert <eckert@cisco.com>
Thread-Topic: [manet] manet: IP multicast comments
Thread-Index: AQHPplz80GmLKmbrSk6wiZoicSy84ZutZocAgAAaRdD///0fgIAAFkeQ
Date: Wed, 23 Jul 2014 12:27:05 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D004C8@GLKXM0002V.GREENLNK.net>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CFE435@GLKXM0002V.GREENLNK.net> <20140723120033.GB17023@cisco.com>
In-Reply-To: <20140723120033.GB17023@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/zWaIMxhB8tbEV99iDy_ZkECYfAI
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:35 -0700
Cc: MANET IETF <manet@ietf.org>, Henning Rogge <hrogge@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 12:27:02 -0000

Radios tend to behave the way physics demands, and we can't stop then doing=
 inconvenient things. Though if we are clever we can use what they do to ad=
vantage.

Every MANET protocol in the WG does not supported unidirectional links. Tha=
t applies to NHDP, OLSRv2, SMF, AODVv2. Making a protocol work with unidire=
ctional links is not straightforward, given that the sender doesn't know if=
 it's a 1-directional link, or a 0-directional link. Blind flooding is the =
obvious exception that can take advantage of unidirectional links.

--=20
Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Toerless Eckert [mailto:eckert@cisco.com]=20
Sent: 23 July 2014 13:01
To: Dearlove, Christopher (UK)
Cc: Henning Rogge; MANET IETF; pim@ietf.org
Subject: Re: [manet] manet: IP multicast comments

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

On Wed, Jul 23, 2014 at 11:13:59AM +0000, Dearlove, Christopher (UK) wrote:
> They can't always be retransmitted through the same interface, you may ne=
ed to use other interface(s) to reach the intended destinations.
>=20
> When flooding (as SMF) you would naturally flood through all interfaces.

Well, "natural" flooding outside of MANET wold not send back to the receivi=
ng interface. In Manet this seems to be necessary if the radio does not do =
that for you.

> If building a tree you need to ensure the tree has bidirectional branches=
.

Well, i thought unidirectional link adjacencies are potentially important t=
o support. Likewise asymmetric links.

Cheers
    Toerless

> --
> Christopher Dearlove
> Senior Principal Engineer, Information Assurance Group Communications,=20
> Networks and Image Analysis Capability BAE Systems Advanced Technology=20
> Centre West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194=A0|  Fax: +44 1245 242124=20
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace=20
> Centre, Farnborough, Hants, GU14 6YU, UK Registered in England & Wales=20
> No: 1996687
>=20
>=20
> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Henning Rogge
> Sent: 23 July 2014 11:37
> To: Toerless Eckert
> Cc: MANET IETF; pim@ietf.org
> Subject: Re: [manet] manet: IP multicast comments
>=20
> ----------------------! WARNING ! ---------------------- This message ori=
ginates from outside our organisation, either from an external partner or f=
rom the internet.
> Consider carefully whether you should click on any links, open any attach=
ments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for instructions=
 on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrot=
e:
> > Having not followed Manet for a couple of years, and sat in=20
> > yesterdays meeting, where there was a question about multicast, =20
> > some questions and
> > comments:
> >
> > (1) It sounded to me as if every MANET solution support IP multicast=20
> > flooding, but thats pretty much it ? What for example would be the=20
> > solution for flooding when you use eg: OSPF with Manet extensions ?
> > SMF ?
>=20
> I think one main difference with MANET is that you have a non-transitive =
network... just because that you can hear someone on interface X does not m=
ean all your neighbors on interface X can hear this station.
>=20
> This means that multicast packets coming in through an interface typicall=
y have to be retransmitted through the same interface again.
>=20
> I don't even know if there is any kind of kernel support for this kind of=
 forwarding.
>=20
> Henning Rogge
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>=20
> ********************************************************************
> This email and any attachments are confidential to the intended=20
> recipient and may also be privileged. If you are not the intended=20
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or=20
> distribute its contents to any other person.
> ********************************************************************
>=20

--
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!



From nobody Thu Jul 24 12:05:49 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9082C1A0B05; Wed, 23 Jul 2014 05:34:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 nG9ma8DvyjIF; Wed, 23 Jul 2014 05:34:57 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E24A1B2858; Wed, 23 Jul 2014 05:34:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,717,1400022000"; d="scan'208";a="460155514"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 23 Jul 2014 13:34:55 +0100
X-IronPort-AV: E=Sophos;i="5.01,717,1400022000"; d="scan'208";a="58763607"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 23 Jul 2014 13:35:02 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.210]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0174.001; Wed, 23 Jul 2014 13:35:03 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Toerless Eckert <eckert@cisco.com>, Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: [manet] manet: IP multicast comments
Thread-Index: AQHPplz80GmLKmbrSk6wiZoicSy84ZutfBqAgAAJnACAABHZQA==
Date: Wed, 23 Jul 2014 12:35:02 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D00506@GLKXM0002V.GREENLNK.net>
References: <CADnDZ8-yD63UGsCoAC+4BwAB48NErR9DJV4+Nja-xN=hVTqU2w@mail.gmail.com> <20140723122826.GC17023@cisco.com>
In-Reply-To: <20140723122826.GC17023@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/cWZneTzs74ATj_7IZvEJ6u-aZsU
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:35 -0700
Cc: "manet@ietf.org" <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 12:34:59 -0000

It depends on whether one views multicast as something special to be done a=
fter unicast, or something different. In the former case, as we have a unic=
ast proactive protocol but not a reactive protocol, doing proactive multica=
st first makes sense. In the latter case, not necessarily. Though there may=
 be an argument that the proactive network is ready - and the unicast routi=
ng protocol has information to exploit.

-- =

Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Toerless Eckert
Sent: 23 July 2014 13:28
To: Abdussalam Baryun
Cc: manet@ietf.org; pim@ietf.org
Subject: Re: [manet] manet: IP multicast comments

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

On Wed, Jul 23, 2014 at 01:54:03PM +0200, Abdussalam Baryun wrote:
> On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wrot=
e:
> =

> >
> > (2b) The routing ADs seem to be running around trying to do =

> > load-balancing of work across WGs, so it might be feasible to =

> > proceed with eg: protocol work for manet compatible IP multicast in =

> > the IP Multicast WG (currently called PIM). From what i could glean =

> > from Alias statements yesterday in PIM WG, they where primarily =

> > thinking of bringing MPLS multicast over to the Multicast WG, but i =

> > think one may want to consider Manet multicast as well. =

> > Nevertheless, see (2a), use-cases should IMHO be really owned by =

> > Manet-WG itself.
> >
> The multicast routings in MANET is very different than PIM and MPLS.

Can you remember if that reasoning was ever brought before PIM WG ?

> They  have very very different use cases.

Adio/Video conferencing ? Sensoric (telemtry) data flooding ?
I'd be surprised if the use cases turn out to be justifying difference in a=
rchitecture. If at all, its the mobility.

> So I support that the WG works on manet multicast protocols after =

> finishing unicast protocols. As we can now start working on a =

> proactive multicast protocol as we finished OLSRv2. Reactive multicast =

> should not be started/adopted until we do our AODVv2.

Any specific reasons to go first with a proactive protocol ?

Btw: It would really be good as i said in anothrer mail to evaluate the app=
licability of SSM to the use cases because that allows for the most simple =
proactive tree building.

Cheers
    Toerless

_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From nobody Thu Jul 24 12:05:51 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE591B27A5; Wed, 23 Jul 2014 05:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 YXdTfXND6pHH; Wed, 23 Jul 2014 05:56:49 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E4BD1A0ADD; Wed, 23 Jul 2014 05:56:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,717,1400022000"; d="scan'208";a="388800730"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 23 Jul 2014 13:56:44 +0100
X-IronPort-AV: E=Sophos;i="5.01,717,1400022000"; d="scan'208";a="65792304"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 23 Jul 2014 13:56:51 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.210]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0174.001; Wed, 23 Jul 2014 13:56:51 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Toerless Eckert <eckert@cisco.com>
Thread-Topic: [manet] manet: IP multicast comments
Thread-Index: AQHPplz80GmLKmbrSk6wiZoicSy84ZutfBqAgAAJnACAABHZQP//8OKAgAAUdhA=
Date: Wed, 23 Jul 2014 12:56:51 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D0254F@GLKXM0002V.GREENLNK.net>
References: <CADnDZ8-yD63UGsCoAC+4BwAB48NErR9DJV4+Nja-xN=hVTqU2w@mail.gmail.com> <20140723122826.GC17023@cisco.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D00506@GLKXM0002V.GREENLNK.net> <20140723123813.GD17023@cisco.com>
In-Reply-To: <20140723123813.GD17023@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/A0uz4RfxoH-ZDk2bbJRghzog1eA
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:35 -0700
Cc: "manet@ietf.org" <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 12:56:51 -0000

I think that was more than a reuse of code argument, and if that's all you =
think it was, you've missed the point that it's about what networks might a=
lready exist. But on your points, if there's already a proactive unicast pr=
otocol, you've already committed to much of the state. I also wouldn't call=
 it unnecessary state, if it were unnecessary it wouldn't be collected. It'=
s more a necessary evil to achieve your other objectives.

--=20
Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Toerless Eckert [mailto:eckert@cisco.com]=20
Sent: 23 July 2014 13:38
To: Dearlove, Christopher (UK)
Cc: Abdussalam Baryun; manet@ietf.org; pim@ietf.org
Subject: Re: [manet] manet: IP multicast comments

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

On Wed, Jul 23, 2014 at 12:35:02PM +0000, Dearlove, Christopher (UK) wrote:
> It depends on whether one views multicast as something special to be done=
 after unicast, or something different. In the former case, as we have a un=
icast proactive protocol but not a reactive protocol, doing proactive multi=
cast first makes sense. In the latter case, not necessarily. Though there m=
ay be an argument that the proactive network is ready - and the unicast rou=
ting protocol has information to exploit.

Thats an engineerings "reuse of code" argument.

I was more thinking of use-case requirements. Reactive protocols tend to ha=
ve problems delivering first packets reliably unless you go through additio=
nal hoops. Proactive protocols have problems avoiding unnecessary state and=
 therefore have possible negative scaling impacts to the applications.

Toerless

> --
> Christopher Dearlove
> Senior Principal Engineer, Information Assurance Group Communications,=20
> Networks and Image Analysis Capability BAE Systems Advanced Technology=20
> Centre West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194=A0|  Fax: +44 1245 242124=20
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace=20
> Centre, Farnborough, Hants, GU14 6YU, UK Registered in England & Wales=20
> No: 1996687
>=20
>=20
> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Toerless=20
> Eckert
> Sent: 23 July 2014 13:28
> To: Abdussalam Baryun
> Cc: manet@ietf.org; pim@ietf.org
> Subject: Re: [manet] manet: IP multicast comments
>=20
> ----------------------! WARNING ! ---------------------- This message ori=
ginates from outside our organisation, either from an external partner or f=
rom the internet.
> Consider carefully whether you should click on any links, open any attach=
ments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for instructions=
 on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> On Wed, Jul 23, 2014 at 01:54:03PM +0200, Abdussalam Baryun wrote:
> > On Wed, Jul 23, 2014 at 12:00 PM, Toerless Eckert <eckert@cisco.com> wr=
ote:
> >=20
> > >
> > > (2b) The routing ADs seem to be running around trying to do=20
> > > load-balancing of work across WGs, so it might be feasible to=20
> > > proceed with eg: protocol work for manet compatible IP multicast=20
> > > in the IP Multicast WG (currently called PIM). From what i could=20
> > > glean from Alias statements yesterday in PIM WG, they where=20
> > > primarily thinking of bringing MPLS multicast over to the=20
> > > Multicast WG, but i think one may want to consider Manet multicast as=
 well.
> > > Nevertheless, see (2a), use-cases should IMHO be really owned by=20
> > > Manet-WG itself.
> > >
> > The multicast routings in MANET is very different than PIM and MPLS.
>=20
> Can you remember if that reasoning was ever brought before PIM WG ?
>=20
> > They  have very very different use cases.
>=20
> Adio/Video conferencing ? Sensoric (telemtry) data flooding ?
> I'd be surprised if the use cases turn out to be justifying difference in=
 architecture. If at all, its the mobility.
>=20
> > So I support that the WG works on manet multicast protocols after=20
> > finishing unicast protocols. As we can now start working on a=20
> > proactive multicast protocol as we finished OLSRv2. Reactive=20
> > multicast should not be started/adopted until we do our AODVv2.
>=20
> Any specific reasons to go first with a proactive protocol ?
>=20
> Btw: It would really be good as i said in anothrer mail to evaluate the a=
pplicability of SSM to the use cases because that allows for the most simpl=
e proactive tree building.
>=20
> Cheers
>     Toerless
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>=20
> ********************************************************************
> This email and any attachments are confidential to the intended=20
> recipient and may also be privileged. If you are not the intended=20
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or=20
> distribute its contents to any other person.
> ********************************************************************


From nobody Thu Jul 24 12:05:52 2014
Return-Path: <jpmacker@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BABB81B2887; Wed, 23 Jul 2014 07:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 m1ODnIkt4EIw; Wed, 23 Jul 2014 07:57:33 -0700 (PDT)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CD331B287A; Wed, 23 Jul 2014 07:57:33 -0700 (PDT)
Received: by mail-qg0-f53.google.com with SMTP id q107so1495083qgd.26 for <multiple recipients>; Wed, 23 Jul 2014 07:57:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CM7vKt7Cz+XvkDPpI1R465uFy7TXG1/RG8Ou/LWEht0=; b=KK4r5lytG1ZS42lNK2DHHQ74UESrgddDv8QAA8+6qAesjA36m9PlUHFQvQJDaHfT0M oi1TNiXcXbthEFNyrIkI8/k7DCdL8Fb79KAF1YLDT+H4EChCn/arZAIOtbku/4tAByLf gPe5zmIbh1zr8uxFWfa0voDA6SERUMjzb7+wxcxSrHM8LJgoKTiPgnu+fO69jCR3o8TB 2F5M3UAgmE06bdWs1MXhBa6GUYEdpnnU74HiLhInSHq5BEkvAQbtQ/bkVhCAsLiC5ojI N7CfcYHgUDBPPysb6DEXYpAa1rrW9jWc9JRc2T8dMg/5nLV8V6lMp5y5JT+NsebXjUb1 fquA==
MIME-Version: 1.0
X-Received: by 10.140.29.138 with SMTP id b10mr2831026qgb.15.1406127451946; Wed, 23 Jul 2014 07:57:31 -0700 (PDT)
Received: by 10.140.101.140 with HTTP; Wed, 23 Jul 2014 07:57:31 -0700 (PDT)
In-Reply-To: <20140723100019.GK24330@cisco.com>
References: <20140723100019.GK24330@cisco.com>
Date: Wed, 23 Jul 2014 10:57:31 -0400
Message-ID: <CAHA-Tp79SMqShTsmOujK7FwE+u8Nsn0eEYVt6b6G61ZpPxuHkA@mail.gmail.com>
From: Joseph Macker <jpmacker@gmail.com>
To: Toerless Eckert <eckert@cisco.com>
Content-Type: multipart/alternative; boundary=001a113a75a2484b5004fedd8fe8
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/ROlK7-YKuHjaBZMK8VnJyOot_y0
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:36 -0700
Cc: "manet@ietf.org" <manet@ietf.org>, pim@ietf.org
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 14:57:38 -0000

--001a113a75a2484b5004fedd8fe8
Content-Type: text/plain; charset=UTF-8

Toerless:

Thanks for your comments. Sorry rewinding the thread a bit for some
historical perspective in case it helps.

On Wed, Jul 23, 2014 at 6:00 AM, Toerless Eckert <eckert@cisco.com> wrote:

> Having not followed Manet for a couple of years, and sat in yesterdays
> meeting, where there was a question about multicast,  some questions and
> comments:
>
> (1) It sounded to me as if every MANET solution support IP multicast
> flooding, but thats pretty much it ? What for example would
> be the solution for flooding when you use eg: OSPF with Manet
> extensions ? SMF ?
>

Many moons ago the Manet WG rechartered to make  more focused engineering
progress in the unicast areas and optimized flooding areas. Years ago there
used to be a slew of group-specific multicast discussions, work (both
reactive and proactive),  and proposals including SSM-related ones,etc. In
the last several meetings there has been some revisiting of these older
ideas with IDs ODMRP and adaptive multicast (adapts between flooding and
path-optimization as convergence/reliability allows).  Both of the newer
IDs build off of progress made in other areas.

Related to your other above question there have been successful live
experiments with OSPF-Manet variants and SMF.  Where SMF shared the
optimized control plane info of OSPF-Manet, not saying this it the right
thing to use in many deployments but its been demonstrated.  Nonetheless,
SMF is intended to be a limited application case design.


> (2) There seemed to be some interest in working on BTF (Metter Than
> Flooding) IP multicast protocols (a), but also (b) some concerns about
> work overload that this might result in for manet.
>

I am perhaps less worried about workload but some have raised concerns
about technical engineering maturity.  I believe progress has been in some
areas here over the years and there is room for this but if pursued it has
to be scoped.


> (2a) Is there any write down of use cases in Manet that require
> such BTF IP multicast services with manet ? If yes, please provide
> pointers, if not, i'd suggest that is the first thing to write down.
>
> I got the understanding that eg: the evolution from SA (situation
> awareness == very low bitrate) as the prime use case to also
> voice/video group communication is such a typical use case for BTF
> multicast, but without it being written down and prioritized, it is
> IMHO premature to proceed on protocol work.
>

> And there is a lot more than just prioritization of work to get
> from the use cases details. For example, since 2000, we do have
> in the IETF two IP multicast service models. The traditional
> group-join one, we now call ASM (Any Source Multicast), and
> SSM, where the application has to know the source IP address,
> and includes it in IGMP membership reports. SSM simplifies
> BTF solutions drastical. It also increases security (not
> attacks by unwanted sources). So the use case analysis needs to
> vet whether SSM is an appropriate service or not for the use
> case.
>

Definitely good points before the "now old" rechartering these tradeoffs
were discussed alot within the manet community..  There was also an
"explicit group" multicast proposal as well as SSM discussions.  At that
time lots of manet people were also working with PIM solutions at least for
gatewaying,etc.

I think MANET includes a rich set of application needs and multicast is
very important. Pub/sub data services, streaming services, control,
discovery are potential examples.

We do need to discuss the models, but also the convergence/reliability
issues tend to dominate the manet /mesh specific tradeoff and design space
as well as the potentially the need for support mechanisms (e.g., dup
detection). So the specific design challenges are an important part of any
design here.


> (2b) The routing ADs seem to be running around trying to do
> load-balancing of work across WGs, so it might be feasible to
> proceed with eg: protocol work for manet compatible IP multicast
> in the IP Multicast WG (currently called PIM). From what i
> could glean from Alias statements yesterday in PIM WG, they
> where primarily thinking of bringing MPLS multicast over to the
> Multicast WG, but i think one may want to consider Manet
> multicast as well. Nevertheless, see (2a), use-cases should
> IMHO be really owned by Manet-WG itself.
>

Personally I have worked alot with variants of PIM in the past.  Especially
gatewaying to/from MANET type networks.  It would be good to have more
cross discussions.



> Cheers
>     Toerless
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--001a113a75a2484b5004fedd8fe8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Toerless:</div><div><br></div><div>Thanks for your co=
mments. Sorry rewinding the thread a bit for some historical perspective in=
 case it helps.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">
On Wed, Jul 23, 2014 at 6:00 AM, Toerless Eckert <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:eckert@cisco.com" target=3D"_blank">eckert@cisco.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex">
Having not followed Manet for a couple of years, and sat in yesterdays<br>
meeting, where there was a question about multicast, =C2=A0some questions a=
nd<br>
comments:<br>
<br>
(1) It sounded to me as if every MANET solution support IP multicast<br>
flooding, but thats pretty much it ? What for example would<br>
be the solution for flooding when you use eg: OSPF with Manet<br>
extensions ? SMF ?<br></blockquote><div><br></div><div>Many moons ago the M=
anet WG rechartered to make =C2=A0more focused engineering progress in the =
unicast areas and optimized flooding areas. Years ago there used to be a sl=
ew of group-specific multicast discussions, work (both reactive and proacti=
ve), =C2=A0and proposals including SSM-related ones,etc. In the last severa=
l meetings there has been some revisiting of these older ideas with IDs ODM=
RP and adaptive multicast (adapts between flooding and path-optimization as=
 convergence/reliability allows). =C2=A0Both of the newer IDs build off of =
progress made in other areas.</div>
<div><br></div><div>Related to your other above question there have been su=
ccessful live experiments with OSPF-Manet variants and SMF. =C2=A0Where SMF=
 shared the optimized control plane info of OSPF-Manet, not saying this it =
the right thing to use in many deployments but its been demonstrated. =C2=
=A0Nonetheless, SMF is intended to be a limited application case design.</d=
iv>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<br>
(2) There seemed to be some interest in working on BTF (Metter Than<br>
Flooding) IP multicast protocols (a), but also (b) some concerns about<br>
work overload that this might result in for manet.<br></blockquote><div><br=
></div><div>I am perhaps less worried about workload but some have raised c=
oncerns about technical engineering maturity. =C2=A0I believe progress has =
been in some areas here over the years and there is room for this but if pu=
rsued it has to be scoped.</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<br>
(2a) Is there any write down of use cases in Manet that require<br>
such BTF IP multicast services with manet ? If yes, please provide<br>
pointers, if not, i&#39;d suggest that is the first thing to write down.<br=
>
<br>
I got the understanding that eg: the evolution from SA (situation<br>
awareness =3D=3D very low bitrate) as the prime use case to also<br>
voice/video group communication is such a typical use case for BTF<br>
multicast, but without it being written down and prioritized, it is<br>
IMHO premature to proceed on protocol work.<br></blockquote><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;=
border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex=
">
<br>
And there is a lot more than just prioritization of work to get<br>
from the use cases details. For example, since 2000, we do have<br>
in the IETF two IP multicast service models. The traditional<br>
group-join one, we now call ASM (Any Source Multicast), and<br>
SSM, where the application has to know the source IP address,<br>
and includes it in IGMP membership reports. SSM simplifies<br>
BTF solutions drastical. It also increases security (not<br>
attacks by unwanted sources). So the use case analysis needs to<br>
vet whether SSM is an appropriate service or not for the use<br>
case.<br></blockquote><div><br></div><div>Definitely good points before the=
 &quot;now old&quot; rechartering these tradeoffs were discussed alot withi=
n the manet community.. =C2=A0There was also an &quot;explicit group&quot; =
multicast proposal as well as SSM discussions. =C2=A0At that time lots of m=
anet people were also working with PIM solutions at least for gatewaying,et=
c.</div>
<div><br></div><div>I think MANET includes a rich set of application needs =
and multicast is very important. Pub/sub data services, streaming services,=
 control, discovery are potential examples.</div><div><br></div><div>We do =
need to discuss the models, but also the convergence/reliability issues ten=
d to dominate the manet /mesh specific tradeoff and design space as well as=
 the potentially the need for support mechanisms (e.g., dup detection). So =
the specific design challenges are an important part of any design here.</d=
iv>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<br>
(2b) The routing ADs seem to be running around trying to do<br>
load-balancing of work across WGs, so it might be feasible to<br>
proceed with eg: protocol work for manet compatible IP multicast<br>
in the IP Multicast WG (currently called PIM). From what i<br>
could glean from Alias statements yesterday in PIM WG, they<br>
where primarily thinking of bringing MPLS multicast over to the<br>
Multicast WG, but i think one may want to consider Manet<br>
multicast as well. Nevertheless, see (2a), use-cases should<br>
IMHO be really owned by Manet-WG itself.<br></blockquote><div><br></div><di=
v>Personally I have worked alot with variants of PIM in the past. =C2=A0Esp=
ecially gatewaying to/from MANET type networks. =C2=A0It would be good to h=
ave more cross discussions.</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,=
204);border-left-style:solid;padding-left:1ex">
<br>
Cheers<br>
=C2=A0 =C2=A0 Toerless<br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div></div>

--001a113a75a2484b5004fedd8fe8--


From nobody Thu Jul 24 12:05:53 2014
Return-Path: <bsnyder@idirect.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 170371B2ADD; Wed, 23 Jul 2014 08:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 DXi1HKtdtNsO; Wed, 23 Jul 2014 08:26:17 -0700 (PDT)
Received: from ironport2.idirect.net (ironport2.dmz.idirect.net [198.180.159.30]) by ietfa.amsl.com (Postfix) with ESMTP id D98281B28D9; Wed, 23 Jul 2014 08:26:16 -0700 (PDT)
Received-SPF: None (ironport2.idirect.net: no sender authenticity information available from domain of bsnyder@idirect.net) identity=pra; client-ip=10.250.250.129; receiver=ironport2.idirect.net; envelope-from="bsnyder@idirect.net"; x-sender="bsnyder@idirect.net"; x-conformance=sidf_compatible
Received-SPF: Neutral (ironport2.idirect.net: domain of bsnyder@idirect.net does not assert whether or not 10.250.250.129 is permitted sender) identity=mailfrom; client-ip=10.250.250.129; receiver=ironport2.idirect.net; envelope-from="bsnyder@idirect.net"; x-sender="bsnyder@idirect.net"; x-conformance=sidf_compatible; x-record-type="v=spf1"
Received-SPF: None (ironport2.idirect.net: no sender authenticity information available from domain of postmaster@webmail.idirect.net) identity=helo; client-ip=10.250.250.129; receiver=ironport2.idirect.net; envelope-from="bsnyder@idirect.net"; x-sender="postmaster@webmail.idirect.net"; x-conformance=sidf_compatible
X-IronPort-AV: E=Sophos;i="5.01,718,1400040000";  d="scan'208";a="2535107"
Received: from unknown (HELO webmail.idirect.net) ([10.250.250.129]) by ironport2.idirect.net with ESMTP; 23 Jul 2014 11:26:16 -0400
Received: from VAUS-MBX03.idirect.net ([fe80::f4a3:646a:da7:39c9]) by VAUS-CASHUB02.idirect.net ([fe80::1134:c923:6861:3e3e%14]) with mapi id 14.02.0387.000; Wed, 23 Jul 2014 11:26:16 -0400
From: "Snyder, Brian" <bsnyder@idirect.net>
To: Henning Rogge <hrogge@gmail.com>, Toerless Eckert <eckert@cisco.com>
Thread-Topic: [manet] manet: IP multicast comments
Thread-Index: AQHPplz2bAAam/Fjsku64wVDLp7XuJutulkAgAALoHA=
Date: Wed, 23 Jul 2014 15:26:15 +0000
Message-ID: <84585478AABBBF4B9DF597FC0F84AF7343042E89@VAUS-MBX03.idirect.net>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com>
In-Reply-To: <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.250.250.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/kGMlGbEy7qFKI5rIfOw7uUuBIzs
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:35 -0700
Cc: MANET IETF <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 15:26:24 -0000

> I think one main difference with MANET is that you have a non-transitive =
network... just because that you can hear someone on interface X does not m=
ean all your neighbors on interface X can hear this station.
>This means that multicast packets coming in through an interface typically=
 have to be retransmitted through the same interface again.

I think if satellite is to be considered a use case for MANET then that can=
't be taken as a constant truth.  In satellite we aren't necessarily trying=
 to build MESH networks (in fact that is much less common) but we are still=
 interested in MANET to help us pass link state and we still have a lot of =
mobility (in terms of modems moving between beams / satellites while mobile=
).  So from a multicast requirement, we need there to be the notion on the =
hub side that all downstream (the broadcast outroute)  multicast is only ev=
er sent once, regardless of how many actual DLEP peers are established in t=
his direction.  If end devices use igmp, pim, etc to get upstream devices t=
o forward said multicast - great - the radio doesn't have to know or care s=
ince it's a broadcast - if anyone wants it at all, everyone else has the op=
portunity to see it for free.

In trying to unwrap the implementation I am familiar with from the standard=
 (thanks to many conversations on this list), I believe this may be possibl=
e in theory now. I was thinking one could setup one 'virtual' DLEP peer tha=
t registers for all multicast and broadcast mac address towards my radio.  =
That way my radio can then see all multicast to forward it, regardless of a=
ctual individual clients being subscribed or not. (or even *in network*).  =
  Is this understanding correct?

thanks,
brian


_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Jul 24 12:05:55 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0D21B2AEB; Wed, 23 Jul 2014 08:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 4oN84BCnkwUp; Wed, 23 Jul 2014 08:39:02 -0700 (PDT)
Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24B361A0058; Wed, 23 Jul 2014 08:39:02 -0700 (PDT)
Received: by mail-qg0-f54.google.com with SMTP id z60so1612936qgd.13 for <multiple recipients>; Wed, 23 Jul 2014 08:39:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=q/OGcPhFHtOjAUlcoKlGObMU915Z7bIcgNFFROPC5S8=; b=lX/P6iIXMip8Q86C0cQpjsHs+L5kquIlKBtIuZs3hczcU0csrbLMDPXYcymecOjcB8 IP0ombCNuYvapP2cvKoggXTLGcwrckKmY9yjnNeKQx9tpRCSxENdH+7o356y6tnZrHYV 2m5b7/AWK2De61kkEp/ej60onGOXvq/wYE9WVfC3J3iZmDDe9N26z/j9fG+/hBxrUGJG 4Q16JPzXNom40xLUvxBXyeUBdFK+cQL5v2PyUVHQhbnaRHGI4F5oDzG0s/TeWlDoxL1B 0L4Jm37GRzr/VrZzdQPcFdXTdAGzhknMsKrbndsTylW5zeF2J7HcfvkIbwxzr+7kN6h0 Ue7g==
X-Received: by 10.140.84.168 with SMTP id l37mr3229669qgd.104.1406129941360; Wed, 23 Jul 2014 08:39:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.44.18 with HTTP; Wed, 23 Jul 2014 08:38:41 -0700 (PDT)
In-Reply-To: <84585478AABBBF4B9DF597FC0F84AF7343042E89@VAUS-MBX03.idirect.net>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com> <84585478AABBBF4B9DF597FC0F84AF7343042E89@VAUS-MBX03.idirect.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 23 Jul 2014 17:38:41 +0200
Message-ID: <CAGnRvurbfcTetDjUs-EyUbPmottEUkrvcQweUY8qboig8PjjOw@mail.gmail.com>
To: "Snyder, Brian" <bsnyder@idirect.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/iRoDl9t_YLFkMrZvhZJF_0A1D40
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:36 -0700
Cc: Toerless Eckert <eckert@cisco.com>, MANET IETF <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 15:39:04 -0000

On Wed, Jul 23, 2014 at 5:26 PM, Snyder, Brian <bsnyder@idirect.net> wrote:
>> I think one main difference with MANET is that you have a non-transitive=
 network... just because that you can hear someone on interface X does not =
mean all your neighbors on interface X can hear this station.
>>This means that multicast packets coming in through an interface typicall=
y have to be retransmitted through the same interface again.
>
> I think if satellite is to be considered a use case for MANET then that c=
an't be taken as a constant truth.

Its a constant truth for MANET protocol design because its a common
thing in MANET deployments.

Satcom is already a special case (because there is a "special" node,
the hub), but even there the Satcom hub might be forced to retransmit
every multicast received over the satcom link because otherwise the
rest of the clients would not hear multicast from other clients.

>  In satellite we aren't necessarily trying to build MESH networks (in fac=
t that is much less common) but we are still interested in MANET to help us=
 pass link state and we still have a lot of mobility (in terms of modems mo=
ving between beams / satellites while mobile).  So from a multicast require=
ment, we need there to be the notion on the hub side that all downstream (t=
he broadcast outroute)  multicast is only ever sent once, regardless of how=
 many actual DLEP peers are established in this direction.  If end devices =
use igmp, pim, etc to get upstream devices to forward said multicast - grea=
t - the radio doesn't have to know or care since it's a broadcast - if anyo=
ne wants it at all, everyone else has the opportunity to see it for free.

> In trying to unwrap the implementation I am familiar with from the standa=
rd (thanks to many conversations on this list), I believe this may be possi=
ble in theory now. I was thinking one could setup one 'virtual' DLEP peer t=
hat registers for all multicast and broadcast mac address towards my radio.=
  That way my radio can then see all multicast to forward it, regardless of=
 actual individual clients being subscribed or not. (or even *in network*).=
    Is this understanding correct?

I think the idea with multicast and DLEP is that the radio will either
statically announce multicast MACs/IPs or eavesdrop on IGMP (ICMPv6)
messages and handle them internally. The routing agent then can use
them to fill the local arp table.

Your local radio might filter multicast traffic not meant for your
local router, but I think thats an implementation detail not set in
the draft.

Henning Rogge


From nobody Thu Jul 24 12:05:57 2014
Return-Path: <bsnyder@idirect.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B90CF1B2B78; Wed, 23 Jul 2014 10:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 z0a1nhMvZcY3; Wed, 23 Jul 2014 10:17:24 -0700 (PDT)
Received: from ironport.idirect.net (ironport.dmz.idirect.net [198.180.159.28]) by ietfa.amsl.com (Postfix) with ESMTP id A8A3E1A0270; Wed, 23 Jul 2014 10:16:40 -0700 (PDT)
Received-SPF: None (ironport.idirect.net: no sender authenticity information available from domain of bsnyder@idirect.net) identity=pra; client-ip=10.250.250.129; receiver=ironport.idirect.net; envelope-from="bsnyder@idirect.net"; x-sender="bsnyder@idirect.net"; x-conformance=sidf_compatible
Received-SPF: Neutral (ironport.idirect.net: domain of bsnyder@idirect.net does not assert whether or not 10.250.250.129 is permitted sender) identity=mailfrom; client-ip=10.250.250.129; receiver=ironport.idirect.net; envelope-from="bsnyder@idirect.net"; x-sender="bsnyder@idirect.net"; x-conformance=sidf_compatible; x-record-type="v=spf1"
Received-SPF: None (ironport.idirect.net: no sender authenticity information available from domain of postmaster@webmail.idirect.net) identity=helo; client-ip=10.250.250.129; receiver=ironport.idirect.net; envelope-from="bsnyder@idirect.net"; x-sender="postmaster@webmail.idirect.net"; x-conformance=sidf_compatible
X-IronPort-AV: E=Sophos;i="5.01,718,1400040000"; d="scan'208";a="11337673"
Received: from unknown (HELO webmail.idirect.net) ([10.250.250.129]) by ironport.idirect.net with ESMTP; 23 Jul 2014 13:16:40 -0400
Received: from VAUS-MBX03.idirect.net ([fe80::f4a3:646a:da7:39c9]) by VAUS-CASHUB02.idirect.net ([fe80::1134:c923:6861:3e3e%14]) with mapi id 14.02.0387.000; Wed, 23 Jul 2014 13:16:39 -0400
From: "Snyder, Brian" <bsnyder@idirect.net>
To: Henning Rogge <hrogge@gmail.com>
Thread-Topic: [manet] manet: IP multicast comments
Thread-Index: AQHPplz2bAAam/Fjsku64wVDLp7XuJutulkAgAALoHCAAEi2gP//1gfA
Date: Wed, 23 Jul 2014 17:16:38 +0000
Message-ID: <84585478AABBBF4B9DF597FC0F84AF7343042FCC@VAUS-MBX03.idirect.net>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com> <84585478AABBBF4B9DF597FC0F84AF7343042E89@VAUS-MBX03.idirect.net> <CAGnRvurbfcTetDjUs-EyUbPmottEUkrvcQweUY8qboig8PjjOw@mail.gmail.com>
In-Reply-To: <CAGnRvurbfcTetDjUs-EyUbPmottEUkrvcQweUY8qboig8PjjOw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.250.250.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/1ELmTX7kBBKQBeaQv7NPU_miW0c
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:36 -0700
Cc: Toerless Eckert <eckert@cisco.com>, MANET IETF <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 17:17:32 -0000

On Wed, Jul 23, 2014 at 5:26 PM, Snyder, Brian <bsnyder@idirect.net> wrote:
>>> I think one main difference with MANET is that you have a non-transitiv=
e network... just because that you can hear someone on interface X does not=
 mean all your neighbors on interface X can hear this station.
>>>This means that multicast packets coming in through an interface typical=
ly have to be retransmitted through the same interface again.

>> I think if satellite is to be considered a use case for MANET then that =
can't be taken as a constant truth.

>Its a constant truth for MANET protocol design because its a common thing =
in MANET deployments.

>Satcom is already a special case (because there is a "special" node, the h=
ub), but even there the Satcom hub might be forced to retransmit every mult=
icast received over the satcom link because otherwise the rest of the clien=
ts would not hear multicast from other clients.

Whilst that is true... it is very common in satellite products (at least in=
 my experience) that the radio will hairpin inroute multicast traffic if it=
 is so configured to do so.  However, inroute multicast is quite rare of a =
use case in actuality.  Outroute multicast is very common as the broadcast =
nature of the medium blends beautifully to this use case.  In fact many cus=
tomers solely buy sat for multicast overlay. (However, that's not the MANET=
 use case).=20

What I was very concerned with was routers thinking each peer is its own in=
terface and replicating a downstream packet X times.  That can't be allowed=
 to happen - but again, it's likely this is just a function of the equipmen=
t I've been exposed too (or my own misunderstandings) and not actually expe=
cted by the design.



>>  In satellite we aren't necessarily trying to build MESH networks (in fa=
ct that is much less common) but we are still interested in MANET to help u=
s pass link state and we still have a lot of mobility (in terms of modems m=
oving between beams / satellites while mobile).  So from a multicast requir=
ement, we need there to be the notion on the hub side that all downstream (=
the broadcast outroute)  multicast is only ever sent once, regardless of ho=
w many actual DLEP peers are established in this direction.  If end devices=
 use igmp, pim, etc to get upstream devices to forward said multicast - gre=
at - the radio doesn't have to know or care since it's a broadcast - if any=
one wants it at all, everyone else has the opportunity to see it for free.

>> In trying to unwrap the implementation I am familiar with from the stand=
ard (thanks to many conversations on this list), I believe this may be poss=
ible in theory now. I was thinking one could setup one 'virtual' DLEP peer =
that registers for all multicast and broadcast mac address towards my radio=
.  That way my radio can then see all multicast to forward it, regardless o=
f actual individual clients being subscribed or not. (or even *in network*)=
.    Is this understanding correct?

>I think the idea with multicast and DLEP is that the radio will either sta=
tically announce multicast MACs/IPs or eavesdrop on IGMP (ICMPv6) messages =
and handle them internally. The routing agent then can use them to fill the=
 local arp table.

>Your local radio might filter multicast traffic not meant for your local r=
outer, but I think thats an implementation detail not set in the draft.

Fair enough. Is there anything against the "rules" if one managed multicast=
 membership completely outside the notion of DLEP?  There is still a physic=
al interface (in our case a VLAN trunk port), and I would be happy to have =
that interface decide weather or not to forward multicast with no too littl=
e concern about modem status....  there is some persistent multicast I want=
 to send regardless of DLEP's opinion of spokes being in or out of network.=
 (There is station keeping multicast that must flow even if there are 0 'in=
-network' spokes).

thanks for the discussion,
brian

Henning Rogge


From nobody Thu Jul 24 12:05:59 2014
Return-Path: <shawn.jury@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B471B2A16; Wed, 23 Jul 2014 10:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 UFMK4vfuBWL5; Wed, 23 Jul 2014 10:48:49 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B89D1A02D4; Wed, 23 Jul 2014 10:48:48 -0700 (PDT)
Received: by mail-ig0-f179.google.com with SMTP id h18so1721636igc.12 for <multiple recipients>; Wed, 23 Jul 2014 10:48:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=aqBMNbcEUbxmfrnthpP2bOVlfCFgD8CkVKG+5yxqE0s=; b=JeZ3ZHq0Bh0fUNTc58iqc7cevfg/21xOPglNLXbAZCp2Xf3fpd0F6OeJhv3RxaUXvW lxN+ZC/hG9N8CPbrU883BfzTUhRwaB32PrSvrMPXpyzQny62GxjiFgTbYhRW4w3lCkOr j0F7HLGrIaLzw9e0uL0I/p/4fck+/2OedqOwINWTWniYB0jgPJ+ze023W4hKX6OmWpgX UssUVZPvps7JY9LYBkzy5Kzb2tQTAoPxXENHhvvdSoS3KQ8pExmyADWt1EfgW9lpYHDJ rvAlhxmbW6mtDt6fkFeg7157JXGmuKQZcjYXjtKVhK6Fjw0QOGWx1MZflOkwFzZ2G3Mo lMOg==
X-Received: by 10.50.87.98 with SMTP id w2mr6175160igz.34.1406137727582; Wed, 23 Jul 2014 10:48:47 -0700 (PDT)
Received: from [10.2.2.8] (dynamic-acs-24-144-141-5.zoominternet.net. [24.144.141.5]) by mx.google.com with ESMTPSA id z8sm61487012igl.20.2014.07.23.10.48.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jul 2014 10:48:47 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Shawn Jury <shawn.jury@gmail.com>
In-Reply-To: <84585478AABBBF4B9DF597FC0F84AF7343042FCC@VAUS-MBX03.idirect.net>
Date: Wed, 23 Jul 2014 13:48:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB5F4C39-ED5E-440C-B97A-A81BA6388E69@gmail.com>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com> <84585478AABBBF4B9DF597FC0F84AF7343042E89@VAUS-MBX03.idirect.net> <CAGnRvurbfcTetDjUs-EyUbPmottEUkrvcQweUY8qboig8PjjOw@mail.gmail.com> <84585478AABBBF4B9DF597FC0F84AF7343042FCC@VAUS-MBX03.idirect.net>
To: "Snyder, Brian" <bsnyder@idirect.net>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/xWzWkcFDn9kWBqTccVdpVK-VVCY
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:35 -0700
Cc: MANET IETF <manet@ietf.org>, Henning Rogge <hrogge@gmail.com>, "pim@ietf.org" <pim@ietf.org>, Shawn Jury <shawn.jury@gmail.com>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 17:48:52 -0000

Brian,

On Jul 23, 2014, at 1:16 PM, Snyder, Brian wrote:

>=20
> On Wed, Jul 23, 2014 at 5:26 PM, Snyder, Brian <bsnyder@idirect.net> =
wrote:
>>>> I think one main difference with MANET is that you have a =
non-transitive network... just because that you can hear someone on =
interface X does not mean all your neighbors on interface X can hear =
this station.
>>>> This means that multicast packets coming in through an interface =
typically have to be retransmitted through the same interface again.
>=20
>>> I think if satellite is to be considered a use case for MANET then =
that can't be taken as a constant truth.
>=20
>> Its a constant truth for MANET protocol design because its a common =
thing in MANET deployments.
>=20
>> Satcom is already a special case (because there is a "special" node, =
the hub), but even there the Satcom hub might be forced to retransmit =
every multicast received over the satcom link because otherwise the rest =
of the clients would not hear multicast from other clients.
>=20
> Whilst that is true... it is very common in satellite products (at =
least in my experience) that the radio will hairpin inroute multicast =
traffic if it is so configured to do so.  However, inroute multicast is =
quite rare of a use case in actuality.  Outroute multicast is very =
common as the broadcast nature of the medium blends beautifully to this =
use case.  In fact many customers solely buy sat for multicast overlay. =
(However, that's not the MANET use case).=20
>=20
> What I was very concerned with was routers thinking each peer is its =
own interface and replicating a downstream packet X times.  That can't =
be allowed to happen - but again, it's likely this is just a function of =
the equipment I've been exposed too (or my own misunderstandings) and =
not actually expected by the design.
>=20
>=20

=46rom the draft point of view, DLEP supports multicast as a destination =
so metrics can be applied.  This allows other functionality like =
rate-limiting/shaping for a multicast group(s), but these are outside =
the scope of the DLEP draft.  DLEP doesn't replicate multicast packets =
(again, outside the scope), it assumes the router will take care of =
that.  Even with the implementation you played with, that was the case.  =
As I offered before off-list (and Stan has too), I'd be happy to help =
you better understand how the implementation works, but it not something =
to discuss on the IETF alias as it is a Cisco specific implementation.

This isn't the first time I've heard this mis-interpretation of the DLEP =
spec, wrt how we treat DLEP destinations.  DLEP destinations are used to =
associate metrics about the RF quality.  DLEP destinations can be =
physical (as in a router on the remote side) or logical (ie multicast =
group).  There is no point-to-point connection made between these =
devices.  Even if the router implementation makes use of virtual =
interfaces, the underlying radio protocol is assumed (and must be =
treated) to be broadcast.  I would argue that if you have an =
implementation that doesn't treat the RF as broadcast and makes =
point-to-point links instead, it is not following the DLEP spec =
correctly.  This is the only way I could see multicast packets being =
replicated by a router.  Please help me to understand if there is a =
different view on this.

>=20
>>> In satellite we aren't necessarily trying to build MESH networks (in =
fact that is much less common) but we are still interested in MANET to =
help us pass link state and we still have a lot of mobility (in terms of =
modems moving between beams / satellites while mobile).  So from a =
multicast requirement, we need there to be the notion on the hub side =
that all downstream (the broadcast outroute)  multicast is only ever =
sent once, regardless of how many actual DLEP peers are established in =
this direction.  If end devices use igmp, pim, etc to get upstream =
devices to forward said multicast - great - the radio doesn't have to =
know or care since it's a broadcast - if anyone wants it at all, =
everyone else has the opportunity to see it for free.
>=20
>>> In trying to unwrap the implementation I am familiar with from the =
standard (thanks to many conversations on this list), I believe this may =
be possible in theory now. I was thinking one could setup one 'virtual' =
DLEP peer that registers for all multicast and broadcast mac address =
towards my radio.  That way my radio can then see all multicast to =
forward it, regardless of actual individual clients being subscribed or =
not. (or even *in network*).    Is this understanding correct?
>=20
>> I think the idea with multicast and DLEP is that the radio will =
either statically announce multicast MACs/IPs or eavesdrop on IGMP =
(ICMPv6) messages and handle them internally. The routing agent then can =
use them to fill the local arp table.
>=20
>> Your local radio might filter multicast traffic not meant for your =
local router, but I think thats an implementation detail not set in the =
draft.
>=20
> Fair enough. Is there anything against the "rules" if one managed =
multicast membership completely outside the notion of DLEP?  There is =
still a physical interface (in our case a VLAN trunk port), and I would =
be happy to have that interface decide weather or not to forward =
multicast with no too little concern about modem status....  there is =
some persistent multicast I want to send regardless of DLEP's opinion of =
spokes being in or out of network. (There is station keeping multicast =
that must flow even if there are 0 'in-network' spokes).
>=20

Nothing states you have to use DLEP to manage multicast.  DLEP has the =
capability so that you can help reduce the amount of traffic sent (as =
mentioned above) for those radios that might have a different mechanism =
for sending multicast.  The ROUTER controls what multicast groups are =
being sent to the radio/modem.  If the ROUTER believes that a group has =
joined on the interface, it will send the packet out the interface =
(purposely left generic as there are many ways the ROUTER could learn =
about a group).

Shawn =20

> thanks for the discussion,
> brian
>=20
> Henning Rogge
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Jul 24 12:06:00 2014
Return-Path: <sratliff@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF38A1A083D; Wed, 23 Jul 2014 11:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 ZVe4KxAEuh9M; Wed, 23 Jul 2014 11:00:49 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D27FD1B2A22; Wed, 23 Jul 2014 10:59:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7630; q=dns/txt; s=iport; t=1406138400; x=1407348000; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=HB7gJspBkCiOJfC4alCfsEaX0ZoV0t1cdt14OZuj6u0=; b=TRJH0oFH/xMHV1ED0SbXdEdpEcrSu8yqMqN+z12r2xcLjG8sZ6X/Ety+ /q6OAfMR4ZvS71FdCwxX9nflOcgj55C43kHJqB5S7ZX9fG8kIW3PtNHcq qe1Tx8hWhNKo15E0HisoMr3wpDinECjbH4HXUl62HCjh9UuNKvX4cdPcx I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAO73z1OtJA2L/2dsb2JhbABPCoMOUlcEx1sKh0UBgQsWdoQDAQEBAwEBAQE3NAIJBQsCAQgYHhAhBgslAgQOBYguAwkIDbkCDYcUEwSJfoMggVEpMweDLoEYBZkqggOOIoYeg0hsgUU
X-IronPort-AV: E=Sophos;i="5.01,718,1400025600"; d="scan'208";a="63408331"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-3.cisco.com with ESMTP; 23 Jul 2014 17:59:37 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s6NHxaGs006735 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 23 Jul 2014 17:59:36 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.216]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Wed, 23 Jul 2014 12:59:36 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Shawn Jury <shawn.jury@gmail.com>
Thread-Topic: [manet] manet: IP multicast comments
Thread-Index: AQHPpl0AK+IXaCp+3EmPKrn2532hR5utyx0AgABQ3ICAAAN6gIAAG14AgAAI+YCAAAMFAA==
Date: Wed, 23 Jul 2014 17:59:35 +0000
Message-ID: <E052352F-958C-4526-B584-4CF9D5CF17E5@cisco.com>
References: <20140723100019.GK24330@cisco.com> <CAGnRvur40S-sJUHNzkAHf=cDDUyciTkLaVp5gzJOaFagudKokA@mail.gmail.com> <84585478AABBBF4B9DF597FC0F84AF7343042E89@VAUS-MBX03.idirect.net> <CAGnRvurbfcTetDjUs-EyUbPmottEUkrvcQweUY8qboig8PjjOw@mail.gmail.com> <84585478AABBBF4B9DF597FC0F84AF7343042FCC@VAUS-MBX03.idirect.net> <DB5F4C39-ED5E-440C-B97A-A81BA6388E69@gmail.com>
In-Reply-To: <DB5F4C39-ED5E-440C-B97A-A81BA6388E69@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.102.40.190]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <64F4CCD4B12FD9459A3824FB1F845BA1@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/WqLQIgs21HBDW7Qi4YK47wESyX8
X-Mailman-Approved-At: Thu, 24 Jul 2014 12:05:36 -0700
Cc: "Snyder, Brian" <bsnyder@idirect.net>, MANET IETF <manet@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] [manet] manet: IP multicast comments
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 18:00:56 -0000

On Jul 23, 2014, at 1:48 PM, Shawn Jury <shawn.jury@gmail.com> wrote:

> Brian,
>=20
> On Jul 23, 2014, at 1:16 PM, Snyder, Brian wrote:
>=20
>>=20
>> On Wed, Jul 23, 2014 at 5:26 PM, Snyder, Brian <bsnyder@idirect.net> wro=
te:
>>>>> I think one main difference with MANET is that you have a non-transit=
ive network... just because that you can hear someone on interface X does n=
ot mean all your neighbors on interface X can hear this station.
>>>>> This means that multicast packets coming in through an interface typi=
cally have to be retransmitted through the same interface again.
>>=20
>>>> I think if satellite is to be considered a use case for MANET then tha=
t can't be taken as a constant truth.
>>=20
>>> Its a constant truth for MANET protocol design because its a common thi=
ng in MANET deployments.
>>=20
>>> Satcom is already a special case (because there is a "special" node, th=
e hub), but even there the Satcom hub might be forced to retransmit every m=
ulticast received over the satcom link because otherwise the rest of the cl=
ients would not hear multicast from other clients.
>>=20
>> Whilst that is true... it is very common in satellite products (at least=
 in my experience) that the radio will hairpin inroute multicast traffic if=
 it is so configured to do so.  However, inroute multicast is quite rare of=
 a use case in actuality.  Outroute multicast is very common as the broadca=
st nature of the medium blends beautifully to this use case.  In fact many =
customers solely buy sat for multicast overlay. (However, that's not the MA=
NET use case).=20
>>=20
>> What I was very concerned with was routers thinking each peer is its own=
 interface and replicating a downstream packet X times.  That can't be allo=
wed to happen - but again, it's likely this is just a function of the equip=
ment I've been exposed too (or my own misunderstandings) and not actually e=
xpected by the design.
>>=20
>>=20
>=20
> From the draft point of view, DLEP supports multicast as a destination so=
 metrics can be applied.  This allows other functionality like rate-limitin=
g/shaping for a multicast group(s), but these are outside the scope of the =
DLEP draft.  DLEP doesn't replicate multicast packets (again, outside the s=
cope), it assumes the router will take care of that.  Even with the impleme=
ntation you played with, that was the case.  As I offered before off-list (=
and Stan has too), I'd be happy to help you better understand how the imple=
mentation works, but it not something to discuss on the IETF alias as it is=
 a Cisco specific implementation.
>=20
> This isn't the first time I've heard this mis-interpretation of the DLEP =
spec, wrt how we treat DLEP destinations.  DLEP destinations are used to as=
sociate metrics about the RF quality.  DLEP destinations can be physical (a=
s in a router on the remote side) or logical (ie multicast group).  There i=
s no point-to-point connection made between these devices.  Even if the rou=
ter implementation makes use of virtual interfaces, the underlying radio pr=
otocol is assumed (and must be treated) to be broadcast.  I would argue tha=
t if you have an implementation that doesn't treat the RF as broadcast and =
makes point-to-point links instead, it is not following the DLEP spec corre=
ctly.  This is the only way I could see multicast packets being replicated =
by a router.  Please help me to understand if there is a different view on =
this.

Ditto what Shawn said - Multicast packet replication is required if you're =
using a technique like RFC 5578 (for example), but that's got *everything* =
to do with the PPPoE underpinnings, and *nothing* to do with the link varia=
bility. DLEP treats a multicast group as another logical destination in the=
 network, so that metrics for the logical destination (group) can be report=
ed by the modem, and so that (potentially) a router can make a request via =
Link Characteristics Request for data rate, or latency. The "Destination Up=
" DLEP signal can flow in either direction (e.g. Modem-to-Router, or Router=
-to-Modem) so that either DLEP participant can identify the existence of a =
new destination (e.g. a new multicast group). There's nothing in the DLEP s=
pec referencing multicast replication, because it's not necessary.=20

Regards,
Stan



>=20
>>=20
>>>> In satellite we aren't necessarily trying to build MESH networks (in f=
act that is much less common) but we are still interested in MANET to help =
us pass link state and we still have a lot of mobility (in terms of modems =
moving between beams / satellites while mobile).  So from a multicast requi=
rement, we need there to be the notion on the hub side that all downstream =
(the broadcast outroute)  multicast is only ever sent once, regardless of h=
ow many actual DLEP peers are established in this direction.  If end device=
s use igmp, pim, etc to get upstream devices to forward said multicast - gr=
eat - the radio doesn't have to know or care since it's a broadcast - if an=
yone wants it at all, everyone else has the opportunity to see it for free.
>>=20
>>>> In trying to unwrap the implementation I am familiar with from the sta=
ndard (thanks to many conversations on this list), I believe this may be po=
ssible in theory now. I was thinking one could setup one 'virtual' DLEP pee=
r that registers for all multicast and broadcast mac address towards my rad=
io.  That way my radio can then see all multicast to forward it, regardless=
 of actual individual clients being subscribed or not. (or even *in network=
*).    Is this understanding correct?
>>=20
>>> I think the idea with multicast and DLEP is that the radio will either =
statically announce multicast MACs/IPs or eavesdrop on IGMP (ICMPv6) messag=
es and handle them internally. The routing agent then can use them to fill =
the local arp table.
>>=20
>>> Your local radio might filter multicast traffic not meant for your loca=
l router, but I think thats an implementation detail not set in the draft.
>>=20
>> Fair enough. Is there anything against the "rules" if one managed multic=
ast membership completely outside the notion of DLEP?  There is still a phy=
sical interface (in our case a VLAN trunk port), and I would be happy to ha=
ve that interface decide weather or not to forward multicast with no too li=
ttle concern about modem status....  there is some persistent multicast I w=
ant to send regardless of DLEP's opinion of spokes being in or out of netwo=
rk. (There is station keeping multicast that must flow even if there are 0 =
'in-network' spokes).
>>=20
>=20
> Nothing states you have to use DLEP to manage multicast.  DLEP has the ca=
pability so that you can help reduce the amount of traffic sent (as mention=
ed above) for those radios that might have a different mechanism for sendin=
g multicast.  The ROUTER controls what multicast groups are being sent to t=
he radio/modem.  If the ROUTER believes that a group has joined on the inte=
rface, it will send the packet out the interface (purposely left generic as=
 there are many ways the ROUTER could learn about a group).
>=20
> Shawn =20
>=20
>> thanks for the discussion,
>> brian
>>=20
>> Henning Rogge
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

