From owner-msdp@network-services.uoregon.edu Mon Nov 18 17:02:52 2002 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 RAA05314 for ; Mon, 18 Nov 2002 17:02:52 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAILq8bt019709 for ; Mon, 18 Nov 2002 13:52:08 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gAILq8q0019708 for msdp-outgoing; Mon, 18 Nov 2002 13:52:08 -0800 (PST) Received: from sith.maoz.com (sith.maoz.com [205.167.76.10]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAILq6bt019699; Mon, 18 Nov 2002 13:52:06 -0800 (PST) Received: (from dmm@localhost) by sith.maoz.com (8.12.6/8.12.6) id gAILqwXE002095; Mon, 18 Nov 2002 13:52:58 -0800 Date: Mon, 18 Nov 2002 13:52:58 -0800 From: David Meyer To: msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu Subject: Re: MSDP spec 14 Message-ID: <20021118135258.A2084@sprint.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from mmcbride@cisco.com on Mon, Nov 18, 2002 at 01:50:39PM -0800 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 >> As discussed today in mboned wg: >> >> http://www.ietf.org/internet-drafts/draft-ietf-msdp-spec-14.txt >> Folks, this is the official start of the WG Last call on this document. Comments to the list. Thanks, Dave From owner-msdp@network-services.uoregon.edu Mon Nov 18 17:06:35 2002 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 RAA05420 for ; Mon, 18 Nov 2002 17:06:35 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAILq8bt019709 for ; Mon, 18 Nov 2002 13:52:08 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gAILq8q0019708 for msdp-outgoing; Mon, 18 Nov 2002 13:52:08 -0800 (PST) Received: from sith.maoz.com (sith.maoz.com [205.167.76.10]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAILq6bt019699; Mon, 18 Nov 2002 13:52:06 -0800 (PST) Received: (from dmm@localhost) by sith.maoz.com (8.12.6/8.12.6) id gAILqwXE002095; Mon, 18 Nov 2002 13:52:58 -0800 Date: Mon, 18 Nov 2002 13:52:58 -0800 From: David Meyer To: msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu Subject: Re: MSDP spec 14 Message-ID: <20021118135258.A2084@sprint.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from mmcbride@cisco.com on Mon, Nov 18, 2002 at 01:50:39PM -0800 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 >> As discussed today in mboned wg: >> >> http://www.ietf.org/internet-drafts/draft-ietf-msdp-spec-14.txt >> Folks, this is the official start of the WG Last call on this document. Comments to the list. Thanks, Dave From owner-msdp@network-services.uoregon.edu Tue Nov 19 09:39:56 2002 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 JAA06431 for ; Tue, 19 Nov 2002 09:39:56 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAJEUrbt000951 for ; Tue, 19 Nov 2002 06:30:53 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gAJEUrjv000950 for msdp-outgoing; Tue, 19 Nov 2002 06:30:53 -0800 (PST) Received: from sith.maoz.com (sith.maoz.com [205.167.76.10]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAJEUpbt000937; Tue, 19 Nov 2002 06:30:51 -0800 (PST) Received: (from dmm@localhost) by sith.maoz.com (8.12.6/8.12.6) id gAJEVhiu014515; Tue, 19 Nov 2002 06:31:43 -0800 Date: Tue, 19 Nov 2002 06:31:43 -0800 From: David Meyer To: msdp@network-services.uoregon.edu Cc: mboned@network-services.uoregon.edu Subject: Regarding WG last call for the MSDP spec (WG last call timeout) Message-ID: <20021119063143.A14496@sprint.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i 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 Just to be clear, the WG last call times out on 12/02/2002. Please send comments to the list. Thanks, Dave From owner-msdp@network-services.uoregon.edu Tue Nov 19 09:43:52 2002 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 JAA06480 for ; Tue, 19 Nov 2002 09:43:51 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAJEUrbt000951 for ; Tue, 19 Nov 2002 06:30:53 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gAJEUrjv000950 for msdp-outgoing; Tue, 19 Nov 2002 06:30:53 -0800 (PST) Received: from sith.maoz.com (sith.maoz.com [205.167.76.10]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAJEUpbt000937; Tue, 19 Nov 2002 06:30:51 -0800 (PST) Received: (from dmm@localhost) by sith.maoz.com (8.12.6/8.12.6) id gAJEVhiu014515; Tue, 19 Nov 2002 06:31:43 -0800 Date: Tue, 19 Nov 2002 06:31:43 -0800 From: David Meyer To: msdp@network-services.uoregon.edu Cc: mboned@network-services.uoregon.edu Subject: Regarding WG last call for the MSDP spec (WG last call timeout) Message-ID: <20021119063143.A14496@sprint.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i 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 Just to be clear, the WG last call times out on 12/02/2002. Please send comments to the list. Thanks, Dave From owner-msdp@network-services.uoregon.edu Wed Nov 20 06:49:46 2002 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 GAA16783 for ; Wed, 20 Nov 2002 06:49:45 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAKBaJbt027413 for ; Wed, 20 Nov 2002 03:36:19 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gAKBaJVQ027412 for msdp-outgoing; Wed, 20 Nov 2002 03:36:19 -0800 (PST) Received: from mta0 ([61.144.161.10]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAKBaFbt027346; Wed, 20 Nov 2002 03:36:16 -0800 (PST) Received: from g24332 (mta0 [172.17.1.62]) by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12 2002)) with ESMTPA id <0H5V00CXBHGTCN@mta0.huawei.com>; Wed, 20 Nov 2002 19:34:06 +0800 (CST) Date: Wed, 20 Nov 2002 19:37:53 +0800 From: Guo Feng Subject: Re: MSDP spec 14 To: David Meyer Cc: msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu Reply-to: Guo Feng Message-id: <002e01c29089$4381e220$86326e0a@HUAWEI.COM> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20021118135258.A2084@sprint.net> 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 Two questions: 1.Why is the notification TLV removed ? 2.There are no description about Request and Response TLV Function , will those two TLVs be obsolete ? Thanks, Feng ----- Original Message ----- From: "David Meyer" To: ; Sent: Tuesday, November 19, 2002 5:52 AM Subject: Re: MSDP spec 14 > >> As discussed today in mboned wg: > >> > >> http://www.ietf.org/internet-drafts/draft-ietf-msdp-spec-14.txt > >> > > Folks, this is the official start of the WG Last call on this > document. Comments to the list. > > Thanks, > > Dave > > From owner-msdp@network-services.uoregon.edu Wed Nov 20 06:55:46 2002 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 GAA16880 for ; Wed, 20 Nov 2002 06:55:46 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAKBaJbt027413 for ; Wed, 20 Nov 2002 03:36:19 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gAKBaJVQ027412 for msdp-outgoing; Wed, 20 Nov 2002 03:36:19 -0800 (PST) Received: from mta0 ([61.144.161.10]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAKBaFbt027346; Wed, 20 Nov 2002 03:36:16 -0800 (PST) Received: from g24332 (mta0 [172.17.1.62]) by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12 2002)) with ESMTPA id <0H5V00CXBHGTCN@mta0.huawei.com>; Wed, 20 Nov 2002 19:34:06 +0800 (CST) Date: Wed, 20 Nov 2002 19:37:53 +0800 From: Guo Feng Subject: Re: MSDP spec 14 To: David Meyer Cc: msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu Reply-to: Guo Feng Message-id: <002e01c29089$4381e220$86326e0a@HUAWEI.COM> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20021118135258.A2084@sprint.net> 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 Two questions: 1.Why is the notification TLV removed ? 2.There are no description about Request and Response TLV Function , will those two TLVs be obsolete ? Thanks, Feng ----- Original Message ----- From: "David Meyer" To: ; Sent: Tuesday, November 19, 2002 5:52 AM Subject: Re: MSDP spec 14 > >> As discussed today in mboned wg: > >> > >> http://www.ietf.org/internet-drafts/draft-ietf-msdp-spec-14.txt > >> > > Folks, this is the official start of the WG Last call on this > document. Comments to the list. > > Thanks, > > Dave > > From owner-msdp@network-services.uoregon.edu Wed Nov 20 09:00:11 2002 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 JAA19227 for ; Wed, 20 Nov 2002 09:00:10 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAKDlUbt004277 for ; Wed, 20 Nov 2002 05:47:30 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gAKDlU4G004276 for msdp-outgoing; Wed, 20 Nov 2002 05:47:30 -0800 (PST) Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAKDlRbt004267; Wed, 20 Nov 2002 05:47:27 -0800 (PST) Received: (from eckert@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id FAA20663; Wed, 20 Nov 2002 05:47:15 -0800 (PST) Date: Wed, 20 Nov 2002 05:47:15 -0800 From: Toerless Eckert To: Guo Feng Cc: David Meyer , msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu Subject: Re: MSDP spec 14 Message-ID: <20021120134715.GS1610@cypher.cisco.com> References: <20021118135258.A2084@sprint.net> <002e01c29089$4381e220$86326e0a@HUAWEI.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002e01c29089$4381e220$86326e0a@HUAWEI.COM> User-Agent: Mutt/1.4i 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 On Wed, Nov 20, 2002 at 07:37:53PM +0800, Guo Feng wrote: > Two questions: > > 1.Why is the notification TLV removed ? Because it is not supported in all of the existing implementations and operational practice in the current deployed Internets MSDP infrastructure seem to have shown that that is not a mayor loss - aka: the notification TLVs do not seem to be urgently required to interoperate MSDP. > 2.There are no description about Request and Response TLV Function , will > those two TLVs be obsolete ? None of the things removed from the spec are obsolete, they are just not part of the MSP spec anymore: We have circled for several years around the approach to make a short term solution as good as possible and did not get anywhere. Now we have changed the goal to only include what can considered to be minimally needed to interoperate MSDP and to provide a base functionality that has shown to be implemented by the majority of implementations available and deployed. If a vendor wants to provide this or any other function that at one point in time was (or was not) in the MSDP spec, then he simply adds it to his implementation. He only need to figure out then how to keep his implementation interoperable with the base of MSDP which is specified in the MSDP spec. There are lots of possibilities on how to do this. Cheers Toerless > > ----- Original Message ----- > From: "David Meyer" > To: ; > > Sent: Tuesday, November 19, 2002 5:52 AM > Subject: Re: MSDP spec 14 > > > > >> As discussed today in mboned wg: > > >> > > >> http://www.ietf.org/internet-drafts/draft-ietf-msdp-spec-14.txt > > >> > > > > Folks, this is the official start of the WG Last call on this > > document. Comments to the list. > > > > Thanks, > > > > Dave > > > > > > -- Thanks Toerless Eckert From owner-msdp@network-services.uoregon.edu Wed Nov 20 09:05:15 2002 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 JAA19295 for ; Wed, 20 Nov 2002 09:05:14 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAKDlUbt004277 for ; Wed, 20 Nov 2002 05:47:30 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gAKDlU4G004276 for msdp-outgoing; Wed, 20 Nov 2002 05:47:30 -0800 (PST) Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gAKDlRbt004267; Wed, 20 Nov 2002 05:47:27 -0800 (PST) Received: (from eckert@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id FAA20663; Wed, 20 Nov 2002 05:47:15 -0800 (PST) Date: Wed, 20 Nov 2002 05:47:15 -0800 From: Toerless Eckert To: Guo Feng Cc: David Meyer , msdp@network-services.uoregon.edu, mboned@network-services.uoregon.edu Subject: Re: MSDP spec 14 Message-ID: <20021120134715.GS1610@cypher.cisco.com> References: <20021118135258.A2084@sprint.net> <002e01c29089$4381e220$86326e0a@HUAWEI.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002e01c29089$4381e220$86326e0a@HUAWEI.COM> User-Agent: Mutt/1.4i 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 On Wed, Nov 20, 2002 at 07:37:53PM +0800, Guo Feng wrote: > Two questions: > > 1.Why is the notification TLV removed ? Because it is not supported in all of the existing implementations and operational practice in the current deployed Internets MSDP infrastructure seem to have shown that that is not a mayor loss - aka: the notification TLVs do not seem to be urgently required to interoperate MSDP. > 2.There are no description about Request and Response TLV Function , will > those two TLVs be obsolete ? None of the things removed from the spec are obsolete, they are just not part of the MSP spec anymore: We have circled for several years around the approach to make a short term solution as good as possible and did not get anywhere. Now we have changed the goal to only include what can considered to be minimally needed to interoperate MSDP and to provide a base functionality that has shown to be implemented by the majority of implementations available and deployed. If a vendor wants to provide this or any other function that at one point in time was (or was not) in the MSDP spec, then he simply adds it to his implementation. He only need to figure out then how to keep his implementation interoperable with the base of MSDP which is specified in the MSDP spec. There are lots of possibilities on how to do this. Cheers Toerless > > ----- Original Message ----- > From: "David Meyer" > To: ; > > Sent: Tuesday, November 19, 2002 5:52 AM > Subject: Re: MSDP spec 14 > > > > >> As discussed today in mboned wg: > > >> > > >> http://www.ietf.org/internet-drafts/draft-ietf-msdp-spec-14.txt > > >> > > > > Folks, this is the official start of the WG Last call on this > > document. Comments to the list. > > > > Thanks, > > > > Dave > > > > > > -- Thanks Toerless Eckert From owner-msdp@network-services.uoregon.edu Thu Nov 21 12:58:11 2002 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 MAA12535 for ; Thu, 21 Nov 2002 12:58:10 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gALHelbt021226 for ; Thu, 21 Nov 2002 09:40:47 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gALHelpZ021225 for msdp-outgoing; Thu, 21 Nov 2002 09:40:47 -0800 (PST) Received: from sith.maoz.com (sith.maoz.com [205.167.76.10]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gALHekbt021215; Thu, 21 Nov 2002 09:40:46 -0800 (PST) Received: (from dmm@localhost) by sith.maoz.com (8.12.6/8.12.6) id gALHfbSP025701; Thu, 21 Nov 2002 09:41:37 -0800 Date: Thu, 21 Nov 2002 09:41:37 -0800 From: David Meyer To: msdp@network-services.uoregon.edu Cc: mboned@network-services.uoregon.edu Subject: Re: MSDP spec 14 Message-ID: <20021121094137.A25691@sprint.net> References: <200211201351.gAKDpGVW004308@network-services.uoregon.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200211201351.gAKDpGVW004308@network-services.uoregon.edu>; from eckert@cisco.com on Wed, Nov 20, 2002 at 05:47:15AM -0800 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 All, Toreless summarized the answers to these questions very well. Are there other issues (with Notification or otherwise)? Thanks, Dave On Wed, Nov 20, 2002 at 05:47:15AM -0800, Toerless Eckert wrote: >> On Wed, Nov 20, 2002 at 07:37:53PM +0800, Guo Feng wrote: >> > Two questions: >> > >> > 1.Why is the notification TLV removed ? >> >> Because it is not supported in all of the existing implementations >> and operational practice in the current deployed Internets MSDP >> infrastructure seem to have shown that that is not a mayor loss - >> aka: the notification TLVs do not seem to be urgently required to >> interoperate MSDP. >> >> > 2.There are no description about Request and Response TLV Function , will >> > those two TLVs be obsolete ? >> >> None of the things removed from the spec are obsolete, they are >> just not part of the MSP spec anymore: We have circled for several years >> around the approach to make a short term solution as good as possible and >> did not get anywhere. Now we have changed the goal to only include >> what can considered to be minimally needed to interoperate MSDP >> and to provide a base functionality that has shown to be implemented >> by the majority of implementations available and deployed. >> >> If a vendor wants to provide this or any other function that at one point >> in time was (or was not) in the MSDP spec, then he simply adds it to his >> implementation. He only need to figure out then how to keep his implementation >> interoperable with the base of MSDP which is specified in the MSDP spec. >> There are lots of possibilities on how to do this. >> >> Cheers >> Toerless >> > >> > ----- Original Message ----- >> > From: "David Meyer" >> > To: ; >> > >> > Sent: Tuesday, November 19, 2002 5:52 AM >> > Subject: Re: MSDP spec 14 >> > >> > >> > > >> As discussed today in mboned wg: >> > > >> >> > > >> http://www.ietf.org/internet-drafts/draft-ietf-msdp-spec-14.txt >> > > >> >> > > >> > > Folks, this is the official start of the WG Last call on this >> > > document. Comments to the list. >> > > >> > > Thanks, >> > > >> > > Dave >> > > >> > > >> > >> > >> >> -- >> Thanks >> Toerless Eckert >> From owner-msdp@network-services.uoregon.edu Thu Nov 21 13:04:50 2002 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 NAA12971 for ; Thu, 21 Nov 2002 13:04:50 -0500 (EST) Received: from network-services.uoregon.edu (localhost [127.0.0.1]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gALHelbt021226 for ; Thu, 21 Nov 2002 09:40:47 -0800 (PST) Received: (from majordomo@localhost) by network-services.uoregon.edu (8.12.2/8.12.2/Submit) id gALHelpZ021225 for msdp-outgoing; Thu, 21 Nov 2002 09:40:47 -0800 (PST) Received: from sith.maoz.com (sith.maoz.com [205.167.76.10]) by network-services.uoregon.edu (8.12.2/8.12.2) with ESMTP id gALHekbt021215; Thu, 21 Nov 2002 09:40:46 -0800 (PST) Received: (from dmm@localhost) by sith.maoz.com (8.12.6/8.12.6) id gALHfbSP025701; Thu, 21 Nov 2002 09:41:37 -0800 Date: Thu, 21 Nov 2002 09:41:37 -0800 From: David Meyer To: msdp@network-services.uoregon.edu Cc: mboned@network-services.uoregon.edu Subject: Re: MSDP spec 14 Message-ID: <20021121094137.A25691@sprint.net> References: <200211201351.gAKDpGVW004308@network-services.uoregon.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200211201351.gAKDpGVW004308@network-services.uoregon.edu>; from eckert@cisco.com on Wed, Nov 20, 2002 at 05:47:15AM -0800 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 All, Toreless summarized the answers to these questions very well. Are there other issues (with Notification or otherwise)? Thanks, Dave On Wed, Nov 20, 2002 at 05:47:15AM -0800, Toerless Eckert wrote: >> On Wed, Nov 20, 2002 at 07:37:53PM +0800, Guo Feng wrote: >> > Two questions: >> > >> > 1.Why is the notification TLV removed ? >> >> Because it is not supported in all of the existing implementations >> and operational practice in the current deployed Internets MSDP >> infrastructure seem to have shown that that is not a mayor loss - >> aka: the notification TLVs do not seem to be urgently required to >> interoperate MSDP. >> >> > 2.There are no description about Request and Response TLV Function , will >> > those two TLVs be obsolete ? >> >> None of the things removed from the spec are obsolete, they are >> just not part of the MSP spec anymore: We have circled for several years >> around the approach to make a short term solution as good as possible and >> did not get anywhere. Now we have changed the goal to only include >> what can considered to be minimally needed to interoperate MSDP >> and to provide a base functionality that has shown to be implemented >> by the majority of implementations available and deployed. >> >> If a vendor wants to provide this or any other function that at one point >> in time was (or was not) in the MSDP spec, then he simply adds it to his >> implementation. He only need to figure out then how to keep his implementation >> interoperable with the base of MSDP which is specified in the MSDP spec. >> There are lots of possibilities on how to do this. >> >> Cheers >> Toerless >> > >> > ----- Original Message ----- >> > From: "David Meyer" >> > To: ; >> > >> > Sent: Tuesday, November 19, 2002 5:52 AM >> > Subject: Re: MSDP spec 14 >> > >> > >> > > >> As discussed today in mboned wg: >> > > >> >> > > >> http://www.ietf.org/internet-drafts/draft-ietf-msdp-spec-14.txt >> > > >> >> > > >> > > Folks, this is the official start of the WG Last call on this >> > > document. Comments to the list. >> > > >> > > Thanks, >> > > >> > > Dave >> > > >> > > >> > >> > >> >> -- >> Thanks >> Toerless Eckert >>