From mailman-bounces@ietf.org Tue Jun 1 08:23:30 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22874 for ; Tue, 1 Jun 2004 08:23:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BV5jd-0004ua-Ls for dhc-archive@lists.ietf.org; Tue, 01 Jun 2004 05:39:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: dhc-archive@ietf.org X-No-Archive: yes Message-ID: Date: Tue, 01 Jun 2004 05:06:50 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for dhc-archive@lists.ietf.org: List Password // URL ---- -------- dhcwg@ietf.org aCBd https://www1.ietf.org/mailman/options/dhcwg/dhc-archive%40lists.ietf.org From mailman-admin@ietf.org Tue Jun 1 12:41:12 2004 Received: from optimus.ietf.org ([132.151.1.18]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23058 for ; Tue, 1 Jun 2004 12:41:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BV9AT-0002xb-TL for DHC-ARCHIVE@lists.ietf.org; Tue, 01 Jun 2004 09:19:01 -0400 Date: Tue, 01 Jun 2004 09:19:01 -0400 Message-ID: <20040601131901.26555.15953.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: DHC-ARCHIVE@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, dhcwg-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for DHC-ARCHIVE@lists.ietf.org: List Password // URL ---- -------- dhcwg@ietf.org aCBd https://www1.ietf.org/mailman/options/dhcwg/dhc-archive%40lists.ietf.org From dhcwg-bounces@ietf.org Tue Jun 1 22:32:23 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16205; Tue, 1 Jun 2004 22:32:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVLDI-0001WV-Kc; Tue, 01 Jun 2004 22:10:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVFWr-000764-MQ for dhcwg@megatron.ietf.org; Tue, 01 Jun 2004 16:06:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20909 for ; Tue, 1 Jun 2004 16:06:32 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVFWq-0007Rz-EL for dhcwg@ietf.org; Tue, 01 Jun 2004 16:06:32 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVFVJ-0006Sr-00 for dhcwg@ietf.org; Tue, 01 Jun 2004 16:04:58 -0400 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 1BVFTC-0005NP-00 for dhcwg@ietf.org; Tue, 01 Jun 2004 16:02:46 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 01 Jun 2004 13:02:59 +0000 X-BrightmailFiltered: true 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 i51K2DXl003373 for ; Tue, 1 Jun 2004 13:02:14 -0700 (PDT) Received: from rdroms-w2k01.cisco.com ([161.44.65.119]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJA07403; Tue, 1 Jun 2004 16:02:12 -0400 (EDT) Message-Id: <4.3.2.7.2.20040601155834.02ada9a0@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 01 Jun 2004 16:02:09 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [dhcwg] IPR disclosure and X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org The dhc WG has "Subscriber-ID Suboption for the DHCP Relay Agent Option", ", as a work item. This Internet Draft has passed WG last call and IETF last call. There is an IPR disclosure associated with this Internet Draft, http://ietf.org/ietf/IPR/PacketFront-IPR.txt. The WG needs to decide if it is willing to accept the specification in the Internet Draft with the associated IPR disclosure. draft-ietf-dhc-subscriber-id-06.txt passed WG last call on 2003-09-12 and passed IETF last call on 2004-02-03. During the IETF last call, the IESG received a notification of an IPR disclosure related to the Internet Draft. Although the IPR disclosure had been published 2003-04-17, there was no general notification of that publication and, apparently, no one in the dhc WG or the IESG was aware of the IPR disclosure. The dhc WG discussed the publication of the Internet Draft on the dhcwg mailing list and there was support on both sides of the issue. Because RFC 3667 and RFC 3668 were both ready for publication, discussion was suspended pending publication of those new documents related to IPR in the IETF. The original IPR disclosure applied to two Internet Drafts, and . The original disclosure made no mention of any use licensing agreements for the IPR. Concurrently with the WG discussion on the IPR disclosure, a new IPR disclosure was published on 2004-02-02, which refers only to and which includes RAND (reasonable and non-discriminatory) licensing terms. RFC 3667, "IETF Rights in Contributions," and RFC 3668, "Intellectual Property Rights in IETF Technology" are both relevant to the dhc WG discussion of . Note that the need for disclosure of the IPR issues in this case, although the editors of the draft are not associated with the organization submitting the IPR disclosure, is established by section 6.1.2 of RFC 3668, which requires that: Any individual participating in an IETF discussion who reasonably and personally knows of IPR meeting the conditions of Section 6.6 which the individual believes Covers or may ultimately Cover a Contribution made by another person, or which such IETF participant reasonably and personally knows his or her employer or sponsor may assert against Implementing Technologies based on such Contribution, must make a disclosure in accordance with this Section 6. contains the text required by section 5 of RFC 3668 because of the IPR disclosure relative to the Internet Draft. The current IPR disclosure meets the intent (if not the letter) of section 6.4 of RFC 3668, and the licensing terms meet the RAND requirements of section 6.5 of RFC 3668. At this point, the decision about whether or not to accept as a standard rests with the dhc WG. I need to assess the WG consensus for how to proceed with . Each WG member should review the Internet Draft, the IPR disclosure, RFC 3667 and RFC 3668 to form an opinion about whether should move forward through the standards process. We will conduct a discussion on the WG mailing list, to conclude on Friday, 2004-06-11. I will use the discussion to assess the WG consensus. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Wed Jun 2 02:02:17 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03381; Wed, 2 Jun 2004 02:02:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVNqv-00076d-5f; Wed, 02 Jun 2004 00:59:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVN6B-0003hU-Fk for dhcwg@megatron.ietf.org; Wed, 02 Jun 2004 00:11:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22250 for ; Wed, 2 Jun 2004 00:11:27 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVN67-0001ga-Op for dhcwg@ietf.org; Wed, 02 Jun 2004 00:11:27 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVN58-0001C7-00 for dhcwg@ietf.org; Wed, 02 Jun 2004 00:10:27 -0400 Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1BVN49-0000hq-00 for dhcwg@ietf.org; Wed, 02 Jun 2004 00:09:25 -0400 Received: from [10.0.1.170] (dsl081-147-128.chi1.dsl.speakeasy.net [64.81.147.128]) by toccata.fugue.com (Postfix) with ESMTP id E3A071B2D15 for ; Tue, 1 Jun 2004 23:08:49 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Resent-Date: Tue, 1 Jun 2004 23:09:25 -0500 Message-Id: Content-Transfer-Encoding: 7bit Resent-To: dhcwg@ietf.org Resent-Message-Id: <7FB2A258-B44A-11D8-9004-000A95D9C74C@fugue.com> From: Ted Lemon Subject: Re: [dhcwg] IPR disclosure and Resent-From: Ted Lemon Date: Tue, 1 Jun 2004 23:08:27 -0500 To: Ralph Droms X-Mailer: Apple Mail (2.618) Resent-Date: Wed, 02 Jun 2004 00:09:25 -0400 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit "Reasonable and Non-discriminatory" sounds really nice and comforting, but what does it actually mean? "Reasonable" has no explicit, enforceable meaning whatsoever. It implies that the fee charged for use of the technology will be affordable, but by whom? And why imply it - why not just say it? Sure, in a court of law, "reasonable" is better protection than nothing, but it's not much better. "Non-discriminatory" implies that all implementors will be subject to the same fee structure, which may be unaffordable to some without going against the meaning of the phrase. Generally speaking, what geeks like us mean when they say "reasonable and non-discriminatory" is "there won't be a fee or any patent enforcement unless you take patent enforcement action against us first." I think this is even what the legal folks writing these IPR notices intend when they write them. The problem is that the language they are using actually means something else, and provides no protection at all to implementors of RFCs where such implementations would infringe. Like using sprintf when you should have used snprintf, this does us no harm in the usual case, but could do us great harm if something goes wrong. This is not an idle worry - we have all seen, on many occasions, IPR holding companies do their worst with IP rights that were originally acquired as protection, not as a revenue source, after a failed dot-com's assets were purchased by someone else. For my own part, I am against putting the working group's stamp of approval on technology that is encumbered under the "reasonable and non-discriminatory" label, not because I do not trust the intentions of those who wrote the IPR statements, nor because I don't trust the intentions of those whose names are on the patents, but simply because those people may not be the people who wind up enforcing the IPR statements in the future, and the IPR statements provide plenty of wiggle-room for much more draconian enforcement. My vote is to put both these drafts on the back burner until owners of the intellectual property rights associated with them submit IPR declarations stating that they will not charge for the use of this technology except in cases where the user of the technology has taken some kind of IPR enforcement action against them. I think this is what they intend anyway, which is great, but I don't think it's unreasonable to ask to have it in writing before we proceed. The involved parties here are reasonable people, so I see no reason to think that, given a reason for doing so, they will not do the right thing. I would like to point out, by the way, that this is a quite mainstream viewpoint, and is not in conflict with the latest IETF RFCs on intellectual property rights. I would suggest reading the whole of each RFC, not just choice selections from them. I mention this only because the last time this came up, someone (I forget who) said that it was the IESG's job to figure this stuff out. In fact the IETF policy on this is pretty clear - it's generally up to the working group to make the tradeoff as to whether or not to write specifications that use patented technology. It's certainly allowed for the IESG or the IETF as a whole to intervene if it's perceived that the working group has made a mistake, but the onus is on the working group to make the initial call. So let us not make a mistake - let us hold these drafts back until we get IPR statements that are clear, that protect the owners of the IP rights, but that do not needlessly endanger implementors of these RFCs. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Wed Jun 2 17:23:47 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22098; Wed, 2 Jun 2004 17:23:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVaEJ-0001J3-Ee; Wed, 02 Jun 2004 14:12:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVWHs-000854-CN for dhcwg@megatron.ietf.org; Wed, 02 Jun 2004 10:00:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22409 for ; Wed, 2 Jun 2004 09:59:55 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVWHc-00047n-LD for dhcwg@ietf.org; Wed, 02 Jun 2004 09:59:56 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVWGa-0003cS-00 for dhcwg@ietf.org; Wed, 02 Jun 2004 09:58:53 -0400 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 1BVWFO-0002e0-00 for dhcwg@ietf.org; Wed, 02 Jun 2004 09:57:38 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 02 Jun 2004 06:58:00 +0000 X-BrightmailFiltered: true 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 i52Dv4Xn000808 for ; Wed, 2 Jun 2004 06:57:06 -0700 (PDT) Received: from rdroms-w2k01.cisco.com ([161.44.65.119]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJA59819; Wed, 2 Jun 2004 09:57:03 -0400 (EDT) Message-Id: <4.3.2.7.2.20040602095512.029c0b28@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 02 Jun 2004 09:57:02 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [dhcwg] Agenda for dhc WG meeting at IETF 60 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org It's time to start thinking about our agenda for the WG meeting in San Diego. Please let me know if you have an item you would like to see on the agenda. I've asked to avoid meeting at the same time as the following WGs: dna, dnsext, dnsop, geopriv, ipcdn, ipv6, manet, nemo, netconf, v6ops, zeroconf, zerouter Are there any others I should ask to avoid? - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Wed Jun 2 18:17:56 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26663; Wed, 2 Jun 2004 18:17:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVaFG-0001c9-TU; Wed, 02 Jun 2004 14:13:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVXZK-0007Q6-9p for dhcwg@megatron.ietf.org; Wed, 02 Jun 2004 11:22:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27492 for ; Wed, 2 Jun 2004 11:22:16 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVXZJ-0006Gr-Fk for dhcwg@ietf.org; Wed, 02 Jun 2004 11:22:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVXYD-0005hA-00 for dhcwg@ietf.org; Wed, 02 Jun 2004 11:21:10 -0400 Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BVXXA-0004f2-00; Wed, 02 Jun 2004 11:20:05 -0400 Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BVXD9-00047Q-2b; Wed, 02 Jun 2004 10:59:23 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Wed, 02 Jun 2004 10:59:23 -0400 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Cc: dhc mailing list , dhc chair , Internet Architecture Board , RFC Editor Subject: [dhcwg] Protocol Action: 'NIS Configuration Options for DHCPv6' to Proposed Standard X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org The IESG has approved the following document: - 'NIS Configuration Options for DHCPv6 ' as a Proposed Standard This document is the product of the Dynamic Host Configuration Working Group. The IESG contact persons are Margaret Wasserman and Thomas Narten. Technical Summary This document describes four options for NIS-related configuration information in DHCPv6: NIS Servers [3], NIS+ Servers [3], NIS Client Domain Name [3], NIS+ Client Domain name [3]. Working Group Summary This document was produced by the DHC WG and has been through WG last call and IETF last call. In the last call process, it was verified that an IPv6 implementation of NIS is available. Protocol Quality This document has been reviewed for the IESG by Margaret Wasserman. RFC Editor Note: RFC Editor, please change section 1. of the document as follows: OLD: 1. Introduction This document describes four options for passing configuration information related to Network Information Service (NIS) [3] in DHCPv6 (RFC 3315 [1]). NEW: 1. Introduction This document describes four options for passing configuration information related to Network Information Service (NIS) [3] in DHCPv6 (RFC 3315 [1]). The options defined in this draft can only be used to configure information about NIS servers that can be reached using IPv6. The DHCP option to configure information about IPv4 NIS servers can be found in RFC 2132 [4]. Mechanisms for configuring IPv4/IPv6 dual-stack applications are being considered, but are not specified in this document. And, please add an additional informative reference: [4] Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor Extensions", RFC 2132, March 1997. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Wed Jun 2 19:13:59 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01417; Wed, 2 Jun 2004 19:13:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVaJJ-0003Cz-9M; Wed, 02 Jun 2004 14:17:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVZrN-0000Zs-Fi for dhcwg@megatron.ietf.org; Wed, 02 Jun 2004 13:49:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05485 for ; Wed, 2 Jun 2004 13:49:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVZrM-0004Y1-3w for dhcwg@ietf.org; Wed, 02 Jun 2004 13:49:04 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVZqJ-00047g-00 for dhcwg@ietf.org; Wed, 02 Jun 2004 13:47:59 -0400 Received: from ftp.relicore.com ([4.36.57.198]) by ietf-mx with esmtp (Exim 4.12) id 1BVZpF-0003KW-00 for dhcwg@ietf.org; Wed, 02 Jun 2004 13:46:53 -0400 Received: from STEVEPC ([192.168.0.222]) by ftp.relicore.com (8.12.9/8.12.9) with SMTP id i52HMVJo014815 for ; Wed, 2 Jun 2004 13:22:31 -0400 (EDT) From: "Steve Gonczi" To: Subject: RE: [dhcwg] IPR disclosure and Date: Wed, 2 Jun 2004 13:46:23 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit I agree with Ted. His suggestions are fair and reasonable. The term "Reasonable and Non-discriminatory" is indeed uncomfortably vague. Steve G _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 3 06:47:04 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29956; Thu, 3 Jun 2004 06:47:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVpWI-0007Ci-2Q; Thu, 03 Jun 2004 06:32:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVksJ-00074W-EP for dhcwg@megatron.ietf.org; Thu, 03 Jun 2004 01:34:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24593 for ; Thu, 3 Jun 2004 01:34:31 -0400 (EDT) From: juha.wiljakka@nokia.com Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVks2-0004PW-AM for dhcwg@ietf.org; Thu, 03 Jun 2004 01:34:30 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVkqe-0003qX-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 01:33:04 -0400 Received: from mgw-x2.nokia.com ([131.228.20.22]) by ietf-mx with esmtp (Exim 4.12) id 1BVkpm-0003Pr-00; Thu, 03 Jun 2004 01:32:10 -0400 Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i535W5v22772; Thu, 3 Jun 2004 08:32:05 +0300 (EET DST) X-Scanned: Thu, 3 Jun 2004 08:31:58 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i535VwBh003648; Thu, 3 Jun 2004 08:31:58 +0300 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 000u5HkY; Thu, 03 Jun 2004 08:31:56 EEST Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i535VtH27646; Thu, 3 Jun 2004 08:31:55 +0300 (EET DST) Received: from esebe005.NOE.Nokia.com ([172.21.138.45]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Thu, 3 Jun 2004 08:31:38 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 3 Jun 2004 08:31:37 +0300 Message-ID: <245DBCAEEC4F074CB77B3F984FF9834F020CE3D7@esebe005.ntc.nokia.com> Thread-Topic: IPv6 Host Configuration of Recursive DNS Server Thread-Index: AcRJB7WgdazXpx0ASMSxnG9HUoRN4QAIXcJg To: , , X-OriginalArrivalTime: 03 Jun 2004 05:31:38.0054 (UTC) FILETIME=[0AB99660:01C4492C] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Cc: paul@etri.re.kr Subject: [dhcwg] New draft: IPv6 Host Configuration of Recursive DNS Server X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Hi all, (Firstly, my apologies for cross-posting) Forwarding Paul's e-mail also on IPv6, v6ops and dhc lists. Your = comments on the draft are appreciated on the dnsop mailing list = dnsop@lists.uoregon.edu (no cross-posting, please). BR, -Juha W.- -----Original Message----- From: dnsop-v6conf-bounces@nominum.com [mailto:dnsop-v6conf-bounces@nominum.com]On Behalf Of ext Jaehoon Paul Jeong Sent: 03 June, 2004 04:10 To: dnsop@lists.uoregon.edu Cc: IPv6 DNS Configuration Subject: IPv6 Host Configuration of Recursive DNS Server Hello DNSOP members, As you know, a new draft has been published for IPv6 Host Configuration = of DNS Server Information Approaches: http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-configurati= on-00.txt For a long time, DNS Discovery has been discussed at both IPv6 and DNSOP = working groups. The long discussion seems to be resolved through this draft. In this draft, three approaches are suggested: (a) RA option, (b) DHCPv6 = option, and (c) Well-known anycast addresses for Recursive DNS Servers. We, authors, used "DNS Configuration" instead of "DNS Discovery" because = recursive DNS server address is=20 only configured in IPv6 host, not generating DNS server address like in = IPv6 address autoconfiguration. This draft focuses on describing the attributes of three approaches and = suggesting four applicable scenarios: (a) ISP network, (b) Enterprise network, (c) 3GPP network, (d) Unmanaged = network. Through your review and comments, this will be published as = Informational RFC according to our milestones. IMHO, if necessary, the drafts of two other approaches except DHCPv6 = option will be developed into separate RFCs. Thanks. Paul,=20 IPv6 DNS Configuration Design Team. ------------------------------------------------------ Jaehoon Paul Jeong (Research Engineer) TEL. +82-42-860-1664 Mobile +82-16-711-1765 161 Gajeong-dong Yuseong-gu, Daejeon 305-350, Korea NGI Standardization Research Team/PEC/ETRI Homepage: http://www.adhoc.6ants.net/~paul _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 3 07:29:52 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02790; Thu, 3 Jun 2004 07:29:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVqBQ-0000wS-0D; Thu, 03 Jun 2004 07:14:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVmol-0002PW-41 for dhcwg@megatron.ietf.org; Thu, 03 Jun 2004 03:39:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16532 for ; Thu, 3 Jun 2004 03:38:58 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVmoT-0006l1-MH for dhcwg@ietf.org; Thu, 03 Jun 2004 03:38:57 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVmnb-0006LW-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 03:38:03 -0400 Received: from intermail.se.dataphone.net ([212.37.1.50]) by ietf-mx with esmtp (Exim 4.12) id 1BVmmb-0005uF-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 03:37:01 -0400 Received: from [213.115.251.202] (account budm@weird-solutions.com HELO offset.weird.se) by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.1.5) with ESMTP id 7371132 for dhcwg@ietf.org; Thu, 03 Jun 2004 09:37:00 +0200 From: Bud Millwood Organization: Weird Solutions, Inc. To: dhcwg@ietf.org Subject: Re: [dhcwg] IPR disclosure and Date: Thu, 3 Jun 2004 09:30:40 +0200 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406030930.40267.budm@weird-solutions.com> 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bud Millwood List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit I strongly agree with Ted as well. In fact I think it's possible that we could inadvertently marginalize DHCP over the long term if we don't ensure that the protocol is free of IPR claims. Bud Millwood Weird Solutions, Inc. http://www.weird-solutions.com tel: +46 8 758 3700 fax: +46 8 758 3687 mailto:budm@weird-solutions.com _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 3 14:54:57 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02787; Thu, 3 Jun 2004 14:54:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVwWG-0002KY-4H; Thu, 03 Jun 2004 14:00:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVvoI-0000op-Q6 for dhcwg@megatron.ietf.org; Thu, 03 Jun 2004 13:15:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26049 for ; Thu, 3 Jun 2004 13:15:21 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVvoH-0005rr-Tx for dhcwg@ietf.org; Thu, 03 Jun 2004 13:15:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVvnM-0005Vu-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 13:14:25 -0400 Received: from prattle.redback.com ([155.53.12.9]) by ietf-mx with esmtp (Exim 4.12) id 1BVvmY-0005A2-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 13:13:34 -0400 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 9340A39F88D; Thu, 3 Jun 2004 10:13:33 -0700 (PDT) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23500-05; Thu, 3 Jun 2004 10:13:33 -0700 (PDT) Received: from redback.com (malt.redback.com [155.53.12.41]) by prattle.redback.com (Postfix) with ESMTP id D9CB639F88C; Thu, 3 Jun 2004 10:13:32 -0700 (PDT) Received: from malt (localhost [127.0.0.1]) by redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) with ESMTP id KAA27382; Thu, 3 Jun 2004 10:13:31 -0700 (PDT) Message-Id: <200406031713.KAA27382@redback.com> To: Bud Millwood Subject: Re: [dhcwg] IPR disclosure and In-reply-to: Mail from Bud Millwood dated Thu, 03 Jun 2004 09:30:40 +0200 <200406030930.40267.budm@weird-solutions.com> Date: Thu, 03 Jun 2004 10:13:31 -0700 From: Naiming Shen X-Virus-Scanned: by amavisd-new at redback.com 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 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org "free of IPR claims" ?-) Have you read the page on http://www.ietf.org/ipr.html ? Regards. ] I strongly agree with Ted as well. ] ] In fact I think it's possible that we could inadvertently marginalize DHCP ] over the long term if we don't ensure that the protocol is free of IPR ] claims. ] ] Bud Millwood ] Weird Solutions, Inc. ] http://www.weird-solutions.com ] tel: +46 8 758 3700 ] fax: +46 8 758 3687 ] mailto:budm@weird-solutions.com ] ] _______________________________________________ ] dhcwg mailing list ] dhcwg@ietf.org ] https://www1.ietf.org/mailman/listinfo/dhcwg - Naiming _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 3 18:34:18 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29409; Thu, 3 Jun 2004 18:34:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BW0Md-00035v-S7; Thu, 03 Jun 2004 18:07:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVzhe-0006oK-Eh for dhcwg@megatron.ietf.org; Thu, 03 Jun 2004 17:24:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19371 for ; Thu, 3 Jun 2004 17:24:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVzhd-0005lA-0z for dhcwg@ietf.org; Thu, 03 Jun 2004 17:24:45 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVzW5-00038P-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 17:12:50 -0400 Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1BVzKu-0000NJ-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 17:01:16 -0400 Received: from [10.0.1.2] (dialup-4.240.114.141.Dial1.Phoenix1.Level3.net [4.240.114.141]) by toccata.fugue.com (Postfix) with ESMTP id AA16C1B3E6B; Thu, 3 Jun 2004 16:00:09 -0500 (CDT) In-Reply-To: <200406031713.KAA27382@redback.com> References: <200406031713.KAA27382@redback.com> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <14239A78-B5A1-11D8-9ACE-000A95D9C74C@nominum.com> Content-Transfer-Encoding: 7bit From: Ted Lemon Subject: Re: [dhcwg] IPR disclosure and Date: Thu, 3 Jun 2004 14:00:43 -0700 To: Naiming Shen X-Mailer: Apple Mail (2.618) 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: dhcwg@ietf.org, Bud Millwood X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit On Jun 3, 2004, at 10:13 AM, Naiming Shen wrote: > Have you read the page on http://www.ietf.org/ipr.html ? Personally, I don't care if the RFCs are free from IPR claims, and indeed the mere lack of IPR claims in the IETF IPR repository doesn't mean no such claims exist. However, I do think that we shouldn't advance drafts to RFC when there are IPR claims on the technology in the draft unless either there is a really strong need for the technology described in the draft that overrides our concerns about IPR issues, or the IPR notice includes a disclaimer that offers real protection to implementors as well as to the person who is making the IPR claim. And just to be clear, the IETF's assertions regarding the text of internet drafts is a very different thing than patents. I think we're mostly concerned about patents here, although certainly we also don't want to put copyrighted text into RFCs where we don't have permission to do so. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Jun 4 00:40:52 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26979; Fri, 4 Jun 2004 00:40:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BW6Sm-0003UC-JX; Fri, 04 Jun 2004 00:37:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BW6Pm-00030E-2b for dhcwg@megatron.ietf.org; Fri, 04 Jun 2004 00:34:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26823 for ; Fri, 4 Jun 2004 00:34:42 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BW6Pj-00041w-TH for dhcwg@ietf.org; Fri, 04 Jun 2004 00:34:43 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BW6Oo-0003fk-00 for dhcwg@ietf.org; Fri, 04 Jun 2004 00:33:47 -0400 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx with esmtp (Exim 4.12) id 1BW6Ny-0002xP-00 for dhcwg@ietf.org; Fri, 04 Jun 2004 00:32:54 -0400 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HYR00301OM01V@mailout1.samsung.com> for dhcwg@ietf.org; Fri, 04 Jun 2004 13:32:24 +0900 (KST) Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HYR0042OOLZOR@mailout1.samsung.com> for dhcwg@ietf.org; Fri, 04 Jun 2004 13:32:23 +0900 (KST) Received: from LocalHost ([75.2.47.54]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HYR006KVOLZ86@mmp1.samsung.com> for dhcwg@ietf.org; Fri, 04 Jun 2004 13:32:23 +0900 (KST) Date: Fri, 04 Jun 2004 13:32:21 +0900 From: Heejin Jang To: dhcwg@ietf.org Message-id: <01c601c449ec$ee4f2410$362f024b@LocalHost> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook Express 6.00.2800.1409 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal 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 Content-Transfer-Encoding: 7BIT Cc: Alper Yegin , jinchoe Subject: [dhcwg] I-D ACTION:draft-jang-dhc-haopt-00.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7BIT Hello all, I have posted an I-D that describes a DHCP-based mechanism to distribute dynamic discovery of MIPv6 HA and home subnet. Any feedback will be highly welcome. -------------------------------------------------------------------- A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : DHCP Option for Home Agent Discovery in MIPv6 Author(s) : Heejin Jang, Alper Yegin, Jinhyeok Choi Filename : draft-jang-dhc-haopt-00.txt Pages : 15 Date : 2004-6-2 This draft defines a DHCP-based scheme to enable dynamic discovery of Mobile IPv6 home agent address and home subnet. A new DHCP option is defined to carry the information from a DHCP server to the DHCP client running on the mobile node. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-jang-dhc-haopt-00.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-jang-dhc-haopt-00.txt". _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Jun 4 03:41:03 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18295; Fri, 4 Jun 2004 03:41:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BW9F8-0003z1-8K; Fri, 04 Jun 2004 03:35:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BW99F-0002nl-29 for dhcwg@megatron.ietf.org; Fri, 04 Jun 2004 03:29:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17254 for ; Fri, 4 Jun 2004 03:29:51 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BW99C-0007Wp-Ti for dhcwg@ietf.org; Fri, 04 Jun 2004 03:29:51 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BW98C-0007Ao-00 for dhcwg@ietf.org; Fri, 04 Jun 2004 03:28:49 -0400 Received: from intermail.se.dataphone.net ([212.37.1.50]) by ietf-mx with esmtp (Exim 4.12) id 1BW97G-0006nq-00 for dhcwg@ietf.org; Fri, 04 Jun 2004 03:27:50 -0400 Received: from [213.115.251.202] (account budm@weird-solutions.com HELO offset.weird.se) by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.1.5) with ESMTP id 7405109; Fri, 04 Jun 2004 09:27:47 +0200 From: Bud Millwood Organization: Weird Solutions, Inc. To: dhcwg@ietf.org Subject: Re: [dhcwg] IPR disclosure and Date: Fri, 4 Jun 2004 09:21:21 +0200 User-Agent: KMail/1.6.2 References: <200406031713.KAA27382@redback.com> In-Reply-To: <200406031713.KAA27382@redback.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406040921.21986.budm@weird-solutions.com> 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: Naiming Shen X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bud Millwood List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit On Thursday 03 June 2004 19:13, Naiming Shen wrote: > "free of IPR claims" ?-) > > Have you read the page on http://www.ietf.org/ipr.html ? Yes, I've read that page. I was quite satisfied with Motorola's IPR statement concerning relay agent options (http://www.ietf.org/ietf/IPR/MOTOROLA-DHCP-AGENT-OPTIONS). You're right, though, I didn't mean "free of IPR claims" - what I meant was "free to implement", in the same manner as is stated in the above link. - Bud Bud Millwood Weird Solutions, Inc. http://www.weird-solutions.com tel: +46 8 758 3700 fax: +46 8 758 3687 mailto:budm@weird-solutions.com _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Jun 4 11:22:36 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16664; Fri, 4 Jun 2004 11:22:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BWGNQ-0007UY-BU; Fri, 04 Jun 2004 11:13:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BWGGv-0006BZ-Pz for dhcwg@megatron.ietf.org; Fri, 04 Jun 2004 11:06:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15847 for ; Fri, 4 Jun 2004 11:06:15 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BWGGu-0007GB-UI for dhcwg@ietf.org; Fri, 04 Jun 2004 11:06:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BWGG2-0006vs-00 for dhcwg@ietf.org; Fri, 04 Jun 2004 11:05:22 -0400 Received: from rimp1.nist.gov ([129.6.16.226] helo=smtp.nist.gov) by ietf-mx with esmtp (Exim 4.12) id 1BWGFY-0006bI-00 for dhcwg@ietf.org; Fri, 04 Jun 2004 11:04:52 -0400 Received: from postmark.nist.gov (pushme.nist.gov [129.6.16.92]) by smtp.nist.gov (8.12.10/8.12.10) with ESMTP id i54F4ckZ021383 for ; Fri, 4 Jun 2004 11:04:38 -0400 Received: from nist.gov (itg-03.antd.nist.gov [129.6.50.182]) by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id i54F4U4A025587 for ; Fri, 4 Jun 2004 11:04:30 -0400 (EDT) Message-ID: <40C08F7E.169F3C61@nist.gov> Date: Fri, 04 Jun 2004 11:04:30 -0400 From: "M-K. Shin" Organization: ETRI/NIST X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,ko MIME-Version: 1.0 To: dhcwg@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-NIST-MailScanner: Found to be clean X-MailScanner-From: mshin@nist.gov 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [dhcwg] [Fwd] I-D ACTION:draft-shin-dhc-dhcpv6-opt-ipv4-prefix-00.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit Hi, all, I've submitted a new draft relating to IPv4 prefix options for DHCPv6. This mechanism is intended as one of dual stack requirements for DHCPv6 during the period of co-existence of IPv4 and IPv6. Any feedback will be highly welcome. Thanks,. Myung-Ki. -- ----------------------------------------------------------------- A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IPv4 Prefix Options for DHCPv6 Author(s) : M. Shin, H-C. Lee Filename : draft-shin-dhc-dhcpv6-opt-ipv4-prefix-00.txt Pages : 7 Date : 2004-6-3 This document describes new options for Dynamic Host Configuration Protocol (DHCP) version 6 that provide a mechanism for the delegation of IPv4 prefixes. Through these options, a delegating router can delegate IPv4 prefixes to authorized requesting devices. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-shin-dhc-dhcpv6-opt-ipv4-prefix-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request at ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Mon Jun 7 00:15:39 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06030; Mon, 7 Jun 2004 00:15:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXBOY-0002pP-CX; Mon, 07 Jun 2004 00:05:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXBJD-0002J6-Lk for dhcwg@megatron.ietf.org; Mon, 07 Jun 2004 00:00:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05300 for ; Mon, 7 Jun 2004 00:00:25 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXBJB-0000O8-Qy for dhcwg@ietf.org; Mon, 07 Jun 2004 00:00:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXBIB-00001T-00 for dhcwg@ietf.org; Sun, 06 Jun 2004 23:59:24 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 1BXBGC-0007Ey-00; Sun, 06 Jun 2004 23:57:21 -0400 Received: from paul3 (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i574EZvx025405; Mon, 7 Jun 2004 13:14:35 +0900 (KST) Message-ID: <005801c44c43$77d40540$c470fe81@etri.re.kr> From: "Jaehoon Paul Jeong" To: References: <006d01c44907$92d5a450$c470fe81@etri.re.kr> <004b01c4492d$08626a80$c470fe81@etri.re.kr> Date: Mon, 7 Jun 2004 12:56:50 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=2.2 required=5.0 tests=AWL,MIME_BASE64_LATIN, MIME_BASE64_TEXT autolearn=no version=2.60 Cc: V6OPS WG , DHC WG , IPv6 DNS Configuration , IPv6 WG Subject: [dhcwg] Re: IPv6 Host Configuration of Recursive DNS Server X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0119634468==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org --===============0119634468== Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: base64 SGkgYWxsLA0KDQpGb3IgMSB3ZWVrLCB0aGVyZSBoYXZlIGJlZW4gbm8gY29tbWVudHMgb24gb3Vy IElQdjYgRE5TIENvbmZpZ3VyYWlvbi4NCiAgaHR0cDovL3d3dy5hZGhvYy42YW50cy5uZXQvfnBh dWwvcHVibGljYXRpb25zL2lldGYtaW50ZXJuZXQtZHJhZnQvZHJhZnQtaWV0Zi1kbnNvcC1pcHY2 LWRucy1jb25maWd1cmF0aW9uLTAwLnR4dA0KDQpEb2VzIGl0IG1lYW4gdGhhdCB0aGVyZSBpcyBu byBwcm9ibGVtIGFib3V0IHRoaXMgZHJhZnQgYW5kIGl0IGlzIG9rIHRvIHJlcXVlc3QgV0dMQz8g Oi0pDQoNClBhdWwNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJKYWVo b29uIFBhdWwgSmVvbmciIDxwYXVsQGV0cmkucmUua3I+DQpUbzogPGRuc29wQGxpc3RzLnVvcmVn b24uZWR1Pg0KQ2M6ICJJUHY2IEROUyBDb25maWd1cmF0aW9uIiA8ZG5zb3AtdjZjb25mQG5vbWlu dW0uY29tPg0KU2VudDogVGh1cnNkYXksIEp1bmUgMDMsIDIwMDQgMjozOCBQTQ0KU3ViamVjdDog UmU6IElQdjYgSG9zdCBDb25maWd1cmF0aW9uIG9mIFJlY3Vyc2l2ZSBETlMgU2VydmVyDQoNCg0K PiBUaGVyZSBpcyBzb21lIHByb2JsZW0gb2YgIGNvbHVtbiBhbGlnbm1lbnQgYXQgb3VyIGRyYWZ0 Lg0KPiBZb3UgY2FuIGZpbmQgYSBmaXhlZCB2ZXJzaW9uIGF0IHRoZSBmb2xsb3dpbmcgc2l0ZToN Cj4gIGh0dHA6Ly93d3cuYWRob2MuNmFudHMubmV0L35wYXVsL3B1YmxpY2F0aW9ucy9pZXRmLWlu dGVybmV0LWRyYWZ0L2RyYWZ0LWlldGYtZG5zb3AtaXB2Ni1kbnMtY29uZmlndXJhdGlvbi0wMC50 eHQNCj4gDQo+IFRoYW5rcy4NCj4gDQo+IFBhdWwNCj4gDQo+IC0tLS0tIE9yaWdpbmFsIE1lc3Nh Z2UgLS0tLS0gDQo+IEZyb206ICJKYWVob29uIFBhdWwgSmVvbmciIDxwYXVsQGV0cmkucmUua3I+ DQo+IFRvOiA8ZG5zb3BAbGlzdHMudW9yZWdvbi5lZHU+DQo+IENjOiAiSVB2NiBETlMgQ29uZmln dXJhdGlvbiIgPGRuc29wLXY2Y29uZkBub21pbnVtLmNvbT4NCj4gU2VudDogVGh1cnNkYXksIEp1 bmUgMDMsIDIwMDQgMTA6MTAgQU0NCj4gU3ViamVjdDogSVB2NiBIb3N0IENvbmZpZ3VyYXRpb24g b2YgUmVjdXJzaXZlIEROUyBTZXJ2ZXINCj4gDQo+IA0KPiA+IEhlbGxvIEROU09QIG1lbWJlcnMs DQo+ID4gDQo+ID4gQXMgeW91IGtub3csIGEgbmV3IGRyYWZ0IGhhcyBiZWVuIHB1Ymxpc2hlZCBm b3IgSVB2NiBIb3N0IENvbmZpZ3VyYXRpb24gb2YgRE5TIFNlcnZlciBJbmZvcm1hdGlvbiBBcHBy b2FjaGVzOg0KPiA+ICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1p ZXRmLWRuc29wLWlwdjYtZG5zLWNvbmZpZ3VyYXRpb24tMDAudHh0DQo+ID4gDQo+ID4gRm9yIGEg bG9uZyB0aW1lLCBETlMgRGlzY292ZXJ5IGhhcyBiZWVuIGRpc2N1c3NlZCBhdCBib3RoIElQdjYg YW5kIEROU09QIHdvcmtpbmcgZ3JvdXBzLg0KPiA+IFRoZSBsb25nIGRpc2N1c3Npb24gc2VlbXMg dG8gYmUgcmVzb2x2ZWQgdGhyb3VnaCB0aGlzIGRyYWZ0Lg0KPiA+IA0KPiA+IEluIHRoaXMgZHJh ZnQsIHRocmVlIGFwcHJvYWNoZXMgYXJlIHN1Z2dlc3RlZDogKGEpIFJBIG9wdGlvbiwgKGIpIERI Q1B2NiBvcHRpb24sIGFuZA0KPiA+IChjKSBXZWxsLWtub3duIGFueWNhc3QgYWRkcmVzc2VzIGZv ciBSZWN1cnNpdmUgRE5TIFNlcnZlcnMuDQo+ID4gV2UsIGF1dGhvcnMsIHVzZWQgIkROUyBDb25m aWd1cmF0aW9uIiBpbnN0ZWFkIG9mICJETlMgRGlzY292ZXJ5IiBiZWNhdXNlIHJlY3Vyc2l2ZSBE TlMgc2VydmVyIGFkZHJlc3MgaXMgDQo+ID4gb25seSBjb25maWd1cmVkIGluIElQdjYgaG9zdCwg bm90IGdlbmVyYXRpbmcgRE5TIHNlcnZlciBhZGRyZXNzIGxpa2UgaW4gSVB2NiBhZGRyZXNzIGF1 dG9jb25maWd1cmF0aW9uLg0KPiA+IA0KPiA+IFRoaXMgZHJhZnQgZm9jdXNlcyBvbiBkZXNjcmli aW5nIHRoZSBhdHRyaWJ1dGVzIG9mIHRocmVlIGFwcHJvYWNoZXMgYW5kIHN1Z2dlc3RpbmcgZm91 ciBhcHBsaWNhYmxlIHNjZW5hcmlvczoNCj4gPiAoYSkgSVNQIG5ldHdvcmssIChiKSBFbnRlcnBy aXNlIG5ldHdvcmssIChjKSAzR1BQIG5ldHdvcmssIChkKSBVbm1hbmFnZWQgbmV0d29yay4NCj4g PiANCj4gPiBUaHJvdWdoIHlvdXIgcmV2aWV3IGFuZCBjb21tZW50cywgdGhpcyB3aWxsIGJlIHB1 Ymxpc2hlZCBhcyBJbmZvcm1hdGlvbmFsIFJGQyBhY2NvcmRpbmcgdG8gb3VyIG1pbGVzdG9uZXMu DQo+ID4gSU1ITywgaWYgbmVjZXNzYXJ5LCB0aGUgZHJhZnRzIG9mIHR3byBvdGhlciBhcHByb2Fj aGVzIGV4Y2VwdCBESENQdjYgb3B0aW9uIHdpbGwgYmUgZGV2ZWxvcGVkIGludG8gc2VwYXJhdGUg UkZDcy4NCj4gPiANCj4gPiBUaGFua3MuDQo+ID4gDQo+ID4gUGF1bCwgDQo+ID4gSVB2NiBETlMg Q29uZmlndXJhdGlvbiBEZXNpZ24gVGVhbS4NCj4gPiANCj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPiBKYWVob29uIFBhdWwgSmVv bmcgKFJlc2VhcmNoIEVuZ2luZWVyKQ0KPiA+IFRFTC4gKzgyLTQyLTg2MC0xNjY0DQo+ID4gTW9i aWxlICs4Mi0xNi03MTEtMTc2NQ0KPiA+IDE2MSBHYWplb25nLWRvbmcgWXVzZW9uZy1ndSwgRGFl amVvbiAzMDUtMzUwLCBLb3JlYQ0KPiA+IE5HSSBTdGFuZGFyZGl6YXRpb24gUmVzZWFyY2ggVGVh bS9QRUMvRVRSSQ0KPiA+IEhvbWVwYWdlOiBodHRwOi8vd3d3LmFkaG9jLjZhbnRzLm5ldC9+cGF1 bA0KPiA+IA0KPiA= --===============0119634468== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============0119634468==-- From dhcwg-bounces@ietf.org Mon Jun 7 04:31:02 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01361; Mon, 7 Jun 2004 04:31:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXFUH-0000pP-Lk; Mon, 07 Jun 2004 04:28:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXFPH-00088e-Ll for dhcwg@megatron.ietf.org; Mon, 07 Jun 2004 04:22:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00980 for ; Mon, 7 Jun 2004 04:22:57 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXFPF-0002kH-8F for dhcwg@ietf.org; Mon, 07 Jun 2004 04:22:57 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXFOM-0002Kg-00 for dhcwg@ietf.org; Mon, 07 Jun 2004 04:22:02 -0400 Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de) by ietf-mx with esmtp (Exim 4.12) id 1BXFMJ-0001Mj-00 for dhcwg@ietf.org; Mon, 07 Jun 2004 04:19:55 -0400 Received: from venus.office (venus.office [10.1.1.11]) by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id i578JPDW089810 for ; Mon, 7 Jun 2004 10:19:26 +0200 (CEST) Received: from netlab.nec.de (neptune.office [10.1.1.83]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 4889C1346F6 for ; Mon, 7 Jun 2004 10:19:25 +0200 (CEST) Message-ID: <40C4251D.1040207@netlab.nec.de> Date: Mon, 07 Jun 2004 10:19:41 +0200 From: Cristian Cadar User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dhcwg@ietf.org References: <4.3.2.7.2.20040602095512.029c0b28@flask.cisco.com> In-Reply-To: <4.3.2.7.2.20040602095512.029c0b28@flask.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.35 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [dhcwg] Next DHCPv6 Interoperability Test Event X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit Hi All, I just let you know that the next DHCPv6 interop. test event will be held in Cannes on October 11-15, 2004 organized by ETSI, you can find details here: http://dhcpv6.ccrle.nec.de/index.htm Cristian _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Mon Jun 7 05:15:32 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02927; Mon, 7 Jun 2004 05:15:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXG8J-0000kx-SM; Mon, 07 Jun 2004 05:09:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXG5s-0000GT-9q for dhcwg@megatron.ietf.org; Mon, 07 Jun 2004 05:07:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02464 for ; Mon, 7 Jun 2004 05:06:58 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXG5p-0002L9-UY for dhcwg@ietf.org; Mon, 07 Jun 2004 05:06:58 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXG4r-0001zA-00 for dhcwg@ietf.org; Mon, 07 Jun 2004 05:05:57 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 1BXG3m-0001JN-00; Mon, 07 Jun 2004 05:04:51 -0400 Received: from paul3 (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i579LMvx028785; Mon, 7 Jun 2004 18:21:22 +0900 (KST) Message-ID: <010501c44c6e$50f0ac00$c470fe81@etri.re.kr> From: "Jaehoon Paul Jeong" To: "Christian Huitema" , References: Date: Mon, 7 Jun 2004 18:03:34 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=2.2 required=5.0 tests=AWL,MIME_BASE64_LATIN, MIME_BASE64_TEXT autolearn=no version=2.60 Cc: V6OPS WG , DHC WG , IPv6 WG , Satapati Subject: [dhcwg] Re: IPv6 Host Configuration of Recursive DNS Server X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0825089655==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org --===============0825089655== Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: base64 VGhhbmtzIGZvciB5b3VyIGdvb2QgY29tbWVudHMuDQoNCkkgYWdyZWUgd2l0aCB5b3UgYXQgeW91 ciB0d28gcG9pbnRzLg0KRXNwZWNpYWxseSwgbnVtYmVyIDIgaXMgdGhlIG9waW5pb24gb2YgeW91 ciBjby1hdXRob3IsIFN1cmVzaC4NCkhlIHdpbGwgc3BlYWsgYWJvdXQgeW91ciBvcGluaW9uLg0K DQpQYXVsDQoNCj4tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KPkZyb206ICJDaHJpc3Rp YW4gSHVpdGVtYSIgPGh1aXRlbWFAd2luZG93cy5taWNyb3NvZnQuY29tPg0KPlRvOiAiSmFlaG9v biBQYXVsIEplb25nIiA8cGF1bEBldHJpLnJlLmtyPjsgPGRuc29wQGxpc3RzLnVvcmVnb24uZWR1 Pg0KPlNlbnQ6IE1vbmRheSwgSnVuZSAwNywgMjAwNCAxOjI4IFBNDQo+U3ViamVjdDogUkU6IElQ djYgSG9zdCBDb25maWd1cmF0aW9uIG9mIFJlY3Vyc2l2ZSBETlMgU2VydmVyDQo+DQo+VHdvIHBv aW50czoNCj4NCj4xKSBJbiB0aGUgZGlzYWR2YW50YWdlIG9mIERIQ1B2NiBzZWN0aW9uLCB5b3Ug b3VnaHQgdG8gbWVudGlvbiB0aGF0DQo+dGhlcmUgaXMgYSBlbnN1cmUgdGhhdCB0aGUgREhDUCBz ZXJ2ZXIgYWx3YXlzIHJldHVybnMgYW4gdXAtdG8tZGF0ZQ0KPnZhbHVlIGZvciB0aGUgYWRkcmVz cyBvZiB0aGUgcHJlZmVycmVkIHJlY3Vyc2l2ZSBETlMgc2VydmVyLiBJbiBsYXJnZQ0KPm5ldHdv cmtzLCB0aGlzIGlzIG5vdCB0cml2aWFsOiB0aGUgbm90aW9uIG9mIHdoaWNoIHNlcnZlciBpcyBj bG9zZXN0DQo+ZGVwZW5kcyBvbiByb3V0aW5nIGNvbmZpZ3VyYXRpb24gYW5kIG9uIHNlcnZlciBz dGF0dXMsIGFsbCBvZiB3aGljaCBhcmUNCj5keW5hbWljLiBJbiBjb250cmFzdCwgdGhlIGFueWNh c3QgYXBwcm9hY2ggZ3VhcmFudGVlcyB0aGF0IHRoZSByZXF1ZXN0DQo+d2lsbCByZWFjaCB0aGUg Y2xvc2VzdCBzZXJ2ZXIuDQo+DQo+MikgSW4gdGhlIHVubWFuYWdlZCBjYXNlLCB5b3Ugd3Jvbmds eSBhc3N1bWUgdGhhdCBjYXNlIEMgaXMgImxpa2UgY2FzZQ0KPkEiLiBJbiBmYWN0LCBpdCBpcyBt b3JlIGxpa2UgY2FzZSBCOiBpZiBhIGdhdGV3YXkgcHJvdmlkZXMgSVB2Ng0KPmNvbm5lY3Rpdml0 eSBieSBtYW5hZ2luZyB0dW5uZWxzLCB0aGVuIGl0IGlzIGFsc28gc3VwcG9zZWQgdG8gcHJvdmlk ZQ0KPmFjY2VzcyB0byBhIHJlY3Vyc2l2ZSBETlMgc2VydmVyLg0KPg0KPj4gLS0tLS1PcmlnaW5h bCBNZXNzYWdlLS0tLS0NCj4+IEZyb206IGlwdjYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmlw djYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEphZWhvb24gUGF1bCBKZW9uZw0KPj4g U2VudDogU3VuZGF5LCBKdW5lIDA2LCAyMDA0IDg6NTcgUE0NCj4+IFRvOiBkbnNvcEBsaXN0cy51 b3JlZ29uLmVkdQ0KPj4gQ2M6IFY2T1BTIFdHOyBESEMgV0c7IElQdjYgRE5TIENvbmZpZ3VyYXRp b247IElQdjYgV0cNCj4+IFN1YmplY3Q6IFJlOiBJUHY2IEhvc3QgQ29uZmlndXJhdGlvbiBvZiBS ZWN1cnNpdmUgRE5TIFNlcnZlcg0KPj4gDQo+PiBIaSBhbGwsDQo+PiANCj4+IEZvciAxIHdlZWss IHRoZXJlIGhhdmUgYmVlbiBubyBjb21tZW50cyBvbiBvdXIgSVB2NiBETlMgQ29uZmlndXJhaW9u Lg0KPj4NCj4+aHR0cDovL3d3dy5hZGhvYy42YW50cy5uZXQvfnBhdWwvcHVibGljYXRpb25zL2ll dGYtaW50ZXJuZXQtZHJhZnQvZHJhZnQtaWV0Zi1kbnNvcC1pcHY2LWRucy1jb25maWd1cmF0aW9u LTAwLnR4dA0KPj4gDQo+PiBEb2VzIGl0IG1lYW4gdGhhdCB0aGVyZSBpcyBubyBwcm9ibGVtIGFi b3V0IHRoaXMgZHJhZnQgYW5kIGl0IGlzIG9rIHRvDQo+PiByZXF1ZXN0IFdHTEM/IDotKQ0KPj4g DQo+PiBQYXVs --===============0825089655== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============0825089655==-- From dhcwg-bounces@ietf.org Mon Jun 7 07:07:20 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07149; Mon, 7 Jun 2004 07:07:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXHrt-0000wP-9o; Mon, 07 Jun 2004 07:00:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXBTl-0004ZZ-9x for dhcwg@megatron.ietf.org; Mon, 07 Jun 2004 00:11:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05749 for ; Mon, 7 Jun 2004 00:11:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXBTj-0003aT-39 for dhcwg@ietf.org; Mon, 07 Jun 2004 00:11:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXBSU-0003FO-00 for dhcwg@ietf.org; Mon, 07 Jun 2004 00:10:03 -0400 Received: from vacation.karoshi.com ([198.32.6.68] helo=karoshi.com) by ietf-mx with esmtp (Exim 4.12) id 1BXBRy-0002wI-00; Mon, 07 Jun 2004 00:09:30 -0400 Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by karoshi.com (8.12.8/8.12.8) with ESMTP id i5749UW4018865; Mon, 7 Jun 2004 04:09:30 GMT Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id i5749U4I018862; Mon, 7 Jun 2004 04:09:30 GMT Date: Mon, 7 Jun 2004 04:09:30 +0000 From: bmanning@vacation.karoshi.com To: dnsop-v6conf@nominum.com Message-ID: <20040607040930.GA18426@vacation.karoshi.com.> References: <006d01c44907$92d5a450$c470fe81@etri.re.kr> <004b01c4492d$08626a80$c470fe81@etri.re.kr> <005801c44c43$77d40540$c470fe81@etri.re.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005801c44c43$77d40540$c470fe81@etri.re.kr> User-Agent: Mutt/1.4.1i X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60 X-Mailman-Approved-At: Mon, 07 Jun 2004 07:00:29 -0400 Cc: V6OPS WG , dnsop@lists.uoregon.edu, IPv6 WG , DHC WG Subject: [dhcwg] Re: IPv6 Host Configuration of Recursive DNS Server X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org No. It means: ) there have been over 100 new drafts released ) there are a number of concerns with the approaches taken that have been rasied in past mtgs that are not mentioned or addressed And ... most folks have day jobs that are -not- related to this specific issue. --bill On Mon, Jun 07, 2004 at 12:56:50PM +0900, Jaehoon Paul Jeong wrote: > Hi all, > > For 1 week, there have been no comments on our IPv6 DNS Configuraion. > http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-00.txt > > Does it mean that there is no problem about this draft and it is ok to request WGLC? :-) > > Paul > > ----- Original Message ----- > From: "Jaehoon Paul Jeong" > To: > Cc: "IPv6 DNS Configuration" > Sent: Thursday, June 03, 2004 2:38 PM > Subject: Re: IPv6 Host Configuration of Recursive DNS Server > > > > There is some problem of column alignment at our draft. > > You can find a fixed version at the following site: > > http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-00.txt > > > > Thanks. > > > > Paul > > > > ----- Original Message ----- > > From: "Jaehoon Paul Jeong" > > To: > > Cc: "IPv6 DNS Configuration" > > Sent: Thursday, June 03, 2004 10:10 AM > > Subject: IPv6 Host Configuration of Recursive DNS Server > > > > > > > Hello DNSOP members, > > > > > > As you know, a new draft has been published for IPv6 Host Configuration of DNS Server Information Approaches: > > > http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-configuration-00.txt > > > > > > For a long time, DNS Discovery has been discussed at both IPv6 and DNSOP working groups. > > > The long discussion seems to be resolved through this draft. > > > > > > In this draft, three approaches are suggested: (a) RA option, (b) DHCPv6 option, and > > > (c) Well-known anycast addresses for Recursive DNS Servers. > > > We, authors, used "DNS Configuration" instead of "DNS Discovery" because recursive DNS server address is > > > only configured in IPv6 host, not generating DNS server address like in IPv6 address autoconfiguration. > > > > > > This draft focuses on describing the attributes of three approaches and suggesting four applicable scenarios: > > > (a) ISP network, (b) Enterprise network, (c) 3GPP network, (d) Unmanaged network. > > > > > > Through your review and comments, this will be published as Informational RFC according to our milestones. > > > IMHO, if necessary, the drafts of two other approaches except DHCPv6 option will be developed into separate RFCs. > > > > > > Thanks. > > > > > > Paul, > > > IPv6 DNS Configuration Design Team. > > > > > > ------------------------------------------------------ > > > Jaehoon Paul Jeong (Research Engineer) > > > TEL. +82-42-860-1664 > > > Mobile +82-16-711-1765 > > > 161 Gajeong-dong Yuseong-gu, Daejeon 305-350, Korea > > > NGI Standardization Research Team/PEC/ETRI > > > Homepage: http://www.adhoc.6ants.net/~paul > > > > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Mon Jun 7 07:07:55 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07189; Mon, 7 Jun 2004 07:07:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXHru-0000zv-RS; Mon, 07 Jun 2004 07:00:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXBnJ-0001aD-1f for dhcwg@megatron.ietf.org; Mon, 07 Jun 2004 00:31:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06824 for ; Mon, 7 Jun 2004 00:31:30 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXBnH-0002CF-0B for dhcwg@ietf.org; Mon, 07 Jun 2004 00:31:31 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXBm5-0001mW-00 for dhcwg@ietf.org; Mon, 07 Jun 2004 00:30:18 -0400 Received: from mail3.microsoft.com ([131.107.3.123]) by ietf-mx with esmtp (Exim 4.12) id 1BXBkf-00018U-00; Mon, 07 Jun 2004 00:28:49 -0400 Received: from mail5.microsoft.com ([157.54.6.156]) by mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Sun, 6 Jun 2004 21:28:19 -0700 Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(6.0.3790.1039); Sun, 6 Jun 2004 21:28:36 -0700 Received: from 157.54.5.25 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sun, 06 Jun 2004 21:28:19 -0700 Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Sun, 6 Jun 2004 21:28:30 -0700 Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Sun, 6 Jun 2004 21:28:18 -0700 Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069); Sun, 6 Jun 2004 21:28:36 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 6 Jun 2004 21:28:14 -0700 Message-ID: Thread-Topic: IPv6 Host Configuration of Recursive DNS Server Thread-Index: AcRMRYQUVUKEAKHKQkWMfI6c5EYsCgAAaPiw From: "Christian Huitema" To: "Jaehoon Paul Jeong" , X-OriginalArrivalTime: 07 Jun 2004 04:28:36.0546 (UTC) FILETIME=[E66C4220:01C44C47] 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 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Mon, 07 Jun 2004 07:00:29 -0400 Cc: V6OPS WG , DHC WG , IPv6 DNS Configuration , IPv6 WG Subject: [dhcwg] RE: IPv6 Host Configuration of Recursive DNS Server X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Two points: 1) In the disadvantage of DHCPv6 section, you ought to mention that there is a ensure that the DHCP server always returns an up-to-date value for the address of the preferred recursive DNS server. In large networks, this is not trivial: the notion of which server is closest depends on routing configuration and on server status, all of which are dynamic. In contrast, the anycast approach guarantees that the request will reach the closest server. 2) In the unmanaged case, you wrongly assume that case C is "like case A". In fact, it is more like case B: if a gateway provides IPv6 connectivity by managing tunnels, then it is also supposed to provide access to a recursive DNS server. > -----Original Message----- > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of > Jaehoon Paul Jeong > Sent: Sunday, June 06, 2004 8:57 PM > To: dnsop@lists.uoregon.edu > Cc: V6OPS WG; DHC WG; IPv6 DNS Configuration; IPv6 WG > Subject: Re: IPv6 Host Configuration of Recursive DNS Server >=20 > Hi all, >=20 > For 1 week, there have been no comments on our IPv6 DNS Configuraion. > http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft- > ietf-dnsop-ipv6-dns-configuration-00.txt >=20 > Does it mean that there is no problem about this draft and it is ok to > request WGLC? :-) >=20 > Paul >=20 > ----- Original Message ----- > From: "Jaehoon Paul Jeong" > To: > Cc: "IPv6 DNS Configuration" > Sent: Thursday, June 03, 2004 2:38 PM > Subject: Re: IPv6 Host Configuration of Recursive DNS Server >=20 >=20 > > There is some problem of column alignment at our draft. > > You can find a fixed version at the following site: > > http://www.adhoc.6ants.net/~paul/publications/ietf-internet- > draft/draft-ietf-dnsop-ipv6-dns-configuration-00.txt > > > > Thanks. > > > > Paul > > > > ----- Original Message ----- > > From: "Jaehoon Paul Jeong" > > To: > > Cc: "IPv6 DNS Configuration" > > Sent: Thursday, June 03, 2004 10:10 AM > > Subject: IPv6 Host Configuration of Recursive DNS Server > > > > > > > Hello DNSOP members, > > > > > > As you know, a new draft has been published for IPv6 Host > Configuration of DNS Server Information Approaches: > > > http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns- > configuration-00.txt > > > > > > For a long time, DNS Discovery has been discussed at both IPv6 and > DNSOP working groups. > > > The long discussion seems to be resolved through this draft. > > > > > > In this draft, three approaches are suggested: (a) RA option, (b) > DHCPv6 option, and > > > (c) Well-known anycast addresses for Recursive DNS Servers. > > > We, authors, used "DNS Configuration" instead of "DNS Discovery" > because recursive DNS server address is > > > only configured in IPv6 host, not generating DNS server address like > in IPv6 address autoconfiguration. > > > > > > This draft focuses on describing the attributes of three approaches > and suggesting four applicable scenarios: > > > (a) ISP network, (b) Enterprise network, (c) 3GPP network, (d) > Unmanaged network. > > > > > > Through your review and comments, this will be published as > Informational RFC according to our milestones. > > > IMHO, if necessary, the drafts of two other approaches except DHCPv6 > option will be developed into separate RFCs. > > > > > > Thanks. > > > > > > Paul, > > > IPv6 DNS Configuration Design Team. > > > > > > ------------------------------------------------------ > > > Jaehoon Paul Jeong (Research Engineer) > > > TEL. +82-42-860-1664 > > > Mobile +82-16-711-1765 > > > 161 Gajeong-dong Yuseong-gu, Daejeon 305-350, Korea > > > NGI Standardization Research Team/PEC/ETRI > > > Homepage: http://www.adhoc.6ants.net/~paul > > > > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Mon Jun 7 15:36:34 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10391; Mon, 7 Jun 2004 15:36:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXPq1-00011D-PV; Mon, 07 Jun 2004 15:31:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXPla-000889-Ue for dhcwg@megatron.ietf.org; Mon, 07 Jun 2004 15:26:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09188 for ; Mon, 7 Jun 2004 15:26:40 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXPlZ-0003QS-AY for dhcwg@ietf.org; Mon, 07 Jun 2004 15:26:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXPkY-0002sT-00 for dhcwg@ietf.org; Mon, 07 Jun 2004 15:25:39 -0400 Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1BXPjX-0002K5-00; Mon, 07 Jun 2004 15:24:35 -0400 Received: from [10.0.1.3] (dsl093-162-248.tus1.dsl.speakeasy.net [66.93.162.248]) by toccata.fugue.com (Postfix) with ESMTP id 742991B2E68; Mon, 7 Jun 2004 14:22:55 -0500 (CDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <49DF15FA-B8B8-11D8-B212-000A95D9C74C@fugue.com> Content-Transfer-Encoding: 7bit From: Ted Lemon Subject: Re: [dhcwg] RE: IPv6 Host Configuration of Recursive DNS Server Date: Mon, 7 Jun 2004 12:24:26 -0700 To: "Christian Huitema" X-Mailer: Apple Mail (2.618) 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: IPv6 DNS Configuration , IPv6 WG , dnsop@lists.uoregon.edu, V6OPS WG , DHC WG , Jaehoon Paul Jeong X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit On Jun 6, 2004, at 9:28 PM, Christian Huitema wrote: > 1) In the disadvantage of DHCPv6 section, you ought to mention that > there is a ensure that the DHCP server always returns an up-to-date > value for the address of the preferred recursive DNS server. In large > networks, this is not trivial: the notion of which server is closest > depends on routing configuration and on server status, all of which are > dynamic. In contrast, the anycast approach guarantees that the request > will reach the closest server. > This is really more of an advantage of using an anycast address over using a unicast address, and has nothing to do with DHCPv6. If you want this functionality, you can use DHCPv6 to configure the anycast address, or you can hard-code the anycast address. The question we're trying to address is really how we configure nodes as they come on to the network, not with what we configure them. The reason that anycast has a place in this discussion is that it's the only possible value that you could just hard-code into the client and thereby bypass configuration altogether. We need to be very careful in discussing this draft not to get confused about what the draft does. It does not say "this is the solution." Rather, it is essentially a sales tool which tries to present the advantages and disadvantages of each option, so that the buyer (the IESG, I guess) can make an informed choice between them. So please let us not digress into deep, detailed discussions about why the other guy's choice is wrong - just say what's good about the proposal you favor, and if you want to be honest, discuss any disadvantages of which you're aware. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Tue Jun 8 04:43:24 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11063; Tue, 8 Jun 2004 04:43:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXc8n-0000Wg-E0; Tue, 08 Jun 2004 04:39:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXc1x-0007d6-MS for dhcwg@megatron.ietf.org; Tue, 08 Jun 2004 04:32:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10288 for ; Tue, 8 Jun 2004 04:32:23 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXc1u-0004Mm-Pq for dhcwg@ietf.org; Tue, 08 Jun 2004 04:32:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXc0w-0003gp-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 04:31:23 -0400 Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132]) by ietf-mx with smtp (Exim 4.12) id 1BXc0B-00030q-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 04:30:35 -0400 Received: (qmail 10129 invoked from network); 8 Jun 2004 08:24:50 -0000 Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134) by necom830.hpcl.titech.ac.jp with SMTP; 8 Jun 2004 08:24:50 -0000 Message-ID: <40C57A46.2030805@necom830.hpcl.titech.ac.jp> Date: Tue, 08 Jun 2004 17:35:18 +0900 From: Masataka Ohta User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: dnsop-v6conf@nominum.com References: In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Content-Transfer-Encoding: 7bit Cc: V6OPS WG , dnsop@lists.uoregon.edu, Jaehoon Paul Jeong , IPv6 WG , DHC WG Subject: [dhcwg] WLAN (was Re: IPv6 Host Configuration of Recursive DNS Server) X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit Dear all; The problem is rather generic than DNS configuration. But... I know ND is wrong. That is, I know it is wrong to have generic link protocols ignoring link specific properties and has been pondering on how such protocols suffer. I just recently noticed that WLAN (802.11*) is not very good at supporting ND (nor DHCP nor any broadcast/multicast protocol). Because WLAN use CSMA/CA, it needs ACK for reliable transmission by confirming that each packet reaches its destination without collision. However, with broadcast/multicast packets, there is no ACK for an obvious reason. If WLAN is lightly loaded, it is not a serious problem. However, if WLAN is heavily loaded, ND (and DHCP and any broadcast/ multicast protocol) works poorly. Note that MIPv6 works poorly too. Still, management beacon frames are transmitted frequently and expected to carry information in a long run. So, it is possible to piggyback broadcast/multicast part of address resolution and autoconfiguration (maybe and routing) in reserved fields of beacon frames. Though it is possible to use some data frame frequently transmitted like beacon frams, it make the already congested WLAN worse. Anyway, the fundamental mistake is to try not to have link specific ways to perform address resolution and autoconfiguration. DHCP simply needs link specific ways of DHCP discover. ND needs, IMHO, a lot more. Note that modifying WLAN protocol to use PIFS is not enough unless combined with frequent transmission. Masataka Ohta _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Tue Jun 8 08:37:34 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22886; Tue, 8 Jun 2004 08:37:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXfne-0002cp-H0; Tue, 08 Jun 2004 08:33:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXfgQ-0000IG-IF for dhcwg@megatron.ietf.org; Tue, 08 Jun 2004 08:26:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22499 for ; Tue, 8 Jun 2004 08:26:25 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXfgQ-0003hh-0T for dhcwg@ietf.org; Tue, 08 Jun 2004 08:26:26 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXffS-00030Y-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 08:25:27 -0400 Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132]) by ietf-mx with smtp (Exim 4.12) id 1BXfeh-0002He-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 08:24:39 -0400 Received: (qmail 11203 invoked from network); 8 Jun 2004 12:18:54 -0000 Received: from yahoobb219001188015.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.1.188.15) by necom830.hpcl.titech.ac.jp with SMTP; 8 Jun 2004 12:18:54 -0000 Message-ID: <40C5B11F.2000301@necom830.hpcl.titech.ac.jp> Date: Tue, 08 Jun 2004 21:29:19 +0900 From: Masataka Ohta User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: Mohacsi Janos References: <40C57A46.2030805@necom830.hpcl.titech.ac.jp> <20040608130454.R73638@mignon.ki.iif.hu> In-Reply-To: <20040608130454.R73638@mignon.ki.iif.hu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: dnsop-v6conf@nominum.com, IPv6 WG , DHC WG , V6OPS WG , dnsop@lists.uoregon.edu, Jaehoon Paul Jeong Subject: [dhcwg] Re: WLAN (was Re: IPv6 Host Configuration of Recursive DNS Server) X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit Mohacsi Janos wrote: >>I know ND is wrong. That is, I know it is wrong to have generic >>link protocols ignoring link specific properties and has been >>pondering on how such protocols suffer. > I think ND is not wrong. ND is wrong, because it was designed to be applicable to all the link types. ND deployed multicast only because some ATM guy said NBMA was capable of not broadcast but multicast, which is totaly denied by the current ND RFC stating that ND may not be applicable to NBMA. > There is a clear need for better support to > discover the link parameters, but it is necessary for mostly to the > routing protocols. If you are talking about QoS, it is a totally different topic. >>However, with broadcast/multicast packets, there is no ACK for >>an obvious reason. > The IPv4 ARP is not better either, as you found. No, ARP is no better, of course. Given the point to multipoint nature of infrastructure WLAN, and given the probability of hidden terminals, ARP is overkill. Just send all the packets to the base station, IP address of which should be piggy-backed in beacon. As for ad-hoc WLAN, it does not work well with multiple link hops that it is a bad idea at L2. > I think the WLAN should > be improved some way to support multicast in some form. It is inherent to CSMA/CA link that broadcast/multicast is unreliable. Our (IETF) approach has been to make IP work over as much link technology as possible. The solution has been never bother to have standard way of address resolution. > I think autoconfiguration can be treated differently, than address > resolution. ND as stand for "Neighbour" Discovery is a very good > improvement to ARP and transport specific things... However, there are people who think ND should take care of everything including DNS configuration. >>ND needs, IMHO, a lot more. > What do you think? Because of its bloated set of features, I think ND hopeless. Masataka Ohta _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Tue Jun 8 08:51:21 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23644; Tue, 8 Jun 2004 08:51:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXfy5-0004sJ-3u; Tue, 08 Jun 2004 08:44:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXepY-00058c-IX for dhcwg@megatron.ietf.org; Tue, 08 Jun 2004 07:31:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19530 for ; Tue, 8 Jun 2004 07:31:47 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXepX-0002rQ-TS for dhcwg@ietf.org; Tue, 08 Jun 2004 07:31:48 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXeoF-00024Z-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 07:30:27 -0400 Received: from mignon.ki.iif.hu ([193.6.222.240] helo=mail.ki.iif.hu) by ietf-mx with esmtp (Exim 4.12) id 1BXemz-0000bf-00; Tue, 08 Jun 2004 07:29:09 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id 7938D5686; Tue, 8 Jun 2004 13:28:37 +0200 (CEST) Received: from mail.ki.iif.hu ([127.0.0.1]) by localhost (mignon.ki.iif.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 73859-01-13; Tue, 8 Jun 2004 13:28:35 +0200 (CEST) Received: by mail.ki.iif.hu (Postfix, from userid 1003) id B4BB85635; Tue, 8 Jun 2004 13:28:35 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id B24615518; Tue, 8 Jun 2004 13:28:35 +0200 (CEST) Date: Tue, 8 Jun 2004 13:28:35 +0200 (CEST) From: Mohacsi Janos X-X-Sender: mohacsi@mignon.ki.iif.hu To: Masataka Ohta In-Reply-To: <40C57A46.2030805@necom830.hpcl.titech.ac.jp> Message-ID: <20040608130454.R73638@mignon.ki.iif.hu> References: <40C57A46.2030805@necom830.hpcl.titech.ac.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at mail.ki.iif.hu 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=none autolearn=no version=2.60 X-Mailman-Approved-At: Tue, 08 Jun 2004 08:44:34 -0400 Cc: dnsop-v6conf@nominum.com, IPv6 WG , DHC WG , V6OPS WG , dnsop@lists.uoregon.edu, Jaehoon Paul Jeong Subject: [dhcwg] Re: WLAN (was Re: IPv6 Host Configuration of Recursive DNS Server) X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Hi Masataka, On Tue, 8 Jun 2004, Masataka Ohta wrote: > Dear all; > > The problem is rather generic than DNS configuration. But... > > I know ND is wrong. That is, I know it is wrong to have generic > link protocols ignoring link specific properties and has been > pondering on how such protocols suffer. I think ND is not wrong. There is a clear need for better support to discover the link parameters, but it is necessary for mostly to the routing protocols. > > I just recently noticed that WLAN (802.11*) is not very good at > supporting ND (nor DHCP nor any broadcast/multicast protocol). > > Because WLAN use CSMA/CA, it needs ACK for reliable transmission > by confirming that each packet reaches its destination without > collision. > > However, with broadcast/multicast packets, there is no ACK for > an obvious reason. The IPv4 ARP is not better either, as you found. I think the WLAN should be improved some way to support multicast in some form. > > If WLAN is lightly loaded, it is not a serious problem. > > However, if WLAN is heavily loaded, ND (and DHCP and any broadcast/ > multicast protocol) works poorly. Note that MIPv6 works poorly > too. > > Still, management beacon frames are transmitted frequently > and expected to carry information in a long run. > > So, it is possible to piggyback broadcast/multicast part > of address resolution and autoconfiguration (maybe and > routing) in reserved fields of beacon frames. I think autoconfiguration can be treated differently, than address resolution. ND as stand for "Neighbour" Discovery is a very good improvement to ARP and transport specific things... Of course ND can get into trouble if no reply for ND requests (with soliticited node multicast address)... > > Though it is possible to use some data frame frequently > transmitted like beacon frams, it make the already congested > WLAN worse. > > Anyway, the fundamental mistake is to try not to have link > specific ways to perform address resolution and autoconfiguration. > > DHCP simply needs link specific ways of DHCP discover. > > ND needs, IMHO, a lot more. What do you think? > > Note that modifying WLAN protocol to use PIFS is not enough > unless combined with frequent transmission. I agree. Janos Mohacsi Network Engineer, Research Associate NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Tue Jun 8 15:53:51 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20088; Tue, 8 Jun 2004 15:53:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXmVJ-0006dM-Bm; Tue, 08 Jun 2004 15:43:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXlPs-0001k6-He for dhcwg@megatron.ietf.org; Tue, 08 Jun 2004 14:33:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15151 for ; Tue, 8 Jun 2004 14:33:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXlPp-0004kz-8k for dhcwg@ietf.org; Tue, 08 Jun 2004 14:33:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXlOp-0003vD-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 14:32:39 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1BXlNi-0002HM-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 14:31:30 -0400 Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 08 Jun 2004 11:31:13 -0700 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i58IUwiU022776 for ; Tue, 8 Jun 2004 11:30:59 -0700 (PDT) Received: from rdroms-w2k01.cisco.com ([161.44.65.119]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJF86248; Tue, 8 Jun 2004 14:30:57 -0400 (EDT) Message-Id: <4.3.2.7.2.20040608142939.020bcd98@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 08 Jun 2004 14:30:54 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [dhcwg] dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org This message announces a WG last call on "Detection of Network Attachment (DNA) in IPv4" . The last call will conclude at 5PM EDT on 2004-06-25. Please respond to this WG last call. If you support acceptance of the document without change, respond with a simple acknowledgment, so that support for the document can be assessed. draft-ietf-dhc-dna-ipv4-07.txt addresses the problem of detecting attachment to an IPv4 network. The time required to detect movement (or lack of movement) between subnets, and to obtain (or continue to use) a valid IPv4 address may be significant as a fraction of the total delay in moving between points of attachment. This specification synthesizes experience garnered over the years in the deployment of hosts supporting ARP, DHCP and IPv4 Link-Local addresses, in order to optimize detection of network attachment by mobile hosts.This draft is available as http://www.ietf.org/internet-drafts/draft-ietf-dhc-dna-ipv4-07.txt - Ralph Droms _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Mon Jun 14 03:13:56 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10278; Mon, 14 Jun 2004 03:13:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BZlaK-0004Nx-66; Mon, 14 Jun 2004 03:08:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BZlNm-0001gj-Nw for dhcwg@megatron.ietf.org; Mon, 14 Jun 2004 02:55:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09369 for ; Mon, 14 Jun 2004 02:55:49 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BZlNk-0006iO-G0 for dhcwg@ietf.org; Mon, 14 Jun 2004 02:55:48 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BZlMk-0006UD-00 for dhcwg@ietf.org; Mon, 14 Jun 2004 02:54:46 -0400 Received: from av2-1-sn3.vrr.skanova.net ([81.228.9.107]) by ietf-mx with esmtp (Exim 4.12) id 1BZlMP-0006Gh-00 for dhcwg@ietf.org; Mon, 14 Jun 2004 02:54:25 -0400 Received: by av2-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 7BC4A37EDB; Mon, 14 Jun 2004 08:53:55 +0200 (CEST) Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net [81.228.9.177]) by av2-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 6E90A37E4F; Mon, 14 Jun 2004 08:53:55 +0200 (CEST) Received: from chardonnay.levkowetz.com (h195n1fls311o871.telia.com [213.64.174.195]) by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 58FFD38009; Mon, 14 Jun 2004 08:53:55 +0200 (CEST) Received: from chardonnay ([127.0.0.1]) by chardonnay.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1BZlLt-0000Vf-00; Mon, 14 Jun 2004 08:53:53 +0200 Date: Mon, 14 Jun 2004 08:53:52 +0200 From: Henrik Levkowetz To: Ralph Droms Subject: Re: [dhcwg] dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt Message-Id: <20040614085352.1a03bbf9@chardonnay> In-Reply-To: <4.3.2.7.2.20040608142939.020bcd98@flask.cisco.com> References: <4.3.2.7.2.20040608142939.020bcd98@flask.cisco.com> X-Mailer: Sylpheed version 0.9.10claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 Content-Transfer-Encoding: 7bit Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit I support the advancement of this document. Henrik Tuesday 8 June 2004, Ralph Droms wrote: > > This message announces a WG last call on "Detection of Network > Attachment (DNA) in IPv4" . The last > call will conclude at 5PM EDT on 2004-06-25. > > Please respond to this WG last call. If you support acceptance of the > document without change, respond with a simple acknowledgment, so that > support for the document can be assessed. > > draft-ietf-dhc-dna-ipv4-07.txt addresses the problem of detecting > attachment to an IPv4 network. The time required to detect movement > (or lack of movement) between subnets, and to obtain (or continue to > use) a valid IPv4 address may be significant as a fraction of the > total delay in moving between points of attachment. This > specification synthesizes experience garnered over the years in the > deployment of hosts supporting ARP, DHCP and IPv4 Link-Local > addresses, in order to optimize detection of network attachment by > mobile hosts.This draft is available as > http://www.ietf.org/internet-drafts/draft-ietf-dhc-dna-ipv4-07.txt _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Tue Jun 15 01:11:56 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08569; Tue, 15 Jun 2004 01:11:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ba60D-0005Gz-7M; Tue, 15 Jun 2004 00:56:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ba5oP-0001cz-Qw for dhcwg@megatron.ietf.org; Tue, 15 Jun 2004 00:44:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07276 for ; Tue, 15 Jun 2004 00:44:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Ba5oN-0001uB-Qa for dhcwg@ietf.org; Tue, 15 Jun 2004 00:44:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ba5nW-0001bm-00 for dhcwg@ietf.org; Tue, 15 Jun 2004 00:43:47 -0400 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx with esmtp (Exim 4.12) id 1Ba5mh-00010g-00 for dhcwg@ietf.org; Tue, 15 Jun 2004 00:42:55 -0400 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HZC003012EOEZ@mailout1.samsung.com> for dhcwg@ietf.org; Tue, 15 Jun 2004 13:42:24 +0900 (KST) Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HZC00CWA2ENW3@mailout1.samsung.com> for dhcwg@ietf.org; Tue, 15 Jun 2004 13:42:23 +0900 (KST) Received: from LocalHost ([168.219.202.103]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HZC00C4C2EN7R@mmp2.samsung.com> for dhcwg@ietf.org; Tue, 15 Jun 2004 13:42:23 +0900 (KST) Date: Tue, 15 Jun 2004 13:43:07 +0900 From: Soohong Daniel Park To: Dhcwg Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7BIT Subject: [dhcwg] DHCP-based Solutions in the "Analysis of IPv6 Tunnel End-point Discovery Mechamisms" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7BIT Hi all, I am not sure how may guys read below draft which was proposed in the v6ops WG to analyze IPv6 TEP Discovery mechanism. This draft cited one draft and wrote several drawbacks. I already proposed this cited draft (03 version currently). http://www.ietf.org/internet-drafts/draft-daniel-dhc-ipv6in4-opt-03.txt I'd like to reflect DHC's comments/feedbacks on the revision as 04. Please let me know your view on this. =================== Subject:Analysis of IPv6 Tunnel End-point Discovery Mechamisms http://www.ietf.org/internet-drafts/draft-palet-v6ops-tun-auto-disc-01.txt 3.4 DHCP-based Solutions In most situations, the users receive the IPv4 information by means of an IPv4 DHCP server. Consequently, one of the parameters to be provided by the DHCP server could be the tunnel end-point address, e.g., as described in [12]. This approach has several drawbacks: o It requires upgrading the DHCP client/server implementations to support this feature. o It is restricted to the local ISP. That is, it will not be effective if the local ISP doesn't provide this parameter. This could be also be an advantage considering that the this would only support the tunnels provided by the local ISP, which would probably be of good quality. o It will not work if DHCP client is not used. DHCP is omitted especially in many dial-up scenarios, where only PPP is used; DHCP is not used in some (advanced) xDSL setups which use static routing. Also, some managed networks do not use DHCP. Still, in many cases, DHCP is used between a customer and the ISP. o If a router is providing local DHCP information (e.g., an ADSL router), the tunnel end-point information would have to be automatically proxied to the "local DHCP", or manually configured on the router to propagate to the hosts in the case that the router is not activating the tunnel itself. o It requires manual configuration/update of the ISP's DHCP servers when there are changes to the tunnel end-points, similar to updating DNS, NTP, etc. servers. - Daniel (Soohong Daniel Park) - Mobile Platform Lab. Samsung Electronics. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 17 03:28:25 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06877; Thu, 17 Jun 2004 03:28:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BarFT-0001wO-SL; Thu, 17 Jun 2004 03:23:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BarCP-0001EK-Kr for dhcwg@megatron.ietf.org; Thu, 17 Jun 2004 03:20:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06447 for ; Thu, 17 Jun 2004 03:20:36 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BarCK-0005DQ-Ls for dhcwg@ietf.org; Thu, 17 Jun 2004 03:20:32 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BarBI-0004qn-00 for dhcwg@ietf.org; Thu, 17 Jun 2004 03:19:28 -0400 Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1BarAX-0004VK-00 for dhcwg@ietf.org; Thu, 17 Jun 2004 03:18:41 -0400 Received: from ocean.jinmei.org (unknown [2001:200:0:8002:200:39ff:fe5e:cfd7]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id DB5B51525D for ; Thu, 17 Jun 2004 16:18:44 +0900 (JST) Date: Thu, 17 Jun 2004 16:18:51 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: dhcwg@ietf.org User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII 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=none autolearn=no version=2.60 Subject: [dhcwg] questions about DHCPv6 authentication X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org (Trying to resend it from a different mail address...sorry if this is a duplicate.) Hello, I have a couple of questions on DHCPv6 authentication described in RFC3315 (Section 21). 1. the RFC says in 21.4.4.4 as follows: 21.4.4.4. Sending Information-request Messages If the server has selected a key for the client in a previous message exchange (see section 21.4.5.1), the client MUST use the same key to generate the authentication information throughout the session. I don't really understand this part...does this assume a separate Solicit-Advertise (or Reply if rapid-commit option is used?) exchanges to negotiate the key? If so, what if the server and/or the client only implement the "stateless" subset described in RFC3736? Note that RFC3736 says: Authenticated DHCP, as described in sections 21 and 22.11 of the DHCP specification [1], can be used to avoid attacks mounted through the stateless DHCP service. I read this to mean that Authenticated DHCP can be used for implementations only support RFC3736. But how can such implementations select the key without the "previous message exchange"? 2. RFC3315 says in Section 21.4.2 (Message Validation) that If the MAC computed by the receiver does not match the MAC contained in the authentication option, the receiver MUST discard the DHCP message. It seems to me this part of the specification some other parts of Section 21.4: 2-1) in Section 21.4.4.2, the RFC allows the client to respond to an Advertise even if it fails on authentication: Client behavior, if no Advertise messages include authentication information or pass the validation test, is controlled by local policy on the client. According to client policy, the client MAY choose to respond to an Advertise message that has not been authenticated. Doesn't this contradict with Section 21.4.2? 2-2) this can be a more serious issue. The RFC says in Section 21.4.4.4 that: If the Reply fails to pass the validation test, the client MUST restart the DHCP configuration process by sending a Solicit message. Doesn't this contradict with Section 21.4.2? Moreover, it seems to me that restarting the configuration process in this case can open up a possibility of DoS attack. What is the background of this specification? Any hints or answers would be highly appreciated. Thanks in advance, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 17 07:14:43 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19406; Thu, 17 Jun 2004 07:14:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bauez-00087b-AH; Thu, 17 Jun 2004 07:02:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BauYQ-0005Un-5Q for dhcwg@megatron.ietf.org; Thu, 17 Jun 2004 06:55:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17776 for ; Thu, 17 Jun 2004 06:55:31 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BauYL-0002HF-0y for dhcwg@ietf.org; Thu, 17 Jun 2004 06:55:29 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BauXB-0001o3-00 for dhcwg@ietf.org; Thu, 17 Jun 2004 06:54:18 -0400 Received: from kummerog.uni-muenster.de ([128.176.184.156]) by ietf-mx with esmtp (Exim 4.12) id 1BauW9-0001OM-00 for dhcwg@ietf.org; Thu, 17 Jun 2004 06:53:14 -0400 Received: by kummerog.uni-muenster.de (Postfix, from userid 1000) id 08F6B27466; Thu, 17 Jun 2004 12:53:18 +0200 (CEST) Date: Thu, 17 Jun 2004 12:53:18 +0200 From: Christian Strauf To: dhcwg@ietf.org Subject: Re: [dhcwg] questions about DHCPv6 authentication Message-ID: <20040617105317.GB11343@kummerog.uni-muenster.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i 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 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Excuse possible dupes, I had trouble with my mailer. Jinmei-san, > 1. the RFC says in 21.4.4.4 as follows: > > 21.4.4.4. Sending Information-request Messages > > If the server has selected a key for the client in a previous message > exchange (see section 21.4.5.1), the client MUST use the same key to > generate the authentication information throughout the session. > > I don't really understand this part...does this assume a separate > Solicit-Advertise (or Reply if rapid-commit option is used?) > exchanges to negotiate the key? If so, what if the server and/or > the client only implement the "stateless" subset described in > RFC3736? Note that RFC3736 says: > > Authenticated DHCP, as described in > sections 21 and 22.11 of the DHCP specification [1], can be used to > avoid attacks mounted through the stateless DHCP service. > > I read this to mean that Authenticated DHCP can be used for > implementations only support RFC3736. But how can such > implementations select the key without the "previous message > exchange"? the key distribution is done out-of-band, as stated in section 21.4.3. Therefore, no inital exchange for key distribution is necessary. The way I understand this section is that clients must keep using the same key they've been using for any previous message exchange that included an authentication option. Stateless DHCPv6 clients are free to use authentication options with pre-shared keys the same way that RFC3315 clients do. > 2. RFC3315 says in Section 21.4.2 (Message Validation) that > > If the MAC > computed by the receiver does not match the MAC contained in the > authentication option, the receiver MUST discard the DHCP message. > > It seems to me this part of the specification some other parts of > Section 21.4: > > 2-1) in Section 21.4.4.2, the RFC allows the client to respond to > an Advertise even if it fails on authentication: > > Client behavior, if no Advertise messages include authentication > information or pass the validation test, is controlled by local > policy on the client. According to client policy, the client MAY > choose to respond to an Advertise message that has not been > authenticated. > > Doesn't this contradict with Section 21.4.2? Yes, partly. I think the part that is contradictory is "[...] or pass the validation test [...]". This section clearly -- as you correctly identified in my eyes -- contradicts the quoted part of 21.4.2 above. I agree that a failed validation test is very critical and should not be open to local policy (i.e. no responses to these advertise messages should be made by the client in any case). The other part ("[...] no Advertise messages include authentication information [...]") may indeed be a matter of local policy. > 2-2) this can be a more serious issue. The RFC says in Section > 21.4.4.4 that: > > If the Reply > fails to pass the validation test, the client MUST restart the DHCP > configuration process by sending a Solicit message. > > Doesn't this contradict with Section 21.4.2? Moreover, it > seems to me that restarting the configuration process in this > case can open up a possibility of DoS attack. What is the > background of this specification? I think that it doesn't contradict section 21.4.2 but as a matter of fact is a logical consequence if validation tests fail. However, I agree 100% that this is a potentially dangerous behaviour because it can be used for DoS attacks on servers and clients. I think that this deserves to be addressed in the Security Considerations section because appropriate timeouts or similar should be in place to prevent this kind of attack by malicious hosts that send malformed replies that will fail validation tests. > Any hints or answers would be highly appreciated. Thanks in advance, I hope that you find my comments useful. Christian _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 17 08:19:40 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23658; Thu, 17 Jun 2004 08:19:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BavnY-0008NW-3Q; Thu, 17 Jun 2004 08:15:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXtL4-0005jc-2v for dhcwg@megatron.ietf.org; Tue, 08 Jun 2004 23:01:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22008 for ; Tue, 8 Jun 2004 23:01:15 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXtL2-0006d5-0U for dhcwg@ietf.org; Tue, 08 Jun 2004 23:01:16 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXtK5-0005lj-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 23:00:17 -0400 Received: from mail.seventwentyfour.com ([209.167.50.21]) by ietf-mx with esmtp (Exim 4.12) id 1BXtJL-0004dx-00 for dhcwg@ietf.org; Tue, 08 Jun 2004 22:59:31 -0400 Received: from seven ([192.168.1.137]) by mail.seventwentyfour.com (VisNetic.MailServer.v6.2.2.0) with SMTP id KNR37895 for ; Tue, 08 Jun 2004 22:59:02 -0400 Date: Tue, 08 Jun 2004 22:59:02 -0400 X-Mailer: 724Mailer V4 From: Roy at SEVENtwentyfour To: dhcwg@ietf.org MIME-Version: 1.0 X-724-ID: SMO3KH X-724-SID: 1059421141 X-724-UID: 0x0 X-724-To: dhcwg@ietf.org X-724-Template: 5 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit Message-Id: 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=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 17 Jun 2004 08:15:13 -0400 Subject: [dhcwg] Broken link in www.dhcp.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roy at SEVENtwentyfour List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit There appears to be a problem on this page of your site. On page http://www.dhcp.org/ the link to http://www.dhcp.org/draft-ietf-dhc-dhcpv6-opt-XX-00.txt gives the error: Not found. As recommended by the Robot Guidelines, this email is to explain our robot's visit to your site, and to let you know about one of the problems we found. We don't store or publish the content of your pages, but rather use the link information to update our map of the World Wide Web. Are these reports helpful? I'd love some feedback. If you prefer not to receive these occasional error notices please let me know. Roy Bryant ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Roy Bryant, roybryant@seventwentyfour.com President SEVENtwentyfour Inc. http://www.seventwentyfour.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 17 08:27:35 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24347; Thu, 17 Jun 2004 08:27:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BavnY-0008Nb-Ce; Thu, 17 Jun 2004 08:15:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BaEom-0007iv-Mp for dhcwg@megatron.ietf.org; Tue, 15 Jun 2004 10:21:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20890 for ; Tue, 15 Jun 2004 10:21:39 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BaEol-0002VZ-Sb for dhcwg@ietf.org; Tue, 15 Jun 2004 10:21:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BaEnm-00026F-00 for dhcwg@ietf.org; Tue, 15 Jun 2004 10:20:39 -0400 Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1BaEmi-0001i7-00 for dhcwg@ietf.org; Tue, 15 Jun 2004 10:19:48 -0400 Received: from ocean.jinmei.org (unknown [2001:200:0:8002:200:39ff:fe5e:cfd7]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 8F7A11525D for ; Tue, 15 Jun 2004 23:19:30 +0900 (JST) Date: Tue, 15 Jun 2004 23:19:35 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: dhcwg@ietf.org User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII 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 X-Mailman-Approved-At: Thu, 17 Jun 2004 08:15:13 -0400 Subject: [dhcwg] questions about DHCPv6 authentication X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Hello, I have a couple of questions on DHCPv6 authentication described in RFC3315 (Section 21). 1. the RFC says in 21.4.4.4 as follows: 21.4.4.4. Sending Information-request Messages If the server has selected a key for the client in a previous message exchange (see section 21.4.5.1), the client MUST use the same key to generate the authentication information throughout the session. I don't really understand this part...does this assume a separate Solicit-Advertise (or Reply if rapid-commit option is used?) exchanges to negotiate the key? If so, what if the server and/or the client only implement the "stateless" subset described in RFC3736? Note that RFC3736 says: Authenticated DHCP, as described in sections 21 and 22.11 of the DHCP specification [1], can be used to avoid attacks mounted through the stateless DHCP service. I read this to mean that Authenticated DHCP can be used for implementations only support RFC3736. But how can such implementations select the key without the "previous message exchange"? 2. RFC3315 says in Section 21.4.2 (Message Validation) that If the MAC computed by the receiver does not match the MAC contained in the authentication option, the receiver MUST discard the DHCP message. It seems to me this part of the specification some other parts of Section 21.4: 2-1) in Section 21.4.4.2, the RFC allows the client to respond to an Advertise even if it fails on authentication: Client behavior, if no Advertise messages include authentication information or pass the validation test, is controlled by local policy on the client. According to client policy, the client MAY choose to respond to an Advertise message that has not been authenticated. Doesn't this contradict with Section 21.4.2? 2-2) this can be a more serious issue. The RFC says in Section 21.4.4.4 that: If the Reply fails to pass the validation test, the client MUST restart the DHCP configuration process by sending a Solicit message. Doesn't this contradict with Section 21.4.2? Moreover, it seems to me that restarting the configuration process in this case can open up a possibility of DoS attack. What is the background of this specification? Any hints or answers would be highly appreciated. Thanks in advance, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 17 08:55:25 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25940; Thu, 17 Jun 2004 08:55:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Baw9l-0008JQ-I7; Thu, 17 Jun 2004 08:38:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BavxT-0002Cw-Q2 for dhcwg@megatron.ietf.org; Thu, 17 Jun 2004 08:25:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24251 for ; Thu, 17 Jun 2004 08:25:30 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BavxT-0001u3-8Q for dhcwg@ietf.org; Thu, 17 Jun 2004 08:25:31 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BavwZ-0001ah-00 for dhcwg@ietf.org; Thu, 17 Jun 2004 08:24:36 -0400 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Bavvh-0000zD-00 for dhcwg@ietf.org; Thu, 17 Jun 2004 08:23:41 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 17 Jun 2004 05:24:22 -0700 Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i5HCN7LZ015662 for ; Thu, 17 Jun 2004 05:23:07 -0700 (PDT) Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-1-72.cisco.com [10.86.240.72]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJM31967; Thu, 17 Jun 2004 08:23:06 -0400 (EDT) Message-Id: <4.3.2.7.2.20040617082201.020b4a10@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 17 Jun 2004 08:23:02 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [dhcwg] *DRAFT* schedule for dhc WG meeting in San Diego X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org TUESDAY, August 3, 2004 0900-1130 Morning Sessions APP simple SIP for Instant Messaging and Presence Leveraging Extensions WG INT dhc Dynamic Host Configuration WG IRTF dtnrg Delay-tolerant Networking Research Group OPS psamp Packet Sampling WG RTG ccamp Common Control and Measurement Plane WG TSV avt Audio/Video Transport WG _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 17 15:25:49 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07644; Thu, 17 Jun 2004 15:25:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bb2FF-0008Ib-Ll; Thu, 17 Jun 2004 15:08:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bb23G-0005Fx-NT for dhcwg@megatron.ietf.org; Thu, 17 Jun 2004 14:55:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04534 for ; Thu, 17 Jun 2004 14:55:53 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bb23F-0000Ik-Lh for dhcwg@ietf.org; Thu, 17 Jun 2004 14:55:53 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bb219-0007eu-00 for dhcwg@ietf.org; Thu, 17 Jun 2004 14:53:43 -0400 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 1Bb20T-0007CO-00 for dhcwg@ietf.org; Thu, 17 Jun 2004 14:53:01 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 17 Jun 2004 11:54:51 +0000 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i5HIqALZ003188 for ; Thu, 17 Jun 2004 11:52:11 -0700 (PDT) Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-118.cisco.com [10.86.242.118]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJM71291; Thu, 17 Jun 2004 14:52:05 -0400 (EDT) Message-Id: <4.3.2.7.2.20040617140757.02c4c540@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 17 Jun 2004 14:51:32 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [dhcwg] WGLC for dnsop WG doc "IPv6 Host Configuration of DNS Server Information Approaches" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org The IESG has requested that the dnsop WG compose a document that describes mechanisms for configuration of DNS server information in hosts. The purpose of the document is to describe the alternative mechanisms and give an analysis of the alternatives in several operational scenarios. The IESG will use this document to determine if additional protocol work in configuration of DNS server information in hosts will be chartered in any WGs. The dnsop WG is conducting a WG last call on this document, "IPv6 Host Configuration of DNS Server Information Approaches", draft-ietf-dnsop-ipv6-dns-configuration-01.txt. The dnsop WG announcement is included below. Because one of the three mechanisms considered in this document is the DHCPv6 "DNS Configuration Options" (RFC 3646), I encourage the dhc WG to review the draft. Please post constructive comments about whether this document fairly describes the mechanisms and issues in DNS server information configuration to dnsop@lists.uoregon.edu. - Ralph --------------------------------- From: David Meyer Folks This note starts the WG Last Call for comments on draft-ietf-dnsop-ipv6-dns-configuration-01.txt, "IPv6 Host Configuration of DNS Server Information Approaches". It can be found on ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-configuration-01.txt Please review the document carefully, and send your feedback to the list. Please also indicate whether or not you believe that this document is ready to go to the IESG. Note that this is a somewhat unusual case as the IESG requested this document. This Last Call will end on 30 June 2004 at 1400 PDT (UTC/GMT-7). Thanks, Dave & Rob . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Jun 18 04:11:33 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04917; Fri, 18 Jun 2004 04:11:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BbEBh-0001Gk-CM; Fri, 18 Jun 2004 03:53:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BbDkj-0003pb-Ee for dhcwg@megatron.ietf.org; Fri, 18 Jun 2004 03:25:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03114 for ; Fri, 18 Jun 2004 03:25:32 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BbDkh-00046P-87 for dhcwg@ietf.org; Fri, 18 Jun 2004 03:25:31 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BbDji-0003mu-00 for dhcwg@ietf.org; Fri, 18 Jun 2004 03:24:31 -0400 Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1BbDig-0003NC-00 for dhcwg@ietf.org; Fri, 18 Jun 2004 03:23:26 -0400 Received: from ocean.jinmei.org (unknown [3ffe:501:100f:1010:4dec:218e:82b5:1997]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 9F61B1525D; Fri, 18 Jun 2004 16:23:26 +0900 (JST) Date: Fri, 18 Jun 2004 16:23:32 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Christian Strauf Subject: Re: [dhcwg] questions about DHCPv6 authentication In-Reply-To: <20040617105317.GB11343@kummerog.uni-muenster.de> References: <20040617105317.GB11343@kummerog.uni-muenster.de> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII 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 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Thanks for the response. >>>>> On Thu, 17 Jun 2004 12:53:18 +0200, >>>>> Christian Strauf said: >> I don't really understand this part...does this assume a separate >> Solicit-Advertise (or Reply if rapid-commit option is used?) >> exchanges to negotiate the key? If so, what if the server and/or >> the client only implement the "stateless" subset described in >> RFC3736? Note that RFC3736 says: (snip) >> I read this to mean that Authenticated DHCP can be used for >> implementations only support RFC3736. But how can such >> implementations select the key without the "previous message >> exchange"? > the key distribution is done out-of-band, as stated in section 21.4.3. > Therefore, no inital exchange for key distribution is necessary. I know that. Perhaps I was not clear enough, but I meant the following process by "negotiation the key": (we assume both the client and the server have a shared secret. It's okay) - the client sends a solicit message with an authentication option. - the server chooses one particular key identified by - the server sends an advertise message with an authentication option authenticated with the selected key - the client extracts the realm and key ID specified by the server from the advertise message. At this point, the client can identify a particular key to be used for authentication in this session. In fact, RFC3315 says: If the server has selected a key for the client in a previous message exchange (see section 21.4.5.1), ^^^^^^^^^^^^^^^^^^^^ and section 21.4.5.1 talks about a solicit-advertise exchange. > The way I > understand this section is that clients must keep using the same key they've > been using for any previous message exchange that included an authentication > option. Stateless DHCPv6 clients are free to use authentication options with > pre-shared keys the same way that RFC3315 clients do. Are you assuming the following procedure? - the client sends an information-request with an authentication option. - the server chooses one particular key identified by - the server sends a reply message with an authentication option authenticated with the selected key - the client extracts the realm and key ID specified by the server from the reply message. At this point, the client can identify a particular key to be used for authenticating the reply message. and, - if the client and the server ever make further exchanges of information-request and reply, they should use the same key used in the first exchange. (By the phrase of "use that same key for validating subsequent messages with the client.") If so, that *may* make sense. However, I think it's very hard to imply the above just from the description in RFC3315. And in that sense, I'd first like to know if this is the real intention of the RFC authors. >> 2. RFC3315 says in Section 21.4.2 (Message Validation) that >> >> If the MAC >> computed by the receiver does not match the MAC contained in the >> authentication option, the receiver MUST discard the DHCP message. >> >> It seems to me this part of the specification some other parts of >> Section 21.4: >> >> 2-1) in Section 21.4.4.2, the RFC allows the client to respond to >> an Advertise even if it fails on authentication: >> >> Client behavior, if no Advertise messages include authentication >> information or pass the validation test, is controlled by local >> policy on the client. According to client policy, the client MAY >> choose to respond to an Advertise message that has not been >> authenticated. >> >> Doesn't this contradict with Section 21.4.2? > Yes, partly. I think the part that is contradictory is "[...] or pass the > validation test [...]". This section clearly -- as you correctly identified in > my eyes -- contradicts the quoted part of 21.4.2 above. I agree that a failed > validation test is very critical and should not be open to local policy (i.e. > no responses to these advertise messages should be made by the client in any > case). > The other part ("[...] no Advertise messages include authentication information > [...]") may indeed be a matter of local policy. Okay, I tend to agree. >> 2-2) this can be a more serious issue. The RFC says in Section >> 21.4.4.4 that: >> >> If the Reply >> fails to pass the validation test, the client MUST restart the DHCP >> configuration process by sending a Solicit message. >> >> Doesn't this contradict with Section 21.4.2? Moreover, it >> seems to me that restarting the configuration process in this >> case can open up a possibility of DoS attack. What is the >> background of this specification? > I think that it doesn't contradict section 21.4.2 but as a matter of fact is a > logical consequence if validation tests fail. However, I agree 100% that this > is a potentially dangerous behaviour because it can be used for DoS attacks on > servers and clients. I think that this deserves to be addressed in the Security > Considerations section because appropriate timeouts or similar should be in > place to prevent this kind of attack by malicious hosts that send malformed > replies that will fail validation tests. Hmm, I'm not sure how appropriate timeouts can protect the attack, but at least I'm happy that I can share my concern on the threat with you. I'd still like to hear from others, particularly from the RFC authors, but so far it seems to me that the authentication mechanism will need some clarification. Does it make sense to write a separate draft like "clarifications on the DHCPv6 authentication mechanism"? JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Jun 18 05:53:06 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10183; Fri, 18 Jun 2004 05:53:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BbFu0-0001Th-1N; Fri, 18 Jun 2004 05:43:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BbFmg-0007oc-G9 for dhcwg@megatron.ietf.org; Fri, 18 Jun 2004 05:35:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09264 for ; Fri, 18 Jun 2004 05:35:40 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BbFmd-0001lK-OG for dhcwg@ietf.org; Fri, 18 Jun 2004 05:35:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BbFkj-0001Pj-00 for dhcwg@ietf.org; Fri, 18 Jun 2004 05:33:42 -0400 Received: from kummerog.uni-muenster.de ([128.176.184.156]) by ietf-mx with esmtp (Exim 4.12) id 1BbFjp-000154-00 for dhcwg@ietf.org; Fri, 18 Jun 2004 05:32:45 -0400 Received: by kummerog.uni-muenster.de (Postfix, from userid 1000) id 5343727585; Fri, 18 Jun 2004 11:32:45 +0200 (CEST) Date: Fri, 18 Jun 2004 11:32:45 +0200 From: Christian Strauf To: "JINMEI Tatuya / ?$B?@L@C#:H" Subject: Re: [dhcwg] questions about DHCPv6 authentication Message-ID: <20040618093245.GB9663@kummerog.uni-muenster.de> References: <20040617105317.GB11343@kummerog.uni-muenster.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i 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 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Jinmei-san, > > the key distribution is done out-of-band, as stated in section 21.4.3. > > Therefore, no inital exchange for key distribution is necessary. > I know that. Perhaps I was not clear enough, but I meant the > following process by "negotiation the key": > (we assume both the client and the server have a shared secret. It's > okay) > > - the client sends a solicit message with an authentication option. > - the server chooses one particular key identified by client DUID, key id> > - the server sends an advertise message with an authentication option > authenticated with the selected key > - the client extracts the realm and key ID specified by the server > from the advertise message. At this point, the client can identify > a particular key to be used for authentication in this session. > > In fact, RFC3315 says: > > If the server has selected a key for the client in a previous message > exchange (see section 21.4.5.1), > ^^^^^^^^^^^^^^^^^^^^ > and section 21.4.5.1 talks about a solicit-advertise exchange. thanks for the clarification. I can see the implications for Stateless DHCPv6 clients now. The problem is that RFC3315 keeps talking about using the Authentication Option in Solicit-Advertise exchanges for an initial key negotiation (also in 21.4). However, I don't see why the inclusion of an Authentication Option in an Information Request option shouldn't work as an initial key negotiation equally well. Clearly, this is not reflected in RFC3315 a.t.m.. Paragraph 21.4.4.4 would make perfect sense even for RFC3736 style exchanges but not with the reference to section 21.4.5.1. Paragraph 21.4 should probably also be more general without direct references to Solicit-Advertise exchanges. > > The way I > > understand this section is that clients must keep using the same key they've > > been using for any previous message exchange that included an authentication > > option. Stateless DHCPv6 clients are free to use authentication options with > > pre-shared keys the same way that RFC3315 clients do. > > Are you assuming the following procedure? [snip] > If so, that *may* make sense. However, I think it's very hard to > imply the above just from the description in RFC3315. And in that Yes, I agree with you that this needs clarification. > sense, I'd first like to know if this is the real intention of the RFC > authors. Good suggestion. I'm very interested in this as well. > I'd still like to hear from others, particularly from the RFC authors, > but so far it seems to me that the authentication mechanism will need > some clarification. Does it make sense to write a separate draft like > "clarifications on the DHCPv6 authentication mechanism"? I think it does. I've heard a number of questions regarding the security of DHCPv6 in enterprise scenarios (it was also addressed in 6NET meetings) and I believe that such a document may be a good reference for answering these questions and for further work on DHCPv6 authentication mechanisms (which is necessary in my eyes because the authentication mechanisms described in RFC3315, though being sufficient in a good number of scenarios, may be insufficient for some scenarios where e.g. X.509 based or some other form of authentication might be desirable). I also know of implementors who would appreciate a clarification document. Christian _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From nv33134@yahoo.com Sat Jun 19 02:55:56 2004 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06186 for ; Sat, 19 Jun 2004 02:55:56 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BbZlb-000723-Tn for dhc-archive@ietf.org; Sat, 19 Jun 2004 02:55:55 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BbZkQ-0006ZJ-00 for dhc-archive@ietf.org; Sat, 19 Jun 2004 02:54:43 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BbZju-0006EB-00; Sat, 19 Jun 2004 02:54:10 -0400 Received: from [220.125.247.152] (helo=ietf.org) by mx2.foretec.com with smtp (Exim 4.24) id 1BbZiy-0000m3-9b; Sat, 19 Jun 2004 02:53:37 -0400 From: "Apelo a João Paulo II:" To: dccp-request@ietf.org Subject: Livrai o Brasil da ação maléfica da esquerda católica! . ism X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 MIME-Version: 1.0 Content-Type: text/html Message-Id: Date: Sat, 19 Jun 2004 02:53:37 -0400 X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=10.7 required=5.0 tests=FORGED_MUA_EUDORA, FORGED_YAHOO_RCVD,FROM_ENDS_IN_NUMS,HTML_40_50,HTML_FONT_BIG, HTML_MESSAGE,LINES_OF_YELLING,MAILTO_SUBJ_REMOVE,MAILTO_TO_REMOVE, MAILTO_TO_SPAM_ADDR,MIME_HTML_NO_CHARSET,MIME_HTML_ONLY, SUBJ_HAS_SPACES,SUBJ_ILLEGAL_CHARS autolearn=no version=2.60 X-Spam-Report: * 1.0 SUBJ_HAS_SPACES Subject contains lots of white space * 0.9 FROM_ENDS_IN_NUMS From: ends in numbers * 0.5 HTML_40_50 BODY: Message is 40% to 50% HTML * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 HTML_FONT_BIG BODY: HTML has a big font * 0.0 LINES_OF_YELLING BODY: A WHOLE LINE OF YELLING DETECTED * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 1.3 MAILTO_SUBJ_REMOVE BODY: mailto URI includes removal text * 0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset * 1.1 MAILTO_TO_SPAM_ADDR URI: Includes a link to a likely spammer email * 0.0 MAILTO_TO_REMOVE URI: Includes a 'remove' email address * 2.7 SUBJ_ILLEGAL_CHARS Subject contains too many raw illegal characters * 0.5 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers * 1.9 FORGED_MUA_EUDORA Forged mail pretending to be from Eudora c0406tfpjpbrres2

