IETF Logo Mail Archive

Re: [pim] reg any cast rp using pim register mechanism

phani Ayyappa <durgam.iit@gmail.com> Tue, 29 January 2019 16:38 UTC

Return-Path: <durgam.iit@gmail.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 CF176130DCD for <pim@ietfa.amsl.com>; Tue, 29 Jan 2019 08:38:34 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CQz4zkytAIlc for <pim@ietfa.amsl.com>; Tue, 29 Jan 2019 08:38:32 -0800 (PST)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83664130E09 for <pim@ietf.org>; Tue, 29 Jan 2019 08:38:32 -0800 (PST)
Received: by mail-pl1-x630.google.com with SMTP id u18so9576081plq.7 for <pim@ietf.org>; Tue, 29 Jan 2019 08:38:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8ijp8SOXxBgUAXqMjRTqLQT1WZfaoa/AmJcNaQrqXXs=; b=GSCv6cP6AvYFROXIuVunH94HIwLdFbeY9r6GxiP+8agW83DZbxYrtrqs7otvgmzkGW X3JIdPyJov6VgF49CFS9icAy990rQfBct6zZxxpacFVh9RZIqy/GruJSIeMBNQW3F7Mj ry+udqVn4obcRJHw0lmSx/bEJpxUh7B9b4r6w/LgvrpXjHmr0rq8n1etVs//tJg74Zmj ePN4/6h9iTcdrk9D22yrX18UOjFK84dsc/n8u6J8qf8e+gjk4fExSwZwZK+ls9O9Ibpa R/ozzB6pXj53r9igc7g52Vi5lTIj5a8fek1lIe57aeBIu8TGf1/GfyUGCj8iuBrq6aTM DQ1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8ijp8SOXxBgUAXqMjRTqLQT1WZfaoa/AmJcNaQrqXXs=; b=B2YFarn8XbkQwiJ/AmYxY1dosTjHLA5FFfSOyhFnA3KQsuMLhelnbDcH4H5mMXtWAN 22USOS+S4wgIjrxh4Y3aGSac2x7t1ZLGdahteKJ3AYp6WgZgo9zX5s6168kjgJxb/0WZ C1LsQprKpclsug450d1+9V5gjQW1uma7e8VEgEWWYZF6yHVu/HugkesUjikcBIhg9kyT za4s6Fuj0tFprFd+o3EXxhGbvfNrhzJV7sFlEFruUcfBaIsngBjOHu+6lagPiCDeuY5o yjsE0nRWc0Mo0CQdRcSyiAhoTKqiRt78XTO09+rHt1rC8rdLdM3jRbpOhfMKNMPzWHTH Oqmw==
X-Gm-Message-State: AJcUukeJbSrX/6hDbBs8GMsKCn+N6AOVMh2FR5zXxKHrQVNr6QbtzRNv 0LvNgCGOqlVPaHItbB6yGWUUJ/zaOxXqTDT5IwvpMA==
X-Google-Smtp-Source: ALg8bN7py6rnIukedIN7uCxeawi4nm71tvw1tVJhdBLhA8+zhdFtqwoXpVHZVuCzCYRJrmQYUHN6Xvw+kDPcCrZV3oY=
X-Received: by 2002:a17:902:bb86:: with SMTP id m6mr27065428pls.315.1548779911870; Tue, 29 Jan 2019 08:38:31 -0800 (PST)
MIME-Version: 1.0
References: <CALXDUZhfLspOKfw0H5k_=1Xhp0Aestm=Gqg8nfip7BfSXe=bag@mail.gmail.com> <F3670415-1AF0-4631-9744-445F1E3AB961@cisco.com> <CALXDUZgXv5mq10WXSmFF94duTWQrFX-ZC7n9tsn8m0c+tk9V0A@mail.gmail.com> <9aae9f97-fa3a-b50f-ee04-a70e1dbc0458@gmail.com>
In-Reply-To: <9aae9f97-fa3a-b50f-ee04-a70e1dbc0458@gmail.com>
From: phani Ayyappa <durgam.iit@gmail.com>
Date: Tue, 29 Jan 2019 08:38:20 -0800
Message-ID: <CALXDUZhgzGtqufQ=bXeOaeC7x48GhwqhuYNR9D9GhTNq4+U_PA@mail.gmail.com>
To: Anish <anish.ietf@gmail.com>
Cc: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007b7f1405809b6c5a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/Kkfo2mfqSd2h6rsQoHYK-3tkfQs>
Subject: Re: [pim] reg any cast rp using pim register mechanism
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Jan 2019 16:38:35 -0000

Hi Anish,
Thanks for the reply.

Thanks
Phani

On Sat, Jan 26, 2019 at 11:49 PM Anish <anish.ietf@gmail.com> wrote:

> Hi Phani,
>
>  For the given scenario you may use anycast-rp register mechanism for
> registering ipv4/v6 customer s.g's b/w AS's. MSDP too may be used for
> registering ipv4 traffic.
>
> Thanks,
>
> Anish
> On 27/01/19 6:36 AM, phani Ayyappa wrote:
>
> Hi Mankamana,
>  Yes. This is related msdp across different domain.  In this case, RP's
> are present  in two different autonomous systems, belong to the same
> customer. These two autonomous systems are connected by ,  overlay
> networks. (makes them reachable with one hop tunnel,  over the under lay.).
> In this scenario, can we use, pim any cast rp, with pim registration
> mechanism to sync the source information across RP's in these two domains ?
>
> Thanks
> Phani.
>
> On Sat, Jan 26, 2019 at 12:36 PM Mankamana Mishra (mankamis) <
> mankamis@cisco.com> wrote:
>
>> Is your question related to using MSDP across different domain ? May be
>> what is the use case you are trying to solve would help .
>>
>>
>> Sent from my iPhone
>>
>> > On Jan 26, 2019, at 19:47, phani Ayyappa <durgam.iit@gmail.com> wrote:
>> >
>> > Hi,
>> >   If the same organization has branches across two different ASes ,
>> then can we use any cast rp using pim registration mechanism for learning
>> sources across these two autonomous systems ?  Please give your opinion on
>> this.
>> >
>> > Thank you
>> > Phani
>> > _______________________________________________
>> > pim mailing list
>> > pim@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pim
>>
>
> _______________________________________________
> pim mailing listpim@ietf.orghttps://www.ietf.org/mailman/listinfo/pim
>
>

v2.23.0 | Report a Bug | By Email