[Last-Call] FW: [ippm] Last Call: <draft-ietf-ippm-ioam-data-11.txt> (Data Fields for In-situ OAM) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I agree most parts of the draft is relatively mature and below are some comments. 

1. In the abstract, " 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."  Given none of these has been standardized, it seems improper to
give such a statement. 

2. When applying IOAM for multicast traffic, we identified some issues that are not handled well
by the current IOAM specification and may need some modifications to it. Details can be found in  https://tools.ietf.org/html/draft-song-multicast-telemetry-06

Best regards,
Haoyu

-----Original Message-----
From: ippm <ippm-bounces@xxxxxxxx> On Behalf Of The IESG
Sent: Tuesday, November 24, 2020 10:24 AM
To: IETF-Announce <ietf-announce@xxxxxxxx>
Cc: acm@xxxxxxxxxxxxxxxx; ippm-chairs@xxxxxxxx; draft-ietf-ippm-ioam-data@xxxxxxxx; ippm@xxxxxxxx
Subject: [ippm] Last Call: <draft-ietf-ippm-ioam-data-11.txt> (Data Fields for In-situ OAM) to Proposed Standard


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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-ippm-ioam-data%2F&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7Cbbb0146bf7a147e51d6508d890a658ec%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637418391415318993%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=%2BUFaTczHikH8kYqdi%2F3CmLMgYbtpHp8%2Ferd0ihEbnIU%3D&amp;reserved=0


The following IPR Declarations may be related to this I-D:

   https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fipr%2F3526%2F&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7Cbbb0146bf7a147e51d6508d890a658ec%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637418391415318993%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=ncOk8%2F%2FAswOanSp3FQSnquqZJasbhwPGNUiAjK%2FPbTY%3D&amp;reserved=0






_______________________________________________
ippm mailing list
ippm@xxxxxxxx
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fippm&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7Cbbb0146bf7a147e51d6508d890a658ec%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637418391415318993%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=6PjMoFSxmg4YogDTNuSP%2FgUjfWyqNruCs%2BWCfchz%2BSk%3D&amp;reserved=0

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux