OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Alex Zinin (alexzininHOME.COM)
Date: Sat Apr 28 2001 - 22:45:34 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Kathy,

     I think I missed this message...

     Indeed draft-ietf-ospf-lls-00.txt overwrites the EA bit
     with L-bit. EA-bit was intended to indicate External Attribute
     capability, but this extensions was not implemented, so
     it is ok to use this position.

     As far as the O-bit is concerned, it is used to indicate
     support of Opaque LSAs, described in RFC2370. 

    --
Alex

    > Hi,
>
>  I am a little bit confused by the options field
>  description in draft-ietf-ospf-lls-00.txt.
>  section 2.1 of draft-ietf-ospf-lls-00.txt introduces a
>  new bit "L" and it has a value of 0x10.
>
>  Figure 2 of section 2.1
>  +---+---+---+---+---+---+---+---+
>  | * | O |DC | L |N/P|MC | E | * |
>  +---+---+---+---+---+---+---+---+
>
>
>  A.2 of RFC2328 defines OSPF options field as below.
>  +---+---+---+---+---+---+---+---+
>  | * | * |DC |EA |N/P|MC | E | * |
>  +---+---+---+---+---+---+---+---+
>
>
>
>  Why does L bit replace EA bit as depicted in Fig.
>  2 of section 2.1?
>  If EA bit is no longer needed, why?
>  What is that 'O' bit in Fig. 2 of section 2.1?
>
>
>
>  Thanks,
>  Kathy Y. Lee
>
>
>  __________________________________________________
>  Do You Yahoo!?
>  Yahoo! Auctions - buy the things you want at great prices
>  http://auctions.yahoo.com/