[ippm] DEX Draft Updated

Tal Mizrahi <tal.mizrahi.phd@gmail.com> Thu, 01 July 2021 12:54 UTC

MIME-Version: 1.0
References: <162514156275.10687.5210311195217579136@ietfa.amsl.com>
In-Reply-To: <162514156275.10687.5210311195217579136@ietfa.amsl.com>
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Thu, 01 Jul 2021 15:54:30 +0300
Message-ID: <CABUE3Xki7N77Z1cKUtg6Y_VcGnH4nZ_b7ae6LcTxLUiac==Dvg@mail.gmail.com>
To: IETF IPPM WG <ippm@ietf.org>, IPPM Chairs <ippm-chairs@ietf.org>, Martin Duke <martin.h.duke@gmail.com>, Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: Barak Gafni <gbarak@nvidia.com>, Frank Brockners <fbrockne@cisco.com>, Haoyu Song <haoyu.song@huawei.com>, Ramesh Sivakolundu <sramesh@cisco.com>, Shwetha Bhandari <shwetha.bhandari@thoughtspot.com>, Tianran Zhou <zhoutianran@huawei.com>, Zhenbin Li <lizhenbin@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/JNiX94A7fN6tUPsA-VQizQEBWms>
Subject: [ippm] DEX Draft Updated
Precedence: list

Hi,

The draft was significantly revised (see links below) following the
security-related feedback from the last IETF meeting, and based on
further discussion that were held at the IOAM design team meetings.

Thanks again, Martin and Mirja, for your feedback.

The main changes compared to the previous version:
- Two sections were added, "DEX Packet Selection", and "Responding to
the DEX Trigger". These two sections are specifically intended to
address Martin's feedback regarding amplification attacks.
- New requirements were added to the security consideration section in
response to the comments in the last IETF meeting:
  - Selective DEX at IOAM encapsulating nodes - in response to
Martin's comments.
    and
  - Rate limiting at IOAM transit nodes - in response to Martin's comments.

  - Avoid pushing the DEX option onto exported packets - in response
to Martin's comments.

  - Only export to trusted nodes - in response to Mirja's comments.

Please let us know if there are further comments, and specifically
regarding the security aspects of the draft.

Cheers,
Tal.



On Thu, Jul 1, 2021 at 3:12 PM <internet-drafts@ietf.org> wrote:
>
>
> A new version of I-D, draft-ietf-ippm-ioam-direct-export-04.txt
> has been successfully submitted by Tal Mizrahi and posted to the
> IETF repository.
>
> Name:           draft-ietf-ippm-ioam-direct-export
> Revision:       04
> Title:          In-situ OAM Direct Exporting
> Document date:  2021-07-01
> Group:          ippm
> Pages:          12
> URL:            https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-direct-export-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-direct-export/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-ippm-ioam-direct-export
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-ippm-ioam-direct-export-04
>
> Abstract:
>    In-situ Operations, Administration, and Maintenance (IOAM) is used
>    for recording and collecting operational and telemetry information.
>    Specifically, IOAM allows telemetry data to be pushed into data
>    packets while they traverse the network.  This document introduces a
>    new IOAM option type called the Direct Export (DEX) option, which is
>    used as a trigger for IOAM data to be directly exported or locally
>    aggregated without being pushed into in-flight data packets.  The
>    exporting method and format are outside the scope of this document.
>
>
>
>
> The IETF Secretariat
>
>

[ippm] DEX Draft Updated Tal Mizrahi
Re: [ippm] DEX Draft Updated Martin Duke
Re: [ippm] DEX Draft Updated Tal Mizrahi
Re: [ippm] DEX Draft Updated Martin Duke