< draft-ietf-pkix-warranty-extn-03.txt		draft-ietf-pkix-warranty-extn-04.txt >
	Internet Engineering Task Force D. Linsenbardt SPYRUS		Internet Engineering Task Force D. Linsenbardt SPYRUS
	Internet-Draft S. Pontius SPYRUS		Internet-Draft S. Pontius SPYRUS
	June 2003 A. Sturgeon SPYRUS		October 2003 A. Sturgeon SPYRUS
	Expires in December 2003		Expires in April 2004
	Internet X.509 Public Key Infrastructure		Internet X.509 Public Key Infrastructure
	Warranty Certificate Extension		Warranty Certificate Extension
	<draft-ietf-pkix-warranty-extn-03.txt>		<draft-ietf-pkix-warranty-extn-04.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with all		This document is an Internet-Draft and is in full conformance with all
	provisions of Section 10 of RFC2026.		provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering Task		Internet-Drafts are working documents of the Internet Engineering Task
	Force (IETF), its areas, and its working groups. Note that other		Force (IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-Drafts.		groups may also distribute working documents as Internet-Drafts.
	skipping to change at page 3, line 35 ¶		skipping to change at page 3, line 41 ¶
	about coverage beyond the scope of the base warranty. Like the base		about coverage beyond the scope of the base warranty. Like the base
	warranty information, the extended warranty information includes the		warranty information, the extended warranty information includes the
	period during which the warranty applies, a warranty value, and a		period during which the warranty applies, a warranty value, and a
	warranty type.		warranty type.
	When present, the terms and conditions pointer provides a reference to		When present, the terms and conditions pointer provides a reference to
	a document containing the terms and conditions associated with the		a document containing the terms and conditions associated with the
	warranty. The document may be a Certificate Policy that contains this		warranty. The document may be a Certificate Policy that contains this
	information, or it may be a document specifically about the warranty.		information, or it may be a document specifically about the warranty.
	It may also be a Relying Party Agreement. The pointer is always a		It may also be a Relying Party Agreement. The pointer is always a
	uniform resource locator (URL). The URL MUST be a non-relative URL,		uniform resource locator (URL). The URL MUST be a non-relative URL
	and it MUST follow the URL syntax and encoding rules specified in		using the http scheme. The URL MUST follow the URL syntax and encoding
	RFC 1738 [URL].		rules specified in RFC 2396 [URI].
	2.1. Warranty Extension Syntax		2.1. Warranty Extension Syntax
	The syntax for the warranty extension is:		The syntax for the warranty extension is:
	Warranty ::= CHOICE {		Warranty ::= CHOICE {
	none NULL, -- No warranty provided		none NULL, -- No warranty provided
	wData WarrantyData } -- Explicit warranty		wData WarrantyData } -- Explicit warranty
	WarrantyData ::= SEQUENCE {		WarrantyData ::= SEQUENCE {
	skipping to change at page 4, line 23 ¶		skipping to change at page 4, line 28 ¶
	CurrencyAmount ::= SEQUENCE {		CurrencyAmount ::= SEQUENCE {
	currency INTEGER (1..999),		currency INTEGER (1..999),
	amount INTEGER (0..MAX),		amount INTEGER (0..MAX),
	amtExp10 INTEGER (0..MAX) }		amtExp10 INTEGER (0..MAX) }
	WarrantyType ::= INTEGER {		WarrantyType ::= INTEGER {
	aggregated (0),		aggregated (0),
	perTransaction (1) }		perTransaction (1) }
	TermsAndConditionsURL ::= IA5String		TermsAndConditionsURL ::= IA5String -- MUST use http scheme
	2.2. Warranty Extension Semantics		2.2. Warranty Extension Semantics
	Warranty is a CHOICE; it is represented either by NULL or		Warranty is a CHOICE; it is represented either by NULL or
	WarrantyData. If the CA selects NULL, then the CA is explicitly		WarrantyData. If the CA selects NULL, then the CA is explicitly
	stating that no warranty is provided. If the CA selects WarrantyData,		stating that no warranty is provided. If the CA selects WarrantyData,
	then the CA is explicitly stating that a warranty is provided, and the		then the CA is explicitly stating that a warranty is provided, and the
	fields within the WarrantyData type MUST provide details about the		fields within the WarrantyData type MUST provide details about the
	warranty that is provided.		warranty that is provided.
	WarrantyData MUST contain information about the base warranty.		WarrantyData MUST contain information about the base warranty.
	WarrantyData MAY contain information about an extended warranty. Both		WarrantyData MAY contain information about an extended warranty. Both
	base warranty and extended warranty information is provided using the		base warranty and extended warranty information is provided using the
	WarrantyInfo type. WarrantyData MAY contain a URL that points to the		WarrantyInfo type. WarrantyData MAY contain a URL that points to the
	terms and conditions of the warranty. The URL is provided using the		terms and conditions of the warranty. The URL is provided using the
	TermsAndConditionsURL type, which is an IA5 string.		TermsAndConditionsURL type, which is an IA5 string. The IA5String MUST
			contain a URI [RFC2396] using the http scheme, such as
			"http://www.example.com/warranty/t_and_c.html".
	WarrantyInfo MUST contain the warranty validity period, the currency		WarrantyInfo MUST contain the warranty validity period, the currency
	amount of the warranty, and the type of warranty. The warranty		amount of the warranty, and the type of warranty. The warranty
	validity period is provided using the WarrantyValidityPeriod type.		validity period is provided using the WarrantyValidityPeriod type.
	The currency amount of the warranty is provided using the		The currency amount of the warranty is provided using the
	CurrencyAmount type. The type of warranty is provided using the		CurrencyAmount type. The type of warranty is provided using the
	WarrantyType type.		WarrantyType type.
	WarrantyValidityPeriod is a CHOICE; it is represented either by NULL		WarrantyValidityPeriod is a CHOICE; it is represented either by NULL
	or ValidityPeriod. If the CA selects NULL, then the validity period		or ValidityPeriod. If the CA selects NULL, then the validity period
	of the warranty MUST be exactly the same as the validity period of the		of the warranty MUST be exactly the same as the validity period of the
	certificate. If the CA selects ValidityPeriod, then the CA is		certificate. If the CA selects ValidityPeriod, then the CA is
	explicitly stating a warranty validity period that is different than		explicitly stating a warranty validity period that is different than
	the validity period of the certificate. If the warranty validity		the validity period of the certificate. If the warranty validity
	period and the certificate validity period are the same, then the CA		period and the certificate validity period are the same, then the CA
	MUST select the NULL choice. The validity periods are expected to be		MUST select the NULL choice. The validity periods are expected to be
	the same in the vast majority of the cases.		the same in the vast majority of the cases. ValidityPeriod is a
			SEQUENCE of two GeneralizedTime values. The first (notBefore)
	ValidityPeriod is a SEQUENCE of two GeneralizedTime values. The first		GeneralizedTime value MUST indicate the date and time that the warranty
	(notBefore) GeneralizedTime value MUST indicate the date and time that		become valid, and the second (notAfter) GeneralizedTime value MUST
	the warranty become valid, and the second (notAfter) GeneralizedTime		indicate the date and time that the warranty expires.
	value MUST indicate the date and time that the warranty expires.
	CurrencyAmount is a SEQUENCE if three integers. Together the integers		CurrencyAmount is a SEQUENCE if three integers. Together the integers
	specify the currency and a monetary value. The first integer		specify the currency and a monetary value. The first integer
	(currency) MUST indicate the currency using one of the currency codes		(currency) MUST indicate the currency using one of the currency codes
	defined in ISO 4217. The second integer (amount) MUST indicate the		defined in ISO 4217. The second integer (amount) MUST indicate the
	value of the warranty. The third integer (amtExp10) MUST indicate the		value of the warranty. The third integer (amtExp10) MUST indicate the
	correct placement of the decimal point in the monetary value, and it		correct placement of the decimal point in the monetary value, and it
	MUST be the minor unit of currency specified in ISO 4217. For example		MUST be the minor unit of currency specified in ISO 4217. For example
	$48,525.50 (in US dollars) is represented as:		$48,525.50 (in US dollars) is represented as:
	currency = 840		currency = 840
	skipping to change at page 5, line 48 ¶		skipping to change at page 6, line 7 ¶
	4. IANA Considerations		4. IANA Considerations
	Certificate extensions and extended key usage values are identified		Certificate extensions and extended key usage values are identified
	by object identifiers (OIDs). The OIDs used in this document are		by object identifiers (OIDs). The OIDs used in this document are
	derived from X.509 [X.509]. No further action by the IANA is		derived from X.509 [X.509]. No further action by the IANA is
	necessary for this document or any anticipated updates.		necessary for this document or any anticipated updates.
	5. Normative References		5. Normative References
	ISO 4217 ISO. Codes for the Representation of Currencies and		ISO 4217 ISO. "Codes for the Representation of Currencies and
	Funds," ISO 4217. 1995.		Funds", ISO 4217. 1995.
	PROFILE Housley, R., Ford, W., Polk, W. and D. Solo, "Internet		PROFILE Housley, R., Ford, W., Polk, W. and D. Solo, "Internet
	X.509 Public Key Infrastructure: Certificate and CRL		X.509 Public Key Infrastructure: Certificate and CRL
	Profile", RFC 3280, May 2002.		Profile", RFC 3280, May 2002.
	URL Berners-Lee, T., Masinter, L., and M. McCahill. "Uniform		URI Berners-Lee, T., Fielding, R., Irving, U.C., and L.
	Resource Locators (URL)", RFC 1738, December 1994.		Masinter. "Uniform Resource Identifiers (URI): Generic
			Syntax", RFC 2396, August 1998.
	X.208-88 CCITT. Recommendation X.208: Specification of Abstract		X.208-88 CCITT. Recommendation X.208: Specification of Abstract
	Syntax Notation One (ASN.1). 1988.		Syntax Notation One (ASN.1). 1988.
	X.209-88 CCITT. Recommendation X.209: Specification of Basic		X.209-88 CCITT. Recommendation X.209: Specification of Basic
	Encoding Rules for Abstract Syntax Notation One (ASN.1).		Encoding Rules for Abstract Syntax Notation One (ASN.1).
	1988.		1988.
	6. Informative References		6. Informative References
	skipping to change at line 401 ¶		skipping to change at line 404 ¶
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT		TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
	NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN		NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
	WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF		WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Acknowledgement		Acknowledgement
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is currently provided by the
	Internet Society.		Internet Society.
	Expires in December 2003		Expires in April 2004
End of changes. 9 change blocks.
	18 lines changed or deleted		20 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/