Per discussion at yesterday's IETF PEM WG meeting, I jumped in and drafted what
I believe to be the necessary 1113ID changes to add the Content-Domain: field
as a hook for future MIME integration work. In the interests of conciseness
and convergence, attached are the salient changes relative to my 7 May
draft as previously sent to pem-dev. I'd appreciate any comments on this text
by next Wednesday, 22 July, so as to send the resultant document to
Internet-Drafts next week.
Added to the end of the Executive Summary section:
The current specification's scope is confined to PEM processing
procedures for the RFC-822 textual mail environment. Follow-on work
in integration of PEM capabilities with other messaging environments
(e.g., MIME) is anticipated and will be addressed in separate and/or
successor documents.
All example messages now bear a "Content-Domain: rfc822" header field following
their "Proc-Type:" field. The Content-Domain field is defined (in a section
now numbered 4.6.1.2, bumping numbers of subsequent sections) as follows:
4.6.1.2 Content-Domain Field
The "Content-Domain:" encapsulated header field describes the type of
content which is represented within a PEM message's encapsulated
text. It carries one string argument, values for which are
registered in [ID1115+]. Only one "Content-Domain:" field occurs in
a PEM message; this field is the PEM message's second encapsulated
header field, immediately following the "Proc-Type:" field.
BNF additions are:
<contentdomain> ::= "Content-Domain" ":" <contentdescrip> CRLF
; The following items are defined in RFC [1115+]
[...]
; <contentdescrip>
--jl