From wes@mti-systems.com  Tue Jan 16 12:20:33 2024
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 90A70C1516E2
 for <opsawg@ietfa.amsl.com>; Tue, 16 Jan 2024 12:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, 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]
 autolearn=unavailable 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 smBSQKenL0w2 for <opsawg@ietfa.amsl.com>;
 Tue, 16 Jan 2024 12:20:33 -0800 (PST)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com
 [IPv6:2607:f8b0:4864:20::72b])
 (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 137E6C1516E1
 for <opsawg@ietf.org>; Tue, 16 Jan 2024 12:20:33 -0800 (PST)
Received: by mail-qk1-x72b.google.com with SMTP id
 af79cd13be357-7833a51a1aaso582729385a.0
 for <opsawg@ietf.org>; Tue, 16 Jan 2024 12:20:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=mti-systems-com.20230601.gappssmtp.com; s=20230601; t=1705436432;
 x=1706041232; darn=ietf.org; 
 h=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=gNfIIgVKjnCezg/bGhGOvNpU60gpviZKkQzUEC8K8b4=;
 b=IRYbJvC4pZgnTQeGbmKf+Cnzlx/Z/R0t5UKSLiBgAMTg57iUdAAEcr+DChsV+zgJLP
 5Rw2iY7gGD0nezawDJTUOe5oRdmN01wRw6TtuENa8edewSmfPAwCvQ0jV8XIb1zfecQg
 63m/sYIhVXss274SeFVLR6APHJQEBzuXa4NXlMjm6eOtWv8Vqqejw2K+byMPyXM7i+Ww
 ZgK8sbuSEOvsaXmdYTN6MQfNM/8SxDAvgBlv8DUa9h77d5qCxPGgkXkWjEweSwmBRo4e
 RSG2mwCwM4D1z+Jv4hxn+2qLEJnY2LKJKFOTbY5SjEksJMbA/IZypwqHI9zG4cAlfSml
 1jMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1705436432; x=1706041232;
 h=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=gNfIIgVKjnCezg/bGhGOvNpU60gpviZKkQzUEC8K8b4=;
 b=pJWPMGdZZkDfEsAs1XKv5jMaxOp5mw03FmOPT/vPRnULfE2RYADhT/9txD/cPGs+dl
 hnmxz4woFf29HIUUCB/JxrDSm3LN77/M54fRRqkoEJ2to7Y+HxFQzHFN0qzJX+ehbqX7
 7y04tD2SwzoaJvWAt1J8Vgj/qLs21QaDV0PkNLT6evnMYvrHSVbBUlmFhVM+iMLPJtSs
 LJrOeYR2xqiXLuI+zmFU0z8HrMDdAIva77KKMdzp28mkoeQVq/Es5FJ7JtG1xdl/POeT
 HEKYPygUxxDZ/E2o147VaSExhwtvALJrHmlOB+Ayfd/tb7yQhf6LMX+WXqGGvMHuHBxf
 aKDQ==
X-Gm-Message-State: AOJu0YzZWXULgT88cdQ+ayr55NnsbBZo13gw8k/OvWv9Jcn2CscaVUHb
 FtjMWf7sNnVA52qPYmJ0vZVWwAVvJswP6f7HJiBPPaf1qjLaxA==
X-Google-Smtp-Source: AGHT+IFBqQ/aaFtc6r0oOvu2LaHLNrC5gDnIMHjROELK4Ym6RV5V0t+2EDw7InSICgsD38stDv3Rbg==
X-Received: by 2002:a0c:e292:0:b0:681:34f3:f732 with SMTP id
 r18-20020a0ce292000000b0068134f3f732mr7921628qvl.126.1705436431895; 
 Tue, 16 Jan 2024 12:20:31 -0800 (PST)
Received: from [192.168.1.102] (069-135-001-122.biz.spectrum.com.
 [69.135.1.122]) by smtp.gmail.com with ESMTPSA id
 i20-20020a0cab54000000b00680c8115a43sm4566771qvb.36.2024.01.16.12.20.31
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Tue, 16 Jan 2024 12:20:31 -0800 (PST)
Content-Type: multipart/alternative;
 boundary="------------akdjXwjF5BEjdLN4wbn9yjt2"
Message-ID: <c5ad1a7d-d50a-4a3e-9ae3-2f3fe7afc945@mti-systems.com>
Date: Tue, 16 Jan 2024 15:20:30 -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>
From: Wesley Eddy <wes@mti-systems.com>
In-Reply-To: <DU2PR02MB10160DB7B0CB1DD07B88FE71B88732@DU2PR02MB10160.eurprd02.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/Li5UmbLbRSrowQyEiubRZY6M12s>
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: Tue, 16 Jan 2024 20:20:33 -0000

This is a multi-part message in MIME format.
--------------akdjXwjF5BEjdLN4wbn9yjt2
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 1/16/2024 11:10 AM, mohamed.boucadair@orange.com wrote:
>
> Are you expecting the implementation to have an exhaustive list of all 
> of the ExIDs in use to understand the difference between 2 and 4 byte 
> usage?
>
> */[Med] Yes because otherwise an implem can’t unambiguously identify 
> and extract ExIDs. We do provide a pointer to the registered ExIDs:/*
>
> *//*
>
> */==/*
>
> Additional Information:  See assigned ExIDs at [IANA-TCP-EXIDs].
>
> */== /*
>
> *//*
>
> */Please let me know if you still think a clarification is needed to 
> the draft. Thanks./*
>
New ExIDs are able to be added to the IANA registry at any time, just 
via requesting them.  Is an IPFIX implementation expected to 
periodically fetch the registry and reload its known values?




--------------akdjXwjF5BEjdLN4wbn9yjt2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/16/2024 11:10 AM,
      <a class="moz-txt-link-abbreviated" href="mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com</a> wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:DU2PR02MB10160DB7B0CB1DD07B88FE71B88732@DU2PR02MB10160.eurprd02.prod.outlook.com">
      <p class="MsoNormal">Are you expecting the implementation to have
        an exhaustive list of all of the ExIDs in use to understand the
        difference between 2 and 4 byte usage?<o:p></o:p></p>
      <p class="MsoNormal"><b><i><span
              style="font-family:&quot;Courier New&quot;" lang="EN-US">[Med]
              Yes because otherwise an implem can’t unambiguously
              identify and extract ExIDs. We do provide a pointer to the
              registered ExIDs:<o:p></o:p></span></i></b></p>
      <p class="MsoNormal"><b><i><span
              style="font-family:&quot;Courier New&quot;" lang="EN-US"><o:p> </o:p></span></i></b></p>
      <p class="MsoNormal"><b><i><span
              style="font-family:&quot;Courier New&quot;" lang="EN-US">==<o:p></o:p></span></i></b></p>
      <p class="MsoNormal" style="background:white"><span
style="font-size:9.5pt;font-family:&quot;var(--bs-font-monospace)&quot;,serif;color:#212529"
          lang="EN-US">Additional Information:  See assigned ExIDs at
          [IANA-TCP-EXIDs].<o:p></o:p></span></p>
      <p class="MsoNormal"><b><i><span
              style="font-family:&quot;Courier New&quot;" lang="EN-US">==
              <o:p></o:p></span></i></b></p>
      <p class="MsoNormal"><b><i><span
              style="font-family:&quot;Courier New&quot;" lang="EN-US"><o:p> </o:p></span></i></b></p>
      <p class="MsoNormal"><b><i><span
              style="font-family:&quot;Courier New&quot;" lang="EN-US">Please
              let me know if you still think a clarification is needed
              to the draft. Thanks.</span></i></b></p>
    </blockquote>
    <p>New ExIDs are able to be added to the IANA registry at any time,
      just via requesting them.  Is an IPFIX implementation expected to
      periodically fetch the registry and reload its known values?</p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------akdjXwjF5BEjdLN4wbn9yjt2--

