From mailman-admin@ietf.org Sat May 1 12:00:17 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id 4D10958EB9 for ; Sat, 1 May 2004 12:00:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJuak-000811-5N for ietf-ppplog@merit.edu; Sat, 01 May 2004 09:31:42 -0400 Date: Sat, 01 May 2004 09:31:42 -0400 Message-ID: <20040501133142.27207.81237.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: ietf-ppplog@merit.edu 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, pppext-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 ietf-ppplog@merit.edu: List Password // URL ---- -------- pppext@ietf.org iwhaka https://www1.ietf.org/mailman/options/pppext/ietf-ppplog%40merit.edu From pppext-admin@ietf.org Mon May 10 12:54:11 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id 12FC659199; Mon, 10 May 2004 12:54: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 1BNDtl-0003P7-G6; Mon, 10 May 2004 12:45:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BN4G9-0002rX-A6 for pppext@optimus.ietf.org; Mon, 10 May 2004 02:27:29 -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 CAA08823 for ; Mon, 10 May 2004 02:27: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 1BN4G5-0002cq-Ir for pppext@ietf.org; Mon, 10 May 2004 02:27:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BN4FH-0002LD-00 for pppext@ietf.org; Mon, 10 May 2004 02:26:35 -0400 Received: from [221.148.23.2] (helo=mail.softteleware.com ident=[W2ayOW52pu6dsAMX6CrJ5DDTLENEYaW3]) by ietf-mx with esmtp (Exim 4.12) id 1BN4Ed-00023o-00 for pppext@ietf.org; Mon, 10 May 2004 02:25:56 -0400 Received: from 192.168.1.43 (IDENT:f5qgVkOJHM0EJVycztYRgI9+0h5/5gIr@softeleware.com [221.148.23.2]) (authenticated) by mail.softteleware.com (8.11.6/8.11.6) with ESMTP id i4A5g6M27742 for ; Mon, 10 May 2004 14:42:06 +0900 Received: from phpmailer ([192.168.1.43]) by 192.168.1.43 with HTTP (UebiMiau); Mon, 10 May 2004 14:42:06 +0900 Date: Mon, 10 May 2004 14:42:06 +0900 To: pppext@ietf.org From: Mykim Reply-To: Mykim Message-ID: X-Priority: 3 X-Mailer: UebiMiau [PHPMailer version 1.70] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/html; charset="euc-kr" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.8 required=5.0 tests=HTML_MESSAGE, HTML_MIME_NO_HTML_TAG,MIME_HTML_ONLY autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Subject: [Pppext] Is there a IPv6 Configuration Protocol Options for DNS IP address? Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , Hello all,

Is there a IPv6 Configuration Protocol Options in IPv6CP?
If there is no IPv6 Configuration Protocol Option then I'd like to know how to get IPv6 DNS address when negotiate PPP.
(I found draft document which is filed as "PPP IPV6 Control Protocol Extensions for DNS Server Addresses". But, it was expired at December 2004 and not published as RFC.)

