Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for your review
Yossi Gilad <yossigi@cs.huji.ac.il> Mon, 03 October 2022 19:08 UTC
Return-Path: <yossigi@cs.huji.ac.il>
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 04941C1524B0 for <auth48archive@ietfa.amsl.com>; Mon, 3 Oct 2022 12:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.004
X-Spam-Level:
X-Spam-Status: No, score=-7.004 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cs.huji.ac.il
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 nk-fBqBrTorN for <auth48archive@ietfa.amsl.com>; Mon, 3 Oct 2022 12:08:03 -0700 (PDT)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54CA1C152572 for <auth48archive@rfc-editor.org>; Mon, 3 Oct 2022 12:08:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:In-Reply-To:References:MIME-Version; bh=ouZHMiAxWxlirEdVENqgAnvBFlhPrl6+8Jzx9Pguvdg=; b=gGLPFoMNqIW866qJ+Nfmc5rAvovuJd/sZ5CjwZAQQyXir3azO5CGSpIENGEqefr0Vn4ZTXJeCDoTuFDLadXKPqaDJyAk8yaI8EQ/jkD37dK6BT7c/BY3bEa90wskPButq5k4NsO6FOon6fWEOoB3JPADB3uYzP4EO6yegCedz7jkPLSXQSZuGo0/YbjcT8vTNnYA9BQYeeQrXsi/svrARYegzBIm7pSc8d5co4FqdY4I0dwdtK44BRMVRKP/Ui9htKdNPbCDGIgaLHoKlx8eV+g2gOdhuHjsVitApGeFh+YEnwJ9vTZO4KLiRDhpANSmUEeNhZjbe9caHKS3C0CW5g==;
Received: from e-bsd.cs.huji.ac.il ([132.65.80.241] helo=outmail.cs.huji.ac.il ident=exim) by kabab.cs.huji.ac.il with esmtp id 1ofQfI-0000s5-MO for auth48archive@rfc-editor.org; Mon, 03 Oct 2022 21:59:44 +0300
Received: from [209.85.208.41] (helo=mail-ed1-f41.google.com) by outmail.cs.huji.ac.il with esmtpsa id 1ofQfI-0004ep-HK for auth48archive@rfc-editor.org; Mon, 03 Oct 2022 21:59:44 +0300
Received: by mail-ed1-f41.google.com with SMTP id z97so15864265ede.8 for <auth48archive@rfc-editor.org>; Mon, 03 Oct 2022 11:59:44 -0700 (PDT)
X-Gm-Message-State: ACrzQf1ICh5Rec7BK69TBaKetVnprluJN3K1VOsxIAi3EoRjR/y0VPYu R3d6nZO3C5lFuuIHO6aSViDUo0uZ0rV/A/sZZpM+2Q==
X-Google-Smtp-Source: AMsMyM4P6kpa1AZLup4ou1QEwn7zQKwM9+9YCQ1rmDgsI01yr7OtsfarNWkdtReTtvLC7sr1PvwzkYiBZEUe5fD2UWY=
X-Received: by 2002:aa7:c314:0:b0:458:dc90:467a with SMTP id l20-20020aa7c314000000b00458dc90467amr7730524edq.284.1664823583647; Mon, 03 Oct 2022 11:59:43 -0700 (PDT)
MIME-Version: 1.0
References: <20220927053054.536874C956@rfcpa.amsl.com>
In-Reply-To: <20220927053054.536874C956@rfcpa.amsl.com>
From: Yossi Gilad <yossigi@cs.huji.ac.il>
Date: Mon, 03 Oct 2022 14:59:32 -0400
X-Gmail-Original-Message-ID: <CAM=NG19rD+2SneYB4XDKna=2fJ+egUpwf1Hyeuxp8sBa2AU++w@mail.gmail.com>
Message-ID: <CAM=NG19rD+2SneYB4XDKna=2fJ+egUpwf1Hyeuxp8sBa2AU++w@mail.gmail.com>
To: rfc-editor@rfc-editor.org
Cc: goldbe@cs.bu.edu, kotikalapudi.sriram@nist.gov, job@fastly.com, benm@workonline.africa, sidrops-ads@ietf.org, sidrops-chairs@ietf.org, morrowc@ops-netman.net, warren@kumari.net, auth48archive@rfc-editor.org
Content-Type: multipart/alternative; boundary="00000000000051526f05ea25f2f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/gp_ro_Bah_FzGMFSYx10HjAcHy4>
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: Mon, 03 Oct 2022 19:08:08 -0000
I approve this RFC for publication On Tue, Sep 27, 2022 at 1:31 AM <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