
From internet-drafts@ietf.org  Mon Dec  2 21:31:14 2013
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 739341AE03C; Mon,  2 Dec 2013 21:31:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 UtBzWS-xCF4I; Mon,  2 Dec 2013 21:31:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC961AE00B; Mon,  2 Dec 2013 21:31:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131203053113.554.18747.idtracker@ietfa.amsl.com>
Date: Mon, 02 Dec 2013 21:31:13 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-explicit-tracking-09.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: Tue, 03 Dec 2013 05:31:14 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Protocol Independent Multicast Working Gr=
oup of the IETF.

	Title           : IGMP/MLD-Based Explicit Membership Tracking Function for=
 Multicast Routers
	Author(s)       : Hitoshi Asaeda
	Filename        : draft-ietf-pim-explicit-tracking-09.txt
	Pages           : 10
	Date            : 2013-12-02

Abstract:
   This document describes the IGMP/MLD-based explicit membership
   tracking function for multicast routers and IGMP/MLD proxy devices
   supporting IGMPv3/MLDv2.  The explicit membership tracking function
   contributes to saving network resources and shortening leave latency.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-explicit-tracking-09


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 wwwrun@rfc-editor.org  Fri Dec  6 10:54:56 2013
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 89D4D1AE0FA; Fri,  6 Dec 2013 10:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Level: 
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, 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 dOiW2pHLZCIN; Fri,  6 Dec 2013 10:54:54 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 500C81AE0F6; Fri,  6 Dec 2013 10:54:54 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9A38F7FC158; Fri,  6 Dec 2013 10:54:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20131206185450.9A38F7FC158@rfc-editor.org>
Date: Fri,  6 Dec 2013 10:54:50 -0800 (PST)
Cc: drafts-update-ref@iana.org, pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] RFC 7063 on Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM) Implementations and Deployments
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: Fri, 06 Dec 2013 18:54:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7063

        Title:      Survey Report on Protocol Independent 
                    Multicast - Sparse Mode (PIM-SM) 
                    Implementations and Deployments 
        Author:     L. Zheng,
                    J. Zhang,
                    R. Parekh
        Status:     Informational
        Stream:     IETF
        Date:       December 2013
        Mailbox:    vero.zheng@huawei.com, 
                    zzhang@juniper.net, 
                    riparekh@cisco.com
        Pages:      12
        Characters: 21964
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pim-rfc4601-update-survey-report-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7063.txt

This document provides supporting documentation to advance the IETF
stream's Protocol Independent Multicast - Sparse Mode (PIM-SM)
protocol from Proposed Standard to Internet Standard.