(ref.: tcs) Está permitida a reprodução total ou parcial desta notícia; não é necessário citar a fonte: Atualidade Brasileira

A João Paulo II: "Livrai o Brasil da ação maléfica da esquerda católica!"

Filial apelo do Brasil pacífico e laborioso, angustiado pelo eclodir de conflitos que poderão levar o País a uma sangrenta guerra social

CIDADE DO VATICANO (AB) - É com preocupação que nosso povo, pacífico, laborioso e religioso, assiste ao eclodir de conflitos que poderão levá-lo a uma sangrenta guerra social. Muitos desses conflitos crescem pela agitação de sacerdotes e leigos da "esquerda católica", que apoiam soluções violentas para os problemas sociais e que contam com a omissão, quando não com o apoio ostensivo, de Prelados dos mais altos na Hierarquia eclesiástica brasileira.

É o que afirma, em extensa mensagem que acaba de chegar a S.S. João Paulo II, a Associação dos Fundadores da TFP - Tradição, Família e Propriedade (para receber gratuitamente, por e-mail, o texto completo, de 12 páginas, da carta a S.S. João Paulo II, clique no link: CartaJoaoPauloII:TextoCompletoGratuito).

Sob a égide da "esquerda católica", com a colaboração da Comissão Pastoral da Terra (CPT) e do Conselho Indigenista Missionário (CIMI) - órgãos da Conferencia Nacional dos Bispos Católicos (CNBB) - se articulam os tentáculos da ação subversiva, para encaminhar o País pelas sendas da miséria e da fome, acrescenta a carta. O próximo passo poderá ser uma guerrilha rural que leve ao Brasil a uma situação similar à da Colômbia. O quadro se vê agravado pela presença da "esquerda católica" no atual governo, cujos membros ocupam postos-chave a partir dos quais desenvolvem uma ação em prol da luta de classes.

