[Taps] [Errata Verified] RFC8095 (6710)

2022-01-27 Thread RFC Errata System 
The following errata report has been verified for RFC8095,
"Services Provided by IETF Transport Protocols and Congestion Control 
Mechanisms". 

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6710

--
Status: Verified
Type: Editorial

Reported by: Jie Zhang 
Date Reported: 2021-10-15
Verified by: RFC Editor  

Section: 3.11.1

Original Text
-
Error detection and verification of the protocol control information
relies on the on the underlying transport (e.g., UDP checksum).

Corrected Text
--
Error detection and verification of the protocol control information
relies on the underlying transport (e.g., UDP checksum).

Notes
-
There is a redundant "on the".

--
RFC8095 (draft-ietf-taps-transports-14)
--
Title   : Services Provided by IETF Transport Protocols and 
Congestion Control Mechanisms
Publication Date: March 2017
Author(s)   : G. Fairhurst, Ed., B. Trammell, Ed., M. Kuehlewind, Ed.
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Editorial Errata Reported] RFC8095 (6710)

2021-10-15 Thread RFC Errata System 
The following errata report has been submitted for RFC8095,
"Services Provided by IETF Transport Protocols and Congestion Control 
Mechanisms".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6710

--
Type: Editorial
Reported by: Jie Zhang 

Section: 3.11.1

Original Text
-
Error detection and verification of the protocol control information
relies on the on the underlying transport (e.g., UDP checksum).

Corrected Text
--
Error detection and verification of the protocol control information
relies on the underlying transport (e.g., UDP checksum).

Notes
-
There is a redundant "on the".

Instructions:
-
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--
RFC8095 (draft-ietf-taps-transports-14)
--
Title   : Services Provided by IETF Transport Protocols and 
Congestion Control Mechanisms
Publication Date: March 2017
Author(s)   : G. Fairhurst, Ed., B. Trammell, Ed., M. Kuehlewind, Ed.
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Held for Document Update] RFC8304 (6371)

2021-01-19 Thread RFC Errata System 
The following errata report has been held for document update 
for RFC8304, "Transport Features of the User Datagram Protocol (UDP) and 
Lightweight UDP (UDP-Lite)". 

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6371

--
Status: Held for Document Update
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-26
Held by: Martin Duke (IESG)

Section: 3.1

Original Text
-
   ERROR_REPORT:  The ERROR_REPORT event informs an application of "soft
  errors", including the arrival of an ICMP or ICMPv6 error message.
  Section 4.1.4 of the requirements for Internet hosts [RFC1122]
  states that "UDP MUST pass to the application layer all ICMP error
  messages that it receives from the IP layer."  For example, this
  event is required to implement ICMP-based Path MTU Discovery
  [RFC1191] [RFC8201].  UDP applications must perform a CONNECT to
  receive ICMP errors.


Corrected Text
--
   ERROR_REPORT:  The ERROR_REPORT event informs an application of "soft
  errors", including the arrival of an ICMP or ICMPv6 error message.
  Section 4.1.3.3 of the requirements for Internet hosts [RFC1122]
  states that "UDP MUST pass to the application layer all ICMP error
  messages that it receives from the IP layer."  For example, this
  event is required to implement ICMP-based Path MTU Discovery
  [RFC1191] [RFC8201].  UDP applications must perform a CONNECT to
  receive ICMP errors.


Notes
-
Incorrect reference to RFC 1122

--
RFC8304 (draft-ietf-taps-transports-usage-udp-07)
--
Title   : Transport Features of the User Datagram Protocol (UDP) 
and Lightweight UDP (UDP-Lite)
Publication Date: February 2018
Author(s)   : G. Fairhurst, T. Jones
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Held for Document Update] RFC8304 (6370)

2021-01-19 Thread RFC Errata System 
The following errata report has been held for document update 
for RFC8304, "Transport Features of the User Datagram Protocol (UDP) and 
Lightweight UDP (UDP-Lite)". 

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6370

--
Status: Held for Document Update
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-26
Held by: Martin Duke (IESG)

Section: 3.1

Original Text
-
   GET_ECN:  The GET_ECN primitive is a network-layer function that
  returns the value of the ECN field in the IP header of a received
  UDP datagram.  Section 3.1.5 of [RFC8085] states that a UDP
  receiver "MUST check the ECN field at the receiver for each UDP
  datagram that it receives on this port", requiring the UDP
  receiver API to pass the received ECN field up to the application
  layer to enable appropriate congestion feedback.

Corrected Text
--
   GET_ECN:  The GET_ECN primitive is a network-layer function that
  returns the value of the ECN field in the IP header of a received
  UDP datagram.  Section 3.1.7 of [RFC8085] states that a UDP
  receiver "MUST check the ECN field at the receiver for each UDP
  datagram that it receives on this port", requiring the UDP
  receiver API to pass the received ECN field up to the application
  layer to enable appropriate congestion feedback.

Notes
-
Incorrect reference to RFC 8085

--
RFC8304 (draft-ietf-taps-transports-usage-udp-07)
--
Title   : Transport Features of the User Datagram Protocol (UDP) 
and Lightweight UDP (UDP-Lite)
Publication Date: February 2018
Author(s)   : G. Fairhurst, T. Jones
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6400)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6400

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6399)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6399

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6396)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6396

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6392)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6392

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6390)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6390

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6374)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6374

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6398)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6398

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6391)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6391

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   Duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6397)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6397

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6395)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6395

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   duplicate of 6373

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Rejected] RFC8303 (6394)

2021-01-19 Thread RFC Errata System 
The following errata report has been rejected for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6394

--
Status: Rejected
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Rejected by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or
 --VERIFIER NOTES-- 
   Duplicate

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Held for Document Update] RFC8303 (6373)

2021-01-19 Thread RFC Errata System 
The following errata report has been held for document update 
for RFC8303, "On the Usage of Transport Features Provided by IETF Transport 
Protocols". 

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6373

--
Status: Held for Document Update
Type: Editorial

Reported by: Nikolai Malykh 
Date Reported: 2020-12-29
Held by: Martin Duke (IESG)

Section: 4.1

Original Text
-
   o  SET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Set_TTL' and 'Set_IPV6_Unicast_Hops'

  Parameters: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to change the IPv4 TTL of
  IPv6 Hop Count value for outgoing UDP(-Lite) datagrams.



Corrected Text
--
   o  SET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Set_TTL' and 'Set_IPV6_Unicast_Hops'

  Parameters: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to change the IPv4 TTL or
  IPv6 Hop Count value for outgoing UDP(-Lite) datagrams.



Notes
-
typo: of instead or

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Editorial Errata Reported] RFC8303 (6374)

2020-12-29 Thread RFC Errata System 
The following errata report has been submitted for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6374

--
Type: Editorial
Reported by: Nikolai Malykh 

Section: 4.1

Original Text
-
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL of the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Corrected Text
--
   o  GET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Get_TTL' and 'Get_IPV6_Unicast_Hops'

  Returns: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to read the IPv4 TTL or the
  IPv6 Hop Count value from a received UDP(-Lite) datagram.


Notes
-
typo: of instead or

Instructions:
-
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Editorial Errata Reported] RFC8303 (6373)

2020-12-29 Thread RFC Errata System 
The following errata report has been submitted for RFC8303,
"On the Usage of Transport Features Provided by IETF Transport Protocols".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6373

--
Type: Editorial
Reported by: Nikolai Malykh 

Section: 4.1

Original Text
-
   o  SET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Set_TTL' and 'Set_IPV6_Unicast_Hops'

  Parameters: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to change the IPv4 TTL of
  IPv6 Hop Count value for outgoing UDP(-Lite) datagrams.



Corrected Text
--
   o  SET_TTL.UDP(-Lite) (IPV6_UNICAST_HOPS):

  Pass 1 primitive/event: 'Set_TTL' and 'Set_IPV6_Unicast_Hops'

  Parameters: IPv4 TTL value or IPv6 Hop Count value

  Comments: this allows an application to change the IPv4 TTL or
  IPv6 Hop Count value for outgoing UDP(-Lite) datagrams.



Notes
-
typo: of instead or

Instructions:
-
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--
RFC8303 (draft-ietf-taps-transports-usage-09)
--
Title   : On the Usage of Transport Features Provided by IETF 
Transport Protocols
Publication Date: February 2018
Author(s)   : M. Welzl, M. Tuexen, N. Khademi
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Editorial Errata Reported] RFC8304 (6371)

2020-12-26 Thread RFC Errata System 
The following errata report has been submitted for RFC8304,
"Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP 
(UDP-Lite)".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6371

--
Type: Editorial
Reported by: Nikolai Malykh 

Section: 3.1

Original Text
-
   ERROR_REPORT:  The ERROR_REPORT event informs an application of "soft
  errors", including the arrival of an ICMP or ICMPv6 error message.
  Section 4.1.4 of the requirements for Internet hosts [RFC1122]
  states that "UDP MUST pass to the application layer all ICMP error
  messages that it receives from the IP layer."  For example, this
  event is required to implement ICMP-based Path MTU Discovery
  [RFC1191] [RFC8201].  UDP applications must perform a CONNECT to
  receive ICMP errors.


Corrected Text
--
   ERROR_REPORT:  The ERROR_REPORT event informs an application of "soft
  errors", including the arrival of an ICMP or ICMPv6 error message.
  Section 4.1.3.3 of the requirements for Internet hosts [RFC1122]
  states that "UDP MUST pass to the application layer all ICMP error
  messages that it receives from the IP layer."  For example, this
  event is required to implement ICMP-based Path MTU Discovery
  [RFC1191] [RFC8201].  UDP applications must perform a CONNECT to
  receive ICMP errors.


Notes
-
Incorrect reference to RFC 1122

Instructions:
-
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--
RFC8304 (draft-ietf-taps-transports-usage-udp-07)
--
Title   : Transport Features of the User Datagram Protocol (UDP) 
and Lightweight UDP (UDP-Lite)
Publication Date: February 2018
Author(s)   : G. Fairhurst, T. Jones
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Editorial Errata Reported] RFC8304 (6370)

2020-12-26 Thread RFC Errata System 
The following errata report has been submitted for RFC8304,
"Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP 
(UDP-Lite)".

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6370

--
Type: Editorial
Reported by: Nikolai Malykh 

Section: 3.1

Original Text
-
   GET_ECN:  The GET_ECN primitive is a network-layer function that
  returns the value of the ECN field in the IP header of a received
  UDP datagram.  Section 3.1.5 of [RFC8085] states that a UDP
  receiver "MUST check the ECN field at the receiver for each UDP
  datagram that it receives on this port", requiring the UDP
  receiver API to pass the received ECN field up to the application
  layer to enable appropriate congestion feedback.

Corrected Text
--
   GET_ECN:  The GET_ECN primitive is a network-layer function that
  returns the value of the ECN field in the IP header of a received
  UDP datagram.  Section 3.1.7 of [RFC8085] states that a UDP
  receiver "MUST check the ECN field at the receiver for each UDP
  datagram that it receives on this port", requiring the UDP
  receiver API to pass the received ECN field up to the application
  layer to enable appropriate congestion feedback.

Notes
-
Incorrect reference to RFC 8085

Instructions:
-
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--
RFC8304 (draft-ietf-taps-transports-usage-udp-07)
--
Title   : Transport Features of the User Datagram Protocol (UDP) 
and Lightweight UDP (UDP-Lite)
Publication Date: February 2018
Author(s)   : G. Fairhurst, T. Jones
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Editorial Errata Reported] RFC8095 (5285)

2018-03-12 Thread RFC Errata System 
The following errata report has been submitted for RFC8095,
"Services Provided by IETF Transport Protocols and Congestion Control 
Mechanisms".

--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5285

--
Type: Editorial
Reported by: Wesley Eddy 

Section: section 3.1

Original Text
-
3.1 Transport Control Protocol (TCP)

Corrected Text
--
3.1 Transmission Control Protocol (TCP)

Notes
-
The acronym-expansion for TCP is incorrect in the section title, but is correct 
in other text within the document.

Instructions:
-
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--
RFC8095 (draft-ietf-taps-transports-14)
--
Title   : Services Provided by IETF Transport Protocols and 
Congestion Control Mechanisms
Publication Date: March 2017
Author(s)   : G. Fairhurst, Ed., B. Trammell, Ed., M. Kuehlewind, Ed.
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] [Errata Verified] RFC8095 (5285)

2018-03-12 Thread RFC Errata System 
The following errata report has been verified for RFC8095,
"Services Provided by IETF Transport Protocols and Congestion Control 
Mechanisms". 

--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5285

--
Status: Verified
Type: Editorial

Reported by: Wesley Eddy 
Date Reported: 2018-03-12
Verified by: Mirja Kühlewind (IESG)

Section: section 3.1

Original Text
-
3.1 Transport Control Protocol (TCP)

Corrected Text
--
3.1 Transmission Control Protocol (TCP)

Notes
-
The acronym-expansion for TCP is incorrect in the section title, but is correct 
in other text within the document.

--
RFC8095 (draft-ietf-taps-transports-14)
--
Title   : Services Provided by IETF Transport Protocols and 
Congestion Control Mechanisms
Publication Date: March 2017
Author(s)   : G. Fairhurst, Ed., B. Trammell, Ed., M. Kuehlewind, Ed.
Category: INFORMATIONAL
Source  : Transport Services
Area: Transport
Stream  : IETF
Verifying Party : IESG

___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps