Return-Path: 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 C8DBBC1D6FB8 for ; Mon, 1 Jul 2024 12:34:40 -0700 (PDT) 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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=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 HZYJ4ubehZ3U for ; Mon, 1 Jul 2024 12:34:36 -0700 (PDT) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 C9832C1D620B for ; Mon, 1 Jul 2024 12:34:36 -0700 (PDT) Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-2ec17eb4493so50097311fa.2 for ; Mon, 01 Jul 2024 12:34:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719862475; x=1720467275; 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=gXnuPeuyA4V4S+67MqqbfMlu8KaNwQsWDb3nTC6Ry98=; b=ONjywfEJ/dTig9+qSSAbPdRTbTIlgwJHORnF6IE4EN/9wpt02SeWf6y8HUXA2wz7yX X7EQDVvLXcDdNs2icc6ecm5Dn+Lv7mKIHTVsF+xLe1f1kRTVs9+JNyp/Y2FWLhM3jMUK eGQbhydrgbKWMBUfupHUj9EYi+ShyjFvDjHaLy4NRqTwUT4sKghO2yR/JA+7XbZM9O7K lORgY5fOvGOJYDjBlirn+yKk6YCSbyUxEcq8COBB511T0Xnq14dIyEswrlcINJVCoDsE 0TjiXcUYlb/FFW4xuIwN4HReE1SZTqgfJWJTI5+uZY3LaWgQtkOWCjwg42hpizibR1+3 R4oQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719862475; x=1720467275; 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=gXnuPeuyA4V4S+67MqqbfMlu8KaNwQsWDb3nTC6Ry98=; b=X9uLmfZXcL51qoKEVcMkhoCJX+A3Kpp5VzRRoOAZg4PKedOfWNpk0yXzoj+upFSBFj QVcyjb5QlAB6Ave4yaxSpNKvzL9xrNVl6B9CCDjx//PANc9IVmYAraxlpRY2rxDJuFPd OXxDpjmagv4jhEA3vJ6VQ4rFvpUDJcpnuhBBRI+7ixleT21Oa5n/cmgneFXri5FFV3+5 qiuw47QNkLCT3jhNiT+ZwVMCKLppWPb1rEsjKstYtGoWCVrep4q1kT2klbtBvmH6i5Gt RyxncCJuGGMfdy4kKWYPJ0UcUU+Bkm/TYuSbD8ycN9c2kj4WNOTa2+xzbijcK1VeIo9f ejRw== X-Forwarded-Encrypted: i=1; AJvYcCUawjyDxCbaO/TkOY8B+2y+7gBr8r3+YlOaeM1zJiTD3NQLgYmTeE9vYj/kR2cJP/iL5ckQ1UaEnAk+xvg= X-Gm-Message-State: AOJu0Yxh/xTV9/FmW8HH2r+6P4Bi1KOZgOMrj5ez/zqYzdvzwF/G0xVH NdZBxXiiyVu/1yS4jKwTFuVUmSGUpwi27torkt6sW67n3UtQtr3XsHitSNmPDY+pjNyZthBYczG 1VxC4TSKtpJMLe95YEiKTdivGdA== X-Google-Smtp-Source: AGHT+IH08qBoZxlFrL7bjNVlQxV1MsF8U3Tvc9lMb+LBxbSHjek9SX+KwF+CcSmSdx1v8a2y0gPlklIAEUfmlppXYB4= X-Received: by 2002:a2e:a492:0:b0:2ec:5018:d4e2 with SMTP id 38308e7fff4ca-2ee5e39385cmr50703041fa.19.1719862474700; Mon, 01 Jul 2024 12:34:34 -0700 (PDT) MIME-Version: 1.0 References: <9BCD18D8-0597-4AFE-9C80-726542D0A7DE@pfrc.org> In-Reply-To: <9BCD18D8-0597-4AFE-9C80-726542D0A7DE@pfrc.org> From: Yingzhen Qu Date: Mon, 1 Jul 2024 12:34:23 -0700 Message-ID: To: Jeffrey Haas Content-Type: multipart/alternative; boundary="000000000000de0129061c34afef" Message-ID-Hash: VV764FJMOIO45HXMXBHLL2IJ2OXELAEP X-Message-ID-Hash: VV764FJMOIO45HXMXBHLL2IJ2OXELAEP X-MailFrom: yingzhen.ietf@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Roman Danyliw , "idr@ietf.org" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BIdr=5D_Re=3A_AD_Review_of_draft-ietf-idr-bgp-sendholdtimer-10?= List-Id: Inter-Domain Routing Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000de0129061c34afef Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Jeff, Thanks for the confirmation. I've updated the draft to use trust200902. As for which disclaimer to use, this is an IETF wide issue. For long-lived documents, we need to be able to identify which disclaimer to use. Thanks, Yingzhen On Mon, Jul 1, 2024 at 11:59=E2=80=AFAM Jeffrey Haas wrote= : > Use trust200902. > > The IDR chairs will work with the IESG to figure out how we can get some > sort of long-lived documentation that the approval exists. > > -- Jeff > > > On Jul 1, 2024, at 2:01 PM, Yingzhen Qu wrote: > > Hi Norman andJob, > > I looked at a few RFCs with normative references published before 10 > November 2008, where trust200902 was used instead of pre5378Trust200902. > How do we know which one should be used? > > Thanks, > Yingzhen > > On Sun, Jun 30, 2024 at 6:52=E2=80=AFPM Job Snijders wro= te: > >> On Mon, 1 Jul 2024 at 10:41, Yingzhen Qu wrote= : >> >>> Hi Roman, >>> >>> Thanks for the review and comments. I've uploaded version -11 to addres= s >>> your comments. Please see detailed answers inline below. >>> >>> Thanks, >>> Yingzhen >>> >>> On Tue, Jun 25, 2024 at 8:48=E2=80=AFAM Roman Danyliw wr= ote: >>> >>>> Hi! >>>> >>>> I'm swapping with John and stepping in as the responsible AD for >>>> draft-ietf-idr-bgp-sendholdtimer. I performed an AD review on >>>> draft-ietf-idr-bgp-sendholdtimer-10. Thanks for this document. My >>>> feedback is as follows: >>>> >>>> ** idnits reports: >>>> >>>> -- The document seems to lack a disclaimer for pre-RFC5378 work, but >>>> may >>>> have content which was first submitted before 10 November 2008. >>>> If you >>>> have contacted all the original authors and they are all willing >>>> to grant >>>> the BCP78 rights to the IETF Trust, then this is fine, and you ca= n >>>> ignore >>>> this comment. If not, you may need to add the pre-RFC5378 >>>> disclaimer. >>>> (See the Legal Provisions document at >>>> https://trustee.ietf.org/license-info for more information.) >>>> >>>> Have the original authors been contact or should the alternative >>>> boilerplate be used? >>>> >>> >>> [Yingzhen]: updated to use "pre5378Trust200902". >>> >> >> >> I am not sure that=E2=80=99s needed. As far as I can tell idnits is bein= g too >> conservative in this instance. >> >> Multiple updates to RFC 4271 have been performed over the last few years >> with the trust200902, where one or two sentences were copied to indicate >> the =E2=80=9Cnew text=E2=80=9D insertion point, for example RFC 8212. >> >> I=E2=80=99m also under the impression the original authors granted the I= ETF Trust >> some rights. >> >> I=E2=80=99d prefer if we change the boilerplate back. >> >> Kind regards, >> >> Job >> >> _______________________________________________ > Idr mailing list -- idr@ietf.org > To unsubscribe send an email to idr-leave@ietf.org > > > --000000000000de0129061c34afef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Jeff,

