draft-ietf-ospf-transport-instance-09.txt   draft-ietf-ospf-transport-instance-10.txt 
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track A. Roy Intended status: Standards Track A. Roy
Expires: April 4, 2013 S. Mirtorabi Expires: October 7, 2013 S. Mirtorabi
Cisco Systems Cisco Systems
October 1, 2012 April 5, 2013
OSPF Transport Instance Extensions OSPF Transport Instance Extensions
draft-ietf-ospf-transport-instance-09.txt draft-ietf-ospf-transport-instance-10.txt
Abstract Abstract
OSPFv2 and OSPFv3 include a reliable flooding mechanism to OSPFv2 and OSPFv3 include a reliable flooding mechanism to
disseminate routing topology and Traffic Engineering (TE) information disseminate routing topology and Traffic Engineering (TE) information
within a routing domain. Given the effectiveness of these within a routing domain. Given the effectiveness of these
mechanisms, it is convenient to envision using the same mechanism for mechanisms, it is convenient to envision using the same mechanism for
dissemination of other types of information within the domain. dissemination of other types of information within the domain.
However, burdening OSPF with this additional information will impact However, burdening OSPF with this additional information will impact
intra-domain routing convergence and possibly jeopardize the intra-domain routing convergence and possibly jeopardize the
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on April 4, 2013. This Internet-Draft will expire on October 7, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 12, line 32 skipping to change at page 12, line 32
Bradner, S., "Key words for use in RFCs to Indicate Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering
Extensions to OSPF", RFC 3630, September 2003. Extensions to OSPF", RFC 3630, September 2003.
6.2. Informative References 6.2. Informative References
[ISIS-GEN-APP] [ISIS-GEN-APP]
Ginsberg, L., Previdi, S., and M. Shand, "Advertising Ginsberg, L., Previdi, S., and M. Shand, "Advertising
Generic Information in IS-IS", Generic Information in IS-IS", RFC 6823, December 2012.
draft-ietf-isis-genapp-04.txt (work in progress).
Appendix A. Acknowledgments Appendix A. Acknowledgments
The RFC text was produced using Marshall Rose's xml2rfc tool. The RFC text was produced using Marshall Rose's xml2rfc tool.
Although very different mechanisms are utilized, the concept of using Although very different mechanisms are utilized, the concept of using
a separate instance to advertise non-routing information in an IGP a separate instance to advertise non-routing information in an IGP
was first introduced in "Advertising Generic Information in IS-IS" was first introduced in "Advertising Generic Information in IS-IS"
[ISIS-GEN-APP]. [ISIS-GEN-APP].
 End of changes. 6 change blocks. 
7 lines changed or deleted 6 lines changed or added

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