Re: [smime] some s/mime related drafts I've been asked to AD sponsor

What was the criteria for selecting the items in the innermost content
type set included in [1]?  For example, why include TrustAnchorList
content type from 5914 but not the TAMP content types from 5934?

The interop considerations section states ContentInfo is always the
outermost structure.  Should RFC 4073 be updated to reflect this?

On 9/2/13 6:23 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

>S/MIMErs: please take a look at these and let the list know (a) if you
>have any concerns, (b) if you might implement them, or both.
>
>--Paul Hoffman
>
>On Sep 2, 2013, at 2:57 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
>wrote:
>
>> 
>> Folks,
>> 
>> Sean, Russ and Jim have authored three s/mime related drafts [1,2,3]
>> and asked me to sponsor them for publication. I've read them and
>> they seem like reasonable additions to the set of s/mime RFCs to
>> me, but I'd like to check that nobody has any issue with that
>> before starting IETF LC in a week or so.
>> 
>> I'd specifically be interested in hearing from anyone who'd
>> likely implement these. I'll send my own comments (which are
>> minor) during the IETF LC.
>> 
>> Thanks,
>> S.
>> 
>> [1] http://tools.ietf.org/html/draft-turner-application-cms-media-type
>> [2]
>> http://tools.ietf.org/html/draft-housley-ct-keypackage-receipt-n-error
>> [3]
>> 
>>http://tools.ietf.org/html/draft-turner-ct-keypackage-receipt-n-error-alg
>>s
>> 
>> _______________________________________________
>> smime mailing list
>> smime@ietf.org
>> https://www.ietf.org/mailman/listinfo/smime
>> 
>
>_______________________________________________
>smime mailing list
>smime@ietf.org
>https://www.ietf.org/mailman/listinfo/smime