A missiva faz referência a livros do Prof. Plinio Corrêa de Oliveira nos quais o autor denunciou a esquerda eclesiástica encastoada na CNBB, como sendo a força capaz de contaminar a opinião pública brasileira, pacata e conservadora, com as febricitações da demagogia revolucionária (Prof.Plinio:EnviarMaisInfo).

E conclui com um apelo: Santo Padre, não permitais que, em nome da Igreja, leigos, religiosos e até altos eclesiásticos conduzam nossa Pátria, que nasceu sob o signo da Cruz, para uma fratricida guerra social, tão avessa ao espírito cristão e à índole bondosa de nosso povo! Ouvi, Santo Padre, o apelo filial e angustiado que Vos dirigimos: "Salvai o Brasil da ação maléfica da esquerda católica!"

040611AB - Atualidade Brasileira

LINKS:

CartaJoaoPauloII:MinhaAdesão (ao clicar neste link, favor acrescentar nome completo, cidade e RG ou CIC; seu e-mail será impresso e enviado a Roma, junto com as demais adesões recebidas; pode incluir nomes e dados de familiares, amigos e colegas de trabalho, com o prévio consentimento destes)

CartaJoaoPauloII:Concordo ---- Discordo ---- EmTermos (em qualquer das três opções, escreva, de preferência, nome, cidade e RG ou CIC)

