IETF Logo Mail Archive

Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard

Ole Troan <otroan@employees.org> Tue, 08 October 2013 17:35 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB79221E8271; Tue, 8 Oct 2013 10:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qi3qBnT55re9; Tue, 8 Oct 2013 10:35:29 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id 6B30D21E8213; Tue, 8 Oct 2013 10:35:29 -0700 (PDT)
Received: from dhcp-10-61-105-20.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 5B50C5FF8; Tue, 8 Oct 2013 10:35:28 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>
Date: Tue, 08 Oct 2013 18:16:30 +0200
Message-Id: <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Oct 2013 17:35:29 -0000

Fred,

> Hi, I would like to make a small amendment to what I said in my
> previous message as follows:
> 
> 4) Section 5, change the final paragraph to:
> 
>   "As a result of the above mentioned requirements, a packet's header
>   chain length MUST fit within the Path MTU associated with its
>   destination.  Hosts MAY discover the Path MTU, using procedures such
>   as those defined in [RFC1981] and [RFC4821]. However, if a host does
>   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
>   1280 bytes [RFC2460]. The host MUST then limit each packet's header
>   chain length to the Path MTU minus 256 bytes in case additional
>   encapsulation headers are inserted by tunnels on the path."

I would claim that additional encapsulation headers are already considered in the 1280 minimum MTU.
as in: 1500 - 1280.

cheers,
Ole

v2.35.0 | Report a Bug | By Email | System Status