Re: [OSPF] OSPFv2 option bit

Abhay Roy <akr@cisco.com> Wed, 03 October 2007 13:49 UTC

Return-path: <ospf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Id4bE-0002BZ-O4; Wed, 03 Oct 2007 09:49:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Id4bC-00028O-PK for ospf@ietf.org; Wed, 03 Oct 2007 09:49:14 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Id4bC-00023p-Bo for ospf@ietf.org; Wed, 03 Oct 2007 09:49:14 -0400
X-IronPort-AV: E=Sophos;i="4.21,224,1188802800"; d="scan'208";a="229695243"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 03 Oct 2007 06:49:13 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l93DnDGH006605; Wed, 3 Oct 2007 06:49:13 -0700
Received: from akr-lnx (akr-lnx.cisco.com [171.71.54.82]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l93DnD0X023187; Wed, 3 Oct 2007 13:49:13 GMT
Date: Wed, 03 Oct 2007 06:49:13 -0700
From: Abhay Roy <akr@cisco.com>
To: Santosh P K <sanpk316@gmail.com>
Subject: Re: [OSPF] OSPFv2 option bit
In-Reply-To: <a0d41f8e0710030153u572e1a8ci1c00923b102a7a5@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0710030645371.15804@akr-lnx.cisco.com>
References: <a0d41f8e0710030153u572e1a8ci1c00923b102a7a5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2454; t=1191419353; x=1192283353; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=akr@cisco.com; z=From:=20Abhay=20Roy=20<akr@cisco.com> |Subject:=20Re=3A=20[OSPF]=20OSPFv2=20option=20bit |Sender:=20; bh=IsS6NNN+JOfne2b9TRbqqMEV6fy3DyVXFK+5SJyNR0w=; b=REhR6aGybJ1Kz4Zd4yW8cSBe9aStY+T5JwAtjyOLEQEY+ZQi1Mbka1T8FFF2/NeiBGqbItZP aVYdHWCEXa5M2wOIFEQAXo6AFEWkbfE7ZsAdXWVtSDQHrM1NKilLR92O;
Authentication-Results: sj-dkim-2; header.From=akr@cisco.com; dkim=pass (sig from cisco.com/sjdkim2002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: "ospf@ietf.org" <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 Santosh,

There is also the respin of RFC4813 (which includes OSPFv3),
which is on standards track. Once we get to handling IANA
action from draft-ietf-ospf-lls-03.txt, IANA will allocate
bit 0x10 for L-bit.

Regards,
-Abhay

On 10/03/07+0530 at 2:23pm, Santosh P K writes:

> Hi All,
>       I was going through the option bits of OSPFv2. I have couple of
> doubts on this please clarify.
>
>
>      In RFC 2328 in A.2  it says
>                 +----------------------------------------------+
>                  | * | * | DC | EA | N/P | MC | E | * |
>                 +----------------------------------------------+
>     That is
>      Value   Description
>        ------  ----------------
>        0x01    Reserved
>        0x02    E-bit
>        0x04    MC-bit
>        0x08    N/P-bit
>        0x10    EA
>        0x20    DC-bit
>        0x40    Reserved
>        0x80    Reserved
>
>
>
> In RFC 4813 OSPF Link-Local Signaling sec 2.1 it says
>                    +---+---+---+---+---+---+---+---+
>                     | * | O | DC| L |N/P| MC| E | * |
>                    +---+---+---+---+---+---+---+-+-+
>
> That is
>       Value   Description
>        ------  ----------------
>        0x01    Reserved
>        0x02    E-bit
>        0x04    MC-bit
>        0x08    N/P-bit
>        0x10    L-bit
>        0x20    DC-bit
>        0x40    O-bit
>        0x80    Reserved
>
>
>
> In IANA document (http://www.iana.org/assignments/ospfv2-parameters)
> last updated 2007-08-14 says
>
>
>           Value   Description       Reference
>             ------     ----------------       ---------
>            0x01    MT-bit            [RFC4915]
>            0x02    E-bit              [RFC2328]
>            0x04    MC-bit           [RFC1584]
>            0x08    N/P-bit           [RFC3101]
>            0x10    Reserved
>            0x20    DC-bit            [RFC1793]
>            0x40    O-bit              [RFC2370]
>            0x80    DN-bit            [RFC4576]
>
>
> In all the three documents there is a conflict for bit  0x10, RFC 2328
> uses it as EA bit , RFC 4813 uses it as L bit and IANA document says
> its reserved. Out of all these three which one shall i consider.
>
>
> Thanks and regards
> Santosh P K
>
> _______________________________________________
> 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