Skip to main content

7. Changes from RFC 3036

Here is a list of changes from RFC 3036

1. Removed the Host Address FEC and references to it, since it is
   not used by any implementation.

2. Split the reference list into normative and informative
   references

3. Removed "MPLS using ATM VP Switching" from the list of
   normative references, and references to it.

 4. Removed reference to RFC 1700 and replaced it with a link to
   http://www.iana.org/assignments/address-family-numbers.

5. Removed reference to RFC 1771 and replaced it with a reference
   to RFC 4271.

6. Clarified the use of the F-bit.

7. Added option to allow split horizon when doing Ordered
   Control.

8. Clarified the processing of messages with the U-bit set during
   the session initialization procedures

9. Clarified the processing of the E-bit during session
   initialization procedures.

10. Added text explaining that the Shutdown message in the state transition diagram is implemented as a notification message with a Status TLV indicating a fatal error.

  1. Added case for TLV length too short in the specification for handling malformed TLVs.

  2. Explained the security threat posed by hello spoofing.

  3. Added reference to 4271 and 4278 and text for standards maturity variance with regards to the MD5 option.

  4. Added text from 3031 explaining the handling of implicit NULL label.

  5. Included the encoding of DLCIs to remove normative reference to 3034.

  6. Moved references to 3031, 3032, and 3034 to informative.

  7. In the section describing handling of unknown TLV, removed reference to inexistent section (errata in original document).

  8. Added text clarifying how to achieve interoperability when sending vendor-private TLVs and messages.

  9. In the "receive label request" procedures, if a loop is detected, changed the procedure to send a notification before aborting the rest of the processing.

  10. In "receive label release" procedures, clarified the behavior for merge-capable LSRs.

  11. In "receive label release" procedures, clarified the behavior for receipt of an unknown FEC.

  12. In note 4 of "Detect Change in FEC Next Hop", modified the text to reference the correct set of conditions for sending a label request procedure (typo in the original document).

  13. In the procedures for "LSR decides to no longer label switch a FEC", clarified the fact that the label must not be reused until a label release is received.

  14. In the routine "Prepare_Label_Mapping_Attributes", added a note regarding the treatment of unknown TLVs according to their U and F-bits.

  15. In the Address message processing procedures, clarified the behavior for the case where an LSR receives re-advertisement of an address previously advertised it, or withdrawal of an address from an LSR that has not previously advertised that address.

  16. In the routine "Receive Label Mapping", clarified the meaning of PrevAdvLabel when no label advertisement message has been sent previously.

  17. In the "Receive Label Mapping" procedures, if a loop is detected, modified the procedure to send a notification before aborting the rest of the processing.

  18. In the "Receive Label Mapping" procedures, corrected step LMp.10 to handle label mapping messages for additional (non- merged) LSPs for the FEC.

  19. In the "Receive Label Mapping" procedures, clarified behavior when receiving a duplicate label for the same FEC.

  20. In the routine "Receive Label Abort Request", clarified the behavior for non-merging LSRs.

  21. Added the following items to the section discussing areas for future study:

  o  extensions for communicating the maximum transmission unit
  o  basic peer discovery on NBMA media
  o  option of shutting down an adjacency
  o  mechanisms for securing Hello messages
  o  detection of a stateless fast control plane restart
  o  support of "end of LIB" message

  o  mechanisms for dealing with the case where different LSRs
     advertise the same address