On 25/07/11 19:37, Leif Johansson wrote: > On 07/25/2011 08:19 PM, Dave CROCKER wrote: > >> On 7/25/2011 1:16 PM, 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. There is considerably more than a bikeshedding difference between > >> a) normative dependence on a protocol, where the new exercise is >> merely a syntactic re-coding" > >> vs, for example > >> b) "take the ideas from the existing work and use them as a basis for >> writing a new protocol." > >> 2. There is a significant constituency in the current topic that are >> using language that sounds very much like option a) above. > > The '+1's today seem to indicate there is significant support for (2) > but I'm not so sure the difference is all that big. > > I propose that the asn.1->json technology change is big enough (if you > take things like tooling, development models etc into account) so as > to make a literal 1-1 translation unlikely. > > WOES will (imho) have to make intelligent choices about what to keep > from cms and what it doesn't need. That to me sounds more like "drawing > experience from" rather than "basing on".
FWIW, my understanding of "basing on" matches Leif's above. The idea with "basing on" CMS as I understand it is to avoid starting over with analysis of the basic concepts and features (cutting things out is fine) and was not to say "use ASN.1 encoding". Maybe "basing on" wasn't a good term. Whatever. S. > > Cheers Leif > > _______________________________________________ woes mailing list [email protected] https://www.ietf.org/mailman/listinfo/woes _______________________________________________ woes mailing list [email protected] https://www.ietf.org/mailman/listinfo/woes