Thanks for the confirmation. I= 've updated the draft to use trust200902.

As f= or which disclaimer to use, this is an IETF wide issue. For long-lived docu= ments, we need to be able to identify which disclaimer to use.
Thanks,
Yingzhen

On Mon, Jul 1, 2024 at 11:59= =E2=80=AFAM Jeffrey Haas <jhaas@pfrc.o= rg> wrote:
Use trust200902. =C2=A0
The IDR chairs will work with the IESG to figure out how we can= get some sort of long-lived documentation that the approval exists.
<= div>
-- Jeff


On Jul 1, 2024, at 2:01 PM, Yingzhen Qu <yingzhen.ietf@gmail.com> wrote:<= /div>
Hi Norman andJob,

I looked at a few RFCs with normati= ve references published=C2=A0before 10 N= ovember 2008, where trust200902 was used instead of pre5378Trust200902. How= do we know which one should be used?

Thanks,
Yingzh= en

On Sun, Jun 30, 2024 at 6:52=E2=80=AFPM Job Snijders <job@fastly.com> wr= ote:
On Mon= , 1 Jul 2024 at 10:41, Yingzhen Qu <yingzhen.ietf@gmail.com> wrote:
Hi Roman,

Thanks for the review and comments. I've uploaded = version -11 to address your comments. Please see detailed=C2=A0answers inli= ne below.

Thanks,
Yingzhen

On Tue, Jun 25= , 2024 at 8:48=E2=80=AFAM Roman Danyliw <rdd@cert.org> wrote:
Hi!

I'm swapping with John and stepping in as the responsible AD for draft-= ietf-idr-bgp-sendholdtimer.=C2=A0 I performed an AD review on draft-ietf-id= r-bgp-sendholdtimer-10.=C2=A0 Thanks for this document.=C2=A0 My feedback i= s as follows:

** idnits reports:

=C2=A0 -- The document seems to lack a disclaimer for pre-RFC5378 work, but= may
=C2=A0 =C2=A0 =C2=A0have content which was first submitted before 10 Novemb= er 2008.=C2=A0 If you
=C2=A0 =C2=A0 =C2=A0have contacted all the original authors and they are al= l willing to grant
=C2=A0 =C2=A0 =C2=A0the BCP78 rights to the IETF Trust, then this is fine, = and you can ignore
=C2=A0 =C2=A0 =C2=A0this comment.=C2=A0 If not, you may need to add the pre= -RFC5378 disclaimer.
=C2=A0 =C2=A0 =C2=A0(See the Legal Provisions document at
=C2=A0 =C2=A0 =C2=A0https://trustee.ietf.org/license-info= for more information.)

Have the original authors been contact or should the alternative boilerplat= e be used?

[Yingzhen]: updated to use &= quot;pre5378Trust200902".


I am not sure that=E2=80=99s needed. As far as I can tell i= dnits is being too conservative in this instance.
=
= Multiple updates to RFC 4271 have been performed over the last few years wi= th the trust200902, where one or two sentences were copied to indicate the = =E2=80=9Cnew text=E2=80=9D insertion point, for example RFC 8212.

I=E2=80= =99m also under the impression the original authors granted the IETF Trust = some rights.

I=E2=80=99d prefer if we change the boilerplate back.
<= div style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">
Kind regard= s,

Job

=
_______________________________________________
Idr mailing list -- idr@ietf.org
To unsubs= cribe send an email to idr-leave@ietf.org

--000000000000de0129061c34afef--