Interest in IPv6 Hop by Hop options
Alan Davy <adavy@tssg.org> Wed, 04 November 2009 16:40 UTC
Return-Path: <adavy@tssg.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA1C73A698B for <ipv6@core3.amsl.com>; Wed, 4 Nov 2009 08:40:45 -0800 (PST)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qaWEzPz4B+JA for <ipv6@core3.amsl.com>; Wed, 4 Nov 2009 08:40:44 -0800 (PST)
Received: from smtps.tssg.org (smtps.tssg.org [193.1.185.47]) by core3.amsl.com (Postfix) with ESMTP id 43F933A6977 for <ipv6@ietf.org>; Wed, 4 Nov 2009 08:40:43 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.44,680,1249254000"; d="scan'208";a="887941"
Received: from unknown (HELO [10.37.2.134]) ([10.37.2.134]) by smtps.tssg.org with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Nov 2009 16:41:04 +0000
Message-ID: <4AF1AE7A.6000705@tssg.org>
Date: Wed, 04 Nov 2009 16:40:26 +0000
From: Alan Davy <adavy@tssg.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Interest in IPv6 Hop by Hop options
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 04 Nov 2009 16:40:45 -0000
Hi All, We are currently specifying an IPv6 hop by hop option which will be used to carry node related information along a path within a network domain. There has been previous proposals submitted to the IETF within this area, such as IPv6 Route Record [1] and Connection/Link Status Investigation[2]. We are aware of the reasons these proposals have been rejected previously, being mainly related to the problems of the hop by hop option and the operators unwillingness to share private data. As such a technique has a variety of useful applications to management and monitoring, we believe that a standard method of managing data entry within an IPv6 hop by hop option along with standard data format templates can be of great benefit to the future development of in-line based network management and monitoring protocols. We would like to see if there is much interest in specifying such a draft and whether anyone would like to assist in the specification of such an Internet Draft. We wish to constrain this solution to intra domain (such as DiffServ). Looking forward to some discussion on this issue. [1] http://tools.ietf.org/html/draft-kitamura-ipv6-record-route-00 [2] http://tools.ietf.org/html/draft-ietf-ipngwg-hbh-ext-csi-02 Best Regards, -- Alan Davy
- Interest in IPv6 Hop by Hop options Alan Davy
- Re: Interest in IPv6 Hop by Hop options Rémi Denis-Courmont
- Re: Interest in IPv6 Hop by Hop options Alan Davy
- Re: Interest in IPv6 Hop by Hop options Rémi Denis-Courmont
- Re: Interest in IPv6 Hop by Hop options Christopher Morrow