| < draft-ietf-ospf-ospfv3-traffic-12.txt | draft-ietf-ospf-ospfv3-traffic-13.txt > | |||
|---|---|---|---|---|
| Network Working Group K. Ishiguro | Network Working Group K. Ishiguro | |||
| Internet-Draft V. Manral | Internet-Draft V. Manral | |||
| Intended status: Standards Track IP Infusion, Inc | Intended status: Standards Track IP Infusion, Inc | |||
| Expires: December 9, 2008 A. Davey | Expires: December 14, 2008 A. Davey | |||
| Data Connection Limited | Data Connection Limited | |||
| A. Lindem (Editor) | A. Lindem (Editor) | |||
| Redback Networks | Redback Networks | |||
| June 7, 2008 | June 12, 2008 | |||
| Traffic Engineering Extensions to OSPF version 3 | Traffic Engineering Extensions to OSPF version 3 | |||
| draft-ietf-ospf-ospfv3-traffic-12.txt | draft-ietf-ospf-ospfv3-traffic-13.txt | |||
| Status of this Memo | Status of this Memo | |||
| By submitting this Internet-Draft, each author represents that any | By submitting this Internet-Draft, each author represents that any | |||
| applicable patent or other IPR claims of which he or she is aware | applicable patent or other IPR claims of which he or she is aware | |||
| have been or will be disclosed, and any of which he or she becomes | have been or will be disclosed, and any of which he or she becomes | |||
| aware will be disclosed, in accordance with Section 6 of BCP 79. | aware will be disclosed, in accordance with Section 6 of BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| skipping to change at page 1, line 38 ¶ | skipping to change at page 1, line 38 ¶ | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| This Internet-Draft will expire on December 9, 2008. | This Internet-Draft will expire on December 14, 2008. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (C) The IETF Trust (2008). | Copyright (C) The IETF Trust (2008). | |||
| Abstract | Abstract | |||
| This document describes extensions to OSPFv3 to support intra-area | This document describes extensions to OSPFv3 to support intra-area | |||
| Traffic Engineering (TE). This document extends OSPFv2 TE to handle | Traffic Engineering (TE). This document extends OSPFv2 TE to handle | |||
| IPv6 networks. A new TLV and several new sub-TLVs are defined to | IPv6 networks. A new TLV and several new sub-TLVs are defined to | |||
| skipping to change at page 13, line 5 ¶ | skipping to change at page 12, line 15 ¶ | |||
| 6. Management Considerations | 6. Management Considerations | |||
| The typical management interface for routers running the new | The typical management interface for routers running the new | |||
| extensions to OSPF for intra-area Traffic Engineering is SNMP-based. | extensions to OSPF for intra-area Traffic Engineering is SNMP-based. | |||
| The extra management objects for configuration operations and | The extra management objects for configuration operations and | |||
| statistics are defined in [OSPFV3-MIB] and an implementation of the | statistics are defined in [OSPFV3-MIB] and an implementation of the | |||
| extensions defined in this document SHOULD provide for the | extensions defined in this document SHOULD provide for the | |||
| appropriate hooks or instrumentation that allow for the MIB objects | appropriate hooks or instrumentation that allow for the MIB objects | |||
| to be implemented. | to be implemented. | |||
| The following MIB variables have been added to the OSPFv3 MIB in | ||||
| support of TE: | ||||
| ospfv3AreaTEEnabled | ||||
| This TruthValue MIB variable in the ospf3AreaEntry table entry | ||||
| indicates whether or not OSPFv3 TE advertisement for OSPFv3 | ||||
| interfaces is enabled for the corresponding area. The default | ||||
| value is FALSE. | ||||
| ospfv3IfTEDisabled | ||||
| This TruthValue MIB variable in the ospf3IfEntry table entry | ||||
| indicates whether or not OSPFv3 TE advertisement for OSPFv3 for | ||||
| the corresponding interface is disabled. This MIB variable is | ||||
| only applicable if ospfv3AreaTEEnabled is TRUE for the interface's | ||||
| area. The default value is FALSE. | ||||
| 7. IANA Considerations | 7. IANA Considerations | |||
| The following IANA assignments are to be made from existing | The following IANA assignments are to be made from existing | |||
| registries: | registries: | |||
| 1. The OSPFv3 LSA type function code 10 needs to be assigned to the | 1. The OSPFv3 LSA type function code 10 needs to be assigned to the | |||
| OSPFv3 Intra-Area-TE-LSA. | OSPFv3 Intra-Area-TE-LSA. | |||
| 2. The Router IPv6 Address TLV type 3 needs to be assigned from the | 2. The Router IPv6 Address TLV type 3 needs to be assigned from the | |||
| existing registry for OSPF TE TLVs. | existing registry for OSPF TE TLVs. | |||
| End of changes. 5 change blocks. | ||||
| 4 lines changed or deleted | 20 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||