CartaJoaoPauloII:TextoCompletoGratuitoPorE-Mail

TELEFONES DE CONTATO:

Associação dos Fundadores da TFP - Tradição Família Propriedade

Tels.: (011) 3822-3241 (011) 3661-8545

Rua Avaré, 359 - 01243-030 - Bairro Pacaembu - São Paulo (SP)

POSTDATA 1:

Está no prelo o livreto "Pastoral da Terra e MST incendeiam o Brasil" (20 capítulos breves, 56 pp.). Para receber gratuitamente, por e-mail, o Índice e a Introdução, clique em:

Livro:DesejoReceberIntroGratuitamentePorE-Mail

Para adquirir a edição impressa, clique no seguinte link, incluindo nome, endereço postal e telefone de contato, e receberá as instruções de pagamento (valor do exemplar, correio incluído: R$ 10,00)

Livro:DesejoAdquirirPorCorreio

POSTDATA 2:

Para conhecer detalhes inéditos das atuais estratégias da "esquerda católica" no Brasil e em outros países, sugerimos a leitura de 5 e-Books a respeito do Fórum Social Mundial de Porto Alegre (2001-2002-2003), do Fórum Social Brasileiro de Belo Horizonte (2003) e do Fórum Social Mundial de Bombay (2004). Receba via e-mail, links para fazer download gratuito dos 5 e-Books, clicando em:

ForumSocial:e-BooksGratuitos

LINK DE REMOÇÃO:

Retirar Caso já tiver efetuado anteriormente, sem sucesso, o pedido de remoção, lhe solicitamos o enorme favor de copiar e nos enviar na íntegra o denominado "Código Fonte da Mensagem", para nossos técnicos poderem verificar a qual e-mail, exatamente, lhe escrevemos, e assim tirá-lo imediatamente do Address Book. Clique acima da mensagem com o botão direito do "mouse", depois em "Propriedades", "Detalhes" e "Código Fonte". Solicitamos desculpas pelos inconvenientes ocasionados.

A difusão desta mensagem e seu conteúdo são de exclusiva responsabilidade da agência Atualidade Brasileira.

 From dhcwg-bounces@ietf.org Mon Jun 21 18:22:13 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09707; Mon, 21 Jun 2004 18:22:13 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcX0n-00037n-P8; Mon, 21 Jun 2004 18:11:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcWqM-0005B3-Mk for dhcwg@megatron.ietf.org; Mon, 21 Jun 2004 18:00:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06219 for ; Mon, 21 Jun 2004 18:00:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BcWqL-0002vL-AZ for dhcwg@ietf.org; Mon, 21 Jun 2004 18:00:45 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BcWoD-0002QN-00 for dhcwg@ietf.org; Mon, 21 Jun 2004 17:58:34 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx with esmtp (Exim 4.12) id 1BcWn9-0001yL-00 for dhcwg@ietf.org; Mon, 21 Jun 2004 17:57:27 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 21 Jun 2004 17:57:26 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i5LLutwc021413 for ; Mon, 21 Jun 2004 17:56:56 -0400 (EDT) Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-34.cisco.com [10.86.242.34]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJP22200; Mon, 21 Jun 2004 17:56:54 -0400 (EDT) Message-Id: <4.3.2.7.2.20040621175636.020da900@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 21 Jun 2004 17:56:52 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [dhcwg] REMINDER: dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org This message announces a WG last call on "Detection of Network Attachment (DNA) in IPv4" . The last call will conclude at 5PM EDT on 2004-06-25. Please respond to this WG last call. If you support acceptance of the document without change, respond with a simple acknowledgment, so that support for the document can be assessed. draft-ietf-dhc-dna-ipv4-07.txt addresses the problem of detecting attachment to an IPv4 network. The time required to detect movement (or lack of movement) between subnets, and to obtain (or continue to use) a valid IPv4 address may be significant as a fraction of the total delay in moving between points of attachment. This specification synthesizes experience garnered over the years in the deployment of hosts supporting ARP, DHCP and IPv4 Link-Local addresses, in order to optimize detection of network attachment by mobile hosts.This draft is available as http://www.ietf.org/internet-drafts/draft-ietf-dhc-dna-ipv4-07.txt - Ralph Droms _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Mon Jun 21 19:07:47 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13364; Mon, 21 Jun 2004 19:07:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcXhH-0002JT-4Y; Mon, 21 Jun 2004 18:55:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcXd5-00018m-Ny for dhcwg@megatron.ietf.org; Mon, 21 Jun 2004 18:51:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11810 for ; Mon, 21 Jun 2004 18:51:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BcXd4-0002FY-9f for dhcwg@ietf.org; Mon, 21 Jun 2004 18:51:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BcXc6-0001wv-00 for dhcwg@ietf.org; Mon, 21 Jun 2004 18:50:06 -0400 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 1BcXbM-0001Pq-00 for dhcwg@ietf.org; Mon, 21 Jun 2004 18:49:20 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 21 Jun 2004 15:51:58 +0000 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i5LMmlgI020948 for ; Mon, 21 Jun 2004 15:48:48 -0700 (PDT) Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-34.cisco.com [10.86.242.34]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJP26067; Mon, 21 Jun 2004 18:48:46 -0400 (EDT) Message-Id: <4.3.2.7.2.20040621184653.020ffcd8@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 21 Jun 2004 18:48:44 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [dhcwg] *DRAFT* Agenda for dhc WG meeting in San Diego X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Below is the draft scheduled time and agenda for the dhc WG meeting in San Diego. Let me know if you have additional items for the agenda. - Ralph ----- TUESDAY, August 3, 2004 0900-1130 Morning Sessions APP simple SIP for Instant Messaging and Presence Leveraging Extensions WG INT dhc Dynamic Host Configuration WG IRTF dtnrg Delay-tolerant Networking Research Group OPS psamp Packet Sampling WG RTG ccamp Common Control and Measurement Plane WG TSV avt Audio/Video Transport WG ----- DHC WG agenda - IETF 60 0900 Tue 2004-08-03 (tentative) (Last revised 06/21/2004 06:45 PM) ---------------------------------- Administrivia Ralph Droms 05 minutes Agenda bashing DNS zone suffix option for DHCPv6 Renxiang Yan 15 minutes Accept as dhc WG work item? Renumbering Requirements for Stateless DHCPv6 ??? 15 minutes Ready for WG last call? Lifetime Option for DHCPv6 ??? 15 minutes Ready for WG last call (depending on status of 'Renumbering Requirements')? IPv4 and IPv6 Dual-Stack Issues for DHCPv6 ??? 30 minutes Ready for WG last call? DHCP Option for Configuring IPv6-over-IPv4 Tunnels S. Daniel Park 15 minutes Accept as dhc WG work item? ----------- Total 95 minutes _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Tue Jun 22 14:14:49 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10922; Tue, 22 Jun 2004 14:14:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcpis-00059y-4p; Tue, 22 Jun 2004 14:10:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcm2y-0000V5-AF for dhcwg@megatron.ietf.org; Tue, 22 Jun 2004 10:14:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11112 for ; Tue, 22 Jun 2004 10:14:45 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bcm2x-0005o1-1N for dhcwg@ietf.org; Tue, 22 Jun 2004 10:14:47 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BckiS-0003dG-00 for dhcwg@ietf.org; Tue, 22 Jun 2004 08:49:33 -0400 Received: from alpha1.its.monash.edu.au ([130.194.1.1]) by ietf-mx with esmtp (Exim 4.12) id 1Bck0u-0006BR-00 for dhcwg@ietf.org; Tue, 22 Jun 2004 08:04:32 -0400 Received: from localhost ([130.194.13.83]) by vaxc.its.monash.edu.au (PMDF V6.1 #39306) with ESMTP id <01LBM30ZF3108WW11G@vaxc.its.monash.edu.au> for dhcwg@ietf.org; Tue, 22 Jun 2004 21:55:59 +1000 Received: from splat.its.monash.edu.au (localhost.its.monash.edu.au [127.0.0.1]) by localhost (Postfix) with ESMTP id ED0CB23C005 for ; Tue, 22 Jun 2004 21:55:58 +1000 (EST) Received: from mail1.monash.edu.au (bigted.its.monash.edu.au [130.194.11.60]) by splat.its.monash.edu.au (Postfix) with ESMTP id D8DE4164007 for ; Tue, 22 Jun 2004 21:55:58 +1000 (EST) Date: Tue, 22 Jun 2004 21:55:58 +1000 From: Greg Daley Subject: [dhcwg] REMINDER: dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt To: dhcwg@ietf.org Message-id: <22d4b222a059.22a05922d4b2@mail1.monash.edu.au> MIME-version: 1.0 X-Mailer: Netscape Webmail Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en 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 Content-Transfer-Encoding: 7BIT X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7BIT I support this document going forward. Greg Daley. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Wed Jun 23 05:02:14 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09212; Wed, 23 Jun 2004 05:02:14 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd3bi-0005bA-F7; Wed, 23 Jun 2004 04:59:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd14i-0005rI-N8 for dhcwg@megatron.ietf.org; Wed, 23 Jun 2004 02:17:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23490 for ; Wed, 23 Jun 2004 02:17:33 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bd14e-0004uX-So for dhcwg@ietf.org; Wed, 23 Jun 2004 02:17:32 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bcy9W-0001hD-00 for dhcwg@ietf.org; Tue, 22 Jun 2004 23:10:23 -0400 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx with esmtp (Exim 4.12) id 1BcwMs-0003aH-00 for dhcwg@ietf.org; Tue, 22 Jun 2004 21:16:02 -0400 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HZQ0000LM5OSE@mailout1.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 10:15:24 +0900 (KST) Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HZQ00MJWM4W39@mailout1.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 10:14:57 +0900 (KST) Received: from LocalHost ([168.219.202.103]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HZQ001QOM4S5L@mmp2.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 10:14:52 +0900 (KST) Date: Wed, 23 Jun 2004 10:15:46 +0900 From: Soohong Daniel Park Subject: RE: [dhcwg] REMINDER: dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt In-reply-to: <4.3.2.7.2.20040621175636.020da900@flask.cisco.com> To: dhcwg@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: multipart/mixed; boundary="Boundary_(ID_WSEj59TOm9ZywdzEhviy/w)" Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-MS-TNEF-Correlator: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Cc: soohong.park@samsung.com X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org This is a multi-part message in MIME format. --Boundary_(ID_WSEj59TOm9ZywdzEhviy/w) Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7BIT This draft looks good and I second it. My comments are as below; [1] Category is correct as PS ? I think BCP would be better. [2] 1. Introduction, >This document concerns the interaction of mechanisms used by IPv4 >protocol stacks. Network attachment detection and its interaction >with interface configuration is considered elsewhere, for example in >Neighbor Discovery for IPv6 [RFC2461], IPv6 Stateless Address >Autoconfiguration [RFC2462] and Mobility Support in IPv6 [MIPv6]. I am not sure why this draft refers rfc2461,2462 and even MIPv6. This draft is strictly bound to IPv4 especially DHCPv4 and IPv4LL and something like that, so I think we don't need to refer IPv6 protocol. [3] 2.3 IPv4 Address Acquisition To obtain its IPv4 address quickly, Rapid Commit option of DHCPv4 can be used for optimizing detection of network attachment on mobile hosts. With my experience, it's stable and fast than current mechanism, thus if feasible, you can indicate this utility at this section. http://www.ietf.org/internet-drafts/draft-ietf-dhc-rapid-commit-opt-03.txt (I updated and published it as 04 version yesterday) For reference, I cite a result of comparison between them. (It was tested on both wired and wireless though testbed was so simple) =========================================== Item Mean value Standard deviation =========================================== Time delay (sec.) Existing 0.051269 0.002349 New 0.001541 0.001213 =========================================== Packet loss (packet) Existing 417.04 53.10322 New 366.02 32.55092 =========================================== Hope this helps Regards - Daniel (Soohong Daniel Park) - Mobile Platform Lab. Samsung Electronics. --Boundary_(ID_WSEj59TOm9ZywdzEhviy/w) Content-type: application/ms-tnef; name=winmail.dat Content-disposition: attachment; filename=winmail.dat Content-Transfer-Encoding: base64 eJ8+Ii4BAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAAtQMAAAAAAAC4AAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANQHBgAXAAoADwAAAAMAFAEB A5AGAKgKAAAnAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADAC4AAAAAAAMANgAA AAAAHgBwAAEAAABZAAAAW2RoY3dnXSBSRU1JTkRFUjogZGhjIFdHIGxhc3QgY2FsbCBvbiBkaGMg V0cgbGFzdCBjYWxsIG9uIGRyYWZ0LWlldGYtZGhjLWRuYS1pcHY0LTA3LnR4dAAAAAACAXEAAQAA ABYAAAABxFi/nIPetLk/7tNDVqf7a9oLx+Z9AAACAR0MAQAAAB4AAABTTVRQOlNPT0hPTkcuUEFS S0BTQU1TVU5HLkNPTQAAAAsAAQ4AAAAAQAAGDgACCIG/WMQBAgEKDgEAAAAYAAAAAAAAAOfUxVY3 wUNLqTYRDDtYSx7CgAAACwAfDgEAAAACAQkQAQAAAKIFAACeBQAA8ggAAExaRnVdqKhPAwAKAHJj cGcxMjXyMgD7MzYB6AKkA+QHE08CgwBQA9QCAGNoCsBzeGV0MBCpDlAEVRHZPyo/AoB9CoF2CJB3 a+kLgGQ0DGBjAFALAwtgMm4OEDA0EyELxCBUQmgEACBkcmEBgCApCQBvawQgZxfgZCBzAHAYYEkg EjAFoBiRaRx0LgqiCoQKgE15IL0FoG0HgAIwBCAKwGUYcEkEIGJlCQB3OxmKW4AxXSBDYXRlGDDe chpQF0EFoQlwYwVAG0EqUAXwPxixdBcwbmtAIEJDUCB3CGBsPxhgG3AbYQJABJAZe1syuRywMS4Y sAIwA2BkFYC0dGkCICwK4wqAPhckmG9jdRqiGmFuYwSRfwQgHrAbIAuAIBEA0CICIDhvZiAHgBHx AwBzbR0EIHUSMB+RGlBJUHbrFWAidHADYHQjMAbwGNBdAZBjGAAhYAexdB9Qcvce8BzgJ/FoI2MB ABzwJOT/GIIZUAQgJIkiZQPwHrAkdI5mANAbIBkBZmlnCHD/HOAlAh1jAIEEgSZBG4ASMD53JFAJ cCJAAhAFwGV4fGFtC1AkYiJlB8AtEGjbBuAFwEQEAAWgdgSQGlADL0ImoTYgW1JGQ7gyNDYcoCJA MgNTAZB3HPAv0BCCZBdwM7EiZUE+dSeCLPoyVSEhGIJNbw5iAxAZUBpQU3VwcNcJESRxMfVNMgJd GXsYwPkvoCBuJ3AY0AhwGyAu0O8aUB6xF1YJcGYEkAQgLHDaYzKSLDYyGHNlMXADoP84cxl1FykX QRExJ9EFEB3g/mwaUAKxG2AIYBiRJ4AmkzkugHNwBZAHMT+BREjPHyBAoRiDJrFMTCJVGILucwNw EkAewWcTAShQP7L9NxBrGyAesBzgIkBDQB6HpncbICMgbicFQG4J4F9AMztzMfQnViBMMxywMhwu M0B0M/UQoGNxdfcEABlQK0dUQGA24AGQN+H7KoJAg2FJtUpBKBA/gCJA+FJhcC4gHMAagRlQJTDv BTAlBUGEGYRjA5EfsSYj9y9CTkJOAHpDoSmZJUFGUC8onyURBGA28WUZhGhv6yfgKDFXK/JtGlAv gEDw7wiBI9EiQBlQJwQgJ+ECYP8bIRiRLIAn4ESiA6AjQB2x/wIwGYQldyJAHrAmIBlAJVDbO5Ab QGlWcSJAeQhgGmD/A5EVMQ3gHOE6tDTgNwQc4H86sxmEGOEiAiFgU+UCQHDQOi8vd15ALgiQADCy LgWwZy8kg1IhLRdzNHMvF3MtXoJfkGhjti0XgE2RLRpyGVAtTkGwLTAzLgzQV/UoGMDNN3BkHOEY ZHB1AmAEAO8kUBkyGzIWYCAxcQCQJRFOeQeQIBFjIHkpGYpGvwWxO3NVlBjAQRBbEWE7Yf06MGxO ISVQGnEKsQQAJRHvH+FFwD0RJEFtGXVi0AVA/ncbQRzwZZEYYGlyJ3AsEP8D8C5SGIJsQjOjHrAI YDDA/2tDG3BswRtBRREAkC+yZgu+PXAPcR9xpjlFHPBtDIRvc3UTEXPjEmBNWaADoHb/B0AKUHPd M1EVQAsRKZEU4P8tU2+veH9xzz3DB3EpkQtg9nlidRjhLmYAAZEoUHyEPEV4BAAiAEOxfFIwLiQw NQ4gNjl9hjAy/DM0fkAZlEPif88/owfB43PdfqIxNTQAUH5mDiC8MTN3f4SveZ8ZolAoAbcSQBfB NEYoCrCHMil8nzt8YYKwN33gFWBzZSA182IgFlAzMg5QGZN/7yhSP4FeDzA9gH7QikeLIC41+DUw OYtFha+Q33ItGYTOSE5AWyUkUGxwNFUZhO5SHQALEZQrLTEQJbEbgPggKFMX4FRAUSGWRYcQ3yjA ZgWWIDbTGyBQC2AAMPsFsDnQTAGgIWAGECXwQBC9UTBFL9Ad4ANgAwBjKDALGYoUoQCcEAAAHgBC EAEAAAA0AAAAPDQuMy4yLjcuMi4yMDA0MDYyMTE3NTYzNi4wMjBkYTkwMEBmbGFzay5jaXNjby5j b20+AAsAE4AIIAYAAAAAAMAAAAAAAABGAAAAAAOFAAAAAAAAAwAngAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAAADADSACCAGAAAAAADAAAAAAAAARgAAAAAQhQAAAAAAAAMAOYAIIAYAAAAAAMAA AAAAAABGAAAAAFKFAACOagEAHgBGgAggBgAAAAAAwAAAAAAAAEYAAAAAVIUAAAEAAAAEAAAAOS4w AAsAR4AIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAAAACwBLgAggBgAAAAAAwAAAAAAAAEYAAAAA DoUAAAAAAAADAEyACCAGAAAAAADAAAAAAAAARgAAAAARhQAAAAAAAAMAToAIIAYAAAAAAMAAAAAA AABGAAAAABiFAAAAAAAAHgBcgAggBgAAAAAAwAAAAAAAAEYAAAAANoUAAAEAAAABAAAAAAAAAB4A XYAIIAYAAAAAAMAAAAAAAABGAAAAADeFAAABAAAAAQAAAAAAAAAeAF6ACCAGAAAAAADAAAAAAAAA RgAAAAA4hQAAAQAAAAEAAAAAAAAACwBjgAggBgAAAAAAwAAAAAAAAEYAAAAAgoUAAAEAAAACAfgP AQAAABAAAADn1MVWN8FDS6k2EQw7WEseAgH6DwEAAAAQAAAA59TFVjfBQ0upNhEMO1hLHgIB+w8B AAAAnwAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABQU1RQUlguRExMAAAAAAAAAABOSVRB+b+4AQCq ADfZbgAAAEM6XERvY3VtZW50cyBhbmQgU2V0dGluZ3NcQWRtaW5pc3RyYXRvclxMb2NhbCBTZXR0 aW5nc1xBcHBsaWNhdGlvbiBEYXRhXE1pY3Jvc29mdFxPdXRsb29rXG91dGxvb2sucHN0AAADAP4P BQAAAAMADTT9NwAAAgF/AAEAAAA4AAAAPEVERUxLSkRHUEdOSVBPQU9ITU5QTUVKRUZNQUEuc29v aG9uZy5wYXJrQHNhbXN1bmcuY29tPgADAAYQNXx7pAMABxCIBQAAAwAQEAAAAAADABEQAQAAAB4A CBABAAAAZQAAAFRISVNEUkFGVExPT0tTR09PREFORElTRUNPTkRJVE1ZQ09NTUVOVFNBUkVBU0JF TE9XOzFDQVRFR09SWUlTQ09SUkVDVEFTUFM/SVRISU5LQkNQV09VTERCRUJFVFRFUjIxSU4AAAAA AsM= --Boundary_(ID_WSEj59TOm9ZywdzEhviy/w) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --Boundary_(ID_WSEj59TOm9ZywdzEhviy/w)-- From dhcwg-bounces@ietf.org Thu Jun 24 13:05:04 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29853; Thu, 24 Jun 2004 13:05:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXIE-00019l-KB; Thu, 24 Jun 2004 12:41:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd2Gz-0005kL-2O for dhcwg@megatron.ietf.org; Wed, 23 Jun 2004 03:34:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25840 for ; Wed, 23 Jun 2004 03:34:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bd2Gw-00030T-LQ for dhcwg@ietf.org; Wed, 23 Jun 2004 03:34:18 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bd1Ix-0007bU-00 for dhcwg@ietf.org; Wed, 23 Jun 2004 02:32:20 -0400 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx with esmtp (Exim 4.12) id 1Bcymj-00051A-00 for dhcwg@ietf.org; Tue, 22 Jun 2004 23:50:54 -0400 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HZQ00E01TBWSZ@mailout2.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 12:50:20 +0900 (KST) Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HZQ004MSTBVT6@mailout2.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 12:50:20 +0900 (KST) Received: from LocalHost ([168.219.202.103]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HZQ0013ATBQ5L@mmp2.samsung.com> for dhcwg@ietf.org; Wed, 23 Jun 2004 12:50:14 +0900 (KST) Date: Wed, 23 Jun 2004 12:51:08 +0900 From: Soohong Daniel Park Subject: RE: [dhcwg] REMINDER: dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt In-reply-to: <4.3.2.7.2.20040621175636.020da900@flask.cisco.com> To: dhcwg@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7BIT X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7BIT This draft looks good and I second it. My comments are as below; [1] Category is correct as PS ? I think BCP would be better. [2] 1. Introduction, >This document concerns the interaction of mechanisms used by IPv4 >protocol stacks. Network attachment detection and its interaction >with interface configuration is considered elsewhere, for example in >Neighbor Discovery for IPv6 [RFC2461], IPv6 Stateless Address >Autoconfiguration [RFC2462] and Mobility Support in IPv6 [MIPv6]. I am not sure why this draft refers rfc2461,2462 and even MIPv6. This draft is strictly bound to IPv4 especially DHCPv4 and IPv4LL and something like that, so I think we don't need to refer IPv6 protocol. [3] 2.3 IPv4 Address Acquisition To obtain its IPv4 address quickly, Rapid Commit option of DHCPv4 can be used for optimizing detection of network attachment on mobile hosts. With my experience, it's stable and fast than current mechanism, thus if feasible, you can indicate this utility at this section. http://www.ietf.org/internet-drafts/draft-ietf-dhc-rapid-commit-opt-03.txt (I updated and published it as 04 version yesterday) For reference, I cite a result of comparison between them. (It was tested on both wired and wireless though testbed was so simple) =========================================== Item Mean value Standard deviation =========================================== Time delay (sec.) Existing 0.051269 0.002349 New 0.001541 0.001213 =========================================== Packet loss (packet) Existing 417.04 53.10322 New 366.02 32.55092 =========================================== Hope this helps - Daniel (Soohong Daniel Park) - Mobile Platform Lab. Samsung Electronics. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 24 14:25:19 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09238; Thu, 24 Jun 2004 14:25:19 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXOM-00037k-Pc; Thu, 24 Jun 2004 12:48:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdEcl-0000Lb-Py; Wed, 23 Jun 2004 16:45:39 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16010; Wed, 23 Jun 2004 16:45:36 -0400 (EDT) Message-Id: <200406232045.QAA16010@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Wed, 23 Jun 2004 16:45:36 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-rapid-commit-opt-04.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : Rapid Commit Option for DHCPv4 Author(s) : P. Kim, et al. Filename : draft-ietf-dhc-rapid-commit-opt-04.txt Pages : 11 Date : 2004-6-23 This document defines a new DHCPv4 option, modeled on the DHCPv6 Rapid Commit option, for obtaining IP address and configuration information using a 2-message exchange rather than the usual 4- message exchange, expediting client configuration. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-rapid-commit-opt-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-rapid-commit-opt-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-rapid-commit-opt-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-6-23170919.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-rapid-commit-opt-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-rapid-commit-opt-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-6-23170919.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Thu Jun 24 14:27:36 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09611; Thu, 24 Jun 2004 14:27:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXOQ-00038p-2s; Thu, 24 Jun 2004 12:48:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdEcv-0000Lp-7E; Wed, 23 Jun 2004 16:45:49 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16017; Wed, 23 Jun 2004 16:45:46 -0400 (EDT) Message-Id: <200406232045.QAA16017@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Wed, 23 Jun 2004 16:45:46 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-vendor-03.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : Vendor-Identifying Vendor Options for DHCPv4 Author(s) : J. Littlefield Filename : draft-ietf-dhc-vendor-03.txt Pages : 10 Date : 2004-6-23 The DHCP options for Vendor Class and Vendor-Specific Information can be ambiguous when a DHCP client represents multiple vendors. This document defines two new options, modeled on the IPv6 options for vendor class and vendor-specific information, which contain Enterprise Numbers to remove ambiguity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-vendor-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-vendor-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-vendor-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-6-23170928.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-vendor-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-vendor-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-6-23170928.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Thu Jun 24 15:51:05 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21182; Thu, 24 Jun 2004 15:51:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXQN-0003st-MJ; Thu, 24 Jun 2004 12:50:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdKMU-0005JN-0Z for dhcwg@megatron.ietf.org; Wed, 23 Jun 2004 22:53:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10687 for ; Wed, 23 Jun 2004 22:53:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BdKMR-0005yp-FA for dhcwg@ietf.org; Wed, 23 Jun 2004 22:53:11 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BdKLS-0005aY-00 for dhcwg@ietf.org; Wed, 23 Jun 2004 22:52:11 -0400 Received: from alpha1.its.monash.edu.au ([130.194.1.1]) by ietf-mx with esmtp (Exim 4.12) id 1BdKKV-0005Dl-00 for dhcwg@ietf.org; Wed, 23 Jun 2004 22:51:11 -0400 Received: from localhost ([130.194.13.85]) by vaxc.its.monash.edu.au (PMDF V6.1 #39306) with ESMTP id <01LBOCIHWQ8C8WW79M@vaxc.its.monash.edu.au> for dhcwg@ietf.org; Thu, 24 Jun 2004 12:48:59 +1000 Received: from broink.its.monash.edu.au (localhost.its.monash.edu.au [127.0.0.1]) by localhost (Postfix) with ESMTP id 9F30A158005; Thu, 24 Jun 2004 12:48:59 +1000 (EST) Received: from eng.monash.edu.au (knuth.eng.monash.edu.au [130.194.252.110]) by broink.its.monash.edu.au (Postfix) with ESMTP id 80EDD12000F; Thu, 24 Jun 2004 12:48:59 +1000 (EST) Date: Thu, 24 Jun 2004 12:48:59 +1000 From: Greg Daley Subject: Re: [dhcwg] REMINDER: dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt To: Soohong Daniel Park Message-id: <40DA411B.7090102@eng.monash.edu.au> Organization: Monash University MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en, en-us User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 References: 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 Content-Transfer-Encoding: 7BIT Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: greg.daley@eng.monash.edu.au List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7BIT Hi Daniel, Here are some opinions. Soohong Daniel Park wrote: > This draft looks good and I second it. > > My comments are as below; > > [1] Category is correct as PS ? I think BCP would be better. I'm actually interested in this as well, but for a different reason. > [2] 1. Introduction, > >>This document concerns the interaction of mechanisms used by IPv4 >>protocol stacks. Network attachment detection and its interaction >>with interface configuration is considered elsewhere, for example in >>Neighbor Discovery for IPv6 [RFC2461], IPv6 Stateless Address >>Autoconfiguration [RFC2462] and Mobility Support in IPv6 [MIPv6]. > > > I am not sure why this draft refers rfc2461,2462 and even MIPv6. > This draft is strictly bound to IPv4 especially DHCPv4 and IPv4LL > and something like that, so I think we don't need to refer IPv6 protocol. > > [3] 2.3 IPv4 Address Acquisition > To obtain its IPv4 address quickly, Rapid Commit option of DHCPv4 > can be used for optimizing detection of network attachment on mobile > hosts. With my experience, it's stable and fast than current > mechanism, thus if feasible, you can indicate this utility at this > section. > http://www.ietf.org/internet-drafts/draft-ietf-dhc-rapid-commit-opt-03.txt > (I updated and published it as 04 version yesterday) If the document is a BCP, then it cannot really reference alternative procedures which aren't RFC's. Also, even if the document is PS, there would be some conflict as to whether the rapid commit would need to be normatively referenced. A normative reference to another draft which is still to go through IESG review is probably worth avoiding at this stage. The rapid commit will be able to indicate the benefits itself. People will use it in addition to the DNAv4 procedures as it is a compatible optimization. Greg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 24 15:53:36 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21573; Thu, 24 Jun 2004 15:53:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXQc-00040k-TS; Thu, 24 Jun 2004 12:50:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdLY2-0006rX-No for dhcwg@megatron.ietf.org; Thu, 24 Jun 2004 00:09:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15183 for ; Thu, 24 Jun 2004 00:09:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BdLY0-0003bS-Ak for dhcwg@ietf.org; Thu, 24 Jun 2004 00:09:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BdLX1-0003E3-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 00:08:12 -0400 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx with esmtp (Exim 4.12) id 1BdLVz-0002Uz-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 00:07:07 -0400 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HZS0085POQSJB@mailout1.samsung.com> for dhcwg@ietf.org; Thu, 24 Jun 2004 13:06:28 +0900 (KST) Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HZS005ULOL06V@mailout1.samsung.com> for dhcwg@ietf.org; Thu, 24 Jun 2004 13:03:01 +0900 (KST) Received: from LocalHost ([168.219.202.103]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HZS00BJROKV6Q@mmp2.samsung.com> for dhcwg@ietf.org; Thu, 24 Jun 2004 13:02:56 +0900 (KST) Date: Thu, 24 Jun 2004 13:03:51 +0900 From: Soohong Daniel Park Subject: RE: [dhcwg] REMINDER: dhc WG last call on dhc WG last call ondraft-ietf-dhc-dna-ipv4-07.txt In-reply-to: <40DA411B.7090102@eng.monash.edu.au> To: greg.daley@eng.monash.edu.au Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7BIT Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7BIT Hi Greg. > I'm actually interested in this as well, but for a > different reason. um..I am wondering what a different reason is. >If the document is a BCP, then it cannot really reference >alternative procedures which aren't RFC's. I know of course, thus I said *for reference* in the previous mail. Also if required, it can be solved in RFC queue prior to publishing RFC. Anyway I don't have a hard stance at this time. >The rapid commit will be able to indicate the benefits >itself. People will use it in addition to the DNAv4 procedures >as it is a compatible optimization. That's what I am saying...^.^ Regards. - Daniel (Soohong Daniel Park) - Mobile Platform Lab. Samsung Electronics. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 24 15:55:57 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22092; Thu, 24 Jun 2004 15:55:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXQt-00047j-Ef; Thu, 24 Jun 2004 12:50:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdNHe-0002Zq-I3 for dhcwg@megatron.ietf.org; Thu, 24 Jun 2004 02:00:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21350 for ; Thu, 24 Jun 2004 02:00:24 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BdNHb-00067E-Td for dhcwg@ietf.org; Thu, 24 Jun 2004 02:00:24 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BdNGh-0005lE-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 01:59:27 -0400 Received: from alpha9.its.monash.edu.au ([130.194.1.9]) by ietf-mx with esmtp (Exim 4.12) id 1BdNG0-0005P1-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 01:58:44 -0400 Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au (PMDF V5.2-31 #39306) with ESMTP id <01LBOJ3DTULW8X7B1O@vaxh.its.monash.edu.au> for dhcwg@ietf.org; Thu, 24 Jun 2004 15:57:38 +1000 Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id CB27D80036; Thu, 24 Jun 2004 15:57:37 +1000 (EST) Received: from eng.monash.edu.au (knuth.eng.monash.edu.au [130.194.252.110]) by larry.its.monash.edu.au (Postfix) with ESMTP id A6E3D3C015; Thu, 24 Jun 2004 15:57:37 +1000 (EST) Date: Thu, 24 Jun 2004 15:57:37 +1000 From: Greg Daley Subject: Re: [dhcwg] REMINDER: dhc WG last call on dhc WG last call ondraft-ietf-dhc-dna-ipv4-07.txt To: Soohong Daniel Park Message-id: <40DA6D51.5000609@eng.monash.edu.au> Organization: Monash University MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 X-Accept-Language: en, en-us References: 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 Content-Transfer-Encoding: 7BIT Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: greg.daley@eng.monash.edu.au List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7BIT Soohong Daniel Park wrote: > Hi Greg. > > >>I'm actually interested in this as well, but for a >>different reason. > > > um..I am wondering what a different reason is. > Well, we've got a charter item in DNA WG for DNA for IPv6. This is basically providing similar sets of functions to DNAv4: no new messages, adjustments of how a host interprets the information received. This is currently being listed as BCP for DNAv6. An indication that the DNAv4 work is standards work may impact on the choices made for DNA WG. Greg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 24 17:44:44 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16328; Thu, 24 Jun 2004 17:44:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdbQG-0000So-B0; Thu, 24 Jun 2004 17:06:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdaXw-0003vb-C7 for dhcwg@megatron.ietf.org; Thu, 24 Jun 2004 16:10:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23809 for ; Thu, 24 Jun 2004 16:10:05 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BdaXv-0004zO-2L for dhcwg@ietf.org; Thu, 24 Jun 2004 16:10:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BdZyQ-000667-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 15:33:28 -0400 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BdZW6-0000Np-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 15:04:10 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 24 Jun 2004 12:06:19 -0700 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 i5OJ3bSc023824 for ; Thu, 24 Jun 2004 12:03:38 -0700 (PDT) Received: from [161.44.65.215] ([161.44.65.215]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJR60835; Thu, 24 Jun 2004 15:03:36 -0400 (EDT) Message-ID: <40DB2588.4050200@cisco.com> Date: Thu, 24 Jun 2004 15:03:36 -0400 From: Josh Littlefield Organization: Cisco Systems User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dhcwg@ietf.org Subject: Re: [dhcwg] I-D ACTION:draft-ietf-dhc-vendor-03.txt References: <200406232045.QAA16017@ietf.org> In-Reply-To: <200406232045.QAA16017@ietf.org> Content-Type: multipart/mixed; boundary="------------070505060404060005050409" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org This is a multi-part message in MIME format. --------------070505060404060005050409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Attached please find diffs for this version, for your convenience. The changes are very minor, and result from some errors detected during AD review. Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. > > Title : Vendor-Identifying Vendor Options for DHCPv4 > Author(s) : J. Littlefield > Filename : draft-ietf-dhc-vendor-03.txt > Pages : 10 > Date : 2004-6-23 > -- ===================================================================== Josh Littlefield Cisco Systems, Inc. joshl@cisco.com 1414 Massachusetts Avenue tel: 978-936-1379 fax: same Boxborough, MA 01719-2205 --------------070505060404060005050409 Content-Type: text/plain; name="draft-ietf-dhc-vendor-02-03-diff.txt" Content-Disposition: inline; filename="draft-ietf-dhc-vendor-02-03-diff.txt" Content-Transfer-Encoding: 7bit 5c5 < Expires: November 17, 2004 May 17, 2004 --- > Expires: December 21, 2004 June 21, 2004 9c9 < draft-ietf-dhc-vendor-02.txt --- > draft-ietf-dhc-vendor-03.txt 34c34 < This Internet-Draft will expire on November 17, 2004. --- > This Internet-Draft will expire on December 21, 2004. 55c55 < Littlefield Expires November 17, 2004 [Page 1] --- > Littlefield Expires December 21, 2004 [Page 1] 57c57 < Internet-Draft Vendor-Identifying Vendor Options May 2004 --- > Internet-Draft Vendor-Identifying Vendor Options June 2004 73,74c73,74 < Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8 < Intellectual Property and Copyright Statements . . . . . . . . 9 --- > Author's Address . . . . . . . . . . . . . . . . . . . . . . . 9 > Intellectual Property and Copyright Statements . . . . . . . . 10 111c111 < Littlefield Expires November 17, 2004 [Page 2] --- > Littlefield Expires December 21, 2004 [Page 2] 113c113 < Internet-Draft Vendor-Identifying Vendor Options May 2004 --- > Internet-Draft Vendor-Identifying Vendor Options June 2004 145,148c145,149 < [6], which contain Enterprise Numbers to remove ambiguity about the < interpretation of their contents. If desired, these new options can < be used in addition to the current vendor class and vendor < information options, whose definition is unaffected by this document. --- > [6], which contain IANA-assigned Enterprise Numbers [3] to remove > ambiguity about the interpretation of their contents. If desired, > these new options can be used in addition to the current vendor class > and vendor information options, whose definition is unaffected by > this document. 154,163c155,163 < option defined here contains an enterprise number, followed by an < internal data length, followed by vendor-specific data. This < sequence may be repeated multiple times within each option. Because < of the possibility that the aggregate of the vendor-specific data for < either option will exceed 255 octets, these options are hereby < declared to be "concatenation-requiring", as defined by RFC 3396 [4]. < As such, the aggregate of all instances of vendor-specific data is to < be considered one long option, for each of the two options defined < here. These long options can be divided into smaller options for < packet encoding in conformance with RFC 3396, on whatever octet --- > option defined here contains an enterprise number (assigned by IANA > [3]), followed by an internal data length, followed by > vendor-specific data. This sequence may be repeated multiple times > within each option. Because of the possibility that the aggregate of > the vendor-specific data for either option will exceed 255 octets, > these options are hereby declared to be "concatenation-requiring", as > defined by RFC 3396 [4]. As such, the aggregate of all instances of > vendor-specific data is to be considered one long option, for each of > the two options defined here. These long options can be divided into 167c167 < Littlefield Expires November 17, 2004 [Page 3] --- > Littlefield Expires December 21, 2004 [Page 3] 169c169 < Internet-Draft Vendor-Identifying Vendor Options May 2004 --- > Internet-Draft Vendor-Identifying Vendor Options June 2004 172,174c172,175 < boundaries are convenient to the implementation. Dividing on the < boundaries between vendor instances is not required, but may be < convenient for encoding or packet tracing. --- > smaller options for packet encoding in conformance with RFC 3396, on > whatever octet boundaries are convenient to the implementation. > Dividing on the boundaries between vendor instances is not required, > but may be convenient for encoding or packet tracing. 216d216 < option-code OPTION_V-I_VENDOR_CLASS (to be assigned by IANA) 223c223 < Littlefield Expires November 17, 2004 [Page 4] --- > Littlefield Expires December 21, 2004 [Page 4] 225c225 < Internet-Draft Vendor-Identifying Vendor Options May 2004 --- > Internet-Draft Vendor-Identifying Vendor Options June 2004 228c228,231 < option-len 5 + length of vendor class data field --- > option-code OPTION_V-I_VENDOR_CLASS (to be assigned by IANA) > > option-len total length of all following option data in > octets 273,274d275 < Vendor-Identifying Vendor-Specific Information Option, there is no < requirement for such a flow. 277a279 > Littlefield Expires December 21, 2004 [Page 5] 279c281 < Littlefield Expires November 17, 2004 [Page 5] --- > Internet-Draft Vendor-Identifying Vendor Options June 2004 281d282 < Internet-Draft Vendor-Identifying Vendor Options May 2004 282a284,285 > Vendor-Identifying Vendor-Specific Information Option, there is no > requirement for such a flow. 314c317,318 < option-len 5 + length of option-data field --- > option-len total length of all following option data in > octets 328,331d331 < An Enterprise Number SHOULD only occur once among all instances of < this option. Behavior is undefined if an Enterprise Number occurs < multiple times. The information for each Enterprise Number is < treated independently, regardless or whether it occurs in an option 335c335 < Littlefield Expires November 17, 2004 [Page 6] --- > Littlefield Expires December 21, 2004 [Page 6] 337c337 < Internet-Draft Vendor-Identifying Vendor Options May 2004 --- > Internet-Draft Vendor-Identifying Vendor Options June 2004 339a340,343 > An Enterprise Number SHOULD only occur once among all instances of > this option. Behavior is undefined if an Enterprise Number occurs > multiple times. The information for each Enterprise Number is > treated independently, regardless or whether it occurs in an option 384,386d387 < message integrity mechanism, as described in RFC 3118 [8], which may < be used if authenticity is required for data carried by the options < defined in this document. 389a391 > Littlefield Expires December 21, 2004 [Page 7] 391c393 < Littlefield Expires November 17, 2004 [Page 7] --- > Internet-Draft Vendor-Identifying Vendor Options June 2004 393d394 < Internet-Draft Vendor-Identifying Vendor Options May 2004 394a396,398 > message integrity mechanism, as described in RFC 3118 [8], which may > be used if authenticity is required for data carried by the options > defined in this document. 432a437,451 > > > > > > > > > > > Littlefield Expires December 21, 2004 [Page 8] > > Internet-Draft Vendor-Identifying Vendor Options June 2004 > > 447d465 < Littlefield Expires November 17, 2004 [Page 8] 449c467,505 < Internet-Draft Vendor-Identifying Vendor Options May 2004 --- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Littlefield Expires December 21, 2004 [Page 9] > > Internet-Draft Vendor-Identifying Vendor Options June 2004 503c559 < Littlefield Expires November 17, 2004 [Page 9] --- > Littlefield Expires December 21, 2004 [Page 10] --------------070505060404060005050409 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --------------070505060404060005050409-- From dhcwg-bounces@ietf.org Thu Jun 24 18:30:51 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22498; Thu, 24 Jun 2004 18:30:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdcaM-0000rv-Cw; Thu, 24 Jun 2004 18:20:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcAW7-0006xL-TK for dhcwg@megatron.ietf.org; Sun, 20 Jun 2004 18:10:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02860 for ; Sun, 20 Jun 2004 18:10:20 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BcAW6-0006pC-4N for dhcwg@ietf.org; Sun, 20 Jun 2004 18:10:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BcAV5-0006bg-00 for dhcwg@ietf.org; Sun, 20 Jun 2004 18:09:20 -0400 Received: from ints.mail.pike.ru ([195.9.45.194]) by ietf-mx with esmtp (Exim 4.12) id 1BcAUW-0006OK-00 for dhcwg@ietf.org; Sun, 20 Jun 2004 18:08:44 -0400 Received: (qmail 47066 invoked from network); 20 Jun 2004 22:29:21 -0000 Received: from stratess.ints.pike (HELO strates) (195.9.37.191) by ints.mail.pike.ru with SMTP; 20 Jun 2004 22:29:21 -0000 Date: Mon, 21 Jun 2004 02:08:39 +0400 From: strates X-Mailer: The Bat! (v1.36) S/N F29DEE5D / Educational X-Priority: 3 (Normal) Message-ID: <1489.040621@mail.ru> To: dhcwg@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=3.2 required=5.0 tests=FORGED_MUA_THEBAT autolearn=no version=2.60 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 24 Jun 2004 18:20:44 -0400 Subject: [dhcwg] [Question]DHCPv6 implementations X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: strates List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit I tried to learn what are nowdays available DHCPv6 client/server implementations. Using the search engines I could only find - KAME implementation for *BSDs: stateless DHCPv6, and they are not going to improve it - Widespread linux-related http://dhcpv6.sourceforge.net implementation - Some traces of proprietary CISCO IOS and NEC implementations (http://www.dhcpv6.org/ with only relay agent available for public) - USAGI implementation which leads to a project which claimed himself 'dead'(http://www.linux-ipv6.org/links.html -> http://www.hycomat.co.uk/dhcp/) - Signs of some Linux implementation (there is some gentoo related stuff, config files in google). - DHCPv6 support in HP-UX It is quite strange for me, that only a few incomplete implementations are present (yes, stateless IPv6 autoconfiguration fulfils a lot of work instead of DHCPv6, and many people seem to be satisfied with s-less autoconfiguration and router prefix advertisement, but still...) Later I found www.dfn.de/uploaded/DHCPv6.pdf and I understood that it seems there are really only a few implementations. Could anybody advertise anything in addition to the list above? Thanks beforehand _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 24 18:56:23 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24960; Thu, 24 Jun 2004 18:56:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdceN-0003gz-35; Thu, 24 Jun 2004 18:24:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdVU6-00039H-F6 for dhcwg@megatron.ietf.org; Thu, 24 Jun 2004 10:45:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18799 for ; Thu, 24 Jun 2004 10:45:48 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BdVU5-0000HV-LU for dhcwg@ietf.org; Thu, 24 Jun 2004 10:45:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BdVT5-0007gQ-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 10:44:48 -0400 Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BdVRp-0006xD-00; Thu, 24 Jun 2004 10:43:29 -0400 Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BdVJF-0001xP-Ln; Thu, 24 Jun 2004 10:34:37 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 24 Jun 2004 10:34:37 -0400 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 X-Mailman-Approved-At: Thu, 24 Jun 2004 18:24:53 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] Last Call: 'Vendor-Identifying Vendor Options for DHCPv4' to Proposed Standard X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org The IESG has received a request from the Dynamic Host Configuration WG to consider the following document: - 'Vendor-Identifying Vendor Options for DHCPv4 ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2004-07-08. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-dhc-vendor-03.txt _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 24 19:41:50 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24970; Thu, 24 Jun 2004 18:56:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdceM-0003g7-MH; Thu, 24 Jun 2004 18:24:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdBe5-0004Lk-79 for dhcwg@megatron.ietf.org; Wed, 23 Jun 2004 13:34:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16754 for ; Wed, 23 Jun 2004 13:34:47 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BdBe3-0002Mx-UL for dhcwg@ietf.org; Wed, 23 Jun 2004 13:34:48 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BdAHa-0000Va-00 for dhcwg@ietf.org; Wed, 23 Jun 2004 12:07:31 -0400 Received: from nwkea-mail-1.sun.com ([192.18.42.13]) by ietf-mx with esmtp (Exim 4.12) id 1Bd9Q4-00015K-00 for dhcwg@ietf.org; Wed, 23 Jun 2004 11:12:13 -0400 Received: from hs-ehdb03-01.Germany.Sun.COM ([129.157.142.201]) by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id i5NFAJJ6016958; Wed, 23 Jun 2004 08:10:20 -0700 (PDT) Received: from [217.95.19.13] (vpn-129-150-117-9.SFBay.Sun.COM [129.150.117.9]) by hs-ehdb03-01.Germany.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id i5NFAGDm015366; Wed, 23 Jun 2004 17:10:17 +0200 (MEST) Date: Wed, 23 Jun 2004 17:09:57 +0200 (CEST) From: Erik Guttman X-X-Sender: erik@slap.local To: Ralph Droms Subject: Re: [dhcwg] REMINDER: dhc WG last call on dhc WG last call on draft-ietf-dhc-dna-ipv4-07.txt In-Reply-To: <4.3.2.7.2.20040621175636.020da900@flask.cisco.com> Message-ID: References: <4.3.2.7.2.20040621175636.020da900@flask.cisco.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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=none autolearn=no version=2.60 X-Mailman-Approved-At: Thu, 24 Jun 2004 18:24:53 -0400 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Erik Guttman List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org I have reviewed the document. I paid particular attention to the resolution of the issues I suggested (13-17). Satisfactory resolutions for each of these have been added to draft 07. I recommend this document be advanced. Regards, Erik _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 24 21:54:59 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12839; Thu, 24 Jun 2004 21:54:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdfi2-0008LK-Oa; Thu, 24 Jun 2004 21:40:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BddhV-0003iY-QZ for dhcwg@megatron.ietf.org; Thu, 24 Jun 2004 19:32:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00448 for ; Thu, 24 Jun 2004 19:32:08 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BddZn-0005QD-Af for dhcwg@ietf.org; Thu, 24 Jun 2004 19:24:15 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BddFv-0000SC-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 19:03:43 -0400 Received: from bay16-f3.bay16.hotmail.com ([65.54.186.53] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1Bdce8-0006R9-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 18:24:40 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 24 Jun 2004 15:24:09 -0700 Received: from 62.83.196.190 by by16fd.bay16.hotmail.msn.com with HTTP; Thu, 24 Jun 2004 22:24:09 GMT X-Originating-IP: [62.83.196.190] X-Originating-Email: [placidamenteinsensible@hotmail.com] X-Sender: placidamenteinsensible@hotmail.com From: "fer no tengo" To: dhcwg@ietf.org Date: Fri, 25 Jun 2004 00:24:09 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Message-ID: X-OriginalArrivalTime: 24 Jun 2004 22:24:09.0419 (UTC) FILETIME=[F808F9B0:01C45A39] 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=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id TAA00448 X-Mailman-Approved-At: Thu, 24 Jun 2004 21:40:53 -0400 Subject: [dhcwg] DHCPv6 configuration files X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Hello, I'd like to know if exists any standard or recommended scheme for = the=20 configuration files of DHCPv6 servers and clients that everybody should=20 respect. Thank you. Bye. _________________________________________________________________ Reparaciones, servicios a domicilio, empresas, profesionales... Todo en l= a=20 gu=EDa telef=F3nica de QDQ. http://qdq.msn.es/msn.cfm _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Jun 24 23:14:15 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17352; Thu, 24 Jun 2004 23:14:15 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdh3v-0007zt-Tb; Thu, 24 Jun 2004 23:07:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdgf3-0002UW-C8 for dhcwg@megatron.ietf.org; Thu, 24 Jun 2004 22:41:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15838 for ; Thu, 24 Jun 2004 22:41:50 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdgf1-000275-IL for dhcwg@ietf.org; Thu, 24 Jun 2004 22:41:51 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bdge5-0001iQ-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 22:40:54 -0400 Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1Bdgcg-0001K2-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 22:39:26 -0400 Received: from ocean.jinmei.org (unknown [3ffe:501:100f:1048:acae:2aa0:194e:20bc]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 6DEA21525D; Fri, 25 Jun 2004 11:39:19 +0900 (JST) Date: Fri, 25 Jun 2004 11:39:26 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: strates Subject: Re: [dhcwg] [Question]DHCPv6 implementations In-Reply-To: <1489.040621@mail.ru> References: <1489.040621@mail.ru> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII 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 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org >>>>> On Mon, 21 Jun 2004 02:08:39 +0400, >>>>> strates said: > - KAME implementation for *BSDs: stateless DHCPv6, and they are not going > to improve it Just checking: what do you mean by "not going to improve it"? We (KAME) are actually seriously maintaining the implementation, including bug fixes and supporting new features. In fact, we've recently implemented the brand-new lifetime option, and have just newly supported the authentication mechanism. Perhaps you simply meant we do not have a plan to implement address allocation by DHCPv6. In that sense you're correct, though I'd not say "not going to improve it" meaning luck of a plan for one part of the big specification (even if the part is a major goal of the specification). Of course, I admit our implementation is "incomplete" in that it does not support address allocation. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Jun 25 08:42:07 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26984; Fri, 25 Jun 2004 08:42:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdpzL-0005n3-B4; Fri, 25 Jun 2004 08:39:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdpwe-0004x4-GS for dhcwg@megatron.ietf.org; Fri, 25 Jun 2004 08:36:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26583 for ; Fri, 25 Jun 2004 08:36:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdpwd-00014c-M8 for dhcwg@ietf.org; Fri, 25 Jun 2004 08:36:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bdpvg-0000kF-00 for dhcwg@ietf.org; Fri, 25 Jun 2004 08:35:41 -0400 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 1Bdpum-0000Ln-00 for dhcwg@ietf.org; Fri, 25 Jun 2004 08:34:44 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 25 Jun 2004 05:38:04 +0000 X-BrightmailFiltered: true 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 i5PCYASc011979; Fri, 25 Jun 2004 05:34:11 -0700 (PDT) Received: from volzw2k (che-vpn-cluster-2-2.cisco.com [10.86.242.2]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJS04347; Fri, 25 Jun 2004 08:34:08 -0400 (EDT) From: "Bernie Volz" To: "'strates'" , Subject: RE: [dhcwg] [Question]DHCPv6 implementations Date: Fri, 25 Jun 2004 08:34:08 -0400 Organization: Cisco Message-ID: <001001c45ab0$b621f840$6601a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.5709 In-Reply-To: <1489.040621@mail.ru> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 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 Content-Transfer-Encoding: 7bit X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7bit There's also http://klub.com.pl/dhcpv6/. > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] > On Behalf Of strates > Sent: Sunday, June 20, 2004 6:09 PM > To: dhcwg@ietf.org > Subject: [dhcwg] [Question]DHCPv6 implementations > > > I tried to learn what are nowdays available DHCPv6 > client/server implementations. Using the search engines I > could only find > - KAME implementation for *BSDs: stateless DHCPv6, and they > are not going to improve it > - Widespread linux-related http://dhcpv6.sourceforge.net > implementation > - Some traces of proprietary CISCO IOS and NEC > implementations (http://www.dhcpv6.org/ with only relay agent > available for public) > - USAGI implementation which leads to a project which claimed > himself 'dead'(http://www.linux-ipv6.org/links.html -> > http://www.hycomat.co.uk/dhcp/) > - Signs of some Linux implementation (there is some gentoo > related stuff, config files in google). > - DHCPv6 support in HP-UX > > It is quite strange for me, that only a few incomplete > implementations are present (yes, stateless IPv6 > autoconfiguration fulfils a lot of work instead of DHCPv6, > and many people seem to be satisfied with s-less > autoconfiguration and router prefix advertisement, but > still...) Later I found www.dfn.de/uploaded/DHCPv6.pdf and I > understood that it seems there are really only a few > implementations. Could anybody advertise anything in addition > to the list above? Thanks beforehand > > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Jun 25 08:57:48 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27854; Fri, 25 Jun 2004 08:57:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdq5m-0006zl-A0; Fri, 25 Jun 2004 08:46:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdq07-0005qK-CG for dhcwg@megatron.ietf.org; Fri, 25 Jun 2004 08:40:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26896 for ; Fri, 25 Jun 2004 08:40:13 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdq06-0002Is-Od for dhcwg@ietf.org; Fri, 25 Jun 2004 08:40:14 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bdpz7-000208-00 for dhcwg@ietf.org; Fri, 25 Jun 2004 08:39:14 -0400 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Bdpy9-0001QB-00; Fri, 25 Jun 2004 08:38:13 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 25 Jun 2004 05:41:41 -0700 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i5PCbe4N019237; Fri, 25 Jun 2004 05:37:40 -0700 (PDT) Received: from volzw2k (che-vpn-cluster-2-2.cisco.com [10.86.242.2]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJS04543; Fri, 25 Jun 2004 08:37:39 -0400 (EDT) From: "Bernie Volz" To: Subject: RE: [dhcwg] Last Call: 'Vendor-Identifying Vendor Options for DHCPv4' to Proposed Standard Date: Fri, 25 Jun 2004 08:37:38 -0400 Organization: Cisco Message-ID: <001101c45ab1$3363b460$6601a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.5709 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 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 Content-Transfer-Encoding: quoted-printable Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: quoted-printable I fully support this document moving forward and hope the IESG will move this document along quickly. This should greatly reduce the need for = vendors to "hijack" the site-specific options as they have been doing in the = past and which can cause interoperability issues. These new vendor options = are much better than the old ones from RFC 2132. - Bernie Volz > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20 > On Behalf Of The IESG > Sent: Thursday, June 24, 2004 10:35 AM > To: IETF-Announce > Cc: dhcwg@ietf.org > Subject: [dhcwg] Last Call: 'Vendor-Identifying Vendor=20 > Options for DHCPv4' to Proposed Standard=20 >=20 >=20 > The IESG has received a request from the Dynamic Host=20 > Configuration WG to=20 > consider the following document: >=20 > - 'Vendor-Identifying Vendor Options for DHCPv4 ' > as a Proposed Standard >=20 > The IESG plans to make a decision in the next few weeks, and=20 > solicits final comments on this action. Please send any=20 > comments to the iesg@ietf.org or ietf@ietf.org mailing lists=20 > by 2004-07-08. >=20 > The file can be obtained via=20 > http://www.ietf.org/internet-drafts/draft-ietf-dhc-vendor-03.t xt _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Jun 25 20:42:02 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23264; Fri, 25 Jun 2004 20:42:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Be1D7-0004rB-9A; Fri, 25 Jun 2004 20:38:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Be1BO-00045d-RZ for dhcwg@megatron.ietf.org; Fri, 25 Jun 2004 20:36:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23148 for ; Fri, 25 Jun 2004 20:36:36 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Be1BM-0003EU-TJ for dhcwg@ietf.org; Fri, 25 Jun 2004 20:36:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Be1At-0002yQ-00 for dhcwg@ietf.org; Fri, 25 Jun 2004 20:36:07 -0400 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx with esmtp (Exim 4.12) id 1Be19a-0002T5-00 for dhcwg@ietf.org; Fri, 25 Jun 2004 20:34:46 -0400 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HZW0060548V63@mailout2.samsung.com> for dhcwg@ietf.org; Sat, 26 Jun 2004 09:34:07 +0900 (KST) Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HZW00E6348SEX@mailout2.samsung.com> for dhcwg@ietf.org; Sat, 26 Jun 2004 09:34:05 +0900 (KST) Received: from LocalHost ([168.219.202.103]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HZW00ABD48SCC@mmp1.samsung.com> for dhcwg@ietf.org; Sat, 26 Jun 2004 09:34:04 +0900 (KST) Date: Sat, 26 Jun 2004 09:34:55 +0900 From: Soohong Daniel Park In-reply-to: To: v6ops@ops.ietf.org, Tim Chown , Christian Huitema Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7BIT Cc: Dhcwg Subject: [dhcwg] RE: ISATAP (Was RE: DSTM) X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org Content-Transfer-Encoding: 7BIT > For the record, we are using ISATAP as the default IPv6 connectivity on > the Microsoft campus, enabling every computer in our network to get IPv6 > connectivity. It is particularly useful in those buildings where native > IPv6 routers have not yet been deployed. Just reference. We are using a DHCP for enabling IPv6 connectivity in our IPv4 offices with simple option. Regards. - Daniel (Soohong Daniel Park) - Mobile Platform Lab. Samsung Electronics. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From nv33134@yahoo.com Mon Jun 28 01:42:51 2004 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26134 for ; Mon, 28 Jun 2004 01:42:51 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Beouo-0006wD-RU for dhc-archive@ietf.org; Mon, 28 Jun 2004 01:42:50 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Beoty-0006la-00 for dhc-archive@ietf.org; Mon, 28 Jun 2004 01:41:59 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Beosy-0006an-00; Mon, 28 Jun 2004 01:40:56 -0400 Received: from [202.104.153.66] (helo=ietf.org) by mx2.foretec.com with smtp (Exim 4.24) id 1Beo08-0005dE-29; Mon, 28 Jun 2004 00:44:17 -0400 From: "Atualidade Brasileira" To: announcement@ietf.org Subject: Moral e Economia: relação indispensável . obe X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 MIME-Version: 1.0 Content-Type: text/html Message-Id: Date: Mon, 28 Jun 2004 00:44:17 -0400 X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=11.2 required=5.0 tests=AWL,FORGED_MUA_EUDORA, FORGED_YAHOO_RCVD,FROM_ENDS_IN_NUMS,HTML_50_60,HTML_FONT_BIG, HTML_MESSAGE,MAILTO_SUBJ_REMOVE,MAILTO_TO_REMOVE,MAILTO_TO_SPAM_ADDR, MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,REMOVE_REMOVAL_2WORD, SUBJ_HAS_SPACES,SUBJ_ILLEGAL_CHARS autolearn=no version=2.60 X-Spam-Report: * 1.0 SUBJ_HAS_SPACES Subject contains lots of white space * 0.9 FROM_ENDS_IN_NUMS From: ends in numbers * 0.5 REMOVE_REMOVAL_2WORD BODY: List removal information * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 HTML_FONT_BIG BODY: HTML has a big font * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.2 HTML_50_60 BODY: Message is 50% to 60% HTML * 1.3 MAILTO_SUBJ_REMOVE BODY: mailto URI includes removal text * 0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset * 1.1 MAILTO_TO_SPAM_ADDR URI: Includes a link to a likely spammer email * 0.0 MAILTO_TO_REMOVE URI: Includes a 'remove' email address * 2.7 SUBJ_ILLEGAL_CHARS Subject contains too many raw illegal characters * 0.5 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers * 1.9 FORGED_MUA_EUDORA Forged mail pretending to be from Eudora * 0.4 AWL AWL: Auto-whitelist adjustment www.msn.com

