Re: Question about RFC 3125

It's defined as OID in the referenced document ETSI TS101733
https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.02.01_60/ts_101733v020201p.pdf

It's also defined in the new version that obsoletes 101733 (ETSI EN 319 122-1)
https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.01.01_60/en_31912201v010101p.pdf


Stefan Santesson 

On 2019-11-12, 17:03, "pkix on behalf of Sean Turner" <[email protected] on behalf of [email protected]> wrote:

    I mean it has to be an OID - right?
    
    spt
    
    > On Nov 12, 2019, at 10:29, Russ Housley <[email protected]> wrote:
    > 
    > Section 3.4 of RFC 3125 talks about Commitment Rules, and it specifies the following structure:
    > 
    >   CommitmentType ::= SEQUENCE {
    >        identifier                      CommitmentTypeIdentifier,
    >        fieldOfApplication      [0] FieldOfApplication OPTIONAL,
    >        semantics               [1] DirectoryString OPTIONAL }
    > 
    > However, CommitmentTypeIdentifier is never defined.  Is it an object identifier?
    > 
    > Can anyone point to a public signature policy that uses the SignaturePolicy defined in RFC 3125?
    > 
    > Russ
    > 
    > _______________________________________________
    > pkix mailing list
    > [email protected]
    > https://www.ietf.org/mailman/listinfo/pkix
    
    _______________________________________________
    pkix mailing list
    [email protected]
    https://www.ietf.org/mailman/listinfo/pkix
    


_______________________________________________
pkix mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pkix