I expect your prompt reply.
_______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-admin@ietf.org Mon May 10 13:46:54 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id 7F7F758F9D; Mon, 10 May 2004 13:46:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNEly-00042B-8n; Mon, 10 May 2004 13:41:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNEHt-0007ph-AE for pppext@optimus.ietf.org; Mon, 10 May 2004 13:09:57 -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 NAA17495 for ; Mon, 10 May 2004 13:09:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNEHr-0000G1-FG for pppext@ietf.org; Mon, 10 May 2004 13:09:55 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNEGr-0007hd-00 for pppext@ietf.org; Mon, 10 May 2004 13:08:53 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1BNEG0-00074S-00 for pppext@ietf.org; Mon, 10 May 2004 13:08:00 -0400 Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-5.cisco.com with ESMTP; 10 May 2004 10:07:42 -0700 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i4AH7R0Q007951; Mon, 10 May 2004 10:07:28 -0700 (PDT) Received: from bray-w2k01.cisco.com (che-vpn-cluster-2-86.cisco.com [10.86.242.86]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id ATA62129; Mon, 10 May 2004 10:06:39 -0700 (PDT) Message-Id: <4.3.2.7.2.20040510130157.022796d0@mira-sjcm-4.cisco.com> X-Sender: bray@mira-sjcm-4.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 10 May 2004 13:07:24 -0400 To: Mykim From: John Bray Subject: Re: [Pppext] Is there a IPv6 Configuration Protocol Options for DNS IP address? Cc: pppext@ietf.org In-Reply-To: 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.0 required=5.0 tests=none autolearn=no version=2.60 Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , At 01:42 AM 5/10/2004, Mykim wrote: >Hello all, > >Is there a IPv6 Configuration Protocol Options in IPv6CP? >If there is no IPv6 Configuration Protocol Option then I'd like to know >how to get IPv6 DNS address when negotiate PPP. Use DHCP. >(I found draft document which is filed as "PPP IPV6 Control Protocol >Extensions for DNS Server Addresses". But, it was expired at December 2004 >and not published as RFC.) It was rejected by the working group. The consensus was that it duplicated the existing capability already provided by DHCP. John >I expect your prompt reply. >_______________________________________________ Pppext mailing list >Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-admin@ietf.org Mon May 10 15:26:46 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id A7336591E3; Mon, 10 May 2004 15:26:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNGFI-0006ki-Is; Mon, 10 May 2004 15:15:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNG9A-0003KJ-Rv for pppext@optimus.ietf.org; Mon, 10 May 2004 15:09:04 -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 PAA25578 for ; Mon, 10 May 2004 15:09:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNG97-0002t1-Pe for pppext@ietf.org; Mon, 10 May 2004 15:09:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNG8A-0002YW-00 for pppext@ietf.org; Mon, 10 May 2004 15:08:03 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1BNG7O-0001uZ-00 for pppext@ietf.org; Mon, 10 May 2004 15:07:14 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-5.cisco.com with ESMTP; 10 May 2004 12:06:57 -0700 Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4AJ6fC1016508; Mon, 10 May 2004 12:06:41 -0700 (PDT) Received: from gwzw2k (sjc-vpn2-78.cisco.com [10.21.112.78]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with ESMTP id MAA29228; Mon, 10 May 2004 12:06:40 -0700 (PDT) Reply-To: From: "Glen Zorn" To: "'John Bray'" , "'Mykim'" Cc: Subject: RE: [Pppext] Is there a IPv6 Configuration Protocol Options for DNS IP address? Date: Mon, 10 May 2004 12:05:59 -0700 Organization: Cisco Systems Message-ID: <005c01c436c1$ea536b20$710b000a@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.4024 In-Reply-To: <4.3.2.7.2.20040510130157.022796d0@mira-sjcm-4.cisco.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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 Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , pppext-admin@ietf.org writes: > At 01:42 AM 5/10/2004, Mykim wrote: >> Hello all, >> >> Is there a IPv6 Configuration Protocol Options in IPv6CP? >> If there is no IPv6 Configuration Protocol Option then I'd like to >> know how to get IPv6 DNS address when negotiate PPP. > > Use DHCP. > >> (I found draft document which is filed as "PPP IPV6 Control Protocol >> Extensions for DNS Server Addresses". But, it was expired at >> December 2004 and not published as RFC.) > > It was rejected by the working group. The consensus was that it > duplicated the existing capability already provided by DHCP. One might add that the IETF is rapidly duplicating the capability already provided by ISO/OSI: that of valuing intellectual purity over running networks; if this continues, one might also expect a similar slide into irrelevance and the twilight obscurity of textbook footnotes. OF course, CDMA2000 vendors won't throw away backward compatibility with their installed base just because the IETF says "use DHCP", nor does this edict change the reasons that they didn't implement DHCP in the first place. I expect that what will happen is that 3GPP2 will simply define a new vendor-specific option and use PPP. The WG will have washed its hands, to the effect that an even larger percentage of PPP implementations will be non-standard. > > John > > >> I expect your prompt reply. >> _______________________________________________ Pppext mailing list >> Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext > > > _______________________________________________ > Pppext mailing list > Pppext@ietf.org > https://www1.ietf.org/mailman/listinfo/pppext Hope this helps, ~gwz "They that can give up essential liberty to obtain a little temporary safety deserve neither..." -- Benjamin Franklin, 1759 "It is forbidden to kill; therefore all murderers are punished unless they kill in large numbers and to the sound of trumpets." -- Voltaire _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-admin@ietf.org Mon May 10 16:03:27 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id E0AD05917C; Mon, 10 May 2004 16:03:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNGnq-0005yl-NV; Mon, 10 May 2004 15:51:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNGgE-0004ad-Bs for pppext@optimus.ietf.org; Mon, 10 May 2004 15:43: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 PAA28689 for ; Mon, 10 May 2004 15:43: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 1BNGgC-00076Q-Vg for pppext@ietf.org; Mon, 10 May 2004 15:43:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNGfG-0006j9-00 for pppext@ietf.org; Mon, 10 May 2004 15:42:14 -0400 Received: from h-66-167-171-107.sttnwaho.covad.net ([66.167.171.107] helo=internaut.com) by ietf-mx with esmtp (Exim 4.12) id 1BNGeL-0006Lc-00 for pppext@ietf.org; Mon, 10 May 2004 15:41:17 -0400 Received: from localhost (aboba@localhost) by internaut.com (8.10.2/8.10.2) with ESMTP id i4AJjHe02360; Mon, 10 May 2004 12:45:17 -0700 Date: Mon, 10 May 2004 12:45:17 -0700 (PDT) From: Bernard Aboba To: Glen Zorn Cc: pppext@ietf.org Subject: RE: [Pppext] Is there a IPv6 Configuration Protocol Options for DNS IP address? In-Reply-To: <005c01c436c1$ea536b20$710b000a@amer.cisco.com> Message-ID: References: <005c01c436c1$ea536b20$710b000a@amer.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=AWL autolearn=no version=2.60 Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , > this edict change the reasons that they didn't implement DHCP in the > first place. The reasons that DHCP was not implemented for IPv4 do not apply to IPv6. It is widely expected that "stateless DHCPv6" servers will be implemented on NASen, so that there is no need to deploy DHCPv6 servers in the network. _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-admin@ietf.org Mon May 10 19:34:21 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id 2D252591C2; Mon, 10 May 2004 19:34:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNK8y-0007pz-3t; Mon, 10 May 2004 19:25:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNK5J-0006aq-BG for pppext@optimus.ietf.org; Mon, 10 May 2004 19:21: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 TAA15963 for ; Mon, 10 May 2004 19:21:19 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNK5H-0007Fw-NA for pppext@ietf.org; Mon, 10 May 2004 19:21:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNK4F-0006uN-00 for pppext@ietf.org; Mon, 10 May 2004 19:20:15 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1BNK3H-0006EU-00 for pppext@ietf.org; Mon, 10 May 2004 19:19:15 -0400 Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4ANIfSu012042; Mon, 10 May 2004 16:18:42 -0700 (PDT) Received: from gwzw2k (sjc-vpn4-695.cisco.com [10.21.82.183]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with ESMTP id QAA14762; Mon, 10 May 2004 16:18:41 -0700 (PDT) Reply-To: From: "Glen Zorn" To: "'Bernard Aboba'" Cc: Subject: RE: [Pppext] Is there a IPv6 Configuration Protocol Options for DNS IP address? Date: Mon, 10 May 2004 16:18:01 -0700 Organization: Cisco Systems Message-ID: <000901c436e5$1c39d7a0$bf4ba5ce@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.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: 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 Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , Bernard Aboba writes: >> this edict change the reasons that they didn't implement DHCP in the >> first place. > > The reasons that DHCP was not implemented for IPv4 do not apply to > IPv6. I honestly don't know what reason(s) 3GPP2 had for not using DHCP w/IPv4. However, I'm pretty sure that whatever those reasons were, they can't be changed by proclamation. ;-) > It is widely expected that "stateless DHCPv6" servers will be > implemented on NASen, so that there is no need to deploy DHCPv6 > servers in the network. Hope this helps, ~gwz "They that can give up essential liberty to obtain a little temporary safety deserve neither..." -- Benjamin Franklin, 1759 "It is forbidden to kill; therefore all murderers are punished unless they kill in large numbers and to the sound of trumpets." -- Voltaire _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-admin@ietf.org Mon May 10 21:01:33 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id B11BF591C3; Mon, 10 May 2004 21:01:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNLWz-0001G2-Jt; Mon, 10 May 2004 20:54:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNLTL-0000Ov-FU for pppext@optimus.ietf.org; Mon, 10 May 2004 20:50: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 UAA19568 for ; Mon, 10 May 2004 20:50:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNLTJ-00066d-4r for pppext@ietf.org; Mon, 10 May 2004 20:50:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNLSI-0005mA-00 for pppext@ietf.org; Mon, 10 May 2004 20:49:11 -0400 Received: from [221.148.23.2] (helo=mail.softteleware.com ident=[NF2Xtuc4JNbHySsAsBcOB8i28nqO62IM]) by ietf-mx with esmtp (Exim 4.12) id 1BNLRG-000584-00 for pppext@ietf.org; Mon, 10 May 2004 20:48:06 -0400 Received: from 192.168.1.43 (IDENT:sOqSnAouQWQk4uiWM4FgIJHmqqerx+Zd@softeleware.com [221.148.23.2]) (authenticated) by mail.softteleware.com (8.11.6/8.11.6) with ESMTP id i4B03xM09966; Tue, 11 May 2004 09:03:59 +0900 Received: from phpmailer ([192.168.1.43]) by 192.168.1.43 with HTTP (UebiMiau); Tue, 11 May 2004 09:03:59 +0900 Date: Tue, 11 May 2004 09:03:59 +0900 To: John Bray From: Mykim Cc: pppext@ietf.org Reply-To: Mykim Subject: Re: [Pppext] Is there a IPv6 Configuration Protocol Options for DNS IP address? Message-ID: X-Priority: 3 X-Mailer: UebiMiau [PHPMailer version 1.70] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/html; charset="euc-kr" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=2.1 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE, HTML_MIME_NO_HTML_TAG,MIME_HTML_ONLY autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , Thank you for your reply.

In CDMA 2000 environmant, MS(Mobile Station) that uses IPv6 gets IPv6 address by  negotiating PPP(IPv6CP) with PDSN(Packet Data Serving Node).
In this case, how can MS get IPv6 DNS address? (If MS not use DHCP)
If MS has to get IPv6 DNS address by using DHCP, does DHCP server have to exist in CDMA 2000 network?

--------- Original Message --------
sender: "John Bray" <bray@cisco.com>
To: "Mykim" <mykim@softteleware.com>
Cc: pppext@ietf.org
subject: Re: [Pppext] Is there a IPv6 Configuration Protocol Options for DNS IP address?
Date: 11/05/04 10:23

At 01:42 AM 5/10/2004, Mykim wrote:
>Hello all,
>
>Is there a IPv6 Configuration Protocol Options in IPv6CP?
>If there is no IPv6 Configuration Protocol Option then I'd like to know
>how to get IPv6 DNS address when negotiate PPP.

Use DHCP.

>(I found draft document which is filed as "PPP IPV6 Control Protocol
>Extensions for DNS Server Addresses". But, it was expired at December 2004
>and not published as RFC.)

It was rejected by the working group. The consensus was that it duplicated
the existing capability already provided by DHCP.

John


>I expect your prompt reply.
>_______________________________________________ Pppext mailing list
>Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext
_______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-admin@ietf.org Mon May 10 21:41:56 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id C0C31591DE; Mon, 10 May 2004 21:41:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNM8j-0000Mj-D5; Mon, 10 May 2004 21:33:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNM2G-0007jF-6s for pppext@optimus.ietf.org; Mon, 10 May 2004 21:26:20 -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 VAA21027 for ; Mon, 10 May 2004 21:26: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 1BNM2D-0002fj-IO for pppext@ietf.org; Mon, 10 May 2004 21:26:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNM1H-0002Lr-00 for pppext@ietf.org; Mon, 10 May 2004 21:25:20 -0400 Received: from segue.merit.edu ([198.108.1.41]) by ietf-mx with esmtp (Exim 4.12) id 1BNM0i-00022F-00 for pppext@ietf.org; Mon, 10 May 2004 21:24:44 -0400 Received: by segue.merit.edu (Postfix) id 86917591CC; Mon, 10 May 2004 21:24:45 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from webshielde250.example (ip-90-191-97-218.anlai.com [218.97.191.90]) by segue.merit.edu (Postfix) with SMTP id 9A44458C91 for ; Mon, 10 May 2004 21:24:43 -0400 (EDT) Received: from voip_ems1(10.8.1.50) by webshielde250.example via csmap id 4cb6cdf4_a2ea_11d8_85a1_0002b3bc9708_8594; Tue, 11 May 2004 09:27:00 +0800 (CST) Date: Tue, 11 May 2004 09:29:02 +0800 To: "Ietf-ppp" From: "Fred" Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--------dorsbkwcitzouwlimlmm" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MIME_HTML_ONLY autolearn=no version=2.60 Subject: [Pppext] RE: Message Notify Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , ----------dorsbkwcitzouwlimlmm Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
----------dorsbkwcitzouwlimlmm Content-Type: application/octet-stream; name="Information.vbs" Content-Disposition: attachment; filename="Information.vbs" X-NAI-WebShielde250-mimepp: Attachment repaired Content-Transfer-Encoding: base64 ----------dorsbkwcitzouwlimlmm-- _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-admin@ietf.org Tue May 11 06:58:28 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id 5067558FFC; Tue, 11 May 2004 06:58:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNUsj-00019S-AS; Tue, 11 May 2004 06:53:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNUnY-0008F0-Ek for pppext@optimus.ietf.org; Tue, 11 May 2004 06:47: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 GAA18437 for ; Tue, 11 May 2004 06:47: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 1BNUnU-0004ET-8L for pppext@ietf.org; Tue, 11 May 2004 06:47:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNUmY-0003sB-00 for pppext@ietf.org; Tue, 11 May 2004 06:46:43 -0400 Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx with esmtp (Exim 4.12) id 1BNUlc-0003W0-00 for pppext@ietf.org; Tue, 11 May 2004 06:45:45 -0400 Received: from eastmail2bur.East.Sun.COM ([129.148.13.40]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id i4BAhrhO024016; Tue, 11 May 2004 04:43:54 -0600 (MDT) Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail2bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id i4BAjEii029134; Tue, 11 May 2004 06:45:14 -0400 (EDT) Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.12.11+Sun/8.12.11) with ESMTP id i4BAj50m003778; Tue, 11 May 2004 06:45:05 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.12.11+Sun/8.12.11/Submit) id i4BAj52G003775; Tue, 11 May 2004 06:45:05 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16544.44721.697973.281653@gargle.gargle.HOWL> Date: Tue, 11 May 2004 06:45:05 -0400 From: James Carlson To: Mykim Cc: John Bray , pppext@ietf.org Subject: Re: [Pppext] Is there a IPv6 Configuration Protocol Options for DNS IP address? In-Reply-To: Mykim's message of 11 May 2004 09:03:59 References: X-Mailer: VM 7.01 under Emacs 21.3.1 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,HTML_MESSAGE autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , Mykim writes: > Thank you for your reply.

