IETF Logo Mail Archive

Re: [pim] Supporting multiple upstream interface in IGMP/MLD proxy

Bharat Joshi <bharat_joshi@infosys.com> Wed, 03 July 2013 15:47 UTC

Return-Path: <bharat_joshi@infosys.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 803E821F9CE8 for <pim@ietfa.amsl.com>; Wed, 3 Jul 2013 08:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1DKMuUrrY2T for <pim@ietfa.amsl.com>; Wed, 3 Jul 2013 08:47:32 -0700 (PDT)
Received: from KECGATE03.infosys.com (kecgate03.infosysconsulting.com [122.98.10.31]) by ietfa.amsl.com (Postfix) with ESMTP id A65A821F9CF2 for <pim@ietf.org>; Wed, 3 Jul 2013 08:47:31 -0700 (PDT)
X-TM-IMSS-Message-ID: <202f95bd00057a4e@infosys.com>
Received: from BLRKECHUB05.ad.infosys.com ([10.66.236.45]) by infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service 7.1) id 202f95bd00057a4e ; Wed, 3 Jul 2013 21:15:51 +0530
Received: from BLRKECHUB09.ad.infosys.com (10.66.236.119) by BLRKECHUB05.ad.infosys.com (10.66.236.45) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 3 Jul 2013 21:17:03 +0530
Received: from BLRKECMBX12.ad.infosys.com ([fe80::a0dd:c35f:79ad:4993]) by Blrkechub09.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Wed, 3 Jul 2013 21:17:03 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Toerless Eckert <eckert@cisco.com>
Thread-Topic: [pim] Supporting multiple upstream interface in IGMP/MLD proxy
Thread-Index: Ac53+kq9XnMmV+mWSsWtieEya4tx7f//qJ0AgABruPY=
Date: Wed, 03 Jul 2013 15:47:02 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED32E92A65@BLRKECMBX12.ad.infosys.com>
References: <35347FBF2796F94E936EE76C0E6047ED32E929F9@BLRKECMBX12.ad.infosys.com>, <20130703145046.GW17405@cisco.com>
In-Reply-To: <20130703145046.GW17405@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.37.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Supporting multiple upstream interface in IGMP/MLD proxy
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 15:47:36 -0000

Here are the two:

draft-asaeda-pim-mldproxy-multif-01 - http://datatracker.ietf.org/doc/draft-asaeda-pim-mldproxy-multif/
draft-zhang-pim-muiimp-00 - http://datatracker.ietf.org/doc/draft-zhang-pim-muiimp/

Thanks,
Bharat
________________________________________
From: Toerless Eckert [eckert@cisco.com]
Sent: Wednesday, July 03, 2013 8:20 PM
To: Bharat Joshi
Cc: pim@ietf.org
Subject: Re: [pim] Supporting multiple upstream interface in IGMP/MLD proxy

Draft names ?

On Wed, Jul 03, 2013 at 02:33:32PM +0000, Bharat Joshi wrote:
> Hi,
>
>      I was going through the drafts submitted to PIM working group and came across two drafts that propose the solution to support multiple upstream interface in IGMP/MLD proxy.
>
>      I have couple of question on this:
>
> 1. Something similar already exist and being used by the operators. Are we trying to standardize this?
>
> 2. As this is device specific, won't a simple configuration is enough? The configuration could be vendor specific as there is no protocol interaction required. As far as I know, this is exactly what some of the vendors that implement this, used.
>
> Regards,
> Bharat
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
> for the use of the addressee(s). If you are not the intended recipient, please
> 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 has 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 reserves the
> right to monitor and review the content of all messages sent to or from this 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

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

v2.23.0 | Report a Bug | By Email