IETF Logo Mail Archive

RE: IPv6 Type 0 Routing Header issues

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Fri, 27 April 2007 18:43 UTC

Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhVPj-00022c-Sp; Fri, 27 Apr 2007 14:43:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhVPi-00022W-5C for ipv6@ietf.org; Fri, 27 Apr 2007 14:43:26 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69] helo=blv-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhVPg-0001qP-Qe for ipv6@ietf.org; Fri, 27 Apr 2007 14:43:26 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216]) by blv-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id l3RIhO26026945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 27 Apr 2007 11:43:24 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_RELAY) with ESMTP id l3RIhNZ9018535; Fri, 27 Apr 2007 11:43:23 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com [128.225.80.27]) by blv-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id l3RIhDav018223; Fri, 27 Apr 2007 11:43:23 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Apr 2007 14:43:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 27 Apr 2007 14:43:21 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD169@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <017501c78855$84a6f380$8df4da80$@net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: IPv6 Type 0 Routing Header issues
Thread-Index: AceIAa6HuP4+0Lm9RSu2Fd9lb2FPKgAEcskgABBiriAAKYdiIA==
References: <CA7D9B4A761066448304A6AFC09ABDA9015AD161@XCH-NE-1V2.ne.nos.boeing.com> <017501c78855$84a6f380$8df4da80$@net>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: alh-ietf@tndh.net
X-OriginalArrivalTime: 27 Apr 2007 18:43:22.0558 (UTC) FILETIME=[EEA925E0:01C788FB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ipv6@ietf.org
Subject: RE: IPv6 Type 0 Routing Header issues
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Tony Hain [mailto:alh-ietf@tndh.net] 
> Sent: Thursday, April 26, 2007 6:52 PM
> 
> As I recall the primary goal was to allow a system to state a specific
> transit path because it was the one that the subscriber had a 
> contract with.
> Think dialing a local number to get a specific long-distance carrier's
> presence, rather than paying the extortion rate that the 
> local provider
> charges for their random selection of long-distance.

That makes good sense for the sending host. But the receiving host would
have no reason to forward anything beyond the destination address of the
packet, no matter what the extension header says. Except for the case of
multiple IP addresses in that host, which I had not considered.

If Steve Deering wanted all hosts, whether set to forward packets or
not, to process extension headers, my only conclusion is that he was
thinking of multiple IP addresses in that host.

Just trying to figure out what the corner cases are.

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email