idnits 2.17.1 draft-ietf-ion-discov-atmarp-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-20) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 5 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 6 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 100 has weird spacing: '...ar$addr a oct...' == Line 101 has weird spacing: '...ar$mask a oct...' == Line 133 has weird spacing: '...er/mask atmfS...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 21, 1997) is 9739 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1577 (ref. '1') (Obsoleted by RFC 2225) -- No information found for draft-ietf-ion-classic2 - is the name correct? -- Possible downref: Normative reference to a draft: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Non-RFC (?) normative reference: ref. '5' -- Possible downref: Non-RFC (?) normative reference: ref. '6' Summary: 9 errors (**), 0 flaws (~~), 7 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft Mike Davison 3 Cisco Systems 4 August 21, 1997 6 ILMI-Based Server Discovery for ATMARP 7 9 Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months 17 and may be updated, replaced, or obsoleted by other documents at any 18 time. It is inappropriate to use Internet- Drafts as reference 19 material or to cite them other than as "work in progress." 21 To view the entire list of current Internet-Drafts, please check the 22 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 23 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Europe), 24 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 25 ftp.isi.edu (US West Coast). 27 Abstract 29 This memo defines how ILMI-based Server Discovery, which provides a 30 method for ATM-attached hosts and routers to dynamically determine 31 the ATM address of servers, shall be used to locate ATMARP servers. 33 1. Introduction 35 Presently, configuring a host or router to use ATMARP [1,2] is 36 cumbersome and error-prone since it requires at least one ATM 37 addresses to be statically configured on each host or router in the 38 network. Further, it is impossible to implement a diskless host to 39 use ATMARP since local configuration is required. ILMI-based Server 40 Discovery, hereafter referred to as "server discovery," provides a 41 solution to these problems. 43 A brief overview of the Service Registry MIB, as defined by the ATM 44 Forum, is provided in this memo. The reader should consult [3] for a 45 complete description of this MIB, but the information contained here 46 is sufficient for an understanding of its use to support ATMARP 47 server discovery. 49 2. ILMI 4.0 Service Registry MIB 51 Server discovery utilizes the Service Registry MIB defined by the ATM 52 Forum in ILMI Specification Version 4.0 [3]. To support the existing 53 framework for IP over ATM, ATM switches must support the Service 54 Registry MIB. 56 A row in the service registry table [3] is defined as: 58 AtmfSrvcRegEntry ::= SEQUENCE { 59 atmfSrvcRegPort INTEGER, 60 atmfSrvcRegServiceID OBJECT IDENTIFIER, 61 atmfSrvcRegATMAddress AtmAddress, 62 atmfSrvcRegAddressIndex INTEGER, 63 atmfSrvcRegParm1 OCTET STRING 64 } 66 The definition of each field in this structure is: 68 atmfSrvcRegPort - The port number for which this entry contains 69 management information. The value of zero may be used to 70 indicate the ATM interface over which a management request 71 was received. 73 atmfSrvcRegServiceID - This is the service identifier which 74 uniquely identifies the type of service at the address 75 provided in the table. (See Appendix for ATMARP OID.) 77 atmfSrvcRegATMAddress - This is the full address of the service. 79 The ATM client will use this address to establish a connection 80 with the service. 82 atmfSrvcRegAddressIndex - An arbitrary integer to differentiate 83 multiple rows containing different ATM addresses for the same 84 service on the same port. 86 atmfSrvcRegParm1 - An octet string whose size and meaning is 87 determined by the value of atmfSrvcRegServiceID. 89 The service registry table is indexed by atmfSrvcRegPort, 90 atmfSrvcRegServiceID and atmfSrvcRegAddressIndex. 92 3. Service Parameter String 94 A generic parameter string is defined in the service registry table, 95 thus allowing protocol-specific parameters to be specified. To be 96 consistent with [1,2], the parameter string for ATMARP shall be: 98 ar$pro 16 bits Protocol type 99 ar$plen 8 bits Length of protocol address (a) 100 ar$addr a octets Network address 101 ar$mask a octets Network mask 103 Where 105 ar$pro - see Assigned Numbers for protocol type number for 106 protocol using ATMARP. (IPv4 is 0x0800, IPv6 is 0x86DD) 108 ar$plen - Length of the protocol address. (IPv4 is 4, IPv6 is 16) 110 ar$addr - Network address represented in network byte order 112 ar$mask - Network mask represented in network byte order 114 4. ATMARP Client Behavior 116 An ATMARP client will access the service registry table via ILMI 117 using the SNMP GetNext operator to "sweep" (SNMP parlance for a 118 linear search) beginning with {Port = 0, ServiceID = , 119 Index = 0} while holding the port number and the serviceID constant. 120 (Port number 0 is used within ILMI to indicate "this port.") 122 An ATMARP client with no local configuration, such as a diskless 123 workstation, must use the row with the lowest index value if multiple 124 ATMARP servers, possibly for multiple networks, are listed. 126 ATMARP clients that have local IP configuration must use a row that 127 has the appropriate IP address. For example, consider the case where 128 an IP router has 3 logical interfaces defined on a single physical 129 interface with IP addresses 1.0.0.1/8, 128.10.0.1/16 and 130 171.69.150.226/24. The router will sweep the service registry table 131 looking for a rows that have atmfSrvcRegParm1 values as shown below: 133 Network number/mask atmfSrvcRegParm1 134 -------------------- -------------------------------------- 135 1.0.0.0/8 08 00 04 01 00 00 00 ff 00 00 00 136 128.10.0.0/16 08 00 04 80 0a 00 00 ff ff 00 00 137 171.69.150.0/24 08 00 04 ab 45 96 00 ff ff ff 00 139 When the correct atmfSrvcRegParm1 values are located, the router may 140 then establish an SVC to the selected server and perform the 141 appropriate protocol operations. 143 Redundant ATMARP servers are supported with multiple rows in the 144 service registry table. This list of ATMARP servers is ordered with 145 the primary ATMARP server having the lowest index value. The ATMARP 146 client must attempt to utilize the primary ATMARP server before 147 utilizing a secondary ATMARP server. Administrators must ensure that 148 the listed ATMARP servers are synchronized via [4]. 150 5. ATMARP Server Behavior 152 An ATMARP server shall be locally configured. The ATMARP server may 153 retrieve the ATMARP service registry data to validate the results. If 154 an incorrect row is retrieved the error may be flagged in a locally 155 significant way. 157 6. Relationship with PNNI Augmented Routing 159 An augmented version PNNI ("PNNI Augmented Routing," or PAR) [5] is 160 being developed by the ATM Forum. PAR could potentially distribute 161 data such as ATMARP server addresses. Further, the ATM Forum is 162 developing a proxy mechanism for PAR (Proxy PAR) [6] that would allow 163 a UNI-attached host or router to access PAR data without a full PAR 164 implementation. 166 These mechanisms offer a promising way to manage the service registry 167 tables maintained on each switch in an ATM network, yet would not 168 require changes to the mechanism defined in this memo. Hosts and 169 routers can continue to utilize ILMI-based or Proxy PAR-based server 170 discovery and network administrators could manage the service 171 registry data with local configuration or via PAR and Proxy PAR. 173 7. Security Considerations 175 The server discovery mechanism is intended for environments where a 176 given ATM switch and its attached hosts or routers are in the same 177 administrative domain, hence no authentication is required. 179 Appendix - ATMARP Server Discovery MIB 181 SERVER-DISCOVERY-ATMARP DEFINITIONS ::= BEGIN 183 -- 184 -- This OID names ATMARP within the context of server discovery. 185 -- It does not name any managed objects. 186 -- 187 serverDiscoveryATMARP OBJECT IDENTIFIER ::= 189 END 191 References 193 [1] Laubach, M., "Classical IP and ARP over ATM," RFC 1577, 194 Hewlett-Packard Laboratories, December 1993. 196 [2] Laubach, M. Halpern, J., "Classical IP and ARP over ATM," 197 draft-ietf-ion-classic2-02.txt, (update to RFC 1577), March 1997. 199 [3] ATM Forum, "Integrated Local Management Interface (ILMI) 200 Specification Version 4.0," af-ilmi-0065.000, September, 1996. 202 [4] Luciani, J., and Fox, B., "A distributed ATMARP Service Using 203 SCSP," , April, 1997. 205 [5] Callon, R., et al., "An Overview of PNNI Augmented Routing," 206 ATM-Forum 96-0354, April, 1996. 208 [6] Przygienda, T., and Droz, P., "Proxy PAR," ATM-Forum 97-0495, 209 July, 1997. 211 Author's Address 213 Mike Davison 214 Cisco Systems 215 170 West Tasman Drive 216 San Jose, California 95134 218 Phone: (408) 526-4000 219 EMail: mike.davison@cisco.com