Re: [OSPF] update "draft-kou-ospf-immediately-replying-hello-00.txt"

Zengjie Kou <kouzengjie@huawei.com> Mon, 19 June 2006 11:34 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsI1k-0002M8-UL; Mon, 19 Jun 2006 07:34:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsI1j-0002M3-H8 for ospf@ietf.org; Mon, 19 Jun 2006 07:34:43 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsI1h-0002uA-K6 for ospf@ietf.org; Mon, 19 Jun 2006 07:34:43 -0400
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J1300K8ZVBHTG@szxga02-in.huawei.com> for ospf@ietf.org; Mon, 19 Jun 2006 19:45:17 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J1300CPAVBH7N@szxga02-in.huawei.com> for ospf@ietf.org; Mon, 19 Jun 2006 19:45:17 +0800 (CST)
Received: from k49110 ([10.110.114.150]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J130045WV2PGC@szxml04-in.huawei.com> for ospf@ietf.org; Mon, 19 Jun 2006 19:40:02 +0800 (CST)
Date: Mon, 19 Jun 2006 19:29:20 +0800
From: Zengjie Kou <kouzengjie@huawei.com>
Subject: Re: [OSPF] update "draft-kou-ospf-immediately-replying-hello-00.txt"
To: mike shand <mshand@cisco.com>, Acee Lindem <acee@cisco.com>
Message-id: <001901c69393$9ba00930$96726e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <00a901c68ece$65b73330$96726e0a@china.huawei.com> <4492D4D7.6070805@cisco.com> <4493FC03.9000007@cisco.com> <4494534E.1060804@cisco.com> <7.0.1.0.0.20060619105457.02108aa0@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: ospf@ietf.org
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org

hi, mike
 For interoperability of the immediate hello, i think it is necessary.
 If each implementation is independent, the mechanism will be not consistent and the effort of immediate hello will be small.
 If we standardize the implementation or mechanism, all the router supporting immediate hello will respond conformably. The
effort will be great.
 The experiment data in the draft shows some evident benefits with immediate hello consistent interoperability.

thanks
Zengjie

----- Original Message ----- 
From: "mike shand" <mshand@cisco.com>
To: "Acee Lindem" <acee@cisco.com>
Cc: <ospf@ietf.org>
Sent: Monday, June 19, 2006 5:56 PM
Subject: Re: [OSPF] update "draft-kou-ospf-immediately-replying-hello-00.txt"


> At 20:09 17/06/2006, Acee Lindem wrote:
>>Hi Zengjie,
>>Russ White wrote:
>>
>> >-----BEGIN PGP SIGNED MESSAGE-----
>> >Hash: SHA1
>> >
>> >
>> >
>> >
>> >>Speaking as a WG member, my personal opinion is that the WG should
>> >>accept this document an an informational of BCP track RFC.
>> >>
>> >>
>> >
>> >This sounds fine.... Count my vote in that direction, as well.
>> >
>> >
>>Actually, I meant NOT accept as WG document I guess that what I get for
>>trying
>>to respond to E-mail sitting in the middle seat on a crowded plane. Here
>>is my
>>reasoning why:
>>
>>1. This behavior is not new - there are several implementations that
>>already reply immediately in certain situations.
>>2. There are many ways of doing this and it is unlikely we will
>>agree on the exact details of how it should be done. I, for one,
>>have implemented it differently than documented in this draft.
> 
> and more particularly it doesn't matter from an interoperability 
> point of view which way you do it, so
> this doesn't seem to be behaviour which it makes sense to standardize.
> 
>         Mike
> 
> 
> 
>>I just don't think there is that much to be gained by documenting
>>this after the fact when there isn't agreement on the sudtleties of
>>operation.
>>
>>Sorry for the confusion.
>>
>>Thanks,
>>Acee
>>
>> >:-)
>> >
>> >Russ
>> >
>> >
>> >
>> >- --
>> >riw@cisco.com CCIE <>< Grace Alone
>> >
>> >-----BEGIN PGP SIGNATURE-----
>> >Version: GnuPG v1.4.2.2 (MingW32)
>> >Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>> >
>> >iD8DBQFEk/wDER27sUhU9OQRAvY9AKCrebSk6VRgr6L/SJGB12m4ZErV0ACg1B+8
>> >UKcbdXfJwL/u5nzZERpS7HI=
>> >=8pvC
>> >-----END PGP SIGNATURE-----
>> >
>> >
>> >
>>
>>_______________________________________________
>>OSPF mailing list
>>OSPF@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ospf
> 
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www1.ietf.org/mailman/listinfo/ospf
>

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf