H A D | name6.c | be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh
|
H A D | getaddrinfo.c | be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh be26adb5 Thu Feb 10 02:59:50 GMT 2000 Yoshinobu Inoue <shin@FreeBSD.org> Let getaddrinfo() and related functions supports traditional IPv4 format (shortend format, etc)
Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync"
So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format.
Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh
|