Re: [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ssh-iana-requirements-03> for your review
Sandy Ginoza <sginoza@amsl.com> Tue, 23 January 2024 19:58 UTC
Return-Path: <sginoza@amsl.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 4C70AC14F714; Tue, 23 Jan 2024 11:58:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 zOWTgRK5ewlH; Tue, 23 Jan 2024 11:58:29 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 859A9C14F711; Tue, 23 Jan 2024 11:58:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 78850424B432; Tue, 23 Jan 2024 11:58:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NnIBSN9GIN1C; Tue, 23 Jan 2024 11:58:29 -0800 (PST)
Received: from smtpclient.apple (2603-8000-9603-b513-81ef-3d94-f702-3bb5.res6.spectrum.com [IPv6:2603:8000:9603:b513:81ef:3d94:f702:3bb5]) by c8a.amsl.com (Postfix) with ESMTPSA id 18AFE424B427; Tue, 23 Jan 2024 11:58:29 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <002901da4cb4$1ef6b580$5ce42080$@akayla.com>
Date: Tue, 23 Jan 2024 11:57:56 -0800
Cc: RFC Editor <rfc-editor@rfc-editor.org>, Roman Danyliw <rdd@cert.org>, auth48archive@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3615E41A-91B0-4126-8CD7-042019639394@amsl.com>
References: <20231205013254.6974C1182211@rfcpa.amsl.com> <002901da4cb4$1ef6b580$5ce42080$@akayla.com>
To: peter@akayla.com
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/0oZBSaUvlOXtAbEuKp1kQvVBaiU>
Subject: Re: [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ssh-iana-requirements-03> 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: Tue, 23 Jan 2024 19:58:30 -0000
Hi Peter, Thank you for your review! We have made the updates and marked your approval on the AUTH48 page. The current file are available here: https://www.rfc-editor.org/authors/rfc9519.xml https://www.rfc-editor.org/authors/rfc9519.txt https://www.rfc-editor.org/authors/rfc9519.pdf https://www.rfc-editor.org/authors/rfc9519.html AUTH48 diff: https://www.rfc-editor.org/authors/rfc9519-auth48diff.html Comprehensive diffs: https://www.rfc-editor.org/authors/rfc9519-diff.html https://www.rfc-editor.org/authors/rfc9519-rfcdiff.html AUTH48 page: https://www.rfc-editor.org/auth48/rfc9519 As we have your approval, we will continue with the publication process shortly. Thank you. RFC Editor/sg > On Jan 21, 2024, at 1:52 PM, <peter@akayla.com> <peter@akayla.com> wrote: > > I approve publication of this specification as modified by the RFC Editor. I am fine with the first two changes marked [rfced] and the third one (inclusive language) does not appear to apply. I have walked through all 4 formats for the RFC, and they appear all right from what I can discern. > > Thanks for the hard work in getting this document into shape for publication. > > Kind regards, > -Peter Yee > > -----Original Message----- > From: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org> > Sent: Monday, December 4, 2023 5:33 PM > To: peter@akayla.com > Cc: rfc-editor@rfc-editor.org; rdd@cert.org; auth48archive@rfc-editor.org > Subject: AUTH48: RFC-to-be 9519 <draft-yee-ssh-iana-requirements-03> for your review > > *****IMPORTANT***** > > Updated 2023/12/04 > > 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/rfc9519.xml > https://www.rfc-editor.org/authors/rfc9519.html > https://www.rfc-editor.org/authors/rfc9519.pdf > https://www.rfc-editor.org/authors/rfc9519.txt > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9519-diff.html > https://www.rfc-editor.org/authors/rfc9519-rfcdiff.html (side by side) > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9519-xmldiff1.html > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9519 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC 9519 (draft-yee-ssh-iana-requirements-03) > > Title : Update to the IANA SSH Protocol Parameters Registry Requirements > Author(s) : P. Yee > WG Chair(s) : > Area Director(s) : > > >
- [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ssh-ia… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ss… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ss… Sandy Ginoza
- Re: [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ss… Sandy Ginoza
- Re: [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ss… Sandy Ginoza
- [auth48] [AD - Roman] Re: AUTH48: RFC-to-be 9519 … Sandy Ginoza
- Re: [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ss… peter
- Re: [auth48] AUTH48: RFC-to-be 9519 <draft-yee-ss… Sandy Ginoza