Return-Path: <zahed.sarker.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id B7484C14CE36;
	Thu, 30 May 2024 12:23:29 -0700 (PDT)
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 rz4zoiwFHfWe; Thu, 30 May 2024 12:23:28 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com
 [IPv6:2607:f8b0:4864:20::530])
	(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 B6A52C14F689;
	Thu, 30 May 2024 12:23:28 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id
 41be03b00d2f7-681bee6bb13so993096a12.1;
        Thu, 30 May 2024 12:23:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1717097008; x=1717701808; 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=/rbwpK/vinpiPBmb0uw5XV1lgCynYaYQK+OgkOFo3Mk=;
        b=SRJ6gRJREsSKgX+HhbcQ+faUlcXk8LhTh11FAMksET81LxKR5ZiN9W7xyVyE/lu6/5
         +SrGHWTARSAho0Z4mT+n+i9KAvUdnFeAlU/OlRw+2pLiIpS5OhthyEYFgvxfHCri9GQ1
         8FiJ2N9PWFq/ybQtP3SEGn6TqaQDXbQr/jriDhh/dqoJDxhQeCdxsOXEpM00QLIeT53K
         ErIR0KmrWNo3wHDCqersdWvLtTSUpw4WyHe1EhZusBZ0TndP5s+Lbm+VumOpvNSdRXfk
         HFxrvQp0rcLejQa6pi5J13osjpVD9py4y5Njubzpy/q08iznrSJBRAyRrIkKSV3olOiX
         HmhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1717097008; x=1717701808;
        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=/rbwpK/vinpiPBmb0uw5XV1lgCynYaYQK+OgkOFo3Mk=;
        b=X8rYtoKBgb8CjHMnoU9GXCVOUS+1IBsG4bCxukauMQsB2ki4v5Y2Er6gXnz5r0n/Er
         nzk6Mu6U+elD5HbXtLBAzIYEatSGOpvnVxL53riBpItlF4Hl7bErhI0Y7K5I6qVkjaJK
         nL1FhKqZ6zRH2/wkXputAu/QMBM0zKoGsKsPhD/pcoeAylPLm7zpxWdT6fEHIhfm06tA
         5d5Hybd2rKa1ubIYBg2smWyfx0Wq4RuhFD2LiNF04EIT5hpJkhEumwk095jYK6P1LJmF
         pH7vMSogTbNu1di7u+qdCGWjN9pEn7DfFUbdQZnhDR86SuskE5XsFVCcrYt30NU/m9SQ
         0GAA==
X-Forwarded-Encrypted: i=1;
 AJvYcCVuVIP6cuWhAdNmPfNRI6qw3pfPM2wFvj+akyN45dFmA2yLYpiWy51w7hnaG7WZdl7hh/d/KfGIWcDsVHh+NeiDAKYDBu6UU2n7HsnbW0pCwSBhV5z429Mi4iNy+xK+aK72hxGhh5d0I3HZ0k2BH90MLlRb
X-Gm-Message-State: AOJu0YyWXG9Zbjua59HU42ZNVG/G6SwQAmGCyZJp19fDKsUagwScEd0i
	olwbybGARws8YM7mxiiSR4/AWo4i4lp0B7PQrOD8bVJhCo8zZRxUYyuv02BAGSYCxpqHeEm1nwS
	VUTJr3+MkhuXKcjeSIBC8Fi6QbT4=
X-Google-Smtp-Source: 
 AGHT+IHh8g2XWqTxyPwJh5ilMqiz/xgyXjWf3K1MtjFC91znXaiI25fnMO0gnz4+biI8R8Yl39NUVQk9Vbr2tr/TMs0=
X-Received: by 2002:a17:90b:3651:b0:2b9:fc72:547e with SMTP id
 98e67ed59e1d1-2c1acc6dd47mr3888110a91.18.1717097007714; Thu, 30 May 2024
 12:23:27 -0700 (PDT)
MIME-Version: 1.0
References: <171706936834.39334.16043434987658907025@ietfa.amsl.com>
 <F6A70A5A-D620-47EC-996B-8DBD01CF813C@gmail.com>
In-Reply-To: <F6A70A5A-D620-47EC-996B-8DBD01CF813C@gmail.com>
From: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Date: Thu, 30 May 2024 21:23:16 +0200
Message-ID: 
 <CAEh=tcd1MFgZz5frZXRhrK9N2QeJDSQrmRgFypmj1hr6Hd0jrg@mail.gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000003096bc0619b0cd25"
Message-ID-Hash: POQ7UL7WDFKQE65MSHAFWPPBCNAGRWUH
X-Message-ID-Hash: POQ7UL7WDFKQE65MSHAFWPPBCNAGRWUH
X-MailFrom: zahed.sarker.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0;
 nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size;
 news-moderation; no-subject; digests; suspicious-header
CC: 6man Chairs <6man-chairs@ietf.org>, IESG <iesg@ietf.org>,
 IPv6 List <ipv6@ietf.org>, draft-ietf-6man-comp-rtg-hdr@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: =?utf-8?q?=5BIPv6=5DRe=3A_Zaheduzzaman_Sarker=27s_Discuss_on_draft-ietf-6man?=
 =?utf-8?q?-comp-rtg-hdr-09=3A_=28with_DISCUSS=29?=
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/ipv6/sbfZc4_PeBMtrblJ1zyylsOfeoc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

--0000000000003096bc0619b0cd25
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Bob, Hi Ron,

We discussed this today during the telechat, and I was made aware of rate
limiting property of ICMPv6 by my learned colleagues.

We are fine here. No need to add anything in this spec.

I will clear my discuss.

//Zahed

On Thu, 30 May 2024 at 18:11, Bob Hinden <bob.hinden@gmail.com> wrote:

> Hi,
>
>
> On May 30, 2024, at 4:42=E2=80=AFAM, Zaheduzzaman Sarker via Datatracker =
<
> noreply@ietf.org> wrote:
>
> Zaheduzzaman Sarker has entered the following ballot position for
> draft-ietf-6man-comp-rtg-hdr-09: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to
> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positio=
ns/
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-6man-comp-rtg-hdr/
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks for working on this specification.  Special Thanks to Gorry
> Fairhurst
> for the TSVART review.
>
> I have one question that I would like to discuss further to understand
> better -
>
> - In the processing rules, we are seding ICMPv6 Messages so how often are
> we
> sending them? if this is not rate limited, what are the risks we are not
> considering here?
>
>
> Rate limiting of ICMP error message is part of the ICMPv6 specification
> RFC 4443.
>
> See Section  2.4. Message Processing Rules, subsection (f) of
> https://datatracker.ietf.org/doc/html/rfc4443.
>
> Routers implement rate limiting ICMPv6 error messages.    Is there
> something specific about this draft that this needs to be called out?
>
> Bob
>
>
>
>
>
>
>

--0000000000003096bc0619b0cd25
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Bob, Hi Ron,</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">We discussed this today during the telechat, and I was made aware=
 of rate limiting property of ICMPv6 by my learned colleagues.=C2=A0</div><=
div dir=3D"auto"><br></div><div dir=3D"auto">We are fine here. No need to a=
dd anything in this spec.</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">I will clear my discuss.</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">//Zahed</div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Thu, 30 May 2024 at 18:11, Bob Hinden &lt;<a href=3D"mai=
lto:bob.hinden@gmail.com">bob.hinden@gmail.com</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div style=3D"line-break:after-white-space">Hi,<=
/div><div style=3D"line-break:after-white-space"><br id=3D"m_72073530389057=
94341lineBreakAtBeginningOfMessage"><div><br><blockquote type=3D"cite"><div=
>On May 30, 2024, at 4:42=E2=80=AFAM, Zaheduzzaman Sarker via Datatracker &=
lt;<a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org</=
a>&gt; wrote:</div><br><div><div>Zaheduzzaman Sarker has entered the follow=
ing ballot position for<br>draft-ietf-6man-comp-rtg-hdr-09: Discuss<br><br>=
When responding, please keep the subject line intact and reply to all<br>em=
ail addresses included in the To and CC lines. (Feel free to cut this<br>in=
troductory paragraph, however.)<br><br><br>Please refer to <a href=3D"https=
://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/" ta=
rget=3D"_blank">https://www.ietf.org/about/groups/iesg/statements/handling-=
ballot-positions/</a> <br>for more information about how to handle DISCUSS =
and COMMENT positions.<br><br><br>The document, along with other ballot pos=
itions, can be found here:<br><a href=3D"https://datatracker.ietf.org/doc/d=
raft-ietf-6man-comp-rtg-hdr/" target=3D"_blank">https://datatracker.ietf.or=
g/doc/draft-ietf-6man-comp-rtg-hdr/</a><br><br><br>------------------------=
----------------------------------------------<br>DISCUSS:<br>-------------=
---------------------------------------------------------<br><br>Thanks for=
 working on this specification.=C2=A0 Special Thanks to Gorry Fairhurst<br>=
for the TSVART review.<br><br>I have one question that I would like to disc=
uss further to understand better -<br><br> - In the processing rules, we ar=
e seding ICMPv6 Messages so how often are we<br> sending them? if this is n=
ot rate limited, what are the risks we are not<br> considering here?<br><br=
></div></div></blockquote></div><br></div><div style=3D"line-break:after-wh=
ite-space"><div>Rate limiting of ICMP error message is part of the ICMPv6 s=
pecification RFC 4443. =C2=A0=C2=A0</div><div><br></div><div>See Section =
=C2=A02.4. Message Processing Rules, subsection (f) of=C2=A0<a href=3D"http=
s://datatracker.ietf.org/doc/html/rfc4443" target=3D"_blank">https://datatr=
acker.ietf.org/doc/html/rfc4443</a>.</div><div><br></div><div>Routers imple=
ment rate limiting ICMPv6 error messages. =C2=A0 =C2=A0Is there something s=
pecific about this draft that this needs to be called out?</div></div><div =
style=3D"line-break:after-white-space"><div><br></div><div>Bob</div><div><b=
r></div><div><br></div><div><br></div><div><br></div><div><br></div><div><b=
r></div></div></blockquote></div></div>

--0000000000003096bc0619b0cd25--

