IETF Logo Mail Archive

Re: [OPSAWG] Tsvart early review of draft-ietf-opsawg-ipfix-tcpo-v6eh-05

Wesley Eddy <wes@mti-systems.com> Wed, 17 January 2024 13:25 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BFB0C14F5F8 for <opsawg@ietfa.amsl.com>; Wed, 17 Jan 2024 05:25:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mti-systems-com.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S_a63xgTMrOK for <opsawg@ietfa.amsl.com>; Wed, 17 Jan 2024 05:24:59 -0800 (PST)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 840E2C14CF18 for <opsawg@ietf.org>; Wed, 17 Jan 2024 05:24:59 -0800 (PST)
Received: by mail-qk1-x72e.google.com with SMTP id af79cd13be357-7831ed13d39so881184785a.0 for <opsawg@ietf.org>; Wed, 17 Jan 2024 05:24:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20230601.gappssmtp.com; s=20230601; t=1705497898; x=1706102698; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=i8J5pAeCSVNVOE2bzxM2jFCOxKkxnUdhWTHPi9ndMcs=; b=KVhI5YEw9A6F9aMPPz+w3ox5whLcMk3ujYd5QmrPg81zsYpK3L+2LhylcxQfn/kzB0 hWQ3S1ECzeTWHNWPLugY2H074yd3mVbGEax97ZQ/f8ccNzHM+j5vCg6bIXlGV8jaUlHc TCWfCRZpM5KdLjs2B4PXG+8ELKTZoG4SWudccZxck6yMQ5DoxZ0UJitp91FiOYFBRJrS gidRUydn09hI51yEQ5ysLmmEDgNX7GHMsR41SocCA2zV9DBMB3aszEbZnyNRmV5tIYyy 9fVnP+4DGzlJrgjvSz/4xiwakVt5j3/Y9kMxWr9H1co2+LOmiu+2NubqO9Nhiiq3JM8J h7kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705497898; x=1706102698; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=i8J5pAeCSVNVOE2bzxM2jFCOxKkxnUdhWTHPi9ndMcs=; b=KCUBWqIho06fQj6u7wV7b7dG5BBow0Ws5cKRRMtSbexiR7XFDJEshGQScJVAcIUEwr tE7E8P+7RTGbhZi5keJ0DCzFts/w4d/YBXYnIXdH7RQz6J6VCtIdYT9wXBuKHLLson2N nV1g77EeqzSSzLFvfz1wvw1tF+VuQC1wPx4EZ7KtfDuiIU+h/Jp8wVqOVQBhSgwvglEs N2/5cr6nwUINslpvIIwnUd3z1EoMcBsHMwEyh+i8rDm2nLxy65EKOi0dD1asJcpLVe0v 536CjOtx2C/MTjFBfGzaX4W0Vzk4aAB+Se27xZ39i53oWgSc5XZPgunYYUNAUtLAR73d 5QLg==
X-Gm-Message-State: AOJu0YzhFf9anYrL88shxkTSsmNKypSMktX34RqKp9ieEK8/k+SzyvLr +bM2rrDS+Xn0zPL6WFc50Q8EToINw0tWiA==
X-Google-Smtp-Source: AGHT+IHXiulMA3aSnhZo7oe11m562oj8slTnMu2EHlVWXZi1FCObFwpZ8KPuJeAlwv4MHb25uq/3PQ==
X-Received: by 2002:a05:6214:21ce:b0:681:2616:8f1b with SMTP id d14-20020a05621421ce00b0068126168f1bmr12763442qvh.45.1705497898540; Wed, 17 Jan 2024 05:24:58 -0800 (PST)
Received: from [192.168.1.17] (066-061-072-087.res.spectrum.com. [66.61.72.87]) by smtp.gmail.com with ESMTPSA id ei16-20020ad45a10000000b006816fa492f3sm1308009qvb.61.2024.01.17.05.24.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Jan 2024 05:24:58 -0800 (PST)
Message-ID: <e13aafdf-dd1e-468d-a822-c04ee240dcc0@mti-systems.com>
Date: Wed, 17 Jan 2024 08:24:56 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: mohamed.boucadair@orange.com, "tsv-art@ietf.org" <tsv-art@ietf.org>
Cc: "draft-ietf-opsawg-ipfix-tcpo-v6eh.all@ietf.org" <draft-ietf-opsawg-ipfix-tcpo-v6eh.all@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <170421960173.20693.6271938298987993574@ietfa.amsl.com> <DU2PR02MB10160E07E26F7B486D45DFDFE886C2@DU2PR02MB10160.eurprd02.prod.outlook.com> <faf715ff-dae2-49cf-b29d-daca4cae73a7@mti-systems.com> <DU2PR02MB10160DB7B0CB1DD07B88FE71B88732@DU2PR02MB10160.eurprd02.prod.outlook.com> <c5ad1a7d-d50a-4a3e-9ae3-2f3fe7afc945@mti-systems.com> <DU2PR02MB1016044FD09FADB216F965C2988722@DU2PR02MB10160.eurprd02.prod.outlook.com>
From: Wesley Eddy <wes@mti-systems.com>
In-Reply-To: <DU2PR02MB1016044FD09FADB216F965C2988722@DU2PR02MB10160.eurprd02.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/oFwa8NeiQpwSpfssWDexIctwihU>
Subject: Re: [OPSAWG] Tsvart early review of draft-ietf-opsawg-ipfix-tcpo-v6eh-05
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jan 2024 13:25:03 -0000

On 1/17/2024 3:34 AM, mohamed.boucadair@orange.com wrote:
> [Med] This can be part of regular code updates. Please note that this 
> is not unusual in ipfix (see for example ipv4Options, natevent, etc. 
> in https://www.iana.org/assignments/ipfix/ipfix.xhtml which depend on 
> an IANA registry).

Ok; do you think the document should explain this in a sentence or two 
for implementers?

If they are not all familiar with details of how ExIDs are used, then it 
seems like a stretch to assume they'll all understand that products need 
to be designed to periodically update ExID definitions.

v2.46.0 | Report a Bug | By Email | System Status