IETF Logo Mail Archive

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

tirumal reddy <kondtir@gmail.com> Tue, 21 February 2023 12:17 UTC

Return-Path: <kondtir@gmail.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 2AB53C14F740 for <tsvwg@ietfa.amsl.com>; Tue, 21 Feb 2023 04:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 (2048-bit key) header.d=gmail.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 3KPT0m1fi1ze for <tsvwg@ietfa.amsl.com>; Tue, 21 Feb 2023 04:17:44 -0800 (PST)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 7E689C14EB18 for <tsvwg@ietf.org>; Tue, 21 Feb 2023 04:17:44 -0800 (PST)
Received: by mail-lf1-x131.google.com with SMTP id g8so1736448lfj.2 for <tsvwg@ietf.org>; Tue, 21 Feb 2023 04:17:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=grsT3/CJSDz6tAO3nUc874IM4H07VfOAlsWAI/cBMbU=; b=SBX8y8cPggBptTeE7SbMGhrFPa0AVmEn5tXvRDufVYKWbAtyAXWtEFx+fyPYfAqxJy 0OnmwoniZkGXHMgss8R7tjyo3Md3yDxlnEekUDQhqT/kAPWI8VCNJL1LFApVhE/fxW83 oSKvKUuTnjrUAaMA8Z6YPQn+9/GvivBei5HK36sqoEdt22SXviOWUgmnSuW+qD7LHdMW epA68hokg22UN+heRtLDzIhBK1UwuCerYp+pVz9iJzcebC7DTWT3RX8OmaNVsRb1zEp6 mPRzqxJryg0Lm5YM+3JLvDQIIQfs7vN969Ojmc8+3ldSuBKrSQQfRvAGQJRYyotmKYR9 tLvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=grsT3/CJSDz6tAO3nUc874IM4H07VfOAlsWAI/cBMbU=; b=2mk06oIuKtLNgAAtMutTMJ2MBDYvxrmB3PPSak5nxXozf/lRXDOp9UssJLtKk0jpsy cJhVIN7m1iO/NqHzTG4rAXeE8b3v3gRiUBvxZNhx6KwGr6/RSyCou0pzAFfiaTzbbIaw ZG8O0SGTXy1aV77zrm1syGvpmukuaZ7V3WH2dpiVgWKw6OqipZyimHqOoI4xHYFGhlrv KEgJ58cyiWFdQEpE8U7CW+R9/e+9Aa/6Y4VL/c4rDTHKPXptC63KCPjwKdA01kQ8hShe qgSFTLhN93pFvMoF+o8WcpSiZisRB2mg8+XWqo3BiVAoMqB4+G6sMbm4SR+e4rlJGooY gCzg==
X-Gm-Message-State: AO0yUKWauB2y5MRJFTmdCutcgJhITmnqLNVyDvMOuZVhoQ0Isp4JE43J 2TGQI5ktGPVdguSJKheTN/tK3yB03EY9tcMVxq0=
X-Google-Smtp-Source: AK7set+6DBVm5IIaOwer5m+qIkaAsSEeVM+d/GKn0OqPH7xYj2Ab6yoSWuVa3A2DZ5gCp9j04ClblcxJAzHXEdPEGEc=
X-Received: by 2002:ac2:5926:0:b0:4d5:ca32:7bc5 with SMTP id v6-20020ac25926000000b004d5ca327bc5mr1705544lfi.12.1676981861840; Tue, 21 Feb 2023 04:17:41 -0800 (PST)
MIME-Version: 1.0
References: <167592939329.52949.17763475463632062767@ietfa.amsl.com> <CAFpG3gdFojRowTpo-DBDh2czC9d-KemSetmeaOC3VZ=COqvOgg@mail.gmail.com> <CACL_3VE5KectHscwWLy3QfuqT_N1g8d=jFuL_Ar0zV=kdniG6w@mail.gmail.com>
In-Reply-To: <CACL_3VE5KectHscwWLy3QfuqT_N1g8d=jFuL_Ar0zV=kdniG6w@mail.gmail.com>
From: tirumal reddy <kondtir@gmail.com>
Date: Tue, 21 Feb 2023 17:47:30 +0530
Message-ID: <CAFpG3gfYKdRQOsJ-NqAT64dRYJ3BX2yVcb4V=aw+TmPvJN-wOQ@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
Cc: tsvwg@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002b7a1e05f534c473"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/2chIxDsyIeiYEbFdzWAj0rfJ0BY>
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: Tue, 21 Feb 2023 12:17:45 -0000

On Tue, 21 Feb 2023 at 04:56, C. M. Heard <heard@pobox.com> wrote:

> 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?
>

Yes, the draft does not suggest any in-transit modification of the UDP
option.

-Tiru


> 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