Opened 15 years ago
Last modified 15 years ago
#106 new enhancement
XBATCH documentation
Reported by: | Julien ÉLIE | Owned by: | eagle |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | doc | Version: | |
Severity: | wishlist | Keywords: | compliance |
Cc: |
Description
XBATCH should probably be documented in an Informational Internet-Draft.
Note: See
TracTickets for help on using
tickets.
According to Russ Allbery in an IETF-NNTP posting:
Compressed feeds in general require something that replaces the current data conveyance method so that you can convey arbitrary binary data over NNTP. The problem with the existing NNTP protocol for binary data is that the data MUST end in CRLF, which is considered part of the data. We need some way of avoiding that, or some set of commands that say that the first CRLF of CRLF.CRLF isn't part of the data.
XBATCH is worth documenting. I don't know if it's worth standardizing as BATCH, but I wouldn't mind at all. Most of the work there will be defining the batch format, and that will depend on how many different transforms people feel like writing up (c7unbatch, cunbatch, gunbatch, etc.).
In practice, there are five interesting batch formats: straight rnews, the binary compressed formats for compress, gzip, and bzip2 (cunbatch, gunbatch, and bunbatch respectively), and c7unbatch, which is cunbatch with a transport encoding that I'm not sure anything else uses
All of them except c7unbatch are fairly easy to document. c7unbatch we might be able to get away with just declaring obsolete.