Permalink
Browse files

s/2553bis/3493

  • Loading branch information...
1 parent 1aff7ad commit 2d10700ca3bc418f221c5416eb0580f9a67b05ca itojun committed Sep 9, 2003
Showing with 9 additions and 9 deletions.
  1. +3 −3 COVERAGE
  2. +3 −3 IMPLEMENTATION
  3. +3 −3 PORTABILITY
View
@@ -1,6 +1,6 @@
Support coverage table for KAME/*BSD and KAME-merged *BSD
KAME project
-$KAME: COVERAGE,v 1.132 2003/04/09 08:21:41 suz Exp $
+$KAME: COVERAGE,v 1.133 2003/09/09 11:22:42 itojun Exp $
x: supported/integrated
@@ -194,7 +194,7 @@ IPV6_V6ONLY x x - x - - x -
getaddrinfo obeys configured resolv order
(+) x x x x x x -
-getaddrinfo supports AI_ADDRCONFIG (2553bis)
+getaddrinfo supports AI_ADDRCONFIG (RFC3493)
- - - x - - x -
(*1) enabled by default, cannot turn it off
@@ -208,7 +208,7 @@ getnameinfo uses addr%numeric for scopeid > maxifindex
getnameinfo, 2nd arg type is socklen_t
x x x x x x x -
-getnameinfo uses EAI_xx as return value (2553bis)
+getnameinfo uses EAI_xx as return value (RFC3493)
x x x x x x x -
getnameinfo always return a string with scope
View
@@ -2,7 +2,7 @@
KAME Project
http://www.kame.net/
- $KAME: IMPLEMENTATION,v 1.352 2003/08/06 23:40:33 itojun Exp $
+ $KAME: IMPLEMENTATION,v 1.353 2003/09/09 11:22:42 itojun Exp $
NOTE: The document tries to describe behaviors/implementation choices
@@ -1294,8 +1294,8 @@ On the contrary, XNET draft defines as follows:
/* and bunch of padding */
};
-In December 1999, it was agreed that RFC2553bis should pick the latter (XNET)
-definition.
+In December 1999, it was agreed that RFC2553bis (RFC3493) should pick the
+latter (XNET) definition.
KAME kit prior to December 1999 used RFC2553 definition. KAME kit after
December 1999 (including December) will conform to XNET definition,
View
@@ -1,6 +1,6 @@
Portability guideline
KAME project
- $KAME: PORTABILITY,v 1.67 2002/06/11 03:03:21 jinmei Exp $
+ $KAME: PORTABILITY,v 1.68 2003/09/09 11:22:42 itojun Exp $
Source code in the "kame" directory will be shared among operating systems
@@ -224,8 +224,8 @@ across those possibilities.
into __ss_len, or (2) never touch __ss_len. cast to sockaddr * and use
sa_len.
- Next version of RFC2553 (RFC2553bis) will define ss_len (not __ss_len),
- and be synchronized better with X/Open document.
+ Next version of RFC2553 (RFC2553bis = RFC3493) will define ss_len (not
+ __ss_len), and be synchronized better with X/Open document.
- Never, never touch the __u6_addr{,8,16,32} member in struct in6_addr
directly. Symbols starting with "__" are NOT supposed to be used.

0 comments on commit 2d10700

Please sign in to comment.