[dhcwg] Comments on "Configured Tunnel End Point Option for DHCPv6"
Ralph Droms <rdroms@cisco.com> Tue, 10 February 2004 22:57 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27780 for <dhcwg-archive@odin.ietf.org>; Tue, 10 Feb 2004 17:57:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aqgoa-0003NW-Ql for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 17:57:12 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1AMvCrK012985 for dhcwg-archive@odin.ietf.org; Tue, 10 Feb 2004 17:57:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aqgoa-0003NM-MC for dhcwg-web-archive@optimus.ietf.org; Tue, 10 Feb 2004 17:57:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27716 for <dhcwg-web-archive@ietf.org>; Tue, 10 Feb 2004 17:57:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqgoX-0004Ql-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:57:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqgnX-0004J6-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:56:07 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AqgmY-0004BS-00 for dhcwg-web-archive@ietf.org; Tue, 10 Feb 2004 17:55:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqgmV-000312-RY; Tue, 10 Feb 2004 17:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aqglk-0002yy-1k for dhcwg@optimus.ietf.org; Tue, 10 Feb 2004 17:54:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27565 for <dhcwg@ietf.org>; Tue, 10 Feb 2004 17:54:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aqglh-000456-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 17:54:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aqgkk-0003zE-00 for dhcwg@ietf.org; Tue, 10 Feb 2004 17:53:14 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Aqgk3-0003nb-01 for dhcwg@ietf.org; Tue, 10 Feb 2004 17:52:32 -0500
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 10 Feb 2004 15:00:21 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i1AMqD4U000233 for <dhcwg@ietf.org>; Tue, 10 Feb 2004 14:52:13 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-1-31.cisco.com [10.86.240.31]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AFY88479; Tue, 10 Feb 2004 17:52:11 -0500 (EST)
Message-Id: <4.3.2.7.2.20040210174302.02864790@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 10 Feb 2004 17:52:08 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Comments on "Configured Tunnel End Point Option for DHCPv6"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Some comments on "Configured Tunnel End Point Option for DHCPv6", draft-ietf-dhc-dhcpv6-ctep-opt-00.txt: Because there are several types of tunnels defined in RFC 2893, it would be helpful to mention explicitly the section (section 4, I think?) in which "configured tunnels" are defined. Unless I'm misunderstanding RFC 2893 (which is not unlikely), the endpoint of a configured tunnel should be the IPv4 address of a router that can strip off the IPv4 header and forward the tunnelled IPv6 datagram to its destination. So, the CTEP address for each endpoint should be an IPv4 address? - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Comments on "Configured Tunnel End Point … Ralph Droms
- RE: [dhcwg] Comments on "Configured Tunnel End Po… S. Daniel Park
- RE: [dhcwg] Comments on "Configured Tunnel End Po… S. Daniel Park
- RE: [dhcwg] Comments on "Configured Tunnel End Po… Ralph Droms
- RE: [dhcwg] Comments on "Configured Tunnel End Po… S. Daniel Park
- RE: [dhcwg] Comments on "Configured Tunnel End Po… Ralph Droms