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

LUIS MIGUEL CONTRERAS MURILLO <lmcm@tid.es> Wed, 03 July 2013 16:05 UTC

Return-Path: <lmcm@tid.es>
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 9429521F9C91 for <pim@ietfa.amsl.com>; Wed, 3 Jul 2013 09:05:49 -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 8pQYZqCfSFgf for <pim@ietfa.amsl.com>; Wed, 3 Jul 2013 09:05:45 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA0521F9CA7 for <pim@ietf.org>; Wed, 3 Jul 2013 09:05:45 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MPD0026NBDJ3K@tid.hi.inet> for pim@ietf.org; Wed, 03 Jul 2013 18:05:43 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49]) by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id A5.67.02911.7DB44D15; Wed, 03 Jul 2013 18:05:43 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MPD0026HBDJ3K@tid.hi.inet> for pim@ietf.org; Wed, 03 Jul 2013 18:05:43 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS7-MAD.hi.inet ([::1]) with mapi id 14.02.0342.003; Wed, 03 Jul 2013 18:05:43 +0200
Date: Wed, 03 Jul 2013 16:05:42 +0000
From: LUIS MIGUEL CONTRERAS MURILLO <lmcm@tid.es>
In-reply-to: <35347FBF2796F94E936EE76C0E6047ED32E92A65@BLRKECMBX12.ad.infosys.com>
X-Originating-IP: [10.95.64.115]
To: Bharat Joshi <bharat_joshi@infosys.com>, Toerless Eckert <eckert@cisco.com>
Message-id: <823234EF5C7C334998D973D822FF801B44F89454@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-language: es-ES
Content-transfer-encoding: quoted-printable
Accept-Language: es-ES, en-US
Thread-topic: [pim] Supporting multiple upstream interface in IGMP/MLD proxy
Thread-index: Ac53+kq9XnMmV+mWSsWtieEya4tx7f//40kAgAAPuQD//9pD4A==
X-AuditID: 0a5f4e69-b7f118e000000b5f-e1-51d44bd7d735
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsXCFe9nqHvd+0qgwYz1ehZfHt5kdmD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxvL/QgWPpCturl/F1sD4R6yLkZNDQsBE4tC3iWwQtpjEhXvr gWwuDiGB7YwSlzZ9ZoFwvjNKbFqyD8qZxijx6MMkJpAWFgFViUmdd8FsNgFDiVk7J7GC2MIC 3hK9r76BjeUUCJE4tOwcK8QKBYk/5x6zgNgiAv4SMy+9ZwSxmQUUJT79/Qhkc3DwAvVOWBkI EuYVEJT4MfkeC0SJjkTv92/MELa4xJxfE1khbG2JJ+8ugNmMArISK8+fZoQY7yPRN3UZE4Tt JPFr0gJmiBMEJJbsOQ9li0q8fPwPrFdI4ACjxNZj6hMYxWchWT0LyepZSFbPQrJ6ASPLKkax 4qSizPSMktzEzJx0AyO9jEy9zLzUkk2MkCjK3MG4fKfKIUYBDkYlHl4JqyuBQqyJZcWVuYcY JTiYlUR4rS2BQrwpiZVVqUX58UWlOanFhxiZODilGhhXCvu/4U2rsvIonlfeJO3EdFx9ct/S yPKwa5Lel633fHaYbjZxSgJj1YyqzzfOvLRWesTUs8XVtk+2+dqk0h0cvY7PO1p0/k29e0dG NvLMVbdtMwXFHe9M5TpwjKO6Zvea+OsNVxJXbpa7ofzyzwbPd3qRsUv7JFf9r2XZ41tjM6fA /upJtkNKLMUZiYZazEXFiQAbxTIZgAIAAA==
References: <35347FBF2796F94E936EE76C0E6047ED32E929F9@BLRKECMBX12.ad.infosys.com> <20130703145046.GW17405@cisco.com> <35347FBF2796F94E936EE76C0E6047ED32E92A65@BLRKECMBX12.ad.infosys.com>
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 16:05:49 -0000

Please, consider this draft as well (originally contributed to the Multimob WG), as it has been already presented in PIM WG and will be submitted to PIM WG for the Berlin meeting.

http://datatracker.ietf.org/doc/draft-contreras-multimob-multiple-upstreams/

Best regards,

Luis

-----Mensaje original-----
De: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] En nombre de Bharat Joshi
Enviado el: miércoles, 03 de julio de 2013 17:47
Para: Toerless Eckert
CC: pim@ietf.org
Asunto: Re: [pim] Supporting multiple upstream interface in IGMP/MLD proxy

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!
_______________________________________________
pim mailing list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx