< draft-ietf-roamops-phonebook-xml-04.txt		draft-ietf-roamops-phonebook-xml-05.txt >
	Network Working Group M. Riegel		Network Working Group M. Riegel
	Internet-Draft Siemens AG		Internet-Draft Siemens AG
	Category: Standards Track G. Zorn		Category: Standards Track G. Zorn
	<draft-ietf-roamops-phonebook-xml-04.txt> Cisco Systems		<draft-ietf-roamops-phonebook-xml-05.txt> Cisco Systems
	August 2000		September 2000
	XML DTD for Roaming Access Phone Book		XML DTD for Roaming Access Phone Book
	1. Status of this Memo		1. 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 other		Task Force (IETF), its areas, and its working groups. Note that other
	skipping to change at page 1, line 31 ¶		skipping to change at page 1, line 31 ¶
	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.
	The distribution of this memo is unlimited. It is filed as		The distribution of this memo is unlimited. It is filed as
	<draft-ietf-roamops-phonebook-xml-04.txt>,		<draft-ietf-roamops-phonebook-xml-05.txt>,
	and expires January 31, 2001.		and expires February 28, 2001.
	Please send comments to the Roaming Operations Working Group mailing		Please send comments to the Roaming Operations Working Group mailing
	list (roamops@tdmx.rutgers.edu) or to the editor of this draft		list (roamops@tdmx.rutgers.edu) or to the editor of this draft
	(maximilian.riegel@icn.siemens.de).		(maximilian.riegel@icn.siemens.de).
	2. Abstract		2. Abstract
	This document defines the syntax as well as the semantics of the		This document defines the syntax as well as the semantics of the
	information to be included in the phone book for roaming		information to be included in the phone book for roaming
	applications. It comprises the information necessary to select the		applications. It comprises the information necessary to select the
	most appropriate ISP and to configure the host to get access to the		most appropriate ISP and to configure the host to get access to the
	skipping to change at page 4, line 7 ¶		skipping to change at page 4, line 7 ¶
	effort required to implement it.		effort required to implement it.
	5. Specification of Requirements		5. Specification of Requirements
	In this document, the key words "MAY", "MUST, "MUST NOT", "optional",		In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
	"recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as		"recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as
	described in [1].		described in [1].
	6. Value type notations for 'stronger' typing		6. Value type notations for 'stronger' typing
	XML currently does not have capabilities for 'strong typing' of the		XML DTDs do not currently have capabilities for 'strong typing' of
	content of elements. The only type definition foreseen in the base		the content of elements. The only type definition foreseen in the
	specification is "#PCDATA", 'parsable character data'. This might be		base specification is "#PCDATA", 'parsable character data'. This
	sufficient and is used throughout this document to define elements		might be sufficient and is used throughout this document to define
	containing information mainly aimed for interpretation by human		elements containing information mainly aimed for interpretation by
	beings.		human beings.
	To enable a more concise description of the content of particular		To enable a more concise description of the content of particular
	elements several value type notations are introduced. This allows for		elements several value type notations are introduced. This allows for
	a more detailed type description of the content of elements in cases		a more detailed type description of the content of elements in cases
	where it seems to be desirable.		where it seems to be desirable.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<!-- Phone book value type notation declarations -->		<!-- Phone book value type notation declarations -->
	<!NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/NOTATION		<!NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/NOTATION
	value Type Fully_qualified_domain_name">		value Type Fully_qualified_domain_name">
	skipping to change at page 28, line 32 ¶		skipping to change at page 28, line 32 ¶
	10. Security Considerations		10. Security Considerations
	The secure distribution and transport of information of a phone book		The secure distribution and transport of information of a phone book
	for roaming applications require a reliable authentication of the		for roaming applications require a reliable authentication of the
	issuer of the information as well as means to preserve the integrity		issuer of the information as well as means to preserve the integrity
	of the provided information.		of the provided information.
	No specific elements for security requirements are provided by the		No specific elements for security requirements are provided by the
	phone book XML DTD itself. It is assumed that security of the roaming		phone book XML DTD itself. It is assumed that security of the roaming
	phone book is provided by means outside of the scope of this		phone book is provided by means outside of the scope of this
	specification, such as the transfer of the phone book through a		specification, such as signing the phone book using pgp.
	secure http or secure socket layer, or encrypted using pgp.
	11. IANA Considerations		11. IANA Considerations
	This specification provides the possibility to define further		This specification provides the possibility to define further
	attribute values for all information elements owning enumerated		attribute values for all information elements owning enumerated
	attribute lists as well as to extend the main structures 'pop',		attribute lists as well as to extend the main structures 'pop',
	'setup', 'support' and 'provider' by additional information elements.		'setup', 'support' and 'provider' by additional information elements.
	Therefore the specification of the roaming phone book can be adopted		Therefore the specification of the roaming phone book can be adopted
	to future requirements without changing this document. Extensions and		to future requirements without changing this document. Extensions and
	refinements to this specification can be achieved by registration of		refinements to this specification can be achieved by registration of
	skipping to change at page 32, line 15 ¶		skipping to change at page 32, line 15 ¶
	Cisco Systems, Inc.		Cisco Systems, Inc.
	500 108th Avenue N.E., Suite 500		500 108th Avenue N.E., Suite 500
	Bellevue, WA 98004		Bellevue, WA 98004
	USA		USA
	Phone: +1 425 438 8218		Phone: +1 425 438 8218
	E-Mail: gwz@cisco.com		E-Mail: gwz@cisco.com
	16. Expiration Date		16. Expiration Date
	This memo is filed as draft-ietf-roamops-phonebook-xml-04.txt and		This memo is filed as draft-ietf-roamops-phonebook-xml-05.txt and
	expires on January 31, 2001.		expires on February 28, 2001.
End of changes. 5 change blocks.
	12 lines changed or deleted		11 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/