SDLP Architecture (arch)
draft-norton-sdlp-arch-00

Internet-Draft                                                 M. Norton
Intended status: Informational                               Independent
Expires: November 30, 2026                                  May 31, 2026

                 SDLP Architecture (arch)
                   draft-norton-sdlp-arch-00

M. Norton
Email: mark433norton@gmail.com
May 2026

This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
https://www.ietf.org/1id-abstracts.html

The list of Internet-Draft Shadow Directories can be accessed at
https://www.ietf.org/shadow.html

Abstract

   The Secured Digital Lifecycle Protocol (SDLP) defines a universal,
   lifecycle-governed framework for the creation, identity,
   transformation, distribution, and retirement of digital goods.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at the RFC Editor
   website.

Copyright Notice

Copyright (c) 2026 IETF Trust and the persons identified as the
document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document.

This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.


1.  Introduction

   The Secured Digital Lifecycle Protocol (SDLP) defines a structured,
   identity-anchored, lifecycle-driven model for digital goods. It
   establishes the conceptual foundation upon which all subsequent SDLP
   specifications will be built.

2.  Purpose of SDLP

   SDLP exists to address three systemic issues in digital goods:
   identity ambiguity, uncontrolled duplication, and undefined lifecycle
   transitions. SDLP provides a universal framework to ensure that every
   digital object has a clear identity, lineage, and lifecycle.

3.  Design Principles

   SDLP is governed by three core principles:

   *  P1. Identity First -- Every digital object must possess a
      persistent DigitalID.

   *  P2. Lifecycle Determinism -- Every object must exist in exactly
      one lifecycle state at any given time.

   *  P3. Transformation Integrity -- All transformations must be
      explicit, authenticated, and lineage-preserving.

4.  Terminology

   DigitalID:  The persistent identity of a digital object.

   Instance:  A specific materialization of a DigitalID.

   Lifecycle State:  A protocol-defined phase of existence.

   Transformation:  A rule-governed change to an object or instance.

   Retirement:  The terminal lifecycle state.

5.  Lifecycle Model Overview

   SDLP defines a universal lifecycle model consisting of:

   1.  Creation
   2.  Activation
   3.  Distribution
   4.  Transformation
   5.  Verification

  6.  Retention
   7.  Retirement

draft-norton-sdlp-identity will define the DigitalID
specification. draft-norton-sdlp-lifecycle will define the
lifecycle state machine. draft-norton-sdlp-obj-format will
define transformation rules and lineage guarantees.


6.  Out-of-Scope Items

   The following are explicitly out of scope for this document:

   *  Implementation details
   *  Transport mechanisms
   *  Storage formats
   *  Cryptographic algorithm selection
   *  Commercial licensing models
   *  UI or UX considerations

7.  Security Considerations

   SDLP requires that all lifecycle transitions be authenticated,
   authorized, and recorded. Identity spoofing, unauthorized
   transformations, and lineage tampering must be mitigated by
   protocol-level controls defined in later SDLP documents.

8.  IANA Considerations

   This document makes no requests of IANA.

Appendix A.  Rationale for RFC 0

   RFC 0 exists to establish the philosophical and structural foundation
   of SDLP before defining any technical mechanisms. It ensures that all
   subsequent SDLP documents share a unified conceptual framework.

Author's Address

M. Norton
El Mirage, Arizona
United States
Email: mark433norton@gmail.com