+1, IMHO, Encap/Decap should be part of Tunnel.
Linda -----Original Message----- From: i2rs [mailto:[email protected]] On Behalf Of Manish Kumar (manishkr) Sent: Monday, November 16, 2015 2:18 PM To: Nitin Bahadur; Chris Bowers; Mach Chen; [email protected] Subject: Re: [i2rs] feedback on draft-ietf-i2rs-rib-data-model-03 Encap/Decap belong to a different layer (actually one that ties two layers together) and RIB doesn't look the right place for encap/decap to me. Thanks, Manish On 17/11/15 1:25 am, "i2rs on behalf of Nitin Bahadur" <[email protected] on behalf of [email protected]> wrote: > > >>I find it odd that the current data model provides the ability to >>configure encap, but not decap, for VXLAN. This would require the >>user of the data model to configure VXLAN tunnel-encap using one data model >>and vxlan-decap using another data model. I think this is perhaps an >>indication that VXLAN encap does not belong in the RIB data model either. > >I¹ll buy that argument. And I believe we can extend that argument to >GRE & NVGRE as well. > >Anyone on the list have comments related to this? > >Thanks >Nitin > > >_______________________________________________ >i2rs mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
