Relaxing RSVP Loop Checking
draft-balls-ccamp-relax-loop-check-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-05-23 (latest revision 2012-11-19) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-balls-ccamp-relax-loop-check-02.txt
Abstract
This specification relaxes the rules governing loop checking within RSVP. These were originally defined in RFC3209 and are too strict for the requirements of today's data planes.
Authors
Steve Balls
(steve.balls@metaswitch.com)
Jonathan Hardwick
(jonathan.hardwick@metaswitch.com)
Cyril Margaria
(cyril.margaria@nsn.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)