draft-ietf-ospf-transport-instance-02.txt   draft-ietf-ospf-transport-instance-03.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 6, 2010 S. Mirtorabi Expires: April 8, 2010 S. Mirtorabi
Cisco Systems Cisco Systems
October 3, 2009 October 5, 2009
OSPF Transport Instance Extensions OSPF Transport Instance Extensions
draft-ietf-ospf-transport-instance-02.txt draft-ietf-ospf-transport-instance-03.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 April 6, 2010. This Internet-Draft will expire on April 8, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 39 skipping to change at page 2, line 39
2.4. Network Prioritization . . . . . . . . . . . . . . . . . . 5 2.4. Network Prioritization . . . . . . . . . . . . . . . . . . 5
2.5. OSPF Transport Instance Omission of Routing Calculation . 5 2.5. OSPF Transport Instance Omission of Routing Calculation . 5
2.6. Non-routing Instance Separation . . . . . . . . . . . . . 6 2.6. Non-routing Instance Separation . . . . . . . . . . . . . 6
2.7. Non-Routing Sparse Topologies . . . . . . . . . . . . . . 6 2.7. Non-Routing Sparse Topologies . . . . . . . . . . . . . . 6
2.7.1. Remote OSPF Neighbor . . . . . . . . . . . . . . . . . 7 2.7.1. Remote OSPF Neighbor . . . . . . . . . . . . . . . . . 7
3. OSPF Transport Instance Information Encoding . . . . . . . . . 8 3. OSPF Transport Instance Information Encoding . . . . . . . . . 8
3.1. OSPFv2 Transport Instance Information Encoding . . . . . . 8 3.1. OSPFv2 Transport Instance Information Encoding . . . . . . 8
3.2. OSPFv3 Transport Instance Information Encoding . . . . . . 8 3.2. OSPFv3 Transport Instance Information Encoding . . . . . . 8
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Normative References . . . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1. Normative References . . . . . . . . . . . . . . . . . . . 11
6.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 12 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
OSPFv2 [OSPFV2] and OSPFv3 [OSPFV3] include a reliable flooding OSPFv2 [OSPFV2] and OSPFv3 [OSPFV3] include a reliable flooding
mechanism to disseminate routing topology and Traffic Engineering mechanism to disseminate routing topology and Traffic Engineering
(TE) information within a routing domain. Given the effectiveness of (TE) information within a routing domain. Given the effectiveness of
these mechanisms, it is convenient to envision using the same these mechanisms, it is convenient to envision using the same
mechanism for dissemination of other types of information within the mechanism for dissemination of other types of information within the
skipping to change at page 11, line 5 skipping to change at page 11, line 5
4. Security Considerations 4. Security Considerations
The security considerations for the Transport Instance will not be The security considerations for the Transport Instance will not be
different for those for OSPFv2 [OSPFV2] and OSPFv3 [OSPFV3]. different for those for OSPFv2 [OSPFV2] and OSPFv3 [OSPFV3].
5. IANA Considerations 5. IANA Considerations
No new IANA assignments are required for this draft. No new IANA assignments are required for this draft.
6. Normative References 6. References
6.1. Normative References
[MULTI-INST] [MULTI-INST]
Lindem, A., Mirtorabi, S., and A. Roy, "OSPF Multi- Lindem, A., Mirtorabi, S., and A. Roy, "OSPF Multi-
Instance Extensions", Instance Extensions",
draft-acee-ospf-multi-instance-02.txt (work in progress). draft-acee-ospf-multi-instance-01.txt (work in progress).
[OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The [OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The
OSPF Opaque LSA Option", RFC 5250, July 2008. OSPF Opaque LSA Option", RFC 5250, July 2008.
[OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, July 2008. for IPv6", RFC 5340, July 2008.
[RFC-KEYWORDS] [RFC-KEYWORDS]
Bradner, S., "Key words for use in RFC's to Indicate Bradner, S., "Key words for use in RFC's 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
[ISIS-GEN-APP]
Ginsberg, L., Previdi, S., and M. Shand, "Advertising
Generic Information in IS-IS",
draft-ietf-isis-genapp-01.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
a separate instance to advertise non-routing information in an IGP
was first introduced in "Advertising Generic Information in IS-IS"
[ISIS-GEN-APP].
Thanks to Jonathan Sadler for comments on the document. Thanks to Jonathan Sadler for comments on the document.
Authors' Addresses Authors' Addresses
Acee Lindem Acee Lindem
Ericsson Ericsson
102 Carric Bend Court 102 Carric Bend Court
Cary, NC 27519 Cary, NC 27519
USA USA
 End of changes. 9 change blocks. 
7 lines changed or deleted 23 lines changed or added

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