I have reviewed this draft as part of the last-call reviews of the Operations Directorate. These comments should be taken by authors and WG chairs just as any other last-call comment. In its abstract this document mentions: "This document defines the default behavior of a BGP speaker when there is no import or export policy associated with an External BGP session." Introduction The document's introduction describes a well known operational caveat that has caused countless headaches over the years to those involved in BGP operations. A BGP speaker may, and in may cases, will, accept and publish anythin to its neighbors when there is no more specific routing policy applied. Proposed solution The document proposes a set of default behaviours for BGP speakers in the absence of configured routing policies. The document references RFC4271 in the second paragraph. I believe it would benefit from referencing 4271 in the third paragraph for the definition of "EBGP peer". The fourth paragraph proposes a default operating mode of "import nothing" and "export nothing". This terminology should be familiar for anyone working on BGP operations. I however believe the reader would benefit from a provided definition of these terms. The above comments are all minor points and Overall I believe the document is clear and well written and ready to move forward.