> On Jan 14, 2022, at 6:39 PM, Aijun Wang <[email protected]> wrote: > > Hi, Robert: > > I would say some people are likely to hear other’s explanations, some are > reluctant. > Anyway, I am eager to hear the independent technical analysis. > > For the current scenarios and solutions, we have analyzed that RFC 5316 and > RFC5392 are not suitable for such purposes—we must generate bogus AS, bogus > Remote ASBR Router ID on every inter-AS, or non inter-AS boundary links. > > I would like to hear the constructive comments, or other solutions that > better the the one in this draft.
Chair Hat, Just to be clear, whether this draft is adopted or not does not require that people agree with your solution or provide better ones. The WG has to decide if it actually thinks it's worthwhile to work on the problem at all. Then it also has to decide if this draft in it's current form is the right vehicle to do this work. Only if those 2 things are satisfied will the document be adopted as a WG document. Thanks, Chris. > > Aijun Wang > China Telecom > >> On Jan 15, 2022, at 07:15, Robert Raszuk <[email protected]> wrote: >> >> >> Hi Aijun, >> >> If not, I would say both you and Les’s understanding of this draft is not >> correct. >> >> If two (or more) subject matter experts like Les & John can not understand >> the IGP draft I would not draw an immediate conclusion that this is their >> perception fault. >> >> Instead I would take a step back and see that perhaps there is something >> wrong with the draft itself ? >> >> Thx, >> Robert. >> > _______________________________________________ > Lsr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lsr _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
