From owner-if-mib@padauk.vnd.tek.com Fri Sep 10 04:31:23 1999 Received: from fw1.tek.com (fw1.tek.com [192.65.17.16]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26283 for ; Fri, 10 Sep 1999 04:31:23 -0400 (EDT) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id BAA26663 for ; Fri, 10 Sep 1999 01:31:24 -0700 (PDT) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.192.78]) by fw1.tek.com with ESMTP id BAA26657 for ; Fri, 10 Sep 1999 01:31:23 -0700 (PDT) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id BAA12834 for if-mib-outgoing; Fri, 10 Sep 1999 01:27:56 -0700 (PDT) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Message-ID: <015d01befb66$0ddee520$0201a8c0@nec.oleane.com> From: "Peter lewis" To: Subject: QoS Summit Date: Fri, 10 Sep 1999 10:25:32 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-if-mib@vnd.tek.com Precedence: bulk Content-Transfer-Encoding: 7bit QoS Summit: key requirements for advanced applications running on future networks. Technologies (MPLS, ATM, IntSev/DiffServ, Frame Relay). Managing, policing, billing, charging QoS. The annual rendez-vous with top senior specialists. Paris, France, 16-19 November 1999 Please see details at the following web address: http://www.upperside.fr/baqos.htm Sorry to post this message on the list. Thanks From chantall@upperside.fr Mon Sep 13 07:09:17 1999 Received: from s2.smtp.oleane.net (s2.smtp.oleane.net [195.25.12.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20466; Mon, 13 Sep 1999 07:09:15 -0400 (EDT) Received: from Dell (dyn-1-1-203.Cor.dialup.oleane.fr [62.161.8.203]) by s2.smtp.oleane.net with SMTP id MAA06211; Mon, 13 Sep 1999 12:59:42 +0200 (CEST) Message-ID: <000e01befdd7$61936c40$0701a8c0@oleane.com> From: "Chantal Ladouce" To: "chantal" Subject: From Firewall to IPSec VPNs Date: Mon, 13 Sep 1999 13:00:07 +0200 Organization: upperside MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01BEFDE7.E7B19440" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 This is a multi-part message in MIME format. ------=_NextPart_000_000B_01BEFDE7.E7B19440 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Security services and protection mechanisms IPv6 promises regarding IPSec Certification infrastructure Standardization update Case Studies: ISPs, carriers, private networks AH and ESP protocols description Possible future extensions and modifications of the IKE protocol Complementarity between IPSec and firewalls Global Site-to-Site IPSec VPN's with End-to-End SLA's Managing widespread IPSEC virtual private networks Solving IPSec VPNs scalability Results of some interoperability tests IPSec architectures and non-standardized aspects of IPSec Adding IPSec VPN functions in an existing router network Impact of fragmentation on the performance of IPSec coding IPSEC 99 Conference From Firewall to IPSec VPNs October 26, 27, 28, 29, 1999 Paris - France More infos: www.upperside.fr/baipsec.htm ------=_NextPart_000_000B_01BEFDE7.E7B19440 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Security services and protection mechanisms
IPv6 = promises=20 regarding IPSec
Certification infrastructure
Standardization=20 update
Case Studies: ISPs, carriers, private networks
AH and ESP = protocols=20 description
Possible future extensions and modifications of the IKE=20 protocol
Complementarity between IPSec and firewalls
Global = Site-to-Site=20 IPSec VPN's with End-to-End SLA's
Managing widespread IPSEC virtual = private=20 networks
Solving IPSec VPNs scalability
Results of some = interoperability=20 tests
IPSec architectures and non-standardized aspects of = IPSec
Adding=20 IPSec VPN functions in an existing router network
Impact of = fragmentation on=20 the performance of IPSec coding

IPSEC 99 Conference
From = Firewall to=20 IPSec VPNs

October 26, 27, 28, 29, 1999
Paris - = France

More=20 infos: www.upperside.fr/baipsec.htm=

