NAIPs — NAIS Improvement Proposals

The NAIP process is how changes to the NAIS standard are proposed, discussed, and ratified.

What is a NAIP?

A NAIS Improvement Proposal (NAIP) is a design document that describes a proposed change to the NAIS standard. NAIPs provide a consistent and controlled path for new features, protocol changes, and process improvements.

Process

1. Draft

Open a pull request with a new NAIP document. Use the template below.

2. Discussion

Community review and feedback via PR comments and GitHub Discussions.

3. Review Period

Minimum 14-day review period for non-breaking changes, 30 days for breaking changes.

4. Ratification

Accepted by consensus among active contributors. Merged into this repository.

5. Implementation

Changes are incorporated into the specification and reference implementations.

NAIP Template

# NAIP-XXXX: Title

- **Author:** Name <email>
- **Status:** Draft | Review | Accepted | Rejected | Withdrawn
- **Created:** YYYY-MM-DD
- **Requires:** (list any dependent NAIPs)

## Summary
One-paragraph description of the proposal.

## Motivation
Why is this change needed? What problem does it solve?

## Specification
Technical details of the proposed change.

## Backwards Compatibility
Impact on existing implementations.

## Security Considerations
Any security implications.

## Reference Implementation
Link to implementation if available.

Principles

• Backwards compatible when possible
• Vendor neutral — no single company benefits
• Minimal — solve one problem well
• Built on standards — DNS, HTTPS, JSON

Related

• spec — Current specification
• nais — Main website
• governance — Full governance model