>> >>> >> >3. Section 6 >> ><route> ::= <match> <nexthop-list> >> > [<route-attributes>] >> > [<route-vendor-attributes>] >>
>> Another attribute may be needed is the I2RS client identifier, since >>there will be multiple clients that may install route into the rib. The client identifier should be a part of the I2RS data protocol, rather than RIB model. Since the same client-id will be reusable across many other things (not just RIB). I guess we will closely monitor the status of the data protocol and can later figure out where to put the client-id. I agree that the client-id needs to go somewhere. Thanks Nitin _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
