Thanks for the review Mike. May I add that I am also missing an IPR statement as required per RFC2026 sect 10.
And... you issued the doc in Nov 2002, and have listed that it expires in Dec 2002. Should we still be reviewing this doc? Let us hope that ietf secretariat does not use that date that you put in the doc ;-) W.r.t. > 11.) I notice that ranges have been added to ipForwardPolicy and > ipCidrRouteTos index variables to ensure that they are non-negative. > That's not actually required by the SMI, and, strictly speaking, > it is not a legal revision. It is probably acceptable since it > cannot possibly change anything on the wire, but another solution > would be to leave these as-is and turn off the the strict checking > in your SMICng include file (#removeOpt "B"). > I have been encouraging people to add ranges to index objects when/if they make sense. And I think in this case they do make sense. As you say, strictly once cannot make such a change. But also, strictly, a negative index is not allowed. Bert -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
