SPKM3 Issues
From Linux NFS
meridia wwe ringtones phentermine online cheap xanax cheap hydrocodone cheap zanaflex free ringtones buy didrex real ringtones buy fioricet buy diazepam cheap rivotril ativan online sonyericsson ringtones free sagem ringtones verizon ringtones free sharp ringtones cheap ortho wellbutrin online online valium cheap nexium tracfone ringtones free sony ericsson ringtones cool ringtones zoloft motorola ringtones qwest ringtones free samsung ringtones free nextel ringtones celexa online free ericsson ringtones free midi ringtones cheap tenuate cheap levitra adipex online punk ringtones propecia online cheap albuterol cheap alprazolam buy viagra order tramadol free sony ringtones ambien online funny ringtones cheap hgh free polyphonic ringtones cheap cialis nokia ringtones cheap flexeril norco online cheap ultracet carisoprodol online kyocera ringtones cheap clonazepam cheap pharmacy online cyclobenzaprine online cheap ultram cheap lisinopril xenical online zyban online mono ringtones buy lorazepam sprint ringtones lipitor online prozac online free music ringtones hoodia online online vigrx cheap diethylpropion cheap lortab vicodin online free mtv ringtones free alltel ringtones soma online free jazz ringtones sildenafil online paxil online mp3 ringtones cheap clomid free cingular ringtones =Names in SPKM3=
One of the main issues SPKM3 draft needs to address is naming. X500 distinguished name has no predefined canonical form. rfc2253 defines a string representation of an X500 distinguished name but it is not in a canonical form. it imposes no ordering of multi-valued RDNs. rfc2253 does not take care of white spaces. in the SPKM3 draft, we take care of such issues. however, it is still not possible to have printable canonical names. some implementation may lack an OID-to-string translation for an attribute present in an X500 distinguished name. in such case, rfc2253 proposes to use the hex value of the OID (for more details see rfc2253). however, der-encoded rfc2253 gets us closer to a canonical binary representation of an X500 distinguished name.
-- issue: case sensitivity. each RDN's AttributeValueAssertion (AVA) can define its own matching rules. for instance, it can state that values of this attribute are case insensitive. can we just declare that values are always case insensitive.
rfc2743 defines three name classes: an internal name (special case being a mechanism name), contiguous ("flat") name, and an exported name (canonicalized name). for spkm3, contiguous name is an rfc2253 string representation of the DN order
