Internet-Draft

The official Internet-Draft for SAMP version 0.1, including its current status, specification scope, revision process and priorities for technical review.

SAMP Internet-Draft

The Simple Agent Management Protocol is currently documented in the following individual Internet-Draft:

Simple Agent Management Protocol (SAMP)

draft-efstathiou-samp-agent-management-00

Author: Stelio E. Efstathiou

Published: 17 August 2026

Current version: `-00`

Intended status: Experimental

Document type: Individual Internet-Draft

Current expiration date: 18 February 2027

Status of the Document

An Internet-Draft is a working document used to present technical proposals for discussion, review and further development.

The publication of an Internet-Draft does not mean that the document has been adopted, approved or endorsed by the IETF. An individual Internet-Draft has no formal standing in the IETF standards process unless subsequent action is taken by the relevant IETF community and processes.

The SAMP Internet-Draft is therefore a public technical proposal, not an Internet Standard or RFC.

The `-00` version establishes the initial Experimental protocol baseline and is intended to support:

  • technical review;
  • identification of protocol overlap or unnecessary duplication;
  • validation of operational and security requirements;
  • controlled experimental implementations;
  • framework adapter development;
  • and independent interoperability testing.

Specification Scope

The current Internet-Draft defines:

  • the SAMP architecture and protocol roles;
  • agent lifecycle and trust states;
  • agent profiles and profile categories;
  • autonomy classes;
  • core protocol operations;
  • common message-envelope requirements;
  • transport bindings;
  • authentication and message-integrity mechanisms;
  • replay detection and request correlation;
  • configuration and execution policy;
  • error handling;
  • extensibility considerations;
  • and the initial security model.

SAMP version 0.1 is intentionally limited to an Experimental baseline. Future revisions may change protocol structures, requirements and terminology based on technical review and implementation experience.

Document Evolution

Internet-Drafts are versioned documents.

The current revision is identified by the suffix `-00`. Subsequent revisions will use `-01`, `-02` and so forth.

The Datatracker URL without a version suffix always provides access to the current revision and the complete document history:

https://datatracker.ietf.org/doc/draft-efstathiou-samp-agent-management/

When a new revision is published, earlier versions remain available through the Datatracker for comparison and historical reference.

Internet-Drafts expire if they are not updated within the applicable publication period. Expiration does not automatically indicate rejection, adoption or technical invalidity; it indicates that the particular Internet-Draft revision is no longer active.

Authoritative Source

The published Internet-Draft remains the authoritative source for all normative SAMP protocol requirements.

Content on this website is explanatory and project-oriented. If any website description, article, implementation note or example appears inconsistent with the current Internet-Draft, the Internet-Draft takes precedence.

Implementations should identify the specific SAMP draft version against which they were developed and tested.

Review Priorities

Technical review of the initial version is particularly welcome in the following areas:

  • whether SAMP addresses a genuine operational-management protocol gap;
  • overlap and boundaries with existing or emerging protocols;
  • lifecycle, enrollment and trust-state semantics;
  • agent profile structure and extensibility;
  • autonomy classification;
  • transport and message-envelope design;
  • authentication, authorization and key management;
  • replay protection and retry behavior;
  • safe configuration semantics;
  • policy-gated execution;
  • operational deployment scenarios;
  • and interoperability requirements.

The objective of the `-00` revision is not to claim that every question has been resolved. Its purpose is to provide a concrete technical baseline that can be criticized, implemented and improved.

Technical Feedback

Technical comments, security observations, implementation experience and proposed use cases are welcome.

Contact:

mailto:[email protected]

mailto:[email protected]

Public discussion channels will be referenced on this site as SAMP is introduced to the relevant IETF mailing lists and technical communities.

Important Notice

This document is an individual Internet-Draft.

It is not endorsed by the IETF, has not been adopted by an IETF Working Group, and currently has no formal standing in the IETF standards process.