OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Oliver Carter (ojcDATACONNECTION.COM)
Date: Wed Jan 30 2002 - 08:47:59 CST

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

    Hi All,

    I need a clarification to the GMPLS extensions to Traffic Engineering within
    OSPF as specified in
    draft-ietf-ccamp-ospf-gmpls-extensions-01.txt

    Section 5.5 of the draft states
    <-- SNIP -->
       When the Switching Capability field is PSC-1, PSC-2, PSC-3, or PSC-4,
       the specific information includes Interface MTU and Minimum LSP
       Bandwidth. The Interface MTU is encoded as a two octets integer. The
       Minimum LSP Bandwidth is is encoded in a 4 octets field in the IEEE
       floating point format. The units are bytes (not bits!) per second.
    <-- SNIP -->

    When constructing this information do we need any padding bytes? In other
    words should I build up this info as

    MTU|MTU|PAD|PAD|
    LSP|LSP|LSP|LSP|

    or

    MTU|MTU|LSP|LSP|
    LSP|LSP|PAD|PAD|

    I can't find anywhere it specifies which of these methods to use so if
    someone can tell me definitively how this should be done I would be very
    grateful.

    Regards

    Oli

    ----------------------------------------
    Oliver Carter
    DC-OSPF Development Team
    Data Connection Ltd.
    Telephone: +44 20 83661177
    Facsimile: +44 20 83631039
    www.dataconnection.com
    ----------------------------------------