Hi Alvaro,
Thanks for the review. Please see NB> below
(1) Even if just Informative, it would be nice to have a reference to
draft-ietf-i2rs-rib-data-model.
NB> I'm not sure how referencing works. If I understand correctly,
rib-info-model then can't be published until data-model is published...and then
there is circular referencing.
(2) I think that the use of some Normative Language is not as expected.
(2.1) For example, in S2.1 (RIB definition): "There MAY be many routing
instances and each routing instance MAY contain RIBs." In both cases "MAY"
seems to be a statement of fact, and not a normative statement to indicate
that
a routing instance can optionally include RIBs.
NB> Rewording to " A network device MAY contain routing instances and each
routing instance MAY contain RIBs."
Note that S2.2 (Routing
instance) identifies a rib-list as a mandatory component of a routing
instance,
and there's no clear indication that the list may be empty.
NB> Good point. I'll fix that.
(2.2) S2.1: "A routing instance MAY even have two or more RIBs of the same
rib
family (e.g., IPv6)." This use of "MAY" also seems to be stating a fact.
NB> Yes it is a fact. So removed use of "MAY".
(2.3) "MAY be optionally", "MAY contain the following optional fields" are
redundant phrases as MAY already means optional.
NB> Good point. Fixed.
Thanks
Nitin
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
