Subject: [ippm] Fw:New Version Notification for draft-xiao-ippm-ioam-conf-state-08.txt

From: <[email-masked]>
Date: Thu, 21 Jan 2021 11:39:21 +0800 (CST)

Hi IPPM WG,

As suggested by the WG Chairs Tommy and Ian, we submitted an updated version of this document, in order to address the comments received during the adoption call.

There are three major changes made in this update, as follows:
1. Explain how this work interacts with and could overlap with YANG or IGP, and when the various mechanisms are appropriate.
2. Add IANA registry for SoR Capability and TSF+TSL Capability, at the meantime explain why we don't have IANA registry for new types and sub-types.
3. Improve the Security Considerations section, describing possible security mechanisms to protect integrity and confidentiality.

Best Regards,
Xiao Min

原始邮件

发件人：[email-masked]
收件人：Greg Mirsky;Lei Bo;肖敏10093570;
日 期 ：2021年01月21日 11:08
主 题 ：New Version Notification for draft-xiao-ippm-ioam-conf-state-08.txt

A new version of I-D, draft-xiao-ippm-ioam-conf-state-08.txt
has been successfully submitted by Xiao Min and posted to the
IETF repository.
 
Name:        draft-xiao-ippm-ioam-conf-state
Revision:    08
Title:        Echo Request/Reply for Enabled In-situ OAM Capabilities
Document date:    2021-01-20
Group:        ippm
Pages:        18
URL:            https://www.ietf.org/archive/id/draft-xiao-ippm-ioam-conf-state-08.txt
Status:         https://datatracker.ietf.org/doc/draft-xiao-ippm-ioam-conf-state/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-xiao-ippm-ioam-conf-state
Htmlized:       https://tools.ietf.org/html/draft-xiao-ippm-ioam-conf-state-08
Diff:           https://www.ietf.org/rfcdiff?url2=draft-xiao-ippm-ioam-conf-state-08
 
Abstract:
   This document describes an extension to the echo request/reply
   mechanisms used in IPv6, MPLS and SFC environments, which can be used
   within an IOAM domain, allowing the IOAM encapsulating node to
   acquire the enabled IOAM capabilities of each IOAM transit node and/
   or IOAM decapsulating node.

 
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
 
The IETF Secretariat