I-D Action: draft-song-ippm-ioam-ipv6-support-00.txt
internet-drafts@ietf.org Tue, 03 March 2020 18:10 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 DEC743A24C9 for <i-d-announce@ietf.org>; Tue, 3 Mar 2020 10:10:13 -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-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.119.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158325901382.7698.4629317770084762159@ietfa.amsl.com>
Date: Tue, 03 Mar 2020 10:10:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/8M1kR66JAbXFYhFigmePsKmRdzM>
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: Tue, 03 Mar 2020 18:10:14 -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 Filename : draft-song-ippm-ioam-ipv6-support-00.txt Pages : 10 Date : 2020-03-03 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 its location in the IPv6 header packets, this arrangement creates practical challenges for implementation, especially when other extension headers, such as 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 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-00 https://datatracker.ietf.org/doc/html/draft-song-ippm-ioam-ipv6-support-00 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-00.… internet-drafts