Revised Definition of The GMPLS Switching Capability and Type Fields
draft-berger-ccamp-swcaps-update-02
| Document | Type | Replaced Internet-Draft (candidate for ccamp WG) | |
|---|---|---|---|
| Last updated | 2013-05-14 (latest revision 2012-07-04) | ||
| Replaced by | draft-ietf-ccamp-swcaps-update | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-ccamp-swcaps-update | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-berger-ccamp-swcaps-update-02.txt
Abstract
GMPLS provides control for multiple switching technologies, and hierarchical switching within a technology. GMPLS routing and signaling use common values to indicate switching technology type. These values are carried in routing in the Switching Capability field, and in signaling in the Switching Type field. While the values using in these fields are the primary indicators of the technology and hierarchy level being controlled, the values are not consistently defined and used across the different technologies supported by GMPLS. This document is intended to resolve the inconsistent definition and use of the Switching Capability and Type fields by narrowly scoping the meaning and use of the fields. This document updates any document that uses the GMPLS Switching Capability and Types fields, in particular RFC 3471, RFC 4202, RFC 4203, and RFC 5307.
Authors
Lou Berger
(lberger@labn.net)
Julien Meuric
(julien.meuric@orange-ftgroup.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)