Basically, yeah, although it may be handy to incorporate some parts of CMS by reference (semantics/definitions of certain fields, say).
--Richard On Jul 25, 2011, at 1:28 PM, Eric Rescorla wrote: > That works for me. Certainly when I talk about basing something on > CMS, what I mean > is that I'm imitating CMS, not that there is a normative dependency. > > -Ekr > > > On Mon, Jul 25, 2011 at 1:18 PM, Matt Miller <[email protected]> wrote: >> >> On Jul 25, 2011, at 13:16, Leif Johansson wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On 07/25/2011 06:59 PM, Paul C. Bryan wrote: >>>> I now find myself hoping this is not the beginning someone making a case >>>> for ASN.1 encoding in WOES. >>>> >>>> For my edification, can someone comment on how CMS would likely be >>>> referenced in WOES? Would it likely be a normative reference (i.e. key >>>> transport/wrapping, as it is in xmlenc-core), or otherwise would it >>>> probably be just informational? >>> >>> We seem to be bike-shedding on the words "based on" in the charter. >>> Perhaps it helps if we say something to the effect that WOES draws >>> upon experience from CMS and XML-dsig/enc and leave it at that. >>> >> >> +1 >> >> >> - m&m >> >> Matt Miller - <[email protected]> >> Collaboration Software Group - Cisco Systems, Inc. >> >> >> >> >> _______________________________________________ >> woes mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/woes >> >> > _______________________________________________ > woes mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/woes _______________________________________________ woes mailing list [email protected] https://www.ietf.org/mailman/listinfo/woes
