From owner-ietf-ppp@merit.edu Fri Oct 10 09:16:18 2003 Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26895 for ; Fri, 10 Oct 2003 09:16:17 -0400 (EDT) Received: by trapdoor.merit.edu (Postfix) id 74F1491311; Fri, 10 Oct 2003 09:15:33 -0400 (EDT) Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id E128F91321; Fri, 10 Oct 2003 09:15:32 -0400 (EDT) Delivered-To: ietf-ppp@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 166F491311 for ; Fri, 10 Oct 2003 09:15:31 -0400 (EDT) Received: by segue.merit.edu (Postfix) id F1FFB5DDE0; Fri, 10 Oct 2003 09:15:30 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from cvis162.marconicomms.com (cvis162.marconicomms.com [128.87.251.112]) by segue.merit.edu (Postfix) with ESMTP id 2A4FA5DDA8 for ; Fri, 10 Oct 2003 09:15:30 -0400 (EDT) Received: from cvis155.mail.marconicomms.com by cvis162.marconicomms.com with ESMTP (8.11.7p1+Sun/mcig-4) id h9ADFR622282; Fri, 10 Oct 2003 14:15:27 +0100 (BST) Received: from cvdgwy01.uk.marconicomms.com (unverified) by cvis156.mail.marconicomms.com (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Fri, 10 Oct 2003 14:15:21 +0100 Subject: Reliable PPP To: ietf-ppp@merit.edu From: "Fabio Poggi" Date: Fri, 10 Oct 2003 15:13:56 +0200 Message-ID: X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1 (5012HF354 | August 26, 2003) at 10/10/2003 14:15:10 MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu Dear all, I need your suggestion. I need to connect an IP host with a proper static IP address to an IP network through a TDM network. Moreover I need a reliable IP connection between this IP host and the IP network. So, I thought to set up two different PPP session (this would guarantee physical reliability), over different TDM links, toward the IP network and to manage these PPP links with an adaptation function in my IP host (in order to not duplicate IP traffic on IP network). This function will use, in Tx toward the IP network, the PPP session from which, in Rx, it has receive PPP traffic. When a fail occurs, the adaptation function switch on the other PPP session. Two PPP sessions are monitored by Echo Request/Reply message. The IP network will see my IP host's IP address on two different PPP link and it will be a task of IP network routing protocol to identify the proper route toward my IP host. In case one PPP link fails, my IP host has always an available link toward the IP network and the IP network routing protocol will reconverge in order to find out another proper route toward my IP host. Do you think this sounds good ? I don't know if there some IETF work on this problem. If it exists, someone can provide me ? Thank in advance. Fabio From owner-ietf-ppp@merit.edu Fri Oct 10 11:30:13 2003 Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03553 for ; Fri, 10 Oct 2003 11:30:12 -0400 (EDT) Received: by trapdoor.merit.edu (Postfix) id 5A7BB913DD; Fri, 10 Oct 2003 11:29:03 -0400 (EDT) Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 3617E913E2; Fri, 10 Oct 2003 11:29:01 -0400 (EDT) Delivered-To: ietf-ppp@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 68A61913CB for ; Fri, 10 Oct 2003 11:26:18 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 5549E5DDAC; Fri, 10 Oct 2003 11:26:18 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34]) by segue.merit.edu (Postfix) with ESMTP id BF7025DE18 for ; Fri, 10 Oct 2003 11:26:17 -0400 (EDT) Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id h9AFQG5u025655; Fri, 10 Oct 2003 09:26:16 -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 h9AFQFQv002827; Fri, 10 Oct 2003 11:26:15 -0400 (EDT) Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.12.9+Sun/8.12.9) with ESMTP id h9AFQ0ZH083778; Fri, 10 Oct 2003 11:26:00 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.12.9+Sun/8.12.9/Submit) id h9AFQ0pD083775; Fri, 10 Oct 2003 11:26:00 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16262.53128.74286.333634@gargle.gargle.HOWL> Date: Fri, 10 Oct 2003 11:26:00 -0400 From: James Carlson To: Fabio Poggi Cc: ietf-ppp@merit.edu Subject: Re: Reliable PPP In-Reply-To: Fabio Poggi's message of 10 October 2003 15:13:56 References: X-Mailer: VM 7.01 under Emacs 21.3.2 Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu Content-Transfer-Encoding: 7bit Fabio Poggi writes: > I need to connect an IP host with a proper static IP address to an IP > network through a TDM network. Not that it matters greatly to me, but this doesn't appear to be the right place to be asking a question like this. The IETF PPP working group deals with extensions to the Point-to-Point Protocol itself, not deployment or usage. > Moreover I need a reliable IP connection between this IP host and the IP > network. Please define what you mean by "reliable." > So, I thought to set up two different PPP session (this would guarantee > physical reliability), over different TDM links, toward the IP network and The first problem is a matter of facilities sharing. I'm going to assume that by "reliable," you mean "survives a fault in at least any one component." In that case, do the TDM links you have in mind share any facilities at the hardware level? How are failures there covered? > to manage these PPP links with an adaptation function in my IP host (in > order to not duplicate IP traffic on IP network). This function will use, > in Tx toward the IP network, the PPP session from which, in Rx, it has > receive PPP traffic. When a fail occurs, the adaptation function switch on > the other PPP session. That can work, though I'd personally recommend either duplication or distribution instead. The problem with stateful mechanisms like this -- switching back and forth between redundant links -- is that they introduce new failure modes (e.g., having each end believe a different link has failed), and those new modes are frequently more likely to occur. In other words, it sometimes makes overall reliability *worse.* For duplication, send the same packet over both links, and have the peer eliminate the duplicates. Note that PPP guarantees in-order delivery, so this should be pretty simple. For distribution, pick some reasonable method (such as a flow-identifying hash) to distribute packets among the available links, so that if a link fails, only a fraction of the connections are affected until the failure has been detected. > Two PPP sessions are monitored by Echo Request/Reply message. I'd suggest looking into LQM (RFC 1989). Echo-Request/Reply works, but it's a bit crude and won't detect service degradation. > The IP network will see my IP host's IP address on two different PPP link > and it will be a task of IP network routing protocol to identify the proper > route toward my IP host. > In case one PPP link fails, my IP host has always an available link toward > the IP network and the IP network routing protocol will reconverge in order > to find out another proper route toward my IP host. That's another way to do it. It isn't necessary to give those links separate IP addresses or expose them to the routing protocol, as long as you have control over the implementations on each end. But it is one way to deal with the issue, and might be advantageous if there are many different routers that have multiple links, and there are systems behind those that can forward through any of those routers. -- 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 From owner-ietf-ppp@merit.edu Wed Oct 15 00:39:19 2003 Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16764 for ; Wed, 15 Oct 2003 00:39:18 -0400 (EDT) Received: by trapdoor.merit.edu (Postfix) id B5F379120D; Wed, 15 Oct 2003 00:39:12 -0400 (EDT) Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 4763191220; Wed, 15 Oct 2003 00:39:11 -0400 (EDT) Delivered-To: ietf-ppp@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 2CFB29120D for ; Wed, 15 Oct 2003 00:39:10 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 13A4A5DE2E; Wed, 15 Oct 2003 00:39:10 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from ohsmtp02.ogw.rr.com (ohsmtp02.ogw.rr.com [65.24.7.37]) by segue.merit.edu (Postfix) with ESMTP id C9DBC5DDEC for ; Wed, 15 Oct 2003 00:39:09 -0400 (EDT) Received: from columbus.rr.com (dhcp93124156.columbus.rr.com [24.93.124.156]) by ohsmtp02.ogw.rr.com (8.12.10/8.12.2) with ESMTP id h9F4d8I5016435; Wed, 15 Oct 2003 00:39:08 -0400 (EDT) Date: Wed, 15 Oct 2003 00:39:08 -0400 Subject: PPP Vendor Protocol to Proposed Standard Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: ietf-ppp@merit.edu, iesg-secretary@ietf.org To: Thomas Narten , Margaret Wasserman From: Karl Fox Content-Transfer-Encoding: 7bit Message-Id: <83B5C8CA-FEC9-11D7-B8B0-000A958718F0@columbus.rr.com> X-Mailer: Apple Mail (2.552) Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu Content-Transfer-Encoding: 7bit Thomas and Margaret, The PPPEXT Working Group recommends that PPP Vendor Protocol, draft-ietf-pppext-vendor-protocol-00.txt, be advanced to Proposed Standard. Note to the IESG Secretary: Please modify the text to incorporate the below assigned numbers. Thanks, Karl -----Original Message----- From: IANA [mailto:iana@iana.org] Sent: Wednesday, August 13, 2003 1:48 PM To: richard.winslow@l-3com.com Subject: RE: Application for PPP Number (005b, 405b, 805b, c05b) Dear Rich, We have assigned the following PPP numbers with you as the point of contact: 005b Vendor-Specific Network Protocol (VSNP) [Winslow] 405b Vendor-Specific Protocol (VSP) [Winslow] 805b Vendor-Specific Network Control Protocol (VSNCP) [Winslow] c05b Vendor-Specific Authentication Protocol (VSAP) [Winslow] [Winslow] Rich Winslow, , August 2003. Please notify the IANA if there is a change in contact information. Thank you, Michelle S. Cotton IANA Administrator *************************************************************** Internet Assigned Numbers Authority (IANA) 4676 Admiralty Way, Suite 330 Marina del Rey, California 90292 Voice: (310) 823-9358 FAX: (310) 823-8649 email: iana@iana.org *************************************************************** From owner-ietf-ppp@merit.edu Wed Oct 15 07:34:40 2003 Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25305 for ; Wed, 15 Oct 2003 07:34:40 -0400 (EDT) Received: by trapdoor.merit.edu (Postfix) id DFFE89123A; Wed, 15 Oct 2003 07:34:21 -0400 (EDT) Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id A9CBE91240; Wed, 15 Oct 2003 07:34:21 -0400 (EDT) Delivered-To: ietf-ppp@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id A18079123A for ; Wed, 15 Oct 2003 07:34:16 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 81D145DDB3; Wed, 15 Oct 2003 07:34:16 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.132]) by segue.merit.edu (Postfix) with ESMTP id DA2B75DD9E for ; Wed, 15 Oct 2003 07:34:15 -0400 (EDT) Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.17.195.10]) by e34.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id h9FBVDbl321924; Wed, 15 Oct 2003 07:31:13 -0400 Received: from cichlid.adsl.duke.edu (sig-9-65-204-233.mts.ibm.com [9.65.204.233]) by westrelay01.boulder.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9FBVCRn122990; Wed, 15 Oct 2003 05:31:12 -0600 Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.9.3) with ESMTP id h9FBUNS07567; Wed, 15 Oct 2003 07:30:35 -0400 Message-Id: <200310151130.h9FBUNS07567@cichlid.adsl.duke.edu> To: Karl Fox Cc: Margaret Wasserman , ietf-ppp@merit.edu Subject: Re: PPP Vendor Protocol to Proposed Standard In-Reply-To: Message from karlfox@columbus.rr.com of "Wed, 15 Oct 2003 00:39:08 EDT." <83B5C8CA-FEC9-11D7-B8B0-000A958718F0@columbus.rr.com> Date: Wed, 15 Oct 2003 07:30:22 -0400 From: Thomas Narten Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu > Note to the IESG Secretary: Please modify the text to incorporate > the below assigned numbers. Note: the secretariate doesn't/won't do this sort of thing (they don't really edit documents). The document authors need to do this. Thomas From owner-ietf-ppp@merit.edu Wed Oct 15 08:08:45 2003 Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26394 for ; Wed, 15 Oct 2003 08:08:44 -0400 (EDT) Received: by trapdoor.merit.edu (Postfix) id E410F91247; Wed, 15 Oct 2003 08:08:35 -0400 (EDT) Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id AFC869124A; Wed, 15 Oct 2003 08:08:35 -0400 (EDT) Delivered-To: ietf-ppp@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id BC01691247 for ; Wed, 15 Oct 2003 08:08:34 -0400 (EDT) Received: by segue.merit.edu (Postfix) id AB3785DDE3; Wed, 15 Oct 2003 08:08:34 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from ohsmtp03.ogw.rr.com (ohsmtp03.ogw.rr.com [65.24.7.38]) by segue.merit.edu (Postfix) with ESMTP id 3B24B5DDD0 for ; Wed, 15 Oct 2003 08:08:34 -0400 (EDT) Received: from columbus.rr.com (dhcp93124156.columbus.rr.com [24.93.124.156]) by ohsmtp03.ogw.rr.com (8.12.10/8.12.2) with ESMTP id h9FC8QCL020156; Wed, 15 Oct 2003 08:08:30 -0400 (EDT) Date: Wed, 15 Oct 2003 08:08:26 -0400 Subject: Re: PPP Vendor Protocol to Proposed Standard Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Karl Fox To: Thomas Narten , Margaret Wasserman , ietf-ppp@merit.edu, iesg-secretary@ietf.org Content-Transfer-Encoding: 7bit In-Reply-To: <83B5C8CA-FEC9-11D7-B8B0-000A958718F0@columbus.rr.com> Message-Id: <47EC40AD-FF08-11D7-B8B0-000A958718F0@columbus.rr.com> X-Mailer: Apple Mail (2.552) Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu Content-Transfer-Encoding: 7bit Please disregard this message. I jumped the gun. Thanks, Karl On Wednesday, October 15, 2003, at 12:39 AM, Karl Fox wrote: > Thomas and Margaret, > > The PPPEXT Working Group recommends that PPP Vendor Protocol, > draft-ietf-pppext-vendor-protocol-00.txt, be advanced to Proposed > Standard. > > Note to the IESG Secretary: Please modify the text to incorporate the > below > assigned numbers. > > Thanks, > > Karl > > -----Original Message----- > From: IANA [mailto:iana@iana.org] > Sent: Wednesday, August 13, 2003 1:48 PM > To: richard.winslow@l-3com.com > Subject: RE: Application for PPP Number (005b, 405b, 805b, c05b) > > > Dear Rich, > > We have assigned the following PPP numbers with > you as the point of contact: > > 005b Vendor-Specific Network Protocol (VSNP) [Winslow] > 405b Vendor-Specific Protocol (VSP) [Winslow] > 805b Vendor-Specific Network Control Protocol (VSNCP) > [Winslow] > c05b Vendor-Specific Authentication Protocol (VSAP) > [Winslow] > > [Winslow] Rich Winslow, , August 2003. > > Please notify the IANA if there is a change in contact > information. > > Thank you, > > Michelle S. Cotton > IANA Administrator > > *************************************************************** > Internet Assigned Numbers Authority (IANA) > 4676 Admiralty Way, Suite 330 > Marina del Rey, California 90292 > > Voice: (310) 823-9358 > FAX: (310) 823-8649 > email: iana@iana.org > *************************************************************** > From owner-ietf-ppp@merit.edu Wed Oct 15 15:34:31 2003 Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18656 for ; Wed, 15 Oct 2003 15:34:31 -0400 (EDT) Received: by trapdoor.merit.edu (Postfix) id 4CEB09126D; Wed, 15 Oct 2003 15:33:53 -0400 (EDT) Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 1482991296; Wed, 15 Oct 2003 15:33:52 -0400 (EDT) Delivered-To: ietf-ppp@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id E43699126D for ; Wed, 15 Oct 2003 15:33:51 -0400 (EDT) Received: by segue.merit.edu (Postfix) id D25805DDBB; Wed, 15 Oct 2003 15:33:51 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from ietf.org (odin.ietf.org [132.151.1.176]) by segue.merit.edu (Postfix) with ESMTP id ACD2D5DDEA for ; Wed, 15 Oct 2003 15:33:45 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18516; Wed, 15 Oct 2003 15:33:33 -0400 (EDT) Message-Id: <200310151933.PAA18516@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-ppp@merit.edu From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-pppext-vendor-protocol-01.txt Date: Wed, 15 Oct 2003 15:33:33 -0400 Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF. Title : PPP Vendor Protocol Author(s) : J. Carlson, R. Winslow Filename : draft-ietf-pppext-vendor-protocol-01.txt Pages : 10 Date : 2003-10-15 The Point-to-Point Protocol (PPP) [1] defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. PPP Vendor Extensions [2] adds vendor- specific general-purpose Configuration Option and Code numbers. This document extends these features to cover vendor-specific Network, Authentication, and Control Protocols. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pppext-vendor-protocol-01.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-pppext-vendor-protocol-01.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-pppext-vendor-protocol-01.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: <2003-10-15142650.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pppext-vendor-protocol-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pppext-vendor-protocol-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-15142650.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-ppp@merit.edu Wed Oct 15 21:37:07 2003 Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02345 for ; Wed, 15 Oct 2003 21:37:07 -0400 (EDT) Received: by trapdoor.merit.edu (Postfix) id 8AAB591213; Wed, 15 Oct 2003 21:36:58 -0400 (EDT) Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 568849121C; Wed, 15 Oct 2003 21:36:58 -0400 (EDT) Delivered-To: ietf-ppp@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 6CC5591213 for ; Wed, 15 Oct 2003 21:36:57 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 57DCC5DE05; Wed, 15 Oct 2003 21:36:57 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from cosmos.ds.org (unknown [199.74.133.199]) by segue.merit.edu (Postfix) with ESMTP id 32B585DE02 for ; Wed, 15 Oct 2003 21:36:57 -0400 (EDT) Received: from columbus.rr.com (dhcp93124156.columbus.rr.com [24.93.124.156]) by cosmos.ds.org (Postfix) with ESMTP id 190FE178D6; Wed, 15 Oct 2003 19:36:56 -0600 (MDT) Date: Wed, 15 Oct 2003 21:36:56 -0400 Subject: PPP Vendor Protocol - Working Group Last Call Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Karl Fox To: ietf-ppp@merit.edu Content-Transfer-Encoding: 7bit Message-Id: <3A2D4725-FF79-11D7-86E5-000A958718F0@columbus.rr.com> X-Mailer: Apple Mail (2.552) Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu Content-Transfer-Encoding: 7bit This is last call. I will advise the area directors that we want to take PPP Vendor Protocol (draft-ietf-pppext-vendor-protocol-01.txt) to Proposed Standard on October 30, 2003 unless there is substantive comment raised on the list.