------=_NextPart_000_000B_01BEFDE7.E7B19440-- From owner-if-mib@padauk.vnd.tek.com Thu Sep 16 15:05:14 1999 Received: from fw1.tek.com (fw1.tek.com [192.65.17.16]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25074 for ; Thu, 16 Sep 1999 15:05:14 -0400 (EDT) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id MAA01562 for ; Thu, 16 Sep 1999 12:05:12 -0700 (PDT) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.192.78]) by fw1.tek.com with ESMTP id MAA01556 for ; Thu, 16 Sep 1999 12:05:12 -0700 (PDT) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id MAA00243 for if-mib-outgoing; Thu, 16 Sep 1999 12:00:24 -0700 (PDT) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Message-Id: <199909161900.MAA29536@cocobolo.vnd.tek.com> To: if-mib@vnd.tek.com Cc: ted.brunner@tek.com Subject: advancing the if-mib From: Ted Brunner Reply-to: ted.brunner@tek.com Date: Thu, 16 Sep 1999 12:00:21 -0700 Sender: owner-if-mib@vnd.tek.com Precedence: bulk We are on our way to advancing the interface mib to standard. There are still a few details to work through, but At this point I would like to start the process of collecting implementation experience with the interface mib, and with the inverse stack mib. So as a background process to everything else, would someone from every vendor please send me an implementation report explaining -what they implemented, what they did not. -differences between whats implemented and the definitions. -please include experience with 64bit counters. -please include experience with counter roll-overs. -and anything else you think is interesting. Would you please send it to me. Send it to the list also, unless you would prefer not. Let me know if any part of the report should be keep confidential and reported as anonymous. I would rather have as much info as possible directly associated with a vendor. Thank you for your help. I will be gone on a trip and out of email for the next week, when I return I will get in touch with respondents. Ted Brunner VideoTele.com Tektronix MS 50-475 ted.brunner@tek.com 14150 SW Karl Braun 503.627.1317 Beaverton OR 97005 From owner-if-mib@padauk.vnd.tek.com Fri Sep 17 07:56:24 1999 Received: from fw1.tek.com (fw1.tek.com [192.65.17.16]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02492 for ; Fri, 17 Sep 1999 07:56:23 -0400 (EDT) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id EAA19278 for ; Fri, 17 Sep 1999 04:56:08 -0700 (PDT) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.192.78]) by fw1.tek.com with ESMTP id EAA19271 for ; Fri, 17 Sep 1999 04:56:07 -0700 (PDT) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id EAA11165 for if-mib-outgoing; Fri, 17 Sep 1999 04:52:24 -0700 (PDT) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Message-Id: <199909171148.HAA04085@hygro.adsl.duke.edu> To: ted.brunner@tek.com cc: if-mib@vnd.tek.com Subject: Re: advancing the if-mib In-Reply-To: Message from Ted Brunner of "Thu, 16 Sep 1999 12:00:21 PDT." <199909161900.MAA29536@cocobolo.vnd.tek.com> Date: Fri, 17 Sep 1999 07:48:27 -0400 From: Thomas Narten Sender: owner-if-mib@vnd.tek.com Precedence: bulk > Would you please send it to me. Send it to the > list also, unless you would prefer not. Let me know > if any part of the report should be keep confidential > and reported as anonymous. I would rather have as > much info as possible directly associated with a vendor. While it might be useful for background and planning purposes to know of what sort of stuff vendors are working on, but don't want to make public, note that the interoperability report that the IESG requires for document advancement needs to name names. Anonymous entries can't count because folks can't challenge them publically, or even evaluate their correctness. Thomas From owner-if-mib@padauk.vnd.tek.com Tue Sep 28 17:26:07 1999 Received: from fw1.tek.com ([192.65.17.16]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03088 for ; Tue, 28 Sep 1999 17:26:06 -0400 (EDT) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id OAB15784 for ; Tue, 28 Sep 1999 14:25:37 -0700 (PDT) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.192.78]) by fw1.tek.com with ESMTP id OAA15774 for ; Tue, 28 Sep 1999 14:25:37 -0700 (PDT) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id OAA09186 for if-mib-outgoing; Tue, 28 Sep 1999 14:21:39 -0700 (PDT) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Message-Id: <199909282121.OAA18721@cocobolo.vnd.tek.com> To: if-mib@vnd.tek.com Cc: ted.brunner@tek.com Subject: implementation reports needed From: Ted Brunner Reply-to: ted.brunner@tek.com Date: Tue, 28 Sep 1999 14:21:36 -0700 Sender: owner-if-mib@vnd.tek.com Precedence: bulk To progress the if-mib (draft-ietf-ifmib-ifmib2-00.txt) and the associated inverse stack mib (draft-ietf-ifmib-invstackmib-01.txt) we need to generate an implementation report. I sent out a mass request two weeks ago, but not many of you responded. I will put the summary together, but I need a report from each vendor detailing how they have implemented the if-mib. Be sure to include details on (among other things) -Counter64 -ifCounterDiscontinuityTime Please send me something, this week if possible. Ted Brunner VideoTele.com Tektronix MS 50-475 ted.brunner@tek.com 14150 SW Karl Braun 503.627.1317 Beaverton OR 97005