On May 13, 2022 at 1:47:55 AM, Yingzhen Qu wrote:
Yingzhen: Hi! > The milestones are very aggressive, I’d suggest the architecture document > should be after the problem and the use case documents. I will be posting an updated charter later today. It will address the aggressive milestones and some other things. > For all the protocol extensions, they’re not in the milestones, will they be > included in the corresponding architecture docs? No. The WG will not be chartered to do extension work. Instead, that work will be done in the WGs responsible for each protocol. This will also be reflected in the update. ... > > The "Source Address Validation in Intra-domain and Inter-domain Networks > > (SAVNET)" working group will define a protocol-independent architecture > > and procedures to overcome the limitations of existing SAV mechanisms. > > > [Yingzhen]: what does “protocol-independent architecture” mean here? For the intra-domain solution, for example, there exact extensions and operations may vary from one protocol to another, while still following a common architecture. That's what is meant by protocol-independent, that it shouldn't be specified with just one protocol (or type of protocol) in mind. ... > [Yingzhen]: I must have missed the discussion here. The DSAV framework > presented at IETF 113 was not based on extensions to IGPs for intra-domain, I > understand for inter-domain BGP may be used. Why is it "Where possible, > existing control and management plane protocols must be used within existing > architectures to implement the SAV function” ? This sounds very strict to me. We sensed a preference at the BOF to use extensions rather than to design a new protocol. That is why, as we moved the work to the routing area, we added that text in there. However, the WG may decide, with proper discussion and analysis, to follow a different path. Note that the Charter doesn't mention a specific solution. IOW, this WG is not being chartered to standardize DSAV -- that is a possible outcome, but there may be others too. Thanks! Alvaro. _______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
