< draft-ietf-ion-discov-atmarp-04.txt   draft-ietf-ion-discov-atmarp-05.txt >
Internet-Draft Mike Davison Internet-Draft Mike Davison
Cisco Systems Cisco Systems
Nov 15, 1998 Nov 15, 1998
ILMI-Based Server Discovery for ATMARP ILMI-Based Server Discovery for ATMARP
<draft-ietf-ion-discov-atmarp-04.txt> <draft-ietf-ion-discov-atmarp-05.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
To learn the current status of any Internet Draft, please check the To learn the current status of any Internet Draft, please check the
skipping to change at page 1, line 36 skipping to change at page 1, line 37
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
This memo provides information for the Internet community. This memo This memo provides information for the Internet community. This memo
does not specify an Internet standard of any kind. Distribution of does not specify an Internet standard of any kind. Distribution of
this memo is unlimited. this memo is unlimited.
Abstract Abstract
This memo defines how ILMI-based Server Discovery, which provides a This memo defines how ILMI-based Server Discovery, which provides a
method for ATM-attached hosts and routers to dynamically determine method for ATM-attached hosts and routers to dynamically determine
the ATM address of servers, shall be used to locate ATMARP servers. the ATM addresses of servers, shall be used to locate ATMARP
servers.
1. Introduction 1. Introduction
Presently, configuring a host or router to use ATMARP [1] is Presently, configuring a host or router to use ATMARP [1] is
cumbersome and error-prone since it requires at least one ATM cumbersome and error-prone since it requires at least one ATM
addresses to be statically configured on each host or router in the addresses to be statically configured on each host or router in the
network. Further, it is impossible to implement a diskless host to network. Further, it is impossible to implement a diskless host to
use ATMARP since local configuration is required. ILMI-based Server use ATMARP since local configuration is required. ILMI-based Server
Discovery, hereafter referred to as "server discovery," provides a Discovery, hereafter referred to as "server discovery," provides a
solution to these problems. solution to these problems.
skipping to change at page 4, line 39 skipping to change at page 4, line 39
An ATMARP client with no local configuration, such as a diskless An ATMARP client with no local configuration, such as a diskless
workstation, must use the row with the lowest index value if multiple workstation, must use the row with the lowest index value if multiple
ATMARP servers, possibly for multiple networks, are listed. ATMARP servers, possibly for multiple networks, are listed.
ATMARP clients that have local IP configuration must use a row that ATMARP clients that have local IP configuration must use a row that
has the appropriate IP address. For example, consider the case where has the appropriate IP address. For example, consider the case where
an IP router has 3 logical interfaces defined on a single physical an IP router has 3 logical interfaces defined on a single physical
interface with IP addresses 1.0.0.1/8, 128.10.0.1/16 and interface with IP addresses 1.0.0.1/8, 128.10.0.1/16 and
171.69.150.226/24. The router will sweep the service registry table 171.69.150.226/24. The router will sweep the service registry table
looking for a rows that have atmfSrvcRegParm1 values as shown below: looking for rows that have atmfSrvcRegParm1 values as shown below:
Network number/mask atmfSrvcRegParm1 Network number/mask atmfSrvcRegParm1
-------------------- -------------------------------------- -------------------- --------------------------------------
1.0.0.0/8 08 00 04 01 00 00 00 ff 00 00 00 1.0.0.0/8 08 00 04 01 00 00 00 ff 00 00 00
128.10.0.0/16 08 00 04 80 0a 00 00 ff ff 00 00 128.10.0.0/16 08 00 04 80 0a 00 00 ff ff 00 00
171.69.150.0/24 08 00 04 ab 45 96 00 ff ff ff 00 171.69.150.0/24 08 00 04 ab 45 96 00 ff ff ff 00
When the correct atmfSrvcRegParm1 values are located, the router may When the correct atmfSrvcRegParm1 values are located, the router may
then establish an SVC to the selected server and perform the then establish an SVC to the selected server and perform the
appropriate protocol operations. appropriate protocol operations.
skipping to change at page 5, line 25 skipping to change at page 5, line 25
5. ATMARP Server Behavior 5. ATMARP Server Behavior
An ATMARP server shall be locally configured. The ATMARP server may An ATMARP server shall be locally configured. The ATMARP server may
retrieve the ATMARP service registry data to validate the results. If retrieve the ATMARP service registry data to validate the results. If
an incorrect row is retrieved the error may be flagged in a locally an incorrect row is retrieved the error may be flagged in a locally
significant way. significant way.
6. Relationship with PNNI Augmented Routing 6. Relationship with PNNI Augmented Routing
An augmented version PNNI ("PNNI Augmented Routing," or PAR) is being An augmented version PNNI ("PNNI Augmented Routing," or PAR) [3] has
developed by the ATM Forum. PAR can distribute data such as ATMARP been developed by the ATM Forum. PAR can distribute data such as
server addresses. Further, the ATM Forum is developing a proxy ATMARP server addresses. Further, the ATM Forum is developing a proxy
mechanism for PAR (Proxy PAR) that would allow a UNI-attached host or mechanism for PAR (Proxy PAR) that would allow a UNI-attached host or
router to access PAR data without a full PAR implementation. These router to access PAR data without a full PAR implementation. These
mechanisms offer a promising way to manage the service registry mechanisms offer a promising way to manage the service registry
tables maintained on each switch in an ATM network, yet would not tables maintained on each switch in an ATM network, yet would not
require changes to the mechanism defined in this memo. Hosts and require changes to the mechanism defined in this memo. Hosts and
routers can continue to utilize ILMI-based or Proxy PAR-based server routers can continue to utilize ILMI-based or Proxy PAR-based server
discovery and network administrators could manage the service discovery and network administrators could manage the service
registry data with local configuration or via PAR and Proxy PAR. registry data with local configuration or via PAR and Proxy PAR.
7. Security Considerations 7. Security Considerations
skipping to change at page 7, line 5 skipping to change at page 6, line 43
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
References References
[1] Laubach, M. Halpern, J., "Classical IP and ARP over ATM," [1] Laubach, M. Halpern, J., "Classical IP and ARP over ATM,"
RFC 2225, Com21, Inc. and Newbridge Networks, Inc., April 1998. RFC 2225, Com21, Inc. and Newbridge Networks, Inc., April 1998.
[2] ATM Forum, "Integrated Local Management Interface (ILMI) [2] ATM Forum, "Integrated Local Management Interface (ILMI)
Specification Version 4.0," af-ilmi-0065.000, September, 1996. Specification Version 4.0," af-ilmi-0065.000, September, 1996.
[3] ATM Forum, "PNNI Augmented Routing (PAR) Version 1.0,"
af-ra-0104, January, 1999.
Author's Address Author's Address
Mike Davison Mike Davison
Cisco Systems Cisco Systems
170 West Tasman Drive 170 West Tasman Drive
San Jose, California 95134 San Jose, California 95134
Phone: (408) 526-4000 Phone: (408) 526-4000
EMail: mike.davison@cisco.com EMail: mike.davison@cisco.com
 End of changes. 6 change blocks. 
7 lines changed or deleted 12 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/