draft-ietf-ospf-lls-02.txt   draft-ietf-ospf-lls-03.txt 
Network Working Group A. Zinin Network Working Group A. Zinin
Internet-Draft Alcatel Internet-Draft Alcatel
Intended status: Standards Track B. Friedman Intended status: Standards Track A. Roy
Expires: July 13, 2007 A. Roy Expires: January 31, 2008 L. Nguyen
L. Nguyen
D. Young
Cisco Systems Cisco Systems
January 9, 2007 B. Friedman
Redback Networks
D. Yeung
August 2007
OSPF Link-local Signaling OSPF Link-local Signaling
draft-ietf-ospf-lls-02.txt draft-ietf-ospf-lls-03.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 39
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 July 13, 2007. This Internet-Draft will expire on January 31, 2008.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
OSPF is a link-state intra-domain routing protocol. OSPF routers OSPF is a link-state intra-domain routing protocol. OSPF routers
exchange information on a link using packets that follow a well- exchange information on a link using packets that follow a well-
defined fixed format. The format is not flexible enough to enable defined fixed format. The format is not flexible enough to enable
new features which need to exchange arbitrary data. This memo new features which need to exchange arbitrary data. This memo
describes a backward-compatible technique to perform link-local describes a backward-compatible technique to perform link-local
signaling, i.e., exchange arbitrary data on a link. signaling, i.e., exchange arbitrary data on a link.
skipping to change at page 3, line 25 skipping to change at page 3, line 25
OSPFv2 or OSPFv3 will be used when the text is protocol specific. OSPFv2 or OSPFv3 will be used when the text is protocol specific.
One potential way of solving this task could be introducing a new One potential way of solving this task could be introducing a new
packet type. However, that would mean introducing extra packets on packet type. However, that would mean introducing extra packets on
the network which may not be desirable and may cause backward the network which may not be desirable and may cause backward
compatibility issues. This document describes how to exchange data compatibility issues. This document describes how to exchange data
using standard OSPF packet types. using standard OSPF packet types.
1.1. Conventions Used In This Document 1.1. Conventions Used In This Document
In this document, the key words "MUST", "MUST NOT", "REQUIRED", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
and "OPTIONAL" are to be interpreted as described in RFC2119 [KEY]. document are to be interpreted as described in RFC 2119 [KEY].
2. Proposed solution 2. Proposed solution
To perform link-local signaling (LLS), OSPF routers add a special To perform link-local signaling (LLS), OSPF routers add a special
data block at the end of OSPF packets or right after the data block at the end of OSPF packets or right after the
authentication data block when cryptographic authentication is used. authentication data block when cryptographic authentication is used.
The length of the LLS block is not included into the length of OSPF The length of the LLS block is not included into the length of OSPF
packet, but is included in the IPv4/IPv6 packet length. Figure 1 packet, but is included in the IPv4/IPv6 packet length. Figure 1
illustrates how the LLS data block is attached. illustrates how the LLS data block is attached.
skipping to change at page 14, line 14 skipping to change at page 14, line 14
Authors' Addresses Authors' Addresses
Alex Zinin Alex Zinin
Alcatel Alcatel
Sunnyvale Sunnyvale
USA USA
Email: zinin@psg.com Email: zinin@psg.com
Barry Friedman
Cisco Systems
170 West Tasman Drive
San Jose, CA 95134
USA
Email: friedman@cisco.com
Abhay Roy Abhay Roy
Cisco Systems Cisco Systems
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: akr@cisco.com Email: akr@cisco.com
Liem Nguyen Liem Nguyen
Cisco Systems Cisco Systems
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: lhnguyen@cisco.com Email: lhnguyen@cisco.com
Derek Young Barry Friedman
Cisco Systems 300 Holger Way
170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: myeung@cisco.com Email: friedman@redback.com
Derek Young
Email: derekmyeung@yahoo.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2007). Copyright (C) The IETF Trust (2007).
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 AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
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.
Intellectual Property 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 to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 11 change blocks. 
28 lines changed or deleted 23 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/