| CARVIEW |
Select Language
HTTP/1.1 200 OK
Date: Mon, 14 Jul 2025 15:23:52 GMT
Server: Apache
X-Content-Type-Options: nosniff
Vary: Accept-Encoding
Last-Modified: Sat, 14 Jan 2017 01:37:41 GMT
ETag: "12d7-54603ff064340-gzip"
Accept-Ranges: bytes
Cache-Control: max-age=31536000
Expires: Tue, 14 Jul 2026 15:23:52 GMT
Content-Encoding: gzip
X-Frame-Options: SAMEORIGIN
Referrer-Policy: origin-when-cross-origin
Content-Security-Policy: upgrade-insecure-requests
X-XSS-Protection: 1; mode=block
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8
Strict-Transport-Security: max-age=48211200; preload
GNSO Email Archives: [council]
ICANN/GNSO
GNSO Email List Archives
[council]
Re: [council] voting procedures
I would very much like to support Amadeu on this. Especially for non english natives a written document ensures a clear understanding of the implications a resolution might have. Best, tom Am 25.09.2003 schrieb Amadeu Abril i Abril: > Bruce and all, > > I think that in Carthage we should spend some minutes discussing better > ways of managing votes on resolutions. Amending resolutions on the fly > over the phone makes understanding the final picture very difficult. > Indeed, if we do have net access we always can see modified versions > (but we still should be able to find a ways to wathc the amendments > being introduced. Unfortunately not everybody can have mail/web access > during teleconfs. So we also need to revisit the written procedure for > voting. I dont think that we should require a confirmation by subsequent > teleconf. Perhaps this is so for the legal Board of a California > corporation, but the GNSO is an adivsory policy body, and whould enjoiy > more flexibility. > > Amadeu > > > Gruss, tom (__) (OO)_____ (oo) /|\ A cow is not entirely full of | |--/ | * milk some of it is hamburger! w w w w
|