IETF OSI-DS Working Group				Chris Weider
INTERNET--DRAFT						Mark Knopper
							Merit Network
							June 1991

	Schema for NIC Profile information in X.500

Status of this memo:

The authors wish to put put up a readily accessible, distributed Directory
of Network Information Centers, or NICs.  This paper discusses the schema
used to hold the NIC Profiles, as well as the DIT structure necessary for
this information.

This draft document will be submitted to the RFC as a protocol specification.
Distribution of this memo is unlimited.  Please send comments to the
authors.


INTERNET--DRAFT		NIC Profile Schema		June 1991

SECTION 1: PRELIMINARIES

1.1 Introduction

The authors of this document, in conjuction with the chairs of the IETF
Network Information Services Infrastructure (NISI) group, would like
to implement a Directory of Network Information Centers, or NICs. 
This will enable NICs to find each other easily, will allow users with access
to a DSA to find out where NICs are, and will in general facilitate the 
distribution of information about the Internet and some of its infrastructure.

This RFC proposes a set of standard schema for this information.

1.2 Information to be incorporated

The profile for each NIC contains the following information:  the name of
the NIC, the name of the parent organization, the e-mail address of the NIC,
the postal address of the NIC, the hours of operation, a contact person,
services offered, publications offered, and the networks which the NIC serves.

SECTION 2: NEW ATTRIBUTES AND OBJECT CLASSES

2.1 New attributes

As many of the attributes required here are already defined, let's just 
list the new attributes:

	parentOrganizationName: Name of the parent organization;
	servicesOffered:  services offered by a particular NIC;
	publicationsOffered: publications offered by a particular NIC;
	associatedNetworks: a network associated with a perticular NIC.

The ASN.1 definitions follow.

_____________________________________________________________________________

parentOrganizationName ATTRIBUTE
	WITH ATTRIBUTE SYNTAX
	caseIgnoreStringSyntax
	(SIZE (1 .. ub-parentorg))

ub-parentorg INTEGER ::= 128

servicesOffered ATTRIBUTE
	WITH ATTRIBUTE SYNTAX
	caseIgnoreStringSyntax
	(SIZE (1 .. ub-servicesoff))

ub-servicesoff INTEGER ::= 128

publicationsOffered ATTRIBUTE
	WITH ATTRIBUTE SYNTAX
	caseIgnoreStringSyntax
	(SIZE (1 .. ub-puboffered))

ub-puboffered INTEGER ::= 128


INTERNET--DRAFT		NIC Profile Schema		June 1991

associatedNetworks ATTRIBUTE
	WITH ATTRIBUTE SYNTAX
	caseIgnoreStringSyntax
	(SIZE (1 .. ub-assocnets))

ub-assocnets INTEGER ::= 64

		ASN.1 definitions for new attributes
_____________________________________________________________________________


2.2 New object class.

The new object class associated with this information is detailed in ASN.1
below.

____________________________________________________________________________

nicProfile OBJECT-CLASS
	SUBCLASS OF pilotObject
	MUST CONTAIN { commonName }
	MAY CONTAIN { parentOrganizationName, rfc822Mailbox, postalAddress,
	  roomNumber, streetAddress, postOfficeBox, stateOrProvinceName,
	  telephoneNumber, facsimileTelephoneNumber, hoursOfService,
	  contactName, servicesOffered, publicationsOffered,
	  associatedNetworks }

		ASN.1 definition for new object class

__________________________________________________________________________

SECTION 3: DIT STRUCTURE

3.1 DIT structure changes

This information will reside in a subtree of the o=Internet branch, in
the ou=NIC Profiles subtree.  A sample RDN for an entry would be
@o=Internet@ou=NIC Profiles@cn=NSF Network Service Center.

SECTION 4: AUTHOR INFORMATION

4.1 Author's addresses

	Chris Weider, clw@merit.edu
	Mark Knopper, mak@merit.edu
	1075 Beal Avenue
	Ann Arbor, MI 48109