I asked people at Microsoft to run a check on this and it appears after quick code check that CAPI supports BMPString for encoding and VisibleString and BMPString for decoding This is somewhat contradictory to Tomas findings. But to the proposal: > > The current document says: > > SHOULD UTF8 > MAY IA5String > MUST NOT VisibleString & BMPString > > The proposal is: > > SHOULD UTF8 > MAY VisibleString > MUST NOT IA5String or BMPString > If the purpose is to align with current deployment, then why not say: SHOULD UTF8 MAY VisibleString or BMPString MUST NOT IA5String /Stefan On 09-11-18 11:45 PM, "Stephen Kent" <kent at bbn.com> wrote: > At 9:21 AM +0100 11/18/09, Tomas Gustavsson wrote: >> I mean MS client software, when displaying certificates in Windows >> XP for example it will only display the user notice if it is a >> BMPString. >> With this in mind I also assume that MS CA issues user notices with >> BMPString although I haven't verified. >> >> Haven't tested on Vista or Win 7 though (I'm a linux fanboy :-)), >> wich was the reason for the question. I can make a test of this >> myself though. >> >> Cheers, >> Tomas > > Thanks for the clarification, and the offer to run tests on Vista and Win 7. > From what you say, it appears that the MS client and CA software were > not compliant with this aspect of 5280, and would not become so under > the propose changes re user notice. > > Steve > _______________________________________________ > pkix mailing list > pkix at ietf.org > https://www.ietf.org/mailman/listinfo/pkix
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.