IETF Logo Mail Archive

Re: [Idr] 2nd WG LC for CT drafts - which includes draft-ietf-idr-bgp-ct, draft-ietf-idr-bgp-ct-srv6, and draft-ietf-idr-bgp-fwd-rr-01 (2/16/2024 to 3/1/2024).

Robert Raszuk <robert@raszuk.net> Fri, 01 March 2024 19:56 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE33BC1516F3 for <idr@ietfa.amsl.com>; Fri, 1 Mar 2024 11:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (2048-bit key) header.d=raszuk.net
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 vpgVDeMWk-J3 for <idr@ietfa.amsl.com>; Fri, 1 Mar 2024 11:56:27 -0800 (PST)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 E77B8C151093 for <idr@ietf.org>; Fri, 1 Mar 2024 11:56:27 -0800 (PST)
Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-565ef8af2f5so3687872a12.3 for <idr@ietf.org>; Fri, 01 Mar 2024 11:56:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1709322986; x=1709927786; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZiFdaQSoTR/q0zFjsrpx+VH/CwXVEexTMQHrJfT96GI=; b=CiMsAr/I2D+OjlNe18fwSQzI/2gJUXnmACebrBMGxmSg1ympdYbtNO7LMsU6Q0f8Li CsUXiaz+071czCSOr0+f+Q2CB/32lYZ6EONGUsOVyQlhcoBd3J49xnqDim7EO26COBfr 6W4zyAOX7+OurMAqlebbLKvIi0oQ5nlRT+bS+r70yyj4wzD6a0Vw6zLLpaXdAYWJ+dnl 8vBUeR7a/SNsbR89FP3Za18HIFVHTVDAhIZQK0NhWS95fFEiR8me3vF4Oycuo6NpIVJe kw+JoGPS5N/1TYPqLe/tFOSYvuZZ6q+UuaJ9ViZfamUoHxpbq0Rrntrfx9lhkPxGlDrg fYiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709322986; x=1709927786; 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=ZiFdaQSoTR/q0zFjsrpx+VH/CwXVEexTMQHrJfT96GI=; b=sTvLtp4bh/Llt42pnoVEnfHzuv2gVW8OoK2lQbm+TxZILEZqU7EnYaPVoaai79apVA geeiyDzpdTbHLgbzFt4XKTJRqJP4A9niIOxAb2em+rUqRWE5GX/JVzA6ZV3FS3LoMEbA csWbZP1li+VSS0JAh6YoVjZjx65jslSZ90NUfBTZ9yQvoXLitQXq5II0Mfc0m4MqczQC JKrLOi63uY8BraXhyBkylIKtD2OO/aps8sK4NYbXqg01MUPqQa0Jqi8xRDzhwJap5GK5 Fz7KnL9+0NW8DPKRa3pK8E+BsCJlMVUwaYfYfFtV+20L+Mbb49YV8z+I1Q1OsHRsKnV0 ylxA==
X-Forwarded-Encrypted: i=1; AJvYcCUIXArPeZibuzKN0+GuhnGBwcaxUvBI3yE4L9xoQ9vurizB3l7Vcgn+K9oLeh2b/+agCu1FG/dJ5TzGSlc=
X-Gm-Message-State: AOJu0YyQ1gLvtuVqOs23DTylTB4pfPH634V7rkkcFhdiRK3rZ9qXYYI8 kqTZPJQkZJfOIXaOy1m491X7kXfL+zXSUYNxifXBGWehSnmNK46PM7BQqwXGkIgrnsM1ZzGXp7H sJ6ksK6oDsZCbRrhFCW5JAM1rBfBQCC+33AlsgQ==
X-Google-Smtp-Source: AGHT+IHZYDgFUZfITQdiNJjnICbRR21I31wS5a2uh1Ce2SOLFW8e2QjS37BxJEPa7A0boirVcCuzHUK7GowZy7X/IrA=
X-Received: by 2002:a05:6402:1848:b0:566:a7c0:c8e8 with SMTP id v8-20020a056402184800b00566a7c0c8e8mr2275390edy.12.1709322986008; Fri, 01 Mar 2024 11:56:26 -0800 (PST)
MIME-Version: 1.0
References: <CO6PR05MB7796D42F85108E8EA4A3B445AC592@CO6PR05MB7796.namprd05.prod.outlook.com> <CO6PR05MB7796219AF6A418AAA3C5D456AC5E2@CO6PR05MB7796.namprd05.prod.outlook.com> <CAOj+MMGisd=NyDAJRxqeU6tEX3JATh4_tH5jMLbedOpOGCajNQ@mail.gmail.com> <CO6PR05MB7796176A0E6CDDB3CAA15B72AC5E2@CO6PR05MB7796.namprd05.prod.outlook.com> <CAOj+MMHsF=9NeRHR=bsJswy=3dRjxiTgQdGR96TkQ4QezQYykg@mail.gmail.com> <CA+wi2hNqVTj24Xu0cY2-bXC_DypaziFMurjJy92FXW5PoMW-mw@mail.gmail.com>
In-Reply-To: <CA+wi2hNqVTj24Xu0cY2-bXC_DypaziFMurjJy92FXW5PoMW-mw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 01 Mar 2024 20:56:14 +0100
Message-ID: <CAOj+MMEz+aiXM1c-DbGJgFOrqBe-d6zr+LU0N31+8_t=YGevsA@mail.gmail.com>
To: Tony Przygienda <tonysietf@gmail.com>
Cc: Antoni Przygienda <prz@juniper.net>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000063454506129ec596"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ANxIqbON1zSYjcpFugwHWQzqgfw>
Subject: Re: [Idr] 2nd WG LC for CT drafts - which includes draft-ietf-idr-bgp-ct, draft-ietf-idr-bgp-ct-srv6, and draft-ietf-idr-bgp-fwd-rr-01 (2/16/2024 to 3/1/2024).
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2024 19:56:31 -0000

