RFC Errata
Found 1 record.
Status: Rejected (1)
RFC 5515, "Layer 2 Tunneling Protocol (L2TP) Access Line Information Attribute Value Pair (AVP) Extensions", May 2009
Source of RFC: IETF - NON WORKING GROUPArea Assignment: int
Errata ID: 4620
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Jewgenij Bytschkow
Date Reported: 2016-02-17
Rejected by: Eric Vyncke
Date Rejected: 2023-08-03
Section 4.1. says:
The following AVPs MUST be present in the CSUN:
Message Type
Connect Speed Update (more than one may be present in the CSUN)
Note that the LAC MUST NOT include a Connect Speed Update AVP for
which it did not send a Connect Speed Update Enable AVP in the prior
Incoming-Call-Request (ICRQ) control message for the session.
It should say:
The following AVPs MUST be present in the CSUN:
Message Type
Connect Speed Update (more than one may be present in the CSUN)
If a CSUN message contains two or more Connect Speed Update AVPs
(as updates for two or more sessions in the tunnel), the Session ID
of the L2TP control message MUST be 0. It is because a CSUN message
with several Connect Speed Update AVPs is related to several sessions
in the tunnel, rather than to a single session.
Note that the LAC MUST NOT include a Connect Speed Update AVP for
which it did not send a Connect Speed Update Enable AVP in the prior
Incoming-Call-Request (ICRQ) control message for the session.
Notes:
The suggested additional MUST requirement is important for LAC-LNS
operation in order to avoid arbitrary, opposite and conflicting
interpretations and implementations of the RFC5515 on LAC and LNS.
--VERIFIER NOTES--
Section 4.1.1.2 of RFC 3931 has reserved that value of 0 for Session ID, this specific value cannot be re-used.