Re: A problem with RFC 6465's Uniform Format for Extension Headers
Jen Linkova <furry13@gmail.com> Tue, 04 February 2014 14:20 UTC
Return-Path: <furry13@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9C81A0211 for <ipv6@ietfa.amsl.com>; Tue, 4 Feb 2014 06:20:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oYdoFY_ALsyL for <ipv6@ietfa.amsl.com>; Tue, 4 Feb 2014 06:20:55 -0800 (PST)
Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 2999F1A00EC for <6man@ietf.org>; Tue, 4 Feb 2014 06:20:55 -0800 (PST)
Received: by mail-qc0-f175.google.com with SMTP id x13so13385719qcv.20 for <6man@ietf.org>; Tue, 04 Feb 2014 06:20:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=umOf7YHn6mRkzVpoEmq6wUTxlVpPzMOJVqwjSZ0ZCUY=; b=UxMPkTH1yuyIIQcytOgMVzWOjTBFanDdloZe6Hktdxpln8yrCWgNiExFwqzele0U9+ hXEyS69tXFDAMNxWF3bVrnTfnPag3uHgj/eyd5psWeh0O7StrOaENSy0U5vGY6oAdzHv gXXHsIFQrfJ4siBzgDGfmEtkJ2PpFsB778nzZLug/bMJ5T7A0M3Olvv58+RdWNev5oS4 f4y2PcX1lf2XqFyDSk8UGn3yY9WZI99jJ99bCLhcfSCGvv/QScx+DjvHVNaBFR6CM9Fd TdAb96op3O0hLRsISUK6Oj0o5siw2IjvNdoTJpXQ13TgsBITluItMj2DkPjOhqBZ/Bg9 w0uA==
X-Received: by 10.224.75.138 with SMTP id y10mr67230745qaj.72.1391523654679; Tue, 04 Feb 2014 06:20:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.40.197 with HTTP; Tue, 4 Feb 2014 06:20:34 -0800 (PST)
In-Reply-To: <52EAF63A.7050108@si6networks.com>
References: <20140130230740.25350.9524.idtracker@ietfa.amsl.com> <52EAF63A.7050108@si6networks.com>
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 04 Feb 2014 15:20:34 +0100
Message-ID: <CAFU7BATrYRsNJ7D4AJSy62XobNaGDgW-zTvX=yrqZea-Q67YPA@mail.gmail.com>
Subject: Re: A problem with RFC 6465's Uniform Format for Extension Headers
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "C. M. Heard" <heard@pobox.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 14:20:58 -0000
Hi Fernando, On Fri, Jan 31, 2014 at 2:02 AM, Fernando Gont <fgont@si6networks.com> wrote: > Mike Heard noted that the Uniform Format specified in RFC 6465 can't > possibly work.. and after giving some thought about it, it turns out > that implementing it would hamper the deployment of new transport protocols. > > We've written a short I-D that discussed the problem, and that proposes > an alternative, such that we achieve the same goal without possibly > messing with our Transport friends. :-) > > The I-D is available at: > <http://www.ietf.org/internet-drafts/draft-gont-6man-ipv6-universal-extension-header-00.txt> Somehow that proposed Universal Extension Header looks exactly like an Options Extension Header to me. Am I missing something? I'm trying to use my imagination but couldn't see any possible scenario when UEH would work and Options header would not. > -------- 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@ietf.org > To: Fernando Gont <fgont@si6networks.com>, "Fernando Gont" > <fgont@si6networks.com>, "Shucheng LIU (Will)" <liushucheng@huawei.com>, > Will (Shucheng) Liu <liushucheng@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 > > > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -- SY, Jen Linkova aka Furry
- A problem with RFC 6465's Uniform Format for Exte… Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Hagen Paul Pfeifer
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Hagen Paul Pfeifer
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Jen Linkova
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Suresh Krishnan
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Thomas Narten
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … brianjusa
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Randy Bush
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Randy Bush
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Karsten Thomann
- Re: A problem with RFC 6465's Uniform Format for … Hagen Paul Pfeifer
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Mark ZZZ Smith
- Re: A problem with RFC 6465's Uniform Format for … C. M. Heard
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … RJ Atkinson
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … RJ Atkinson
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: Re: A problem with RFC 6465's Uniform Format … Ray Hunter
- Re: A problem with RFC 6465's Uniform Format for … C. M. Heard
- Re: A problem with RFC 6465's Uniform Format for … Mark ZZZ Smith
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Dan Lüdtke
- Re: A problem with RFC 6465's Uniform Format for … Mark ZZZ Smith
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont