I-D ACTION:draft-ietf-mixer-rfc1664bis-00.txt

Internet-Drafts@ietf.org Mon, 03 February 1997 15:28 UTC

Received: from ietf.org by ietf.org id aa17417; 3 Feb 97 10:28 EST
Received: from ietf.ietf.org by ietf.org id aa14963; 3 Feb 97 9:56 EST
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
cc: ietf-mixer@innosoft.com
Sender: ietf-announce-request@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mixer-rfc1664bis-00.txt
Date: Mon, 03 Feb 1997 09:56:15 -0500
X-Orig-Sender: cclark@ietf.org
Message-ID: <9702030956.aa14963@ietf.org>

 A New Internet-Draft is available from the on-line Internet-Drafts 
 directories. This draft is a work item of the MIME - X.400 Gateway Working
 Group of the IETF.                                                        

       Title     : Using the Internet DNS to Distribute MIXER Conformant
                   Global Address Mapping (MCGAM)
       Pages     : 23                        
       Author(s) : C. Allocchio
       Filename  : draft-ietf-mixer-rfc1664bis-00.txt
       Pages     : 23
       Date      : 01/31/1997

This memo is the complete technical specification to store in the Internet 
Domain Name System (DNS) the mapping information (MCGAM) needed by MIXER 
conformant e-mail gateways and other tools to map RFC822 domain names into 
X.400 O/R names and vice versa.  Mapping information can be managed in a 
distributed rather than a centralised way. Organizations can publish their 
MIXER mapping or preferred gateway routing information using just local 
resources (their local DNS server), avoiding the need for a strong 
coordination with any centralised organization. MIXER conformant gateways 
and tools located on Internet hosts can retrieve the mapping information 
querying the DNS instead of having fixed tables which need to be centrally 
updated and distributed.    

This memo obsoletes RFC1664. It includes the changes introduced by 
MIXER specification with respect to RFC1327: the new 'gate1' 
(O/R addresses to domain) table is fully supported. Full backward 
compatibility with RFC1664 specification is mantained, too.   

RFC1664 was a joint effort of IETF X400 operation working group (x400ops) 
and TERENA (formely named "RARE") Mail and Messaging working group (WG-MSG). 
This update was performed by the IETF MIXER working group.                      

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
     "get draft-ietf-mixer-rfc1664bis-00.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-ietf-mixer-rfc1664bis-00.txt
 
Internet-Drafts directories are located at:	
	                                                
     o  Africa:  ftp.is.co.za                    
	                                                
     o  Europe:  ftp.nordu.net            	
                 ftp.nis.garr.it                 
	                                                
     o  Pacific Rim: munnari.oz.au               
	                                                
     o  US East Coast: ds.internic.net           
	                                                
     o  US West Coast: ftp.isi.edu               
	                                                
Internet-Drafts are also available by mail.	
	                                                
Send a message to:  mailserv@ds.internic.net. In the body type: 
     "FILE /internet-drafts/draft-ietf-mixer-rfc1664bis-00.txt".
							
NOTE: The mail server at ds.internic.net can return the document in
      MIME-encoded form by using the "mpack" utility.  To use this
      feature, insert the command "ENCODING mime" before the "FILE"
      command.  To decode the response(s), you will need "munpack" or
      a MIME-compliant mail reader.  Different MIME-compliant mail readers
      exhibit different behavior, especially when dealing with
      "multipart" MIME messages (i.e., documents which have been split
      up into multiple messages), so check your local documentation on
      how to manipulate these messages.
							
							

Below is the data which will enable a MIME compliant mail reader 
implementation to automatically retrieve the ASCII version
of the Internet-Draft.
ftp://ds.internic.net/internet-drafts/draft-ietf-mixer-rfc1664bis-00.txt"><ftp://ds.internic.net/internet-drafts/draft-ietf-mixer-rfc1664bis-00.txt>