This is the
talk page for discussing improvements to the
Cite IETF template. |
|
![]() | This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
![]() | This template is one of several templates used to provide or request sources for articles. |
![]() | This template is a Citation Style 1 specific-source template based on {{ Citation/core}}. For centralised Citation Style 1 discussions, see Help talk:Citation Style 1. |
Could anyone give an estimate of the date this template is going live? I think I can use this template very much... —— Dandor iD ( talk) 12:03, 6 January 2010 (UTC)
Can the template be changed to point to https instead of http? I.e. https://tools.ietf.org/? -- 194.246.123.103 ( talk) 01:59, 8 May 2011 (UTC)
|Citation class=IETF document
means that the HTML class is set to two classes: 'IETF' and 'document'. The space should be removed or replaced. ---—
Gadget850 (Ed)
talk
01:22, 16 October 2011 (UTC)
Since the template is designed specifically for IETF-published documents, can we just always pass IETF to {{ citation/core}}? If not, we could at least default to that if the parameter is omitted. Superm401 - Talk 02:13, 17 March 2012 (UTC)
|publisher=
parameter breaks cases where this template is used for
shortened footnotes. I tried the same thing when I created this template and had to default it to being blank for this reason. There may yet be a better way to do this, but I never could figure out an easy way to make it work. If anyone happens to have any questions about the way this template was designed, try pinging me on my talk page since I can get notifications for those. --
Tothwolf (
talk)
07:10, 14 May 2014 (UTC){{
csdoc|date}}
and {{
csdoc|url}}
.
[1]
[2] --
Tothwolf (
talk)
09:08, 14 May 2014 (UTC)|ref=ietf
and |idlink=ietf
. And most of the |publisher=
-less invocations on the regression tests page don't seem to fit the description on
WP:SFN? —
SamB (
talk)
17:29, 4 June 2014 (UTC)
Parameter issues:
---— Gadget850 (Ed) talk 16:49, 29 July 2012 (UTC)
The following code:
{{cite IETF
| title = Title
| rfc = 1234
| sectionname = Section name
| section = 1
| last = Blogs
| first = Joe
| editor-last = Blags
| editor-first = Joan
| month = January
| year = 1970
}}
Generates the following result:
{{
citation}}
: Unknown parameter |month=
ignored (
help)Note the editor name isn't marked as such, and appears in the wrong place compared with usage without a section link. I think it should look more like this:
Usage without a section name shows up sensibly:
{{
citation}}
: Unknown parameter |month=
ignored (
help)As does without any editors:
{{
citation}}
: Unknown parameter |month=
ignored (
help)I attempted to fix this myself, but took one look at the template markup and ran away.
Help?
— me_ and 20:58, 4 April 2013 (UTC)
The "csdoc" Citation Style 1 documentation subtemplates that were being used by this template's documentation will be updated next week to remove all of the descriptions of how non-Lua templates are rendered. This template does not use the CS1 Lua module, so the documentation it transcluded (until a few minutes ago) would have become even more inaccurate than it already was. Because of this, I have substed all of the current documentation subtemplates into this template's documentation page.
In slightly less technical terms, this citation template uses {{ citation/core}} to render citations, but other Citation Style 1 citations that used citation/core, like {{ cite book}}, have been migrated to use a Lua module. The module has features and changes that have been updated over the past two years and that do not apply, and never have applied, to this template.
Someone may want to check the documentation for this template against its actual function and adjust the documentation accordingly. I believe that it is not accurate. You can visit Help talk:Citation Style 1 or respond here if you have any questions. I will watch this page for a while. – Jonesey95 ( talk) 14:18, 12 April 2015 (UTC)
archive-url
or dead-url
don't exist, though archiveurl
does.
80.221.159.67 (
talk)
11:31, 28 August 2016 (UTC) (edited: 11:33, 28 August 2016 (UTC))Documentation says "for multiple authors, use author-link1", but this parameter format doesn't work. Either the template code or the documentation needs to be changed. Nurg ( talk) 02:11, 15 May 2018 (UTC)
The current live version of {{
cite IETF}}
relies on {{
citation/core}}
which is obsolete and not actively maintained.
There is a new sandbox version of this template that uses
Module:Template wrapper to feed parameters to
Module:Citation/CS1 as if this template were {{
citation}}
. Doing this allows {{cite IETF}}
to support all of the parameters that {{citation}}
supports and renders this template in a manner that is consistent with the rest of the cs1|2 family of templates – the sandbox set |mode=cs1
so that the rendering is in the same format as {{cite IETF}}
.
There is an extensive
testcases page. I have modified that page to use {{
test case}}
which compares the output from the live template to the output of the sandbox template. When the two outputs are the same, {{test case}}
produces a collapsed box with a green header; when not the same, an uncollapsed box with a yellow header. At the time of this writing, all of the boxes in the testcases page have yellow headers because Module:Citation/CS1 and {{citation/core}}
create different html. For example, testcase #1 is this:
{{Cite IETF|title=The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force}}
'"`UNIQ--templatestyles-0000001E-QINU`"'<cite class="citation cs1">''The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force''.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=The+Tao+of+IETF%3A+A+Novice%27s+Guide+to+the+Internet+Engineering+Task+Force&rfr_id=info%3Asid%2Fen.wikipedia.org%3ATemplate+talk%3ACite+IETF" class="Z3988"></span>
'"`UNIQ--templatestyles-00000020-QINU`"'<cite class="citation cs1">''The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force''.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=The+Tao+of+IETF%3A+A+Novice%27s+Guide+to+the+Internet+Engineering+Task+Force&rfr_id=info%3Asid%2Fen.wikipedia.org%3ATemplate+talk%3ACite+IETF" class="Z3988"></span>
Some things that 'work' in the live template do not work in the sandbox version. These things are listed below by testcase number:
|url=
) from |rfc=
. In the live version, that url is applied to |sectionname=
. cs1|2 constrains |url=
to apply only to |title=
but, because there is no title, there is a missing title error. Applying a title corrects the problem (see testcase 15)|url=
to apply only to |title=
, in the sandbox version, |sectionname=
is not linked by the url created from |rfc=
but |title=
is; this is correct because a url to the whole document belongs to the title of the whole document, not to a section of that document{{Cite IETF/sandbox|accessdate=November 7, 2009|format=PDF|page=3|pages=3 – 5|rfc=2026|section=1.2|sectionname=The Internet Standards Process|title=The Internet Standards Process -- Revision 3|url=http://www.faqs.org/ftp/rfc/pdf/rfc2026.txt.pdf |_debug=yes}}
{{citation}}
:
{{citation/new |accessdate=November 7, 2009 |at=pp. 3 – 5. sec. 1.2 |doi-access=free |doi=10.17487/RFC2026 |format=PDF |id=[[Request for Comments|RFC]] [https://datatracker.ietf.org/doc/html/rfc2026 2026] |mode=cs1 |section-url=http://www.faqs.org/ftp/rfc/pdf/rfc2026.txt.pdf#section-1.2 |section=The Internet Standards Process |title=The Internet Standards Process -- Revision 3 |url=http://www.faqs.org/ftp/rfc/pdf/rfc2026.txt.pdf}}
{{citation}}
template renders this way:
{{cite IETF/sandbox}}
template:
I have to noodle-out testcase 52. Once I've done that, I propose to update the live template with the code in the sandbox. Comments? Objections?
— Trappist the monk ( talk) 14:16, 8 March 2019 (UTC)
{{
cite IETF/sandbox}}
builds the section url fragment with the numeric entity #
in stead of with a #
character. It does this because the #
character is reserved to MediaWiki for ordered list markup.
Module:Citation/CS1 is looking for a #
character fragment delimiter when it test urls to see if it should set an internal version of |section-format=
to PDF. The fix for this is likely not here be at Module:Citation/CS1. I have made that change to
Module:Citation/CS1/sandbox.{{
citation/core}}
does not have support for internal creation of any of the various format parameters supported by the Lua module suite.There having been no objections, updated.
— Trappist the monk ( talk) 10:54, 15 March 2019 (UTC)
The following
{{cite IETF | title = Title | rfc = 1234 | sectionname = Section name | last = Blogs | first = Joe | editor-last = Blags | editor-first = Joan | year = 1970}}
gives
This is very weird. It should give something much closer to
or, if the automatic DOI/URL are desired
i.e. RFC 1234 should be
RFC
1234
Headbomb {
t ·
c ·
p ·
b}
21:39, 7 December 2019 (UTC)
{{
cite ietf|rfc = 5068|title = Email Submission Operations: Access and Accountability Requirements|section = 5|author1=C. Hutzler|author2=D. Crocker|author3=P. Resnick|author4=E. Allman|date=November 2007|work=Best Current Practice|publisher=
IETF|quote=This document does not provide recommendations on specific security implementations. It simply provides a warning that transmitting user credentials in clear text over insecure networks SHOULD be avoided in all scenarios as this could allow attackers to listen for this traffic and steal account data. In these cases, it is strongly suggested that an appropriate security technology MUST be used.|accessdate=24 August 2011}}
works normally.
But {{
cite ietf|rfc = 5068|title = Email Submission Operations: Access and Accountability Requirements|section = 5|sectionname = Message Submission Authentication/Authorization Technologies|author1=C. Hutzler|author2=D. Crocker|author3=P. Resnick|author4=E. Allman|publisher=
IETF|quote=This document does not provide recommendations on specific security implementations. It simply provides a warning that transmitting user credentials in clear text over insecure networks SHOULD be avoided in all scenarios as this could allow attackers to listen for this traffic and steal account data. In these cases, it is strongly suggested that an appropriate security technology MUST be used.|accessdate=4 August 2011}}
gets the error message |section= ignored
What I would like is the section number and name displayed, with a link to the section URL; I don't see a section-url parameter in the documentation. Shmuel (Seymour J.) Metz Username:Chatul ( talk) 23:15, 22 May 2020 (UTC)
{{cite ietf |rfc=5068| title = Email Submission Operations: Access and Accountability Requirements |section=5 |work=Best Current Practice |publisher=IETF}}
{{cite ietf |rfc=5068| title = Email Submission Operations: Access and Accountability Requirements |section=5 |sectionname=Message Submission Authentication/Authorization Technologies |work=Best Current Practice |publisher=IETF}}
{{
citation}}
: |section=
ignored (
help){{
cite ietf}}
is a wrapper template around {{
citation}}
. That template uses |work=
and its aliases as a trigger to shift from 'book' mode to 'periodical' mode. |section=
is an alias of |chapter=
neither of which is supported by {{citation}}
when it is in 'periodical' mode.{{cite ietf |rfc=5068| title = Email Submission Operations: Access and Accountability Requirements |section=5 |sectionname=Message Submission Authentication/Authorization Technologies |publisher=IETF}}
|section-url=
but it has been too long since I have had anything to do with this template so I no longer remember what it does and I am occupied with other things at the moment. You might look in
Template:cite ietf/testcases to see if one of those illustrates the parameter's use. If you can discover how it is used, please write a bit of documentation so that others won't have to do the same.<nowiki>{{foo|bar}}</nowiki>
instead of {{tlx|foo|bar}}
when describing issues with {{
foo}} or are you referring to the substitution of {{=}}
for =
?{{cite IETF
| rfc = 6609
| std = 72
| title = Message Submission for Mail
}}
seems to work; is it valid?<nowiki>...</nowiki>
tags wrapping templates to be discussed as you did for question #3. The first thing I did after reading your initial post was to copy your two examples from the rendered page so that I could see what you were seeing. That did not work. I did not see an error message. If you look at your second example you will see this:
|author4{{=}}E. Allman |author5= T. Finch |date=November 2007 |work=Best Current Practice |publisher{{=}}[[IETF]]
{{
tlx}}
, |author5=
, |date=
, |work=
are {{tlx}}
parameters. Those parameter names are not supported by {{tlx}}
so are ignored. To see what you were seeing, I had to rewrite your examples.{{
cite ietf}}
is a wrapper template around {{
citation}}
which is rendered by
Module:Citation/CS1. The module knows only that it is rendering a {{citation}}
template and that you are asking it to render something that it cannot. It cannot know from a handful of parameters which of them you really mean to use so I made the arbitrary choice of using the same error detection and reporting scheme that is used for the cs1 templates that do not support |chapter=
and its aliases; that way only one error detection and reporting mechanism is required for similar problems.{{
citation/core}}
.|work=
is not documented here because it was not part of the original template but is available as a {{citation}}
parameter (all {{citation}}
parameters are available for use). I see no reason to document it. Another, I think more likely, reason for |section-url=
is to link |sectionname=
to someplace other than the IETF website's copy – a mirror perhaps, for this example, //example.com
:
{{cite ietf |rfc=5068| title = Email Submission Operations: Access and Accountability Requirements |section=5 |sectionname=Message Submission Authentication/Authorization Technologies |section-url=//example.com |publisher=IETF}}
RFCs never change. If an IETF specification has to be changed, a new RFC with a new number is published, which updates or deprecates the old RFC. So there is little point in adding "Retrieved on <date>" when citing an RFC.
Maybe this should be removed from the examples? Or, if it is desirable for reasons of consistency, maybe a short note about that should be added? -- Ehlo127001 ( talk) 15:29, 4 July 2021 (UTC)
I'm not in the mood to fix this now. When |doi=
is present but empty, and when |rfc=
has a value, this template sets |doi-access=free
. Compare:
{{cite IETF |title=Specification of Internet Transmission Control Protocol|rfc=675|sectionname= |section= |page= |last1=Cerf |first1=Vinton|last2=Dalal|first2=Yogen|last3=Sunshine|first3=Carl|date=December 1974 |publisher=[[Internet Engineering Task Force|IETF]] |access-date= |doi=}}
{{cite IETF |title=Specification of Internet Transmission Control Protocol|rfc=675|sectionname= |section= |page= |last1=Cerf |first1=Vinton|last2=Dalal|first2=Yogen|last3=Sunshine|first3=Carl|date=December 1974 |publisher=[[Internet Engineering Task Force|IETF]] |access-date=}}
— Trappist the monk ( talk) 11:55, 24 August 2021 (UTC)
The https://tools.ietf.org/html/rfcXXX
now redirects to https://datatracker.ietf.org/doc/html/rfcXXX
. For example
https://tools.ietf.org/html/rfc114 redirects to
https://datatracker.ietf.org/doc/html/rfc114. The
Template:IETF RFC was updated already accordingly. Thanks.
Prikryl (
talk)
09:53, 18 May 2023 (UTC)
Some comment on this datatracker url and difference in visualization:
It would not matter much if the way to go from the non-timeline version to the one showing the timeline was more clear. I had to Ctrl+F in the page source code to find, it's the blue datatracker button at the top of the sidepanel. And to go from the timeline version to the non-timeline version is more straightforward, it's the "htmlized" blue button.
Maybe it's a matter of personal preference, but I prefer the timeline version. — Arthurfragoso ( talk) 14:03, 2 August 2023 (UTC)
html/
" from the code line #13 ( |datatracker.ietf.org/doc/html/rfc{{{Rfc}}}
) and publish.html/
" inside <!-- -->
( |datatracker.ietf.org/doc/<!-- html/ -->rfc{{{Rfc}}}
) might work too, but I'm not sure.
Nishimoto, Gilberto Kiyoshi (
talk)
19:54, 3 August 2023 (UTC)and also a compare function in the History tabA compare function is also available in the sidebar in the https://datatracker.ietf.org/doc/html/rfc4677/ view. You don't get the timeline, or the tabs, however. Guy Harris ( talk) 21:23, 3 August 2023 (UTC)
This is the
talk page for discussing improvements to the
Cite IETF template. |
|
![]() | This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
![]() | This template is one of several templates used to provide or request sources for articles. |
![]() | This template is a Citation Style 1 specific-source template based on {{ Citation/core}}. For centralised Citation Style 1 discussions, see Help talk:Citation Style 1. |
Could anyone give an estimate of the date this template is going live? I think I can use this template very much... —— Dandor iD ( talk) 12:03, 6 January 2010 (UTC)
Can the template be changed to point to https instead of http? I.e. https://tools.ietf.org/? -- 194.246.123.103 ( talk) 01:59, 8 May 2011 (UTC)
|Citation class=IETF document
means that the HTML class is set to two classes: 'IETF' and 'document'. The space should be removed or replaced. ---—
Gadget850 (Ed)
talk
01:22, 16 October 2011 (UTC)
Since the template is designed specifically for IETF-published documents, can we just always pass IETF to {{ citation/core}}? If not, we could at least default to that if the parameter is omitted. Superm401 - Talk 02:13, 17 March 2012 (UTC)
|publisher=
parameter breaks cases where this template is used for
shortened footnotes. I tried the same thing when I created this template and had to default it to being blank for this reason. There may yet be a better way to do this, but I never could figure out an easy way to make it work. If anyone happens to have any questions about the way this template was designed, try pinging me on my talk page since I can get notifications for those. --
Tothwolf (
talk)
07:10, 14 May 2014 (UTC){{
csdoc|date}}
and {{
csdoc|url}}
.
[1]
[2] --
Tothwolf (
talk)
09:08, 14 May 2014 (UTC)|ref=ietf
and |idlink=ietf
. And most of the |publisher=
-less invocations on the regression tests page don't seem to fit the description on
WP:SFN? —
SamB (
talk)
17:29, 4 June 2014 (UTC)
Parameter issues:
---— Gadget850 (Ed) talk 16:49, 29 July 2012 (UTC)
The following code:
{{cite IETF
| title = Title
| rfc = 1234
| sectionname = Section name
| section = 1
| last = Blogs
| first = Joe
| editor-last = Blags
| editor-first = Joan
| month = January
| year = 1970
}}
Generates the following result:
{{
citation}}
: Unknown parameter |month=
ignored (
help)Note the editor name isn't marked as such, and appears in the wrong place compared with usage without a section link. I think it should look more like this:
Usage without a section name shows up sensibly:
{{
citation}}
: Unknown parameter |month=
ignored (
help)As does without any editors:
{{
citation}}
: Unknown parameter |month=
ignored (
help)I attempted to fix this myself, but took one look at the template markup and ran away.
Help?
— me_ and 20:58, 4 April 2013 (UTC)
The "csdoc" Citation Style 1 documentation subtemplates that were being used by this template's documentation will be updated next week to remove all of the descriptions of how non-Lua templates are rendered. This template does not use the CS1 Lua module, so the documentation it transcluded (until a few minutes ago) would have become even more inaccurate than it already was. Because of this, I have substed all of the current documentation subtemplates into this template's documentation page.
In slightly less technical terms, this citation template uses {{ citation/core}} to render citations, but other Citation Style 1 citations that used citation/core, like {{ cite book}}, have been migrated to use a Lua module. The module has features and changes that have been updated over the past two years and that do not apply, and never have applied, to this template.
Someone may want to check the documentation for this template against its actual function and adjust the documentation accordingly. I believe that it is not accurate. You can visit Help talk:Citation Style 1 or respond here if you have any questions. I will watch this page for a while. – Jonesey95 ( talk) 14:18, 12 April 2015 (UTC)
archive-url
or dead-url
don't exist, though archiveurl
does.
80.221.159.67 (
talk)
11:31, 28 August 2016 (UTC) (edited: 11:33, 28 August 2016 (UTC))Documentation says "for multiple authors, use author-link1", but this parameter format doesn't work. Either the template code or the documentation needs to be changed. Nurg ( talk) 02:11, 15 May 2018 (UTC)
The current live version of {{
cite IETF}}
relies on {{
citation/core}}
which is obsolete and not actively maintained.
There is a new sandbox version of this template that uses
Module:Template wrapper to feed parameters to
Module:Citation/CS1 as if this template were {{
citation}}
. Doing this allows {{cite IETF}}
to support all of the parameters that {{citation}}
supports and renders this template in a manner that is consistent with the rest of the cs1|2 family of templates – the sandbox set |mode=cs1
so that the rendering is in the same format as {{cite IETF}}
.
There is an extensive
testcases page. I have modified that page to use {{
test case}}
which compares the output from the live template to the output of the sandbox template. When the two outputs are the same, {{test case}}
produces a collapsed box with a green header; when not the same, an uncollapsed box with a yellow header. At the time of this writing, all of the boxes in the testcases page have yellow headers because Module:Citation/CS1 and {{citation/core}}
create different html. For example, testcase #1 is this:
{{Cite IETF|title=The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force}}
'"`UNIQ--templatestyles-0000001E-QINU`"'<cite class="citation cs1">''The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force''.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=The+Tao+of+IETF%3A+A+Novice%27s+Guide+to+the+Internet+Engineering+Task+Force&rfr_id=info%3Asid%2Fen.wikipedia.org%3ATemplate+talk%3ACite+IETF" class="Z3988"></span>
'"`UNIQ--templatestyles-00000020-QINU`"'<cite class="citation cs1">''The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force''.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=The+Tao+of+IETF%3A+A+Novice%27s+Guide+to+the+Internet+Engineering+Task+Force&rfr_id=info%3Asid%2Fen.wikipedia.org%3ATemplate+talk%3ACite+IETF" class="Z3988"></span>
Some things that 'work' in the live template do not work in the sandbox version. These things are listed below by testcase number:
|url=
) from |rfc=
. In the live version, that url is applied to |sectionname=
. cs1|2 constrains |url=
to apply only to |title=
but, because there is no title, there is a missing title error. Applying a title corrects the problem (see testcase 15)|url=
to apply only to |title=
, in the sandbox version, |sectionname=
is not linked by the url created from |rfc=
but |title=
is; this is correct because a url to the whole document belongs to the title of the whole document, not to a section of that document{{Cite IETF/sandbox|accessdate=November 7, 2009|format=PDF|page=3|pages=3 – 5|rfc=2026|section=1.2|sectionname=The Internet Standards Process|title=The Internet Standards Process -- Revision 3|url=http://www.faqs.org/ftp/rfc/pdf/rfc2026.txt.pdf |_debug=yes}}
{{citation}}
:
{{citation/new |accessdate=November 7, 2009 |at=pp. 3 – 5. sec. 1.2 |doi-access=free |doi=10.17487/RFC2026 |format=PDF |id=[[Request for Comments|RFC]] [https://datatracker.ietf.org/doc/html/rfc2026 2026] |mode=cs1 |section-url=http://www.faqs.org/ftp/rfc/pdf/rfc2026.txt.pdf#section-1.2 |section=The Internet Standards Process |title=The Internet Standards Process -- Revision 3 |url=http://www.faqs.org/ftp/rfc/pdf/rfc2026.txt.pdf}}
{{citation}}
template renders this way:
{{cite IETF/sandbox}}
template:
I have to noodle-out testcase 52. Once I've done that, I propose to update the live template with the code in the sandbox. Comments? Objections?
— Trappist the monk ( talk) 14:16, 8 March 2019 (UTC)
{{
cite IETF/sandbox}}
builds the section url fragment with the numeric entity #
in stead of with a #
character. It does this because the #
character is reserved to MediaWiki for ordered list markup.
Module:Citation/CS1 is looking for a #
character fragment delimiter when it test urls to see if it should set an internal version of |section-format=
to PDF. The fix for this is likely not here be at Module:Citation/CS1. I have made that change to
Module:Citation/CS1/sandbox.{{
citation/core}}
does not have support for internal creation of any of the various format parameters supported by the Lua module suite.There having been no objections, updated.
— Trappist the monk ( talk) 10:54, 15 March 2019 (UTC)
The following
{{cite IETF | title = Title | rfc = 1234 | sectionname = Section name | last = Blogs | first = Joe | editor-last = Blags | editor-first = Joan | year = 1970}}
gives
This is very weird. It should give something much closer to
or, if the automatic DOI/URL are desired
i.e. RFC 1234 should be
RFC
1234
Headbomb {
t ·
c ·
p ·
b}
21:39, 7 December 2019 (UTC)
{{
cite ietf|rfc = 5068|title = Email Submission Operations: Access and Accountability Requirements|section = 5|author1=C. Hutzler|author2=D. Crocker|author3=P. Resnick|author4=E. Allman|date=November 2007|work=Best Current Practice|publisher=
IETF|quote=This document does not provide recommendations on specific security implementations. It simply provides a warning that transmitting user credentials in clear text over insecure networks SHOULD be avoided in all scenarios as this could allow attackers to listen for this traffic and steal account data. In these cases, it is strongly suggested that an appropriate security technology MUST be used.|accessdate=24 August 2011}}
works normally.
But {{
cite ietf|rfc = 5068|title = Email Submission Operations: Access and Accountability Requirements|section = 5|sectionname = Message Submission Authentication/Authorization Technologies|author1=C. Hutzler|author2=D. Crocker|author3=P. Resnick|author4=E. Allman|publisher=
IETF|quote=This document does not provide recommendations on specific security implementations. It simply provides a warning that transmitting user credentials in clear text over insecure networks SHOULD be avoided in all scenarios as this could allow attackers to listen for this traffic and steal account data. In these cases, it is strongly suggested that an appropriate security technology MUST be used.|accessdate=4 August 2011}}
gets the error message |section= ignored
What I would like is the section number and name displayed, with a link to the section URL; I don't see a section-url parameter in the documentation. Shmuel (Seymour J.) Metz Username:Chatul ( talk) 23:15, 22 May 2020 (UTC)
{{cite ietf |rfc=5068| title = Email Submission Operations: Access and Accountability Requirements |section=5 |work=Best Current Practice |publisher=IETF}}
{{cite ietf |rfc=5068| title = Email Submission Operations: Access and Accountability Requirements |section=5 |sectionname=Message Submission Authentication/Authorization Technologies |work=Best Current Practice |publisher=IETF}}
{{
citation}}
: |section=
ignored (
help){{
cite ietf}}
is a wrapper template around {{
citation}}
. That template uses |work=
and its aliases as a trigger to shift from 'book' mode to 'periodical' mode. |section=
is an alias of |chapter=
neither of which is supported by {{citation}}
when it is in 'periodical' mode.{{cite ietf |rfc=5068| title = Email Submission Operations: Access and Accountability Requirements |section=5 |sectionname=Message Submission Authentication/Authorization Technologies |publisher=IETF}}
|section-url=
but it has been too long since I have had anything to do with this template so I no longer remember what it does and I am occupied with other things at the moment. You might look in
Template:cite ietf/testcases to see if one of those illustrates the parameter's use. If you can discover how it is used, please write a bit of documentation so that others won't have to do the same.<nowiki>{{foo|bar}}</nowiki>
instead of {{tlx|foo|bar}}
when describing issues with {{
foo}} or are you referring to the substitution of {{=}}
for =
?{{cite IETF
| rfc = 6609
| std = 72
| title = Message Submission for Mail
}}
seems to work; is it valid?<nowiki>...</nowiki>
tags wrapping templates to be discussed as you did for question #3. The first thing I did after reading your initial post was to copy your two examples from the rendered page so that I could see what you were seeing. That did not work. I did not see an error message. If you look at your second example you will see this:
|author4{{=}}E. Allman |author5= T. Finch |date=November 2007 |work=Best Current Practice |publisher{{=}}[[IETF]]
{{
tlx}}
, |author5=
, |date=
, |work=
are {{tlx}}
parameters. Those parameter names are not supported by {{tlx}}
so are ignored. To see what you were seeing, I had to rewrite your examples.{{
cite ietf}}
is a wrapper template around {{
citation}}
which is rendered by
Module:Citation/CS1. The module knows only that it is rendering a {{citation}}
template and that you are asking it to render something that it cannot. It cannot know from a handful of parameters which of them you really mean to use so I made the arbitrary choice of using the same error detection and reporting scheme that is used for the cs1 templates that do not support |chapter=
and its aliases; that way only one error detection and reporting mechanism is required for similar problems.{{
citation/core}}
.|work=
is not documented here because it was not part of the original template but is available as a {{citation}}
parameter (all {{citation}}
parameters are available for use). I see no reason to document it. Another, I think more likely, reason for |section-url=
is to link |sectionname=
to someplace other than the IETF website's copy – a mirror perhaps, for this example, //example.com
:
{{cite ietf |rfc=5068| title = Email Submission Operations: Access and Accountability Requirements |section=5 |sectionname=Message Submission Authentication/Authorization Technologies |section-url=//example.com |publisher=IETF}}
RFCs never change. If an IETF specification has to be changed, a new RFC with a new number is published, which updates or deprecates the old RFC. So there is little point in adding "Retrieved on <date>" when citing an RFC.
Maybe this should be removed from the examples? Or, if it is desirable for reasons of consistency, maybe a short note about that should be added? -- Ehlo127001 ( talk) 15:29, 4 July 2021 (UTC)
I'm not in the mood to fix this now. When |doi=
is present but empty, and when |rfc=
has a value, this template sets |doi-access=free
. Compare:
{{cite IETF |title=Specification of Internet Transmission Control Protocol|rfc=675|sectionname= |section= |page= |last1=Cerf |first1=Vinton|last2=Dalal|first2=Yogen|last3=Sunshine|first3=Carl|date=December 1974 |publisher=[[Internet Engineering Task Force|IETF]] |access-date= |doi=}}
{{cite IETF |title=Specification of Internet Transmission Control Protocol|rfc=675|sectionname= |section= |page= |last1=Cerf |first1=Vinton|last2=Dalal|first2=Yogen|last3=Sunshine|first3=Carl|date=December 1974 |publisher=[[Internet Engineering Task Force|IETF]] |access-date=}}
— Trappist the monk ( talk) 11:55, 24 August 2021 (UTC)
The https://tools.ietf.org/html/rfcXXX
now redirects to https://datatracker.ietf.org/doc/html/rfcXXX
. For example
https://tools.ietf.org/html/rfc114 redirects to
https://datatracker.ietf.org/doc/html/rfc114. The
Template:IETF RFC was updated already accordingly. Thanks.
Prikryl (
talk)
09:53, 18 May 2023 (UTC)
Some comment on this datatracker url and difference in visualization:
It would not matter much if the way to go from the non-timeline version to the one showing the timeline was more clear. I had to Ctrl+F in the page source code to find, it's the blue datatracker button at the top of the sidepanel. And to go from the timeline version to the non-timeline version is more straightforward, it's the "htmlized" blue button.
Maybe it's a matter of personal preference, but I prefer the timeline version. — Arthurfragoso ( talk) 14:03, 2 August 2023 (UTC)
html/
" from the code line #13 ( |datatracker.ietf.org/doc/html/rfc{{{Rfc}}}
) and publish.html/
" inside <!-- -->
( |datatracker.ietf.org/doc/<!-- html/ -->rfc{{{Rfc}}}
) might work too, but I'm not sure.
Nishimoto, Gilberto Kiyoshi (
talk)
19:54, 3 August 2023 (UTC)and also a compare function in the History tabA compare function is also available in the sidebar in the https://datatracker.ietf.org/doc/html/rfc4677/ view. You don't get the timeline, or the tabs, however. Guy Harris ( talk) 21:23, 3 August 2023 (UTC)