[Idr] [2nd Try] Re: [EVPN] RFC7432: Query on IPv6 Originating Router's IP Address usage with Inclusive Multicast Ethernet Tag Route

TULASI RAM REDDY <tulasiramireddy@gmail.com> Fri, 22 January 2021 06:12 UTC

Return-Path: <tulasiramireddy@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B12B3A1111; Thu, 21 Jan 2021 22:12:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 xYBkWisOKybn; Thu, 21 Jan 2021 22:12:27 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 65D213A0E1E; Thu, 21 Jan 2021 22:12:27 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id f6so4101869ots.9; Thu, 21 Jan 2021 22:12:27 -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; bh=h2094dK36iisQUtIuH4O0ZNqiLdEF55sulb8LTgbLB8=; b=IIsbdXFiRmbHq1pekty+qpJavDfXL9Ynf0mBQSMZDIf1BON3sOa79f0yrGT81J326d DOmPrdwWNi7xsTsjcbBTI1yPTHhQ9NwMKgz6XdXQj6JuPKela4eUxbn/ev3o6wikxgQ4 Gj+eYxio1qqy9DKJH314qEC8xlNJ3WqeZkvmqR/HulsGc5K8nibn14lPdE031qwj+6WW MehoJRvmNUutNfvs8FIOttKx4jPP1E6c0R8VIR1f275r44Ct8i8vVGNO2Rj+PYGtzX8r BlfAsKOaK5+5lnxdBdyUQku+c+oQWczwQD5rWYvgLxQnPdzo2ro6pQ8OAd7iqNw8t3Kq 9Zww==
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; bh=h2094dK36iisQUtIuH4O0ZNqiLdEF55sulb8LTgbLB8=; b=dDdmdNLt69M6DfHZDBAWHBes7KicJN8Wh3/ZXwjDKxHwv9c6McEedivxcvTe1T4Ygf BU2/0B4MHdZcc3w2H+51KtRFEmTc2pyQeNIv65S00+CE7+JeKws6FDd+4uK8xW2ltl8Z dWZstRVE3ZA+2UlInuZQuLY0G7EGzdELcIyVpAxqkkItRCQoKQB1PwkhQnkZx7EWtcpn jUEHqxzyFR66CWJQW6tcKlyVQFehOMk21WFIaMBPV8f43aO56ts5y62G6GTlg30vu8QO Tm3z/C5Y18jFgKW+PX7nH5wUEUej+Mt2BgmgME2ROPbr0fc7gTpSIjxz/SjuG+ieVhuC Wi4A==
X-Gm-Message-State: AOAM5313OYWjMyYygSV3gVzrJtbKKahT5SMQx4yOutm6h5jjWAjV1sHv Kyagp2xR+87b2IjLM7pVdpNNXc8SmAq6BiskN/hqNKGB8Lc=
X-Google-Smtp-Source: ABdhPJwVw6CCCT0sW1TEMfscK+//wI6uoQbheICY8FMDeTU9LDFN9tqTuLKH2f2KdahJl4LIkvsbEe5eARcxy3MpoO0=
X-Received: by 2002:a9d:6f17:: with SMTP id n23mr2223009otq.371.1611295946548; Thu, 21 Jan 2021 22:12:26 -0800 (PST)
MIME-Version: 1.0
References: <CA+JENaLUa6YtJwOmAQhU_Qu7TBK9-sHJqE2tV2tYT4FJyo-sYQ@mail.gmail.com> <CA+JENaJp_+YTBxoQAsfvOQaOPQUOwHjge7OweqN5pjWpyE9_tw@mail.gmail.com>
In-Reply-To: <CA+JENaJp_+YTBxoQAsfvOQaOPQUOwHjge7OweqN5pjWpyE9_tw@mail.gmail.com>
From: TULASI RAM REDDY <tulasiramireddy@gmail.com>
Date: Fri, 22 Jan 2021 11:42:14 +0530
Message-ID: <CA+JENa+9AJO9fGj6q8PXHLxhVhusfBb72GoOqiG9z7yShpm+Dg@mail.gmail.com>
To: bess@ietf.org, idr@ietf.org
Content-Type: multipart/alternative; boundary="00000000000085a7c605b9771293"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/xAqebcSg51utqRXbs_A0F1imBJg>
Subject: [Idr] [2nd Try] Re: [EVPN] RFC7432: Query on IPv6 Originating Router's IP Address usage with Inclusive Multicast Ethernet Tag Route
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 06:12:29 -0000

Hi All,

Awaiting for inputs on this.

Thanks,
Tulasi.
On Tue, Jan 19, 2021 at 11:04 AM TULASI RAM REDDY <tulasiramireddy@gmail.com>
wrote:

> +IDR WG
> Can some one please help on this?
>
> Thanks,
> Tulasi.
>
> On Mon, Jan 18, 2021 at 7:57 AM TULASI RAM REDDY <
> tulasiramireddy@gmail.com> wrote:
>
>> Hi All,
>>
>>
>>
>> According to below note in “Sec 11.1.  Constructing Inclusive Multicast
>> Ethernet Tag Route”, It looks implementation can
>>
>> use BGP router ID(32-bit) as Originating Router's IP Address even with
>> pure IPv6 deployment..
>>
>>
>>
>> If the implementation choose this way, does it cause any known
>> interoperable issues or
>>
>> It is expected to use IPv6 loopback address here as the originating
>> router IP address with IPv6 BGP peering?
>>
>>
>>
>> It will be great, if someone throws light on the major implementations
>> here..
>>
>>
>>
>> <snip: “Sec 11.1.  Constructing Inclusive Multicast Ethernet Tag Route”>
>>
>>    The Originating Router's IP Address field value MUST be set to an IP
>>
>>    address of the PE that should be common for all the EVIs on the PE
>>
>>    (e.g., this address may be the PE's loopback address).  The IP
>>
>>    Address Length field is in bits.
>>
>> </snip>
>>
>>
>>
>> Thanks,
>>
>> Tulasi.
>>
>
>
> --
> TULASI RAMI REDDY N
>


-- 
TULASI RAMI REDDY N