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

Acee Lindem <acee@cisco.com> Sat, 17 June 2006 19:09 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrgAO-00007Z-I3; Sat, 17 Jun 2006 15:09:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrgAN-00007U-7Y for ospf@ietf.org; Sat, 17 Jun 2006 15:09:07 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrgAK-00060n-U3 for ospf@ietf.org; Sat, 17 Jun 2006 15:09:07 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 17 Jun 2006 15:09:05 -0400
X-IronPort-AV: i="4.06,145,1149480000"; d="scan'208"; a="90308520:sNHT30032976"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k5HJ93no024521; Sat, 17 Jun 2006 15:09:03 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 17 Jun 2006 15:09:03 -0400
Received: from [10.82.216.166] ([10.82.216.166]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 17 Jun 2006 15:09:02 -0400
Message-ID: <4494534E.1060804@cisco.com>
Date: Sat, 17 Jun 2006 15:09:02 -0400
From: Acee Lindem <acee@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Russ White <riw@cisco.com>
Subject: Re: [OSPF] update "draft-kou-ospf-immediately-replying-hello-00.txt"
References: <00a901c68ece$65b73330$96726e0a@china.huawei.com> <4492D4D7.6070805@cisco.com> <4493FC03.9000007@cisco.com>
In-Reply-To: <4493FC03.9000007@cisco.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Jun 2006 19:09:02.0895 (UTC) FILETIME=[7F106BF0:01C69241]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
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 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.

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