Vivek, On 1/8/2016 11:34 AM, Vivek Venkatraman wrote: > > On Thu, Jan 7, 2016 at 8:39 AM, Lou Berger <[email protected] > <mailto:[email protected]>> wrote: > > > > On 1/7/2016 11:12 AM, Vivek Venkatraman wrote: > > > > On Thu, Jan 7, 2016 at 7:36 AM, Lou Berger <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > > > ... > > do you think default originate apply to other safi's such as > > ENCAP, VPN, > > EVPN and whatever comes next? I'm leaning towards no... > > > > > > I feel the same way. The default_originate command need not be > > installed for those AFI/SAFI. But I believe they make sense for the > > multicast AFs and others like labeled-unicast (1/4 or 2/4). > > > VPN = 4 > > > I meant the real (IANA) value, that should be in the protocol packets. > VPN is 128 (1/128 or 2/128) while labeled-unicast is 4. >
> As mentioned in one of my other mails, we have a patch that clearly > demarcates IANA and internal values and maps between them. It is done > as part of our BGP-LU implementation, but I can see if it is useful to > remove the LU part of the code and post it. > > Of course, since SAFI_ENCAP is only a small value (7), it does not > immediately matter (there are only 2 unused slots - 5 and 6 - in the > definitions). Yup, lots (maybe too many) ways to refer to the same thing. Also, FYI the code being discussed has other issues when dealing with normal network announcements, so need to spend some time coming up with the 'right answer'. Will let you know what I/we end up with. Thanks, Lou > > > Lou > > > > > > > _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
