Re: [Idr] [bess] Type 1 RD for Pure IPv6 network -- EVPN
Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Wed, 03 February 2021 10:02 UTC
Return-Path: <muthu.arul@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 B4F543A171E; Wed, 3 Feb 2021 02:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=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 uWmdhmE_9GOm; Wed, 3 Feb 2021 02:02:50 -0800 (PST)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 6543A3A1714; Wed, 3 Feb 2021 02:02:50 -0800 (PST)
Received: by mail-lf1-x132.google.com with SMTP id m22so32457304lfg.5; Wed, 03 Feb 2021 02:02:50 -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=Z630eL1KEMPX3hUg9MfLDIQVsISJSKzFZk5yASOXuEI=; b=EE18aGFiHYT048R2qc31CbBOEb4zG5sPnEECi9q23uSo6h6IIOaIPdhvVh3nrbeUzn MJWhSXhYx99tkCkIqflYNOTKeFIjhNKQAolOGTcvugLogLvbHS/QksBJTGGSqLb3s8qS 3BOZmawEyKft7+/B7E2IOCm6myCGA8+pDmwWgVvH1AGOeyfioASoOHxh94/uvRGFx4r1 dkuu9HDSDwKXIsUxquSE0r8jVVadLJhuycbEpvYfJwZotoUM4JV3Zok9CMr1E8YSDKUw l74q8YHnCoUL240OTg64X3sSXQRbNyQ9xo+IMXIn1KhaJeRN9JGRbvLJuacmBqoLrhip GFww==
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=Z630eL1KEMPX3hUg9MfLDIQVsISJSKzFZk5yASOXuEI=; b=rYrPPtQHhOLcZbcKZrKVqoxbCR887R2k1TXTKOJ8zDWNZ8hadK3uDswhfFpliYhCKs 146R0nGbS3VqBtOGNegEOkO0zkrYAqve0Hew+pi3HcbrHBGRNOqLruSIDoiQkrXV0gSC 7tUtOE9Rmc/K4XiA4oMD7NPAkisNuRLV6fGbpSx2Dea6gEiE4AxlxxJyo7P0UQccfKiK qFzBJcvAaG+RnI81jl2sRq8g5Qn3YyaB3isgab8iM4XbgtfIxQBNWMEOACYICbKj+ilj iAFhIyzI8Ddw/zB8d//qg4iR/NlgiIJOnTHTg+ud+fRu/dnaArA3tEwqu+p/NVB94zcF ia2g==
X-Gm-Message-State: AOAM5301yG5m1YQmPevN7elVQF2Rx+CXi3jI6JxEIpwfY2B0KRMMx9dA u9/jfteTJB9OMp4V1EcmaS9M3DSZ13a4n6ViVDA=
X-Google-Smtp-Source: ABdhPJxdjswUneFYBPyjIDlwBSKZvRDV76QQTDUQrENiPDCohzWScxxwCEAHPm29MAQ0OL80zcUuNK0/ohPR60N4XII=
X-Received: by 2002:a05:6512:514:: with SMTP id o20mr1413076lfb.385.1612346568400; Wed, 03 Feb 2021 02:02:48 -0800 (PST)
MIME-Version: 1.0
References: <CA+JENaK55mrR0hDEbTC62kASxTLtEfbmRkWh-VUhRU3oPQcBVA@mail.gmail.com> <CAKz0y8zOjsHS-_Nm7b_AYVy93zE4aDxvKJ+iTBtMDmdP5SCCoQ@mail.gmail.com> <CABNhwV3Jy_gH351+COn-ta14T5WVb0aixb9598nHHrJceOyz_Q@mail.gmail.com> <CAKz0y8zDkZ9q5f5B7VWdmtSwoXtDhuYzfTRyMpd52-=vpHsOrw@mail.gmail.com> <BYAPR11MB3207920855AA27ED706E8257C0B49@BYAPR11MB3207.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB3207920855AA27ED706E8257C0B49@BYAPR11MB3207.namprd11.prod.outlook.com>
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Wed, 03 Feb 2021 15:32:37 +0530
Message-ID: <CAKz0y8zfowB4vF5-DsdSecbGgwLqnn9vTcrUeJf7zsWwJkKu0Q@mail.gmail.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
Cc: Gyan Mishra <hayabusagsm@gmail.com>, TULASI RAM REDDY <tulasiramireddy@gmail.com>, "bess@ietf.org" <bess@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000076e38805ba6bb0c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/KGWGZL1dw4XwREZSnVnJroEanQE>
Subject: Re: [Idr] [bess] Type 1 RD for Pure IPv6 network -- EVPN
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: Wed, 03 Feb 2021 10:02:53 -0000
Not sure, it was just a question..will let Gyan comment if there are devices out there that don't support RFC6286.. Regards, Muthu On Wed, Feb 3, 2021 at 11:21 AM Jakob Heitz (jheitz) <jheitz@cisco.com> wrote: > Why preclude RFC 6286 ? > > > > Regards, > > Jakob. > > > > *From:* Idr <idr-bounces@ietf.org> *On Behalf Of * Muthu Arul Mozhi > Perumal > *Sent:* Tuesday, February 2, 2021 9:21 PM > *To:* Gyan Mishra <hayabusagsm@gmail.com> > *Cc:* TULASI RAM REDDY <tulasiramireddy@gmail.com>; bess@ietf.org; > idr@ietf.org > *Subject:* Re: [Idr] [bess] Type 1 RD for Pure IPv6 network -- EVPN > > > > Hi Gyan, > > > > Please see inline.. > > Regards, > > Muthu > > > > On Sat, Jan 30, 2021 at 3:26 AM Gyan Mishra <hayabusagsm@gmail.com> wrote: > > Muthu > > > > How does RFa. 6286 AS wide BGP identifier change the BGP path selection > process when all attributes are equal and ‘bestpath compare-routerid” is > uses so the valid/best path is deterministic and oldest versus newest > default. > > The AS wide BGP identifier shouldn't change the BGP path selection process > in this case, since you compare by converting them to host byte order and > treating them as 4-octet unsigned integers as per RFC4271. > > > > > > > > I believe the BGP Identifier just as with OSPF or ISIS does not have to be > routable, so in an IPv6 only network precluding RFC 6286 I believe could > you still use a 4 octet IP address as the router-id. > > > > Right. However, if we preclude RFC6286, then the BGP identifier needs to > be a valid unicast host IPv4 address (for e.g. can't be a multicast > address): > > > > <snip RFC4271> > > Syntactic correctness means that the BGP Identifier field represents > a valid unicast IP host address. > > </snip> > > > > > > > > This question comes up a lot these days as operations migrate to some > flavor of IPv6 only core MPLS LDPv6, SR-MPLSv6, SRv6. > > > > > > Thanks > > > > Gyan > > On Wed, Jan 27, 2021 at 5:45 AM Muthu Arul Mozhi Perumal < > muthu.arul@gmail.com> wrote: > > Hi Tulasi, > > > In pure IPv6 networks, I think using the BGP identifier in place of the IP > address part in the type 1 RD should suffice for all practical purposes. > The only catch is, if it is an AS-wide unique BGP identifier [RFC6286], > then it is not an IP address 'per se'. But, I think it makes no difference > from an interoperability standpoint.. > > Perhaps, in line with RFC6286, we should redefine the IP address part of > the type 1 RD as just a 4-octet, unsigned, non-zero integer.. > > Regards, > > Muthu > > > > On Fri, Jan 22, 2021 at 11:31 AM TULASI RAM REDDY < > tulasiramireddy@gmail.com> wrote: > > Hi All, > > > > In a pure IPv6 network, how do one expect to construct the Type 1 RD. > > As per EVPN RFC 7432 for EAD per ES, it should be Type 1 RD, but if the > loopback address is only IPv6 then what is the expectation here? > > Should we use BGP router ID(32bit) here? > > > > From RFC7432: EVPN > 8.2.1 <https://tools.ietf.org/html/rfc7432#section-8.2.1>. Constructing > Ethernet A-D per Ethernet Segment Route > > The Route Distinguisher (RD) MUST be a Type 1 RD [RFC4364 <https://tools.ietf.org/html/rfc4364>]. The > > *value field comprises an IP address of the PE (typically, the* > > * loopback address)* followed by a number unique to the PE. > > > > Thanks, > > TULASI RAMI REDDY N > > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > -- > > <http://www.verizon.com/> > > *Gyan Mishra* > > *Network Solutions Architect * > > > > *M 301 502-1347 13101 Columbia Pike *Silver Spring, MD > > > >
- [Idr] Type 1 RD for Pure IPv6 network -- EVPN TULASI RAM REDDY
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Muthu Arul Mozhi Perumal
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Gyan Mishra
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Jakob Heitz (jheitz)
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Muthu Arul Mozhi Perumal
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Jakob Heitz (jheitz)
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Muthu Arul Mozhi Perumal
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Gyan Mishra
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Jakob Heitz (jheitz)
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Gyan Mishra
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Jakob Heitz (jheitz)
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Acee Lindem (acee)
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … TULASI RAM REDDY
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Gyan Mishra
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Jakob Heitz (jheitz)
- Re: [Idr] [bess] Type 1 RD for Pure IPv6 network … Gyan Mishra