Issue 4142: Module suggestions (csiv2-ftf) Source: Syracuse University (Dr. Polar Humenn, polar(at)adiron.com) Nature: Uncategorized Issue Severity: Summary: In looking at it, I think CSI would make a good "base" module. Since other modules are only related to CSI, such as CSIIOP and GSSUP, I see no reason why those two modules cannot depend on CSI. Define in CSI: AssociationOptions GSSToken GSS_NT_ExportedName X509CertificateChain X501DistinguishedName As part of another issue, change the use of ScopedName in GSSUP to CSI::GSS_NT_ExportedName. As yet another issue, is to get rid of the ASN.1 dependance on X509CertificateChain and X501DistinguishedName and somehow make it consistent with the PKI spec. Or get rid of them all together, and just use ExportedName format with proper OIDs. Resolution: Same as issue 4141 Revised Text: Same as issue 4141 Actions taken: January 10, 2001: received issue October 3, 2001: closed issue Discussion: End of Annotations:===== X-Authentication-Warning: marcy.adiron.com: polar owned process doing -bs Date: Wed, 10 Jan 2001 10:50:24 -0500 (EST) From: Polar Humenn To: csiv2-ftf@omg.org Subject: Module suggestions In-Reply-To: <3A5C7FA7.ABBCBDE6@east.sun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: >PAe9VlEe96HA!!A6h!! In looking at it, I think CSI would make a good "base" module. Since other modules are only related to CSI, such as CSIIOP and GSSUP, I see no reason why those two modules cannot depend on CSI. Define in CSI: AssociationOptions GSSToken GSS_NT_ExportedName X509CertificateChain X501DistinguishedName As part of another issue, change the use of ScopedName in GSSUP to CSI::GSS_NT_ExportedName. As yet another issue, is to get rid of the ASN.1 dependance on X509CertificateChain and X501DistinguishedName and somehow make it consistent with the PKI spec. Or get rid of them all together, and just use ExportedName format with proper OIDs.