[LACNIC/Seguridad] Nuevo IETF I-D: draft-gont-6man-ipv6-universal-extension-header-00.txt

[Fernando Gont]

Estimados,

FYI:
<http://www.ietf.org/internet-drafts/draft-gont-6man-ipv6-universal-extension-header-00.txt>

Este I-D fue escrito con pocas horas de sueño. -- lo que esta
garantizado es que hay algo horrible en algún lado: o en el RFC a
actualizar, o en el draft que acabamos de publicar. :-)

Comentarios serán bienvenidos.

Saludos,
Fernando




-------- Original Message --------
Subject: New Version Notification for
draft-gont-6man-ipv6-universal-extension-header-00.txt
Date: Thu, 30 Jan 2014 15:07:40 -0800
From: internet-drafts en ietf.org
To: Fernando Gont <fgont en si6networks.com>, "Fernando Gont"
<fgont en si6networks.com>, "Shucheng LIU (Will)" <liushucheng en huawei.com>,
Will (Shucheng) Liu <liushucheng en huawei.com>


A new version of I-D, draft-gont-6man-ipv6-universal-extension-header-00.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-gont-6man-ipv6-universal-extension-header
Revision:	00
Title:		IPv6 Universal Extension Header
Document date:	2014-01-31
Group:		Individual Submission
Pages:		6
URL:
http://www.ietf.org/internet-drafts/draft-gont-6man-ipv6-universal-extension-header-00.txt
Status:
https://datatracker.ietf.org/doc/draft-gont-6man-ipv6-universal-extension-header/
Htmlized:
http://tools.ietf.org/html/draft-gont-6man-ipv6-universal-extension-header-00


Abstract:
   This document analyzes a problem in the Uniform Format for IPv6
   Extension Headers specified in RFC 6564, which results in forwarding
   nodes and middle-boxes not being able to process an IPv6 Header Chain
   if it contains an unrecognized IPv6 Extension Header that follows the
   aforementioned Uniform Format.  Additionally, it specifies a new IPv6
   Extension Header - the Universal Extension Header - that overcomes
   the aforementioned problem, and enables the extensibility of IPv6
   without impairing middleboxes that need to process the entire IPv6
   Header Chain.  Finally, this document formally updates RFC 6564





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat