Hi Muthu
Please see in-line
On Wed, Feb 3, 2021 at 12:20 AM Muthu Arul Mozhi Perumal <
muthu.a...@gmail.com> wrote:
> Hi Gyan,
>
> Please see inline..
> Regards,
> Muthu
>
> On Sat, Jan 30, 2021 at 3:26 AM Gyan Mishra <hayabusa...@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.
>
Gyan> So with RFC 6286 the 4 octet unsigned could be any number from 1
to 4.2 billion. I see in the remarks that the BGP identifier is to use RFC
4271 process for path selection resolution.
In the route selection, where the BGP Identifier is not used in
comparing a route from an internal neighbor and a route from an
external neighbor. In addition, routes from BGP speakers with
identical BGP Identifiers have been dealt with (e.g., parallel BGP
sessions between two BGP speakers).
When you are comparing two paths with the same router-id and you convert to
host byte order and treat as unsigned integer per RFC 4271 can you give an
example of how that would work. I am not following the verbiage. If the
BGP identifier is the same AS wide would the host byte order be the same
for each BGP speaker?
The BGP Identifier of the local system is compared to the BGP
Identifier of the remote system (as specified in the OPEN
message). Comparing BGP Identifiers is done by converting them
to host byte order and treating them as 4-octet unsigned
integers.
>
>>
>> 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>
>
>
Gyan> I do see that verbiage in section 6.2
If the BGP Identifier field of the OPEN message is syntactically
incorrect, then the Error Subcode MUST be set to Bad BGP Identifier.
Syntactic correctness means that the BGP Identifier field represents
a valid unicast IP host address.
BGP with IGP call back NH tracker checks the NH but how does BGP code
validate the RIB that the router-id is a connected loopback but
and also advertised by IGP. I have not tried it but if you set a
bogus router-id would all the BGP peers go down.
I will try that in the lab.
>>
>> 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.a...@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 <
>>> tulasiramire...@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
>>> i...@ietf.org
>>> https://www.ietf.org/mailman/listinfo/idr
>>>
>> --
>>
>> <http://www.verizon.com/>
>>
>> *Gyan Mishra*
>>
>> *Network Solutions A**rchitect *
>>
>>
>>
>> *M 301 502-134713101 Columbia Pike
>> <https://www.google.com/maps/search/13101+Columbia+Pike?entry=gmail&source=g>
>> *Silver
>> Spring, MD
>>
>> --
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*M 301 502-134713101 Columbia Pike *Silver Spring, MD
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
