Re: [OPSEC] Secdir last call review of draft-ietf-opsec-probe-attribution
tirumal reddy <kondtir@gmail.com> Tue, 04 July 2023 04:57 UTC
Return-Path: <kondtir@gmail.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E618C15155F; Mon, 3 Jul 2023 21:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.085
X-Spam-Level:
X-Spam-Status: No, score=-7.085 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, 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 gR0mCMYt3OA0; Mon, 3 Jul 2023 21:57:25 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 AAF97C15155C; Mon, 3 Jul 2023 21:57:25 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-4fb87828386so1626664e87.1; Mon, 03 Jul 2023 21:57:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688446643; x=1691038643; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wspHcFcjK65iG9ike6Se1taEOfpW9pgGxoSyLYd+LVg=; b=V85o4ZgL7e1rWz6r4in4gefln+Uu4pQ0kVHBA02bSZgbOi7WQus/MN0U9BXPlWhIx/ AfJ0F4gPWg8nVRnBx6FL8Mdgn2hOuL4oTEtLMRX+nk2S56D8gBjFKvIhUFCMwIfJG0/l Hb0cjIM6jsl53U26U+Vv8Rnj8a/XqxiK2pMPSUc0rT9KeZEdGJe6/7BkV9X09StPlDHk cX4NNHqKhTWJc/meRrVErfvp9kZEwP2RJR97Yl0O7MX0nJ4+XR35edYujnjojWeDHBLx hjqKacNlCQL7c3XufmPjaklY4wIHnvAqIjeyjNEAgXrRzWQTxrC21pfnDiWbED9OX1bA FgmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688446643; x=1691038643; 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=wspHcFcjK65iG9ike6Se1taEOfpW9pgGxoSyLYd+LVg=; b=aLVup7p9PdJeZmIajppmNYMuoUhCMgFml1UUNkaH3KiK3KkIoeAn/KtATJlAf7MiLs ftM5r1tiC9rkjHIIpxNtwJLGJCwrl8qtrSlpFQ7fz8+GjvTrSUZ9VCyG4GKGaND5pcmg XntdXzGHU2PGdOxwoRMWAMlsh4FQzWpLHxG3igw6qrQUy9bmIxbxuZAyn7FrvIMSWSke 2vMGqQwv6Uu9vRN0zmhuOwKhXkP5nT3JTTpu1W+lz/zMkV5UWOolrGhIF7FzIT5gqxkI s6r8Gw9vJcaus1kmt0Y0PDMoxi9RneDqtTEeIjO6ijQkVzMtHirfA27rRVZyHLdVsFgD b75w==
X-Gm-Message-State: ABy/qLZV8Ocs2jfIjIn2Y489Lik0UGZwIhMKs966JWlaEEgT1DtvTqPr zcYNnDrxU2DC2huJr63QerMwm9s/amBeP3Z+RZk=
X-Google-Smtp-Source: APBJJlEhgZx/2ajxuCh/NAGEGcofNTPokkoQoWqvQ63/sl3FvXSsjsR+gg9Bii+fx+tRB8uvF7r9C0SGO0Ob3gkTlOo=
X-Received: by 2002:a2e:a41a:0:b0:2b6:9ebc:d8c4 with SMTP id p26-20020a2ea41a000000b002b69ebcd8c4mr7498342ljn.0.1688446642808; Mon, 03 Jul 2023 21:57:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAFpG3gf4yORu3ZBWq1NpQgOUWszDsBGSGcZzPJH9cWd0JLHW-g@mail.gmail.com> <A644D21F-3D9D-4718-84F4-675498491D41@cisco.com>
In-Reply-To: <A644D21F-3D9D-4718-84F4-675498491D41@cisco.com>
From: tirumal reddy <kondtir@gmail.com>
Date: Tue, 04 Jul 2023 10:27:11 +0530
Message-ID: <CAFpG3geu8B_CrRL9Qsc1C-yX490TrzPMZ2_+N0bf+Wk5a77iHQ@mail.gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-opsec-probe-attribution.all@ietf.org" <draft-ietf-opsec-probe-attribution.all@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005de94a05ffa21e8e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/NBMtnYQyDmt4zyFykxcwNzDSwm4>
Subject: Re: [OPSEC] Secdir last call review of draft-ietf-opsec-probe-attribution
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsec/>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2023 04:57:30 -0000
On Fri, 23 Jun 2023 at 12:55, Eric Vyncke (evyncke) <evyncke@cisco.com> wrote: > Hello Tiru, > > > > Thank you for your detailed review. I have submitted a revised I-D > incorporating your suggestions. > > > > Look below for EV> for further comments. > > > > Best regards > > > > -éric > > > > *From: *OPSEC <opsec-bounces@ietf.org> on behalf of tirumal reddy < > kondtir@gmail.com> > *Date: *Tuesday, 20 June 2023 at 08:08 > *To: *"secdir@ietf.org" <secdir@ietf.org>, "last-call@ietf.org" < > last-call@ietf.org>, "draft-ietf-opsec-probe-attribution.all@ietf.org" < > draft-ietf-opsec-probe-attribution.all@ietf.org>, "opsec@ietf.org" < > opsec@ietf.org> > *Subject: *[OPSEC] Secdir last call review of > draft-ietf-opsec-probe-attribution > > > > Reviewer: Tirumaleswar Reddy > Review result: Ready with issues > > I have reviewed this document as part of the security directorate's > ongoing effort to review all IETF documents being processed by the > IESG. These comments were written primarily for the benefit of the > security area directors. Document editors and WG chairs should treat > these comments just like any other last call comments. > > The summary of the review is Ready with issues. > > [1] > else (or in addition), the Probe Description URI is > "https://[2001:db8::dead]/.well-known/probing.txt". In this case, > there might be a certificate verification issue. > > Comment> It is possible to get a certificate with IP address from a public > CA > (see https://datatracker.ietf.org/doc/html/rfc8738). > > EV> good catch, text amended > > > [2] > > You may want to consider referring to > https://datatracker.ietf.org/doc/draft-ietf-6man-hbh-processing/, > It discusses HBH option processing by intermediate nodes and > recommendations to process new HBH options. > > > > EV> I would prefer not to refer to a draft (and I fear that the 6MAN HbH > is far from being published). > Sure but I suggest to high-light the issues with HBH options like the ones discussed in Section 4 of draft-ietf-6man-hbh-processing that at the time of writing this specification routers are typically configured to drop HBH options. > > [3] > I suggest discussing the privacy implications that an eavesdropper will be > able to view the PII data in the Probe. > > EV> Added some note in the security section that no PII should be in the > Probe Description (notably no personal address/email/phone). Good catch. > > > [4] > As a consequence, the recipient of this information cannot trust it > without confirmation. If a recipient cannot confirm the information > or does not wish to do so, it should treat the flows as if there were > no probe attribution. > > Comment> How can the recipient of the probe information validate it is > authentic for confirmation ? > > > > EV> applying common sense and doing some basic verification (e.g., is the > email address valid ?). This is all about good faith. > Okay but you should suggest all possible checks like the scheme for the probe URI must be "https", email address is valid etc. -Tiru > > > Cheers, > > -Tiru >
- [OPSEC] Secdir last call review of draft-ietf-ops… tirumal reddy
- Re: [OPSEC] Secdir last call review of draft-ietf… Eric Vyncke (evyncke)
- Re: [OPSEC] Secdir last call review of draft-ietf… tirumal reddy