This I-D seems at odds with RFC8126 over the use of Expert Review in s.8.7
' The responsible AD will appoinht ...'
RFC8126 seems clear that the IESG appoints and may do so in advance and
having more than one is recommended
'the expert will approve or deny..'
RFC8126 seems clear that that is the role of IANA. The expert
recommends and it is then up to IANA to act
'the expert can approve allocations.
No, that is the role of IANA; early allocation is possible but that is
the decision of IANA.
On 24/11/2020 18:23, The IESG wrote:
The IESG has received a request from the IP Performance Measurement WG (ippm)
to consider the following document: - 'Data Fields for In-situ OAM'
<draft-ietf-ippm-ioam-data-11.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2020-12-08. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.
Abstract
In-situ Operations, Administration, and Maintenance (IOAM) records
operational and telemetry information in the packet while the packet
traverses a path between two points in the network. This document
discusses the data fields and associated data types for in-situ OAM.
In-situ OAM data fields can be encapsulated into a variety of
protocols such as NSH, Segment Routing, Geneve, IPv6 (via extension
header), or IPv4. In-situ OAM can be used to complement OAM
mechanisms based on e.g. ICMP or other types of probe packets.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-data/
The following IPR Declarations may be related to this I-D:
https://datatracker.ietf.org/ipr/3526/
_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf-announce
.
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
