Browse Prior Art Database

Requirements for Signaling Protocols (RFC3726)

IP.com Disclosure Number: IPCOM000027978D
Original Publication Date: 2004-Apr-01
Included in the Prior Art Database: 2004-Apr-16
Document File: 43 page(s) / 98K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Brunner: AUTHOR [+2]

Abstract

This document defines requirements for signaling across different network environments, such as across administrative and/or technology domains. Signaling is mainly considered for Quality of Service (Qos) such as the Resource Reservation Protocol (RSVP). However, in recent years, several other applications of signaling have been defined. For example, signaling for label distribution in Multiprotocol Label Switching (MPLS) or signaling to middleboxes. To achieve wide applicability of the requirements, the starting point is a diverse set of scenarios/use cases concerning various types of networks and application interactions. This document presents the assumptions before listing the requirements. The requirements are grouped according to areas such as architecture and design goals, signaling flows, layering, performance, flexibility, security, and mobility.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group M. Brunner, Ed.

Request for Comments: 3726 NEC

Category: Informational April 2004

Requirements for Signaling Protocols

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2004). All Rights Reserved.

Abstract

This document defines requirements for signaling across different

network environments, such as across administrative and/or technology

domains. Signaling is mainly considered for Quality of Service (Qos)

such as the Resource Reservation Protocol (RSVP). However, in recent

years, several other applications of signaling have been defined.

For example, signaling for label distribution in Multiprotocol Label

Switching (MPLS) or signaling to middleboxes. To achieve wide

applicability of the requirements, the starting point is a diverse

set of scenarios/use cases concerning various types of networks and

application interactions. This document presents the assumptions

before listing the requirements. The requirements are grouped

according to areas such as architecture and design goals, signaling

flows, layering, performance, flexibility, security, and mobility.

Brunner Informational [Page 1]

RFC 3726 Requirements for Signaling Protocols April 2004

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 5

2. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . 5

3. Problem Statement and Scope. . . . . . . . . . . . . . . . . . 6

4. Assumptions and Exclusions . . . . . . . . . . . . . . . . . . 8

4.1. Assumptions and Non-Assumptions. . . . . . . . . . . . . 8

4.2. Exclusions . . . . . . . . . . . . . . . . . . . . . . . 9

5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.1. Architecture and Design Goals. . . . . . . . . . . . . . 11

5.1.1. NSIS SHOULD Provide Availability Information

on Request . . . . . . . . . . . . . . . . . . . 11

5.1.2. NSIS MUST be Designed Modularly. . . . . . . . . 11

5.1.3. NSIS MUST Decouple Protocol and Information. . . 12

5.1.4. NSIS MUST Support Independence of Signaling and

Network Control Paradigm . . . . . . . . . . . . 12

5.1.5. NSIS SHOULD be Able to Carry Opaque Objects. . . 12

5.2. Signaling Flows. . . . . . . . . . . . . . . . . . . . . 12

5.2.1. The Placement of NSIS Initiator, Forwarder, and

Responder Anywhere in the Network MUST be

Allowed. . . . . . . . . . . . . . . . . . . . . 12

5.2.2. NSIS MUST Support Path-Coupled and MAY Support

Path-Decoupled Signaling . . . . . . . . . . . . 13

5.2.3. Concealment of Topology and Technology

Information SHOULD be Possible . . . . . . . . . 13

5.2.4. Transparent Signaling Through Networks SHOULD be

Possible . . . . . . . . . . . . . . . . . . . . 13

5.3. Messaging. . . . . . . . . . . . . . . . . . . . . . . . 13

5.3.1. Explicit Erasure of State MUST be...