This document is a product of the Protocol Independent Multicast Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From sebastian.woelke@posteo.de  Thu Dec 19 07:48:25 2013
Return-Path: <sebastian.woelke@posteo.de>
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 573D81ADFE4 for <pim@ietfa.amsl.com>; Thu, 19 Dec 2013 07:48:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.538] 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 nqyzLfSy8KS8 for <pim@ietfa.amsl.com>; Thu, 19 Dec 2013 07:48:23 -0800 (PST)
Received: from mx02a.posteo.de (mx02a.posteo.de [89.146.194.168]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD2D1ADF4F for <pim@ietf.org>; Thu, 19 Dec 2013 07:48:23 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.posteo.de (Postfix) with ESMTP id 2173D344987 for <pim@ietf.org>; Thu, 19 Dec 2013 15:48:20 +0000 (UTC)
X-Virus-Scanned: amavisd-new at posteo.de
Received: from posteo.de ([10.125.125.134]) by localhost (amavis1.posteo.de [10.125.125.165]) (amavisd-new, port 10026) with ESMTP id P-vaGMVLalmb for <pim@ietf.org>; Thu, 19 Dec 2013 16:48:08 +0100 (CET)
Received: from mail.posteo.de (localhost [127.0.0.1]) by mail.posteo.de (Postfix) with ESMTPSA id 802BE203FC6EF for <pim@ietf.org>; Thu, 19 Dec 2013 16:48:08 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Date: Thu, 19 Dec 2013 16:48:08 +0100
From: Sebastian Woelke <sebastian.woelke@posteo.de>
To: <pim@ietf.org>
Message-ID: <5bb865dfcae2e717fe0dcda76916fda0@posteo.de>
X-Sender: sebastian.woelke@posteo.de
User-Agent: Posteo Webmail
Subject: [pim] release of a igmp/mld proxy
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: Thu, 19 Dec 2013 15:48:25 -0000

Hi,

I would like to announce a new version of the mcproxy. It can be 
downloaded from our project page (http://mcproxy.realmv6.org/).
The mcproxy complies the IGMP/MLD proxy standard (RFC 4605) and 
supports the group membership protocols IGMPv3 and MLDv2 as well.
In additional it meets the requirements of the multicast source and 
listener support in proxy mobile IPv6 
(draft-ietf-multimob-pmipv6-source-06 and RFC 6224).

Key features:
  - supports IPv4 (IGMPv3)
  - supports IPv6 (MLDv2)
  - can be instantiated multiple times
  - dynamically configurable at runtime
  - can be configured to peer data between its instances
  - supports multiple upstreams


For further questions and comments don't hesitate to contact me.

Kind regards,
Sebastian

From eckert@cisco.com  Thu Dec 19 07:55:16 2013
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 90F381ADFA8 for <pim@ietfa.amsl.com>; Thu, 19 Dec 2013 07:55:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.439
X-Spam-Level: 
X-Spam-Status: No, score=-14.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_71=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, 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 WZrqC4eDCuIz for <pim@ietfa.amsl.com>; Thu, 19 Dec 2013 07:55:15 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 467201ADF5D for <pim@ietf.org>; Thu, 19 Dec 2013 07:55:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1684; q=dns/txt; s=iport; t=1387468514; x=1388678114; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=xb8TczFAf7/5gjWGu3+S/fhS/AZpNASwRmvu8EZeUNQ=; b=WEDg/dPs+fYdfjnIZzPk0eWa+vjJYXSsY2SUjBs6japYxAdBrJNQ9nbR 6a6z8O6cDu+mctAAW2iLzVgEoGHPo8P3qercqNpKFiULZ8msbJ0hscX6y VLbbVjjFgH3Gb2aXd80oeZztKnQeDaudB61YITDVyyS8J7DqFuevkoRAz M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFACoWs1KrRDoI/2dsb2JhbABZgws4uX6BFBZ0giUBAQEEAQEBNzQLEAsYCSUPBRM2E4gDDspsF48SB4MjgRMEiUOOUgGBMJBkg0wb
X-IronPort-AV: E=Sophos;i="4.95,512,1384300800"; d="scan'208";a="98438859"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 19 Dec 2013 15:55:12 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBJFt8MM008219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Dec 2013 15:55:08 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 rBJFt75r017139; Thu, 19 Dec 2013 07:55:07 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id rBJFt7Cw017137; Thu, 19 Dec 2013 07:55:07 -0800
Date: Thu, 19 Dec 2013 07:55:07 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Sebastian Woelke <sebastian.woelke@posteo.de>
Message-ID: <20131219155507.GA6467@cisco.com>
References: <5bb865dfcae2e717fe0dcda76916fda0@posteo.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5bb865dfcae2e717fe0dcda76916fda0@posteo.de>
User-Agent: Mutt/1.4.2.2i
Cc: pim@ietf.org
Subject: Re: [pim] release of a igmp/mld proxy
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: Thu, 19 Dec 2013 15:55:16 -0000

Nice!

Some questions:

Q1: I am totally not up to date on the freeware linux development side. How does
this mcproxy compare to any other linux software modules with which to build
eg: a linux router for multicast (what other options in SW are available ?).

Q2: Any existing or future plans to incude this into common linux router
distributions - DD-WRT or the like ?

Q3: How much will the implementation protect against killing SSM by
ASM receivers ? Aka: If  your proxy receives an IGMPv3 INCLUDE(S,G1)
membership from host 1 and an IGMPv3 EXCLUDE({},G1) from host 2, what
will it send out on the upstream interface ?

Cheers
Toerless Eckert

On Thu, Dec 19, 2013 at 04:48:08PM +0100, Sebastian Woelke wrote:
> Hi,
> 
> I would like to announce a new version of the mcproxy. It can be 
> downloaded from our project page (http://mcproxy.realmv6.org/).
> The mcproxy complies the IGMP/MLD proxy standard (RFC 4605) and 
> supports the group membership protocols IGMPv3 and MLDv2 as well.
> In additional it meets the requirements of the multicast source and 
> listener support in proxy mobile IPv6 
> (draft-ietf-multimob-pmipv6-source-06 and RFC 6224).
> 
> Key features:
>  - supports IPv4 (IGMPv3)
>  - supports IPv6 (MLDv2)
>  - can be instantiated multiple times
>  - dynamically configurable at runtime
>  - can be configured to peer data between its instances
>  - supports multiple upstreams
> 
> 
> For further questions and comments don't hesitate to contact me.
> 
> Kind regards,
> Sebastian
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

From sebastian.woelke@posteo.de  Thu Dec 19 19:43:27 2013
Return-Path: <sebastian.woelke@posteo.de>
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 27B3B1ADF6A for <pim@ietfa.amsl.com>; Thu, 19 Dec 2013 19:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.488
X-Spam-Level: 
X-Spam-Status: No, score=-1.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_71=0.6, RP_MATCHES_RCVD=-0.538] 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 IiHmjpb3XPl6 for <pim@ietfa.amsl.com>; Thu, 19 Dec 2013 19:43:24 -0800 (PST)
Received: from mx02a.posteo.de (mx02a.posteo.de [89.146.194.168]) by ietfa.amsl.com (Postfix) with ESMTP id 792C81ADF33 for <pim@ietf.org>; Thu, 19 Dec 2013 19:43:24 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.posteo.de (Postfix) with ESMTP id A917B3DA9C46; Fri, 20 Dec 2013 03:43:21 +0000 (UTC)
X-Virus-Scanned: amavisd-new at posteo.de
Received: from posteo.de ([10.125.125.134]) by localhost (amavis1.posteo.de [10.125.125.165]) (amavisd-new, port 10026) with ESMTP id n0cPpQs1IwWo; Fri, 20 Dec 2013 04:43:12 +0100 (CET)
Received: from mail.posteo.de (localhost [127.0.0.1]) by mail.posteo.de (Postfix) with ESMTPSA id 6B7A9203C98E6; Fri, 20 Dec 2013 04:43:12 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Dec 2013 04:43:12 +0100
From: Sebastian Woelke <sebastian.woelke@posteo.de>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20131219155507.GA6467@cisco.com>
References: <5bb865dfcae2e717fe0dcda76916fda0@posteo.de> <20131219155507.GA6467@cisco.com>
Message-ID: <18c026789ea56347fdb4b5e4c6352008@posteo.de>
X-Sender: sebastian.woelke@posteo.de
User-Agent: Posteo Webmail
Cc: pim@ietf.org
Subject: Re: [pim] release of a igmp/mld proxy
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: Fri, 20 Dec 2013 03:43:27 -0000

hi,

thank you for your questions, here are my answers:

> Q1: I am totally not up to date on the freeware linux development=20
> side. How does
> this mcproxy compare to any other linux software modules with which=20
> to build
> eg: a linux router for multicast (what other options in SW are=20
> available ?).

There are two notable linux multicast proxies:
igmpproxy (http://sourceforge.net/projects/igmpproxy):
  - supports IGMPv2
  - uses the multicast routing table of the linux kernel

ecmh (http://sourceforge.net/p/ecmh):
  - supports MLDv1/2
  - independent of the linux kernel via userspace routing

igmpproxy doesn't support multiple instances and missing IGMPv3.
And ecmh only supports the slower userspace routing.

> Q2: Any existing or future plans to incude this into common linux=20
> router
> distributions - DD-WRT or the like ?

The mcproxy is developed and tested only on ubuntu, but yes I want to=20
porting it to the more relevant distributions in this field (OpenWRT,=20
DD-WRT).

> Q3: How much will the implementation protect against killing SSM by
> ASM receivers ? Aka: If  your proxy receives an IGMPv3 INCLUDE(S,G1)
> membership from host 1 and an IGMPv3 EXCLUDE({},G1) from host 2, what
> will it send out on the upstream interface ?

Very interesting question, I never thought about this problem. So the=20
current version would sends unaware of any protection the report=20
EXCLUDE({},G1) to the upstream.
But I think I could update the proxy in the following way:
Currently it is possible to define filter rules, for example =E2=80=9Cforwa=
rd=20
only data of the channel (S,G1) to the downstream interface eth0 and=20
ignore all other data=E2=80=9D. In this case, if the proxy receives an IGMP=
v3=20
EXCLUDE({}, G1) on the downstream interface eth0, it could be easily=20
converted to the report INCLUDE(S,G1).

Kind regards,
Sebastian


> On Thu, Dec 19, 2013 at 04:48:08PM +0100, Sebastian Woelke wrote:
>> Hi,
>>
>> I would like to announce a new version of the mcproxy. It can be
>> downloaded from our project page (http://mcproxy.realmv6.org/).
>> The mcproxy complies the IGMP/MLD proxy standard (RFC 4605) and
>> supports the group membership protocols IGMPv3 and MLDv2 as well.
>> In additional it meets the requirements of the multicast source and
>> listener support in proxy mobile IPv6
>> (draft-ietf-multimob-pmipv6-source-06 and RFC 6224).
>>
>> Key features:
>>  - supports IPv4 (IGMPv3)
>>  - supports IPv6 (MLDv2)
>>  - can be instantiated multiple times
>>  - dynamically configurable at runtime
>>  - can be configured to peer data between its instances
>>  - supports multiple upstreams
>>
>>
>> For further questions and comments don't hesitate to contact me.
>>
>> Kind regards,
>> Sebastian
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim

From eckert@cisco.com  Fri Dec 20 00:11:17 2013
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 C10251ADFD4 for <pim@ietfa.amsl.com>; Fri, 20 Dec 2013 00:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.439
X-Spam-Level: 
X-Spam-Status: No, score=-14.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_71=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, 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 PlMc2WTSYbX2 for <pim@ietfa.amsl.com>; Fri, 20 Dec 2013 00:11:15 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3E68D1ADFCE for <pim@ietf.org>; Fri, 20 Dec 2013 00:11:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3278; q=dns/txt; s=iport; t=1387527073; x=1388736673; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=FnglUcitoWvLopWQIOfAJShhKKxd3kzFn4LizdYci3A=; b=H54tWM/0hIsddgLMncIPGY9YTmI+ElAPwc2uEp8LR670HHvsR6LJiAwy phPL3RKD1NrwepIwmw/pnyqEV8SaXlX85Z3SiO4rOabDfdbpRZU2S/u7J EFBtCrg0Qsrw1iKvYi4bOMrFLUEFU168VQT/ihvIWUJBftnphpwANeB7A I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAHz6s1KrRDoI/2dsb2JhbABZgws4ugqBFxZ0giUBAQEEAQEBNzQLEAsSBgklDwUTIhQTiAMOyk4XjxIHhDYEiUOOUgGBMJBkg0wb
X-IronPort-AV: E=Sophos;i="4.95,519,1384300800"; d="scan'208";a="97787606"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 20 Dec 2013 08:11:13 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBK8BC0s030167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Dec 2013 08:11:12 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 rBK8BB08008349; Fri, 20 Dec 2013 00:11:11 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id rBK8BBQo008348; Fri, 20 Dec 2013 00:11:11 -0800
Date: Fri, 20 Dec 2013 00:11:11 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Sebastian Woelke <sebastian.woelke@posteo.de>
Message-ID: <20131220081111.GG6467@cisco.com>
References: <5bb865dfcae2e717fe0dcda76916fda0@posteo.de> <20131219155507.GA6467@cisco.com> <18c026789ea56347fdb4b5e4c6352008@posteo.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <18c026789ea56347fdb4b5e4c6352008@posteo.de>
User-Agent: Mutt/1.4.2.2i
Cc: pim@ietf.org
Subject: Re: [pim] release of a igmp/mld proxy
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: Fri, 20 Dec 2013 08:11:18 -0000

Thanks, Sebastian, sounds good!

On Fri, Dec 20, 2013 at 04:43:12AM +0100, Sebastian Woelke wrote:
> hi,
> 
> thank you for your questions, here are my answers:
> 
> >Q1: I am totally not up to date on the freeware linux development 
> >side. How does
> >this mcproxy compare to any other linux software modules with which 
> >to build
> >eg: a linux router for multicast (what other options in SW are 
> >available ?).
> 
> There are two notable linux multicast proxies:
> igmpproxy (http://sourceforge.net/projects/igmpproxy):
>  - supports IGMPv2
>  - uses the multicast routing table of the linux kernel
> 
> ecmh (http://sourceforge.net/p/ecmh):
>  - supports MLDv1/2
>  - independent of the linux kernel via userspace routing
> 
> igmpproxy doesn't support multiple instances and missing IGMPv3.
> And ecmh only supports the slower userspace routing.
> 
> >Q2: Any existing or future plans to incude this into common linux 
> >router
> >distributions - DD-WRT or the like ?
> 
> The mcproxy is developed and tested only on ubuntu, but yes I want to 
> porting it to the more relevant distributions in this field (OpenWRT, 
> DD-WRT).
> 
> >Q3: How much will the implementation protect against killing SSM by
> >ASM receivers ? Aka: If  your proxy receives an IGMPv3 INCLUDE(S,G1)
> >membership from host 1 and an IGMPv3 EXCLUDE({},G1) from host 2, what
> >will it send out on the upstream interface ?
> 
> Very interesting question, I never thought about this problem. So the 
> current version would sends unaware of any protection the report 
> EXCLUDE({},G1) to the upstream.
> But I think I could update the proxy in the following way:
> Currently it is possible to define filter rules, for example ???forward 
> only data of the channel (S,G1) to the downstream interface eth0 and 
> ignore all other data???. In this case, if the proxy receives an IGMPv3 
> EXCLUDE({}, G1) on the downstream interface eth0, it could be easily 
> converted to the report INCLUDE(S,G1).
> 
> Kind regards,
> Sebastian
> 
> 
> >On Thu, Dec 19, 2013 at 04:48:08PM +0100, Sebastian Woelke wrote:
> >>Hi,
> >>
> >>I would like to announce a new version of the mcproxy. It can be
> >>downloaded from our project page (http://mcproxy.realmv6.org/).
> >>The mcproxy complies the IGMP/MLD proxy standard (RFC 4605) and
> >>supports the group membership protocols IGMPv3 and MLDv2 as well.
> >>In additional it meets the requirements of the multicast source and
> >>listener support in proxy mobile IPv6
> >>(draft-ietf-multimob-pmipv6-source-06 and RFC 6224).
> >>
> >>Key features:
> >> - supports IPv4 (IGMPv3)
> >> - supports IPv6 (MLDv2)
> >> - can be instantiated multiple times
> >> - dynamically configurable at runtime
> >> - can be configured to peer data between its instances
> >> - supports multiple upstreams
> >>
> >>
> >>For further questions and comments don't hesitate to contact me.
> >>
> >>Kind regards,
> >>Sebastian
> >>_______________________________________________
> >>pim mailing list
> >>pim@ietf.org
> >>https://www.ietf.org/mailman/listinfo/pim

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


From adrian@olddog.co.uk  Sat Dec 28 11:50:46 2013
Return-Path: <adrian@olddog.co.uk>
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 ADC151AE2F2 for <pim@ietfa.amsl.com>; Sat, 28 Dec 2013 11:50:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.147
X-Spam-Level: **
X-Spam-Status: No, score=2.147 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] 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 63wB-P5pcLJT for <pim@ietfa.amsl.com>; Sat, 28 Dec 2013 11:50:45 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA9B1AE26F for <pim@ietf.org>; Sat, 28 Dec 2013 11:50:45 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id rBSJocQm006291; Sat, 28 Dec 2013 19:50:38 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id rBSJoWGv006265 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 28 Dec 2013 19:50:35 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-ietf-pim-explicit-tracking.all@tools.ietf.org>
References: <20131219184054.30062.29353.idtracker@ietfa.amsl.com>
In-Reply-To: <20131219184054.30062.29353.idtracker@ietfa.amsl.com>
Date: Sat, 28 Dec 2013 19:50:34 -0000
Message-ID: <064b01cf0406$17444a20$45ccde60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH+uZDi2pAFIvk6Y1y5Tu1pzUPfVpoKljIg
Content-Language: en-gb
X-TM-AS-MML: No
Cc: pim@ietf.org
Subject: Re: [pim] <draft-ietf-pim-explicit-tracking-09.txt> updated by Cindy Morgan
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Sat, 28 Dec 2013 19:50:46 -0000

Authors and chairs (WG copied for information),

This document had a bit of a lumpy ride when it was in front of the =
IESG. A number of ADs said words to the effect of "What is being =
standardised here? There is nothing that affects on-wire behavior, and =
there are many ways that this function could be implemented in a =
router."

I tried several approaches in discussion, mainly saying that while this =
document does not tell you how to achieve interoperability, it does tell =
you how to not break interoperability. That is, this document provides a =
core (default) suggestion of how the function can be achieved in a way =
that will not break PIM. My arguments fell, however, on stony ground =
since the document does not say this.

Currently we have three Abstain positions and four ADs still to ballot. =
We need two more No Objection ballots to get the document through. I =
have put the document back on the agenda for the next telechat, but I =
think we should take some proactive steps. These could be any of:

1. Downgrade to Informational and add a small piece of text explaining =
how this document describes a safe mechanism for achieving the function.

2. Remain at Standards Track and add a more substantial piece of text =
explaining how this document ensure interoperability by describing the =
black-box behavior of an implementation and offering a safe mechanism =
for achieving the function while acknowledging that other methods of =
implementation exist. In effect, this text must say that =
interoperability will not be broken if the method described is used.

3. Dig in our heals and say that the document is fine as it is (giving =
reasons!).

Your thoughts?
Adrian


> -----Original Message-----
> From: DraftTracker Mail System [mailto:iesg-secretary@ietf.org]
> Sent: 19 December 2013 18:41
> To: Adrian Farrel
> Subject: <draft-ietf-pim-explicit-tracking-09.txt> updated by Cindy =
Morgan
>=20
>=20
> Please DO NOT reply to this email.
>=20
> I-D: <draft-ietf-pim-explicit-tracking-09.txt>
> ID Tracker URL: =
http://datatracker.ietf.org/doc/draft-ietf-pim-explicit-tracking/
>=20
> State changed to IESG Evaluation::AD Followup from IESG Evaluation


From bharat_joshi@infosys.com  Sun Dec 29 20:43:55 2013
Return-Path: <bharat_joshi@infosys.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 228351AE39D for <pim@ietfa.amsl.com>; Sun, 29 Dec 2013 20:43:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level: 
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538] 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 KuJK7wJ_W67b for <pim@ietfa.amsl.com>; Sun, 29 Dec 2013 20:43:53 -0800 (PST)
Received: from kecgate06.infosys.com (kecgate06.infosys.com [122.98.14.33]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8E51AE3E1 for <pim@ietf.org>; Sun, 29 Dec 2013 20:43:52 -0800 (PST)
X-TM-IMSS-Message-ID: <aea658050019bdcf@infosys.com>
Received: from BLRKECHUB05.ad.infosys.com ([10.66.236.45]) by infosys.com ([122.98.14.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id aea658050019bdcf ; Mon, 30 Dec 2013 10:14:37 +0530
Received: from BLRKECHUB10.ad.infosys.com (10.66.236.120) by BLRKECHUB05.ad.infosys.com (10.66.236.45) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 30 Dec 2013 10:13:31 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by blrkechub10.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Mon, 30 Dec 2013 10:13:31 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: One question on RFC 4601
Thread-Index: Ac8FGa/rCxU2QhpUR7G7WJs42d8ZaQ==
Date: Mon, 30 Dec 2013 04:43:30 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED48517EB9@BLRKECMBX13.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.200.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [pim] One question on RFC 4601
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, 30 Dec 2013 04:43:55 -0000

Hi,

      I was reading up PIM Assert mechanism in RFC 4601 once again. I am =
not sure if its worth mentioning but I decided to do it because we are wo=
rking on revising PIM protocol standard and if required it can be handled=
 there.

      In section 3.6, 'Multi-Access Transit LANs', its mentioned that mul=
ti-access LANs can cause complication for three reasons in the following =
statement:

The overview so far has concerned itself with point-to-point transit
links.  However, using multi-access LANs such as Ethernet for transit
is not uncommon. This can cause complications for three reasons:

      And then it defines the three reasons where main issue is MRIB mism=
atch in two downstream routers. I was wondering that will not we hit upon=
 the same issue with local membership. Let me give an example.

      Let us assume there are three routers where R1 and R2 is upstream a=
nd R3 is a downstream router. These routers are connected to a LAN and th=
is LAN also has local hosts. Let us assume R1 is elected as DR. Let us as=
sume that for a (*,G) membership, R3 selects R2 as the upstream router. N=
ow in case a local host is interested in (*,G), R1 being the DR will hand=
le it. With this setup, both R1 and R2 will setup the multicast tree for =
(*,G) and forward the traffic to the LAN. So we again hit the same condit=
ion as defined in the section 3.6.

      Same thing can happen when local host join (S,G) or R3 joins (S,G) =
and local host join (*,G) etc.

      My question is, is this correct to use 'three reasons' causing this=
 complication when there could be more reasons like I mentioned above?

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

From eckert@cisco.com  Sun Dec 29 21:04:52 2013
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 60D941AE3A5 for <pim@ietfa.amsl.com>; Sun, 29 Dec 2013 21:04:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.038
X-Spam-Level: 
X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, 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 8tJLV--e1c4Z for <pim@ietfa.amsl.com>; Sun, 29 Dec 2013 21:04:50 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 342CC1AE396 for <pim@ietf.org>; Sun, 29 Dec 2013 21:04:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7661; q=dns/txt; s=iport; t=1388379884; x=1389589484; h=from:to:subject:date:message-id:references:in-reply-to: reply-to:mime-version; bh=8FZ4ve+urxCe3XvPW+lc5838fpScuoneMifeaJwYeSM=; b=f3FvQufNKrulhs2J+K2S7al2upx3U6/FSLB0DuyY+RuT1IkwnR74vcCH tVNBv+3vj91i73BhbPDd5PPKSYV343DhHlVNWqzviKzvHMbfIsWit+eXN BAQ9CNlye8iJNpLzmv1+AXbP3v9qTMroXGa0TAbKlzEUSB50XKxlchrDW o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAIH+wFKtJXHA/2dsb2JhbABYgkdEOKdtkkaBFRZ0giYBAQQBAQEqQRsCAQghJQ8YCw4XAgQBEogEDchqF48ZC4Q2BIUdknqEFI4Agy0
X-IronPort-AV: E=Sophos;i="4.95,572,1384300800"; d="scan'208,217";a="9584075"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by alln-iport-6.cisco.com with ESMTP; 30 Dec 2013 05:04:44 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id rBU54iPL018493 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 30 Dec 2013 05:04:44 GMT
Received: from xmb-rcd-x15.cisco.com ([169.254.5.15]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Sun, 29 Dec 2013 23:04:43 -0600
From: "Toerless Eckert (eckert)" <eckert@cisco.com>
To: Bharat Joshi <bharat_joshi@infosys.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] One question on RFC 4601
Thread-Index: AQHPBRyn851CpgSaEk+p1D9RG+q6+A==
Date: Mon, 30 Dec 2013 05:04:43 +0000
Message-ID: <yitgsdh7vohy2i4e2i8xon9j.1388379786891@email.android.com>
References: <35347FBF2796F94E936EE76C0E6047ED48517EB9@BLRKECMBX13.ad.infosys.com>
In-Reply-To: <35347FBF2796F94E936EE76C0E6047ED48517EB9@BLRKECMBX13.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_yitgsdh7vohy2i4e2i8xon9j1388379786891emailandroidcom_"
MIME-Version: 1.0
Subject: Re: [pim] One question on RFC 4601
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Toerless Eckert \(eckert\)" <eckert@cisco.com>
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, 30 Dec 2013 05:04:52 -0000

--_000_yitgsdh7vohy2i4e2i8xon9j1388379786891emailandroidcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Think of the dr function as a separate logical downstream router and you wi=
ll find that your example is just another instance of multiple downstram ro=
uters.




Sent from my Samsung Captivate Glide on AT&T

Bharat Joshi <bharat_joshi@infosys.com> wrote:
Hi,

      I was reading up PIM Assert mechanism in RFC 4601 once again. I am no=
t sure if its worth mentioning but I decided to do it because we are workin=
g on revising PIM protocol standard and if required it can be handled there=
.

      In section 3.6, 'Multi-Access Transit LANs', its mentioned that multi=
-access LANs can cause complication for three reasons in the following stat=
ement:

The overview so far has concerned itself with point-to-point transit
links.  However, using multi-access LANs such as Ethernet for transit
is not uncommon. This can cause complications for three reasons:

      And then it defines the three reasons where main issue is MRIB mismat=
ch in two downstream routers. I was wondering that will not we hit upon the=
 same issue with local membership. Let me give an example.

      Let us assume there are three routers where R1 and R2 is upstream and=
 R3 is a downstream router. These routers are connected to a LAN and this L=
AN also has local hosts. Let us assume R1 is elected as DR. Let us assume t=
hat for a (*,G) membership, R3 selects R2 as the upstream router. Now in ca=
se a local host is interested in (*,G), R1 being the DR will handle it. Wit=
h this setup, both R1 and R2 will setup the multicast tree for (*,G) and fo=
rward the traffic to the LAN. So we again hit the same condition as defined=
 in the section 3.6.

      Same thing can happen when local host join (S,G) or R3 joins (S,G) an=
d local host join (*,G) etc.

      My question is, is this correct to use 'three reasons' causing this c=
omplication when there could be more reasons like I mentioned above?

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solel=
y
for the use of the addressee(s). If you are not the intended recipient, ple=
ase
notify the sender by e-mail and delete the original message. Further, you a=
re not
to copy, disclose, or distribute this e-mail or its contents to any other p=
erson and
any such actions are unlawful. This e-mail may contain viruses. Infosys has=
 taken
every reasonable precaution to minimize this risk, but is not liable for an=
y damage
you may sustain as a result of any virus in this e-mail. You should carry o=
ut your
own virus checks before opening the e-mail or attachment. Infosys reserves =
the
right to monitor and review the content of all messages sent to or from thi=
s e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
pim mailing list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

--_000_yitgsdh7vohy2i4e2i8xon9j1388379786891emailandroidcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Think of the dr function as a separate logical downstream router and y=
ou will find that your example is just another instance of multiple downstr=
am routers.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style=3D"font-size:75%; color:#575757">Sent from my Samsung Captivate =
Glide on AT&amp;T</div>
</div>
<br>
Bharat Joshi &lt;bharat_joshi@infosys.com&gt; wrote:<br>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Hi,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I was reading up PIM Assert mechanism in RFC=
 4601 once again. I am not sure if its worth mentioning but I decided to do=
 it because we are working on revising PIM protocol standard and if require=
d it can be handled there.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In section 3.6, 'Multi-Access Transit LANs',=
 its mentioned that multi-access LANs can cause complication for three reas=
ons in the following statement:<br>
<br>
The overview so far has concerned itself with point-to-point transit<br>
links.&nbsp; However, using multi-access LANs such as Ethernet for transit<=
br>
is not uncommon. This can cause complications for three reasons:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; And then it defines the three reasons where =
main issue is MRIB mismatch in two downstream routers. I was wondering that=
 will not we hit upon the same issue with local membership. Let me give an =
example.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Let us assume there are three routers where =
R1 and R2 is upstream and R3 is a downstream router. These routers are conn=
ected to a LAN and this LAN also has local hosts. Let us assume R1 is elect=
ed as DR. Let us assume that for a (*,G) membership, R3 selects
 R2 as the upstream router. Now in case a local host is interested in (*,G)=
, R1 being the DR will handle it. With this setup, both R1 and R2 will setu=
p the multicast tree for (*,G) and forward the traffic to the LAN. So we ag=
ain hit the same condition as defined
 in the section 3.6.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Same thing can happen when local host join (=
S,G) or R3 joins (S,G) and local host join (*,G) etc.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; My question is, is this correct to use 'thre=
e reasons' causing this complication when there could be more reasons like =
I mentioned above?<br>
<br>
Regards,<br>
Bharat Joshi<br>
<a href=3D"http://bite-the-bytes.blogspot.com/">http://bite-the-bytes.blogs=
pot.com/</a><br>
**************** CAUTION - Disclaimer *****************<br>
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solel=
y <br>
for the use of the addressee(s). If you are not the intended recipient, ple=
ase <br>
notify the sender by e-mail and delete the original message. Further, you a=
re not
<br>
to copy, disclose, or distribute this e-mail or its contents to any other p=
erson and
<br>
any such actions are unlawful. This e-mail may contain viruses. Infosys has=
 taken
<br>
every reasonable precaution to minimize this risk, but is not liable for an=
y damage
<br>
you may sustain as a result of any virus in this e-mail. You should carry o=
ut your
<br>
own virus checks before opening the e-mail or attachment. Infosys reserves =
the <br>
right to monitor and review the content of all messages sent to or from thi=
s e-mail
<br>
address. Messages sent to or from this e-mail address may be stored on the =
<br>
Infosys e-mail system.<br>
***INFOSYS******** End of Disclaimer ********INFOSYS***<br>
_______________________________________________<br>
pim mailing list<br>
pim@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/=
mailman/listinfo/pim</a><br>
</div>
</span></font>
</body>
</html>

--_000_yitgsdh7vohy2i4e2i8xon9j1388379786891emailandroidcom_--

From bharat_joshi@infosys.com  Sun Dec 29 21:12:22 2013
Return-Path: <bharat_joshi@infosys.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 C6B351AE3A5 for <pim@ietfa.amsl.com>; Sun, 29 Dec 2013 21:12:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level: 
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538] 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 N5D6Q57co-Pt for <pim@ietfa.amsl.com>; Sun, 29 Dec 2013 21:12:20 -0800 (PST)
Received: from kecgate02.infosys.com (kecgate02.infosys.com [122.98.14.32]) by ietfa.amsl.com (Postfix) with ESMTP id A09AC1AE396 for <pim@ietf.org>; Sun, 29 Dec 2013 21:12:19 -0800 (PST)
X-TM-IMSS-Message-ID: <aec6b3e500179f99@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.14.32]) with ESMTP (TREND IMSS SMTP Service 7.1) id aec6b3e500179f99 ; Mon, 30 Dec 2013 10:41:40 +0530
Received: from BLRKECHUB10.ad.infosys.com (10.66.236.120) by blrkechub01.ad.infosys.com (10.66.236.41) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 30 Dec 2013 10:41:39 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by blrkechub10.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Mon, 30 Dec 2013 10:41:38 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "Toerless Eckert (eckert)" <eckert@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] One question on RFC 4601
Thread-Index: Ac8FGa/rCxU2QhpUR7G7WJs42d8Zaf//qbqAgABdQvM=
Date: Mon, 30 Dec 2013 05:11:37 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED48517EE5@BLRKECMBX13.ad.infosys.com>
References: <35347FBF2796F94E936EE76C0E6047ED48517EB9@BLRKECMBX13.ad.infosys.com>, <yitgsdh7vohy2i4e2i8xon9j.1388379786891@email.android.com>
In-Reply-To: <yitgsdh7vohy2i4e2i8xon9j.1388379786891@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.200.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pim] One question on RFC 4601
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, 30 Dec 2013 05:12:23 -0000

Yes. I agree. It can be seen as just another instance of what is already me=
ntioned in that section.

Do you think it will help if we add some text here to explain this?

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/
________________________________________
From: Toerless Eckert (eckert) [eckert@cisco.com]
Sent: Monday, December 30, 2013 10:34 AM
To: Bharat Joshi; pim@ietf.org
Subject: RE: [pim] One question on RFC 4601

Think of the dr function as a separate logical downstream router and you wi=
ll find that your example is just another instance of multiple downstram ro=
uters.




Sent from my Samsung Captivate Glide on AT&T

Bharat Joshi <bharat_joshi@infosys.com> wrote:
Hi,

      I was reading up PIM Assert mechanism in RFC 4601 once again. I am no=
t sure if its worth mentioning but I decided to do it because we are workin=
g on revising PIM protocol standard and if required it can be handled there=
.

      In section 3.6, 'Multi-Access Transit LANs', its mentioned that multi=
-access LANs can cause complication for three reasons in the following stat=
ement:

The overview so far has concerned itself with point-to-point transit
links.  However, using multi-access LANs such as Ethernet for transit
is not uncommon. This can cause complications for three reasons:

      And then it defines the three reasons where main issue is MRIB mismat=
ch in two downstream routers. I was wondering that will not we hit upon the=
 same issue with local membership. Let me give an example.

      Let us assume there are three routers where R1 and R2 is upstream and=
 R3 is a downstream router. These routers are connected to a LAN and this L=
AN also has local hosts. Let us assume R1 is elected as DR. Let us assume t=
hat for a (*,G) membership, R3 selects R2 as the upstream router. Now in ca=
se a local host is interested in (*,G), R1 being the DR will handle it. Wit=
h this setup, both R1 and R2 will setup the multicast tree for (*,G) and fo=
rward the traffic to the LAN. So we again hit the same condition as defined=
 in the section 3.6.

      Same thing can happen when local host join (S,G) or R3 joins (S,G) an=
d local host join (*,G) etc.

      My question is, is this correct to use 'three reasons' causing this c=
omplication when there could be more reasons like I mentioned above?

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solel=
y
for the use of the addressee(s). If you are not the intended recipient, ple=
ase
notify the sender by e-mail and delete the original message. Further, you a=
re not
to copy, disclose, or distribute this e-mail or its contents to any other p=
erson and
any such actions are unlawful. This e-mail may contain viruses. Infosys has=
 taken
every reasonable precaution to minimize this risk, but is not liable for an=
y damage
you may sustain as a result of any virus in this e-mail. You should carry o=
ut your
own virus checks before opening the e-mail or attachment. Infosys reserves =
the
right to monitor and review the content of all messages sent to or from thi=
s e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
pim mailing list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

From eckert@cisco.com  Sun Dec 29 21:40:47 2013
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 F35191AE3F0 for <pim@ietfa.amsl.com>; Sun, 29 Dec 2013 21:40:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.038
X-Spam-Level: 
X-Spam-Status: No, score=-15.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, 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 rqsgpDQFE2nh for <pim@ietfa.amsl.com>; Sun, 29 Dec 2013 21:40:41 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 181911AE3E1 for <pim@ietf.org>; Sun, 29 Dec 2013 21:40:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9966; q=dns/txt; s=iport; t=1388382035; x=1389591635; h=from:to:subject:date:message-id:references:in-reply-to: reply-to:mime-version; bh=axNBH9I1mPmVVXv2csy1s38TvZ6whvlPv1mTPLw4yoE=; b=RU9DDuV+fmarQ7F6AL5z7DNFFTax2lX9ZqtLy3HsRQliADsHwEI5V083 WL9pmTfB9159vG5DYbgfUjbnOA5iRearVCCcgEXG4JJj4K4ZONg0WjeOB z6KOSvCQnm6yHq2tvw/LjnwMKWwsR+DO18EVh3WtiBNSzr9TSPWC1PlhT Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApcGAHQGwVKtJV2c/2dsb2JhbABYgkdEOKdtjw2DOYEVFnSCJQEBAQQBAQEqQRsCAQgRAQMBAQolDxgLDgkGCAIEARKIBA3IdRePGQsGhDAEhR2SeoQUjgCDLQ
X-IronPort-AV: E=Sophos;i="4.95,572,1384300800";  d="scan'208,217";a="294440951"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP; 30 Dec 2013 05:40:35 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rBU5eY24018103 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 30 Dec 2013 05:40:34 GMT
Received: from xmb-rcd-x15.cisco.com ([169.254.5.15]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Sun, 29 Dec 2013 23:40:34 -0600
From: "Toerless Eckert (eckert)" <eckert@cisco.com>
To: Bharat Joshi <bharat_joshi@infosys.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] One question on RFC 4601
Thread-Index: AQHPBRyn851CpgSaEk+p1D9RG+q6+JpslZaA//+jgnA=
Date: Mon, 30 Dec 2013 05:40:34 +0000
Message-ID: <bgdp6spd19hhd62ip65frjhn.1388381738004@email.android.com>
References: <35347FBF2796F94E936EE76C0E6047ED48517EB9@BLRKECMBX13.ad.infosys.com>, <yitgsdh7vohy2i4e2i8xon9j.1388379786891@email.android.com>, <35347FBF2796F94E936EE76C0E6047ED48517EE5@BLRKECMBX13.ad.infosys.com>
In-Reply-To: <35347FBF2796F94E936EE76C0E6047ED48517EE5@BLRKECMBX13.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_bgdp6spd19hhd62ip65frjhn1388381738004emailandroidcom_"
MIME-Version: 1.0
Subject: Re: [pim] One question on RFC 4601
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Toerless Eckert \(eckert\)" <eckert@cisco.com>
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, 30 Dec 2013 05:40:47 -0000

--_000_bgdp6spd19hhd62ip65frjhn1388381738004emailandroidcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am always a fan of a lot of explanations, but ietf protocol specs are usu=
ally terse, and a lot of folks will argue about verbosity in standards spec=
s. After all, one wants to review and aprove the whoole doc, so those folks=
 have a point.

In ?1993? There where both a pim-v1 protocol draft and a pim architecture d=
raft. The architecture draft died out unfortunately. I think it would be a =
great idea to revive it and put all explanatory stuff beyond whats necessar=
y in the protocol spec into such a pom arch rfc.


Sent from my Samsung Captivate Glide on AT&T

Bharat Joshi <bharat_joshi@infosys.com> wrote:
Yes. I agree. It can be seen as just another instance of what is already me=
ntioned in that section.

Do you think it will help if we add some text here to explain this?

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/
________________________________________
From: Toerless Eckert (eckert) [eckert@cisco.com]
Sent: Monday, December 30, 2013 10:34 AM
To: Bharat Joshi; pim@ietf.org
Subject: RE: [pim] One question on RFC 4601

Think of the dr function as a separate logical downstream router and you wi=
ll find that your example is just another instance of multiple downstram ro=
uters.




Sent from my Samsung Captivate Glide on AT&T

Bharat Joshi <bharat_joshi@infosys.com> wrote:
Hi,

      I was reading up PIM Assert mechanism in RFC 4601 once again. I am no=
t sure if its worth mentioning but I decided to do it because we are workin=
g on revising PIM protocol standard and if required it can be handled there=
.

      In section 3.6, 'Multi-Access Transit LANs', its mentioned that multi=
-access LANs can cause complication for three reasons in the following stat=
ement:

The overview so far has concerned itself with point-to-point transit
links.  However, using multi-access LANs such as Ethernet for transit
is not uncommon. This can cause complications for three reasons:

      And then it defines the three reasons where main issue is MRIB mismat=
ch in two downstream routers. I was wondering that will not we hit upon the=
 same issue with local membership. Let me give an example.

      Let us assume there are three routers where R1 and R2 is upstream and=
 R3 is a downstream router. These routers are connected to a LAN and this L=
AN also has local hosts. Let us assume R1 is elected as DR. Let us assume t=
hat for a (*,G) membership, R3 selects R2 as the upstream router. Now in ca=
se a local host is interested in (*,G), R1 being the DR will handle it. Wit=
h this setup, both R1 and R2 will setup the multicast tree for (*,G) and fo=
rward the traffic to the LAN. So we again hit the same condition as defined=
 in the section 3.6.

      Same thing can happen when local host join (S,G) or R3 joins (S,G) an=
d local host join (*,G) etc.

      My question is, is this correct to use 'three reasons' causing this c=
omplication when there could be more reasons like I mentioned above?

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solel=
y
for the use of the addressee(s). If you are not the intended recipient, ple=
ase
notify the sender by e-mail and delete the original message. Further, you a=
re not
to copy, disclose, or distribute this e-mail or its contents to any other p=
erson and
any such actions are unlawful. This e-mail may contain viruses. Infosys has=
 taken
every reasonable precaution to minimize this risk, but is not liable for an=
y damage
you may sustain as a result of any virus in this e-mail. You should carry o=
ut your
own virus checks before opening the e-mail or attachment. Infosys reserves =
the
right to monitor and review the content of all messages sent to or from thi=
s e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
pim mailing list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

--_000_bgdp6spd19hhd62ip65frjhn1388381738004emailandroidcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>I am always a fan of a lot of explanations, but ietf protocol specs ar=
e usually terse, and a lot of folks will argue about verbosity in standards=
 specs. After all, one wants to review and aprove the whoole doc, so those =
folks have a point.</div>
<div><br>
</div>
<div>In ?1993? There where both a pim-v1 protocol draft and a pim architect=
ure draft. The architecture draft died out unfortunately. I think it would =
be a great idea to revive it and put all explanatory stuff beyond whats nec=
essary in the protocol spec into
 such a pom arch rfc.</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style=3D"font-size:75%; color:#575757">Sent from my Samsung Captivate =
Glide on AT&amp;T</div>
</div>
<br>
Bharat Joshi &lt;bharat_joshi@infosys.com&gt; wrote:<br>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Yes. I agree. It can be seen as just another insta=
nce of what is already mentioned in that section.<br>
<br>
Do you think it will help if we add some text here to explain this?<br>
<br>
Regards,<br>
Bharat Joshi<br>
<a href=3D"http://bite-the-bytes.blogspot.com/">http://bite-the-bytes.blogs=
pot.com/</a><br>
________________________________________<br>
From: Toerless Eckert (eckert) [eckert@cisco.com]<br>
Sent: Monday, December 30, 2013 10:34 AM<br>
To: Bharat Joshi; pim@ietf.org<br>
Subject: RE: [pim] One question on RFC 4601<br>
<br>
Think of the dr function as a separate logical downstream router and you wi=
ll find that your example is just another instance of multiple downstram ro=
uters.<br>
<br>
<br>
<br>
<br>
Sent from my Samsung Captivate Glide on AT&amp;T<br>
<br>
Bharat Joshi &lt;bharat_joshi@infosys.com&gt; wrote:<br>
Hi,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I was reading up PIM Assert mechanism in RFC=
 4601 once again. I am not sure if its worth mentioning but I decided to do=
 it because we are working on revising PIM protocol standard and if require=
d it can be handled there.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In section 3.6, 'Multi-Access Transit LANs',=
 its mentioned that multi-access LANs can cause complication for three reas=
ons in the following statement:<br>
<br>
The overview so far has concerned itself with point-to-point transit<br>
links.&nbsp; However, using multi-access LANs such as Ethernet for transit<=
br>
is not uncommon. This can cause complications for three reasons:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; And then it defines the three reasons where =
main issue is MRIB mismatch in two downstream routers. I was wondering that=
 will not we hit upon the same issue with local membership. Let me give an =
example.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Let us assume there are three routers where =
R1 and R2 is upstream and R3 is a downstream router. These routers are conn=
ected to a LAN and this LAN also has local hosts. Let us assume R1 is elect=
ed as DR. Let us assume that for a (*,G) membership, R3 selects
 R2 as the upstream router. Now in case a local host is interested in (*,G)=
, R1 being the DR will handle it. With this setup, both R1 and R2 will setu=
p the multicast tree for (*,G) and forward the traffic to the LAN. So we ag=
ain hit the same condition as defined
 in the section 3.6.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Same thing can happen when local host join (=
S,G) or R3 joins (S,G) and local host join (*,G) etc.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; My question is, is this correct to use 'thre=
e reasons' causing this complication when there could be more reasons like =
I mentioned above?<br>
<br>
Regards,<br>
Bharat Joshi<br>
<a href=3D"http://bite-the-bytes.blogspot.com/">http://bite-the-bytes.blogs=
pot.com/</a><br>
**************** CAUTION - Disclaimer *****************<br>
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solel=
y<br>
for the use of the addressee(s). If you are not the intended recipient, ple=
ase<br>
notify the sender by e-mail and delete the original message. Further, you a=
re not<br>
to copy, disclose, or distribute this e-mail or its contents to any other p=
erson and<br>
any such actions are unlawful. This e-mail may contain viruses. Infosys has=
 taken<br>
every reasonable precaution to minimize this risk, but is not liable for an=
y damage<br>
you may sustain as a result of any virus in this e-mail. You should carry o=
ut your<br>
own virus checks before opening the e-mail or attachment. Infosys reserves =
the<br>
right to monitor and review the content of all messages sent to or from thi=
s e-mail<br>
address. Messages sent to or from this e-mail address may be stored on the<=
br>
Infosys e-mail system.<br>
***INFOSYS******** End of Disclaimer ********INFOSYS***<br>
_______________________________________________<br>
pim mailing list<br>
pim@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/=
mailman/listinfo/pim</a><br>
</div>
</span></font>
</body>
</html>

--_000_bgdp6spd19hhd62ip65frjhn1388381738004emailandroidcom_--
