draft-ietf-rserpool-common-param-15.txt   draft-ietf-rserpool-common-param-16.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Experimental Q. Xie Intended status: Experimental Q. Xie
Expires: June 5, 2008 Motorola, Inc. Expires: September 28, 2008 Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
December 3, 2007 March 27, 2008
Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace
Redundancy Protocol (ENRP) Parameters Redundancy Protocol (ENRP) Parameters
draft-ietf-rserpool-common-param-15.txt draft-ietf-rserpool-common-param-16.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 40 skipping to change at page 1, line 40
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 June 5, 2008. This Internet-Draft will expire on September 28, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document details the parameters of the Aggregate Server Access This document details the parameters of the Aggregate Server Access
Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP)
protocols defined within the Reliable Server Pooling (RSerPool) protocols defined within the Reliable Server Pooling (RSerPool)
architecture. architecture.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 4
2. Parameters in General . . . . . . . . . . . . . . . . . . . . 4 2. Parameters in General . . . . . . . . . . . . . . . . . . . . 5
3. ENRP-ASAP Common Parameters . . . . . . . . . . . . . . . . . 5 3. ENRP-ASAP Common Parameters . . . . . . . . . . . . . . . . . 6
3.1. IPv4 Address Parameter . . . . . . . . . . . . . . . . . . 7 3.1. IPv4 Address Parameter . . . . . . . . . . . . . . . . . . 8
3.2. IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 7 3.2. IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 8
3.3. DCCP Transport Parameter . . . . . . . . . . . . . . . . . 7 3.3. DCCP Transport Parameter . . . . . . . . . . . . . . . . . 9
3.4. SCTP Transport Parameter . . . . . . . . . . . . . . . . . 8 3.4. SCTP Transport Parameter . . . . . . . . . . . . . . . . . 9
3.5. TCP Transport Parameter . . . . . . . . . . . . . . . . . 9 3.5. TCP Transport Parameter . . . . . . . . . . . . . . . . . 10
3.6. UDP Transport Parameter . . . . . . . . . . . . . . . . . 10 3.6. UDP Transport Parameter . . . . . . . . . . . . . . . . . 11
3.7. UDP-Lite Transport Parameter . . . . . . . . . . . . . . . 11 3.7. UDP-Lite Transport Parameter . . . . . . . . . . . . . . . 12
3.8. Pool Member Selection Policy Parameter . . . . . . . . . . 12 3.8. Pool Member Selection Policy Parameter . . . . . . . . . . 13
3.9. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 12 3.9. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 13
3.10. Pool Element Parameter . . . . . . . . . . . . . . . . . . 13 3.10. Pool Element Parameter . . . . . . . . . . . . . . . . . . 14
3.11. Server Information Parameter . . . . . . . . . . . . . . . 14 3.11. Server Information Parameter . . . . . . . . . . . . . . . 15
3.12. Operation Error Parameter . . . . . . . . . . . . . . . . 15 3.12. Operation Error Parameter . . . . . . . . . . . . . . . . 16
3.12.1. Unspecified Error . . . . . . . . . . . . . . . . . . 16 3.12.1. Unspecified Error . . . . . . . . . . . . . . . . . . 17
3.12.2. Unrecognized Parameter Error . . . . . . . . . . . . 17 3.12.2. Unrecognized Parameter Error . . . . . . . . . . . . 18
3.12.3. Unrecognized Message Error . . . . . . . . . . . . . 17 3.12.3. Unrecognized Message Error . . . . . . . . . . . . . 18
3.12.4. Invalid Values Error . . . . . . . . . . . . . . . . 17 3.12.4. Invalid Values Error . . . . . . . . . . . . . . . . 18
3.12.5. Non-unique PE Identifier Error . . . . . . . . . . . 17 3.12.5. Non-unique PE Identifier Error . . . . . . . . . . . 18
3.12.6. Inconsistent Pool Policy Error . . . . . . . . . . . 17 3.12.6. Inconsistent Pool Policy Error . . . . . . . . . . . 18
3.12.7. Lack of Resources Error . . . . . . . . . . . . . . . 17 3.12.7. Lack of Resources Error . . . . . . . . . . . . . . . 18
3.12.8. Inconsistent Transport Type Error . . . . . . . . . . 17 3.12.8. Inconsistent Transport Type Error . . . . . . . . . . 18
3.12.9. Inconsistent Data/Control Configuration Error . . . . 18 3.12.9. Inconsistent Data/Control Configuration Error . . . . 19
3.12.10. Rejected due to security considerations . . . . . . . 18 3.12.10. Rejected due to security considerations . . . . . . . 19
3.12.11. Unknown Poor Handle Error . . . . . . . . . . . . . . 18 3.12.11. Unknown Pool Handle Error . . . . . . . . . . . . . . 19
3.13. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 18 3.13. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 19
3.14. PE Identifier Parameter . . . . . . . . . . . . . . . . . 18 3.14. PE Identifier Parameter . . . . . . . . . . . . . . . . . 19
3.15. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 19 3.15. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 20
4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 20 3.16. Opaque Transport Parameter . . . . . . . . . . . . . . . . 20
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 22
5.1. A New Table for RSerPool Parameter Types . . . . . . . . . 22 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
5.2. A New Table for RSerPool Error Causes . . . . . . . . . . 23 5.1. A New Table for RSerPool Parameter Types . . . . . . . . . 24
6. Security Considerations . . . . . . . . . . . . . . . . . . . 25 5.2. A New Table for RSerPool Error Causes . . . . . . . . . . 26
7. Normative References . . . . . . . . . . . . . . . . . . . . . 26 6. Security Considerations . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 7. Normative References . . . . . . . . . . . . . . . . . . . . . 28
Intellectual Property and Copyright Statements . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
Intellectual Property and Copyright Statements . . . . . . . . . . 30
1. Introduction 1. Introduction
Aggregate Server Access Protocol (ASAP) [I-D.ietf-rserpool-asap] in Aggregate Server Access Protocol (ASAP) [I-D.ietf-rserpool-asap] in
conjunction with the Endpoint Handlespace Redundancy Protocol (ENRP) conjunction with the Endpoint Handlespace Redundancy Protocol (ENRP)
[I-D.ietf-rserpool-enrp] provides a high availability data transfer [I-D.ietf-rserpool-enrp] provides a high availability data transfer
mechanism over IP networks. mechanism over IP networks.
Both protocols work together and so share many common parameters used Both protocols work together and so share many common parameters used
in message formats. This document details the common message in message formats. This document details the common message
skipping to change at page 6, line 40 skipping to change at page 7, line 40
| 0xb | Server Information | | 0xb | Server Information |
| | | | | |
| 0xc | Operation Error | | 0xc | Operation Error |
| | | | | |
| 0xd | Cookie | | 0xd | Cookie |
| | | | | |
| 0xe | PE Identifier | | 0xe | PE Identifier |
| | | | | |
| 0xf | PE Checksum | | 0xf | PE Checksum |
| | | | | |
| 0x10 | Opaque Transport |
| | |
| others | (reserved by IETF) | | others | (reserved by IETF) |
+--------+------------------------------+ +--------+------------------------------+
Table 1 Table 1
Parameter Length: 16 bits (unsigned integer) Parameter Length: 16 bits (unsigned integer)
The Parameter Length field contains the size of the parameter in The Parameter Length field contains the size of the parameter in
bytes, including the Parameter Type, Parameter Length, and bytes, including the Parameter Type, Parameter Length, and
Parameter Value fields. Thus, a parameter with a zero-length Parameter Value fields. Thus, a parameter with a zero-length
Parameter Value field would have a Length field of 4. Parameter Value field would have a Length field of 4.
skipping to change at page 14, line 24 skipping to change at page 15, line 24
Home ENRP Server Identifier: 32 bits (unsigned integer) Home ENRP Server Identifier: 32 bits (unsigned integer)
Indicates the current home ENRP server of this PE. Set to all 0's Indicates the current home ENRP server of this PE. Set to all 0's
if the PE's home ENRP server is undetermined. if the PE's home ENRP server is undetermined.
Registration Life: 32 bits (signed integer) Registration Life: 32 bits (signed integer)
Indicates the life time of the registration in number of seconds. Indicates the life time of the registration in number of seconds.
A value of -1 indicates infinite life time. A value of -1 indicates infinite life time.
User Transport User Transport
This can be either an DCCP, SCTP, TCP, UDP, or UDP-Lite type This can be either an DCCP, SCTP, TCP, UDP, UDP-Lite, or Opaque
transport parameter (see Section 3.3, Section 3.4, Section 3.5, transport parameter (see Section 3.3, Section 3.4, Section 3.5,
Section 3.6, Section 3.7). A PE MUST have one and only one User Section 3.6, Section 3.7, Section 3.16). A PE MUST have one and
Transport. only one User Transport.
Member Selection Policy Member Selection Policy
Contains one of the defined member selection policy parameters Contains one of the defined member selection policy parameters
(see Section 3.8). (see Section 3.8).
ASAP Transport ASAP Transport
This indicates the ASAP transport address of the PE and MUST be an This indicates the ASAP transport address of the PE and MUST be an
SCTP type transport parameter (see Section 3.4). SCTP type transport parameter (see Section 3.4).
3.11. Server Information Parameter 3.11. Server Information Parameter
skipping to change at page 16, line 28 skipping to change at page 17, line 28
| 0x4 | Non-unique PE Identifier | | 0x4 | Non-unique PE Identifier |
| | | | | |
| 0x5 | Inconsistent Pooling Policy | | 0x5 | Inconsistent Pooling Policy |
| | | | | |
| 0x6 | Lack of Resources | | 0x6 | Lack of Resources |
| | | | | |
| 0x7 | Inconsistent Transport Type | | 0x7 | Inconsistent Transport Type |
| | | | | |
| 0x8 | Inconsistent Data/Control Configuration | | 0x8 | Inconsistent Data/Control Configuration |
| | | | | |
| 0x9 | Unknown Poor Handle | | 0x9 | Unknown Pool Handle |
| | | | | |
| 0xa | Rejected due to security considerations | | 0xa | Rejected due to security considerations |
| | | | | |
| others | reserved by IETF | | others | reserved by IETF |
+------------------+-----------------------------------------+ +------------------+-----------------------------------------+
Table 2 Table 2
Cause Length: 16 bits (unsigned integer) Cause Length: 16 bits (unsigned integer)
Set to the size of the parameter in bytes, including the Cause Set to the size of the parameter in bytes, including the Cause
skipping to change at page 18, line 18 skipping to change at page 19, line 18
registering PE that the Transport Use field in the User Transport it registering PE that the Transport Use field in the User Transport it
sent in its registration is inconsistent to the pool's overall data/ sent in its registration is inconsistent to the pool's overall data/
control channel configuration. There is no cause specific control channel configuration. There is no cause specific
information. information.
3.12.10. Rejected due to security considerations 3.12.10. Rejected due to security considerations
This error cause is used by any endpoint to indicate a rejection of a This error cause is used by any endpoint to indicate a rejection of a
request due to a failure in security credentials or authorizations. request due to a failure in security credentials or authorizations.
3.12.11. Unknown Poor Handle Error 3.12.11. Unknown Pool Handle Error
This error cause is used by an ENRP server to indicate to a PE or PU This error cause is used by an ENRP server to indicate to a PE or PU
that the requested pool is unknown by the server. There is no cause that the requested pool is unknown by the server. There is no cause
specific information. specific information.
3.13. Cookie Parameter 3.13. Cookie Parameter
This parameter defines a TLV that carries a Cookie. This parameter defines a TLV that carries a Cookie.
0 1 2 3 0 1 2 3
skipping to change at page 20, line 5 skipping to change at page 20, line 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Checksum | Padding | | PE Checksum | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Checksum: 16 bits (unsigned integer) PE Checksum: 16 bits (unsigned integer)
An overall checksum of all PEs in the current handlespace owned by An overall checksum of all PEs in the current handlespace owned by
an ENRP server (which is normally the sender of this TLV). The an ENRP server (which is normally the sender of this TLV). The
definition and calculation of this checksum is defined in definition and calculation of this checksum is defined in
[I-D.ietf-rserpool-enrp]. [I-D.ietf-rserpool-enrp].
3.16. Opaque Transport Parameter
This parameter defines a TLV that carries opaque transport
information.
0 1 2 3
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 = 0x10 | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Opaque Transport Data :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of bytes,
including the Type, Length, and Opaque Transport Data.
Opaque Transport Data: variable length
The Opaque Transport Data is an arbitrary byte string of (Length -
4) bytes.
4. Common Message Formats 4. Common Message Formats
The figure below illustrates the common format for all ASAP and ENRP The figure below illustrates the common format for all ASAP and ENRP
messages. Each message is formatted with a Message Type field, a messages. Each message is formatted with a Message Type field, a
message-specific Flag field, a Message Length field, and a Value message-specific Flag field, a Message Length field, and a Value
field. field.
0 1 2 3 0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 23, line 40 skipping to change at page 25, line 40
| 0xb | Server Information | | 0xb | Server Information |
| | | | | |
| 0xc | Operation Error | | 0xc | Operation Error |
| | | | | |
| 0xd | Cookie | | 0xd | Cookie |
| | | | | |
| 0xe | PE Identifier | | 0xe | PE Identifier |
| | | | | |
| 0xf | PE Checksum | | 0xf | PE Checksum |
| | | | | |
| 0x10 | Opaque Transport |
| | |
| others | (reserved by IETF) | | others | (reserved by IETF) |
+--------+------------------------------+ +--------+------------------------------+
For registering at IANA an RSerPool Parameter Type in this table a For registering at IANA an RSerPool Parameter Type in this table a
request has to be made to assign such a number. This number must be request has to be made to assign such a number. This number must be
unique. The "Specification Required" policy of [RFC2434] MUST be unique. The "Specification Required" policy of [RFC2434] MUST be
applied. applied.
5.2. A New Table for RSerPool Error Causes 5.2. A New Table for RSerPool Error Causes
skipping to change at page 24, line 26 skipping to change at page 26, line 32
| 0x4 | Non-unique PE Identifier | | 0x4 | Non-unique PE Identifier |
| | | | | |
| 0x5 | Inconsistent Pooling Policy | | 0x5 | Inconsistent Pooling Policy |
| | | | | |
| 0x6 | Lack of Resources | | 0x6 | Lack of Resources |
| | | | | |
| 0x7 | Inconsistent Transport Type | | 0x7 | Inconsistent Transport Type |
| | | | | |
| 0x8 | Inconsistent Data/Control Configuration | | 0x8 | Inconsistent Data/Control Configuration |
| | | | | |
| 0x9 | Unknown Poor Handle | | 0x9 | Unknown Pool Handle |
| | | | | |
| 0xa | Rejected due to security considerations | | 0xa | Rejected due to security considerations |
| | | | | |
| others | reserved by IETF | | others | reserved by IETF |
+------------------+-----------------------------------------+ +------------------+-----------------------------------------+
For registering at IANA an RSerPool Error Cause in this table a For registering at IANA an RSerPool Error Cause in this table a
request has to be made to assign such a number. This number must be request has to be made to assign such a number. This number must be
unique. The "Specification Required" policy of [RFC2434] MUST be unique. The "Specification Required" policy of [RFC2434] MUST be
applied. applied.
skipping to change at page 26, line 28 skipping to change at page 28, line 28
November 2007. November 2007.
[I-D.ietf-rserpool-enrp] [I-D.ietf-rserpool-enrp]
Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
Silverton, "Endpoint Handlespace Redundancy Protocol Silverton, "Endpoint Handlespace Redundancy Protocol
(ENRP)", draft-ietf-rserpool-enrp-18 (work in progress), (ENRP)", draft-ietf-rserpool-enrp-18 (work in progress),
November 2007. November 2007.
[I-D.ietf-rserpool-policies] [I-D.ietf-rserpool-policies]
Tuexen, M. and T. Dreibholz, "Reliable Server Pooling Tuexen, M. and T. Dreibholz, "Reliable Server Pooling
Policies", draft-ietf-rserpool-policies-07 (work in Policies", draft-ietf-rserpool-policies-08 (work in
progress), November 2007. progress), March 2008.
Authors' Addresses Authors' Addresses
Randall R. Stewart Randall R. Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
4875 Forest Drive 4875 Forest Drive
Suite 200 Suite 200
Columbia, SC 29206 Columbia, SC 29206
USA USA
skipping to change at page 28, line 7 skipping to change at page 30, line 7
Michael Tuexen Michael Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
Stegerwaldstr. 39 Stegerwaldstr. 39
48565 Steinfurt 48565 Steinfurt
Germany Germany
Email: tuexen@fh-muenster.de Email: tuexen@fh-muenster.de
Full Copyright Statement 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
skipping to change at page 28, line 44 skipping to change at line 1080
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 of
such proprietary rights by implementers or users of this 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 at
http://www.ietf.org/ipr. 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 any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 16 change blocks. 
55 lines changed or deleted 78 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/