Subject: I-D ACTION:draft-ietf-ipngwg-bsd-api-03.txt (fwd)
To: None <current-users@NetBSD.ORG>
From: Peter Galbavy <peter@wonderland.org>
List: current-users
Date: 11/22/1995 22:07:44
I am posting this in case it is of interest to the hackers out there...

Forwarded message:
> From ietf-announce-request@IETF.CNRI.Reston.VA.US Wed Nov 22 13:37:46 1995
> Mime-Version: 1.0
> Content-Type: Multipart/Mixed; Boundary="NextPart"
> To: IETF-Announce:;
> cc: ipng@sunroof.eng.sun.com
> Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
> From: Internet-Drafts@CNRI.Reston.VA.US
> Reply-to: Internet-Drafts@CNRI.Reston.VA.US
> Subject: I-D ACTION:draft-ietf-ipngwg-bsd-api-03.txt
> Date: Wed, 22 Nov 95 10:01:41 -0500
> X-Orig-Sender: cclark@CNRI.Reston.VA.US
> Message-ID:  <9511221001.aa11649@IETF.CNRI.Reston.VA.US>
> 
> --NextPart
> 
> A Revised Internet-Draft is available from the on-line Internet-Drafts 
> directories. This draft is a work item of the IPNG Working Group of the 
> IETF.                                                                      
> 
>        Title     : IPv6 Program Interfaces for BSD Systems                 
>        Author(s) : R. Gilligan, S. Thomson, J. Bound
>        Filename  : draft-ietf-ipngwg-bsd-api-03.txt
>        Pages     : 33
>        Date      : 11/21/1995
> 
> In order to implement the version 6 Internet Protocol (IPv6) [1] in an 
> operating system based on Berkeley Unix (4.x BSD), changes must be made to 
> the application program interface (API).  TCP/IP applications written for 
> BSD-based operating systems have in the past enjoyed a high degree of 
> portability because most of the systems derived from BSD provide the same 
> API, known informally as "the socket interface".  We would like the same 
> portability with IPv6.  This memo presents a set of extensions to the BSD 
> socket API to support IPv6.  The changes include a new data structure to 
> carry IPv6 addresses, new name to address translation library functions, 
> new address conversion functions, and some new setsockopt() options.  The 
> extensions are designed to provide access to IPv6 features, while 
> introducing a minimum of change into the system and providing complete 
> compatibility for existing IPv4 applications.                              
> 
> 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-ipngwg-bsd-api-03.txt".
> A URL for the Internet-Draft is:
> ftp://ds.internic.net/internet-drafts/draft-ietf-ipngwg-bsd-api-03.txt
>  
> Internet-Drafts directories are located at:	
> 	                                                
>      o  Africa                                   
>         Address:  ftp.is.co.za (196.4.160.8)	
> 	                                                
>      o  Europe                                   
>         Address:  nic.nordu.net (192.36.148.17)	
>         Address:  ftp.nis.garr.it (192.12.192.10)
> 	                                                
>      o  Pacific Rim                              
>         Address:  munnari.oz.au (128.250.1.21)	
> 	                                                
>      o  US East Coast                            
>         Address:  ds.internic.net (198.49.45.10)	
> 	                                                
>      o  US West Coast                            
>         Address:  ftp.isi.edu (128.9.0.32)  	
> 	                                                
> Internet-Drafts are also available by mail.	
> 	                                                
> Send a message to:  mailserv@ds.internic.net. In the body type: 
>      "FILE /internet-drafts/draft-ietf-ipngwg-bsd-api-03.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.
> 							
> For questions, please mail to Internet-Drafts@cnri.reston.va.us.
> 							
> 
> Below is the data which will enable a MIME compliant mail reader 
> implementation to automatically retrieve the ASCII version
> of the Internet-Draft.
> 
> --NextPart
> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
> 
> --OtherAccess
> Content-Type:  Message/External-body;
>         access-type="mail-server";
>         server="mailserv@ds.internic.net"
> 
> Content-Type: text/plain
> Content-ID: <19951121171011.I-D@CNRI.Reston.VA.US>
> 
> ENCODING mime
> FILE /internet-drafts/draft-ietf-ipngwg-bsd-api-03.txt
> 
> --OtherAccess
> Content-Type:   Message/External-body;
>         name="draft-ietf-ipngwg-bsd-api-03.txt";
>         site="ds.internic.net";
>         access-type="anon-ftp";
>         directory="internet-drafts"
> 
> Content-Type: text/plain
> Content-ID: <19951121171011.I-D@CNRI.Reston.VA.US>
> 
> --OtherAccess--
> 
> --NextPart--
> 


-- 
Peter Galbavy                                           peter@wonderland.org
@ Home                                                 phone://44/973/499465
in Wonderland                              http://www.wonderland.org/~peter/
                               snail://UK/NW1_6LE/London/21_Harewood_Avenue/