IETF Logo Mail Archive

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

phani Ayyappa <durgam.iit@gmail.com> Sun, 27 January 2019 01:06 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 F41731288BD for <pim@ietfa.amsl.com>; Sat, 26 Jan 2019 17:06:32 -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 5mhkVBJ8Ts9K for <pim@ietfa.amsl.com>; Sat, 26 Jan 2019 17:06:30 -0800 (PST)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 D308812426A for <pim@ietf.org>; Sat, 26 Jan 2019 17:06:30 -0800 (PST)
Received: by mail-pl1-x632.google.com with SMTP id p8so6186523plo.2 for <pim@ietf.org>; Sat, 26 Jan 2019 17:06:30 -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=gDcT3HHOBlqp/NZ7Vg6x2RgtkoDp+37Xtcn1w459ho0=; b=LuhL0cNd7lscdvhEOkazKMwDHjVPkzjwSW/PXSDLgQy9VXk+fPSGumcbIHJaRH+xhC L0dNFl4MUauPI3jxRCISrSlJ//dXabJpkv913XqcUe70JUmbFDiKx32bWyc7ODw2AIMq od+cMMjYj5aEWvi8kADfTAxQZCK3MKhD4aHarCZHCxQms6JY1Vn8Q8UNuVVzn9POfXH7 +vOM4hnP+eT+c/LfLrwTASlXyt7rRhWFDr73dUeSm0wHuFpdtMnAeLe5HTAyDUytno1y pQ3DxMxFUwxdd0MsixrFwSiznRfvGHzchRu0s6QljzvYFzoxmYL+5nAc2o2WZ2Py4ppO qwcw==
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=gDcT3HHOBlqp/NZ7Vg6x2RgtkoDp+37Xtcn1w459ho0=; b=Gro5/t30zvdqheQ1zYYKmznNE3Prt+sxw1DlyN+wPNKVOnwVzmPDdqlkQuxVIVeNKx vv4eAAqdyrWQSHXaVTKA9+lz/ghAqbDobh4AsMzlj3hIoGvdxj/tZit5tky5ZaJCg53z qh1e7qfPVj2ehyzrqIxyyZBlIq5ESD2EvWro6cLfXESE3ZQI4VPfdAOGC3OOZJGcTDlv akAEXY1eRa1lgRXkgNApx/g+xatY7rZENWju1tBYF5e4uvcu8MAiqL51kXmc22V227qH HQMuosx0aYyD7QK6abDEQM/ItjBfbNCWzh3Nz1j05XE+Z6/E5HGHkdGQXt8J8IWl3rD2 RFBg==
X-Gm-Message-State: AJcUukdhPBxbDCOyTngKpLLI9zuBzMHFlscpup5XckwTR3UxRjbcpFw4 QagKPJ5uoC1sLS6ddm+a5QHJhS79WpvZHqKQi3o=
X-Google-Smtp-Source: ALg8bN7BNRdef+TzfvwVvNp06gYF8wouXK7EoOQfp4UDznmRhimjHj4rEcEbUMEiUlw/WkRSeACsEdXcv1+Cx1S59v4=
X-Received: by 2002:a17:902:82c2:: with SMTP id u2mr16702389plz.110.1548551190043; Sat, 26 Jan 2019 17:06:30 -0800 (PST)
MIME-Version: 1.0
References: <CALXDUZhfLspOKfw0H5k_=1Xhp0Aestm=Gqg8nfip7BfSXe=bag@mail.gmail.com> <F3670415-1AF0-4631-9744-445F1E3AB961@cisco.com>
In-Reply-To: <F3670415-1AF0-4631-9744-445F1E3AB961@cisco.com>
From: phani Ayyappa <durgam.iit@gmail.com>
Date: Sat, 26 Jan 2019 17:06:19 -0800
Message-ID: <CALXDUZgXv5mq10WXSmFF94duTWQrFX-ZC7n9tsn8m0c+tk9V0A@mail.gmail.com>
To: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
Cc: "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000995f620580662b5c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/Tx46V7YGplDZOxookAoYMyZhZBE>
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: Sun, 27 Jan 2019 01:06:33 -0000

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
>

v2.23.0 | Report a Bug | By Email