IETF Logo Mail Archive

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

Anish <anish.ietf@gmail.com> Sun, 27 January 2019 07:49 UTC

Return-Path: <anish.ietf@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 D7264128D0C for <pim@ietfa.amsl.com>; Sat, 26 Jan 2019 23:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 0W8mob1RS2ZO for <pim@ietfa.amsl.com>; Sat, 26 Jan 2019 23:49:31 -0800 (PST)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 DE6041288BD for <pim@ietf.org>; Sat, 26 Jan 2019 23:49:30 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id e5so6392902plb.5 for <pim@ietf.org>; Sat, 26 Jan 2019 23:49:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=3SXHMV92kHEW96/poAnqIv2ZqQqUCboTJhYG1ZWRZDM=; b=DzoKmiBcSADyPe5TvflzJyl4/A3NKS1uf65HhDCpR9SSNvuJex3Kw7bRIBZJ2Klzw5 jjmOqFcNMqalGzY02QnEKG6/6zMEpl9eajNnvmQHLRmquClxz++xgXa6dI3S7OOXlbs0 jE6bMXCBEoVBP49NTNFyh4bnX2I4Pd3hca++57R+CaOglFIAXaYJGiSKKaDuooIf91v5 91sQDmKzxis4viiigSWZfYiUWrBRhYFVOMV76RO1KXgTHU4cj8mABHZ9QVtD49Sanjwn LXCZdh/HoU8QXcBDESTGOOYPwudMnxTXfzB2yNpBj0QnQryJCnGqCsqwC+ccRvXk3JjB QvEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=3SXHMV92kHEW96/poAnqIv2ZqQqUCboTJhYG1ZWRZDM=; b=LmsYTctbFCGnl5yI0j+fXCq3xvPsagwtZ9uS+vtl219u9QFG0Q8/0UFyvW3Ct2B8rU qgRkw6itxGR+5F46rTVQMYdlCiQl1w1BL8x7G6k8JmnnFMVS5bne0dKQJhzVxur8+tCw VHlGJ6YIBDXOqgMD9Fgf/76zqC1c2udziOeaJDx/h8eR0XUQFZgkvDgNODB8FBmq5R4Y YJwwrTaJS6on7RC4mb0ywvtZeBImBqBArEJjhzMwmvYbDas+AMLVSkw/JCdVjQUjrDJv HI6YswOoHYO4B3yEA2sTdbNNPIS7i+oZkcLn4y3+jDLMjfI/WMCXAHDn3xASTHJQ0FIN mvkA==
X-Gm-Message-State: AJcUukdbxRogUnozaqNRKr0nFUWSvW9Enky7dr1Q1PZobxxPrY8HuCp9 RLQYIU1Dcq0W3KHSZYKhfgvHwW7L
X-Google-Smtp-Source: ALg8bN6V9P7jXQ2FLJM9qi+hDju4a44ONA0VrhUuoXcL3uBqbTbpyQp+eb12rFpfFuvy0/K3b5JUuQ==
X-Received: by 2002:a17:902:4081:: with SMTP id c1mr17729785pld.87.1548575370162; Sat, 26 Jan 2019 23:49:30 -0800 (PST)
Received: from [192.168.1.3] ([183.82.22.70]) by smtp.gmail.com with ESMTPSA id s190sm39687976pfb.103.2019.01.26.23.49.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 26 Jan 2019 23:49:29 -0800 (PST)
To: phani Ayyappa <durgam.iit@gmail.com>, "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
Cc: "pim@ietf.org" <pim@ietf.org>
References: <CALXDUZhfLspOKfw0H5k_=1Xhp0Aestm=Gqg8nfip7BfSXe=bag@mail.gmail.com> <F3670415-1AF0-4631-9744-445F1E3AB961@cisco.com> <CALXDUZgXv5mq10WXSmFF94duTWQrFX-ZC7n9tsn8m0c+tk9V0A@mail.gmail.com>
From: Anish <anish.ietf@gmail.com>
Message-ID: <9aae9f97-fa3a-b50f-ee04-a70e1dbc0458@gmail.com>
Date: Sun, 27 Jan 2019 13:19:27 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <CALXDUZgXv5mq10WXSmFF94duTWQrFX-ZC7n9tsn8m0c+tk9V0A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------842D518C79DB1DDCDBBCBDCE"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/ZCvG_TaXPEXA394kNufXZbSIyTk>
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 07:49:33 -0000

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

v2.23.0 | Report a Bug | By Email