<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.norton-sdlp-obj-format" target="https://datatracker.ietf.org/doc/html/draft-norton-sdlp-obj-format-06">
   <front>
      <title>SDLP Object Format Specification</title>
      <author initials="M." surname="Norton" fullname="Mark Norton">
         <organization>Independent</organization>
      </author>
      <date month="August" day="2" year="2026" />
      <abstract>
	 <t>   This document defines the canonical object format for the Secured
   Digital Lifecycle Protocol (SDLP). The object format specifies the
   normative byte-level representation used for hashing, signing,
   validation, and interoperability across SDLP implementations. All
   SDLP-governed objects MUST follow the canonical encoding, field
   ordering, and serialization grammar defined in this specification.

   Object-Format-06 freezes the canonical envelope grammar and provides
   a concrete example of a fully serialized SDLP object to illustrate
   how DigitalID, InstanceID, Lineage, Timestamp, and Body are encoded
   in practice. This revision also introduces brief application context
   describing how SDLP objects are used in provenance, auditability, and
   regulated-content workflows.

   This document updates and replaces draft-norton-sdlp-obj-format-05
   and provides the authoritative definition of the SDLP object format
   required for interoperable identity, lineage, and lifecycle
   processing.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-norton-sdlp-obj-format-06" />
   
</reference>
