[ippm] Issue with draft-ietf-ippm-ioam-data

Stewart Bryant <stewart.bryant@gmail.com> Thu, 27 May 2021 15:45 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 012743A13EF; Thu, 27 May 2021 08:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M_uQhkmowPE3; Thu, 27 May 2021 08:45:22 -0700 (PDT)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2742C3A13EE; Thu, 27 May 2021 08:45:21 -0700 (PDT)
Received: by mail-wr1-x433.google.com with SMTP id r10so324376wrj.11; Thu, 27 May 2021 08:45:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:date:cc:to; bh=EWB9hM72IiETzpsmC+cRIQWQujYnTIaS0gPRoMjy/U0=; b=qa3TZGpm8Cw0jCtJXPw4grs0XzcT3kYQKhEpH10lk07gn7+AvsXOQYhcofxCUX+PyE 2/0+uywQtvoChEoIT4a3cVRH0rujrKOpSyniMrhBW/oyZ90ZVJ4KId0/95Nn0BSEGstc zdgbjHA/gD/4v+v1KiBXh+yxS+ZBjOB4d13ugO63lQNrMRAuV9LUEMRCjghHdhMZSRcg Dda/0B2l5/wndyR30AFsRJ5QB0XhDsqZFsoaR91fzApmIPNPZhM5KpsXm/WiNlLX23o5 rcnP1Bq1m7X+I2RPbn8uI/GC8UEwGBCblCKuJUlvhrGUKaxO27M+WfCk5Nt7JewbRWu9 vEtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to; bh=EWB9hM72IiETzpsmC+cRIQWQujYnTIaS0gPRoMjy/U0=; b=SIzJIga99jcPxvb6endS/X7EvAh9tO2Wjo+KhYilAWLuZGAlNBHcGt9e618ABQqdIU sq36sPsuZ8Ytx+WY/6i9tg04uYUnHQua1ljSW3PCUFNlUc+p0sjHd2VgEDEVtKEGuihE OiEau+Xga6KhNEIoFNCfC7bIG1JfdKF+hmB3yB8LfzIbwBJwXMT+z8M00W2MqCeU+0AP FOHdQsaWajipTbBu+QF/2e3Fff9i8/KSMFMihBP56953rgjd+2QdH2A+OXzOnjAXGwSD 73OMx+WXb5G+FuE2mtHjnloW+W+xqrvVOb4a/7TJmcnmHBqK2oQgHCT6Y0E7g2Wc1IQ2 jIAw==
X-Gm-Message-State: AOAM533Evt2bz71diUTTyAl8lHPwA1WgarEQ56XYDQXFgFUkEjoJBBGJ juHEwoCklJA/QoloENrL/DAJrF8CtXI=
X-Google-Smtp-Source: ABdhPJxt8AE0WnYmtzOCMeJmgbNbJYimkvzAroOGBvyj6wBr7EeOW/O+bzsdQyg3JiQeFJFrX/QYKQ==
X-Received: by 2002:adf:f907:: with SMTP id b7mr4077834wrr.357.1622130319193; Thu, 27 May 2021 08:45:19 -0700 (PDT)
Received: from [192.168.8.155] ([85.255.234.115]) by smtp.gmail.com with ESMTPSA id i1sm3613031wrp.51.2021.05.27.08.45.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 May 2021 08:45:18 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_39711A6C-7507-4CFF-9D05-9D35126EFA75"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
Message-Id: <F74B98FF-E08E-4F8C-B23E-C327F4A7A1A5@gmail.com>
Date: Thu, 27 May 2021 16:45:17 +0100
To: IESG <iesg@ietf.org>, draft-ietf-ippm-ioam-data@ietf.org, ippm@ietf.org, ippm-chairs@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/hT3AKo442buyN557aZqmwjTLsGE>
Subject: [ippm] Issue with draft-ietf-ippm-ioam-data
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2021 15:45:24 -0000

I have been looking at "Data Fields for In-situ OAM" draft-ietf-ippm-ioam-data-12 as part of some work that we are doing in MPLS.

The following came up in an MPLS design team meeting:

In para 5.4 IOAM Trace Option-Types

In the section on Incremental Trace-Option: there is the text:

The IOAM
      encapsulating node allocates space for the Incremental Trace
      Option-Type. 

One interpretation of this is that the ingress node preallocates space that the P nodes draw down on as needed to include their IOAM information.

Others thought that the the P nodes did an insertion into the packet by essentially moving all previous bytes to the “left” and adding in new information.

This clearly needs to be clarified in the text.

I also think the MTU text needs to be expanded because P routers now need to understand the MTU which was something that was not previously required.

Best regards

Stewart