Plantilla:Cita IETF

De Wikipedia, la enciclopedia libre

Referencia vacía (ayuda) .

Icono de documentación de plantilla Documentación de la plantilla[ver] [editar] [historial] [purgar]
La documentación de esta plantilla no está traducida o es una traducción defectuosa o incompleta.
Si quieres colaborar, busca el texto original y mejora o finaliza esta traducción. Mientras tanto, no elimines este aviso.


Esta es una plantilla para citar documentos de la IETF[1]​[2]​ incluyendo:

Uso

Nota: Los nombres de los parámetros deben estar en minúsculas.

  • |appendix= – Número de apéndice. |appendix=A.1 produce "sec. A.1" También se utiliza para crear un enlace de anclaje para la URL del documento.
  • |autolink= – |autolink=sí or |autolink=no Genere automáticamente un enlace a ietf.org para los documentos especificados con|rfc=, |std=, |bcp=, |fyi=, |draft=, |ien=, o |rtr=. (habilitado por defecto)
  • |bcp= – Número de documento Best Current Practice (BCP). También se utiliza para generar automáticamente un enlace a ietf.org.
  • |draft= – Nombre del documento Internet Draft (I-D), incluido el borrador principal. También se utiliza para generar automáticamente un enlace a ietf.org.
  • |fyi= – Número de documento For Your Information (FYI). También se utiliza para generar automáticamente un enlace a ietf.org.
  • |idanchor= – Enlace de destino de destino. Por defecto, no se genera ningún enlace de anclaje. El valor especial |idanchor=ietf genera un enlace de anclaje adecuado para usar con el parámetro ref de esta plantilla. Requiere uno de id, rfc, std, bcp, fyi, draft Los campos ien o rtr estarán presentes en el texto del enlace de anclaje.
  • |idlink= – Ancla del documento interno o título de un artículo de Wikipedia para vincular a través del identificador del documento. El artículo ya debería existir. No debe estar enlazado a si mismo. Úsese junto con id, rfc, std, bcp, fyi , draft, ien o rtr.
  • |idlinktype= –Uno de los valores: id, rfc, std, bcp, fyi, draft, ien o rtr se puede asignar a idlinktype para forzar a la plantilla a usar el identificador de documento especificado como el texto del enlace para idanchor o idlink. Úsese junto con idanchor o idlink e id, rfc, std , bcp, fyi, draft, ien or rtr.
  • |ien= – Number of the Internet Experiment Note (IEN) document. Also used to automatically generate a link to ietf.org.
  • |nosec= – Using section, 'sections, or appendix automatically places the sec. notation. Se |nosec=y to hide the sec. notation.
  • |referenceid= – Reference id for the document. Used to create an anchor link for the document's URL.
  • |rfc= – Number of the Request for Comments (RFC) document. Also used to automatically generate a link to ietf.org.
  • |rtr= – Number of the RARE Technical Reports (RTR) document. Also used to automatically generate a link to ietf.org.
  • |section= – Section number of the document. |section=4.3.1 produces "sec. 4.3.1" Also used to create an anchor link for the document's URL. Can also be used in combination with sections to link to the first section in the given section range.
  • |sections= – Section range of the document. |sections=4.3-4.7 produces "sec. 4.3-4.7"
  • |sectionname= – The section name or section title of the document, written in full; displays before title and enclosed in quotes.
  • |std= – Number of the Internet Standard (STD) document. Also used to automatically generate a link to ietf.org.

As with all cs1|2 templates, |title= is required. If omitted, the template will attempt to auto-generate a title using the first of rfc, std, bcp, fyi, draft, ien, rtr or id document identifier parameters, in that order.

Copy a blank version to use. Remember to use the "|" (pipe) character between each parameter. Please delete any unused parameters to avoid clutter in the edit window.