Tony,

Please kindly do not turn the cat around now.

It was Yourself who started to give such recommendations to IDR WG not me.
So that required follow-up.

Quote:

*From: Antoni Przygienda <prz@juniper.net <prz@juniper.net>>*

*Date: Tuesday, 27 February 2024 at 20:22*


*... it’s premature to advance anything relying on SRv6 to anything close
to a standards document until the security model/concerns/architecture are
clarified.*


Best,
R.

On Fri, Mar 1, 2024 at 6:43 PM Tony Przygienda <tonysietf@gmail.com> wrote:

> Is Webster unclear in its definition of "abstain", Robert?
>
> And if you have objections to the SRv6 security work, please follow the
> according groups and comment there. This is not the place ...
>
> -- tony
>
>
>
> On Fri, Mar 1, 2024 at 6:20 PM Robert Raszuk <robert@raszuk.net> wrote:
>
>>
>> Oh you want to freeze some work in IDR with the broken concept of
>> "trusted domain" :)  Note in IDR we call it One Administrative Domain.
>>
>> But please do not ...
>>
>> IDR is not about that - quite contrary it is about Inter-Domain Routing
>> and last time I checked SRv6 is using packets with IPv6 headers which
>> as such *are* globally routable by the notion of longest locator match.
>>
>> Cheers,
>> Robert
>>
>> On Fri, Mar 1, 2024 at 6:13 PM Antoni Przygienda <prz@juniper.net> wrote:
>>
>>> please follow the int-area and discussion around pending drafts, amongst
>>> them trusted domain discussions …
>>>
>>>
>>>
>>> thanks
>>>
>>>
>>>
>>>    - tony
>>>
>>>
>>>
>>>
>>> Juniper Business Use Only
>>> From: Robert Raszuk <robert@raszuk.net>
>>> *Date: *Friday, 1 March 2024 at 18:06
>>> *To: *Antoni Przygienda <prz@juniper.net>
>>> *Cc: *Susan Hares <shares@ndzh.com>, idr@ietf.org <idr@ietf.org>
>>> *Subject: *Re: [Idr] 2nd WG LC for CT drafts - which includes
>>> draft-ietf-idr-bgp-ct, draft-ietf-idr-bgp-ct-srv6, and
>>> draft-ietf-idr-bgp-fwd-rr-01 (2/16/2024 to 3/1/2024).
>>>
>>> *[External Email. Be cautious of content]*
>>>
>>>
>>>
>>> Hi Antoni,
>>>
>>>
>>>
>>> on it since I think that given the current SRv6 security discussion and
>>> situation it’s premature to advance anything relying on SRv6 to anything
>>> close to a standards document until the security
>>> model/concerns/architecture are clarified.
>>>
>>>
>>>
>>> For those who do not track all IETF WGs actively could you please
>>> provide a link to this discussion and explain/summarize the "situation" ?
>>>
>>>
>>>
>>> Thank you,
>>>
>>> Robert
>>>
>>>
>>>
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>
>

v2.23.0 | Report a Bug | By Email