< draft-ietf-pkix-ac509prof-07.txt		draft-ietf-pkix-ac509prof-08.txt >
	PKIX Working Group S. Farrell		PKIX Working Group S. Farrell
	INTERNET-DRAFT Baltimore Technologies		INTERNET-DRAFT Baltimore Technologies
	Expires in six months R. Housley		Expires in six months R. Housley
	SPYRUS		RSA Laboratories
	1st June 2001		4 June 2001
	An Internet Attribute Certificate		An Internet Attribute Certificate
	Profile for Authorization		Profile for Authorization
	<draft-ietf-pkix-ac509prof-07.txt>		<draft-ietf-pkix-ac509prof-08.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of [RFC2026].		all provisions of Section 10 of [RFC2026].
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts. Internet-Drafts are draft documents valid for a maximum of		Drafts. Internet-Drafts are draft documents valid for a maximum of
	skipping to change at page 30, line 34 ¶		skipping to change at page 30, line 34 ¶
	There is often a requirement to map between the authentication		There is often a requirement to map between the authentication
	supplied by a particular security protocol (e.g. TLS, S/MIME) and		supplied by a particular security protocol (e.g. TLS, S/MIME) and
	the AC holder's identity. If the authentication uses PKCs, then this		the AC holder's identity. If the authentication uses PKCs, then this
	mapping is straightforward. However, it is envisaged that ACs will		mapping is straightforward. However, it is envisaged that ACs will
	also be used in environments where the holder may be authenticated		also be used in environments where the holder may be authenticated
	using other means. Implementers SHOULD be very careful in mapping		using other means. Implementers SHOULD be very careful in mapping
	the authenticated identity to the AC holder.		the authenticated identity to the AC holder.
	9. IANA Considerations		9. IANA Considerations
	The OIDs used in this document have been delegated by the IANA and		Attributes and attribute certificate extensions are identified by
	no further action by the IANA is necessary for this document or any		object identifiers (OIDs). Many of the OIDs used in this
			document are copied from X.509 [X.509-2000]. Other OIDs
			were assigned from an arc delegated by the IANA. No further
			action by the IANA is necessary for this document or any
	anticipated updates.		anticipated updates.
	10. References		10. References
	[CMC] Myers, M., et al. "Certificate Management Messages over		[CMC] Myers, M., et al. "Certificate Management Messages over
	CMS", RFC2797.		CMS", RFC2797.
	[CMP] Adams, C., Farrell, S., "Internet X.509 Public Key		[CMP] Adams, C., Farrell, S., "Internet X.509 Public Key
	Infrastructure - Certificate Management Protocols",		Infrastructure - Certificate Management Protocols",
	RFC2510.		RFC2510.
	[CMS] Housley, R., "Cryptographic Message Syntax", RFC 2630.		[CMS] Housley, R., "Cryptographic Message Syntax", RFC 2630.
	skipping to change at page 38, line 13 ¶		skipping to change at page 38, line 13 ¶
	END		END
	Appendix C: Change History		Appendix C: Change History
	<<This Appendix to be deleted before RFC>>		<<This Appendix to be deleted before RFC>>
	This appendix lists major changes since the previous revision.		This appendix lists major changes since the previous revision.
	Major changes since last revision:		Major changes since last revision:
			Changes from -07 to -08:
			1. Fixed Title page.
			2. Updated IANA Considerations.
	Changes from -06 to -07:		Changes from -06 to -07:
	1. Added IANA considerations section		1. Added IANA considerations section
	2. Changed DEFAULT version to v2		2. Changed DEFAULT version to v2
	3. Further deprecated v1 syntax since X.509 did		3. Further deprecated v1 syntax since X.509 did
	4. Fixed ASN.1 tagging nits		4. Fixed ASN.1 tagging nits
	Changes from -05 to -06:		Changes from -05 to -06:
	5. Added new item 1 to validation rules in section 5.		5. Added new item 1 to validation rules in section 5.
End of changes. 4 change blocks.
	5 lines changed or deleted		13 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/