Internet Draft
sri@qsun.att.com Fri, 26 March 1993 09:53 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02246; 26 Mar 93 4:53 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02240; 26 Mar 93 4:53 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa02717; 26 Mar 93 4:53 EST
Received: from haig.cs.ucl.ac.uk by IETF.CNRI.Reston.VA.US id aa01512; 26 Mar 93 2:53 EST
Received: from att-out.att.com by haig.cs.ucl.ac.uk with Internet SMTP id <g.00694-0@haig.cs.ucl.ac.uk>; Fri, 26 Mar 1993 06:42:36 +0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: sri@qsun.att.com
Date: Fri, 26 Mar 1993 01:36:00 -0500
Original-From: qsun!sri (Srinivas R Sataluri +1 908 949 7782)
To: osi-ds@cs.ucl.ac.uk
Cc: markk@internic.net
Subject: Internet Draft
Message-ID: <9303260254.aa01512@IETF.CNRI.Reston.VA.US>
Folks: Enclosed is a draft of our document titled "Representing Registration Information in the X.500 Directory." We appreciate your constructive criticism. With the permission of the Chair, we look forward to a discussion of our proposal at the 10th OSI-DS Working Group meeting on 3/29/93 at Columbus, Ohio. We apologize for this last minute submission. Thanks. mark kosters markk@internic.net sri sataluri sri@qsun.att.com -------- OSI-DS Working Group Mark Kosters INTERNET-DRAFT Network Solutions Srinivas Sataluri AT&T Bell Laboratories March 1993 Representing Registration Information in the X.500 Directory Status of this Memo This draft document is for unlimited distribution for discussion. Please send comments to the authors or to the discussion group "osi-ds@cs.ucl.ac.uk". Abstract This document describes the objects necessary to represent NSFNet registration information in the X.500 Directory. The registration information is currently maintained in the WHOIS database by the InterNIC registration services provider. 1. Introduction The WHOIS utility is a lookup facility to find out information about networks, ASNs, domains, DNS servers and Points of Contacts that are registered under the InterNIC registration services provider. The InterNIC registration services provider is responsible for being the world-wide IP and ASN registry, the first and second level domain name system registry, and hosts and Points of Contacts for those particular Internet Elements. Several groups have worked on the problem of representing network information in the X.500 Directory. As part of the DARPA FOX project a schema for representing the WHOIS information in X.500 was undertaken. The list of references indicates the previous work on which this proposal is based. 2. Directory Information Tree Structure The DIT structure used for storing objects defined below will be: @o=Internet@ou=Network Information@ou= Points of Contact IP Networks Autonomous System Numbers Domains Servers Kosters and Sataluri [Page 1] Representing Registration Information in X.500 March 1993 Objects of the class poc will be listed under ou=Points of Contact; objects of the classes ipnetwork and ipblock (recursively) will be listed under ou=IP Networks; objects of the classes asn and asnblock (recursively) will be listed under ou=Autonomous System Numbers; objects of the class domainname (recursively) will be listed under ou=Domains; and objects of the class server will be listed under ou=Servers. 3. Objects 3.1 The NIC Object The NIC Object is a super class object and every object we define for representing registration information is a subclass of the NIC Object. nicObject OBJECT-CLASS SUBCLASS OF quipuObject MUST CONTAIN { commonName } MAY CONTAIN { handle, registrationDate, nicOrgAttributeSet } We include the commonName attribute as a required attribute for every object. The RDN of an object will be encoded and stored in the commonName attribute. The principal reason for doing this is to enable several existing DUAs, designed specifically for searching the Directory for persons to be put to meaningful use. Examples of the commonName attribute values are: cn=192.112.38.0 for an ipnetwork object, cn=192.0.0.0..192.0.255.0 for an ipblock object, cn=1 for an asn object, cn=2..8 for an asnblock object, cn=arpa for a domainname object, cn=NS.NETSOL.COM for a server object, and cn=Mark Kosters (MAK21) for a poc object. At present, every registered entity is assigned an unique identifier. This identifier is stored in the handle attribute. We included the handle attribute in the MAY section to enable other NICs that do not assign unique identifiers to use the schema without changes. However, every entity mastered by the InterNIC DSAs will have the handle attribute populated. The registrationDate attribute stores the date the entity was first registered with the NIC. The latest change time to the data is Kosters and Sataluri [Page 2] Representing Registration Information in X.500 March 1993 recorded in the lastModifiedTime attribute of the quipuObject. Every entity mastered by the InterNIC DSAs will have the registrationDate attribute populated. Every registered entity is assigned to some organization by the NIC. The information about the organization is maintained in the attributes in nicOrgAttributeSet. It should be apparent that the organization information is being duplicated at several places in the DIT. This design decision is based on our desire to discourage the searching of the Network Information branch of the DIT for organizations. To obtain an entry in the X.500 Directory, organizations should join the white pages project and secure a place in the DIT. nicOrgAttributeSet ATTRIBUTE-SET { organizationName, telephoneNumber, facsimileTelephoneNumber, postOfficeBox, streetAddress, postalCode, stateOrProvinceName, countryName, orgInfoSee } If an organization is already participating in the pilot project, the orgInfoSee attribute will contain the DN of its entry in the DIT. On the other hand, if an organization is not a participant in the pilot project, limited information about the organization is stored in the attributes in the above set. We hope to encourage organizations to join the pilot. 3.2 Representing IP Networks The NIC distributes IP addresses to various organizations that request them. In several cases, blocks of IP addresses are given out. The information about the IP addresses will be stored under the ou=IP Networks branch of the DIT using two different kinds of objects. The ipnetwork object stores information about a single IP network address and will be a leaf node. The ipblock object will store information about a block of IP network addresses and should typically be a non- leaf node. We will discuss each of these objects in turn. ipnetwork OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { ipNetNumber } MAY CONTAIN { Kosters and Sataluri [Page 3] Representing Registration Information in X.500 March 1993 ipNetName, providerInfoSee, adminContactInfoSee, techContactInfoSee, inaddrServerInfoSee, domainInfoSee } The ipNetNumber will form the RDN of an ipnetwork object and can only have a single value. Further, the value of this attribute will be duplicated in the commonName field (see nicObject description above). The ipNetName attribute is used to store a network name when available. The providerInfoSee attribute stores the DN of an organization that is the service provider for this network. If the service provider is not participating in the pilot project, this field will be left unassigned. Note that the organizational attributes contain information about the organization to which this IP network address is assigned and not about the service provider. The adminContactInfoSee and the techContactInfoSee are DN attributes that are pointers into the Points of Contact space in the Network Information branch of the DIT. The inaddrServerInfoSee is a DN attribute that is a pointer to a server entity in the Servers space in the Network Information branch of the DIT. Similarly, domainInfoSee is a DN attribute that is a pointer to a domainname entity in the Domains space in the Network Information branch of the DIT. ipblock OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { ipNetLowerBound, ipNetUpperBound } MAY CONTAIN { ipNetName, ipNetNumber, providerInfoSee, adminContactInfoSee, techContactInfoSee, inaddrServerInfoSee, domainInfoSee, delegatedBlock, Kosters and Sataluri [Page 4] Representing Registration Information in X.500 March 1993 masterDSA } The ipblock object will be used to store information about a block of IP network addresses that are either assigned to a single organization or to an other registration authority. If the entity that receives these network addresses chooses not to run an X.500 DSA, the corresponding ipblock entity will be a leaf node in the DIT. We hope that initially, at least the delegated registration authorities will choose to run a DSA to master the information about the IP network addresses assigned to them. In such a case, the corresponding ipblock entity in the DIT will be a non-leaf node and the masterDSA attribute will be set to contain the DN of the DSA mastering the data. The pair of attributes, ipNetLowerBound and ipNetUpperBound together form the RDN of an ipblock entity. The information in these two fields is encoded in the commonName field as shown in an example in the nicObject description above. The ipNetName attribute is used to store a name for this block of addresses, if available. The ipNetNumber attribute will only be used if the entity is a leaf node. The IP network addresses in the ipblock are enumerated using the ipNetNumber attribute, and thus this attribute will have multiple values when used in the ipblock object class context. The reason for including this information is to ensure that a search for a specific IP network address will succeed. o=internet | ou=Network Information | ou=IP Networks | ------------------------------------------------------------------------- | | | | ipNetNumber=w ipNetNumber=x ... (ipNetLowerBound=y, ipNetUpperBound=z) ... | --------------------------------------------------------- | | | ipNetNumber=y1 (ipNetLowerBound=y2, ipNetUpperBound=y3) ... 3.3 Representing Autonomous System Numbers The design philosophy behind the Autonomous System Numbers is identical to the one for ipnetwork and ipblock objects. The definition of the asn and asnblock objects is given in section 4, Schema. Kosters and Sataluri [Page 5] Representing Registration Information in X.500 March 1993 o=internet | ou=Network Information | ou=Autonomous System Numbers | ---------------------------------------------------------------------- | | | | asnNumber=w asnNumber=x ... (asnLowerBound=y, asnUpperBound=z) ... | --------------------------------------------------------- | | | asnNumber=y1 (asnLowerBound=y2, asnUpperBound=y3) ... 3.4 Representing the Domain Name Space The InterNIC registration services provider maintains a registry of the first and second level Domain Name System names. The DNS names registered with the NIC will be stored under the ou=Domains branch of the DIT using the domainname object. domainname OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { domainComponent } MAY CONTAIN { domainName, domainNameServerInfoSee, networkInfoSee, dnsRRecord, adminContactInfoSee, techContactInfoSee, zoneContactInfoSee, masterDSA } The domainComponent attribute will form the RDN of a domainname object and can only have a single value. Further, the value of this attribute will be duplicated in the commonName field (see nicObject description above). The domainName attribute will contain the DNS domain name easily derived from the place of the entity in the DIT. For instance, domainName=att.com for the entity, @o=internet@ou=Network Information@ou=Domains@domainComponent=com@ domainComponent=att. The dnsRRecord attribute describes the Resource Records (RR) within DNS for that particular domain. The attribute stores an ordered list Kosters and Sataluri [Page 6] Representing Registration Information in X.500 March 1993 of Resource Records. Ordering is important here since if the name field is blank for a given RR, it defaults to the name of the previous RR. If the second level of the domain name, if an organization chooses to run a X.500 DSA and masters lower levels of domain components, our second level entry will be a non-leaf node with the masterDSA attribute set to the DN of the appropriate DSA. If an organization does not choose to run a DSA and make their data available, our entry will be a leaf node. o=internet | ou=Network Information | ou=Domains | ---------------------------------------------------------------------- | | | | domainComponent=ARPA domainComponent=edu domainComponent=es ... | ------------------------------------------------- | | | domainComponent=rutgers domainComponent=vt ... 3.5 Representing Servers 3.6 Representing Points of Contact 4 Schema We present the schema for the various objects and attributes used to represent the registration information using the proformas in the RFC1274. However, we cooked up a proforma for the definition of an AttributeSet. Attribute Set: NIC Organizational Attribute Set Description: The NIC Organizational Attribute Set is a minimal set of attributes that identify an organization. The orgInfoSee attribute points to the organization's entry in the DIT, if any. ASN1ASMacro: nicOrgAttributeSet ATTRIBUTE-SET { organizationName, telephoneNumber, Kosters and Sataluri [Page 7] Representing Registration Information in X.500 March 1993 facsimileTelephoneNumber, postOfficeBox, streetAddress, postalCode, stateOrProvinceName, countryName, orgInfoSee } Object Class: NIC Object Description: The NIC Object is a superclass object that has attributes used to represent the registration data. Every object defined below is a subclass of the NIC Object. ASN1OCMacro: nicObject OBJECT-CLASS SUBCLASS OF quipuObject MUST CONTAIN { commonName } MAY CONTAIN { handle, registrationDate, nicOrgAttributeSet } Object Class: Point of Contact Description: The Point of Contact object represents information regarding individuals registered with the NIC as points of contact for various Internet Elements. ASN1OCMacro: poc OBJECT-CLASS SUBCLASS OF nicObject, person MUST CONTAIN { } MAY CONTAIN { organizationalUnitName, title, rfc822Mailbox, networkInfoSee, asnInfoSee, domainInfoSee, domainNameServerInfoSee, inaddrServerInfoSee } Object Class: IP Network Kosters and Sataluri [Page 8] Representing Registration Information in X.500 March 1993 Description: The IP Network object contains information regarding IP Networks registered with the NIC. ASN1OCMacro: ipnetwork OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { ipNetNumber } MAY CONTAIN { ipNetName, providerInfoSee, adminContactInfoSee, techContactInfoSee, inaddrServerInfoSee, domainInfoSee } Object Class: IP Network Block Description: The IP Network Block object contains information regarding IP Network blocks handed out by the NIC. ASN1OCMacro: ipblock OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { ipNetLowerBound, ipNetUpperBound } MAY CONTAIN { ipNetName, ipNetNumber, providerInfoSee, adminContactInfoSee, techContactInfoSee, inaddrServerInfoSee, domainInfoSee, delegatedBlock, masterDSA } Object Class: Autonomous System Number Description: The Autonomous System Number object contains information regarding Autonomous Systems registered with the NIC. ASN1OCMacro: asn OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { Kosters and Sataluri [Page 9] Representing Registration Information in X.500 March 1993 asnNumber } MAY CONTAIN { asnName, adminContactInfoSee, techContactInfoSee } Object Class: Blocks of Autonomous System Numbers Description: The Blocks of Autonomous System Numbers object contains information regarding Autonomous System Number blocks registered with the NIC. ASN1OCMacro: asnblock OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { asnLowerBound, asnUpperBound } MAY CONTAIN { asnName, asnNumber, adminContactInfoSee, techContactInfoSee, delegatedBlock, masterDSA } Object Class: Domain Name Description: The Domain Name object contains information regarding Domains (i.e., entities of the Domain Name System) registered with the NIC. The NIC only maintains the first and second level domain name system names. ASN1OCMacro: domainname OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { domainComponent } MAY CONTAIN { domainName, domainNameServerInfoSee, networkInfoSee, dnsRRecord, adminContactInfoSee, techContactInfoSee, zoneContactInfoSee, Kosters and Sataluri [Page 10] Representing Registration Information in X.500 March 1993 masterDSA } Object Class: Server Description: The Server object contains information regarding registered with the NIC as is stored in the WHOIS database. ASN1OCMacro: server OBJECT-CLASS SUBCLASS OF nicObject MUST CONTAIN { hostName } MAY CONTAIN { ipAddress, cpu, operatingSystem, adminContactInfoSee, techContactInfoSee, seeAlso } -------------------------------------------------------------------------- Attribute Type: Registration Date Description: The Registration Date attribute lists the date of first registration of the object. OCMust: OCMay: nicObject ASN1ATMacro: registrationDate ATTRIBUTE WITH ATTRIBUTE SYNTAX uTCTimeSyntax SINGLE VALUE Attribute Type: Administrative Contact Information Description: The administrative contact information attribute specifies the administrator for an entity. OCMust: OCMay: ipnetwork, ipblock, asn, asnblock, domainname Kosters and Sataluri [Page 11] Representing Registration Information in X.500 March 1993 ASN1ATMacro: adminContactInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax Attribute Type: Technical Contact Information Description: The technical contact information attribute specifies the technical contact for an entity. OCMust: OCMay: ipnetwork, ipblock, asn, asnblock, domainname ASN1ATMacro: techContactInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax Attribute Type: Zone Contact Information Description: The zone contact information attribute specifies either the zone contact for a domain or the domain itself. See RFC1032. OCMust: OCMay: domainname ASN1ATMacro: zoneContactInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax Attribute Type: CPU Description: The CPU attribute lists the computer model of a server. OCMust: OCMay: server ASN1ATMacro: cpu ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-cpu)) SINGLE VALUE ub-cpu INTEGER ::= 64 Kosters and Sataluri [Page 12] Representing Registration Information in X.500 March 1993 Attribute Type: Operating System Description: The Operating System attribute lists the operating system name and version being used by a server. OCMust: OCMay: server ASN1ATMacro: operatingSystem ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-operatingsystem)) SINGLE VALUE ub-operatingsystem INTEGER ::= 64 Attribute Type: IP Network Number Description: The IP Network Number attribute lists the IP network address of an IP network. OCMust: ipnetwork OCMay: ipblock ASN1ATMacro: ipNetNumber ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-ipnetworknumber)) ub-ipnetworknumber INTEGER ::= 16 Attribute Type: IP Network Block Lower Bound Description: The IP Network Block Lower Bound attribute lists the beginning IP network number of a block of IP network addresses. OCMust: ipblock OCMay: ASN1ATMacro: ipNetLowerBound ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-ipnetworknumber)) Kosters and Sataluri [Page 13] Representing Registration Information in X.500 March 1993 SINGLE VALUE Attribute Type: IP Network Block Upper Bound Description: The IP Network Block Upper Bound attribute lists the ending IP network number of a block of IP network addresses. OCMust: ipblock OCMay: ASN1ATMacro: ipNetUpperBound ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-ipnetworknumber)) SINGLE VALUE Attribute Type: Autonomous System Number Description: The Autonomous System Number attribute lists the autonomous system number of an autonomous system [reference]. OCMust: asn OCMay: asnblock ASN1ATMacro: asnNumber ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-asnnumber)) ub-asnnumber INTEGER ::= 16 Attribute Type: Autonomous System Number Block Lower Bound Description: The Autonomous System Number Lower Bound attribute lists the beginning ASN number of a block of Autonomous System Numbers. OCMust: asnblock OCMay: ASN1ATMacro: asnLowerBound ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax Kosters and Sataluri [Page 14] Representing Registration Information in X.500 March 1993 (SIZE (1 .. ub-asnnumber)) SINGLE VALUE Attribute Type: Autonomous System Number Block Upper Bound Description: The Autonomous System Number Upper Bound attribute lists the ending ASN number of a block of Autonomous System Numbers. OCMust: asnblock OCMay: ASN1ATMacro: asnUpperBound ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-asnnumber)) SINGLE VALUE Attribute Type: IN-ADDR Server Information Description: The IN-ADDR Server Information attribute identifies a computer running a DNS server with knowledge of the IN-ADDR domain. OCMust: OCMay: poc, ipnetwork, ipblock ASN1ATMacro: inaddrServerInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax Attribute Type: Domain Name Server Information Description: The Domain Name Server Information attribute identifies a computer running a DNS server. OCMust: OCMay: poc, domainname ASN1ATMacro: domainNameServerInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax Kosters and Sataluri [Page 15] Representing Registration Information in X.500 March 1993 Attribute Type: Domain Information Description: The Domain Information attribute identifies an Internet domain. OCMust: OCMay: poc, ipnetwork, ipblock ASN1ATMacro: domainInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax Attribute Type: Autonomous System Information Description: The Autonomous System Information attribute identifies an Internet autonomous system. OCMust: OCMay: poc ASN1ATMacro: asnInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax Attribute Type: Network Information Description: The Network Information attribute identifies an IP network. OCMust: OCMay: poc, domainname ASN1ATMacro: networkInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax Attribute Type: Organization Information Description: The Organization Information attribute identifies an Organization participating in the pilot project. OCMust: Kosters and Sataluri [Page 16] Representing Registration Information in X.500 March 1993 OCMay: nicObject ASN1ATMacro: orgInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax SINGLE VALUE Attribute Type: Provider Information Description: The Provider Information attribute identifies the service provider of a network service and can be included only if the service provider is participating in the pilot project. OCMust: OCMay: ipnetwork, ipblock ASN1ATMacro: providerInfoSee ATTRIBUTE WITH ATTRIBUTE SYNTAX distinguishedNameSyntax SINGLE VALUE Attribute Type: IP Network Name Description: The IP Network Name attribute lists the name of an IP network. OCMust: OCMay: ipnetwork, ipblock ASN1ATMacro: ipNetName ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-names)) SINGLE VALUE ub-names INTEGER ::= 64 Attribute Type: Autonomous System Name Description: The Autonomous System Name attribute lists the name of an Autonomous System. OCMust: Kosters and Sataluri [Page 17] Representing Registration Information in X.500 March 1993 OCMay: asn, asnblock ASN1ATMacro: asnName ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-names)) SINGLE VALUE Attribute Type: Host Name Description: The Host Name attribute lists the hostname of a server. OCMust: server OCMay: ASN1ATMacro: hostName ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-names)) SINGLE VALUE Attribute Type: IP Address Description: The IP Address attribute lists the IP address of a server. OCMust: server OCMay: ASN1ATMacro: ipAddress ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-ipnetworknumber)) SINGLE VALUE Attribute Type: Handle Description: The Handle lists the unique identifier assigned by a registration authority to each registered entity. OCMust: OCMay: nicObject Kosters and Sataluri [Page 18] Representing Registration Information in X.500 March 1993 ASN1ATMacro: handle ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-handle)) SINGLE VALUE ub-handle INTEGER ::= 10 Attribute Type: Delegated Block Description: The Delegated Block boolean attribute denotes whether a block of IP network addresses or autonomous system numbers has been delegated to an other registration authority. OCMust: OCMay: ipblock, asnblock ASN1ATMacro: delegatedBlock ATTRIBUTE WITH ATTRIBUTE SYNTAX booleanSyntax SINGLE VALUE Attribute Type: Domain Name Description: OCMust: OCMay: domainname ASN1ATMacro: domainName ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreStringSyntax (SIZE (1 .. ub-domainname)) ub-domainname INTEGER ::= 64 Attribute Type: Domain Name System Resource Record Description: OCMust: OCMay: domainname Kosters and Sataluri [Page 19] Representing Registration Information in X.500 March 1993 ASN1ATMacro: dnsRRecord ATTRIBUTE WITH ATTRIBUTE SYNTAX caseIgnoreListSyntax (SEQUENCE SIZE(1 .. ub-dnsrrecordlist) (SIZE (1 .. ub-dnsrrecord))) ub-dnsrrecordlist INTEGER ::= 64 ub-dnsrrecord INTEGER ::= 64 References [RFC1274]Paul Barker, Steve Hardcastle-Kille. The COSINE and Internet X.500 Schema. RFC 1274, 1991. [RFC1279]Steve Hardcastle-Kille. X.500 and Domains. RFC 1279, November 1991. [OSI-DS-14]Chris Weider, and Mark Knopper. Interim Schema for Network Infrastructure Information in X.500. Internet Draft osi-ds-14, March 1991. [OSI-DS-16]Chris Weider, and Mark Knopper. Schema for Network Informa- tion Center (NIC) Profiles in X.500. Internet Draft osi-ds-16-01, March 1992. [OSI-DS-19]Chris Weider, Mark Knopper, and Ruth Lang. Interim Directory Structure for Schema for Network Infrastructure Information. Inter- net Draft osi-ds-19, April 1991. [OSI-DS-37]Glenn Mansfield, Thomas Johannsen, and Mark Knopper. Chart- ing Networks in the Directory. Draft proposal osi-ds-37, February 1993. [OSI-DS-38]Glenn Mansfield, Thomas Johannsen, and Mark Knopper. Representing IP information in the X.500 Directory. Draft proposal osi-ds-38, February 1993. [OSI-DS-??]Mark Knopper. Representing Networking Infrastructure Infor- mation in X.500. Draft proposal. July 1992. [FOX-SCHEMA]Ruth Lang. FOX WHOIS schema information. Personal Communi- cation, March 1993. [MIN1]osids-minutes-91feb.txt [MIN2]osids-minutes-91jul.txt Kosters and Sataluri March 26, 1993 [Page 20] Representing Registration Information in X.500 March 1993 [MIN3]osids-minutes-92mar.txt 5. Security Considerations Security considerations are not discussed in this memo. 6. Acknowledgements We acknowledge the many constructive comments provided by Ruth Lang of SRI International on earlier drafts of this proposal. 7. Authors' Addresses Mark Kosters Network Solutions Email: markk@internic.net Srinivas Sataluri AT&T Bell Laboratories Email: sri@qsun.att.com Kosters and Sataluri March 26, 1993 [Page 21]
- Internet Draft sri