[auth48] [AD - Roman] Re: AUTH48: RFC-to-be 9519 <draft-yee-ssh-iana-requirements-03> for your review
Sandy Ginoza <sginoza@amsl.com> Fri, 12 January 2024 02:28 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 5E581C14F6F6; Thu, 11 Jan 2024 18:28:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 8VumQcm3KWBf; Thu, 11 Jan 2024 18:28:02 -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 AE486C14F6F4; Thu, 11 Jan 2024 18:28:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 9D355424B432; Thu, 11 Jan 2024 18:28:02 -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 mnrDQaLF8_Uc; Thu, 11 Jan 2024 18:28:02 -0800 (PST)
Received: from smtpclient.apple (2603-8000-9603-b513-74be-48da-175f-cb50.res6.spectrum.com [IPv6:2603:8000:9603:b513:74be:48da:175f:cb50]) by c8a.amsl.com (Postfix) with ESMTPSA id 6BDE6424B427; Thu, 11 Jan 2024 18:28:02 -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: <B575A545-883C-4CA4-8C14-C98A6426C438@amsl.com>
Date: Thu, 11 Jan 2024 18:27:36 -0800
Cc: auth48archive <auth48archive@rfc-editor.org>, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2911E8E3-FE3F-4B9F-966F-F40DE536D960@amsl.com>
References: <20231205013505.839761182211@rfcpa.amsl.com> <969E6CC1-F69A-418E-A058-D6E6D45E57D4@amsl.com> <364C2776-3F6E-408F-9CA8-8EF6BD1DE4D0@amsl.com> <B575A545-883C-4CA4-8C14-C98A6426C438@amsl.com>
To: peter@akayla.com, Roman Danyliw <rdd@cert.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/I0Loqy6wYAFN6LLQk0vYD-SxESk>
Subject: [auth48] [AD - Roman] Re: 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: Fri, 12 Jan 2024 02:28:07 -0000
Hi Roman, Can you help us reach Peter, or perhaps you know if he is on holiday? This document entered AUTH on 4 Dec and we have yet to hear from him. His email address looks current based on what I see in the Datatracker. Thanks, Sandy > On Jan 8, 2024, at 10:07 AM, Sandy Ginoza <sginoza@amsl.com> wrote: > > Hi Peter, > > Happy New Year! > > This is a friendly reminder we await your review of this document. While reviewing this document, please respond to the questions below. > >> 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 >> >> 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/rfc9519.original.v2v3.xml >> >> XMLv3 file that is a best effort to capture v3-related format updates >> only: >> https://www.rfc-editor.org/authors/rfc9519.form.xml > > > Thank you, > RFC Editor/sg > > > >> On Dec 15, 2023, at 6:15 PM, Sandy Ginoza <sginoza@amsl.com> wrote: >> >> Greetings, >> >> We do not believe we have heard from you regarding this document’s readiness for publication. Please review the questions below and the edited document and let us know if any updates are needed. >> >> Thank you, >> RFC Editor/sg >> >> >>> On Dec 8, 2023, at 11:21 AM, Sandy Ginoza <sginoza@amsl.com> wrote: >>> >>> Greetings Peter, >>> >>> This is a friendly reminder that we await your response to the questions below and your input regarding the edited document. >>> >>> We will wait to hear from you before continuing with the publication process. >>> >>> Thank you, >>> RFC Editor/sg >>> >>> >>>> On Dec 4, 2023, at 5:35 PM, rfc-editor@rfc-editor.org wrote: >>>> >>>> Authors, >>>> >>>> While reviewing this document during AUTH48, please resolve (as necessary) >>>> the following questions, which are also in the XML file. >>>> >>>> 1) <!-- [rfced] For clarity, would you like to update the text as follows? >>>> >>>> Original: >>>> This specification updates the requirements for adding new entries to >>>> the IANA Secure Shell (SSH) Protocol Parameters registry. Currently, >>>> the requirement is generally for "IETF Review", as defined in RFC >>>> 8126, although a few portions of the registry require "Standards >>>> Action". >>>> >>>> Perhaps: >>>> This specification updates the registration policies for adding new >>>> entries to registries within the IANA "Secure Shell (SSH) Protocol >>>> Parameters" group of registries. Currently, the registration policy is >>>> generally IETF Review, as defined in RFC 8126, although a few registries >>>> require Standards Action. >>>> --> >>>> >>>> >>>> 2) <!-- [rfced] We verified that these actions match what what appears in >>>> the IANA registries. We note that the registries now list this document as >>>> a reference. Should this action be listed here? For example, would you >>>> like to add the following sentence to the text? >>>> >>>> Affected registries now list this document as a reference. >>>> --> >>>> >>>> >>>> 3) <!-- [rfced] Please review the "Inclusive Language" portion of the >>>> online Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> >>>> and let us know if any changes are needed. >>>> >>>> Note that our script did not flag any words in particular, but this should >>>> still be reviewed as a best practice. >>>> --> >>>> >>>> >>>> Thank you. >>>> >>>> RFC Editor >>>> >>>> >>>> >>>> On Dec 4, 2023, at 5:32 PM, rfc-editor@rfc-editor.org wrote: >>>> >>>> *****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 >>>> >>>> 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/rfc9519.original.v2v3.xml >>>> >>>> XMLv3 file that is a best effort to capture v3-related format updates >>>> only: >>>> https://www.rfc-editor.org/authors/rfc9519.form.xml >>>> >>>> >>>> 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 >>>> >>>> -------------------------------------- >>>> RFC9519 (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