[7830] in Kerberos
CFV: comp.security.gss-api
daemon@ATHENA.MIT.EDU (Mark James)
Wed Aug 21 22:36:09 1996
To: kerberos@MIT.EDU
Date: 22 Aug 1996 02:22:07 -0000
From: jamesm@dialogic.com (Mark James)
Reply-To: jamesm@dialogic.com
FIRST CALL FOR VOTES (of 2)
unmoderated group comp.security.gss-api
Newsgroup line:
comp.security.gss-api Generic Security Service Application Program Interface.
Votes must be received by 23:59:59 UTC, 12 Sep 1996.
This vote is being conducted by a neutral third party. Questions
about the proposed group should be directed to the proponent.
Proponent: Jonathan Kamens <jik@cam.ov.com>
Votetaker: Mark James <jamesm@dialogic.com>
RATIONALE: comp.security.gss-api
Use of the GSS-API and recognition of its status as an emerging
standard are growing. However, the only forum currently devoted to
discussion of the GSS-API is the cat-ietf@MIT.Edu mailing list. This
topic merits a newsgroup in addition to the mailing list for a number
of reasons, including:
* The mailing list's charter is oriented towards the standards
process, rather than towards discussion among users and implementors
of GSS-API. Furthermore, the mailing list's traffic does not
exclusively concern GSS-API. It will be useful to have a forum
whose traffic concerns only the GSS-API, and whose charter is
oriented towards discussion among users and implementors.
* Many people consider newsgroups preferable to mailing lists.
* The traffic on the mailing list is sufficient to justify the
creation of a newsgroup.
* A recent week-long straw poll of whether people want such a
newsgroup found almost 30 parties who were interested enough to
respond to the survey.
* The newsgroup will serve as a forum for people to ask questions
about and discuss the usage of the API without getting involved in
the high-level design discussions which are prevalent on the mailing
list. This is already needed since questions about the API are
already turning up in other newsgroups, and it will become more and
more useful as usage of the API becomes more widespread.
The last item above is not meant to imply that high-level discussions
of the API will be inappropriate in the newsgroup. However, although
they will certainly be considered on-topic in the group, it seems
likely that (a) a much larger proportion of the articles in the group
than on the mailing list will be concerned with basic discussion of,
and questions about, the API, and (b) people who are genuinely
interested in discussing and helping with future design of the API
will continue to do so primarily on the mailing list, since it is the
"official" mailing list of the IETF working group responsible for the
GSS-API.
CHARTER: comp.security.gss-api
The comp.security.gss-api newsgroup is intended for discussion of the
Generic Security Service Application Program Interface (GSS-API),
including mechanism- and implementation-independent discussion of the
GSS-API, discussion of specific GSS-API mechanisms and
implementations, and questions about the design and usage of the
GSS-API.
Discussion about underlying authentication technologies which is not
specifically related to the use of those technologies with the GSS-API
should take place in other newsgroups.
END CHARTER.
HOW TO VOTE:
Send an E-mail message to: jamesm@dialogic.com
Just hitting "Reply" to this CFV might work (but check the "To:"
address). Do not hit "Follow-up", since votes posted to any
newsgroup will not count.
The message should contain one and only one of the following:
I vote YES on comp.security.gss-api
I vote NO on comp.security.gss-api
I ABSTAIN on comp.security.gss-api
I CANCEL my vote on comp.security.gss-api
You must specify the name of the newsgroup, because the vote robot
may be running more than one vote.
VOTING PROCEDURAL NOTES:
You should receive an E-mail acknowledgment within a day or so of
your vote. If you do not, or if the vote robot does not correctly
record your vote, vote again. If you change your mind, vote again.
You may vote as many times as you wish; only your last vote will be
counted. Any problems should be brought to the vote-taker's
attention at the address listed above. It is your responsibility
to ensure that your vote is recorded correctly.
Neither ABSTAIN nor CANCEL messages are counted; they serve only to
cancel previous votes. An abstention is recorded in the final vote
list. A cancellation removes the voter from that list.
Standard voting rules apply: no more than one vote per person (no
matter how many accounts you have), and no more than one vote per
account. Votes must be mailed directly from the voter to the
votetaker. Anonymous, forwarded or proxy votes are not valid. Votes
mailed by robots or WWW/HTML/CGI scripts or forms are not valid.
The purpose of a Usenet vote is to determine the genuine interest of
persons who would read a proposed newsgroup. Soliciting votes from
disinterested parties defeats this purpose. Please do not distribute
this CFV. If you must, direct people to the official CFV as posted
to news.announce.newgroups. Distributing pre-marked or otherwise
edited copies of this CFV is generally considered to be vote fraud.
When in doubt, ask the votetaker.
The result of the vote will be posted shortly after the end of the
voting period. There will then be a five-day period when any errors
or irregularities should be brought up. In order for the new
newsgroup to be created, there must be at least 100 more YES votes
than NO votes, and at least twice as many YES votes as NO votes.
Note that the result of the vote will include a complete list of
voters and how they voted. This is not a secret ballot.
DISTRIBUTION:
This CFV and the eventual RESULT post will appear in the following
newsgroups:
news.announce.newgroups, news.groups, comp.protocols.kerberos,
comp.security.misc, comp.soft-sys.dce
It will also appear in the following mailing lists:
IETF Common Authentication Technology working group
<cat-ietf@mit.edu>
Secure Socket Layer <ssl-talk@netscape.com>
--
Mark James <jamesm@dialogic.com>
