From owner-msdp@network-services.uoregon.edu Wed Jun 4 02:30:58 2003 Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03486 for ; Wed, 4 Jun 2003 02:30:57 -0400 (EDT) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h545xlsR022465 for ; Tue, 3 Jun 2003 22:59:47 -0700 (PDT) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.8/8.12.8/Submit) id h545xlSk022462 for msdp-outgoing; Tue, 3 Jun 2003 22:59:47 -0700 (PDT) X-Authentication-Warning: network-services.uoregon.edu: majordomo set sender to owner-msdp@network-services.uoregon.edu using -f Received: from mailman.research.att.com (H-135-207-24-32.research.att.com [135.207.24.32]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h545xksR022439 for ; Tue, 3 Jun 2003 22:59:46 -0700 (PDT) Received: from unixmail.research.att.com (unixmail.research.att.com [135.207.26.71]) by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h545sp3j015004 for ; Wed, 4 Jun 2003 01:54:51 -0400 Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by unixmail.research.att.com (8.12.8+Sun/8.8.7) with ESMTP id h545wAXs000031 for ; Wed, 4 Jun 2003 01:58:10 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.11.6+Sun/8.8.5) id h545xab08680; Tue, 3 Jun 2003 22:59:36 -0700 (PDT) Message-Id: <200306040559.h545xab08680@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: msdp@network-services.uoregon.edu Subject: MSDP MIB Date: Tue, 3 Jun 2003 22:59:36 -0700 Versions: dmail (solaris) 2.5a/makemail 2.9d Sender: owner-msdp@network-services.uoregon.edu Precedence: bulk X-Archive: ftp://ns.uoregon.edu/mailing-lists/msdp.archive X-Subscribe: majordomo@ns.uoregon.edu X-Unsubscribe: majordomo@ns.uoregon.edu I just republished the MSDP MIB. Since MSDP is now approved, let's get this finished up to go with it. Here are the open issues from the draft. Some of them are irrelevant now since they applied to pieces that we removed to get to the current version. Comments are welcome. -- We need Components to describe multiple instances of MSDP in the same box (similar to the PIM MIB) Need a static RPF-peer table (see spec, section 14.3) Do we need an msdpPeerLastErrorSent, too, for what notification I last sent to this peer? The Backwards Transition notification won't trigger on established -> disabled. Is that desired? A table to express policy was suggested on the MSDP mailing list. More discussion is required before including this in the MIB. (Some of the more discussion: other than filtering announcements at an RP, policy in MSDP == black holes; policy should be in MBGP) An OID for control of encapsulation (e.g. SA-encapsulate the first N packets sent to this group?) was suggested, although it might be more appropriate to be a table for fine-grained control. Is the RowStatus object in the SACache appropriate? (e.g. used to flush potentially bad state) Should there be a mechanism to describe alternate methods of RPF? (e.g. statically configured peer address and RP address lists - could be a table indexed by peer address and RP address with a value of accept/deny) One or more MSDP default-peers? Is it appropriate to use names to distinguish mesh groups? Are there any other variables appropriate for configuring/managing mesh groups? Should the UDP port used for encapsulation be in the Peer table? ----- Begin forwarded message: From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-msdp-mib-07.txt Date: Fri, 30 May 2003 07:15:24 -0400 To: IETF-Announce: ; Cc: msdp@antc.uoregon.edu Reply-to: Internet-Drafts@ietf.org Title : Multicast Source Discovery protocol MIB Author(s) : B. Fenner, D. Thaler Filename : draft-ietf-msdp-mib-07.txt Pages : 32 Date : 2003-5-29 This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Multicast Source Discovery Protocol (MSDP) [2] speakers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-msdp-mib-07.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-msdp-mib-07.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-msdp-mib-07.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. [Don't know how to fetch mail-server a3] ----- End forwarded message: From owner-msdp@network-services.uoregon.edu Wed Jun 4 02:38:10 2003 Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05395 for ; Wed, 4 Jun 2003 02:38:09 -0400 (EDT) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h545xlsR022465 for ; Tue, 3 Jun 2003 22:59:47 -0700 (PDT) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.8/8.12.8/Submit) id h545xlSk022462 for msdp-outgoing; Tue, 3 Jun 2003 22:59:47 -0700 (PDT) X-Authentication-Warning: network-services.uoregon.edu: majordomo set sender to owner-msdp@network-services.uoregon.edu using -f Received: from mailman.research.att.com (H-135-207-24-32.research.att.com [135.207.24.32]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h545xksR022439 for ; Tue, 3 Jun 2003 22:59:46 -0700 (PDT) Received: from unixmail.research.att.com (unixmail.research.att.com [135.207.26.71]) by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h545sp3j015004 for ; Wed, 4 Jun 2003 01:54:51 -0400 Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by unixmail.research.att.com (8.12.8+Sun/8.8.7) with ESMTP id h545wAXs000031 for ; Wed, 4 Jun 2003 01:58:10 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.11.6+Sun/8.8.5) id h545xab08680; Tue, 3 Jun 2003 22:59:36 -0700 (PDT) Message-Id: <200306040559.h545xab08680@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: msdp@network-services.uoregon.edu Subject: MSDP MIB Date: Tue, 3 Jun 2003 22:59:36 -0700 Versions: dmail (solaris) 2.5a/makemail 2.9d Sender: owner-msdp@network-services.uoregon.edu Precedence: bulk X-Archive: ftp://ns.uoregon.edu/mailing-lists/msdp.archive X-Subscribe: majordomo@ns.uoregon.edu X-Unsubscribe: majordomo@ns.uoregon.edu I just republished the MSDP MIB. Since MSDP is now approved, let's get this finished up to go with it. Here are the open issues from the draft. Some of them are irrelevant now since they applied to pieces that we removed to get to the current version. Comments are welcome. -- We need Components to describe multiple instances of MSDP in the same box (similar to the PIM MIB) Need a static RPF-peer table (see spec, section 14.3) Do we need an msdpPeerLastErrorSent, too, for what notification I last sent to this peer? The Backwards Transition notification won't trigger on established -> disabled. Is that desired? A table to express policy was suggested on the MSDP mailing list. More discussion is required before including this in the MIB. (Some of the more discussion: other than filtering announcements at an RP, policy in MSDP == black holes; policy should be in MBGP) An OID for control of encapsulation (e.g. SA-encapsulate the first N packets sent to this group?) was suggested, although it might be more appropriate to be a table for fine-grained control. Is the RowStatus object in the SACache appropriate? (e.g. used to flush potentially bad state) Should there be a mechanism to describe alternate methods of RPF? (e.g. statically configured peer address and RP address lists - could be a table indexed by peer address and RP address with a value of accept/deny) One or more MSDP default-peers? Is it appropriate to use names to distinguish mesh groups? Are there any other variables appropriate for configuring/managing mesh groups? Should the UDP port used for encapsulation be in the Peer table? ----- Begin forwarded message: From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-msdp-mib-07.txt Date: Fri, 30 May 2003 07:15:24 -0400 To: IETF-Announce: ; Cc: msdp@antc.uoregon.edu Reply-to: Internet-Drafts@ietf.org Title : Multicast Source Discovery protocol MIB Author(s) : B. Fenner, D. Thaler Filename : draft-ietf-msdp-mib-07.txt Pages : 32 Date : 2003-5-29 This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Multicast Source Discovery Protocol (MSDP) [2] speakers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-msdp-mib-07.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-msdp-mib-07.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-msdp-mib-07.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. [Don't know how to fetch mail-server a3] ----- End forwarded message: From owner-msdp@network-services.uoregon.edu Tue Jun 10 22:30:29 2003 Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26971 for ; Tue, 10 Jun 2003 22:30:28 -0400 (EDT) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5B2IisR024190 for ; Tue, 10 Jun 2003 19:18:44 -0700 (PDT) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.8/8.12.8/Submit) id h5B2IiAf024189 for msdp-outgoing; Tue, 10 Jun 2003 19:18:44 -0700 (PDT) X-Authentication-Warning: network-services.uoregon.edu: majordomo set sender to owner-msdp@network-services.uoregon.edu using -f Received: from linux.research.att.com (H-135-207-24-16.research.att.com [135.207.24.16]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5B2IhsR024178; Tue, 10 Jun 2003 19:18:43 -0700 (PDT) Received: from unixmail.research.att.com (unixmail.research.att.com [135.207.26.71]) by linux.research.att.com (8.12.8/8.12.8) with ESMTP id h5B2NvEI028297; Tue, 10 Jun 2003 22:23:57 -0400 Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by unixmail.research.att.com (8.12.8+Sun/8.8.7) with ESMTP id h5B2H1Xs029769; Tue, 10 Jun 2003 22:17:02 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.11.6+Sun/8.8.5) id h5B2IXR13705; Tue, 10 Jun 2003 19:18:33 -0700 (PDT) Message-Id: <200306110218.h5B2IXR13705@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu Subject: MSDP MIB questions Date: Tue, 10 Jun 2003 19:18:33 -0700 Versions: dmail (solaris) 2.5a/makemail 2.9d Sender: owner-msdp@network-services.uoregon.edu Precedence: bulk X-Archive: ftp://ns.uoregon.edu/mailing-lists/msdp.archive X-Subscribe: majordomo@ns.uoregon.edu X-Unsubscribe: majordomo@ns.uoregon.edu A couple of brief MSDP MIB questions: 1. Has anyone implemented the draft -06 or -07 (or, for that matter, any version)? I'm curious if renumbering the OIDs would affect anyone. 2. In the Requests table, does it make sense for longest-match to happen first, or highest priority first? 3. I'm planning to delete msdpPeerEncapsulationType, msdpPeerInNotifications, msdpPeerOutNotifications, msdpPeerLastError to reflect evolution of the MSDP spec. Can anyone think of any other changes relevant to the structure of the MIB? Thanks, Bill From owner-msdp@network-services.uoregon.edu Tue Jun 10 22:33:29 2003 Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27035 for ; Tue, 10 Jun 2003 22:33:29 -0400 (EDT) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5B2IisR024190 for ; Tue, 10 Jun 2003 19:18:44 -0700 (PDT) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.8/8.12.8/Submit) id h5B2IiAf024189 for msdp-outgoing; Tue, 10 Jun 2003 19:18:44 -0700 (PDT) X-Authentication-Warning: network-services.uoregon.edu: majordomo set sender to owner-msdp@network-services.uoregon.edu using -f Received: from linux.research.att.com (H-135-207-24-16.research.att.com [135.207.24.16]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5B2IhsR024178; Tue, 10 Jun 2003 19:18:43 -0700 (PDT) Received: from unixmail.research.att.com (unixmail.research.att.com [135.207.26.71]) by linux.research.att.com (8.12.8/8.12.8) with ESMTP id h5B2NvEI028297; Tue, 10 Jun 2003 22:23:57 -0400 Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by unixmail.research.att.com (8.12.8+Sun/8.8.7) with ESMTP id h5B2H1Xs029769; Tue, 10 Jun 2003 22:17:02 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.11.6+Sun/8.8.5) id h5B2IXR13705; Tue, 10 Jun 2003 19:18:33 -0700 (PDT) Message-Id: <200306110218.h5B2IXR13705@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu Subject: MSDP MIB questions Date: Tue, 10 Jun 2003 19:18:33 -0700 Versions: dmail (solaris) 2.5a/makemail 2.9d Sender: owner-msdp@network-services.uoregon.edu Precedence: bulk X-Archive: ftp://ns.uoregon.edu/mailing-lists/msdp.archive X-Subscribe: majordomo@ns.uoregon.edu X-Unsubscribe: majordomo@ns.uoregon.edu A couple of brief MSDP MIB questions: 1. Has anyone implemented the draft -06 or -07 (or, for that matter, any version)? I'm curious if renumbering the OIDs would affect anyone. 2. In the Requests table, does it make sense for longest-match to happen first, or highest priority first? 3. I'm planning to delete msdpPeerEncapsulationType, msdpPeerInNotifications, msdpPeerOutNotifications, msdpPeerLastError to reflect evolution of the MSDP spec. Can anyone think of any other changes relevant to the structure of the MIB? Thanks, Bill From owner-msdp@network-services.uoregon.edu Wed Jun 11 00:58:48 2003 Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29181 for ; Wed, 11 Jun 2003 00:58:48 -0400 (EDT) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5B4nLsR000509 for ; Tue, 10 Jun 2003 21:49:21 -0700 (PDT) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.8/8.12.8/Submit) id h5B4nLEc000508 for msdp-outgoing; Tue, 10 Jun 2003 21:49:21 -0700 (PDT) X-Authentication-Warning: network-services.uoregon.edu: majordomo set sender to owner-msdp@network-services.uoregon.edu using -f Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5B4nKsR000503; Tue, 10 Jun 2003 21:49:20 -0700 (PDT) Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h5B4nDI2013841; Tue, 10 Jun 2003 21:49:13 -0700 (PDT) Received: (from kessler@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id VAA11042; Tue, 10 Jun 2003 21:49:13 -0700 (PDT) From: Andrew Kessler Message-Id: <200306110449.VAA11042@cisco.com> Subject: Re: MSDP MIB questions To: fenner@research.att.com (Bill Fenner) Date: Tue, 10 Jun 2003 21:49:12 -0700 (PDT) Cc: msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu In-Reply-To: <200306110218.h5B2IXR13705@windsor.research.att.com> from "Bill Fenner" at Jun 10, 2003 07:18:33 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-msdp@network-services.uoregon.edu Precedence: bulk X-Archive: ftp://ns.uoregon.edu/mailing-lists/msdp.archive X-Subscribe: majordomo@ns.uoregon.edu X-Unsubscribe: majordomo@ns.uoregon.edu Content-Transfer-Encoding: 7bit I made up this Cisco multicast network management support matrix awhile ago: http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/mcst_sol/mibs.htm It was correct a year ago. Andy From: Bill Fenner A couple of brief MSDP MIB questions: 1. Has anyone implemented the draft -06 or -07 (or, for that matter, any version)? I'm curious if renumbering the OIDs would affect anyone. 2. In the Requests table, does it make sense for longest-match to happen first, or highest priority first? 3. I'm planning to delete msdpPeerEncapsulationType, msdpPeerInNotifications, msdpPeerOutNotifications, msdpPeerLastError to reflect evolution of the MSDP spec. Can anyone think of any other changes relevant to the structure of the MIB? Thanks, Bill From owner-msdp@network-services.uoregon.edu Wed Jun 11 01:01:47 2003 Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29235 for ; Wed, 11 Jun 2003 01:01:46 -0400 (EDT) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5B4nLsR000509 for ; Tue, 10 Jun 2003 21:49:21 -0700 (PDT) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.8/8.12.8/Submit) id h5B4nLEc000508 for msdp-outgoing; Tue, 10 Jun 2003 21:49:21 -0700 (PDT) X-Authentication-Warning: network-services.uoregon.edu: majordomo set sender to owner-msdp@network-services.uoregon.edu using -f Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5B4nKsR000503; Tue, 10 Jun 2003 21:49:20 -0700 (PDT) Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h5B4nDI2013841; Tue, 10 Jun 2003 21:49:13 -0700 (PDT) Received: (from kessler@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id VAA11042; Tue, 10 Jun 2003 21:49:13 -0700 (PDT) From: Andrew Kessler Message-Id: <200306110449.VAA11042@cisco.com> Subject: Re: MSDP MIB questions To: fenner@research.att.com (Bill Fenner) Date: Tue, 10 Jun 2003 21:49:12 -0700 (PDT) Cc: msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu In-Reply-To: <200306110218.h5B2IXR13705@windsor.research.att.com> from "Bill Fenner" at Jun 10, 2003 07:18:33 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-msdp@network-services.uoregon.edu Precedence: bulk X-Archive: ftp://ns.uoregon.edu/mailing-lists/msdp.archive X-Subscribe: majordomo@ns.uoregon.edu X-Unsubscribe: majordomo@ns.uoregon.edu Content-Transfer-Encoding: 7bit I made up this Cisco multicast network management support matrix awhile ago: http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/mcst_sol/mibs.htm It was correct a year ago. Andy From: Bill Fenner A couple of brief MSDP MIB questions: 1. Has anyone implemented the draft -06 or -07 (or, for that matter, any version)? I'm curious if renumbering the OIDs would affect anyone. 2. In the Requests table, does it make sense for longest-match to happen first, or highest priority first? 3. I'm planning to delete msdpPeerEncapsulationType, msdpPeerInNotifications, msdpPeerOutNotifications, msdpPeerLastError to reflect evolution of the MSDP spec. Can anyone think of any other changes relevant to the structure of the MIB? Thanks, Bill From owner-msdp@network-services.uoregon.edu Tue Jun 24 12:15:30 2003 Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22185 for ; Tue, 24 Jun 2003 12:15:29 -0400 (EDT) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5OG2osR013074 for ; Tue, 24 Jun 2003 09:02:50 -0700 (PDT) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.8/8.12.8/Submit) id h5OG2o2T013073 for msdp-outgoing; Tue, 24 Jun 2003 09:02:50 -0700 (PDT) X-Authentication-Warning: network-services.uoregon.edu: majordomo set sender to owner-msdp@network-services.uoregon.edu using -f Received: from sith.maoz.com (sith.maoz.com [205.167.76.10]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5OG2nsR013067; Tue, 24 Jun 2003 09:02:49 -0700 (PDT) Received: (from dmm@localhost) by sith.maoz.com (8.12.9/8.12.9) id h5OG2SqV022561; Tue, 24 Jun 2003 09:02:28 -0700 Date: Tue, 24 Jun 2003 09:02:28 -0700 From: David Meyer To: mboned@network-services.uoregon.edu Cc: msdp@network-services.uoregon.edu, agenda@ietf.org Subject: [MBONED] Draft Agenda for 57 IETF Message-ID: <20030624090228.A22510@1-4-5.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-public-key: http://www.maoz.com/~dmm/public-key.asc X-philosophy: "I just had to let it go" -- John Lennon Sender: owner-msdp@network-services.uoregon.edu Precedence: bulk X-Archive: ftp://ns.uoregon.edu/mailing-lists/msdp.archive X-Subscribe: majordomo@ns.uoregon.edu X-Unsubscribe: majordomo@ns.uoregon.edu Please forward questions, comments, or additional agenda items to me. Thanks, Dave ----- MBONE Deployment WG (MBONED) ============================ Tuesday, July 15, 2003 (0900-1130 Morning Sessions) Draft Agenda ------------ Agenda Bashing 5 minutes Meyer/All Embedding the Address of RP in IPv6 Multicast Address 20 minutes draft-savola-mboned-mcast-rpaddr-03.txt Pekka Savola Multicast Source Discovery Protocol Deployment Scenarios 20 minutes draft-ietf-mboned-msdp-deploy-02.txt Mike McBride MSDP Spec Update draft-ietf-msdp-spec-20.txt 10 minutes Mike McBride MSDP MIB Issues draft-ietf-msdp-mib-07.txt 10 minutes Meyer (Bill Fenner, Dave Thaler) MCOP Issues 15 minutes draft-lehtonen-magma-mcop-03.txt draft-lehtonen-mboned-mcop-operation-00.txt draft-vatiainen-mcop-cops-ps-00.txt Rami Lehtonen Framework for Deploying IP Multicast in IPv6 30 minutes draft-giuliano-mboned-v6mcast-framework-00.txt Lenny Giuliano IPv6 Multicast Addressing -- IANA Considerations 10 minutes Meyer/All From owner-msdp@network-services.uoregon.edu Tue Jun 24 12:19:28 2003 Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22388 for ; Tue, 24 Jun 2003 12:19:27 -0400 (EDT) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5OG2osR013074 for ; Tue, 24 Jun 2003 09:02:50 -0700 (PDT) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.8/8.12.8/Submit) id h5OG2o2T013073 for msdp-outgoing; Tue, 24 Jun 2003 09:02:50 -0700 (PDT) X-Authentication-Warning: network-services.uoregon.edu: majordomo set sender to owner-msdp@network-services.uoregon.edu using -f Received: from sith.maoz.com (sith.maoz.com [205.167.76.10]) by network-services.uoregon.edu (8.12.8/8.12.2) with ESMTP id h5OG2nsR013067; Tue, 24 Jun 2003 09:02:49 -0700 (PDT) Received: (from dmm@localhost) by sith.maoz.com (8.12.9/8.12.9) id h5OG2SqV022561; Tue, 24 Jun 2003 09:02:28 -0700 Date: Tue, 24 Jun 2003 09:02:28 -0700 From: David Meyer To: mboned@network-services.uoregon.edu Cc: msdp@network-services.uoregon.edu, agenda@ietf.org Subject: [MBONED] Draft Agenda for 57 IETF Message-ID: <20030624090228.A22510@1-4-5.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-public-key: http://www.maoz.com/~dmm/public-key.asc X-philosophy: "I just had to let it go" -- John Lennon Sender: owner-msdp@network-services.uoregon.edu Precedence: bulk X-Archive: ftp://ns.uoregon.edu/mailing-lists/msdp.archive X-Subscribe: majordomo@ns.uoregon.edu X-Unsubscribe: majordomo@ns.uoregon.edu Please forward questions, comments, or additional agenda items to me. Thanks, Dave ----- MBONE Deployment WG (MBONED) ============================ Tuesday, July 15, 2003 (0900-1130 Morning Sessions) Draft Agenda ------------ Agenda Bashing 5 minutes Meyer/All Embedding the Address of RP in IPv6 Multicast Address 20 minutes draft-savola-mboned-mcast-rpaddr-03.txt Pekka Savola Multicast Source Discovery Protocol Deployment Scenarios 20 minutes draft-ietf-mboned-msdp-deploy-02.txt Mike McBride MSDP Spec Update draft-ietf-msdp-spec-20.txt 10 minutes Mike McBride MSDP MIB Issues draft-ietf-msdp-mib-07.txt 10 minutes Meyer (Bill Fenner, Dave Thaler) MCOP Issues 15 minutes draft-lehtonen-magma-mcop-03.txt draft-lehtonen-mboned-mcop-operation-00.txt draft-vatiainen-mcop-cops-ps-00.txt Rami Lehtonen Framework for Deploying IP Multicast in IPv6 30 minutes draft-giuliano-mboned-v6mcast-framework-00.txt Lenny Giuliano IPv6 Multicast Addressing -- IANA Considerations 10 minutes Meyer/All