Padding for OSPF packets in the OSPF implementations

"Singh, Gurpreet" <Gurpreet.Singh@SPIRENTCOM.COM> Wed, 09 October 2002 22:00 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06048 for <ospf-archive@LISTS.IETF.ORG>; Wed, 9 Oct 2002 18:00:36 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <2.00763074@cherry.ease.lsoft.com>; Wed, 9 Oct 2002 18:02:40 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 273261 for OSPF@DISCUSS.MICROSOFT.COM; Wed, 9 Oct 2002 18:02:40 -0400
Received: from 63.165.80.17 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 9 Oct 2002 18:02:39 -0400
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19) id <T5AYJ0P2>; Wed, 9 Oct 2002 12:09:41 -1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <8AC36D3167EED41184C800508BD954050320B7EB@apollo.adtech-inc.com>
Date: Wed, 09 Oct 2002 12:09:32 -1000
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: "Singh, Gurpreet" <Gurpreet.Singh@SPIRENTCOM.COM>
Subject: Padding for OSPF packets in the OSPF implementations
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list

Hi

OSPF spec RFC 2328 does not allow any padding field for extra bytes for the
OSPF pakcets.

Consider the following situation.


 <<...OLE_Obj...>>
The IP packet length in the IP header covers the Junk bytes. But the OSPF
header does not.

If such a OSPF packet is received should the implementations accept this
packet as a valid packet or ignore it ?

I know this is a implementation specific question but what would be the
correct implementation according to the protocol specification.

Thanks

Gurpreet