(ref.:spd) Última hora! Acaba de chegar à Cidade do Vaticano filial pedido a S.S. João Paulo II: Santo Padre, protegei o Brasil da "esquerda católica"! Clique aqui para receber gratuitamente, por e-mail, o texto completo da carta.

Série Temas Patrulhados (8)

Moral e Economia: relação indispensável

A formação moral de uma nação, com sólidos princípios culturais e religiosos, é a condição para resolver em profundidade os problemas econômicos, afirma Lindenberg

Verdadeira solução

* Para solucionar em profundidade os problemas econômicos, é necessário que os responsáveis pela formação de uma nação - o Clero em primeiro lugar - efetivamente ensinem os princípios morais, culturais e religiosos que são o fundamento e a "conditio sine qua non" da ordem socioeconômica, afirma Adolpho Lindenberg no artigo "Economia e Moral", da Série Temas Patrulhados.

"Patrulhamento"

* Lindenberg é autor do livro "Os católicos e a economia de mercado", em que denuncia uma política com viés esquerdista que censura, marginaliza, "patrulha" ou encobre com um manto de silêncio, opiniões "politicamente incorretas", não afinadas com as ideologias de esquerda.

Progresso material e hábitos virtuosos

* O articulista acrescenta que a riqueza, a estabilidade econômica e o progresso material de um povo dependem não só do respeito ao direito de propriedade e às leis da livre iniciativa, mas de hábitos sociais virtuosos: esforço intenso, sistematizado, capacidade profissional adquirida pelo estudo e trabalho, vontade e força de poupar , morigeração nos gastos e discernimento na condução dos negócios.

