< draft-fajardo-dime-base-test-suite-00.txt		draft-fajardo-dime-base-test-suite-01.txt >
	DIME Working Group V. Fajardo		DIME Working Group V. Fajardo
	Internet-Draft TARI		Internet-Draft TARI
	Expires: October 30, 2007 A. McNamee		Expires: January 2, 2008 A. McNamee
	Openet-Telecom		Openet-Telecom
	H. Tschofenig		H. Tschofenig
	NokiaSiemens		Nokia Siemens Networks
	J. Bournelle		J. Bournelle
	GET/INT		France Telecom R&D
	April 28, 2007		July 1, 2007
	Diameter Base Protocol Interoperability Test Suite		Diameter Base Protocol Interoperability Test Suite
	draft-fajardo-dime-base-test-suite-00		draft-fajardo-dime-base-test-suite-01.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	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
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on October 30, 2007.		This Internet-Draft will expire on January 2, 2008.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This document describes a collection of test cases to be used for		This document describes a collection of test cases to be used for
	Diameter base protocol interoperability testing.		Diameter base protocol interoperability testing.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Diameter Base Protocol Test Suite . . . . . . . . . . . . . . 5		3. Diameter Base Protocol Test Suite . . . . . . . . . . . . . . 3
	3.1. Required . . . . . . . . . . . . . . . . . . . . . . . . . 5		3.1. Required . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3.1.1. Connectivity and Peering . . . . . . . . . . . . . . . 5		3.1.1. Connectivity and Peering . . . . . . . . . . . . . . . 3
	3.1.2. Routing . . . . . . . . . . . . . . . . . . . . . . . 9		3.1.2. Routing . . . . . . . . . . . . . . . . . . . . . . . 7
	3.1.3. Relay Agent . . . . . . . . . . . . . . . . . . . . . 11		3.1.3. Relay Agent . . . . . . . . . . . . . . . . . . . . . 9
	3.1.4. Redirection Agent . . . . . . . . . . . . . . . . . . 12		3.1.4. Redirection Agent . . . . . . . . . . . . . . . . . . 10
	3.2. Optional . . . . . . . . . . . . . . . . . . . . . . . . . 12		3.2. Optional . . . . . . . . . . . . . . . . . . . . . . . . . 10
	3.2.1. General Statemachine . . . . . . . . . . . . . . . . . 12		3.2.1. General Statemachine . . . . . . . . . . . . . . . . . 10
	3.2.2. Dynamic Peer Discovery . . . . . . . . . . . . . . . . 12		3.2.2. Dynamic Peer Discovery . . . . . . . . . . . . . . . . 10
	4. Diameter Base Protocol Application Support . . . . . . . . . . 14		4. Diameter Base Protocol Application Support . . . . . . . . . . 11
	4.1. Authentication and/or Authorization . . . . . . . . . . . 14		4.1. Authentication and/or Authorization . . . . . . . . . . . 11
	4.1.1. Stateful Session . . . . . . . . . . . . . . . . . . . 14		4.1.1. Stateful Session . . . . . . . . . . . . . . . . . . . 11
	4.1.2. Stateless Session . . . . . . . . . . . . . . . . . . 15		4.1.2. Stateless Session . . . . . . . . . . . . . . . . . . 12
	4.2. Accounting . . . . . . . . . . . . . . . . . . . . . . . . 15		4.2. Accounting . . . . . . . . . . . . . . . . . . . . . . . . 12
	4.2.1. Client Session . . . . . . . . . . . . . . . . . . . . 15		4.2.1. Client Session . . . . . . . . . . . . . . . . . . . . 12
	4.2.2. Server Session . . . . . . . . . . . . . . . . . . . . 16		4.2.2. Server Session . . . . . . . . . . . . . . . . . . . . 13
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 17		5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
	7. Normative References . . . . . . . . . . . . . . . . . . . . . 19		7. Normative References . . . . . . . . . . . . . . . . . . . . . 14
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
	Intellectual Property and Copyright Statements . . . . . . . . . . 21		Intellectual Property and Copyright Statements . . . . . . . . . . 16
	1. Introduction		1. Introduction
	The document is meant to aid in the identifying the functional test		The document is meant to aid in the identifying the functional test
	cases of a Diameter implementation. The Diameter interoperability		cases of a Diameter implementation. The Diameter interoperability
	test suites are categorized by required and optional functionality.		test suites are categorized by required and optional functionality.
	The required functionality is the baseline capability that an		The required functionality is the baseline capability that an
	implementation must support to allow basic interoperability for that		implementation must support to allow basic interoperability for that
	category. Optional functionality covers features that not all		category. Optional functionality covers features that not all
	implementations support or may wish to test. This document also		implementations support or may wish to test. This document also
	skipping to change at page 4, line 11 ¶		skipping to change at page 3, line 28 ¶
	test cases designed for interoperability. Test plans may be included		test cases designed for interoperability. Test plans may be included
	in future revisions of this work or maybe provided in some other		in future revisions of this work or maybe provided in some other
	document.		document.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	Within this document the terms defined in [RFC2119] refers to the		Within this document the terms defined in [RFC2119] refer to the
	functionality that have to be provided by an implementation for the		functionality that has to be provided by an implementation for the
	usage within this interoperability test event.		usage within this interoperability test document.
	3. Diameter Base Protocol Test Suite		3. Diameter Base Protocol Test Suite
	All implementation must conform to [RFC3588].		All implementation must conform to [RFC3588].
	3.1. Required		3.1. Required
	3.1.1. Connectivity and Peering		3.1.1. Connectivity and Peering
	Implementations must conform to Section 5.6 of [RFC3588]. Typical		Implementations must conform to Section 5.6 of [RFC3588]. Typical
	skipping to change at page 20, line 24 ¶		skipping to change at page 15, line 4 ¶
	Email: vfajardo@tari.toshiba.com		Email: vfajardo@tari.toshiba.com
	Alan McNamee		Alan McNamee
	Openet Telecom Inc		Openet Telecom Inc
	6 Beckett Way, Park West Business Park		6 Beckett Way, Park West Business Park
	Clondalkin, Dublin 12		Clondalkin, Dublin 12
	Ireland		Ireland
	Phone: +353 1 620 4600		Phone: +353 1 620 4600
	Email: alan.mcnamee@openet-telecom.com		Email: alan.mcnamee@openet-telecom.com
	Hannes Tschofenig		Hannes Tschofenig
	Nokia Siemens Networks		Nokia Siemens Networks
			Otto-Hahn-Ring 6
			Munich, Bavaria 81739
			Germany
	Phone:		Phone: +49 89 636 40390
	Email: Hannes.Tschofenig@nsn.com		Email: Hannes.Tschofenig@nsn.com
			URI: http://www.tschofenig.com
	Julien Bournelle		Julien Bournelle
	Institut National des Telecommunications		France Telecom R&D
	9 rue Charles Fourier		38-4O rue du general Leclerc
	Evry cedex, 91011		Issy-Les-Moulineaux 92794
	France		France
	Phone: +33 1 60 76 44 79		Email: julien.bournelle@orange-ftgroup.com
	Email: julien.bournelle@int-evry.fr
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
End of changes. 13 change blocks.
	38 lines changed or deleted		40 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/