Aijun, Please see my question regarding the overload bit in section 5.2. What distinguishes each case?
Jeff > On Feb 25, 2026, at 20:03, Aijun Wang <[email protected]> wrote: > > Hi, Jeff and Robert: > > Regarding to the name of "Sequence" field, I think we can modify it later to > "EntryID", which may be more accurate. > And, to Jeff's questions, what's the "two modes" refer to in your question? > > Aijun > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Jeffrey Haas > Sent: Thursday, February 26, 2026 6:11 AM > To: Wei Wang <[email protected]> > Cc: idr <[email protected]>; Robert Raszuk <[email protected]>; BESS > <[email protected]>; Sue Hares <[email protected]>; Keyur Patel <[email protected]> > Subject: [Idr] Re: [bess] Re: Re: Re: Re: draft-ietf-idr-vpn-prefix-orf-25 - > 1 Week WGLC onchanges (1/29/2026 to 1/5/2026) > > Wei, > > >> On Feb 25, 2026, at 04:19, Wei Wang <[email protected]> wrote: >> I think we can add the following sentence in Section 5.2 to clarify that if >> there no VPN Prefix ORF entry on the device, all VPN routes are permit to be >> sent: >> “The default entry for the VPN Prefix ORF type is "Permit All", which means >> that all routes that do not match the existing entries in the VPN Prefix ORF >> table shall be advertised.” >> >> We will update the description of receiver and RR/ASBR according to >> Jeffrey's comment. >> >> Furthermore, I suggest keeping 'Sequence' as it can serve as an identifier >> for operations such as deletion and update of VPN Prefix ORF entries. > > > I'd suggest waiting on changes until the question I asked is answered. It > impacts the suggestions for the updated text. > > What's the difference between the two modes? > > -- Jeff > > _______________________________________________ > Idr mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