Entrelaçamento da moral e a economia

* Infelizmente, esse entrelaçamento de preceitos de ordem moral e de questões econômicas é esquecido pela maioria dos prelados que prega reformas de estrutura, condena a inserção de nossa economia no cenário mundial, censura os lucros das empresas, etc. com o intuito alegado de minorar a sorte dos carentes e marginalizados. Sermões recomendando o hábito de trabalhar metódica e intensamente e a praxe de economizar seriam muito mais úteis do que incitamentos a protestos, greves e invasões, conclui Lindenberg em seu extenso artigo, que oferecemos gratuitamente aos leitores.

040610CN - ConstruNews

Links de opinião

Gostaríamos muito de receber seu seu voto eletrônico sobre a temática abordada neste e-mail, incluindo, se possível, conhecer sua valiosa opinião:

Concordo - Discrepo - EmTermos

Links gratuitos (e-Book e outros artigos):

* Para receber gratuitamente, por e-mail, o texto completo deste artigo, clique em: EsteArtigoCompletoGratuitamente(No.8)

E-BookGratuitoBr (em formato Word, com 11 artigos de Lindenberg)

IntroduçãoGratuitaDoLivro (em formato Word, Introdução do livro "Os católicos e a economia de mercado")

ArtigosAnteriores - ProximosArtigos

