[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dss-dev] Data format guessing of data within Base64Data tag
Dear all, > first of all thank you, for providing this short and to the point corner > case, where a MAC address actually only by interpretation looks like > '<hit/>'. > > In any case, for a next revision of the core protocol, an explicit > conformance section will be imperative (as also **now** mandated by the > rules of OASIS) and I will personally ensure, that this point will be > clearly stated inside, when and if a next revision will be made. > > As an implementer, I already stated, that it surprises me, that an > implementation of DSS "sniffes" on base64 input being "labelled" as data > only, but also, that I expect some policies (from the stakeholders) > having shaped that additional behavior, as we do neither prohibit the > above mentioned MAC-address being entered base64 encoded as text inside > <Base64Data> nor the implementation parsing it. > > Rejecting it though looks like a clear sign for specific policy > enforcement that is clearly out of our scope as DSS editors or DSS TC > chairs but may render this implementation useless for many applications > as a signing entity should not spuriously reject signing based on the > content of the document, I think (common sense only). Signing isn't > proof-reading, is it? > > I for one simply did not forsee in the era between 2005 and 2007, that > any implementer might want to do that ;-) > > Thanks again for taking the time to bring this to our attention. Thank you all for your interest and comments regarding this question. If there is something I could help with, don't hesitate to contact me. :-) Kind regards, Daniel M. Lambea
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]