[doseta-discuss] Fwd: New Version Notification for draft-crocker-doseta-base-03.txt

Dave CROCKER dhc at dcrocker.net
Tue Jul 12 08:59:03 PDT 2011


Latest version is at:

    <https://datatracker.ietf.org/doc/draft-crocker-doseta-base/>

With a diff file at:

    <http://tools.ietf.org/rfcdiff?url2=draft-crocker-doseta-base-03>


Significant changes:

      1. Architecture description clarifies 2 of the components and includes 
text explaining the components.

      2. Drop 'version' tag -- versions don't get used

      3. Enhanced description of 'claims' tag

      4. Added optional 'id' tag, for finer-grained assessment identifier

      5. Reworked the section on Requirements for Tailoring the Signing Service, 
to use the signing template. This included adding "Required Fields" and 
"Required Algorithms" components.

      6. Tweaked the DKIM exemplar appendix.

d/

-------- Original Message --------
Subject: New Version Notification for draft-crocker-doseta-base-03.txt
Date: Mon, 11 Jul 2011 16:21:48 -0700
From: internet-drafts at ietf.org
To: dcrocker at bbiw.net
CC: dcrocker at bbiw.net, msk at cloudmark.com

A new version of I-D, draft-crocker-doseta-base-03.txt has been successfully 
submitted by D. Crocker and posted to the IETF repository.

Filename:	 draft-crocker-doseta-base
Revision:	 03
Title:		 DomainKeys Security Tagging (DOSETA)
Creation date:	 2011-07-12
WG ID:		 Individual Submission
Number of pages: 62

Abstract:
    DomainKeys Security Tagging (DOSETA) is a component mechanism that
    enables easy development of security-related services, such as for
    authentication or encryption.  It uses self-certifying keys based on
    domain names.  The domain name owner can be any actor involved in the
    handling of the data, such as the author's organization, a server
    operator or one of their agents.  The DOSETA Library provides a
    collection of common capabilities, including canonicalization,
    parameter tagging and key retrieval.  The DOSETA Signing Template
    creates common framework for a signature of data that are in a
    "header/content" form.  Defining the meaning of a signature is the
    responsibility of the service that incorporates DOSETA.  Data
    security is enforced through the use of cryptographic algorithms.




The IETF Secretariat


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


More information about the doseta-discuss mailing list