RFC Editor: We've completed the actions for the following RFC-to-be:
draft-ietf-ippm-ioam-data-integrity-20 ACTION 1: We've added the following entries to the IOAM Option-Type registry: 64 IOAM Integrity-Protected Pre-allocated Trace Option-Type Pre-allocated Trace with Integrity Protection [RFC-ietf-ippm-ioam-data-integrity-20, Section 4] 65 IOAM Integrity-Protected Incremental Trace Option-Type Incremental Trace with Integrity Protection [RFC-ietf-ippm-ioam-data-integrity-20, Section 4] 66 IOAM Integrity-Protected POT Option-Type POT with Integrity Protection [RFC-ietf-ippm-ioam-data-integrity-20, Section 4] 67 IOAM Integrity-Protected E2E Option-Type E2E with Integrity Protection [RFC-ietf-ippm-ioam-data-integrity-20, Section 4] Please see https://www.iana.org/assignments/ioam ACTION 2: We've created the following registry and placed in the "In Situ OAM (IOAM)" registry group: IOAM Integrity Protection Methods Registration Procedure(s): IETF Review Reference: [RFC-ietf-ippm-ioam-data-integrity-20] ID Description Protected Header Fields Reference 0x00 AES-GMAC, 16-octet (full) Authentication Tag, 12-octet Initialization Vector. Pre-allocated Trace and Incremental Trace: - Namespace-ID (mask = 0xffff) - NodeLen + Flags + RemainingLen (mask = 0xfb00) - IOAM Trace-Type (mask = 0xffffff) - Reserved (mask = 0x00) POT: - Namespace-ID (mask = 0xffff) - IOAM-POT-Type (mask = 0xff) - IOAM-POT-Flags (mask = 0x00) E2E: - Namespace-ID (mask = 0xffff) - IOAM-E2E-Type (mask = 0xffff) [RFC-ietf-ippm-ioam-data-integrity-20, Section 5] 0x01-0xFE Unassigned 0xFF Reserved [RFC-ietf-ippm-ioam-data-integrity-20] Please see https://www.iana.org/assignments/ioam Please let us know when an RFC number has been assigned and the date of publication by sending a new message to <[email protected]>. Thanks, Sabrina Tanamal IANA -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
