From routing-discussion-admin@ietf.org Tue Feb 4 10:11:02 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24603 for ; Tue, 4 Feb 2003 10:11:02 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14F99J00331; Tue, 4 Feb 2003 10:09:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14F2TJ31984 for ; Tue, 4 Feb 2003 10:02:29 -0500 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24330 for ; Tue, 4 Feb 2003 09:56:27 -0500 (EST) Received: from redback.com (login004.redback.com [155.53.12.57]) by prattle.redback.com (Postfix) with ESMTP id E42431B4DD6; Tue, 4 Feb 2003 07:00:01 -0800 (PST) Message-ID: <3E3FD4EA.5050105@redback.com> From: Acee Lindem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: danny@tcb.net Cc: routing-discussion@ietf.org Subject: Re: GR/NSF Terminology References: <20030130153403.2735C55F62@nomad.tcb.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 04 Feb 2003 09:57:46 -0500 Content-Transfer-Encoding: 7bit Danny, et al, FWIW, draft-ietf-ospf-hitless-restart-06.txt now uses the term "graceful restart" rather than "hitless restart". I didn't change the draft name but once it is published as an RFC all remnants of "hitless" will be gone. Danny McPherson wrote: >>The OSPF document you cite defines various terms, but in an >>OSPF-specific fashion. Furthermore, the definitions are not >>collected anywhere in the document but are peppered throughout it... >>which is fine in context but doesn't lend itself to generic use of >>the terms. > > > Agreed. > > >>Seems like there are two things we could do: >> >>First, leave the documents as they are. This is my preferred >>alternative. The docs are relatively well advanced in terms of >>specification and even deployment, and doing what would be a >>non-trivial update solely for the purpose of aligning terminology >>strikes me a being work for work's sake. This is doubly true because >>a major terminology change creates the risk of introducing subtle >>errors to the spec if one isn't careful. Apart from aesthetics, what >>need do you think is fulfilled by aligning the specs? >> >>Alternately, if we do want to go ahead and change the specs, then a >>(generic) definitions document such as you have volunteered to write >>seems a necessity. I'm not a fan of "framework" documents and I hope >>we could keep the scope of the proposed definitions document focused. > > > OK, so folks don't seem to be to keen on the idea at this point. > Given that I'm not attached to the idea of more work "for the > sake of work" then I'll drop it. I believe there is room for > commonality but look where that's got me in PWE3 *8^/ > > > >>By the way, I think "graceful restart" has historic precedence over >>"hitless restart" if you want to align terms :-). > > > Agreed. > > -danny > > _______________________________________________ > routing-discussion mailing list > routing-discussion@ietf.org > https://www1.ietf.org/mailman/listinfo/routing-discussion > -- Acee _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue Feb 4 10:11:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24621 for ; Tue, 4 Feb 2003 10:11:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h14FHRM00682 for routing-discussion-archive@odin.ietf.org; Tue, 4 Feb 2003 10:17:27 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14F99J00331; Tue, 4 Feb 2003 10:09:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14F2TJ31984 for ; Tue, 4 Feb 2003 10:02:29 -0500 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24330 for ; Tue, 4 Feb 2003 09:56:27 -0500 (EST) Received: from redback.com (login004.redback.com [155.53.12.57]) by prattle.redback.com (Postfix) with ESMTP id E42431B4DD6; Tue, 4 Feb 2003 07:00:01 -0800 (PST) Message-ID: <3E3FD4EA.5050105@redback.com> From: Acee Lindem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: danny@tcb.net Cc: routing-discussion@ietf.org Subject: Re: GR/NSF Terminology References: <20030130153403.2735C55F62@nomad.tcb.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 04 Feb 2003 09:57:46 -0500 Content-Transfer-Encoding: 7bit Danny, et al, FWIW, draft-ietf-ospf-hitless-restart-06.txt now uses the term "graceful restart" rather than "hitless restart". I didn't change the draft name but once it is published as an RFC all remnants of "hitless" will be gone. Danny McPherson wrote: >>The OSPF document you cite defines various terms, but in an >>OSPF-specific fashion. Furthermore, the definitions are not >>collected anywhere in the document but are peppered throughout it... >>which is fine in context but doesn't lend itself to generic use of >>the terms. > > > Agreed. > > >>Seems like there are two things we could do: >> >>First, leave the documents as they are. This is my preferred >>alternative. The docs are relatively well advanced in terms of >>specification and even deployment, and doing what would be a >>non-trivial update solely for the purpose of aligning terminology >>strikes me a being work for work's sake. This is doubly true because >>a major terminology change creates the risk of introducing subtle >>errors to the spec if one isn't careful. Apart from aesthetics, what >>need do you think is fulfilled by aligning the specs? >> >>Alternately, if we do want to go ahead and change the specs, then a >>(generic) definitions document such as you have volunteered to write >>seems a necessity. I'm not a fan of "framework" documents and I hope >>we could keep the scope of the proposed definitions document focused. > > > OK, so folks don't seem to be to keen on the idea at this point. > Given that I'm not attached to the idea of more work "for the > sake of work" then I'll drop it. I believe there is room for > commonality but look where that's got me in PWE3 *8^/ > > > >>By the way, I think "graceful restart" has historic precedence over >>"hitless restart" if you want to align terms :-). > > > Agreed. > > -danny > > _______________________________________________ > routing-discussion mailing list > routing-discussion@ietf.org > https://www1.ietf.org/mailman/listinfo/routing-discussion > -- Acee _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Tue Feb 25 01:54:46 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08528 for ; Tue, 25 Feb 2003 01:54:46 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P6vPp24044; Tue, 25 Feb 2003 01:57:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P6pmp23888 for ; Tue, 25 Feb 2003 01:51:48 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08283 for ; Tue, 25 Feb 2003 01:42:25 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1) by psg.com with esmtp (Exim 3.36 #1) id 18nYr4-000PTe-00 for routing-discussion@ietf.org; Mon, 24 Feb 2003 22:46:18 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.62i) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <13390975535.20030224224607@psg.com> To: routing-discussion@ietf.org Subject: RTG area meeting in SF MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 24 Feb 2003 22:46:07 -0800 Content-Transfer-Encoding: 7bit Folks- We're going to have an open area meeting in SF. If you would like a time slot, please let me know, I'll be putting the agenda together. -- Alex _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue Feb 25 01:55:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08554 for ; Tue, 25 Feb 2003 01:55:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1P74ar24698 for routing-discussion-archive@odin.ietf.org; Tue, 25 Feb 2003 02:04:36 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P6vPp24044; Tue, 25 Feb 2003 01:57:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P6pmp23888 for ; Tue, 25 Feb 2003 01:51:48 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08283 for ; Tue, 25 Feb 2003 01:42:25 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1) by psg.com with esmtp (Exim 3.36 #1) id 18nYr4-000PTe-00 for routing-discussion@ietf.org; Mon, 24 Feb 2003 22:46:18 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.62i) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <13390975535.20030224224607@psg.com> To: routing-discussion@ietf.org Subject: RTG area meeting in SF MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 24 Feb 2003 22:46:07 -0800 Content-Transfer-Encoding: 7bit Folks- We're going to have an open area meeting in SF. If you would like a time slot, please let me know, I'll be putting the agenda together. -- Alex _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Wed Feb 26 16:45:14 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27395 for ; Wed, 26 Feb 2003 16:45:14 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QLbdp12993; Wed, 26 Feb 2003 16:37:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PDqlp30127 for ; Tue, 25 Feb 2003 08:52:47 -0500 Received: from presque.djinesys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00944 for ; Tue, 25 Feb 2003 08:43:14 -0500 (EST) Received: (from root@localhost) by presque.djinesys.com (8.11.3/8.11.1) id h1PDl8v61746 for routing-discussion@ietf.org; Tue, 25 Feb 2003 08:47:08 -0500 (EST) (envelope-from shares@nexthop.com) Received: from mail.corp.nexthop.com ([64.211.218.233]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id h1PDl2C61732 for ; Tue, 25 Feb 2003 08:47:02 -0500 (EST) (envelope-from shares@nexthop.com) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: RTG area meeting in SF X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: Thread-Topic: RTG area meeting in SF Thread-Index: AcLcm0dZeHrq9aDKQV++pta96aVQ+AAOQxtA From: "Susan Hares" To: "Alex Zinin" , X-Virus-Scanned: by AMaViS perl-11 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1PDqlp30128 Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 25 Feb 2003 08:47:02 -0500 Content-Transfer-Encoding: 8bit Alex: Any time before Thursday noon. Sue -----Original Message----- From: Alex Zinin [mailto:zinin@psg.com] Sent: Tuesday, February 25, 2003 1:46 AM To: routing-discussion@ietf.org Subject: RTG area meeting in SF Folks- We're going to have an open area meeting in SF. If you would like a time slot, please let me know, I'll be putting the agenda together. -- Alex _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Wed Feb 26 16:46:07 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27426 for ; Wed, 26 Feb 2003 16:46:07 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QLtmq13995 for routing-discussion-archive@odin.ietf.org; Wed, 26 Feb 2003 16:55:48 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QLbdp12993; Wed, 26 Feb 2003 16:37:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PDqlp30127 for ; Tue, 25 Feb 2003 08:52:47 -0500 Received: from presque.djinesys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00944 for ; Tue, 25 Feb 2003 08:43:14 -0500 (EST) Received: (from root@localhost) by presque.djinesys.com (8.11.3/8.11.1) id h1PDl8v61746 for routing-discussion@ietf.org; Tue, 25 Feb 2003 08:47:08 -0500 (EST) (envelope-from shares@nexthop.com) Received: from mail.corp.nexthop.com ([64.211.218.233]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id h1PDl2C61732 for ; Tue, 25 Feb 2003 08:47:02 -0500 (EST) (envelope-from shares@nexthop.com) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: RTG area meeting in SF X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: Thread-Topic: RTG area meeting in SF Thread-Index: AcLcm0dZeHrq9aDKQV++pta96aVQ+AAOQxtA From: "Susan Hares" To: "Alex Zinin" , X-Virus-Scanned: by AMaViS perl-11 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1PDqlp30128 Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 25 Feb 2003 08:47:02 -0500 Content-Transfer-Encoding: 8bit Alex: Any time before Thursday noon. Sue -----Original Message----- From: Alex Zinin [mailto:zinin@psg.com] Sent: Tuesday, February 25, 2003 1:46 AM To: routing-discussion@ietf.org Subject: RTG area meeting in SF Folks- We're going to have an open area meeting in SF. If you would like a time slot, please let me know, I'll be putting the agenda together. -- Alex _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Thu Feb 27 00:51:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09122 for ; Thu, 27 Feb 2003 00:51:37 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1R5tKp10206; Thu, 27 Feb 2003 00:55:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1R5n0p10065 for ; Thu, 27 Feb 2003 00:49:00 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08874 for ; Thu, 27 Feb 2003 00:38:38 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1) by psg.com with esmtp (Exim 3.36 #1) id 18oGoT-000DCo-00; Wed, 26 Feb 2003 21:42:33 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.62i) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <167259942968.20030226214215@psg.com> To: "Susan Hares" CC: routing-discussion@ietf.org Subject: Re: RTG area meeting in SF In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 26 Feb 2003 21:42:15 -0800 Content-Transfer-Encoding: 7bit Sue- Sorry, I meant if someone wanted a slot for a discussion at the meeting. The meeting itself has been scheduled for Monday 19:30--22:00. -- Alex Tuesday, February 25, 2003, 5:47:02 AM, Susan Hares wrote: > Alex: > Any time before Thursday noon. > Sue > -----Original Message----- > From: Alex Zinin [mailto:zinin@psg.com] > Sent: Tuesday, February 25, 2003 1:46 AM > To: routing-discussion@ietf.org > Subject: RTG area meeting in SF > Folks- > We're going to have an open area meeting in SF. > If you would like a time slot, please let me > know, I'll be putting the agenda together. _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Thu Feb 27 00:52:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09158 for ; Thu, 27 Feb 2003 00:52:39 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1R62Ul10565 for routing-discussion-archive@odin.ietf.org; Thu, 27 Feb 2003 01:02:30 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1R5tKp10206; Thu, 27 Feb 2003 00:55:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1R5n0p10065 for ; Thu, 27 Feb 2003 00:49:00 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08874 for ; Thu, 27 Feb 2003 00:38:38 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1) by psg.com with esmtp (Exim 3.36 #1) id 18oGoT-000DCo-00; Wed, 26 Feb 2003 21:42:33 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.62i) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <167259942968.20030226214215@psg.com> To: "Susan Hares" CC: routing-discussion@ietf.org Subject: Re: RTG area meeting in SF In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 26 Feb 2003 21:42:15 -0800 Content-Transfer-Encoding: 7bit Sue- Sorry, I meant if someone wanted a slot for a discussion at the meeting. The meeting itself has been scheduled for Monday 19:30--22:00. -- Alex Tuesday, February 25, 2003, 5:47:02 AM, Susan Hares wrote: > Alex: > Any time before Thursday noon. > Sue > -----Original Message----- > From: Alex Zinin [mailto:zinin@psg.com] > Sent: Tuesday, February 25, 2003 1:46 AM > To: routing-discussion@ietf.org > Subject: RTG area meeting in SF > Folks- > We're going to have an open area meeting in SF. > If you would like a time slot, please let me > know, I'll be putting the agenda together. _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Fri Feb 28 06:20:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20499 for ; Fri, 28 Feb 2003 06:20:51 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SBORp17898; Fri, 28 Feb 2003 06:24:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SBELp17617 for ; Fri, 28 Feb 2003 06:14:21 -0500 Received: from mailout3.samsung.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20153 for ; Fri, 28 Feb 2003 06:03:23 -0500 (EST) Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) id <0HB000L01MU7KX@mailout3.samsung.com> for routing-discussion@ietf.org; Fri, 28 Feb 2003 20:06:07 +0900 (KST) Received: from ms.samsung.com (localhost [127.0.0.1]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) with ESMTP id <0HB000GSGMU6ZY@mailout3.samsung.com> for routing-discussion@ietf.org; Fri, 28 Feb 2003 20:06:07 +0900 (KST) Received: from custom-daemon.ms.samsung.com by ms.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) id <0HB000601MO06D@ms.samsung.com> for routing-discussion@ietf.org; Fri, 28 Feb 2003 20:02:24 +0900 (KST) Received: from samsung.com (localhost [127.0.0.1]) by ms.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) with ESMTP id <0HB0001MMMNZB2@ms.samsung.com> for routing-discussion@ietf.org; Fri, 28 Feb 2003 20:02:24 +0900 (KST) Received: from [107.108.3.177] by ms.samsung.com (mshttpd); Fri, 28 Feb 2003 11:02:23 +0000 (GMT) From: Karthikeyan Subject: Doubt in OSPF v3 -SPF calculation To: routing-discussion@ietf.org Message-id: <24baa724731f.24731f24baa7@samsung.com> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.05 (built Nov 6 2002) Content-type: text/html; charset=EUC-KR Content-language: ko Content-transfer-encoding: quoted-printable Content-disposition: inline X-Accept-Language: ko Content-Transfer-Encoding: quoted-printable Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 28 Feb 2003 11:02:23 +0000 (GMT) Content-Transfer-Encoding: quoted-printable = =3Chtml=3E=3Cnobr=3E=3Cimg src=3Dhttp=3A//maildb=2Esamsung=2Ecom=3A8001/o= penconfirm=3Fparm=3Dundefined=5F=5Fundefined20030228163610732 width=3D=22= 1=22 height=3D=221=22=3E=3C/nobr=3E =3Cfont size=3D3 face=3D=22=B1=BC=B8=B2=C3=BC=22=3E =3Cpre=3EHello to all= =2C I have some doubt in OSPF v3 SPF calculation=2E In section 3=2E8=2E1 while processing multiple router LSA associated with= the router The RFC says that =22The Options field and the router type bits (bits W=2C V=2C E and B) s= hould always = be taken from =22fragment=22 with the smallest Link State ID=22 = This process is done in step 2 of =22calculating shortest path tree fo= r that area=22 Can anybody explain me why the options field and the router type bits sho= uld always be taken from fragment with smallest Link state ID=3F Thanks in advance=2E S=2EKarthikeyan=3C/font=3E=3C/pre=3E=3C/html=3E _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Fri Feb 28 06:21:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20540 for ; Fri, 28 Feb 2003 06:21:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1SBWAh18198 for routing-discussion-archive@odin.ietf.org; Fri, 28 Feb 2003 06:32:10 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SBORp17898; Fri, 28 Feb 2003 06:24:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SBELp17617 for ; Fri, 28 Feb 2003 06:14:21 -0500 Received: from mailout3.samsung.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20153 for ; Fri, 28 Feb 2003 06:03:23 -0500 (EST) Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) id <0HB000L01MU7KX@mailout3.samsung.com> for routing-discussion@ietf.org; Fri, 28 Feb 2003 20:06:07 +0900 (KST) Received: from ms.samsung.com (localhost [127.0.0.1]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) with ESMTP id <0HB000GSGMU6ZY@mailout3.samsung.com> for routing-discussion@ietf.org; Fri, 28 Feb 2003 20:06:07 +0900 (KST) Received: from custom-daemon.ms.samsung.com by ms.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) id <0HB000601MO06D@ms.samsung.com> for routing-discussion@ietf.org; Fri, 28 Feb 2003 20:02:24 +0900 (KST) Received: from samsung.com (localhost [127.0.0.1]) by ms.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) with ESMTP id <0HB0001MMMNZB2@ms.samsung.com> for routing-discussion@ietf.org; Fri, 28 Feb 2003 20:02:24 +0900 (KST) Received: from [107.108.3.177] by ms.samsung.com (mshttpd); Fri, 28 Feb 2003 11:02:23 +0000 (GMT) From: Karthikeyan Subject: Doubt in OSPF v3 -SPF calculation To: routing-discussion@ietf.org Message-id: <24baa724731f.24731f24baa7@samsung.com> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.05 (built Nov 6 2002) Content-type: text/html; charset=EUC-KR Content-language: ko Content-transfer-encoding: quoted-printable Content-disposition: inline X-Accept-Language: ko Content-Transfer-Encoding: quoted-printable Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 28 Feb 2003 11:02:23 +0000 (GMT) Content-Transfer-Encoding: quoted-printable = =3Chtml=3E=3Cnobr=3E=3Cimg src=3Dhttp=3A//maildb=2Esamsung=2Ecom=3A8001/o= penconfirm=3Fparm=3Dundefined=5F=5Fundefined20030228163610732 width=3D=22= 1=22 height=3D=221=22=3E=3C/nobr=3E =3Cfont size=3D3 face=3D=22=B1=BC=B8=B2=C3=BC=22=3E =3Cpre=3EHello to all= =2C I have some doubt in OSPF v3 SPF calculation=2E In section 3=2E8=2E1 while processing multiple router LSA associated with= the router The RFC says that =22The Options field and the router type bits (bits W=2C V=2C E and B) s= hould always = be taken from =22fragment=22 with the smallest Link State ID=22 = This process is done in step 2 of =22calculating shortest path tree fo= r that area=22 Can anybody explain me why the options field and the router type bits sho= uld always be taken from fragment with smallest Link state ID=3F Thanks in advance=2E S=2EKarthikeyan=3C/font=3E=3C/pre=3E=3C/html=3E _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Fri Feb 28 10:24:16 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01421 for ; Fri, 28 Feb 2003 10:24:16 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFNkp03220; Fri, 28 Feb 2003 10:23:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFFAp02873 for ; Fri, 28 Feb 2003 10:15:10 -0500 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00932 for ; Fri, 28 Feb 2003 10:04:09 -0500 (EST) Received: from redback.com (login001.redback.com [155.53.12.18]) by prattle.redback.com (Postfix) with ESMTP id 327BB62924; Fri, 28 Feb 2003 07:08:04 -0800 (PST) Message-ID: <3E5F7BB3.2040202@redback.com> From: Acee Lindem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karthikeyan Cc: routing-discussion@ietf.org Subject: Re: Doubt in OSPF v3 -SPF calculation References: <24baa724731f.24731f24baa7@samsung.com> Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 28 Feb 2003 10:09:39 -0500 Content-Transfer-Encoding: 7bit Karthikeyan wrote: > > > Hello to all, > > I have some doubt in OSPF v3 SPF calculation. > > In section 3.8.1 while processing multiple router LSA associated with the router > The RFC says that > "The Options field and the router type bits (bits W, V, E and B) should always > be taken from "fragment" with the smallest Link State ID" > This process is done in step 2 of "calculating shortest path tree for that area" > Can anybody explain me why the options field and the router type bits should > always be taken from fragment with smallest Link state ID? Hello Karthikeyan, This allows the originating router to only re-originate a single LSA "fragment" when one of these bits change. Without this rule, the originating router would have to re-originate all the router LSA "fragments" for that area. Thanks, Acee > > Thanks in advance. > S.Karthikeyan > > _______________________________________________ routing-discussion > mailing list routing-discussion@ietf.org > https://www1.ietf.org/mailman/listinfo/routing-discussion -- Acee _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Fri Feb 28 10:25:06 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01456 for ; Fri, 28 Feb 2003 10:25:05 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1SFZa403840 for routing-discussion-archive@odin.ietf.org; Fri, 28 Feb 2003 10:35:36 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFNkp03220; Fri, 28 Feb 2003 10:23:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFFAp02873 for ; Fri, 28 Feb 2003 10:15:10 -0500 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00932 for ; Fri, 28 Feb 2003 10:04:09 -0500 (EST) Received: from redback.com (login001.redback.com [155.53.12.18]) by prattle.redback.com (Postfix) with ESMTP id 327BB62924; Fri, 28 Feb 2003 07:08:04 -0800 (PST) Message-ID: <3E5F7BB3.2040202@redback.com> From: Acee Lindem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karthikeyan Cc: routing-discussion@ietf.org Subject: Re: Doubt in OSPF v3 -SPF calculation References: <24baa724731f.24731f24baa7@samsung.com> Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 28 Feb 2003 10:09:39 -0500 Content-Transfer-Encoding: 7bit Karthikeyan wrote: > > > Hello to all, > > I have some doubt in OSPF v3 SPF calculation. > > In section 3.8.1 while processing multiple router LSA associated with the router > The RFC says that > "The Options field and the router type bits (bits W, V, E and B) should always > be taken from "fragment" with the smallest Link State ID" > This process is done in step 2 of "calculating shortest path tree for that area" > Can anybody explain me why the options field and the router type bits should > always be taken from fragment with smallest Link state ID? Hello Karthikeyan, This allows the originating router to only re-originate a single LSA "fragment" when one of these bits change. Without this rule, the originating router would have to re-originate all the router LSA "fragments" for that area. Thanks, Acee > > Thanks in advance. > S.Karthikeyan > > _______________________________________________ routing-discussion > mailing list routing-discussion@ietf.org > https://www1.ietf.org/mailman/listinfo/routing-discussion -- Acee _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion