Hi Fangwei I understand. But this draft should only state mapping from VFI to VNID and should be agnostic on how VFI is derived. It can be derived from port, VLAN, (port, VLAN), etc.
Please update the draft to only mention VFI to VNID mapping. Regards, Shahram > On Apr 6, 2016, at 9:13 AM, [email protected] wrote: > > Hi，Davari > Thanks for you comments. > Please check my reply with[hfw]. > > >Hi, > > >I like to repeat my comments in today’s NVO3 meeting. This draft goes way > >beyond the RFC and accepted VXLAN drafts. It introduces new modes that are > >not required and >not supported in any implementation. Such as L2 interface > >to VNID mapping or MAC_DA to VNID mapping. > > >I would like to only see VLAN mapping to VNID, which is consistent with > >VXLAN RFC and drafts, else I am against this draft becoming a WG draft,. > > [hfw] Actually, we have implement the L2 interface to VNID mapping in the > product. > > Thanks > Regards. > Fangwei. > > > > > "S. Davari" <[email protected]> > 发件人: "nvo3" <[email protected]> > 2016-04-05 02:24 > > 请答复 给 > "S. Davari" <[email protected]> > > 收件人 > "[email protected]" <[email protected]>, > 抄送 > 主题 > [nvo3] Issue with draft-chen-nvo3-vxlan-yang-02 > > > > > Hi, > > I like to repeat my comments in today’s NVO3 meeting. This draft goes way > beyond the RFC and accepted VXLAN drafts. It introduces new modes that are > not required and not supported in any implementation. Such as L2 interface > to VNID mapping or MAC_DA to VNID mapping. > > I would like to only see VLAN mapping to VNID, which is consistent with > VXLAN RFC and drafts, else I am against this draft becoming a WG draft,. > > Thx > Shahram Davari > Broadcom > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
