RFC-RFCSTD-0004                                                   Section 4
Category: Standards Track                           Formatting Standards

# N. Section Title

[← Previous](./prev.md) | [Index](./00-index.md) | [Next →](./next.md)

---

RFC-BCP-<DOMAIN>-<NUMBER>

### Guideline N — Title
 
**Recommendation**: [Statement using SHOULD/RECOMMENDED]
 
**Rationale**: [Why this is recommended]
 
**Applicability**: [When to apply]
 
**Exceptions**: [When this may not apply]

### Procedure N — Title
 
**When to Use**: [Trigger conditions]
 
**Prerequisites**:
- [What must be true before starting]
 
**Steps**:
1. [First step - describe action, not command]
2. [Second step]
...
 
**Verification**: [How to confirm success]
 
**Recovery**: [What to do if procedure fails]

## Trade-offs
 
### Automated vs Manual Rotation
 
| Factor | Automated | Manual |
|--------|-----------|--------|
| Consistency | High | Variable |
| Operator burden | Low | High |
| Flexibility | Low | High |
| Audit trail | Automatic | Requires discipline |
 
**Recommendation**: Prefer automated rotation. Use manual rotation for
secrets that cannot be automated or during automation failures.

**Exceptions**:
- Emergency rotations due to suspected compromise SHOULD proceed
  immediately regardless of traffic levels.
- Automated rotations with proven reliability MAY proceed during
  any period.
- First-time rotations SHOULD be scheduled during low-traffic
  periods even if automation is used.