IETF Logo Mail Archive

Re: [ippm] Working Group Last Call: draft-ietf-ippm-ioam-data

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Tue, 21 January 2020 13:40 UTC

Return-Path: <fbrockne@cisco.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 7D3B91200E5 for <ippm@ietfa.amsl.com>; Tue, 21 Jan 2020 05:40:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.399
X-Spam-Level:
X-Spam-Status: No, score=-14.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=jCQAzF3H; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Fx/W0i0i
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 KWPfRJJ8fxvU for <ippm@ietfa.amsl.com>; Tue, 21 Jan 2020 05:40:52 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C71A912007C for <ippm@ietf.org>; Tue, 21 Jan 2020 05:40:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11379; q=dns/txt; s=iport; t=1579614051; x=1580823651; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=h0C4mjzpx2beRJCZ7G/MNrAGb+mhNDtc9ygkawRn+Yk=; b=jCQAzF3HtwKG4HwseqPUEVV779bamwvosrlOvVHo4/bTX61RHFqlbbpH +R6Q0rWfOFxDuRphx2vN2R48hSZDfE5o9ed6SK7zXTs1TEDnsiGxT34gc VUIQ7MT1iHSBh3qbAPDrgXMQacE1dGFwya8/mI7kEnrc3JKOfgfkoBNY5 c=;
IronPort-PHdr: 9a23:Yj3zShxtqek2oabXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuLA1f8J/3sYgQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DXAgBV/iZe/5xdJa1lHAEBAQEBBwEBEQEEBAEBgWoEAQELAYEkL1AFbFggBAsqhXCBaAOLAU6CEZMshGKBQoEQA1QJAQEBDAEBIgsCAQGBY4JdAoISJDcGDgIDDQEBBAEBAQIBBQRthTcMhV4BAQEBAxILEBMBATgPAgEIEAEEAQEoBzIUCQgCBAESCBqCfwQCgX1NAy4BAgyiNgKBOYhhgieCfwEBBYEvARNBgwIDFYIMAwaBOAGFGoZ5GoFBP4ERR4JMPoJkAgIBARiBFAESASErCYMMgiyNbohDmSUKgjmHPY8PgkeICpAmjl6IYZIlAgQCBAUCDgEBBYFoIw1acXAVgycTPRgNh10kg3OFFIU/dAIBAQGBJIo2gjIBAQ
X-IronPort-AV: E=Sophos;i="5.70,346,1574121600"; d="scan'208,217";a="409908741"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Jan 2020 13:40:50 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id 00LDeowE004874 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 21 Jan 2020 13:40:50 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 Jan 2020 07:40:49 -0600
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 Jan 2020 08:40:48 -0500
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 21 Jan 2020 07:40:47 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nPoCYk3/oeu/OhKQc/7GM/H0Ws70NBzBQn7x04HPVy/QZrU8skReCt1IUULYOLARb5RUGeHIiS7EQM+SnQPNputTEZiWb6G8k/fcuDHTFM1R/ovWARVtFS32jKtOmqzseKb/RsD/Q2F8cu/J/1XLwS5hSanbQSDkHg7+iD5Sv5ftl7Kz2M+g3OcapTz3JNgQdXRmqK/3Tk6SeodjBahoAaeALwHoqlEhxKOQGcfrt9ovcXTPkvKy8Z9AaicuiEEv20pz16SoyLKvt7/FK+zQM1BxaWWS1HrbSUVbzXbhUGKMQHQ0bo1OVWeT0Md8kMGKuEI1FrEpX5933lOE1qke7g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4PWORfZob5LrnlAW0K7m7uFImqOuER2vTOBleN50d0M=; b=QObTQx5tzc08HBmPCxD+J5n1g7Ju9iqWTWZ6SI8GGdBBXMvFPwpWZzI5yx6zJavIu56HywGpZc4BOji8sBArnSm6OmMoxt6eM1PAt573RqvynNTvM76NAfR+3RVmmt+RpZ3L8q0+M21jdM/28Y4MXSmSJQk4KXdYfMGP889jdT2fFUop0W8yhUBM62b6gx41z3wBCryEjskOMRKjgQa58cnbAwR2cq/UwzO/bNRmLNJxUdXXB1IM9ViEnNclz4vdB4FV70fysWEe31I6Ltv6EXxk9wUMzgsFFeD2lBMbw8unks4MCVHz+gdbhCLRSp6y3WY7L5I9Jd3T/Lx6YntiOA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4PWORfZob5LrnlAW0K7m7uFImqOuER2vTOBleN50d0M=; b=Fx/W0i0ibirB8lkVeym5FRr97GEAqLKkS4wbOqr0D4Uty4Ee8ZyK9dEL+VGheXVtkXwjWUD7MHWLuxHA8O4l78ot+kt4dc90oBqgdvx5Q+Vo20AJAhBt5dV3s0/yZ+6TU8WGCbQHy5F2cJDxQ5i3iuP0uN0ddkUz0adD6FOpXSs=
Received: from BYAPR11MB2584.namprd11.prod.outlook.com (52.135.228.31) by BYAPR11MB3576.namprd11.prod.outlook.com (20.178.206.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.21; Tue, 21 Jan 2020 13:40:46 +0000
Received: from BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::e4af:d550:3094:46cf]) by BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::e4af:d550:3094:46cf%4]) with mapi id 15.20.2644.027; Tue, 21 Jan 2020 13:40:46 +0000
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: Haoyu Song <haoyu.song@futurewei.com>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [ippm] Working Group Last Call: draft-ietf-ippm-ioam-data
Thread-Index: AQHVxXo6Tdne2RKNvUiZXnvcjdbYaaffx88AgBVrsXA=
Date: Tue, 21 Jan 2020 13:40:46 +0000
Message-ID: <BYAPR11MB25840E74A3C28FFE27F29ACBDA0D0@BYAPR11MB2584.namprd11.prod.outlook.com>
References: <E5725DE6-0637-4D52-BD61-2437D29D3C3B@apple.com> <BYAPR13MB2485F7CBE0DC383BFD63B0B29A3F0@BYAPR13MB2485.namprd13.prod.outlook.com>
In-Reply-To: <BYAPR13MB2485F7CBE0DC383BFD63B0B29A3F0@BYAPR13MB2485.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=fbrockne@cisco.com;
x-originating-ip: [2001:420:44f0:1252:f96f:9d6:18a4:35e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0fab1aa1-867c-47be-4836-08d79e77851c
x-ms-traffictypediagnostic: BYAPR11MB3576:
x-microsoft-antispam-prvs: <BYAPR11MB3576EC153D3605AF4A087CF5DA0D0@BYAPR11MB3576.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0289B6431E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(366004)(346002)(376002)(396003)(136003)(199004)(189003)(71200400001)(7696005)(5660300002)(110136005)(52536014)(316002)(86362001)(64756008)(66556008)(66946007)(66476007)(66446008)(76116006)(81156014)(33656002)(9686003)(81166006)(186003)(8676002)(8936002)(478600001)(53546011)(6506007)(55016002)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3576; H:BYAPR11MB2584.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: q7qOdqa/irdGAdsuaxnvErlbhlDKkErpVLYW/s1oZX//69gbnW4Zl+oQ567yYjw0E59nTYf2KnHw+60R5Caatw6CHKyv2W1UJsQHvC8kyIazyxHUs76bAxv59L4FpttsbJQiLkLN8MXrKxhoHtAER2RoRW+FApV5VDJ8O1ZgSR5oE5/eb9NJS5/keebOgKsh7CEWq8oIO5sFzn4JRjCJXR/n7/M+4e/ZvyTD0qNeaS++sLm5IKPJpx1cSgyzxpaYZuXUb/mSyInGzYulHtY01Osv6KL5ZJ0Y6uey/YmBvTSgJHqhy91a83xjOVxiVl/eR9sTcMAepLLYAkRa5dyhpx2L+bA+JX6grrMJazIPzElhPygpL0ssspCDGHwFzgh9aNpkdG3vKQXuhMQGB3xyV6K1jgBvBN+wPYklznmJVv368iZJt0qNKoWLcP1RwAhXuxBPzMt4vnWyj37TJREoQlNYoiFsq3+i7CtrHgNjF9NLz53gExH7dhkzrKiu7jxSEr5ROYxpKuo1DifS1EitOA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB25840E74A3C28FFE27F29ACBDA0D0BYAPR11MB2584namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0fab1aa1-867c-47be-4836-08d79e77851c
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jan 2020 13:40:46.6445 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: xXow9SGc4E8WnP3DeHDSzwz3hypDDazrF9DKlGqV8q52nz3qBR10U24lGyWqzeJYRJpgRwzBvqY8BViKeZBgLw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3576
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/_bCUWoooDmhLY07DqEjFX00rTfY>
Subject: Re: [ippm] Working Group Last Call: 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: Tue, 21 Jan 2020 13:40:57 -0000

Haoyu,

Thanks. Please see inline ("...FB").

From: ippm <ippm-bounces@ietf.org> On Behalf Of Haoyu Song
Sent: Dienstag, 7. Januar 2020 23:26
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>; IETF IPPM WG <ippm@ietf.org>
Subject: Re: [ippm] Working Group Last Call: draft-ietf-ippm-ioam-data

IPPM and IOAM authors,

I have a question about the variable length opaque data field in the trace option. Does that mean each node may add a variable length field (i.e., use a different scheme ID)?

     "When this field is part of the data field but a node populating
      the field has no opaque state data to report, the Length must be
      set to 0 and the Schema ID must be set to 0xFFFFFF to mean no
      schema."

>From the above description, it seems so.  Then there's a problem. If each node's data has different size, then one can't guarantee that the RemainingLen is exactly 0 when the data overflow happens.

...FB: Could you detail the problem a bit more: Why would the remaining length need to be exactly 0 in case of a data overflow? If RemainingLen < (NodeLen + sizeof(opaque snapshot)) in 4 octet units, then a node would not add data.

Another issue:

    "If IOAM-Trace-Type bit 22 is not set, then NodeLen specifies the
      actual length added by each node.  If IOAM-Trace-Type bit 22 is
      set, then the actual length added by a node would be (NodeLen +
      Opaque Data Length)."

I think the "actual length added by a node would be (NodeLen+ size of opaque state snapshot field). Because the opaque data is only a part of the opaque state snapshot field, and  (opaque data length + 4 byte)=size of opaque state snapshot field.  Some other places need similar clarification.
...FB: Thanks. It makes sense to harmonize the description and at the same time, make it more specific - i.e. match it  to what is already used in section 4.4.1, i.e. "NodeLen + sizeof(opaque snapshot)" in 4 octet units.
Cheers, Frank

Haoyu

From: ippm <ippm-bounces@ietf.org<mailto:ippm-bounces@ietf.org>> On Behalf Of Tommy Pauly
Sent: Tuesday, January 07, 2020 8:48 AM
To: IETF IPPM WG <ippm@ietf.org<mailto:ippm@ietf.org>>
Subject: [ippm] Working Group Last Call: draft-ietf-ippm-ioam-data

Hello IPPM,

Happy New Year! This email starts a working group last call for "Data Fields for In-situ OAM" (https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-data/<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-ippm-ioam-data%2F&data=02%7C01%7Chaoyu.song%40futurewei.com%7C62dfcd2f485d4a27f58208d79391677f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637140125044139853&sdata=Sf3SxjE%2FqK3X760G8c0Tfemu%2FPiqpkpIVHswudQWDTc%3D&reserved=0>).

The last call will end on Tuesday, January 21.. Please reply to ippm@ietf.org<mailto:ippm@ietf.org> with your reviews and comments. Please indicate whether you think this document is ready for publication.

Best,
Tommy (as co-chair)

v2.23.0 | Report a Bug | By Email