From nobody Fri Oct 28 07:35:32 2022 Return-Path: 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 64A2FC14EB1C for ; Fri, 28 Oct 2022 07:35:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.103 X-Spam-Level: X-Spam-Status: No, score=-2.103 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aiven.io 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 KRbI6itblgV1 for ; Fri, 28 Oct 2022 07:35:25 -0700 (PDT) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 D768EC14CF0B for ; Fri, 28 Oct 2022 07:35:24 -0700 (PDT) Received: by mail-ej1-x633.google.com with SMTP id k2so13431274ejr.2 for ; Fri, 28 Oct 2022 07:35:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aiven.io; s=google; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=hVhdBxYGEg8ZOkHlkvzeRC/7T8Zmx5ony5PY2/X5rX0=; b=nT58F61QiVxBnpN0a0722ieuuPiR6o8MBl8QBO1Hr9vl7REgTuZ9XxOALdFT3xpH3Z GKbKbn1n0sjDYmqGT7P/ETK6sqUWyJZpS0bfONY2ik2Ovm7ldDVWyENWi3WqZoK/CTdL Ot9M2YGHweOJezQEz2L0Oihctewg6WsfsBIfM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=hVhdBxYGEg8ZOkHlkvzeRC/7T8Zmx5ony5PY2/X5rX0=; b=UXyDneaP6PfTE2sia/Pqxv+SyLd4nyhhVyQBZHILxbydVKuBWG/T4AwbFsLHVIdVPS XD9L0IGz/rqzitZAPJFVhif4/1vp134krvAozMKsXRQnRkvtMDN3OhmOQzakRnZQmt0Q agXkvVruaALRemgjhkRpcF2NkDfVX2O93dDACyr1BlyoLb3WtfPaTWFcgPjdrcFHijEK 8idyR9LfTL687z0Ao8iRNw4QjTfVCqpJ8uPrnhGpQDpSFwwOl8vyUlLDDgW3rbkxSOea Fud2rZje1qUuUQcDIhdt/aloKA+skxpwZYKh2vrHzY9KZ+YsCbzouItc+bZ74pRgvPSq 6HOQ== X-Gm-Message-State: ACrzQf3Xafi4NmIq0lG9AUilGShdVWjW8H7o9UgUtbwM5lMaI9e8rkli WqMY80oyD9uCMQhHv0/QzPvNEOkeIotWge3wI9y9hMoicTQRB1wnQftELjcVs0fWX2C0a/DM5Dz 59zlI+hTgs9M2GYQBVnry3WCHeCzsDUA05ecg7lTA5JI/NC3DWNiyY8H5/Pxzbhw= X-Google-Smtp-Source: AMsMyM6YsTUJZ99lGGv/oSPi8CGqAcEc9iUicsSIzRi7fMiB5YyWyNwXpnMybSLn5r6LKYjgxpidFA== X-Received: by 2002:a17:906:33d8:b0:7ad:a195:ce51 with SMTP id w24-20020a17090633d800b007ada195ce51mr2459388eja.365.1666967723237; Fri, 28 Oct 2022 07:35:23 -0700 (PDT) Received: from smtpclient.apple ([74.122.52.94]) by smtp.gmail.com with ESMTPSA id vs5-20020a170907138500b0078135401b9csm2269025ejb.130.2022.10.28.07.35.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 28 Oct 2022 07:35:22 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-A480D230-F0BD-4AB3-B80F-948339930741 Content-Transfer-Encoding: 7bit From: Paul Wouters Mime-Version: 1.0 (1.0) Date: Fri, 28 Oct 2022 10:35:20 -0400 Message-Id: References: <202210281014303170486@zte.com.cn> Cc: iesg@ietf.org, draft-ietf-ippm-ioam-conf-state@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, marcus.ihlar@ericsson.com In-Reply-To: <202210281014303170486@zte.com.cn> To: xiao.min2@zte.com.cn X-Mailer: iPhone Mail (19G82) Archived-At: Subject: Re: [ippm] Paul Wouters' No Objection on draft-ietf-ippm-ioam-conf-state-07: (with COMMENT) X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2022 14:35:29 -0000 --Apple-Mail-A480D230-F0BD-4AB3-B80F-948339930741 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thank you for the changes ! Paul Sent using a virtual keyboard on a phone > On Oct 27, 2022, at 22:15, xiao.min2@zte.com.cn wrote: >=20 > =EF=BB=BF > Hi Paul, >=20 >=20 >=20 > Following the discussion with John Scudder, I've updated the proposed chan= ges corresponding to your comments. >=20 > Please check inline the new proposed changes. Sorry for the inconvenience.= >=20 >=20 >=20 > Best Regards, >=20 > Xiao Min >=20 > Original > From: =E8=82=96=E6=95=8F10093570 > To: paul.wouters@aiven.io ; > Cc: The IESG ;draft-ietf-ippm-ioam-conf-state@ietf.org ;ippm-chairs@ietf.org ;ippm@ietf.org ;marcus.ihlar@ericsson.com ; > Date: 2022=E5=B9=B410=E6=9C=8826=E6=97=A5 15:27 > Subject: Re: Paul Wouters' No Objection on draft-ietf-ippm-ioam-conf-state= -07: (with COMMENT) > Hi Paul, >=20 >=20 >=20 > Thank you for the review and thoughtful comments. > Please check inline the proposed changes that will be incorporated into th= e next revision. >=20 > Best Regards, > Xiao Min >=20 >=20 >=20 > From: PaulWoutersviaDatatracker > To: The IESG ; > Cc: draft-ietf-ippm-ioam-conf-state@ietf.org ;ippm-chairs@ietf.org ;ippm@ietf.org ;marcus.ihlar@ericsson.com ;marcus.ihl= ar@ericsson.com ; > Date: 2022=E5=B9=B410=E6=9C=8826=E6=97=A5 07:53 > Subject: Paul Wouters' No Objection on draft-ietf-ippm-ioam-conf-state-07:= (with COMMENT) > Paul Wouters has entered the following ballot position for > draft-ietf-ippm-ioam-conf-state-07: No Objection >=20 > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) >=20 >=20 > Please refer to https://www.ietf.org/about/groups/iesg/statements/handling= -ballot-positions/ =20 > for more information about how to handle DISCUSS and COMMENT positions. >=20 >=20 > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-conf-state/ >=20 >=20 >=20 > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- >=20 > Thanks to Chris Lonvick for the SecDir review. He raised a few points that= are > worth addressing: > https://datatracker.ietf.org/doc/review-ietf-ippm-ioam-conf-state-05-secdi= r-lc-lonvick-2022-09-30/ >=20 > Reserved field is reserved for future use and MUST be set to zero. >=20 > Can this be extended to say "and MUST be ignored when non-zero" ? There is= more > than one of these. >=20 > [XM]>>> Yes, I think this can be extended. I propose s/and MUST be ignored= when non-zero/and SHOULD be ignored when non-zero, the reason is that in th= e penultimate paragraph of the security section it indicates that the receiv= er can also report an exception event to the management when non-zero. I'll t= ake care of all the places where the extended text is needed. >=20 > [XM-2]>>> Will use your text "and MUST be ignored when non-zero", and remo= ve "whether all the reserved fields are set to zero" from the penultimate pa= ragraph of the security section. >=20 >=20 > Why is the SoP field specified as two bits from a reserved field, when it o= nly > uses one bit? Why not just take one bit from the reserved field? > [XM]>>> The reason is that in section 4.5.1 of RFC 9197 it says >=20 > Note: Larger or smaller sizes of "PktID" and "Cumulative" data are feasibl= e and could be required for certain deployments, e.g., in case of space cons= traints in the encapsulation protocols used. Future documents could introduc= e different sizes of data for "Proof of Transit". >=20 > Assume the future documents introduce one larger size and one smaller size= , then one bit seems not enough. >=20 >=20 --Apple-Mail-A480D230-F0BD-4AB3-B80F-948339930741 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thank you for the changes !

