A new Request for Comments is now available in online RFC libraries.


        RFC 2391:

        Title:	    Load Sharing using IP Network Address Translation
		    (LSNAT)
	Author(s):  P. Srisuresh, D. Gan
	Status:     Informationl
	Date:       August 1998
        Mailbox:    suresh@ra.lucent.com, dhg@juniper.net
	Pages:      18
        Characters: 44884
        Updates/Obsoletes/See Also: None


        URL:        ftp://ftp.isi.edu/in-notes/rfc2391.txt


Network Address Translators (NATs) translate IP addresses in a 
datagram, transparent to end nodes, while routing the datagram.  
NATs have traditionally been been used to allow private network 
domains to connect to Global networks using as few as one 
globally unique IP address.  In this document, we extend the 
use of NATs to offer Load share feature, where session load can 
be distributed across a pool of servers, instead of directing 
to a single server.  Load sharing is beneficial to service 
providers and system administrators alike in grappling with 
scalability of servers with increasing session load. 

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute