draft-ietf-forces-protocol-07.txt   draft-ietf-forces-protocol-08.txt 
Network Working Group A. Doria (Ed.) Network Working Group A. Doria (Ed.)
Internet-Draft ETRI Internet-Draft ETRI
Expires: September 6, 2006 R. Haas (Ed.) Expires: September 24, 2006 R. Haas (Ed.)
IBM IBM
J. Hadi Salim (Ed.) J. Hadi Salim (Ed.)
Znyx Znyx
H. Khosravi (Ed.) H. Khosravi (Ed.)
Intel Intel
W. M. Wang (Ed.) W. M. Wang (Ed.)
Zhejiang Gongshang University Zhejiang Gongshang University
March 23, 2006
March 5, 2006
ForCES Protocol Specification ForCES Protocol Specification
draft-ietf-forces-protocol-07.txt draft-ietf-forces-protocol-08.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 42 skipping to change at page 1, line 41
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 September 6, 2006. This Internet-Draft will expire on September 24, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document specifies the Forwarding and Control Element Separation This document specifies the Forwarding and Control Element Separation
(ForCES) protocol. ForCES protocol is used for communications (ForCES) protocol. ForCES protocol is used for communications
between Control Elements(CEs) and Forwarding Elements (FEs) in a between Control Elements(CEs) and Forwarding Elements (FEs) in a
skipping to change at page 3, line 34 skipping to change at page 3, line 34
5.1. TML Parameterization . . . . . . . . . . . . . . . . . . 26 5.1. TML Parameterization . . . . . . . . . . . . . . . . . . 26
6. Message encapsulation . . . . . . . . . . . . . . . . . . . . 27 6. Message encapsulation . . . . . . . . . . . . . . . . . . . . 27
6.1. Common Header . . . . . . . . . . . . . . . . . . . . . . 27 6.1. Common Header . . . . . . . . . . . . . . . . . . . . . . 27
6.2. Type Length Value(TLV) Structuring . . . . . . . . . . . 32 6.2. Type Length Value(TLV) Structuring . . . . . . . . . . . 32
6.2.1. Nested TLVs . . . . . . . . . . . . . . . . . . . . . 32 6.2.1. Nested TLVs . . . . . . . . . . . . . . . . . . . . . 32
6.2.2. Scope of the T in TLV . . . . . . . . . . . . . . . . 32 6.2.2. Scope of the T in TLV . . . . . . . . . . . . . . . . 32
6.3. ILV . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.3. ILV . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7. Protocol Construction . . . . . . . . . . . . . . . . . . . . 34 7. Protocol Construction . . . . . . . . . . . . . . . . . . . . 34
7.1. Protocol Grammar . . . . . . . . . . . . . . . . . . . . 34 7.1. Protocol Grammar . . . . . . . . . . . . . . . . . . . . 34
7.1.1. Protocol BNF . . . . . . . . . . . . . . . . . . . . 34 7.1.1. Protocol BNF . . . . . . . . . . . . . . . . . . . . 34
7.1.2. Protocol Visualization . . . . . . . . . . . . . . . 42 7.1.2. Protocol Visualization . . . . . . . . . . . . . . . 43
7.2. Core ForCES LFBs . . . . . . . . . . . . . . . . . . . . 45 7.2. Core ForCES LFBs . . . . . . . . . . . . . . . . . . . . 46
7.2.1. FE Protocol LFB . . . . . . . . . . . . . . . . . . . 46 7.2.1. FE Protocol LFB . . . . . . . . . . . . . . . . . . . 47
7.2.2. FE Object LFB . . . . . . . . . . . . . . . . . . . . 49 7.2.2. FE Object LFB . . . . . . . . . . . . . . . . . . . . 50
7.3. Semantics of message Direction . . . . . . . . . . . . . 49 7.3. Semantics of message Direction . . . . . . . . . . . . . 50
7.4. Association Messages . . . . . . . . . . . . . . . . . . 49 7.4. Association Messages . . . . . . . . . . . . . . . . . . 50
7.4.1. Association Setup Message . . . . . . . . . . . . . . 49 7.4.1. Association Setup Message . . . . . . . . . . . . . . 50
7.4.2. Association Setup Response Message . . . . . . . . . 51 7.4.2. Association Setup Response Message . . . . . . . . . 52
7.4.3. Association Teardown Message . . . . . . . . . . . . 52 7.4.3. Association Teardown Message . . . . . . . . . . . . 53
7.5. Configuration Messages . . . . . . . . . . . . . . . . . 53 7.5. Configuration Messages . . . . . . . . . . . . . . . . . 54
7.5.1. Config Message . . . . . . . . . . . . . . . . . . . 53 7.5.1. Config Message . . . . . . . . . . . . . . . . . . . 54
7.5.2. Config Response Message . . . . . . . . . . . . . . . 55 7.5.2. Config Response Message . . . . . . . . . . . . . . . 56
7.6. Query Messages . . . . . . . . . . . . . . . . . . . . . 56 7.6. Query Messages . . . . . . . . . . . . . . . . . . . . . 57
7.6.1. Query Message . . . . . . . . . . . . . . . . . . . . 57 7.6.1. Query Message . . . . . . . . . . . . . . . . . . . . 58
7.6.2. Query Response Message . . . . . . . . . . . . . . . 58 7.6.2. Query Response Message . . . . . . . . . . . . . . . 59
7.7. Event Notification Message . . . . . . . . . . . . . . . 59 7.7. Event Notification Message . . . . . . . . . . . . . . . 60
7.8. Packet Redirect Message . . . . . . . . . . . . . . . . . 61 7.8. Packet Redirect Message . . . . . . . . . . . . . . . . . 62
7.9. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 64 7.9. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 65
7.10. Operation Summary . . . . . . . . . . . . . . . . . . . . 65 7.10. Operation Summary . . . . . . . . . . . . . . . . . . . . 66
8. Protocol Scenarios . . . . . . . . . . . . . . . . . . . . . 68 8. Protocol Scenarios . . . . . . . . . . . . . . . . . . . . . 69
8.1. Association Setup state . . . . . . . . . . . . . . . . . 68 8.1. Association Setup state . . . . . . . . . . . . . . . . . 69
8.2. Association Established state or Steady State . . . . . . 69 8.2. Association Established state or Steady State . . . . . . 70
9. High Availability Support . . . . . . . . . . . . . . . . . . 72 9. High Availability Support . . . . . . . . . . . . . . . . . . 73
9.1. Responsibilities for HA . . . . . . . . . . . . . . . . . 74 9.1. Responsibilities for HA . . . . . . . . . . . . . . . . . 75
10. Security Considerations . . . . . . . . . . . . . . . . . . . 76 10. Security Considerations . . . . . . . . . . . . . . . . . . . 77
10.1. No Security . . . . . . . . . . . . . . . . . . . . . . . 76 10.1. No Security . . . . . . . . . . . . . . . . . . . . . . . 77
10.1.1. Endpoint Authentication . . . . . . . . . . . . . . . 76 10.1.1. Endpoint Authentication . . . . . . . . . . . . . . . 77
10.1.2. Message authentication . . . . . . . . . . . . . . . 77 10.1.2. Message authentication . . . . . . . . . . . . . . . 78
10.2. ForCES PL and TML security service . . . . . . . . . . . 77 10.2. ForCES PL and TML security service . . . . . . . . . . . 78
10.2.1. Endpoint authentication service . . . . . . . . . . . 77 10.2.1. Endpoint authentication service . . . . . . . . . . . 78
10.2.2. Message authentication service . . . . . . . . . . . 77 10.2.2. Message authentication service . . . . . . . . . . . 78
10.2.3. Confidentiality service . . . . . . . . . . . . . . . 78 10.2.3. Confidentiality service . . . . . . . . . . . . . . . 79
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 79 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 80
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 80 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.1. Normative References . . . . . . . . . . . . . . . . . . 80 12.1. Normative References . . . . . . . . . . . . . . . . . . 81
12.2. Informational References . . . . . . . . . . . . . . . . 80 12.2. Informational References . . . . . . . . . . . . . . . . 81
Appendix A. IANA Considerations . . . . . . . . . . . . . . . . 81 Appendix A. IANA Considerations . . . . . . . . . . . . . . . . 82
A.1. Message Type Name Space . . . . . . . . . . . . . . . . . 81 A.1. Message Type Name Space . . . . . . . . . . . . . . . . . 82
A.2. Operation Type . . . . . . . . . . . . . . . . . . . . . 82 A.2. Operation Type . . . . . . . . . . . . . . . . . . . . . 83
A.3. Header Flags . . . . . . . . . . . . . . . . . . . . . . 82 A.3. Header Flags . . . . . . . . . . . . . . . . . . . . . . 83
A.4. TLV Type Name Space . . . . . . . . . . . . . . . . . . . 83 A.4. TLV Type Name Space . . . . . . . . . . . . . . . . . . . 84
A.5. LFB Class Id Name Space . . . . . . . . . . . . . . . . . 83 A.5. Result-TLV Result Values . . . . . . . . . . . . . . . . 84
A.6. Association Setup Response . . . . . . . . . . . . . . . 84 A.6. LFB Class Id Name Space . . . . . . . . . . . . . . . . . 85
A.7. Association Teardown Message . . . . . . . . . . . . . . 84 A.7. Association Setup Response . . . . . . . . . . . . . . . 86
A.8. Configuration Request Result . . . . . . . . . . . . . . 85 A.8. Association Teardown Message . . . . . . . . . . . . . . 86
Appendix B. ForCES Protocol LFB schema . . . . . . . . . . . . . 86 A.9. Configuration Request Result . . . . . . . . . . . . . . 87
B.1. Capabilities . . . . . . . . . . . . . . . . . . . . . . 91 Appendix B. ForCES Protocol LFB schema . . . . . . . . . . . . . 88
B.2. Attributes . . . . . . . . . . . . . . . . . . . . . . . 91 B.1. Capabilities . . . . . . . . . . . . . . . . . . . . . . 93
Appendix C. Data Encoding Examples . . . . . . . . . . . . . . . 92 B.2. Attributes . . . . . . . . . . . . . . . . . . . . . . . 93
Appendix D. Use Cases . . . . . . . . . . . . . . . . . . . . . 96 Appendix C. Data Encoding Examples . . . . . . . . . . . . . . . 94
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 112 Appendix D. Use Cases . . . . . . . . . . . . . . . . . . . . . 98
Intellectual Property and Copyright Statements . . . . . . . . . 114 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 114
Intellectual Property and Copyright Statements . . . . . . . . . 116
1. Terminology and Conventions 1. Terminology and Conventions
The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT,
RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted
as described in BCP 14, RFC 2119 [RFC2119]. as described in BCP 14, RFC 2119 [RFC2119].
2. Introduction 2. Introduction
Forwarding and Control Element Separation (ForCES) defines an Forwarding and Control Element Separation (ForCES) defines an
skipping to change at page 41, line 4 skipping to change at page 41, line 4
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = RESULT | Length | | Type = RESULT | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result Value | Reserved | | Result Value | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 15: Result TLV Figure 15: Result TLV
The defined Result Values are The defined Result Values are
0 = success 0x00 = Success
1 = no such object 0x01 = Unspecified error with header.
2 = permission denied (e.g., trying to configure an attribute that 0x02 = Header length field does not match actual packet length.
is read- only)
3 = invalid value (the encoded data could not validly be stored in 0x03 = Unresolvable mismatch in versions.
the field)
4 = invalid array creation (when the subscript in an array create is 0x04 = Destination PID is invalid for the message receiver.
not allowed)
255 = unspecified error (for when the FE can not decide what went 0x05 = LFB Class ID is not known by receiver.
wrong)
0x06 = LFB Class ID is known by receiver but not currently in use.
0x07 = LFB Class ID is known but the specified instance of that
class does not exist.
0x08 = The specified path is impossible.
0x09 = The specified path is possible but the element does not exist
(e.g., attempt to modify a table row that has not been created).
0x0A = The specified object exists but it cannot exist for the
operation to succeed (e.g., attempt to add an existing LFB
instance or array subscript).
0x0B = The specified object does not exist but it must exist for the
operation to succeed (e.g., attempt to delete an non-existing
LFB instance or array subscript).
0x0C = Attempt to modify a read-only value.
0x0D = Attempt to create an array with an unallowed subscript.
0x0E = Attempt to set a parameter to a value outside of its
allowable range.
0x0D = Attempt to write contents larger than the target object space
(i.e., exceeding a buffer).
0x10 = Any other error with data parameters.
0x11 = Message type is not acceptable.
0x12 = Message flags are not acceptable for the given message type.
0x13 = A TLV is not acceptable for the given message type.
0x14 = Unspecified error while handling an event.
0x15 = Attempt to perform a valid ForCES operation that is
unsupported by the message receiver.
0x16 = A memory error occurred while processing a message (no error
detected in the message itself)
0x17 = An unspecified error occured while processing a message (no
error detected in the message itself).
others = Reserved others = Reserved
0xFF = unspecified error (for when the FE can not decide what went
wrong)
7.1.1.1.8. DATA TLV 7.1.1.1.8. DATA TLV
A FULLDATA TLV has "T"= FULLDATA, and a 16bit Length followed by the A FULLDATA TLV has "T"= FULLDATA, and a 16bit Length followed by the
data value/contents. Likewise, a SPARSEDATA TLV has "T" = data value/contents. Likewise, a SPARSEDATA TLV has "T" =
SPARSEDATA, a 16bit Length followed by the data value/contents. In SPARSEDATA, a 16bit Length followed by the data value/contents. In
the case of the SPARSEDATA each element in the Value part of the TLV the case of the SPARSEDATA each element in the Value part of the TLV
will be further encapsulated in an ILV. Rules: will be further encapsulated in an ILV. Rules:
1. Both ILVs and TLVs MUST 32 bit aligned. Any padding bits used 1. Both ILVs and TLVs MUST 32 bit aligned. Any padding bits used
for the alignment MUST be zero on transmission and MUST be for the alignment MUST be zero on transmission and MUST be
skipping to change at page 80, line 5 skipping to change at page 80, line 18
ForCES Working Group and especially the following: Furquan Ansari, ForCES Working Group and especially the following: Furquan Ansari,
Alex Audu, Steven Blake, Shuchi Chawla Alan DeKok, Ellen M. Alex Audu, Steven Blake, Shuchi Chawla Alan DeKok, Ellen M.
Deleganes, Xiaoyi Guo, Yunfei Guo, Evangelos Haleplidis, Joel M. Deleganes, Xiaoyi Guo, Yunfei Guo, Evangelos Haleplidis, Joel M.
Halpern (who should probably be listed among the authors), Zsolt Halpern (who should probably be listed among the authors), Zsolt
Haraszti, Fenggen Jia, John C. Lin, Alistair Munro, Jeff Pickering, Haraszti, Fenggen Jia, John C. Lin, Alistair Munro, Jeff Pickering,
T. Sridhlar, Guangming Wang, Chaoping Wu, and Lily L. Yang, for their T. Sridhlar, Guangming Wang, Chaoping Wu, and Lily L. Yang, for their
contributions. We would also like to thank David Putzolu, and contributions. We would also like to thank David Putzolu, and
Patrick Droz for their comments and suggestions on the protocol and Patrick Droz for their comments and suggestions on the protocol and
for their infinite patience. for their infinite patience.
The editors have used the xml2rfc [RFC2629] tools in creating this
document and are very grateful for the existence and quality of these
tools.
12. References 12. References
12.1. Normative References 12.1. Normative References
[FE-MODEL] [FE-MODEL]
Yang, L., Halpern, J., Gopal, R., DeKok, A., Haraszti, Z., Yang, L., Halpern, J., Gopal, R., DeKok, A., Haraszti, Z.,
and S. Blake, "ForCES Forwarding Element Model", and S. Blake, "ForCES Forwarding Element Model",
Feb. 2005. Feb. 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999.
[RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation [RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation
of IP Control and Forwarding", RFC 3654, November 2003. of IP Control and Forwarding", RFC 3654, November 2003.
[RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal, [RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal,
"Forwarding and Control Element Separation (ForCES) "Forwarding and Control Element Separation (ForCES)
Framework", RFC 3746, April 2004. Framework", RFC 3746, April 2004.
12.2. Informational References 12.2. Informational References
[2PCREF] Gray, J., "Notes on database operating systems. In [2PCREF] Gray, J., "Notes on database operating systems. In
Operating Systems: An Advanced Course. Lecture Notes in Operating Systems: An Advanced Course. Lecture Notes in
Computer Science, Vol. 60, pp. 394-481, Springer-Verlag", Computer Science, Vol. 60, pp. 394-481, Springer-Verlag",
1978. 1978.
[ACID] Haerder, T. and A. Reuter, "Principles of Transaction- [ACID] Haerder, T. and A. Reuter, "Principles of Transaction-
Orientated Database Recovery", 1983. Orientated Database Recovery", 1983.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999.
Appendix A. IANA Considerations Appendix A. IANA Considerations
Following the policies outlined in "Guidelines for Writing an IANA Following the policies outlined in "Guidelines for Writing an IANA
Considerations Section in RFCs" (RFC 2434 [RFC2434]), the following Considerations Section in RFCs" (RFC 2434 [RFC2434]), the following
name spaces are defined in ForCES. name spaces are defined in ForCES.
o Message Type Name Space Section 7.1.1 o Message Type Name Space Section 7.1.1
o Operation Type Name Space Section 7.1.1.1.6 o Operation Type Name Space Section 7.1.1.1.6
o Header Flags Section 6.1 o Header Flags Section 6.1
o TLV Type Section 7.1.1 o TLV Type Section 7.1.1
o TLV Result Values Section 7.1.1.1.7
o LFB Class ID Section 7.1.1.1.5 o LFB Class ID Section 7.1.1.1.5
o Result: Association Setup Response Section 7.4.2 o Result: Association Setup Response Section 7.4.2
o Reason: Association Teardown Message Section 7.4.3 o Reason: Association Teardown Message Section 7.4.3
o Configuration Request: Operation Result Section 7.5.1 o Configuration Request: Operation Result Section 7.5.1
A.1. Message Type Name Space A.1. Message Type Name Space
The Message Type is an 8 bit value. The following is the guideline The Message Type is an 8 bit value. The following is the guideline
for defining the Message Type namespace for defining the Message Type namespace
Message Types 0x00 - 0x0F Message Types 0x00 - 0x0F
Message Types in this range are part of the base ForCES Protocol. Message Types in this range are part of the base ForCES Protocol.
Message Types in this range are allocated through an IETF Message Types in this range are allocated through an IETF
consensus action. [RFC2434] consensus action. [RFC2434]
Values assigned by this specification: Values assigned by this specification:
0x00 ............... Reserved 0x00 Reserved
0x01 ............... AssociationSetup 0x01 AssociationSetup
0x02 ............... AssociationTeardown 0x02 AssociationTeardown
0x03 ............... Config 0x03 Config
0x04 ............... Query 0x04 Query
0x05 ............... EventNotification 0x05 EventNotification
0x06 ............... PacketRedirect 0x06 PacketRedirect
0x07 - 0x0E ........ Reserved 0x07 - 0x0E Reserved
0x0F ............... Hearbeat 0x0F Hearbeat
0x11 ............... AssociationSetupRepsonse 0x11 AssociationSetupRepsonse
0x12 ............... Reserved 0x12 Reserved
0x13 ............... ConfigRepsonse 0x13 ConfigRepsonse
0x14 ............... QueryResponse 0x14 QueryResponse
Message Types 0x20 - 0x7F Message Types 0x20 - 0x7F
Message Types in this range are Specification Required [RFC2434] Message Types in this range are Specification Required [RFC2434]
Message Types using this range must be documented in an RFC or Message Types using this range must be documented in an RFC or
other permanent and readily available references. other permanent and readily available references.
Message Types 0x80 - 0xFF Message Types 0x80 - 0xFF
Message Types in this range are reserved for vendor private Message Types in this range are reserved for vendor private
extensions and are the responsibility of individual vendors. IANA extensions and are the responsibility of individual vendors. IANA
management of this range of the Message Type Name Space is management of this range of the Message Type Name Space is
unnecessary. unnecessary.
skipping to change at page 83, line 37 skipping to change at page 84, line 37
TLV Type 0x0200-0x7FFF TLV Type 0x0200-0x7FFF
TLV Types using this range must be documented in an RFC or other TLV Types using this range must be documented in an RFC or other
permanent and readily available references. [RFC2434]. permanent and readily available references. [RFC2434].
TLV Type 0x8000-0xFFFF TLV Type 0x8000-0xFFFF
TLV Types in this range are reserved for vendor private extensions TLV Types in this range are reserved for vendor private extensions
and are the responsibility of individual vendors. IANA management and are the responsibility of individual vendors. IANA management
of this range of the TLV Type Name Space is unnecessary. of this range of the TLV Type Name Space is unnecessary.
A.5. LFB Class Id Name Space A.5. Result-TLV Result Values
The RESULT-TLV RTesult Value is an 8 bit value.
0x00 SUCCESS
0x01 INVALID_HEADER
0x02 LENGTH_MISMATCH
0x03 VERSION_MISMATCH
0x04 INVALID_DESTINATION_PID
0x05 LFB_UNKNOWN
0x06 LFB_NOT_FOUND
0x07 LFB_INSTANCE_ID_NOT_FOUND
0x08 INVALID_PATH
0x09 ELEMENT_DOES_NOT_EXIST
0x0A EXISTS
0x0B NOT_FOUND
0x0C READ_ONLY
0x0D INVALID_ARRAY_CREATION
0x0E VALUE_OUT_OF_RANGE
0x0F CONTENTS_TOO_LONG
0x10 INVALID_PARAMETERS
0x11 INVALID_MESSAGE_TYPE
0x12 INVALID_FLAGS
0x13 INVALID_TLV
0x14 EVENT_ERROR
0x15 NOT_SUPPORTED
0x16 MEMORY_ERROR
0x17 INTERNAL_ERROR
0x18-0xFE Reserved
0xFF UNSPECIFIED_ERROR
All values not assigned in this specification are designated as
Assignment by Expert review.
A.6. LFB Class Id Name Space
The LFB Class ID name space is 32 bits long. The following is the The LFB Class ID name space is 32 bits long. The following is the
guideline for managing the TLV Result Name Space. guideline for managing the LFB Class Id Name Space.
LFB Class ID 0x00000000-0x0000FFFF LFB Class ID 0x00000000-0x0000FFFF
LFB Class IDs in this range are allocated through an IETF LFB Class IDs in this range are allocated through an IETF
consensus process. [RFC2434]. consensus process. [RFC2434].
Values assigned by this specification: Values assigned by this specification:
0x00000000 Reserved 0x00000000 Reserved
0x00000001 FE Protocol LFB 0x00000001 FE Protocol LFB
0x00000002 FE Object LFB 0x00000002 FE Object LFB
LFB Class ID 0x00010000-0x7FFFFFFF LFB Class ID 0x00010000-0x7FFFFFFF
LFB Class IDs in this range are Specification Required [RFC2434] LFB Class IDs in this range are Specification Required [RFC2434]
LFB Class ID using this range must be documented in an RFC or LFB Class ID using this range must be documented in an RFC or
other permanent and readily available references. [RFC2434]. other permanent and readily available references. [RFC2434].
LFB Class Id 0x80000000-0xFFFFFFFFF LFB Class Id 0x80000000-0xFFFFFFFFF
LFB Class IDs in this range are reserved for vendor private LFB Class IDs in this range are reserved for vendor private
extensions and are the responsibility of individual vendors. IANA extensions and are the responsibility of individual vendors. IANA
management of this range of the LFB Class ID Space is unnecessary. management of this range of the LFB Class ID Space is unnecessary.
A.6. Association Setup Response A.7. Association Setup Response
The Association Setup Response name space is 16 bits long. The The Association Setup Response name space is 16 bits long. The
following is the guideline for managing the Association Setup following is the guideline for managing the Association Setup
Response Name Space. Response Name Space.
Association Setup Response 0x0000-0x00FF Association Setup Response 0x0000-0x00FF
Association Setup Responses in this range are allocated through an Association Setup Responses in this range are allocated through an
IETF consensus process. [RFC2434]. IETF consensus process. [RFC2434].
Values assigned by this specification: Values assigned by this specification:
skipping to change at page 84, line 42 skipping to change at page 86, line 42
Required [RFC2434] Values using this range must be documented in Required [RFC2434] Values using this range must be documented in
an RFC or other permanent and readily available references. an RFC or other permanent and readily available references.
[RFC2434]. [RFC2434].
Association Setup Response 0x80000000-0xFFFFFFFFF Association Setup Response 0x80000000-0xFFFFFFFFF
Association Setup Responses in this range are reserved for vendor Association Setup Responses in this range are reserved for vendor
private extensions and are the responsibility of individual private extensions and are the responsibility of individual
vendors. IANA management of this range of the Association Setup vendors. IANA management of this range of the Association Setup
Responses Name Space is unnecessary. Responses Name Space is unnecessary.
A.7. Association Teardown Message A.8. Association Teardown Message
The Association Teardown Message name space is 32 bits long. The The Association Teardown Message name space is 32 bits long. The
following is the guideline for managing the TLV Result Name Space. following is the guideline for managing the Association Teardown
Message Name Space.
Association Teardown Message 0x00000000-0x0000FFFF Association Teardown Message 0x00000000-0x0000FFFF
Association Teardown Messages in this range are allocated through Association Teardown Messages in this range are allocated through
an IETF consensus process. [RFC2434]. an IETF consensus process. [RFC2434].
Values assigned by this specification: Values assigned by this specification:
0x00000000 Normal - Teardown by Administrator 0x00000000 Normal - Teardown by Administrator
0x00000001 Error - Out of Memory 0x00000001 Error - Out of Memory
0x00000002 Error - Application Crash 0x00000002 Error - Application Crash
0x000000FF Error - Unspecified 0x000000FF Error - Unspecified
skipping to change at page 85, line 22 skipping to change at page 87, line 22
Required [RFC2434] Association Teardown Messages using this range Required [RFC2434] Association Teardown Messages using this range
must be documented in an RFC or other permanent and readily must be documented in an RFC or other permanent and readily
available references. [RFC2434]. available references. [RFC2434].
LFB Class Id 0x80000000-0xFFFFFFFFF LFB Class Id 0x80000000-0xFFFFFFFFF
Association Teardown Messages in this range are reserved for Association Teardown Messages in this range are reserved for
vendor private extensions and are the responsibility of individual vendor private extensions and are the responsibility of individual
vendors. IANA management of this range of the Association vendors. IANA management of this range of the Association
Teardown Message Name Space is unnecessary. Teardown Message Name Space is unnecessary.
A.8. Configuration Request Result A.9. Configuration Request Result
The Configuration Request name space is 32 bits long. The following The Configuration Request name space is 32 bits long. The following
is the guideline for managing the Configuration Request Name Space. is the guideline for managing the Configuration Request Name Space.
Configuration Request 0x0000-0x00FF Configuration Request 0x0000-0x00FF
Configuration Requests in this range are allocated through an IETF Configuration Requests in this range are allocated through an IETF
consensus process. [RFC2434]. consensus process. [RFC2434].
Values assigned by this specification: Values assigned by this specification:
0x0000 Success 0x0000 Success
 End of changes. 23 change blocks. 
89 lines changed or deleted 176 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/