<= div>Paul

Sent using a virtual keyboard on a phone

On Oct 27, 2022, at 22:15,= xiao.min2@zte.com.cn wrote:

=EF=BB=BF

= Hi Paul,


Following the di= scussion with John Scudder, I'= ve updated the proposed changes corresponding to your comments.

Please check inline= the new proposed changes. Sorry for the inconvenience.


Best Regards,

=

Xiao Min

Original
From: =E8=82=96=E6=95=8F1009357= 0
To: = paul.wouters@aiven.= io <paul.wouters@aiven.io>;
Cc: The IESG <iesg@ietf.org>;draft-ietf-ippm-ioam-conf-state@ietf.org <= ;draft-ietf-ippm-ioam-conf-state@ietf.org>;ippm-chairs@ietf.org <ippm-chairs@ietf.= org>;ippm= @ietf.org <ippm@ietf.org>;marcus.ihlar@ericsson.com <marcus.ihlar@ericsson.com&g= t;;
Date: 2022=E5=B9=B410=E6=9C=8826=E6=97=A5 15:27
Subject: Re: Paul Wouters' No Objection on draft-ietf= -ippm-ioam-conf-state-07: (with COMMENT)

Hi Paul,


= Thank you for the review and thoughtful comments.

Please check inline the proposed changes that will be incorporated= into the next revision.
=


