Browse Prior Art Database

Volatile Routing Specification

IP.com Disclosure Number: IPCOM000108542D
Original Publication Date: 1992-Jun-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 84K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+3]

Abstract

A methodology is described which prevents unnecessary administration of destination node identifiers (IDs) in a mail system. Administration of system node identifiers is made convenient, especially when a system path contains a dynamically changing set of nodes.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Volatile Routing Specification

       A methodology is described which prevents unnecessary
administration of destination node identifiers (IDs) in a mail
system.  Administration of system node identifiers is made
convenient, especially when a system path contains a dynamically
changing set of nodes.

      System routing agents must be defined with a set of valid node
IDs (e.g., DALHQIC1, MSNVM2, etc.) on a given system.  In many
topologies, a system can have many valid node IDs.  It is also
desirable to administrate new node IDs or remove node IDs in a system
without forcing an update of many connected systems.  This article
describes a methodology for administrating an arbitrary set of node
IDs to a system connection.  For example, a system may have three
connections to other systems.  As is typical in prior art, the valid
node identifiers must be associated with each connection.  Each
connection will have a set of node IDs administrated as valid so that
distribution recipient lists outgoing on a connection contain one of
the node IDs in the set.  A distribution recipient list contains node
IDs which are used in a compare to a node ID routing table for
determining the appropriate connection to send over.  A connection is
a link to another system where a conversation can occur between the
connected systems and data can be transmitted between the systems.  A
variety of protocols can be used on connections.  Consider three
connections defined as CONNECTION 1 supporting NODE001, NODE002,
NODE003, NODE004 and NODE005, CONNECTION 2 supporting NODE009,
NODE010, NODE011, ... NODE789 and CONNECTION 3 supporting NODE006,
NODE007 and NODE008.  Using prior art, connection 2 requires
laborious administration of each valid node ID which can be sent out
on connection 2.  Furthermore, if the topology connected over
connection 2 contain...