From 97bd09c5a60515e4bb70ffeebcd07cb22384bc68 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Zden=C4=9Bk=20Salvet?= Date: Tue, 11 May 2010 10:33:28 +0000 Subject: [PATCH] Zminky o IPv6. --- org.glite.lb.doc/src/LBUG-Introduction.tex | 6 ++++-- org.glite.lb.doc/src/README-standards.txt | 2 ++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/org.glite.lb.doc/src/LBUG-Introduction.tex b/org.glite.lb.doc/src/LBUG-Introduction.tex index dfc001a..4dce9fb 100644 --- a/org.glite.lb.doc/src/LBUG-Introduction.tex +++ b/org.glite.lb.doc/src/LBUG-Introduction.tex @@ -144,8 +144,10 @@ to know where to find the appropriate \LB database too. While it is possible to devise a global service where each job registers its jobid together with the address of the appropriate database, such a service could easily become a bottleneck. We opted for another solution, -to keep the address of the \LB database within the jobid. This way, -finding appropriate \LB database address becomes a local operation +to keep the address of the \LB database within the jobid (actually, +fully qualified hostname is strongly recommended instead of numeric address +and numeric IPv6 address is not supported for backward compatibility reasons). +This way, finding appropriate \LB database address becomes a local operation (at most parsing the jobid) and users can use the same mechanism when connecting to the \LB database to retrieve information about a particular job (users know its jobid). To simplify the situation even further, diff --git a/org.glite.lb.doc/src/README-standards.txt b/org.glite.lb.doc/src/README-standards.txt index 77e795b..d7c7911 100644 --- a/org.glite.lb.doc/src/README-standards.txt +++ b/org.glite.lb.doc/src/README-standards.txt @@ -64,6 +64,8 @@ IETF Standard, for IPv6 related specifications see http://www.ipv6.org/specs.htm - all communication in LB must be modified to fully support IPv6 - affected modules: [org.glite.]jobid, security.gss, security.gsoap-plugin, lb.common, lb.client, lb.logger, lb.server +- done as of release 2.1 (IPv6 is fully supported except use of numeric + IPv6 address in jobid) [SNMP] Simple Network Management Protocol (SNMP), Version 3 IETF Standard, for list of related RFCs see http://en.wikipedia.org/wiki/SNMP#RFCs -- 1.8.2.3