Full version (copy and paste text below and delete parameters you don't need)
{{cite IETF |title= |rfc= |std= |bcp= |fyi= |draft= |ien= |rtr= |sectionname= |section= |sections= |appendix= |referenceid= |page= |pages= |last1= |first1= |authorlink1= |last2= |first2= |authorlink2= |authormask= |editor1-last= |editor1-first= |editor1-link= |others= |date= |year= |orig-year= |publisher=[[Internet Engineering Task Force|IETF]] |location= |language= |format= |access-date= |url= |section-url= |page-url= |autolink= |id= |idanchor= |idlink= |idlinktype= |doi= |doi-broken-date= |issn= |archive-url= |archive-date= |quote= |nopp= |nosec= |ref= |lay-summary= |lay-date= |postscript= |last-author-amp= }}
Most commonly used parameters (use this and you won't have to delete as much)
{{cite IETF |title= |rfc= |sectionname= |section= |page= |last= |first= |author-link= |year= |publisher=[[Internet Engineering Task Force|IETF]] |access-date= |doi= }}
Example 1

{{cite IETF |title=The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force |rfc=4677 |fyi=17 |last1=Hoffman |first1=P. |authorlink1=Paul Hoffman (VPNC) |last2=Harris |first2=S. |date=September 2006 |publisher=[[Internet Engineering Task Force|IETF]] |access-date=October 20, 2009 |doi=10.17487/RFC4677}}

The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force, doi:10.17487/RFC4677, FYI 17. RFC 4677 .

Example 2 
{{cite IETF
| title = Telnet protocol specification
| rfc = 854
| std = 8
| sectionname = Are You There (AYT)
| page = 8
| last1 = Postel
| first1 = J.
| author-link1 = Jon Postel
| last2 = Reynolds
| first2 = J.
| author-link2 = Joyce K. Reynolds
| date = May 1983
| publisher = [[Internet Engineering Task Force|IETF]]
| access-date = October 20, 2009
| doi = 10.17487/RFC0854
}}

«Are You There (AYT)», Telnet protocol specification, p. 8, doi:10.17487/RFC0854, STD 8. RFC 854 .

Examples

  • {{cite IETF | title = JSON | rfc = 7159 | sectionname = IANA Considerations | section = 11 | author = T. Bray | authorlink = Tim Bray | date = March 2014 | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = November 26, 2017 | doi = 10.17487/RFC7159 }}
    → «IANA Considerations», JSON, sec. 11, doi:10.17487/RFC7159, RFC 7159 .
  • {{cite IETF | title = Hypertext Transfer Protocol -- HTTP/1.1 | rfc = 2616 | first1 = R. | last1 = Fielding | authorlink1 = Roy Fielding | first2 = J. | last2 = Gettys | authorlink2 = Jim Gettys | first3 = J. | last3 = Mogul | first4 = H. | last4 = Frystyk | authorlink4 = Henrik Frystyk Nielsen | first5 = L. | last5 = Masinter | first6 = P. | last6 = Leach | first7 = T. | last7 = Berners-Lee | authorlink7 = Tim Berners-Lee |date=June 1999 | publisher = [[Internet Engineering Task Force|IETF]] | doi = 10.17487/RFC2616 }}
    → Hypertext Transfer Protocol -- HTTP/1.1, doi:10.17487/RFC2616, RFC 2616 .
  • {{cite IETF | title = Domain names - concepts and facilities | rfc = 1034 | sectionname = Name space specifications and terminology | section = 3.1 | author = P. Mockapetris | authorlink = Paul Mockapetris |date=November 1987 | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = August 3, 2008 | doi = 10.17487/RFC1034 | quote = A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '. }}
    → «Name space specifications and terminology», Domain names - concepts and facilities, sec. 3.1, doi:10.17487/RFC1034, RFC 1034 .

Technical notes

Regression testing

Regression tests are available here:

Subtemplates

{{Cite IETF}} uses the following subtemplates:

URL generation

HTML versions of the IETF documents are created with the Rfcmarkup tool from Henrik Levkowetz.[10]​[11]​

Request for Comments (RFC), Best Current Practice (BCP), and Internet Draft (I-D) documents which have been processed by the Rfcmarkup tool are cached by https://tools.ietf.org/html/[12]​[13]​ and are linked via:

https://tools.ietf.org/html/rfc<document number>
https://tools.ietf.org/html/bcp<document number>
https://tools.ietf.org/html/draft-<draft name>

Internet Standard (STD) and For Your Information (FYI) documents are linked via the Rfcmarkup tool using the doc= parameter:

https://tools.ietf.org/rfcmarkup?doc=std<document number>
https://tools.ietf.org/rfcmarkup?doc=fyi<document number>

Internet Experiment Note (IEN) and RARE Technical Reports (RTR) documents are linked via the Rfcmarkup tool using the url= parameter and a path to the document:

https://tools.ietf.org/rfcmarkup?url=ftp://ftp.rfc-editor.org/in-notes/ien/ien<document number>.txt
https://tools.ietf.org/rfcmarkup?url=ftp://ftp.rfc-editor.org/in-notes/museum/RAREreports/rtr<document number>.txt

URL anchor generation

Anchors are generated for the URL using four parameters:

|section=number generates #section-<number>
|appendix=number generates #appendix-<number>
|referenceid=id generates #ref-<id>
|page=number generates #page-<number>

The template will give priority to the first of the parameters: |section=, |appendix=, |referenceid=, or |page= in this order and create an anchor using the first matching parameter.

References

  1. ↑ The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force, doi:10.17487/RFC4677, FYI 17. RFC 4677 .
  2. ↑ «Internet Documentation», A Primer On Internet and TCP/IP Tools, sec. 4, doi:10.17487/RFC1739, RFC 1739 .
  3. ↑ «Request for Comments (RFCs)», A Primer On Internet and TCP/IP Tools, pp. 36–38. sec. 4.1, doi:10.17487/RFC1739, RFC 1739 .
  4. ↑ The Internet Standards Process -- Revision 3, doi:10.17487/RFC2026, BCP 9. RFC 2026 .
  5. ↑ «Internet Standards», A Primer On Internet and TCP/IP Tools, pp. 38–39. sec. 4.2, doi:10.17487/RFC1739, RFC 1739 .
  6. ↑ Best Current Practices, doi:10.17487/RFC1818, BCP 1. RFC 1818 .
  7. ↑ F.Y.I. on F.Y.I.: Introduction to the F.Y.I. Notes, doi:10.17487/RFC1150, FYI 1. RFC 1150 .
  8. ↑ «For Your Information Documents», A Primer On Internet and TCP/IP Tools, p. 39. sec. 4.3, doi:10.17487/RFC1739, RFC 1739 .
  9. ↑ «RARE Technical Reports», A Primer On Internet and TCP/IP Tools, p. 40. sec. 4.4, doi:10.17487/RFC1739, RFC 1739 .
  10. ↑ Levkowetz, Henrik (March 7, 2017). «Rfcmarkup Tool». IETF. Consultado el November 26, 2017. 
  11. ↑ Levkowetz, Henrik (July 13, 2016). «rfcmarkup-1.121.tgz (29.7 KB)». IETF. Consultado el November 26, 2017. 
  12. ↑ «IETF Documents». IETF. Consultado el November 2, 2009. 
  13. ↑ «HTTP 404 handler for a directory of htmlized documents». IETF. October 14, 2009. Consultado el November 2, 2009. 

Further reading

Esta documentación está transcluida desde Plantilla:Cita IETF/doc.
Los editores pueden experimentar en la zona de pruebas (crear) y en los casos de prueba (crear) de la plantilla.
Por favor, añade las categorías en la subpágina de documentación. Subpáginas de esta plantilla.
Obtenido de «https://es.wikipedia.org/w/index.php?title=Plantilla:Cita_IETF&oldid=115947206»