Re: Offset Indicating option
Libor Polčák <ipolcak@fit.vutbr.cz> Mon, 26 September 2011 15:06 UTC
Return-Path: <ipolcak@fit.vutbr.cz>
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 87DF621F8DD1 for <ipv6@ietfa.amsl.com>; Mon, 26 Sep 2011 08:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 te1s3xdDAW0I for <ipv6@ietfa.amsl.com>; Mon, 26 Sep 2011 08:06:20 -0700 (PDT)
Received: from kazi.fit.vutbr.cz (kazi6.fit.vutbr.cz [IPv6:2001:67c:1220:808::93e5:80c]) by ietfa.amsl.com (Postfix) with ESMTP id 9C41621F8DA3 for <ipv6@ietf.org>; Mon, 26 Sep 2011 08:06:19 -0700 (PDT)
Received: from [147.229.13.162] (pcpolcak.fit.vutbr.cz [147.229.13.162]) (authenticated user=ipolcak mech=PLAIN bits=0) by kazi.fit.vutbr.cz (envelope-from ipolcak@fit.vutbr.cz) (8.14.5/8.14.4) with ESMTP id p8QF90Zu014325 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 26 Sep 2011 17:09:01 +0200 (CEST)
Message-ID: <4E80958C.3040102@fit.vutbr.cz>
Date: Mon, 26 Sep 2011 17:09:00 +0200
From: Libor Polčák <ipolcak@fit.vutbr.cz>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20110922 Firefox/6.0 SeaMonkey/2.3.1
MIME-Version: 1.0
To: Hagen Paul Pfeifer <hagen@jauu.net>
Subject: Re: Offset Indicating option
References: <4E7FDEFA.6060808@gmail.com> <4E805CB2.1020405@fit.vutbr.cz> <67c39be43f3269913848250f97850642@localhost>
In-Reply-To: <67c39be43f3269913848250f97850642@localhost>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.71 on 147.229.8.12
Cc: 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
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: Mon, 26 Sep 2011 15:06:20 -0000
Hagen Paul Pfeifer wrote: > > Hello Libor, > > ich published a I-D: "IPv6 Extension Headers Reserved Space" > > http://tools.ietf.org/html/draft-pfeifer-6man-exthdr-res-01 > > which try to address some of the problems. Introducing a new "number > model" don't work, but maybe a solution somewhere between - as presented in > the I-D - may address the problem adequate. > > Cheers, Hagen Hello Hagen, we are probably hijacking the thread little bit, but I support your draft. Minor correction though: sec 1, 2nd paragraph One exception is is the hop-by-hop -> One exception is the hop-by-hop I am not sure if you can request IANA for specific range (someone else might want the same numbers at the same time). Maybe, it will be safer if you request 8 consecutive protocol numbers and rephrase IANA Considerations to something like: This document includes a request to IANA. The editors of this draft request the 8 consecutive protocol numbers IP6_EXTHDR_RESERVED_MIN till IP6_EXTHDR_RESERVED_MAX be reserved for uniform formated IPv6 extension header. Additionally, replace numerical constants in the text with these names. Best wishes, Libor
- Offset Indicating option Brian E Carpenter
- Re: Offset Indicating option Libor Polčák
- Re: Offset Indicating option Hagen Paul Pfeifer
- Re: Offset Indicating option John Leslie
- Re: Offset Indicating option Libor Polčák
- Re: Offset Indicating option Brian E Carpenter
- Re: Offset Indicating option John Leslie
- Re: Offset Indicating option Christopher Morrow
- Re: Offset Indicating option Brian E Carpenter
- Re: Offset Indicating option Christopher Morrow
- Re: Offset Indicating option Thomas Narten
- Re: Offset Indicating option Brian Haberman