Re: [bess] Minor comment on draft-ietf-bess-evpn-inter-subnet-forwarding

2019-02-11 Thread Ali Sajassi (sajassi)
Please see my reply inline marked by “AS>”.

From: BESS  on behalf of Muthu Arul Mozhi Perumal 

Date: Wednesday, February 6, 2019 at 11:33 PM
To: "bess@ietf.org" 
Subject: [bess] Minor comment on draft-ietf-bess-evpn-inter-subnet-forwarding

Section 6.2.1 says the following:

   Each NVE advertises a Route Type-5 (RT-5, IP Prefix Route defined in
   [EVPN-PREFIX]) for each of its subnet prefixes with the IP address of
   its TS as the next hop (gateway address field) as follow:

   - RD associated with the IP-VRF
   - ESI = 0
   - Ethernet Tag = 0;
   - IP Prefix Length = 32 or 128
   - IP Prefix = SNi
   - Gateway Address = IPi; IP address of TS
   - Label = 0

Here, s/IP Prefix Length = 32 or 128/IP Prefix Length = 0 to 32 or 0 to 128

AS> Done. Thanks for catching it.

Regards,
Muthu
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


[bess] Minor comment on draft-ietf-bess-evpn-inter-subnet-forwarding

2019-02-06 Thread Muthu Arul Mozhi Perumal
Section 6.2.1 says the following:

   Each NVE advertises a Route Type-5 (RT-5, IP Prefix Route defined in
   [EVPN-PREFIX]) for each of its subnet prefixes with the IP address of
   its TS as the next hop (gateway address field) as follow:

   - RD associated with the IP-VRF
   - ESI = 0
   - Ethernet Tag = 0;
   - IP Prefix Length = 32 or 128
   - IP Prefix = SNi
   - Gateway Address = IPi; IP address of TS
   - Label = 0

Here, s/IP Prefix Length = 32 or 128/IP Prefix Length = 0 to 32 or 0 to 128

Regards,
Muthu
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess