view release on metacpan or  search on metacpan

extra_docs/af-saa-0069.000.txt  view on Meta::CPAN

6.3 CONNECTION USAGE	7
7. NATIVE ATM SERVICES INTERFACE	7
8. ATM DIRECTORY SERVICE INTERFACE	9
9. REFERENCES	9
APPENDIX A: REQUIREMENTS	10
A.1 Basing of ANS on DNS	10
A.2 ANS requirements	10
APPENDIX B: API INTERFACE TO ANS	12
B.1 BSD 4.3 CONFORMANT INTERFACE	12
B.1.1 Specifications	12
B.1.2 IPng aligned interface	14
B.1.3 WinSock 2 aligned interface	14



1. Introduction
 ATM applications require various types of directory services.  Directory services 
can be universal, that is, used by more than one application,  or they may be 
application specific.  An example of a universal directory service is finding an 
ATM address corresponding to the name of an ATM end system.  An example of 
an application specific service is finding the  providers of specific types of 

extra_docs/af-saa-0069.000.txt  view on Meta::CPAN

	struct atmnsap_addr *atmnsap_addr(const char *cp);
	char	*atmnsap_ntoa(struct atmnsap_addr in);

	struct atme164_addr *atme164_addr(const char *cp);
	char	*atme164_ntoa(struct atme164_addr in);

The returned and expected human readable strings conform to the form encountered in 
the master file and described in section 5.4. The returned structures must not be freed by 
the application and are not thread-safe.

????? IPng aligned interface

Since introduction of IPv6 included a new addressing scheme, the internet protocol next 
generation (IPNG) work in progress tries to address the issue of a new application 
programmer's interface, specifically of the name-resolving calls beside many others. 
These calls will support address family parameters so functions can be easily 
implemented to support AF_ATMNSAP and AF_ATME164 as well. Extended functions for 
address to ASCII conversions and vice versa translation can also be found in this work.

????? WinSock 2 aligned interface