Re: [ippm] Roman Danyliw's Discuss on draft-ietf-ippm-ioam-conf-state-07: (with DISCUSS and COMMENT)

Hi Roman,

The I-D submission tool reopens and I've posted -08 revision. Link as below.

https://datatracker.ietf.org/doc/html/draft-ietf-ippm-ioam-conf-state-08

Much appreciated if you would check it over to see whether your DISCUSS point has been addressed.

Best Regards,

Xiao Min

Original

From: 肖敏10093570
To: rdd@cert.org <rdd@cert.org>;
Cc: ippm-chairs@ietf.org <ippm-chairs@ietf.org>;iesg@ietf.org <iesg@ietf.org>;ippm@ietf.org <ippm@ietf.org>;draft-ietf-ippm-ioam-conf-state@ietf.org <draft-ietf-ippm-ioam-conf-state@ietf.org>;
Date: 2022年10月28日 11:45
Subject: Re: [ippm] Roman Danyliw's Discuss on draft-ietf-ippm-ioam-conf-state-07: (with DISCUSS and COMMENT)

_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm

Hi Roman,

Thank you for the reply. I got it.

Best Regards,

Xiao Min

From: RomanDanyliw <rdd@cert.org>
To: 肖敏10093570;
Cc: iesg@ietf.org <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>;
Date: 2022年10月27日 22:21
Subject: RE: Roman Danyliw's Discuss on draft-ietf-ippm-ioam-conf-state-07: (with DISCUSS and COMMENT)

Hi Xiao!

Thanks for the quick response.  The refined text described below addresses my concerns.

Roman

From: iesg <iesg-bounces@ietf.org> On Behalf Of xiao.min2@zte.com.cn
 Sent: Wednesday, October 26, 2022 3:36 AM
 To: Roman Danyliw <rdd@cert.org>
 Cc: iesg@ietf.org; draft-ietf-ippm-ioam-conf-state@ietf.org; ippm-chairs@ietf.org; ippm@ietf.org; marcus.ihlar@ericsson.com
 Subject: Re: Roman Danyliw's Discuss on draft-ietf-ippm-ioam-conf-state-07: (with DISCUSS and COMMENT)

Hi Roman

Thank you for the review and thoughtful comments.

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

Best Regards,

Xiao Min

Original

From: RomanDanyliwviaDatatracker <noreply@ietf.org>

To: The IESG <iesg@ietf.org>;

Cc: 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>;marcus.ihlar@ericsson.com <marcus.ihlar@ericsson.com>;

Date: 2022年10月26日 10:21

Subject: Roman Danyliw's Discuss on draft-ietf-ippm-ioam-conf-state-07: (with DISCUSS and COMMENT)

Roman Danyliw has entered the following ballot position for
 draft-ietf-ippm-ioam-conf-state-07: Discuss

 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.)

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

 The document, along with other ballot positions, can be found here:
 https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-conf-state/

 ----------------------------------------------------------------------
 DISCUSS:
 ----------------------------------------------------------------------

 Section 6.

    A deployment can increase security by using border filtering of
    incoming and outgoing echo requests/replies.

 Thanks for calling out the security impact of echo request/replies.  Since the
 cited RFC9197 reminds the reader that a “network operator is expected to
 enforce policies that prevent IOAM traffic from leaking outside of the
 IOAM-Domain”, why is this guidance not mandatory?

 Would the following text be more appropriate?

 NEW
 A deployment MUST ensure that border filtering drops inbound echo requests with
 a IOAM Capabilities Container Header from outside of the domain, and drops
 outbound echo request/replies with IOAM Capabilities Headers leaving the domain.
 [XM]>>> Yes, I think the text proposed by you is more appropriate. Typo s/a IOAM Capabilities/an IOAM Capabilities.

 ----------------------------------------------------------------------
 COMMENT:
 ----------------------------------------------------------------------

 Thank you to Chris Lonvick for the SECDIR review.

 Section 3.1.  Typo. s/begining/beginning/

 Section 6.  Typo. s/securiy/security/
 [XM]>>> OK, will fix. Thank you for catching them.