draft-ietf-opsawg-operations-and-management-08.txt   draft-ietf-opsawg-operations-and-management-09.txt 
Network Working Group D. Harrington Network Working Group D. Harrington
Internet-Draft Huawei Technologies USA Internet-Draft HuaweiSymantec USA
Intended status: BCP June 23, 2009 Intended status: Informational September 10, 2009
Expires: December 25, 2009 Expires: March 14, 2010
Guidelines for Considering Operations and Management of New Protocols Guidelines for Considering Operations and Management of New Protocols
and Protocol Extensions and Protocol Extensions
draft-ietf-opsawg-operations-and-management-08 draft-ietf-opsawg-operations-and-management-09
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 43 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 25, 2009. This Internet-Draft will expire on March 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 13 skipping to change at page 3, line 13
considered. considered.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. Designing for Operations and Management . . . . . . . . . 5 1.1. Designing for Operations and Management . . . . . . . . . 5
1.2. This Document . . . . . . . . . . . . . . . . . . . . . . 5 1.2. This Document . . . . . . . . . . . . . . . . . . . . . . 5
1.3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4. Background . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4. Background . . . . . . . . . . . . . . . . . . . . . . . . 7
1.5. Available Management Technologies . . . . . . . . . . . . 8 1.5. Available Management Technologies . . . . . . . . . . . . 8
1.6. Terminology . . . . . . . . . . . . . . . . . . . . . . . 9 1.6. Terminology . . . . . . . . . . . . . . . . . . . . . . . 8
2. Operational Considerations - How Will the New Protocol Fit 2. Operational Considerations - How Will the New Protocol Fit
Into the Current Environment? . . . . . . . . . . . . . . . . 9 Into the Current Environment? . . . . . . . . . . . . . . . . 9
2.1. Operations . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1. Operations . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2. Installation and Initial Setup . . . . . . . . . . . . . . 10 2.2. Installation and Initial Setup . . . . . . . . . . . . . . 10
2.3. Migration Path . . . . . . . . . . . . . . . . . . . . . . 11 2.3. Migration Path . . . . . . . . . . . . . . . . . . . . . . 11
2.4. Requirements on Other Protocols and Functional 2.4. Requirements on Other Protocols and Functional
Components . . . . . . . . . . . . . . . . . . . . . . . . 11 Components . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5. Impact on Network Operation . . . . . . . . . . . . . . . 12 2.5. Impact on Network Operation . . . . . . . . . . . . . . . 12
2.6. Verifying Correct Operation . . . . . . . . . . . . . . . 13 2.6. Verifying Correct Operation . . . . . . . . . . . . . . . 13
3. Management Considerations - How Will The Protocol be 3. Management Considerations - How Will The Protocol be
skipping to change at page 4, line 6 skipping to change at page 5, line 4
4.3. Placement of Operations and Manageability 4.3. Placement of Operations and Manageability
Considerations Sections . . . . . . . . . . . . . . . . . 28 Considerations Sections . . . . . . . . . . . . . . . . . 28
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
6. Security Considerations . . . . . . . . . . . . . . . . . . . 28 6. Security Considerations . . . . . . . . . . . . . . . . . . . 28
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29
8. Informative References . . . . . . . . . . . . . . . . . . . . 29 8. Informative References . . . . . . . . . . . . . . . . . . . . 29
Appendix A. Operations and Management Review Checklist . . . . . 32 Appendix A. Operations and Management Review Checklist . . . . . 32
A.1. Operational Considerations . . . . . . . . . . . . . . . . 32 A.1. Operational Considerations . . . . . . . . . . . . . . . . 32
A.2. Management Considerations . . . . . . . . . . . . . . . . 35 A.2. Management Considerations . . . . . . . . . . . . . . . . 35
A.3. Documentation . . . . . . . . . . . . . . . . . . . . . . 36 A.3. Documentation . . . . . . . . . . . . . . . . . . . . . . 36
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
Often when new protocols or protocol extensions are developed, not Often when new protocols or protocol extensions are developed, not
enough consideration is given to how the protocol will be deployed, enough consideration is given to how the protocol will be deployed,
operated and managed. Retrofitting operations and management operated and managed. Retrofitting operations and management
mechanisms is often hard and architecturally unpleasant, and certain mechanisms is often hard and architecturally unpleasant, and certain
protocol design choices may make deployment, operations, and protocol design choices may make deployment, operations, and
management particularly hard. This document provides guidelines to management particularly hard. This document provides guidelines to
help protocol designers and working groups consider the operations help protocol designers and working groups consider the operations
skipping to change at page 6, line 30 skipping to change at page 6, line 30
model is needed, or imply that using a specific management protocol model is needed, or imply that using a specific management protocol
is mandatory. If protocol designers conclude that the technology can is mandatory. If protocol designers conclude that the technology can
be managed solely by using proprietary command line interfaces be managed solely by using proprietary command line interfaces
(CLIs), and no structured or standardized data model needs to be in (CLIs), and no structured or standardized data model needs to be in
place, this might be fine, but it is a decision that should be place, this might be fine, but it is a decision that should be
explicit in a manageability discussion, that this is how the protocol explicit in a manageability discussion, that this is how the protocol
will need to be operated and managed. Protocol designers should will need to be operated and managed. Protocol designers should
avoid having manageability pushed for a later phase of the avoid having manageability pushed for a later phase of the
development of the standard. development of the standard.
Any decision to make a Management Considerations section a mandatory
publication requirement for IETF documents is the responsibility of
the IESG, or specific area directors, or working groups, and this
document avoids recommending any mandatory publication requirements.
For a complex protocol, a completely separate draft on operations and
management might be appropriate, or even a completely separate WG
effort.
This document discusses the importance of considering operations and This document discusses the importance of considering operations and
management by setting forth a list of guidelines and a checklist of management by setting forth a list of guidelines and a checklist of
questions to consider, which a protocol designer or reviewer can use questions to consider, which a protocol designer or reviewer can use
to evaluate whether the protocol and documentation address common to evaluate whether the protocol and documentation address common
operations and management needs. Operations and management are operations and management needs. Operations and management are
highly dependent on their environment, so most guidelines are highly dependent on their environment, so most guidelines are
subjective rather than objective. subjective rather than objective.
1.3. Motivation 1.3. Motivation
skipping to change at page 36, line 22 skipping to change at page 36, line 22
A.3. Documentation A.3. Documentation
Is an operational considerations and/or manageability section part of Is an operational considerations and/or manageability section part of
the document? the document?
Does the proposed protocol have a significant operational impact on Does the proposed protocol have a significant operational impact on
the Internet? the Internet?
Is there proof of implementation and/or operational experience? Is there proof of implementation and/or operational experience?
Appendix B. Change Log
-- Note to RFC Editor: Please remove this section upon publication as
an RFC
Changes from opsawg-05 to opsawg-06
Spelling and grammar corrections
Addressed comments from WGLC.
Editorial comments
Addressed most comments from Randy Bush, Bert Wijnen, Adrian
Farrel,
Removed IETF Management Framework section.
Added discussion of standard protocols.
Changes from opsawg-04 to opsawg-05
added bullets for appendix checklist
aligned checklist order and guidelines order
resolved all DISCUSS and TODO issues.
Changes from opsawg-03 to opsawg-04
improved wording in Introduction
added a number of DISCUSS points raised during WG reviews
added more wording on service management
updated references and copyrights
Changes from opsawg-02 to opsawg-03
From reviews by Lixia Zhang and feedback from WG Chairs' Lunch.
added discussion of impact on the Internet to checklist
spell check
added examples
added discussion of default values
added discussion of database-driven configuration
fixed some references
expanded the checklist
Changes from opsawg-01 to opsawg-02
moved survey of protocols and data models to separate document
changed "working group" to "protocol designer" throughout, as
applicable.
modified wording from negative to positive spin in places.
updated based on comments from Ralf Wolter and David Kessens
Changes from opsawg-00 to opsawg-01
moved Proposed Standard data models to appendix
moved advice out of data model survey and into considerations
section
addressed comments from Adrian and Dan
modified the Introduction and Section 2 in response to many
comments.
expanded radius and syslog discussion, added psamp and VCCV,
modified ipfix,
Changes from harrington-01 to opsawg-00
added text regarding operational models to be managed.
Added checklist appendix (to be filled in after consensus is
reached on main text )
Changes from harrington-00 to harrington-01
modified unclear text in "Design for Operations and Management"
Expanded discussion of counters
Removed some redundant text
Added ACLs to Security Management
Expanded discussion of the status of COPS-PR, SPPI, and PIBs.
Expanded comparison of RADIUS and Diameter.
Added placeholders for EPP and XCAP protocols.
Added Change Log and Open Issues
Author's Address Author's Address
David Harrington David Harrington
Huawei Technologies USA HuaweiSymantec USA
1700 Alma Dr, Suite 100 20245 Stevens Creek Blvd
Plano, TX 75075 Cupertino, CA 95014
USA USA
Phone: +1 603 436 8634 Phone: +1 603 436 8634
Fax: Fax:
EMail: dharrington@huawei.com EMail: ietfdbh@comcast.net
URI: URI:
 End of changes. 9 change blocks. 
125 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/