I-D Action: draft-song-ippm-ioam-ipv6-support-02.txt
internet-drafts@ietf.org Mon, 04 January 2021 18:04 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D0A5B3A0F4A for <i-d-announce@ietf.org>; Mon, 4 Jan 2021 10:04:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-song-ippm-ioam-ipv6-support-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160978345280.4247.9294624871618312828@ietfa.amsl.com>
Date: Mon, 04 Jan 2021 10:04:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/amzj-luVc5WVi5um_riCpHM3E8E>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 18:04:15 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Approaches on Supporting IOAM in IPv6 Authors : Haoyu Song Zhenbin Li Shuping Peng James Guichard Filename : draft-song-ippm-ioam-ipv6-support-02.txt Pages : 11 Date : 2021-01-04 Abstract: It has been proposed to encapsulate IOAM tracing option data fields in IPv6 HbH options header. However, due to size of the trace data and the extension header location in the IPv6 packets, the proposal creates practical challenges for implementation, especially when other extension headers, such as a routing header, also exist and require in-network processing. We propose several alternative approaches to address this challenge, including separating the IOAM trace data to a different extension header, using the postcard-based telemetry (e.g., IOAM DEX) instead, and applying the segment IOAM trace export scheme, based on the network scenario and application requirements. We discuss the pros and cons of each approach and hope to foster standard convergence and industry adoption. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-song-ippm-ioam-ipv6-support/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-song-ippm-ioam-ipv6-support-02 https://datatracker.ietf.org/doc/html/draft-song-ippm-ioam-ipv6-support-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-song-ippm-ioam-ipv6-support-02 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- I-D Action: draft-song-ippm-ioam-ipv6-support-02.… internet-drafts