Re: A problem with RFC 6465's Uniform Format for Extension Headers
Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 03 February 2014 21:43 UTC
Return-Path: <brian.e.carpenter@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 57C9B1A01EE for <ipv6@ietfa.amsl.com>; Mon, 3 Feb 2014 13:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 3-0od-se9S3X for <ipv6@ietfa.amsl.com>; Mon, 3 Feb 2014 13:43:43 -0800 (PST)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 012AF1A0232 for <6man@ietf.org>; Mon, 3 Feb 2014 13:43:42 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id un15so7525044pbc.24 for <6man@ietf.org>; Mon, 03 Feb 2014 13:43:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9o6VxIGIF/n/BRtfKI2whpTzUu0dKCm4/NcOwBC0W/Y=; b=JQ/9USF4Si9RrQwra8MU6rN69Hwf/Jw5ja5SKL19eHUWAvfXeCy+jmS2lRDWtK7DL7 LEWY8zyIKLfbSZw8dLDf2nicZpjaeVYIbRbeugvuvKyckAeYvVZ4rl84DeTnsRmTZ+B6 ysZHpStD12DPyhjAoBGivZndMU1vkV4+iLb6qNbRrh196iFSJetOnO6iuckilyPMjy8o VEosVfXuJwf/HvloCXS/KY8+UOFq2qFcd4xu0veqetIoUzNV7r+C4T0ND3x0M5zesnhm 3z/aiLWcFkkhU00AX3tPqZJumy0ILREiHl1/QBLfWe6UcAL/HVNy93NnPge9UbPxXJSc C3Gg==
X-Received: by 10.66.146.229 with SMTP id tf5mr40092115pab.50.1391463822991; Mon, 03 Feb 2014 13:43:42 -0800 (PST)
Received: from [130.216.38.108] (sc-cs-567-laptop.cs.auckland.ac.nz. [130.216.38.108]) by mx.google.com with ESMTPSA id rb6sm23599580pbb.41.2014.02.03.13.43.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 13:43:42 -0800 (PST)
Message-ID: <52F00D8C.8060501@gmail.com>
Date: Tue, 04 Feb 2014 10:43:40 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hagen Paul Pfeifer <hagen@jauu.net>
Subject: Re: A problem with RFC 6465's Uniform Format for Extension Headers
References: <20140130230740.25350.9524.idtracker@ietfa.amsl.com> <52EAF63A.7050108@si6networks.com> <20140203204716.GD1519@virgo.local>
In-Reply-To: <20140203204716.GD1519@virgo.local>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "C. M. Heard" <heard@pobox.com>, Fernando Gont <fgont@si6networks.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: Mon, 03 Feb 2014 21:43:44 -0000
On 04/02/2014 09:47, Hagen Paul Pfeifer wrote: > * Fernando Gont | 2014-01-30 22:02:50 [-0300]: > >> Folks, >> >> 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. :-) > > Hey Fernando, I realized that too and wrote an I-D (back in July 2011): > > http://tools.ietf.org/html/draft-pfeifer-6man-exthdr-res-01 > > Compared to your solution I propose to reserve a range. Either solution works, but the firewall implementors might have a preference one way or the other. RFC 7045 says "Therefore, it is important that forwarding nodes that inspect IPv6 headers be able to parse all defined extension headers and deal with them appropriately,..." So the question is whether they would find a reserved range or a subtype easier to parse. Brian
- 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