[LAC-TF] implicaciones de declarar IPv4 historico

JORDI PALET MARTINEZ jordi.palet at consulintel.es
Sat Mar 19 06:04:07 BRT 2016

(respondiendo a Nico)

Como es muy corto, lo pego directamente en ingles:

2.  Implications

   Moving an Internet Standard to the Historic maturity level does not
   mean that it cannot be used.  It does mean that any Standards Track
   RFC with a Normative reference to RFC791 is Historic.  This is
   appropriate: any RFC defining IPv4 options is Historic.

   In addition, some RFCs that refer to RFC791, such as [RFC1035]
   IN-ADDR.ARPA, will be Updated By this document, but are not Historic.
   Other documents with incidental references to RFC791 should not be
   affected.  Documents requiring updates are appropriate for [draft-

   The IETF does not update Historic RFCs.  Therefore, the IETF will no
   longer work on IPv4 technologies, including transition technologies.

   The term "IP," without address family specified, is assumed to mean

3.  Security Considerations

   It is possible that bugs inherent to IPv4 will yet be discovered.
   Being Historic, the IETF will not further update IPv4.  Therefore,
   for security reasons, the use of IPv6 exclusively is recommended.

Es decir, en resumen:
1) No significa que IPv4 no pueda ser usado.
2) Significa que los otros estándares con referencias normativas a la especificación original de IPv4 (es decir aquellos que definen “opciones”), tambien históricos, excepto algunos referidos a DNS u otras cuestiones con referencias incidentales a IPv4.
3) El IETF ya no trabajara en actualizaciones de los RFC declarados históricos.
4) El termino IP, sin referencia a la familia de direcciones, implicara IPv6 (en lugar de IPv4 como se sobreentiende ahora).
5) Si se descubren problemas de seguridad en IPv4, el IETF no trabajara en ellos.


More information about the LACTF mailing list