Re: [OSPF] AD Review of draft-ietf-ospf-cap
Acee Lindem <acee@cisco.com> Thu, 19 October 2006 22:56 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GagoX-0001mg-Ut; Thu, 19 Oct 2006 18:56:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GagoW-0001iA-Er for ospf@ietf.org; Thu, 19 Oct 2006 18:56:36 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GagoJ-0004Bx-Jz for ospf@ietf.org; Thu, 19 Oct 2006 18:56:36 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 19 Oct 2006 15:56:23 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9JMuNSo030347; Thu, 19 Oct 2006 15:56:23 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k9JMuMW4016863; Thu, 19 Oct 2006 15:56:22 -0700 (PDT)
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.1830); Thu, 19 Oct 2006 18:56:22 -0400
Received: from [10.82.216.102] ([10.82.216.102]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 18:56:22 -0400
Message-ID: <45380295.3040203@cisco.com>
Date: Thu, 19 Oct 2006 18:56:21 -0400
From: Acee Lindem <acee@cisco.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Bill Fenner <fenner@research.att.com>
Subject: Re: [OSPF] AD Review of draft-ietf-ospf-cap
References: <200610191232.k9JCWdlG028778@bright.research.att.com>
In-Reply-To: <200610191232.k9JCWdlG028778@bright.research.att.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Oct 2006 22:56:22.0112 (UTC) FILETIME=[CBE4C600:01C6F3D1]
DKIM-Signature: a=rsa-sha1; q=dns; l=2401; t=1161298583; x=1162162583; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=acee@cisco.com; z=From:Acee=20Lindem=20<acee@cisco.com> |Subject:Re=3A=20[OSPF]=20AD=20Review=20of=20draft-ietf-ospf-cap; X=v=3Dcisco.com=3B=20h=3Dc+JmBEW7rwvdfW93DwNImUodnlo=3D; b=B/B3wFpzGfrGc6qTU/FngAI3oGXLrajGhM17VtLU7PvtukvLilscJ1WHAjTFD21QcwJ5xlzH 6wVUQcV4ePZX4uGaWMvsXldiOXRXk+ZqbWNHu+70hhKS3ZSBP/wsBvg+;
Authentication-Results: sj-dkim-3.cisco.com; header.From=acee@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
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 Bill, Bill Fenner wrote: > I'm sorry for taking so long on this review. > > My major comment is that I think that the bit order in > the RI TLV is confusing. (Partly because the IETF-standard > packet picture is confusing!) > > Check this combination: > > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Informational Capabilities | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > Bit Capabilities > > 1 OSPF graceful restart capable [GRACE] > .. > > >From the picture, this could mean 0x40000000, while I think it intends > 0x00000001. This may be more confusing when (if) the 33rd bit is > assigned. I'd recommend a description of the bit numbering, along > the lines of > > Bits in the Informational Capabilities field are numbered beginning at > 1, starting at the low-order bit of the first 32-bit word. If further > 32-bit words are used, the low-order bit of the second one is numbered > 33, the next one is 65, etc. > > (That's just off the top of my head and may not make complete sense). > Alternately, you could represent the bits as hex values, e.g. > 0x1, 0x2, 0x4, 0x8, 0x10 instead of 1,2,3,4,5. > Actually we did mean to start with the most significant bit in the 32 bit field consistent with IETF standard numbering. However, the document has changed over its lifetime and it looks like we've missed bit 0. Since this TLV is for informational purposes I think it would make sense to reclaim bit 0. I'll also claify the numbering and contact someone regarding update of one of the existing implementations. > The other item is the IANA considerations. Normally we don't say > that a WG is the expert, since the WG may not live forever; we say > that the IESG designates an expert, and the IESG designates the > current WG chairs while the WG exists. > I'll replace "subject to review by the OSPF WG" with "subject to review by an expert designated by the IESG". Thanks, Acee > Bill > > _______________________________________________ > 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] AD Review of draft-ietf-ospf-cap Bill Fenner
- Re: [OSPF] AD Review of draft-ietf-ospf-cap Acee Lindem
- Re: [OSPF] AD Review of draft-ietf-ospf-cap Acee Lindem
- Re: [OSPF] AD Review of draft-ietf-ospf-cap Bill Fenner
- Re: [OSPF] AD Review of draft-ietf-ospf-cap Bill Fenner
- Re: [OSPF] AD Review of draft-ietf-ospf-cap Acee Lindem