draft-ietf-ospf-rfc2370bis-01.txt   draft-ietf-ospf-rfc2370bis-02.txt 
Internet Draft Lou Berger (LabN) Internet Draft Lou Berger (LabN)
Obsoletes: 2370 Igor Bryskin (Adva) Obsoletes: 2370 Igor Bryskin (Adva)
Category: Standards Track Alex Zinin (Alcatel) Category: Standards Track Alex Zinin (Alcatel)
Expiration Date: December 2007 Original Author: Expiration Date: September 10, 2008 Original Author:
Rob Coltun (Acoustra Productions) Rob Coltun (Acoustra Productions)
March 10, 2008
The OSPF Opaque LSA Option The OSPF Opaque LSA Option
draft-ietf-ospf-rfc2370bis-01.txt draft-ietf-ospf-rfc2370bis-02.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 34 skipping to change at page 1, line 37
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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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 September 10, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines enhancements to the OSPF protocol to support a This document defines enhancements to the OSPF protocol to support a
new class of link-state advertisements (LSA) called Opaque LSAs. new class of link-state advertisements (LSA) called Opaque LSAs.
Opaque LSAs provide a generalized mechanism to allow for the future Opaque LSAs provide a generalized mechanism to allow for the future
extensibility of OSPF. Opaque LSAs consist of a standard LSA header extensibility of OSPF. Opaque LSAs consist of a standard LSA header
followed by application-specific information. The information field followed by application-specific information. The information field
may be used directly by OSPF or by other applications. Standard OSPF may be used directly by OSPF or by other applications. Standard OSPF
link-state database flooding mechanisms are used to distribute Opaque link-state database flooding mechanisms are used to distribute Opaque
LSAs to all or some limited portion of the OSPF topology. LSAs to all or some limited portion of the OSPF topology.
This document replaces RFC 2370 and adds to it a mechanism to enable This document replaces RFC 2370 and adds to it a mechanism to enable
an OSPF router to validate AS-scope opaque LSAs originated outside of an OSPF router to validate AS-scope opaque LSAs originated outside of
the router's OSPF area. the router's OSPF area.
Contents Table of Contents
1 Conventions used in this document ......................... 3 1 Conventions used in this document ......................... 3
2 Introduction .............................................. 3 2 Introduction .............................................. 3
2.1 Organization Of This Document ............................. 3 2.1 Organization Of This Document ............................. 3
2.2 Acknowledgments ........................................... 4 2.2 Acknowledgments ........................................... 4
3 The Opaque LSA ............................................ 4 3 The Opaque LSA ............................................ 4
3.1 Flooding Opaque LSAs ...................................... 5 3.1 Flooding Opaque LSAs ...................................... 5
3.2 Modifications To The Neighbor State Machine ............... 6 3.2 Modifications To The Neighbor State Machine ............... 6
4 Protocol Data Structures .................................. 7 4 Protocol Data Structures .................................. 7
4.1 Additions To The OSPF Neighbor Structure .................. 8 4.1 Additions To The OSPF Neighbor Structure .................. 8
skipping to change at page 16, line 7 skipping to change at page 16, line 7
Syntax Of The Opaque LSA's Link-State ID Syntax Of The Opaque LSA's Link-State ID
The link-state ID of the Opaque LSA is divided into an Opaque Type The link-state ID of the Opaque LSA is divided into an Opaque Type
field (the first 8 bits) and an Opaque ID (the remaining 24 bits). field (the first 8 bits) and an Opaque ID (the remaining 24 bits).
See section 7 of this document for a description of Opaque type See section 7 of this document for a description of Opaque type
allocation and assignment. allocation and assignment.
13. Full Copyright Statement 13. Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
14. Intellectual Property 14. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed
pertain to the implementation or use of the technology described in to pertain to the implementation or use of the technology
this document or the extent to which any license under such rights described in this document or the extent to which any license
might or might not be available; nor does it represent that it has under such rights might or might not be available; nor does it
made any independent effort to identify any such rights. Information represent that it has made any independent effort to identify any
on the procedures with respect to rights in RFC documents can be such rights. Information on the procedures with respect to rights
found in BCP 78 and BCP 79. in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use
such proprietary rights by implementers or users of this of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository
http://www.ietf.org/ipr. at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention
copyrights, patents or patent applications, or other proprietary any copyrights, patents or patent applications, or other
rights that may cover technology that may be required to implement proprietary rights that may cover technology that may be required
this standard. Please address the information to the IETF at ietf- to implement this standard. Please address the information to the
ipr@ietf.org. IETF at ietf-ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is provided by the IETF Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA). Administrative Support Activity (IASA).
Generated on: Mon Jun 4 13:52:53 EDT 2007 Generated on: Mon Mar 10 10:35:48 EDT 2008
 End of changes. 10 change blocks. 
20 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/