IETF Logo Mail Archive

Re: [tsvwg] Fwd: New Version Notification for draft-reddy-tsvwg-explcit-signal-00.txt

"C. M. Heard" <heard@pobox.com> Mon, 20 February 2023 23:26 UTC

Return-Path: <heard@pobox.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3E2DC14CF0C for <tsvwg@ietfa.amsl.com>; Mon, 20 Feb 2023 15:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 (1024-bit key) header.d=pobox.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 OoZsBNFheyTP for <tsvwg@ietfa.amsl.com>; Mon, 20 Feb 2023 15:26:49 -0800 (PST)
Received: from pb-smtp21.pobox.com (pb-smtp21.pobox.com [173.228.157.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49C12C14F74E for <tsvwg@ietf.org>; Mon, 20 Feb 2023 15:26:48 -0800 (PST)
Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 7AA671E8F1D for <tsvwg@ietf.org>; Mon, 20 Feb 2023 18:26:46 -0500 (EST) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:cc:content-type; s=sasl; bh=kln7x3NohdvBUmQNs7xdh36S1s8ANX/Z Lz2vKydp/Pg=; b=ZL+PE/3FNkdorzskefVCaZuIs2DB8V7BxDFWK2AurNZhcrHw CiH9I1Xqu7hAUoRvIZhUux/3ApGJrxJPt0xfQDuymQVmCUiWL6cMtFpIOup/RkES cpZ08Fm/x3D1bIQhI8J1Gsvz3faSS/7Wd84nnyCUfCM7t6ONiO7Cg/IHRuI=
Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 736C31E8F1C for <tsvwg@ietf.org>; Mon, 20 Feb 2023 18:26:46 -0500 (EST) (envelope-from heard@pobox.com)
Received: from mail-ed1-f54.google.com (unknown [209.85.208.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id C6F141E8F1B for <tsvwg@ietf.org>; Mon, 20 Feb 2023 18:26:43 -0500 (EST) (envelope-from heard@pobox.com)
Received: by mail-ed1-f54.google.com with SMTP id s26so10330918edw.11 for <tsvwg@ietf.org>; Mon, 20 Feb 2023 15:26:43 -0800 (PST)
X-Gm-Message-State: AO0yUKWNDzpz5wfzSDOMjHq/i9ztFQjafAnUnVWfmJnYQ7SkeofEjVCk W9pghItaeEi1fo15wcUYYGzVLyMnFn2mMJSVOfQ=
X-Google-Smtp-Source: AK7set+aQcb4c76OwjMD6ejkyO+AnWhCofiDz8ZhAkh1b4le63mCGuIsTHJRXTWAJpcTQJnTu4u+ktGr0exwAJTtndk=
X-Received: by 2002:a17:906:4f0a:b0:8b1:30eb:9dba with SMTP id t10-20020a1709064f0a00b008b130eb9dbamr4799452eju.6.1676935601908; Mon, 20 Feb 2023 15:26:41 -0800 (PST)
MIME-Version: 1.0
References: <167592939329.52949.17763475463632062767@ietfa.amsl.com> <CAFpG3gdFojRowTpo-DBDh2czC9d-KemSetmeaOC3VZ=COqvOgg@mail.gmail.com>
In-Reply-To: <CAFpG3gdFojRowTpo-DBDh2czC9d-KemSetmeaOC3VZ=COqvOgg@mail.gmail.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Mon, 20 Feb 2023 15:26:30 -0800
X-Gmail-Original-Message-ID: <CACL_3VE5KectHscwWLy3QfuqT_N1g8d=jFuL_Ar0zV=kdniG6w@mail.gmail.com>
Message-ID: <CACL_3VE5KectHscwWLy3QfuqT_N1g8d=jFuL_Ar0zV=kdniG6w@mail.gmail.com>
To: tirumal reddy <kondtir@gmail.com>
Cc: tsvwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dcf2d605f529fe22"
X-Pobox-Relay-ID: 09478AE0-B176-11ED-B137-B31D44D1D7AA-06080547!pb-smtp21.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/EYQ_iT8-7rp5bIqFCcsvpSG0Fyk>
Subject: Re: [tsvwg] Fwd: New Version Notification for draft-reddy-tsvwg-explcit-signal-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2023 23:26:53 -0000

One overall question: per
https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options#section-14
,

   UDP options are transport options. Generally, transport headers,
   options, and data are not intended to be modified in-transit. UDP
   options are no exception and here are specified as "MUST NOT" be
   altered in transit. However, the UDP option mechanism provides no
   specific protection against in-transit modification of the UDP
   header, UDP payload, or surplus area, except as provided by the OCS
   or the options selected (e.g., AUTH, or UENC).


Does this draft comply with this requirement?

Mike Heard

On Thu, Feb 9, 2023 at 9:31 PM tirumal reddy <kondtir@gmail.com> wrote:

> Hi all,
>
> The new draft
> https://datatracker.ietf.org/doc/html/draft-reddy-tsvwg-explcit-signal
> defines a mechanism for an endpoint to explicitly signal encrypted metadata
> to the network, and the network to signal its ability to accommodate that
> metadata back to the endpoint. This mechanism can be used where the
> endpoints desire that network elements along the path receive these
> explicit signals. It proposes three mechanisms to encrypt or obfuscate the
> metadata in the explicit signal.
>
> Comments and suggestions are welcome.
>
> Cheers,
> -Tiru
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Thu, 9 Feb 2023 at 13:26
> Subject: New Version Notification for
> draft-reddy-tsvwg-explcit-signal-00.txt
> To: Tirumaleswar Reddy.K <kondtir@gmail.com>, Dan Wing <danwing@gmail.com>,
> Mohamed Boucadair <mohamed.boucadair@orange.com>
>
>
>
> A new version of I-D, draft-reddy-tsvwg-explcit-signal-00.txt
> has been successfully submitted by Tirumaleswar Reddy and posted to the
> IETF repository.
>
> Name:           draft-reddy-tsvwg-explcit-signal
> Revision:       00
> Title:          Encrypted Transport Protocol Path Explicit Signals
> Document date:  2023-02-08
> Group:          Individual Submission
> Pages:          18
> URL:
> https://www.ietf.org/archive/id/draft-reddy-tsvwg-explcit-signal-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-reddy-tsvwg-explcit-signal/
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-reddy-tsvwg-explcit-signal
>
>
> Abstract:
>    This document defines a mechanism for an endpoint to explicitly
>    signal encrypted metadata to the network, and the network to signal
>    its ability to accommodate that metadata back to the endpoint.  This
>    mechanism can be used where the endpoints desire that network
>    elements along the path receive these explicit signals.
>
>
>
>
> The IETF Secretariat
>
>
>

v2.23.0 | Report a Bug | By Email