1. Guidelines Status IETF75 David Harrington

2. 2 draft-ietf-opsawg-operations-and- management Guidelines for considering requirements for operations and management of a protocol draft-07 Publication Requested - May 09 IETF Last Call – May 09 New Version Available (-08-) – June 09 AD Follow up – June 09

3. 3 IETF Last Call Comments GEN-ART –editorial comments – fixed –Ready for publication as BCP

4. 4 IETF Last Call Comments Henning –Might become boilerplate and slow protocol approvals –Make distinction between requirements for new and revised extensions/protocols –Manageability only needed for new protocols Draft-08 –makes distinction but did not follow Hennings suggested solution because, as he said, manageability can be enhanced by deployment experience

5. 5 IETF Last Call Comments Aboba –Text asserts ease of operations and management may impact the success of IETF protocols –RFC5218 discusses what makes a successful protocol. –text assertions should be separated to differentiate issues that are essential for successful global deployment and those that might cripple a protocol Draft-08 –Removes the assertions

6. 6 IETF Last Call Comments Hartman –Not suitable for BCP status –Does not reflect practices across the IETF –Lacks clear actionable guidelines –Not sufficiently clear outside OPS area –interoperability not a primary goal – fixed text

7. 7 IETF Last Call Comments Lear –Not suitable for BCP status –Lacks clear actionable guidelines –interoperability not a primary goal SM –Does not support publication as BCP Eric Rosen –Opposes publication as BCP

8. 8 IETF Last Call Comments Randy Presuhn –Supports publication as Informational –Could reluctantly accept as BCP

9. 9 Draft-ietf-opsawg-nm-survey a survey of existing IETF standards-track NM protocols and data models Needs new editor Needs WG consensus on purpose and direction

10. 10 Thank You Questions? ietfdbh@comcast.net