1st RFD: comp.protocols.dns.std moderated (remove)

1st RFD: comp.protocols.dns.std moderated (remove)

Post by Alexander » Mon, 08 Feb 2010 03:05:42


REQUEST FOR DISCUSSION (RFD)
moderated group comp.protocols.dns.std

This is a formal Request for Discussion (RFD) to remove moderated
newsgroup comp.protocols.dns.std.

RATIONALE:

Probe posts to this group resulted in bounces.

< XXXX@XXXXX.COM > (expanded from
< XXXX@XXXXX.COM >): host webster.isc.org[2001:4f8:1:d::12]
said: 550 5.1.1 < XXXX@XXXXX.COM >: Recipient address
rejected: User unknown in local recipient table (in reply to RCPT TO
command)

NEWSGROUPS LINE:

comp.protocols.dns.std DNS standards activities, including IETF. (Moderated)

DISTRIBUTION:

news.announce.newgroups
news.groups.proposals
comp.protocols.dns.std
comp.protocols.misc

CHARTER OF COMP.PROTOCOLS.DNS.STD

Discussions of IETF and other DNS standards activities will take place
here. Internet drafts, comments and ruminations on internet drafts,
official IETF working group announcements (related to DNS working
groups such as DNSIND and DNSSEC) can be made here. This newsgroup
will be bidirectionally gatewayed to the < XXXX@XXXXX.COM >
mailing list. Traffic crossing over from the newsgroup to the mailing
list or vice versa will be moderated, as will all traffic on the
newsgroup itself. (The mailing list is unmoderated.) Moderation is
considered necessary to filter out SPAM and off-topic posts. (See
section entitled "CHARTER: all groups" for more information about
moderation policy.)

Gateway mailing list name: Name Droppers
Submission address: XXXX@XXXXX.COM
Request address: XXXX@XXXXX.COM
On moderation: the primary moderation mechanism will be a robot which
auto-approves posts if they do not appear to be SPAM and they are not
cross-posted to other groups in the same hierarchy. Articles which
fail the robot's filters will be sent to a human (Paul Vixie) for
handling. Paul Vixie will approve any article which seems to be
mostly on topic; he reserves the right to delete SPAM without
notifying the sender, and the right to suggest to an author that her
choice of newsgroups could profitably have been different, and the
right to pass through errors from the news system such as "more than
50% included text". No article will be rejected on the basis of its
flame content. Cross posted articles will probably be rejected with
an explaination to the author, since very few articles appropriate for
any of these groups will be appropriate for any other group. That
decision will be made on a case by case basis, and the robot will be
informed of newsgroup unions for which cross posting is acceptable so
that human intervention won't be required in that case in the future.

On naming: as a middle aged curmudgeon, your humble speaker feels it
his duty to stamp out incorrect nomenclature such as "TCP/IP". Most
of the network traffic that carries DNS information is UDP, a peer of
TCP in the great protocol stack in the sky. Naming the original
DNS-related newsgroup "comp.protocols.tcp-ip.domains" was an error,
one we propose to (a) not repeat in our selection of names for these
new groups, and (b) repair by deleting/renaming the c.p.t-i.d group to
"comp.protocols.dns.ops". It may or may not be an error to call a
group "comp.protocols.tcp-ip", and we are not making any proposals
that that group be renamed. It would be a huge and compound error to
call