draft-ietf-ccamp-rsvp-restart-ext-01.txt   draft-ietf-ccamp-rsvp-restart-ext-02.txt 
Network Working Group A. Satyanarayana (Cisco Systems) Network Working Group A. Satyanarayana (Cisco Systems)
Internet Draft R. Rahman (Cisco Systems) Internet Draft R. Rahman (Cisco Systems)
Expiration Date: August 2005 Editors Expiration Date: September 2005 Editors
February 2005 March 2005
Extensions to GMPLS RSVP Graceful Restart Extensions to GMPLS RSVP Graceful Restart
draft-ietf-ccamp-rsvp-restart-ext-01.txt draft-ietf-ccamp-rsvp-restart-ext-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668. disclosed, in accordance with RFC 3668.
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 other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line 26 skipping to change at page 2, line 26
2.4.2 Re-Synchronization Procedures ............................. 8 2.4.2 Re-Synchronization Procedures ............................. 8
2.4.3 Procedures on Expiration of Recovery Period ............... 9 2.4.3 Procedures on Expiration of Recovery Period ............... 9
2.5 Compatibility ............................................. 9 2.5 Compatibility ............................................. 9
3 RecoveryPath Summary Refresh .............................. 10 3 RecoveryPath Summary Refresh .............................. 10
3.1 MESSAGE_ID ACK/NACK and MESSAGE_ID LIST Objects ........... 11 3.1 MESSAGE_ID ACK/NACK and MESSAGE_ID LIST Objects ........... 11
3.2 Capability Object ......................................... 12 3.2 Capability Object ......................................... 12
3.2.1 Procedures ................................................ 13 3.2.1 Procedures ................................................ 13
3.2.2 Compatibility ............................................. 13 3.2.2 Compatibility ............................................. 13
3.3 RecoveryPath Summary Refresh Procedures ................... 14 3.3 RecoveryPath Summary Refresh Procedures ................... 14
3.3.1 Generation of RecoveryPath-related Srefresh Messages ...... 14 3.3.1 Generation of RecoveryPath-related Srefresh Messages ...... 14
3.3.2 RecoveryPath-related Srefresh Receive Processing and NACK Generation 16 3.3.2 RecoveryPath-related Srefresh Receive Processing and NACK
Generation ................................................ 15
3.3.3 RecoveryPath-related MESSAGE_ID NACK Receive Processing ... 16 3.3.3 RecoveryPath-related MESSAGE_ID NACK Receive Processing ... 16
4 Acknowledgments ........................................... 17 4 Acknowledgments ........................................... 17
5 Security Considerations ................................... 17 5 Security Considerations ................................... 17
6 IANA Considerations ....................................... 17 6 IANA Considerations ....................................... 17
7 References ................................................ 17 7 References ................................................ 17
7.1 Normative References ...................................... 17 7.1 Normative References ...................................... 17
7.2 Informative References .................................... 18 7.2 Informative References .................................... 18
8 Authors' Addresses ........................................ 18 8 Authors' Addresses ........................................ 18
9 Intellectual Property Considerations ...................... 19 9 Intellectual Property Considerations ...................... 19
10 Disclaimer of Validity .................................... 20 10 Disclaimer of Validity .................................... 20
skipping to change at page 12, line 42 skipping to change at page 13, line 4
The format of a Capability object is: The format of a Capability object is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Class-Num(TBA)| C-Type (1) | | Length | Class-Num(TBA)| C-Type (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |R| | Reserved |R|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RecoveryPath Srefresh Capable (R): 1 bit RecoveryPath Srefresh Capable (R): 1 bit
When set (1), indicates that the sending node is capable of When set (1), indicates that the sending node is capable of
receiving and processing Srefresh messages with the receiving and processing Srefresh messages with the
RecoveryPath Flag set (1) in the MESSAGE_ID LIST object. RecoveryPath Flag set (1) in the MESSAGE_ID LIST object.
Absence of the Capability object MUST be treated as if the Absence of the Capability object MUST be treated as if the
R-bit is cleared (0). R-bit is cleared (0).
Reserved bits Reserved bits
Reserved bits MUST be set to zero on transmission and MUST be Reserved bits MUST be set to zero on transmission and MUST be
ignored on receipt. ignored on receipt.
This document does not define any TLV's to be included in the
Capability object.
3.2.1. Procedures 3.2.1. Procedures
The Capability object is sent within a Hello message to indicate that The Capability object is sent within a Hello message to indicate that
a node supports selective transmission of RecoveryPath messages. To a node supports selective transmission of RecoveryPath messages. To
indicate to a neighbor that selective transmission of RecoveryPath indicate to a neighbor that selective transmission of RecoveryPath
messages is desired, a restarting node MUST include the Capability messages is desired, a restarting node MUST include the Capability
object with the R-bit set (1) in all Hello messages it sends during object with the R-bit set (1) in all Hello messages it sends during
the Recovery Period to the neighbor. When either the Restart_Cap the Recovery Period to the neighbor. When either the Restart_Cap
Object is not present in a Hello message or when the Recovery Time is Object is not present in a Hello message or when the Recovery Time is
zero (0), the Capability object MUST be omitted or the R-bit MUST be zero (0), the Capability object MUST be omitted or the R-bit MUST be
skipping to change at page 18, line 26 skipping to change at page 18, line 26
[RESTART] "RSVP Graceful Restart Extensions", [RESTART] "RSVP Graceful Restart Extensions",
draft-rahman-rsvp-restart-extensions-00, draft-rahman-rsvp-restart-extensions-00,
R. Rahman, et al, October 2003 R. Rahman, et al, October 2003
8. Authors' Addresses 8. Authors' Addresses
Arun Satyanarayana Arun Satyanarayana
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Dr. 170 West Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
Phone: +1 408 853-3206
Email: asatyana@cisco.com Email: asatyana@cisco.com
Lou Berger Lou Berger
Movaz Networks, Inc. Movaz Networks, Inc.
7926 Jones Branch Drive 7926 Jones Branch Drive
Suite 615 Suite 615
McLean VA, 22102 McLean VA, 22102
Phone: +1 703 847-1801 Phone: +1 703 847-1801
Email: lberger@movaz.com Email: lberger@movaz.com
 End of changes. 

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