In CDMA 2000 environmant, MS(Mobile > Station) that uses IPv6 gets IPv6 address by  negotiating > PPP(IPv6CP) with PDSN(Packet Data Serving Node).
In this > case, how can MS get IPv6 DNS address? (If MS not use DHCP)
If Why doesn't it use DHCP? > MS has to get IPv6 DNS address by using DHCP, does DHCP > server have to exist in CDMA 2000 network?

The "server" in this case is extraordinarily trivial: all it needs to be able to do is receive a DHCPINFORM message from the client and send DHCPACK in response. Having the same system that terminates the PPP connection also providing DHCP service would make a lot of sense -- no extra hardware, and a trivial amount of software; likely the same amount of software that would have been required to add the DNS server address options to PPP. -- James Carlson, IP Systems Group Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677 _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-admin@ietf.org Mon May 17 11:33:51 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22]) by segue.merit.edu (Postfix) with ESMTP id 986E759029; Mon, 17 May 2004 11:33:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjzN-0003L5-Ls; Mon, 17 May 2004 11:25:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjye-0003Cc-8l for pppext@optimus.ietf.org; Mon, 17 May 2004 11:24:28 -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 LAA28215 for ; Mon, 17 May 2004 11:24:26 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPjyd-0006zL-By for pppext@ietf.org; Mon, 17 May 2004 11:24:27 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPjxX-0006eE-00 for pppext@ietf.org; Mon, 17 May 2004 11:23:20 -0400 Received: from [202.125.87.74] (helo=brahma.intotoind.com) by ietf-mx with esmtp (Exim 4.12) id 1BPjwY-0006JJ-00 for pppext@ietf.org; Mon, 17 May 2004 11:22:18 -0400 Received: from ajay.intoto.com (3mc66.intotoind.com [172.16.3.66]) by brahma.intotoind.com (8.12.11/8.12.8) with ESMTP id i4HFKg7f011245 for ; Mon, 17 May 2004 20:50:42 +0530 Message-Id: <5.1.0.14.0.20040517205948.02a57f60@172.16.1.10> X-Sender: ajays@172.16.1.10 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 17 May 2004 21:05:27 +0530 To: pppext@ietf.org From: Ajay Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.41 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: [Pppext] MCMLPPP Implementation Sender: pppext-admin@ietf.org Errors-To: pppext-admin@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: PPP Extensions List-Post: List-Help: List-Subscribe: , Hi, I have a implementation of ppp that supports multi-class extensions to MLPPP. I wish to inter-op this s/w with some other implementation. If anybody is aware of an implementation that supports multi-class exts to MP, please do let me know. Regards Ajay _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Fri May 28 07:07:54 2004 Return-Path: Delivered-To: ietf-ppplog@merit.edu Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by segue.merit.edu (Postfix) with ESMTP id E861359506; Fri, 28 May 2004 07:07:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTf7a-0007H2-Ml; Fri, 28 May 2004 07:01:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTTzq-0003df-5b for pppext@megatron.ietf.org; Thu, 27 May 2004 19:09:10 -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 TAA03715 for ; Thu, 27 May 2004 19:09:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BTTzn-0006Y9-Qo for pppext@ietf.org; Thu, 27 May 2004 19:09:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BTTys-0006H9-00 for pppext@ietf.org; Thu, 27 May 2004 19:08:11 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BTTy2-0005jb-00; Thu, 27 May 2004 19:07:18 -0400 Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i4RN6FJ26016; Thu, 27 May 2004 16:06:15 -0700 (PDT) Message-Id: <200405272306.i4RN6FJ26016@boreas.isi.edu> To: IETF-Announce: ; From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 27 May 2004 16:06:15 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.0 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 X-Mailman-Approved-At: Fri, 28 May 2004 07:01:53 -0400 Cc: pppext@ietf.org, rfc-editor@rfc-editor.org Subject: [Pppext] RFC 3772 on Point-to-Point Protocol (PPP) Vendor Protocol X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3772 Title: Point-to-Point Protocol (PPP) Vendor Protocol Author(s): J. Carlson, R. Winslow Status: Standards Track Date: May 2004 Mailbox: james.d.carlson@sun.com, richard.winslow@l-3com.com Pages: 10 Characters: 19846 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pppext-vendor-protocol-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3772.txt The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. The PPP Vendor Extensions document adds vendor-specific general-purpose Configuration Option and Code numbers. This document extends these features to cover vendor-specific Network, Authentication, and Control Protocols. This document is a product of the Point-to-Point Protocol Extensions Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040527160452.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3772 --OtherAccess Content-Type: Message/External-body; name="rfc3772.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040527160452.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext --NextPart--