LinksGratuitos-TODOS (para receber, num só e-mail, todos os links gratuitos acima)

Outros links

EnEspañol - LinkToFreeTranslator

Lindenberg:DesejoAdquirirLivro (receberá instruções sobre como poder adquirir o livro no Brasil)

Remover Caso já tiver efetuado anteriormente, sem sucesso, o pedido de remoção, lhe solicitamos o enorme favor de nos enviar na íntegra o denominado "Código Fonte da Mensagem". Assim poderemos verificar a qual e-mail, exatamente, lhe escrevemos, e tirá-lo imediatamente do Address Book. Instruções para chegar até o "Código Fonte": no Outlook Express clique acima da mensagem com o botão direito do "mouse", depois em "Propriedades", "Detalhes" e "Código Fonte". Solicitamos sinceras desculpas pelos inconvenientes ocasionados.

A difusão desta mensagem --com o intuito de promover um debate cultural, respeitoso de idéias-- é de exclusiva responsabilidade da ConstruNews. Telefone de contato: (11) 9252 - 7873

 

 

 

 

From dhcwg-bounces@ietf.org Mon Jun 28 15:58:22 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27655; Mon, 28 Jun 2004 15:58:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bf1wc-0000lR-5D; Mon, 28 Jun 2004 15:37:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bf1mc-0007mc-Iu; Mon, 28 Jun 2004 15:27:14 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25202; Mon, 28 Jun 2004 15:27:12 -0400 (EDT) Message-Id: <200406281927.PAA25202@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Mon, 28 Jun 2004 15:27:12 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-rapid-commit-opt-05.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : Rapid Commit Option for DHCPv4 Author(s) : P. Kim, et al. Filename : draft-ietf-dhc-rapid-commit-opt-05.txt Pages : 12 Date : 2004-6-28 This document defines a new DHCPv4 option, modeled on the DHCPv6 Rapid Commit option, for obtaining IP address and configuration information using a 2-message exchange rather than the usual 4- message exchange, expediting client configuration. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-rapid-commit-opt-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-rapid-commit-opt-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-rapid-commit-opt-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-6-28151037.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-rapid-commit-opt-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-rapid-commit-opt-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-6-28151037.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Tue Jun 29 07:23:26 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11929; Tue, 29 Jun 2004 07:23:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BfGeT-00054g-EX; Tue, 29 Jun 2004 07:19:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BfGbp-0004g9-Jm for dhcwg@megatron.ietf.org; Tue, 29 Jun 2004 07:17:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11576 for ; Tue, 29 Jun 2004 07:17:05 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BfGbp-0005v4-30 for dhcwg@ietf.org; Tue, 29 Jun 2004 07:17:05 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BfGao-0005by-00 for dhcwg@ietf.org; Tue, 29 Jun 2004 07:16:03 -0400 Received: from tyholt.uninett.no ([158.38.60.10]) by ietf-mx with esmtp (Exim 4.12) id 1BfGZl-00051E-00 for dhcwg@ietf.org; Tue, 29 Jun 2004 07:14:57 -0400 Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b]) by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i5TBEPDW011487 for ; Tue, 29 Jun 2004 13:14:25 +0200 Received: (from venaas@localhost) by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i5TBEP1r014075 for dhcwg@ietf.org; Tue, 29 Jun 2004 13:14:25 +0200 X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f Date: Tue, 29 Jun 2004 13:14:25 +0200 From: Stig Venaas To: dhcwg@ietf.org Message-ID: <20040629111425.GA14068@sverresborg.uninett.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i 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 Subject: [dhcwg] Lifetime option (draft-ietf-dhc-lifetime-00.txt) X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org I would like to get some feedback from you on the lifetime option in order to submit a revised draft ASAP. The main issue, is what should happen when the lifetime expires. Currently it says: When the client detects that the lifetime has expired, it must do as follows. First it MUST ignore or remove the existing lifetime value. If it does not receive a new value in a later request, it MUST behave as if no value was ever provided. Next it MUST wait for a random amount of time between 0 and INF_MAX_DELAY. INF_MAX_DELAY is defined in [RFC 3315]. Finally it must make a new DHCP request, updating the current configuration. This request will usually be an Information-request Message. If client fails to receive a valid response from a server, it MUST retransmit the message according to the retransmission rules specified in [RFC 3315]. If the update fails, the current configuration must be kept as if no lifetime was ever provided. I think it might be better to retry. The retry interval could be a function of the lifetime. The reason I didn't in the current version, is that I was worried what would happen if someone sent a forged reply with say a lifetime of 1s. What do you think? Should there be some retry? What should the function be? Also, should a lifetime of say 0 or 0xffffffff have any special meanings, e.g. infinity? Personally I don't see a need for that. If not, 0 is meaningless, so I could possibly say that the value must be set to non-zero by server, and that clients should ignore 0. I would be happy for any other comments you might have. Stig _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg