From pppext-bounces@ietf.org Tue Apr 25 12:27:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYQNm-0004y9-FE; Tue, 25 Apr 2006 12:27:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYQNl-0004y4-Ok for pppext@ietf.org; Tue, 25 Apr 2006 12:27:21 -0400 Received: from test-iport-2.cisco.com ([171.71.176.105]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYQNl-0000S7-BZ for pppext@ietf.org; Tue, 25 Apr 2006 12:27:21 -0400 Received: from sj-core-1.cisco.com ([171.71.177.237]) by test-iport-2.cisco.com with ESMTP; 25 Apr 2006 09:27:20 -0700 Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k3PGRKw1008758; Tue, 25 Apr 2006 09:27:20 -0700 (PDT) Received: from [10.32.244.219] (stealth-10-32-244-219.cisco.com [10.32.244.219]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k3PGQCb3023828; Tue, 25 Apr 2006 09:26:12 -0700 In-Reply-To: <444E45BD.7C03D843@ericsson.com> References: <73FCF83DC4E52B4EAC7A4B189A11B47F02436BD3@esealmw114.eemea.ericsson.se> <444E45BD.7C03D843@ericsson.com> Mime-Version: 1.0 (Apple Message framework v749.3) Message-Id: <224DFB9F-FA9D-4DF8-ADE3-719F4EF6FA68@cisco.com> From: Fred Baker Date: Tue, 25 Apr 2006 09:27:19 -0700 To: Michal Szewczyk , stevec@microsoft.com X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=4498; t=1145982372; x=1146846372; c=relaxed/simple; s=oregon; h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20 |Subject:Re=3A=20RFC1977 |To:Michal=20Szewczyk=20, =0A=20stevec@microsof t.com; X=v=3Dcisco.com=3B=20h=3D6TC1lY6+Ra8++JL5QDMx6UefQzU=3D; b=gvOrbljuO4vlTs5MJFX+HtUwXqzyeXl/s1qvdUCKdu6AoZVISeZyrGsuX8ArHMFjBW+Wsfso yEvEsi0QJIrt/6AkAeL5SKEs4pOfggYilJhxr+2Ut4kZE6gmuKOdup/c; Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass ( 28 extraneous bytes; sig from cisco.com verified; ); X-Spam-Score: 0.1 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: pppext@ietf.org Subject: [Pppext] Re: RFC1977 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: , Content-Type: multipart/mixed; boundary="===============1336122309==" Errors-To: pppext-bounces@ietf.org --===============1336122309== Content-Type: multipart/alternative; boundary=Apple-Mail-5-171514755 --Apple-Mail-5-171514755 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed OK. I would suggest that this be taken to the list or to the author. I stopped being the chair in 1995, never mind what the RFC says about my being the "current" chair (I never did understand why PPP documents listed me instead of the mailing list). On Apr 25, 2006, at 8:52 AM, Michal Szewczyk wrote: > Hi, > Sorry my mistake 1877 :) > > Best Regards > MIke > > Fred Baker wrote: >> Are we talking about the same document? >> >> http://www.ietf.org/rfc/rfc1977.txt >> 1977 PPP BSD Compression Protocol. V. Schryver. August 1996. (Format: >> TXT=50747 bytes) (Status: INFORMATIONAL) >> >> Vernon's document doesn't mention DNS... >> >> On Apr 25, 2006, at 7:58 AM, Michal Szewczyk ((WA/EPO)) wrote: >> > Hi Fred, >> > >> > just a small question regarding the RFC above. >> > If it's possible for the certain equipment not to provide the frame >> > where should be the DNS ? >> > >> > "By default, no primary DNS address is provided." >> > >> > Is that mean there will not be the DNS field at all in such a >> > frame ? or it will be with \NULL or 0.0.0.0 ? >> > >> > Best Regards >> > Mike >> > >> > -- >> > No virus found in this outgoing message. >> > Checked by AVG Free Edition. >> > Version: 7.1.385 / Virus Database: 268.4.5/321 - Release Date: >> > 2006-04-21 >> >> -- >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.1.385 / Virus Database: 268.4.5/321 - Release Date: >> 2006-04-21 >> --Apple-Mail-5-171514755 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 OK. I would suggest that this be = taken to the list or to the author. I stopped being the chair in 1995, = never mind what the RFC says about my being the "current" chair (I never = did understand why PPP documents listed me instead of the mailing = list).

On Apr 25, 2006, at 8:52 AM, Michal Szewczyk = wrote:

Hi,

Sorry my mistake 1877 :)

Best Regards =
MIke

Fred Baker wrote:

Are we talking about the same document?

http://www.ietf.org/rfc/rfc19= 77.txt
1977 PPP BSD Compression = Protocol. V. Schryver. August 1996. (Format:
=A0=A0=A0=A0=A0 TXT=3D50747 bytes) (Status: = INFORMATIONAL)

Vernon's document doesn't = mention DNS...

On Apr 25, 2006, at 7:58 = AM, Michal Szewczyk ((WA/EPO)) wrote:
> = Hi Fred,
>
> just a small question regarding the RFC above. =
> If it's possible for the certain equipment = not to provide the frame
> where should = be the DNS ?
>
> "By default, no primary DNS address is = provided."
>
> Is that mean there will not be the DNS field at all in = such a
> frame ? or it will be with = \NULL or 0.0.0.0 ?
>
> Best Regards
> = Mike
>
> = --
> No virus found in this outgoing = message.
> Checked by AVG Free = Edition.
> Version: 7.1.385 / Virus = Database: 268.4.5/321 - Release Date:
> = 2006-04-21

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.5/321 - Release = Date: 2006-04-21
=A0

=

= --Apple-Mail-5-171514755-- --===============1336122309== 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 --===============1336122309==-- From pppext-bounces@ietf.org Tue Apr 25 12:42:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYQcP-0001jU-OK; Tue, 25 Apr 2006 12:42:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYQcO-0001jP-Lo for pppext@ietf.org; Tue, 25 Apr 2006 12:42:28 -0400 Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYQcL-0001k2-AV for pppext@ietf.org; Tue, 25 Apr 2006 12:42:28 -0400 Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id k3PGgO4d000357 for ; Tue, 25 Apr 2006 10:42:24 -0600 (MDT) Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id k3PGgNbF015683 for ; Tue, 25 Apr 2006 12:42:24 -0400 (EDT) Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5) with ESMTP id k3PGgNxl006044; Tue, 25 Apr 2006 12:42:23 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5/Submit) id k3PGgNgv006041; Tue, 25 Apr 2006 12:42:23 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17486.20847.483787.158350@gargle.gargle.HOWL> Date: Tue, 25 Apr 2006 12:42:23 -0400 From: James Carlson To: Michal Szewczyk Subject: Re: [Pppext] Re: RFC1977 In-Reply-To: Fred Baker's message of 25 April 2006 09:27:19 References: <73FCF83DC4E52B4EAC7A4B189A11B47F02436BD3@esealmw114.eemea.ericsson.se> <444E45BD.7C03D843@ericsson.com> <224DFB9F-FA9D-4DF8-ADE3-719F4EF6FA68@cisco.com> X-Mailer: VM 7.01 under Emacs 21.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: pppext@ietf.org, Fred Baker , stevec@microsoft.com 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: , Errors-To: pppext-bounces@ietf.org > >> > just a small question regarding the RFC above. > >> > If it's possible for the certain equipment not to provide the frame > >> > where should be the DNS ? > >> > > >> > "By default, no primary DNS address is provided." > >> > > >> > Is that mean there will not be the DNS field at all in such a > >> > frame ? or it will be with \NULL or 0.0.0.0 ? This means that if the option is not included at all, then the peer isn't expected to get a primary DNS address via this mechanism. It may have one through local configuration, BOOTP/DHCP over PPP, assuming the peer to be a server, or possibly other means. Note that the option is a little strange (the address supplied in Configure-Request actually refers to a node on the _other_ side of the link) and, though it's fairly commonly implemented, it's not a standard. The usual usage, when enabled, is that the side requiring a DNS server address (the "client") includes the Primary DNS Server Address option in its IPCP Configure-Request message, with the address set to 0.0.0.0. The peer can then either respond with Configure-Nak to specify a non-zero address for it to use, or with Configure-Reject to say that none is available. The originator then must send _another_ IPCP Configure-Request message with the right option contents (either setting the address per the Nak or removing the option altogether on Reject). Of course, good implementations should sanity-check that Configure-Nak as well. A Nak specifying 0.0.0.0 or some illegal address ought not be used, and should result in treating the message as though Configure-Reject were received. -- James Carlson, KISS Network Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext