Hiding Transit-Only Networks in OSPF
RFC 6860
Yes
No Objection
Note: This ballot was opened for revision 05 and is now closed.
(Stewart Bryant; former steering group member) Yes
(Adrian Farrel; former steering group member) (was Discuss) No Objection
Thanks for addressing the majority of my Discuss points and Comments. One issue remains that I have moved from the Discuss to this Comment: I really think that the use of RFC 2119 language in 2.1.2 and subsequent is inappropriate. In my opinion you are just describing what an implementation does if it wants to achieve a particular effect. You are not describing mandatory to implement interoperability behaviors.
(Barry Leiba; former steering group member) No Objection
(Brian Haberman; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection
(Pete Resnick; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Sean Turner; former steering group member) No Objection
I read this draft a couple of times trying to figure out what you were hiding. Then, I read Adrian's mutterings - I'm with him.
(Stephen Farrell; former steering group member) No Objection
- abstract: I'd say s/minimize/reduce/ would be better in the last sentence. (Same for intro.) The point is that you can't know any reasonable "minimum" here, but you can I guess reduce the liklihood of some attacks. - I agree with Adrian's mutterings about the term "hiding." - Section 7 seems very brief to me but then I don't know much about routing. I also wondered that this section has no uppercase 2119 words - is the "recommended" there intended to be the same as RECOMMENDED aka SHOULD? If so, and 5837 (An ICMP extension?) is all that's needed, then I think it'd be clearer to use SHOULD. If not, then couldn't you RECOMMEND some good way to manage these no-longer-routable devices? - Section 8: very much a quibble but I think "unauthorized access" isn't quite right, fewer routers will be exposed-to/ available-for any access, not just unauthorized access. I'd say better might be to just put the full-stop after "exposed." - Section 10, paragraph 2: sigh - the ack for the idea is fine, I'm just non-actionably lamenting the USPTO's idea of invention;-(
(Wesley Eddy; former steering group member) No Objection