* 6.12. Xref The Xref header content indicates where an article was filed by the last relayer to process it: Xref-content = relayer 1*( space location ) relayer = relayer-name location = newsgroup-name ":" article-locator article-locator = 1* The relayer's name is included so that software can deter- mine which relayer generated the header (and specifically, whether it really was the one that filed the copy being examined). The locations specify what newsgroups the arti- cle was filed under (which may differ from those in the Newsgroups header) and where it was filed under them. The exact form of an article locator is implementation-specific. NOTE: Reading agents can exploit this information to avoid presenting the same article to a reader several times. The information is sometimes available in system databases, but having it in the article is convenient. Relayers traditionally generate an Xref header only if the article is cross-posted, but this is not mandatory, and there is at least one new application ("mirroring": keeping news databases on two hosts identical) where the header is useful in all articles. NOTE: The traditional form of an article locator is a decimal number, with articles in each news- group numbered consecutively starting from 1. NNTP [rrr] demands that such a model be provided, and there may be other software which expects it, but it seems desirable to permit flexibility for unorthodox implementations. A relayer inserting an Xref header into an article MUST delete any previous Xref header. A relayer which is not inserting its own Xref header SHOULD delete any previous Xref header. A relayer MAY delete the Xref header when passing an article on to another relayer. Xref 頭を記事に挿入する中継者は前の Xref 頭を削除し''なければなりません''。 自分の Xref 頭を挿入しない中継者は前の Xref 頭を削除する''べき''です。 中継者は Xref 頭を他の中継者に渡す時に Xref 頭を削除しても ''構いません''。 NOTE: RFC 1036 specified that the Xref header was not transmitted when an article was passed to another relayer, but the major news implementa- tions have never obeyed this rule, and applica- tions like mirroring depend on this disobedience. 参考: RFC 1036 は Xref 頭は記事が他の中継者に渡される時に 転送されないとしていましたが、有名ニュース実装はこの規則に従わず、 鏡化(ミラーリング)のような応用はこの規格違反に依存してきました。 A relayer MUST use the same name in Xref headers as it uses in Path headers. Reading agents MUST ignore an Xref header containing a relayer name that differs from the one that begins the path list. 中継者は Xref 頭に Path 頭と同じ名前を使わ''なければなりません''。 読み代理者は経路表の最初の中継者名と異なる Xref 頭を無視し ''なければなりません''。 *SEE ALSO -[[RFC822と仲間達の頭領域名]] -[[電子ニュース]] --[[新聞組]] --[[RFC1036]] --[[son-of-RFC1036]] --[[draft-usefor-article]] *LICENSE See [[RFCのライセンス]]