Changes between Initial Version and Version 1 of IPv6


Ignore:
Timestamp:
Dec 2, 2007 3:52:31 PM (14 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IPv6

    v1 v1  
     1IPv6 support is available in the following platforms: 
     2 - Windows XP, Windows Server 2003, and Windows Vista, using Microsoft Platform SDK for Windows Server 2003 SP1 
     3 - Symbian 
     4 - Linux, and probably other Unix platforms 
     5 
     6Windows 2000 does not have IPv6 installed, but it may be added by installing [http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/ReadMe.asp Microsoft IPv6 Technology Preview for Windows 2000 (IPv6Kit)]. For information on how to install IPv6Kit on Win2K SP4, please see [http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx IPv6 FAQ]. 
     7 
     8IPv6 is '''NOT''' supported by SDK that comes with Microsoft Visual Studio 6. To use Visual Studio 6, you must install and download the newer Platform SDK above. 
     9 
     10 
     11== IPv6 Support in pjlib == 
     12 
     13pjlib supports IPv6, but this has to be enabled. To enable IPv6, the {{{PJ_HAS_IPV6}}} macro needs to be enabled in {{{pj/config_site.h}}}: 
     14 
     15{{{ 
     16 #define PJ_HAS_IPV6 1 
     17}}} 
     18 
     19 
     20'''Socket Addresses''': 
     21 - An IPv4 socket address is represented by {{{pj_sockaddr_in}}} structure, while an IPv6 socket address is represented by {{{pj_sockaddr_in6}}} structure. The {{{pj_sockaddr}}} structure is a union which may contain IPv4 or IPv6 socket address, depending on the address family field. 
     22 - Various new socket address API's have been added which can work on both IPv4 and IPv6 address, such as: 
     23     - pj_inet_pton() 
     24     - pj_inet_ntop() 
     25     - pj_inet_ntop2() 
     26     - pj_sockaddr_init() 
     27     - pj_sockaddr_get_addr() 
     28     - pj_sockaddr_has_addr() 
     29     - pj_sockaddr_get_addr_len() 
     30     - pj_sockaddr_set_str_addr() 
     31     - pj_sockaddr_get_port() 
     32     - pj_sockaddr_set_port() 
     33     - pj_sockaddr_get_len() 
     34 
     35 
     36'''Socket and IOQueue API''': 
     37 - The {{{pj_sockaddr}}} structure is a union which may contain IPv4 or IPv6 socket address. Application may pass this structure to various pjlib socket functions which take {{{pj_sockaddr_t}}} as an argument, such as {{{pj_sock_bind()}}}, {{{pj_sock_sendto()}}}, {{{pj_sock_recvfrom()}}}, {{{pj_sock_accept()}}}, etc. 
     38 - The ''ioqueue'' is also capable of supporting IPv6. 
     39 
     40 
     41'''Address Resolution API''': 
     42 - A new API {{{pj_getaddrinfo()}}} has been added to resolve both IPv4 and IPv6 addresses, in addition to existing {{{pj_gethostbyname()}}} API which resolves IPv4 address,  
     43 - The {{{pj_gethostip()}}} and {{{pj_getdefaultipinterface()}}} API has been modified to take an additional address family argument. 
     44 
     45 
     46'''IP Helper API''': 
     47 - The {{{pj_enum_ip_interface()}}} API has been modified to take an additional address family argument. 
     48 
     49 
     50== IPv6 Support in pjsip == 
     51 
     52'''IPv6 SIP Transport''': 
     53 - The SIP UDP transport now supports IPv6 sockets, and new API's have been added to facilitate IPv6 transport creation ({{{pjsip_udp_transport_start6()}}} and {{{pjsip_udp_transport_attach2()}}}). Note that if application wants to support both IPv4 and IPv6 UDP transports, two separate UDP transport instances must be created, one for each address family. 
     54 
     55'''IPv6 Address Representation''': 
     56 - IPv6 address may appear in two types of places in the SIP message: in a host part of a header field (such as host part of an URI, or host part in a Via header), and as a parameter value (such as the value of ''received'' and ''maddr'' parameter).  
     57 - Although in the SIP ABNF grammar an IPv6 may or may not be enclosed in square brackets ('''[''' and ''']''' characters), in pjsip all IPv6 addresses will be represented '''without''' the square brackets, for consistency. This means pjsip will remove the square brackets, if they are present, during parsing process, and will enclose the address with square brackets as necessary when pjsip prints the Ipv6 address in a packet for transmission. When application inspects a message component that contains IPv6 address, it will always find it without the enclosing brackets. 
     58 
     59 
     60== IPv6 Support in pjlib-util (DNS SRV and AAAA resolution) == 
     61 
     62To be done. 
     63 
     64 
     65== IPv6 Support in pjmedia (SDP, media transport) == 
     66 
     67To be done. 
     68 
     69 
     70== IPv6 Support in pjnath (STUN and ICE) == 
     71 
     72To be done. 
     73 
     74