| TOC |
|
This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any 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 become aware will be disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 25, 2005.
Copyright (C) The Internet Society (2005).
This document describes the state machines for the NSIS Signaling Layer Protocol for Quality-of-Service signaling (QoS NSLP). A set of state machines for QoS NSLP entities at different locations of a flow path are presented in order to illustrate how QoS NSLP may be implemented.
1.
Introduction
2.
Terminology
3.
Notational conventions used in state diagrams
4.
State Machine Symbols
5.
Common Rules
5.1
Common Procedures
5.2
Common Variables
5.3
Constants
5.4
Assumptions
6.
State machine for QNI QoS NSLP node
7.
State machine for QNE QoS NSLP nodes
8.
State machine for QNR QoS NSLP node
9.
Security Considerations
10.
Open Issues
11.
Change History
11.1
Changes in Version -01
12.
Acknowledgments
13.
References
13.1
Normative References
13.2
Informative References
§
Authors' Addresses
§
Intellectual Property and Copyright Statements
| TOC |
This document describes the state machines for QoS NSLP [1]Bosch, S., Karagiannis, G. and A. McDonald, NSLP for Quality-of-Service signaling, October 2004., trying to show how QoS NSLP can be implemented to support its deployment. The state machines described in this document are illustrative of how the QoS NSLP protocol defined in [1]Bosch, S., Karagiannis, G. and A. McDonald, NSLP for Quality-of-Service signaling, October 2004. may be implemented for the QNI QoS NSLP node, QNE QoS NSLP nodes, and QNR QoS NSLP node in the flow path. Where there are differences [1]Bosch, S., Karagiannis, G. and A. McDonald, NSLP for Quality-of-Service signaling, October 2004. are authoritative. The state machines are informative only. Implementations may achieve the same results using different methods.
According to [1]Bosch, S., Karagiannis, G. and A. McDonald, NSLP for Quality-of-Service signaling, October 2004., there are several possibilities for QoS NSLP signaling, at least including the following:
end-to-end signaling vs. scoped signaling
sender-initiated signaling vs. receiver-initiated signaling
(which need to be incorporated into use scenarios when describing state machine. Note they are represented by way of certain objects/flags in Reserve and Query messages.)
The messages used in the QoS NSLP protocol can be summarized as follows:
Requesting message Responding message ------------------------+--------------------------- RESERVE |None or RESERVE or RESPONSE QUERY |RESERVE or RESPONSE RESPONSE |NONE NOTIFY |NONE ------------------------+---------------------------
We describe a set of state machines for different roles of entities running QoS NSLP to illustrate how QoS NSLP may be implemented.
| TOC |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [2]Bradner, S., Key words for use in RFCs to Indicate Requirement Levels, March 1997..
| TOC |
The following text is reused from [3]Vollbrecht, J., Eronen, P., Petroni, N. and Y. Ohba, State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator, December 2004. and the state diagrams are based on the conventions specified in [4]Institute of Electrical and Electronics Engineers, DRAFT Standard for Local and Metropolitan Area Networks: Port-Based Network Access Control (Revision), January 2004., Section 8.2.1. Additional state machine details are taken from [5]Ohba, Y., State Machines for Protocol for Carrying Authentication for Network Access (PANA), February 2005..
The complete text is reproduced here:
State diagrams are used to represent the operation of the protocol by a number of cooperating state machines each comprising a group of connected, mutually exclusive states. Only one state of each machine can be active at any given time.
All permissible transitions between states are represented by arrows, the arrowhead denoting the direction of the possible transition. Labels attached to arrows denote the condition(s) that must be met in order for the transition to take place. All conditions are expressions that evaluate to TRUE or FALSE; if a condition evaluates to TRUE, then the condition is met. The label UCT denotes an unconditional transition (i.e., UCT always evaluates to TRUE). A transition that is global in nature (i.e., a transition that occurs from any of the possible states if the condition attached to the arrow is met) is denoted by an open arrow; i.e., no specific state is identified as the origin of the transition. When the condition associated with a global transition is met, it supersedes all other exit conditions including UCT. The special global condition BEGIN supersedes all other global conditions, and once asserted remains asserted until all state blocks have executed to the point that variable assignments and other consequences of their execution remain unchanged.
On entry to a state, the procedures defined for the state (if any) are executed exactly once, in the order that they appear on the page. Each action is deemed to be atomic; i.e., execution of a procedure completes before the next sequential procedure starts to execute. No procedures execute outside of a state block. The procedures in only one state block execute at a time, even if the conditions for execution of state blocks in different state machines are satisfied, and all procedures in an executing state block complete execution before the transition to and execution of any other state block occurs, i.e., the execution of any state block appears to be atomic with respect to the execution of any other state block and the transition condition to that state from the previous state is TRUE when execution commences. The order of execution of state blocks in different state machines is undefined except as constrained by their transition conditions. A variable that is set to a particular value in a state block retains this value until a subsequent state block executes a procedure that modifies the value.
On completion of all of the procedures within a state, all exit conditions for the state (including all conditions associated with global transitions) are evaluated continuously until one of the conditions is met. The label ELSE denotes a transition that occurs if none of the other conditions for transitions from the state are met (i.e., ELSE evaluates to TRUE if all other possible exit conditions from the state evaluate to FALSE). Where two or more exit conditions with the same level of precedence become TRUE simultaneously, the choice as to which exit condition causes the state transition to take place is arbitrary.
In addition to the above notation, there are a
couple of clarifications specific to this document. First,
all boolean variables are initialized to FALSE before the
state machine execution begins. Second, the following
notational shorthand is specific to this document:
- <variable> = <expression1> | <expression2> | ...
- Execution of a statement of this form will result in <variable> having a value of exactly one of the expressions. The logic for which of those expressions gets executed is outside of the state machine and could be environmental, configurable, or based on another state machine such as that of the method.
| TOC |
- ( )
- Used to force the precedence of operators in Boolean expressions and to delimit the argument(s) of actions within state boxes.
- ;
- Used as a terminating delimiter for actions within state boxes. Where a state box contains multiple actions, the order of execution follows the normal language conventions for reading text.
- =
- Assignment action. The value of the expression to the right of the operator is assigned to the variable to the left of the operator. Where this operator is used to define multiple assignments, e.g., a = b = X the action causes the value of the expression following the right-most assignment operator to be assigned to all of the variables that appear to the left of the right-most assignment operator.
- !
- Logical NOT operator.
- &&
- Logical AND operator.
- ||
- Logical OR operator.
- if...then...
- Conditional action. If the Boolean expression following the if evaluates to TRUE, then the action following the then is executed.
- \{ statement 1, ... statement N \}
- Compound statement. Braces are used to group statements that are executed together as if they were a single statement.
- !=
- Inequality. Evaluates to TRUE if the expression to the left of the operator is not equal in value to the expression to the right.
- ==
- Equality. Evaluates to TRUE if the expression to the left of the operator is equal in value to the expression to the right.
- >
- Greater than. Evaluates to TRUE if the value of the expression to the left of the operator is greater than the value of the expression to the right.
- <=
- Less than or equal to. Evaluates to TRUE if the value of the expression to the left of the operator is either less than or equal to the value of the expression to the right.
- ++
- Increment the preceding integer operator by 1.
| TOC |
Throughout the document we use terms defined in the [1]Bosch, S., Karagiannis, G. and A. McDonald, NSLP for Quality-of-Service signaling, October 2004., such as flow sender, flow receiver, QUERY, RESERVE or RESPONSE.
- tx_RESERVE(Toff):
- Transmit RESERVE message with 'Teardown' bit off
- tx_RESERVE(Ton):
- Transmit RESERVE message with 'Teardown' bit on
- tx_RESPONSE():
- Transmit RESPONSE message
- tx_QUERY(<object>):
- Transmit QUERY message with <object>
- tx_QUERY(w/o<object>):
- Transmit QUERY message without <object>
- tx_NOTIFY():
- Transmit NOTIFY message
- rx_RESPONSE():
- Receive RESPONSE message
- rx_QUERY():
- Receive QUERY message
- rx_RESERVE():
- Receive RESERVE message
- rx_NOTIFY():
- Transmit NOTIFY message
- TIMEOUT_StateLifetime:
- State lifetime timer expiration
- TIMEOUT_Refresh:
- Refresh interval timer expiration
- TIMEOUT_Refresh:
- Wait-Response interval timer expiration
- tg_QUERY:
- External trigger to send a QUERY message (typically triggered by the application).
- tg_RESERVE:
- External trigger to send a RESERVE message.
- tg_TEARDOWN:
- External trigger to clear previously established QoS state (typically triggered by the application). It is translated to a tx_RESERVE(Ton) message.
- Install QoS state:
- Install the local QoS state.
- Refresh QoS state:
- Refresh the local QoS state.
- Delete QoS state:
- Delete the local QoS state.
- Send info to Application:
- Report information to the application.
- RMF:
- Performs Resource Management Function and returns the following values{AVAIL, NO_AVAIL}.
- SetRII:
- Sets the RII object of the messages e.g. the node requests explicit response to the message being sent. Returns values {0,1}.
- CheckRII:
- Checks the RII object of received RESPONSE message if it is requested by current node or other upstream node. Returns values {LOCAL, NO_LOCAL}.
- ProcessQUERY:
- Processes a Query message and provides the requested info
- RII:
- Request Identification Information (RII) object. Logical variable representing if the RII is set or not. Takes values {0,1}.
- SCOPING:
- Scoping flag of common message header. Takes values {"Next_hop","Whole_path"}.
- RSN:
- Reservation Sequence Number object. Takes values:
- - recRSN - RSN object of the received message
- - currRSN - Current stored RSN value for installed QoS state. (Assumed to be the one for the direction where the message comes from e.g.Upstream/Downstream)
- ACK:
- Acknowledgement flag of common message header. Takes values {"On","Off"}.
- SummaryRefresh:
- Keeps information if Summary refresh method may be used for refreshing a installed QoS state. Takes value {"On","Off"}.
- E_SPEC:
- Error_Spec object. Takes values:
- - 0x02? - Success values
- - 0x04? - Transient Failure values
- - ERROR - Not specified in the QoS NSLP draft, but used here.(Section 10Open Issues)
- QSPEC:
- QoS specification object.
- FlowID:
- Flow ID kept by the installed QoS state.
- Replace:
- Replace flag of common message header. Takes values {"On","Off"}.
- SII:
- Source Identification Information entry. Takes values:
- - CurrSII - SII entry stored for current installed QoS state. (Assumed to be the one for the direction where the message comes from e.g.Upstream/Downstream)
- - newSII - SII of the received message is different from the SII stored for the current installed QoS state.
| TOC |
----------- State: INIT ----------- Condition Action State ------------------------+-------------------------+------------ UCT | initialize variables |IDLE ------------------------+-------------------------+------------
-----------
State: IDLE
-----------
Condition Action State Note
------------------------+-------------------------+-----------+---
rx_QUERY(RII) |ProcessQUERY |IDLE |
|tx_RESPONSE(RII) | |
| | |
(tg_RESERVE) && |Send info to Application |IDLE |
(RMF="NO_AVAIL") | | |
| | |
(tg_RESERVE) && (!RII) |tx_RESERVE(w/oRII), |QoS state |
&& (!setRII) && | Install QoS state, |Installed |
(RMF="AVAIL") | Send info to Application| |
| | |
(tg_RESERVE) && (setRII)|Install QoS state, |QoS state |
&&(RMF="AVAIL") | tx_RESERVE(RII) |Installed +|
| |WAITRESP2 |
| | |
(rx_QUERY)&&(!RII)&& |Tx_RESPONSE(RSN, |IDLE |1)
(RMF="NO_AVAIL") | E_SPEC="ERROR") | |2)
| | |
(rx_QUERY) && (!RII) && |tx_RESERVE(w/oRII), |QoS state |2)
(!setRII) && | Install QoS state, |Installed |
(RMF="AVAIL") | Send info to Application| |
| | |
(rx_QUERY) && (!RII) && |Install QoS state, |QoS state |2)
(setRII) && |tx_RESERVE( RII) |Installed +|
(RMF="AVAIL") | |WAITRESP2 |
| | |
(tg_QUERY) && (setRII) |tx_QUERY(RII) |WAITRESP1 |
| | |
------------------------+-------------------------+-----------+---
Note:
1) How to signal unsuccessful reservation for Receiver initiated
reservation (No RII included; sent Response(RSN) should not be
forwarded further than the next peer). No Error_SPEC value
specified for this case.
2) Relevant for Receiver-initiated reservation.
----------------
State: WAITRESP1
----------------
Condition Action State
------------------------+-------------------------+------------
(TIMEOUT_WaitResp) && |tx_QUERY(RII) |WAITRESP1
(!MaxRetry) | |
| |
(TIMEOUT_WaitResp) && |Send info to Application |IDLE
(MaxRetry) | |
| |
rx_RESPONSE |Send info to Application |IDLE
------------------------+-------------------------+------------
--------------------------------------
State: QoS state installed + WAITRESP2
--------------------------------------
Condition Action State
------------------------+-------------------------+------------
(TIMEOUT_WaitResp) && |tx_RESERVE(RII) |QoS state
(!MaxRetry) | |installed +
| |WAITRESP2
| |
| |
(TIMEOUT_WaitResp) && |Delete QoS state |IDLE
(MaxRetry) |Send info to Application |
| |
rx_RESPONSE(RII, |Delete QoS state |IDLE
E_SPEC="0x04?") |Send info to Application |
| |
| |
rx_RESPONSE(RII, |Send info to Application |QoS state
E_SPEC="0x02?") |SummaryRefresh="On" |installed
------------------------+-------------------------+------------
--------------------------
State: QoS state installed
--------------------------
Condition Action State Note
------------------------+-------------------------+-----------+---
TIMEOUT_Refresh |If (SummaryRefresh="On") |QoS state |
| (Tx_RESERVE(RSN)) && |installed |
| (SummaryRefresh="Off") | |
|Else | |
| Tx_RESERVE(RSN,QSPEC); | |
| | |
rx_RESPONSE(RSN, |SummaryRefresh="On" |QoS state |
E_SPEC="0x02?") | |installed |
| | |
TIMEOUT_StateLifetime |Delete QoS state |IDLE |1)
|Send info to Application | |
| | |
tg_TEARDOWN |Delete QoS state, |IDLE |
| tx_RESERVE(Ton) | |
| | |
rx_NOTIFY(RSN, |Delete QoS state |IDLE |
E_SPEC="0x04?") |Send info to Application | |
------------------------+-------------------------+-----------+---
Note:
1) If QoS state lifetime expires in QNI, should RESERVE(Ton)
be sent downstream the path?
| TOC |
----------- State: INIT ----------- Condition Action State ------------------------+-------------------------+------------ UCT | initialize variables |IDLE ------------------------+-------------------------+------------
-----------
State: IDLE
-----------
Condition Action State Note
------------------------+-------------------------+-----------+---
(rx_QUERY) && (!RII) |tx_QUERY(w/oRII) |IDLE |2)
| | |
(rx_QUERY(RII, |ProcessQUERY, |IDLE |7)
SCOPING="Next_hop") |Tx_RESPONSE(RII) | |
| | |
(rx_QUERY) && (RII) |tx_QUERY(w/RII) |IDLE |7)
| | |
(rx_RESERVE(RII)) && |Tx_RESPONSE(RII, |IDLE |3)
(RMF="NO_AVAIL") | E_SPEC="0x04?") | |
| | |
(rx_RESERVE) && (!RII)&&|Tx_RESPONSE(RSN, |IDLE |3)
(RMF="NO_AVAIL") | E_SPEC="0x04?") | |
| | |
(rx_RESPONSE(RII)) && |Tx_RESPONSE(RII) |IDLE |
(CheckRII="Not_LOCAL")| | |
| | |
(rx_RESERVE)&& !(setRII)|Install QoS state, |QoS State |1a)
&& (RMF="AVAIL") |If(ACK="On") |Installed |
| Tx_RESPONSE(RSN, | |
| E_SPEC="0x02?");| |
|If(RII) Tx_RESPONSE(RII) | |
|Else Tx_RESPONSE(w/oRII)| |
| | |
(rx_RESERVE(SCOPING= |Install QoS state, |QoS State |1b)
"Next_hop")) && |If(RII) Tx_RESPONSE(RII, |Installed |
(RMF="AVAIL") | E_SPEC="0x02?") | |
|Else Tx_RESPONSE(RSN, | |
| E_SPEC="0x02?") | |
| | |
(rx_RESERVE) && (setRII)|Install QoS state, |QoS State |4)
&& (RMF="AVAIL") |Tx_RESPONSE(RII), |Installed +|
|If(ACK="On") |WAITRESP1 |
| Tx_RESPONSE(RSN, | |
| E_SPEC="0x02?");| |
| | |
(tg_QUERY) && (setRII) |tx_QUERY(RII) |WAITRESP2 |5)
------------------------+-------------------------+-----------+---
----------------
State: QoS State Installed + WAITRESP1
----------------
Condition Action State Note
------------------------+-------------------------+-----------+---
(TIMEOUT_WaitResp) && |tx_RESERVE(RII) |WAITRESP1 |
(!MaxRetry) | | |
| | |
(TIMEOUT_WaitResp) && |Delete QoS State, | |
(MaxRetry) && |tx_NOTIFY(RSN, |IDLE |
| E_SPEC="0x04?") | |
|Send info to Application | |
| | |
(rx_RESPONSE(RII, |Delete QoS State, |IDLE |4)
E_SPEC="0x04?")) |tx_NOTIFY(RSN, | |
&&(CheckRII="LOCAL") | E_SPEC="0x04?") | |
|Send info to Application | |
| | |
(rx_RESPONSE(RII, |Send info to Application |QoS State |
E_SPEC="0x02?")) |SummaryRefresh="On" |Installed |
&&(CheckRII="LOCAL") | | |
------------------------+-------------------------+-----------+---
----------------
State: WAITRESP2
----------------
Condition Action State Note
------------------------+-------------------------+-----------+---
(TIMEOUT_WaitResp) && |tx_QUERY(RII) |WAITRESP2 |
(!MaxRetry) | | |
| | |
(TIMEOUT_WaitResp) && |Send info to Application |IDLE |
(MaxRetry) | | |
| | |
(rx_RESPONSE) && |Send info to Application |IDLE |
(CheckRII="LOCAL") | | |
------------------------+-------------------------+-----------+---
------------------
State: QoS State Installed
------------------
Condition Action State Note
------------------------+-------------------------+-----------+---
rx_RESERVE(Ton) |tx_RESERVE(Ton), |IDLE |
|Delete QoS state | |
| | |
rx_RESERVE |Refresh QoS state |QoS State |6)
|If(ACK="On") |Installed |
|Tx_RESPONSE(RSN, | |
| E_SPEC="0x02?") | |
| | |
rx_RESPONSE(RSN, |SummaryRefresh="On" |QoS State |6)
E_SPEC="0x02?") | |Installed |
| | |
TIMEOUT_Refresh |If (SummaryRefresh="On") |QoS State |6)
| (Tx_RESERVE(RSN)) |Installed |
| &&(SummaryRefresh="Off")| |
|Else | |
| Tx_RESERVE(RSN,QSPEC) | |
| | |
(rx_RESPONSE(RII, |SummaryRefresh="On" |QoS State |
E_SPEC="0x02?")) |Tx_RESPONSE(RII, |Installed |
&&(ChechRII="NOT_LOCAL")| E_SPEC="0x02?") | |
| | |
| | |
(TIMEOUT_StateLifetime) |Delete QoS state |IDLE |8)
| | |
(rx_RESPONSE(RII, | | |
E_SPEC="0x04?")) |Delete QoS state |IDLE |
&&(ChechRII="NOT_LOCAL")|rx_RESPONSE(RII, | |
| E_SPEC="0x04?") | |
| | |
rx_RESPONSE(RSN, |Delete QoS state |IDLE |
E_SPEC="0x04?") |rx_NOTIFY(RSN, | |
| E_SPEC="0x04?") | |
| | |
rx_NOTIFY(RSN, |Delete QoS state |IDLE |
E_SPEC="0x04?") |rx_NOTIFY(RSN, | |
| E_SPEC="0x04?") | |
| | |
| | |
(Rx_RESERVE)&&(currSII) |Update QoS state |QoS State |9)
&&(Replace="On") |If (RII) |Installed |
&&(RMF="AVAIL") | Tx_RESERVE(RII,QSPEC)| |
&&((recRSN>=currRSN) |else | |
||(newFlowID)) | Tx_RESERVE(RSN,QSPEC);| |
|If (ACK="On")&&(!RII) | |
| tx_RESPONSE(RSN, | |
| E_SPEC="0x02?");| |
| | |
| | |
(Rx_RESERVE)&&(newSII) |Update QoS state |QoS State |9)
&&(RMF="AVAIL") |If (RII) |Installed |
&&((recRSN>=currRSN) | Tx_RESERVE(RII,QSPEC)| |
||(newFlowID)) |else | |
| Tx_RESERVE(RSN,QSPEC);| |
|If (ACK="On")&&(!RII) | |
| tx_RESPONSE(RSN, | |
| E_SPEC="0x02?");| |
|If (Replace="On") | |
| tx_Reserve(Ton) | |
| to currSII | |
------------------------+-------------------------+-----------+---
NOTE:
1) Successful reservation without Response request (1a) and with
Scoping (1b).
2) Processing of Query msg for Receiver initiated reservation
3) Unsuccessful reservation with/without request for response
from previous node in the path.
4) Unsuccessful reservation. RII requested at the local node.
NOTIFY(RSN) is sent further to the upstream nodes.
5) Processing of Query msg triggered by the application layer.
6) QoS State refresh procedures
7) Processing of Query msg received from an upstream node.
8) We assume that handling of QoS state lifetime expiration
event is based on the local policy of the node.
NOTIFY/Reserve(Ton) messages might be sent to other peers.
These issues are not described in the QoS NSLP draft.
9) Update QoS state and Re-route functionality
| TOC |
----------- State: INIT ----------- Condition Action State ------------------------+-------------------------+------------ UCT | initialize variables |IDLE ------------------------+-------------------------+------------
-----------
State: IDLE
-----------
Condition Action State Note
------------------------+-------------------------+-----------+---
rx_QUERY(RII) |tx_RESPONSE(RII) |IDLE |
| | |
(rx_RESERVE)&&(!RII) |Tx_RESPONSE(RSN, |IDLE |
&& (RMF="NO_A") | E_SPEC="0x04?") | |
| | |
| | |
(rx_RESERVE(RII)) |Tx_RESPONSE(RII, |IDLE |
&& (RMF="NO_A") | E_SPEC="0x04?") | |
| | |
(tg_QUERY) && |tx_QUERY(w/oRII) |WAITRESV |1)
(!setRII) | | |
| | |
| | |
(rx_RESERVE(RII)) |Install QoS state |QoS state |2)
&& (RMF="AVAIL") |Tx_RESPONSE(RII, |installed |
| E_SPEC="0x02?") | |
| | |
(rx_RESERVE)&&(!RII) |Install QoS state |QoS state |2)
&& (RMF="AVAIL") |Tx_RESPONSE(RSN, |installed |
E_SPEC="0x02?") | |
------------------------+-------------------------+-----------+---
---------------
State: WAITRESV
---------------
Condition Action State Note
------------------------+-------------------------+-----------+---
TIMEOUT_WaitResp |Tx_QUERY(w/oRII) |WAITRESV |
| | |
(TIMEOUT_WaitResp) |Send info to Appl. |IDLE |
&& (MaxRetry) | | |
| | |
(rx_RESERVE)&&(!RII) |tx_RESPONSE(RSN, |IDLE |3)
&& (RMF="Not_AVAIL") | E_SPEC="0x04?") | |
|Send info to Appl. | |
| | |
(rx_RESERVE(RII)) |tx_RESPONSE(RII, |IDLE |3)
&& (RMF="Not_AVAIL") | E_SPEC="0x04?") | |
|Send info to Appl. | |
| | |
rx_RESPONSE(E_SPEC= |Send info to Appl. |IDLE |4)
"ERROR")| | |
| | |
| | |
(rx_RESERVE)&&(!RII) |Install QoS state |QoS state |
&& (RMF="AVAIL") |Tx_RESPONSE(RSN, |installed |
| E_SPEC="0x02?") | |
| | |
(rx_RESERVE(RII)) |Install QoS State |QoS state |
&& (RMF="AVAIL") |Tx_RESPONSE(RII) |installed |
| | |
------------------------+-------------------------+-----------+---
------------------
State: QoS state installed
------------------
Condition Action State Note
------------------------+-------------------------+-----------+---
rx_RESERVE |Refresh QoS state |QoS state |
|If(ACK="On") |installed |
| Tx_RESPONSE(RSN, | |
| E_SPEC="0x02?")| |
| | |
TIMEOUT_StateLifetime |Delete QoS state |IDLE |5)
| | |
rx_RESERVE(Ton) |Delete QoS state |IDLE |
| | |
------------------------+-------------------------+------------
Note:
1) Initiation of Receiver-side reservation
2) Successful Reservation with& without response request from the
QNI side
3) Unsuccessful Reservation with & without response request from
the QNI side.
4) How to signal unsuccessful reservation for Receiver initiated
reservation(No RII is included, received Response(RSN) should
not be forwarded.
5) We assume that handling of QoS state lifetime expiration event
is based on the local policy of the node. NOTIFY/Reserve(Ton)
messages might be sent to other peers. These issues are not
described in the QoS NSLP draft.
| TOC |
This document does not raise new security considerations. Any security concerns with the QoS NSLP are likely reflected in security related NSIS work already (such as [1]Bosch, S., Karagiannis, G. and A. McDonald, NSLP for Quality-of-Service signaling, October 2004. or [6]Tschofenig, H. and D. Kroeselberg, Security Threats for NSIS, October 2004.).
For the time being, the state machines described in this document do not consider the security aspect of QoS NSLP protocol itself. A future versions of this document will add security relevant states and state transitions.
| TOC |
This document tries to describe possible states and transitions for QoS NSLP according to its current specification [1]Bosch, S., Karagiannis, G. and A. McDonald, NSLP for Quality-of-Service signaling, October 2004., Section 5. We found some issues during the development of the state machines.
| TOC |
Version -01 covers more functionalities of the QoS NSLP. This requires addition and changes of the notations. The main details are as follows:
| TOC |
The authors would like to thank Sven Van den Bosch for his feedback.
| TOC |
| TOC |
| [1] | Bosch, S., Karagiannis, G. and A. McDonald, "NSLP for Quality-of-Service signaling", Internet-Draft draft-ietf-nsis-qos-nslp-05, October 2004. |
| [2] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", March 1997. |
| TOC |
| [3] | Vollbrecht, J., Eronen, P., Petroni, N. and Y. Ohba, "State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator", Internet-Draft draft-ietf-eap-statemachine-06, December 2004 (TXT, PDF). |
| [4] | Institute of Electrical and Electronics Engineers, "DRAFT Standard for Local and Metropolitan Area Networks: Port-Based Network Access Control (Revision)", IEEE 802-1X-REV/D9, January 2004. |
| [5] | Ohba, Y., "State Machines for Protocol for Carrying Authentication for Network Access (PANA)", Internet-Draft draft-ohba-pana-statemachine-01, February 2005. |
| [6] | Tschofenig, H. and D. Kroeselberg, "Security Threats for NSIS", Internet-Draft draft-ietf-nsis-threats-06, October 2004. |
| TOC |
| Xiaoming Fu | |
| University of Goettingen | |
| Telematics Group | |
| Lotzestr. 16-18 | |
| Goettingen 37083 | |
| Germany | |
| Email: | fu@cs.uni-goettingen.de |
| Hannes Tschofenig | |
| Siemens | |
| Otto-Hahn-Ring 6 | |
| Munich, Bayern 81739 | |
| Germany | |
| Email: | Hannes.Tschofenig@siemens.com |
| Tseno Tsenov | |
| Siemens | |
| Otto-Hahn-Ring 6 | |
| Munich, Bayern 81739 | |
| Germany | |
| Email: | tseno.tsenov@mytum.de |
| TOC |
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
Funding for the RFC Editor function is currently provided by the Internet Society.