Best Rega= rds,

Xiao Min



From: PaulWoutersviaDatatracker <noreply@ietf.org>
= To: The IESG <iesg@ietf.org>;=
Cc: draft-ietf-ippm-ioam-conf-s= tate@ietf.org <draft-ietf-ippm-ioam-conf-state@ietf.org>;ippm-chairs@ietf.org <i= ppm-chairs@ietf.org>;ippm@ietf.org <ippm@ietf.org>;marcus.ihlar@ericsson.com <marcus.ihl= ar@ericsson.com>;marcus.ihlar@ericsson.com <marcus.ihlar@ericsson.com>;<= /div>
Date: 2022=E5=B9=B410=E6=9C=8826=E6=97=A5 07:53
Subject: Paul Wouters' No Objection on draft-ietf-ippm-ioam-conf= -state-07: (with COMMENT)
Paul Wouters has entered the following=  ballot position for
draft-ietf-ippm-ioam-conf-state-07:&n= bsp;No Objection

When responding, please keep&nb= sp;the subject line intact and reply to a= ll
email addresses included in the To and&n= bsp;CC lines. (Feel free to cut this
introd= uctory paragraph, however.)


Please refer to=  https://www.ietf.org/about/groups/iesg/statements/handling-ballot-posi= tions/ 
for more information about how to&= nbsp;handle DISCUSS and COMMENT positions.


= The document, along with other ballot position= s, can be found here:
https://datatracker.ietf.org/do= c/draft-ietf-ippm-ioam-conf-state/



-----------------------= -----------------------------------------------
COMMENT:
-------------= ---------------------------------------------------------

Thanks&nbs= p;to Chris Lonvick for the SecDir review. = ;He raised a few points that are
worth = ;addressing:
https://datatracker.ietf.org/doc/review-ietf-ippm-ioam-conf-= state-05-secdir-lc-lonvick-2022-09-30/

   Reserved&nb= sp;field is reserved for future use and M= UST be set to zero.

Can this be e= xtended to say "and MUST be ignored when&= nbsp;non-zero" ? There is more

than one = of these.

[XM]>>> Yes, I think this can be extended. I p= ropose s/and MUST be ignored when non-zero/and SHOULD be ignored when non-ze= ro, the reason is that in the penultimate paragraph of the security section i= t indicates that the receiver can also report an exception event to the mana= gement when non-zero. I'll take care of all the places where the extended te= xt is needed.

[XM-2]>>> Will use your text "and MUST&nbs= p;be ignored when non-zero", and remove "whether all the rese= rved fields are set to zero" from the penultimate paragraph of the secu= rity section.


Why is the SoP field specified=  as two bits from a reserved field, = when it only
uses one bit? Why not jus= t take one bit from the reserved field?

[XM]>>> The reason is that in section 4.5.1 of RFC 9197 it sa= ys

Note: Larger or smaller sizes of "PktID" and "Cumulative" data are feasible= and could be required for certain deployments, e.g., in case of space const= raints in the encapsulation protocols used. Future documents could introduce= different sizes of data for "Proof of Transit".

Assume the future docum= ents introduce one larger size and one smaller size, then one bit seems not e= nough.


=
= --Apple-Mail-A480D230-F0BD-4AB3-B80F-948339930741--