Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for your review
Job Snijders <job@fastly.com> Wed, 28 September 2022 12:42 UTC
Return-Path: <job@fastly.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21873C15E3FE for <auth48archive@ietfa.amsl.com>; Wed, 28 Sep 2022 05:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.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 5yMUoWcgSwx8 for <auth48archive@ietfa.amsl.com>; Wed, 28 Sep 2022 05:42:11 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 1A428C1522DB for <auth48archive@rfc-editor.org>; Wed, 28 Sep 2022 05:42:11 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id b2so3972170eja.6 for <auth48archive@rfc-editor.org>; Wed, 28 Sep 2022 05:42:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date; bh=z4McTmFk934oEa9A8sM0dGWsiNRHCvgUlJCykkF5cOw=; b=A1CcWWmsPSkxWugHAebZgi991OwEpgldszIS2aH0zP0m8qaPT+kEf6sfZ6+WlD6/0U 1QL4HRWxRAzWFh/rzgzxBEt57Lg5Z51xyRkoJ5NAblrcbW0ILKGJSj0VLXXapHp9gesj 6KffyEmJ6Tda9wdDA29KAWs7sMwsuWBVUxw4k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date; bh=z4McTmFk934oEa9A8sM0dGWsiNRHCvgUlJCykkF5cOw=; b=pP5JWMYUP7hMbGrS3aAGNBt9YWpfMCdA+iskOX5SOJw5VK+mm2jYYS3+UGx1qQTJEl zDWimpUKfMW7m0fzQvBZGkeNhY3PPnq+pFfLxeCjNT/+GKyhBY9/UiGx5CYgFhX+LlQw 9XTrTComJTm/8qpke2fIvrsbr2cRdqKNrlpH2Hy5UIVzovdaU7S0UtaCbMGPEJBRgs/r WpUfbaxU3vdcOsD5l5J9RLG3ENAA/arTSJ/0quOz/UJQsOm7w3PdyA/sVTh8lO8oJDJ+ B/JIwMUcc3pz1yY3/Qimg1vrJiICQZjqZo2r+MkUHw9ubZkIZYF4W3UTLIqR5uHEVzYN X6pw==
X-Gm-Message-State: ACrzQf2Sn0qMfZNysY6K/CswmdVlPMYO55f6kqwt6Ssu+J/iMRSOmFBS m1mVXsmh3ChzDbqpIIhpwMdmkQ==
X-Google-Smtp-Source: AMsMyM6h5XIERKFQxqClEo4j5F1SiXTgVip334th8d9RPE37T12h6qkhW/pexmxmMhgpVJbun69PIQ==
X-Received: by 2002:a17:907:783:b0:76e:f290:8b5 with SMTP id xd3-20020a170907078300b0076ef29008b5mr28083562ejb.395.1664368929495; Wed, 28 Sep 2022 05:42:09 -0700 (PDT)
Received: from snel ([2a10:3781:276:1:16f6:d8ff:fe47:2eb7]) by smtp.gmail.com with ESMTPSA id by7-20020a170906a2c700b007708130c287sm2278172ejb.40.2022.09.28.05.42.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 28 Sep 2022 05:42:09 -0700 (PDT)
Date: Wed, 28 Sep 2022 14:42:07 +0200
From: Job Snijders <job@fastly.com>
To: rfc-editor@rfc-editor.org
Cc: yossigi@cs.huji.ac.il, goldbe@cs.bu.edu, kotikalapudi.sriram@nist.gov, benm@workonline.africa, sidrops-ads@ietf.org, sidrops-chairs@ietf.org, morrowc@ops-netman.net, warren@kumari.net, auth48archive@rfc-editor.org
Message-ID: <YzRBHyNOvG2x1pVX@snel>
References: <20220927053054.536874C956@rfcpa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20220927053054.536874C956@rfcpa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/Q11sp1NXnUgh5y786PHK1TTIbs4>
Subject: Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2022 12:42:15 -0000
Hi all, I approve this RFC for publication. Kind regards, Job On Mon, Sep 26, 2022 at 10:30:54PM -0700, rfc-editor@rfc-editor.org wrote: > *****IMPORTANT***** > > Updated 2022/09/26 > > RFC Author(s): > -------------- > > Instructions for Completing AUTH48 > > Your document has now entered AUTH48. Once it has been reviewed and > approved by you and all coauthors, it will be published as an RFC. > If an author is no longer available, there are several remedies > available as listed in the FAQ (https://www.rfc-editor.org/faq/). > > You and you coauthors are responsible for engaging other parties > (e.g., Contributors or Working Group) as necessary before providing > your approval. > > Planning your review > --------------------- > > Please review the following aspects of your document: > > * RFC Editor questions > > Please review and resolve any questions raised by the RFC Editor > that have been included in the XML file as comments marked as > follows: > > <!-- [rfced] ... --> > > These questions will also be sent in a subsequent email. > > * Changes submitted by coauthors > > Please ensure that you review any changes submitted by your > coauthors. We assume that if you do not speak up that you > agree to changes submitted by your coauthors. > > * Content > > Please review the full content of the document, as this cannot > change once the RFC is published. Please pay particular attention to: > - IANA considerations updates (if applicable) > - contact information > - references > > * Copyright notices and legends > > Please review the copyright notice and legends as defined in > RFC 5378 and the Trust Legal Provisions > (TLP – https://trustee.ietf.org/license-info/). > > * Semantic markup > > Please review the markup in the XML file to ensure that elements of > content are correctly tagged. For example, ensure that <sourcecode> > and <artwork> are set correctly. See details at > <https://authors.ietf.org/rfcxml-vocabulary>. > > * Formatted output > > Please review the PDF, HTML, and TXT files to ensure that the > formatted output, as generated from the markup in the XML file, is > reasonable. Please note that the TXT will have formatting > limitations compared to the PDF and HTML. > > > Submitting changes > ------------------ > > To submit changes, please reply to this email using ‘REPLY ALL’ as all > the parties CCed on this message need to see your changes. The parties > include: > > * your coauthors > > * rfc-editor@rfc-editor.org (the RPC team) > > * other document participants, depending on the stream (e.g., > IETF Stream participants are your working group chairs, the > responsible ADs, and the document shepherd). > > * auth48archive@rfc-editor.org, which is a new archival mailing list > to preserve AUTH48 conversations; it is not an active discussion > list: > > * More info: > https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc > > * The archive itself: > https://mailarchive.ietf.org/arch/browse/auth48archive/ > > * Note: If only absolutely necessary, you may temporarily opt out > of the archiving of messages (e.g., to discuss a sensitive matter). > If needed, please add a note at the top of the message that you > have dropped the address. When the discussion is concluded, > auth48archive@rfc-editor.org will be re-added to the CC list and > its addition will be noted at the top of the message. > > You may submit your changes in one of two ways: > > An update to the provided XML file > — OR — > An explicit list of changes in this format > > Section # (or indicate Global) > > OLD: > old text > > NEW: > new text > > You do not need to reply with both an updated XML file and an explicit > list of changes, as either form is sufficient. > > We will ask a stream manager to review and approve any changes that seem > beyond editorial in nature, e.g., addition of new text, deletion of text, > and technical changes. Information about stream managers can be found in > the FAQ. Editorial changes do not require approval from a stream manager. > > > Approving for publication > -------------------------- > > To approve your RFC for publication, please reply to this email stating > that you approve this RFC for publication. Please use ‘REPLY ALL’, > as all the parties CCed on this message need to see your approval. > > > Files > ----- > > The files are available here: > https://www.rfc-editor.org/authors/rfc9319.xml > https://www.rfc-editor.org/authors/rfc9319.html > https://www.rfc-editor.org/authors/rfc9319.pdf > https://www.rfc-editor.org/authors/rfc9319.txt > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9319-diff.html > https://www.rfc-editor.org/authors/rfc9319-rfcdiff.html (side by side) > > For your convenience, we have also created an alt-diff file that will > allow you to more easily view changes where text has been deleted or > moved: > https://www.rfc-editor.org/authors/rfc9319-alt-diff.html > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9319-xmldiff1.html > > The following files are provided to facilitate creation of your own > diff files of the XML. > > Initial XMLv3 created using XMLv2 as input: > https://www.rfc-editor.org/authors/rfc9319.original.v2v3.xml > > XMLv3 file that is a best effort to capture v3-related format updates > only: > https://www.rfc-editor.org/authors/rfc9319.form.xml > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9319 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9319 (draft-ietf-sidrops-rpkimaxlen-15) > > Title : The Use of maxLength in the RPKI > Author(s) : Y. Gilad, S. Goldberg, K. Sriram, J. Snijders, B. Maddison > WG Chair(s) : Keyur Patel, Chris Morrow > > Area Director(s) : Warren Kumari, Robert Wilton > >
- [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-sidro… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Ben Maddison
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Rebecca VanRheenen
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Ben Maddison
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Sriram, Kotikalapudi (Fed)
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Job Snijders
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Sharon Goldberg
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Rebecca VanRheenen
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Rebecca VanRheenen
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Sriram, Kotikalapudi (Fed)
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Ben Maddison
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Rebecca VanRheenen
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Ben Maddison
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Yossi Gilad
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Rebecca VanRheenen
- [auth48] [AD] Re: AUTH48: RFC-to-be 9319 <draft-i… Rebecca VanRheenen
- Re: [auth48] [AD] Re: AUTH48: RFC-to-be 9319 <dra… Sriram, Kotikalapudi (Fed)
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Sriram, Kotikalapudi (Fed)
- Re: [auth48] [AD] AUTH48: RFC-to-be 9319 <draft-i… Rebecca VanRheenen
- Re: [auth48] [AD] Re: AUTH48: RFC-to-be 9319 <dra… Warren Kumari
- [auth48] [AD attention] RE: [AD] Re: AUTH48: RFC-… Sriram, Kotikalapudi (Fed)
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Sriram, Kotikalapudi (Fed)
- Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-s… Sriram, Kotikalapudi (Fed)
- [auth48] [AD] Re: AUTH48: RFC-to-be 9319 <draft-i… Rebecca VanRheenen
- Re: [auth48] [AD] Re: AUTH48: RFC-to-be 9319 <dra… Warren Kumari
- Re: [auth48] [AD] AUTH48: RFC-to-be 9319 <draft-i… Rebecca VanRheenen