Querry regarding Hop-by-Hop extension header processing.
sreenatha <sreenatha.b@huawei.com> Mon, 06 February 2012 11:02 UTC
Return-Path: <sreenatha.b@huawei.com>
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 99BF021F85BD for <ipv6@ietfa.amsl.com>; Mon, 6 Feb 2012 03:02:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.437
X-Spam-Level:
X-Spam-Status: No, score=-6.437 tagged_above=-999 required=5 tests=[AWL=0.161, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 0+JQ8eGskrGa for <ipv6@ietfa.amsl.com>; Mon, 6 Feb 2012 03:02:57 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 781C021F85B4 for <ipv6@ietf.org>; Mon, 6 Feb 2012 03:02:57 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYY00B29X9R8U@szxga03-in.huawei.com> for ipv6@ietf.org; Mon, 06 Feb 2012 19:01:03 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYY008D4X9I5E@szxga03-in.huawei.com> for ipv6@ietf.org; Mon, 06 Feb 2012 19:01:03 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AGW22817; Mon, 06 Feb 2012 19:00:19 +0800
Received: from SZXEML413-HUB.china.huawei.com (10.82.67.152) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 06 Feb 2012 19:00:17 +0800
Received: from blrprnc08ns (10.18.96.97) by szxeml413-hub.china.huawei.com (10.82.67.152) with Microsoft SMTP Server id 14.1.323.3; Mon, 06 Feb 2012 19:00:27 +0800
Date: Mon, 06 Feb 2012 16:30:09 +0530
From: sreenatha <sreenatha.b@huawei.com>
Subject: Querry regarding Hop-by-Hop extension header processing.
X-Originating-IP: [10.18.96.97]
To: ipv6@ietf.org
Message-id: <002401cce4be$7eb91640$7c2b42c0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_sOcMXEmUZpb9KdmLR8fDvA)"
Content-language: en-us
Thread-index: Aczkvn36rFGi7BC6S0+Pu5hEGOasWQ==
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 06 Feb 2012 03:43:09 -0800
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, 06 Feb 2012 11:02:58 -0000
Hi Folks,
I have one query. In section 4 of RFC 2460, it is said that Hop-by-Hop
extension header should be processed by all nodes including the Source and
destination nodes. What is the point in processing the Hop-by-Hop extension
header by Source node if the node only inserting the Header?
Thanks-
B.Sreenatha Setty,
Software Engineer,
Huawei Technologies India Private Ltd.,
Bangalore
----------------------------------------------------------------------------
--------------------------------------------------------------------------
This e-mail and its attachments contain confidential information from
HUAWEI, which is intended only for the person or entity whose address is
listed above. Any use of the information contained herein in any way
(including, but not limited to, total or partial disclosure, reproduction,
or dissemination) by persons other than the intended recipient(s) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
----------------------------------------------------------------------------
--------------------------------------------------------------------------