[LAC-TF] implicaciones de declarar IPv4 historico

Arturo Servin arturo.servin at gmail.com
Sun Mar 20 14:44:25 BRT 2016


Del 2 al 6 tiene implicaciones bastante importantes que no creo que sea
posible llevarlas a cabo.

.as

On Sat, 19 Mar 2016 at 02:04 JORDI PALET MARTINEZ <
jordi.palet at consulintel.es> wrote:

> (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]
>    "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION" which defines A and
>    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-
>    ietf-sunset4-gapanalysis].
>
>    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
>    "IPv6."
>
> 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.
>
> Saludos,
> Jordi
>
>
>
>
>
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.lacnic.net/pipermail/lactf/attachments/20160320/91417cfd/attachment.html>


More information about the LACTF mailing list