The following entity definitions are suggested by the X-ASVP
technical working group for readers of X-ASVP meta-documents.
Defined by Level 1 extension "ASVP-WEB"
to contain a "sequence_number".
SHOULD contain child entity
URI of public keys to use with BATV
(Bounce Address Tag Validation). Used to redirect the URI search
for entities away from the X-ASVP standard search path.
Key 1 for use with BATV tag "spubasvp"
val Key k ( k = 1DIGIT )
val = 40-1024*( DIGIT / ALPHA / "-" / "_" )
val = "THIS" means to use the key found in
entity on this meta-document
val = "CONTINUE" means to locate keys at the URI
found in entity
Contains an owner's desire [YES|NO]
to receive BULK e-mail. May have children nested inside the
BULKMAIL parent to indicate preference for different types
of BULK e-mail, possibly related to legislation or statutes
in different jurisdictions.
Example usage:
YESNO
NO
Currently Defined Children of BULKMAIL:
- Global setting - Sets default, overridden by subsequent children
- Reference to California Business and Professions Code
section 17529, which was pre-empted by the federal CAN-SPAM Act of 2003.
This now only serves as an example of how the BULKMAIL parent allows
reference extensions for multiple jurisdictional legislative use.
- URL - Location of a terms and conditions document
that a sender consents to when sending e-mail to this recipient
- YES setting refers to opted-in mailing lists
A YES setting means that the address owner
agrees to accept BULK e-mail to which they
have subscribed.
- NO means that all subscriptions to this address
should be automatically unsubscribed whether
or not the owner has at some point subscribed.
- Like but applies to mail from commercial
enterprises (vendors) with whom the recipient has an existing
relationship. Default value is YES
May have children entities defined by the vendor domain.
For example: YES
NO
Indicates that recipient chooses to no longer receive commercial
e-mail from the domain "Sacto.com".
- Unsolicited Commercial E-mail. Default is YES. A value of NO
indicates the recipient's desire to be considered as on the
"National Do Not E-mail" Registry defined by the CAN-SPAM Act.
Defined by Level 1 extension
"ASVP-WEB" to contain the owner's desire [YES|NO] to receive
bounce messages. Unlike RFC-2821 bounce messages, these messages
are to be sent to the "x-asvp" account of the owner's ISP/domain
with the intended recipient e-mail address as the first
non-whitespace in the body of the message followed by "/n/n"
(Should first check the meta-document for user x-asvp@domain.tld
shows FRIENDLYBOUNCE entity set to 'YES'.)
URL of any website the owner wishes
Any block of HTML the meta-document owner wishes to be
visible when the meta-document is rendered in a web browser.
May contain the meta-document owner's
public key if the owner supports an asymmetric encryption protocol
Defined by Level 1 extension "ASVP-WEB"
to contain a reference when reserved word REFERENCE is found
in the entitity. (Allows extension to external
methods.)
SHOULD have at least one nested element.
Used to indicate the owners desire to end the X-ASVP URL lookup
path relative to the entity listed. Default value is CONTINUE
Example usage: STOP
STOP
Value STOP can be overridden with a CONTINUE value
for listed entities.
Example usage: STOP
CONTINUE
Contains an encrypted
package that contains syntax for verification
checks of an "ASVP-WEB" token. This may be used by
some ISP's to allow users to update their token verifier
software (e.g. spam assassin) with instructions of how they want
their ASVP-WEB token interpretted.
(i.e., which part of the "sequence_number" is the token,
and what algorithm should the verifier program use to test it).
Note: This package would contain instructions in the syntax
defined by the specific verifier software in use, and be
encrypted with the public key assigned to that verifier software.