Hi Doug, all, I’m neutral on this as soon as we are consistent.
My proposal was based on RFC5280, which uses “Certification Authority”. Cheers, Med De : Douglas Gash (dcmgash) <[email protected]> Envoyé : dimanche 9 novembre 2025 21:51 À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; [email protected] Cc : [email protected]; [email protected]; Joe Clarke (jclarke) <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected] Objet : Re: AUTH48: RFC-to-be 9887 <draft-ietf-opsawg-tacacs-tls13-24> for your review Hi Mohamed, Many thanks for your comment on the CA consistency. Having reviewed, we understand the correct terminology is “Certificate Authorities”, in which case the remedy is to fix the title of 5.1.4. Thanks! Cisco Confidential From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Date: Tuesday, 28 October 2025 at 15:18 To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, Joe Clarke (jclarke) <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, Douglas Gash (dcmgash) <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: RE: AUTH48: RFC-to-be 9887 <draft-ietf-opsawg-tacacs-tls13-24> for your review Hi Sandy, I trust the authors will follow SOON. Please find below one minor comment: CURRENT: 3.4. TLS Certificate-Based Authentication ... Deploying TLS certificate-based authentication correctly will considerably improve the security of TACACS+ deployments. It is essential for implementers and operators to understand the implications of a TLS certificate-based authentication solution, including the correct handling of certificates, Certificate Authorities (CAs), ... 5.1.4. Unreachable Certification Authority (CA) For consistency, I guess that we need to change "Certificate Authorities (CAs)" to "Certification Authorities (CAs)". Thank you. Cheers, Med > -----Message d'origine----- > De : [email protected]<mailto:[email protected]> > <[email protected]<mailto:[email protected]>> > Envoyé : samedi 25 octobre 2025 03:02 > À : [email protected]<mailto:[email protected]>; > [email protected]<mailto:[email protected]>; > [email protected]<mailto:[email protected]>; > [email protected]<mailto:[email protected]> > Cc : [email protected]<mailto:[email protected]>; > [email protected]<mailto:[email protected]>; opsawg- > [email protected]<mailto:[email protected]>; > [email protected]<mailto:[email protected]>; BOUCADAIR Mohamed INNOV/NET > <[email protected]<mailto:[email protected]>>; > [email protected]<mailto:[email protected]> > Objet : Re: AUTH48: RFC-to-be 9887 <draft-ietf-opsawg-tacacs- > tls13-24> for your review > > > Authors, > > While reviewing this document during AUTH48, please resolve (as > necessary) the following questions, which are also in the source > file. > > 1) <!-- [rfced] May we update this text for readability? > > Original: > While the content of the protocol is highly sensitive, TACACS+ > lacks > effective confidentiality, integrity, and authentication of the > connection and network traffic between the TACACS+ server and > client, > requiring secure transport to safeguard a deployment. The > security > mechanisms as described in Section 10 of [RFC8907] are > extremely > weak. > > Suggested: > The content of the protocol is highly sensitive and requires > secure transport to safeguard a deployment. However, TACACS+ > lacks > effective confidentiality, integrity, and authentication of the > connection and network traffic between the TACACS+ server and > client. > The security mechanisms as described in Section 10 of [RFC8907] > are > extremely weak. > --> > > > 2) <!-- [rfced] Should "for test" be "for testing"? > > Original: > It is a connection without TLS, using the unsecure > TACACS+ authentication and obfuscation (or the unobfuscated > option > for test). > --> > > > 3) <!-- [rfced] We recommend simplifying this sentence for > clarity. Does the connection persist until either a) the TLS > TACACS+ peer closes it or b) an inactivity timeout occurs? Please > consider how the text may be updated. > > Original: > The connection persists until the TLS TACACS+ peer closes it, > either > due to an error, or at the conclusion of the TACACS+ session, > or, if > Single Connection Mode (Section 4.3 of [RFC8907]) has been > negotiated, when an inactivity timeout occurs. > > Perhaps: > The connection persists until the TLS TACACS+ peer closes it or > until an inactivity timeout occurs when Single Connection Mode > (Section 4.3 of [RFC8907]) is used. The TLS TACACS+ peer may > close > the connection due to an error or because the TACACS+ session > has > concluded. > --> > > > 4) <!-- [rfced] "verification" does not appear in Section 6 of RFC > 5280. > Would it be helpful to the reader to use "validation" for > consistency with the reference? > > Original: > The implementation of certificate-based mutual authentication > MUST > support certificate path verification as described in Section 6 > of > [RFC5280]. > --> > > > 5) <!-- [rfced] Is it correct to refer to the "TLS Resumption > protocol"? > > Original: > The TLS Resumption protocol, detailed in [RFC8446], can > minimize the > number of round trips required during the handshake process. > > Perhaps: > TLS Resumption [RFC8446] can minimize the > number of round trips required during the handshake process. > --> > > > 6) <!-- [rfced] Section 5.2 of [RFC5425] is titled "Subject Name > Authorization" and doesn't appear to mention any kind of > obfuscation mechanism. Also, is the obfuscation mechanism > described in both RFC 8907 > and 5425 (or other)? Please review and let us know how/if the > text may be > clarified. > > Original: > [RFC8907] describes the obfuscation mechanism, documented in > Section > 5.2 of [RFC5425]. Such a method is weak. > > > --> > > > 7) <!-- [rfced] We are having trouble parsing "for implementing > protocols that use TLS and their deployment." > > Original: > [BCP195] offers substantial guidance for implementing protocols > that > use TLS and their deployment. > > Perhaps: > [BCP195] offers substantial guidance for implementing and > deploying > protocols that use TLS. > --> > > > 8) <!-- [rfced] The use of "MUST" twice in this sentence reads > oddly. > Please review. > > Original: > Further, operators MUST ensure that the TLS TACACS+ servers > covered > by a wildcard certificate MUST be impervious to redirection of > traffic to a different server (for example, due to on-path > attacks or > DNS cache poisoning). > > Perhaps A: > Further, operators MUST ensure that the TLS TACACS+ servers > covered > by a wildcard certificate are impervious to redirection of > traffic to a different server (for example, due to on-path > attacks or > DNS cache poisoning). > > > Perhaps B: > Further, operators MUST ensure that the TLS TACACS+ servers are > covered > by a wildcard certificate and MUST be impervious to redirection > of > traffic to a different server (for example, due to on-path > attacks or > DNS cache poisoning). > --> > > > 9) <!-- [rfced] Does the operator need to consider the impact of > supporting both TLS and non-TLS connections? > > Original: > * The operator must consider the impact of mixed TLS and Non- > TLS on > security, as mentioned above. > > Perhaps: > * The operator must consider the security impact of supporting > both TLS > and non-TLS connections, as mentioned above. > --> > > > 10) <!-- [rfced] The description of the service name in the first > paragraph differs from the what appears in the registration > template below it and what appears on the IANA site. Is the > intent to relay that the service name "tacacss" is commonly > referred to as "TACACS+ over TLS" rather than the description in > the template? Or, should the descriptions be the same? > > Original: > IANA has allocated a new well-known system TCP/IP port number > (300) > for the service name "tacacss", described as "TACACS+ over > TLS". The > service name "tacacss" follows the common practice of appending > an > "s" to the name given to the Non-TLS well- known port name. > This > allocation is justified in Section 5.3. > > IANA has added tacacss as a new entry to the "Service name and > Transport Protocol Port Number Registry" available at > > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%252%0b>> Fwww.iana.org%2Fassignments%2Fservice-names-port- > numbers&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C76a8d4b1d4 > 7d404baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0% > 7C638969509050890228%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd > WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ% > 3D%3D%7C0%7C%7C%7C&sdata=dJUQueBempdj8PRVRFdY6YWhrK3esoT6jkml%2BlB > cfBY%3D&reserved=0>. > > Description in the template and the IANA registry: > TLS Secure Login Host Protocol (TACACSS) See > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%252%0b>> Fwww.iana.org%2Fassignments%2Fservice-names-port- > numbers%2Fservice-names-port- > numbers.xhtml%3F%3D%26skey%3D2%26page%3D6&data=05%7C02%7Cmohamed.b > oucadair%40orange.com%7C76a8d4b1d47d404baee508de13620f45%7C90c7a20 > af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638969509050910198%7CUnknown%7 > CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa > W4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=7xtGhDN > LLU78rsSpB5%2BeMx6niHtl8b1jRPJxWdhHWOA%3D&reserved=0>. > > If the text should be the same, perhaps the paragraphs could be > combined as > follows: > IANA has allocated the following new well-known system in the > "Service Name and Transport Protocol Port Number Registry" (see > > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%252%0b>> Fwww.iana.org%2Fassignments%2Fservice-names-port- > numbers%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C76a8d4b > 1d47d404baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 > C0%7C638969509050924056%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy > fQ%3D%3D%7C0%7C%7C%7C&sdata=YjBGaM783FW%2B1ZlcUkz6rnbXsrUUlIW4JM%2 > BsF5W34g8%3D&reserved=0>). The > service name "tacacss" follows the common practice of appending > an > "s" to the name given to the non-TLS well-known port name. See > the > justification for the allocation in Section 5.3. > > Related: > Original in Section 3.1: > Given the prevalence of default port usage in existing TACACS+ > client > implementations, this specification assigns a well-known TCP > port > number for TACACS+ over TLS: [TBD] (Section 7), with the > associated > service name "tacacss" Section 7. > > Perhaps: > Given the prevalence of default port usage in existing TACACS+ > client > implementations, this specification assigns well-known TCP port > 300 for TACACS+ over TLS (see Section 7). > > Original in Section 3.1 - We believe this is intentional to align > with the line prior: > * for Non-TLS connection TACACS+: Port number 49. > * for TLS connection TACACS+: (TBD). > --> > > > 11) <!-- [rfced] This document used both "non-TLS" and "Non-TLS". > We have > lowercased instances of "Non-TLS" for consistency and because > overcapitalization can detract from readability. > --> > > > Thank you. > Sandy Ginoza > RFC Production Center > > > On Oct 24, 2025, at 5:59 PM, > [email protected]<mailto:[email protected]> wrote: > > *****IMPORTANT***** > > Updated 2025/10/24 > > 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2<https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%252> > Fwww.rfc- > editor.org%2Ffaq%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com% > 7C76a8d4b1d47d404baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5 > d20%7C0%7C0%7C638969509050937361%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e > U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI > sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FNGSi31x%2FFDMEXMZj8Y3K691h > JR5nKeAv8bDU0HXOag%3D&reserved=0). > > 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > trustee.ietf.org%2Flicense- > info&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C76a8d4b1d47d4 > 04baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 > 38969509050952454%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs > IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% > 3D%7C0%7C%7C%7C&sdata=5SFZrZvZu8hXvVgQZbxOxI8LKyYpLhih%2FAJ%2F2MAI > Sp4%3D&reserved=0). > > * 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%252%0b>> Fauthors.ietf.org%2Frfcxml- > vocabulary&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C76a8d4b > 1d47d404baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 > C0%7C638969509050966337%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy > fQ%3D%3D%7C0%7C%7C%7C&sdata=Q4WPKUBwNxz6mbQOmucoXBoDL23ke1Pte28zpc > AoUmY%3D&reserved=0>. > > * 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 > > * [email protected]<mailto:[email protected]> (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). > > * [email protected]<mailto:[email protected]>, > which is a new archival > mailing list > to preserve AUTH48 conversations; it is not an active > discussion > list: > > * More info: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > mailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh- > 4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 > C76a8d4b1d47d404baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C638969509050979704%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=EPXHFWPhZ0yM2p1IMQVGE8LHewSEtC > NxyE9VxyLtUF8%3D&reserved=0 > > * The archive itself: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > mailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C > 02%7Cmohamed.boucadair%40orange.com%7C76a8d4b1d47d404baee508de1362 > 0f45%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6389695090509928 > 38%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA > wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C > &sdata=WP8OUAxJFV0WjgjHHu0dF8bZM6V611PLsWpXbInbHJI%3D&reserved=0 > > * 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, > [email protected]<mailto:[email protected]> > 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-<http://www.rfc-> > editor.org%2Fauthors%2Frfc9887.xml&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C76a8d4b1d47d404baee508de13620f45%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C638969509051006057%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MX3OM3RtnvePlK > 4oaTh3a4Nv8IpbaBC2J5snbmuRqaA%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-<http://www.rfc-> > editor.org%2Fauthors%2Frfc9887.html&data=05%7C02%7Cmohamed.boucada > ir%40orange.com%7C76a8d4b1d47d404baee508de13620f45%7C90c7a20af34b4 > 0bfbc48b9253b6f5d20%7C0%7C0%7C638969509051019460%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=FgQFh7YmYGdyr > 6f%2FSNq2F4OMdlT9O585PF03ILafr9w%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-<http://www.rfc-> > editor.org%2Fauthors%2Frfc9887.pdf&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C76a8d4b1d47d404baee508de13620f45%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C638969509051032625%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=JaLP0TWiFnzyH7 > BQkvyItPpUYjQ9yyvA9G%2BhvVTC51U%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-<http://www.rfc-> > editor.org%2Fauthors%2Frfc9887.txt&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C76a8d4b1d47d404baee508de13620f45%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C638969509051045650%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ZsJsSVFI%2BQwm > u0rTDhCoWdpwp6BpQ%2Bt23FfrKiyjYP8%3D&reserved=0 > > Diff file of the text: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9887-<http://www.rfc-editor.org%2Fauthors%2Frfc9887-> > diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C76a8d4b1 > d47d404baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C638969509051058817%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=vmFpI8EZ8N3DtWe0oF%2BuB1EqYCgGrqRK%2BJ1 > %2BkfDbYZk%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9887-<http://www.rfc-editor.org%2Fauthors%2Frfc9887-> > rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C76a8d > 4b1d47d404baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 > %7C0%7C638969509051071906%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj > oyfQ%3D%3D%7C0%7C%7C%7C&sdata=hWgeYBo7xugJ%2Feah3mxGJc5v6EDOfQ1ErI > pDIY82bM8%3D&reserved=0 (side by side) > > Diff of the XML: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9887-<http://www.rfc-editor.org%2Fauthors%2Frfc9887-> > xmldiff1.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C76a8 > d4b1d47d404baee508de13620f45%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C638969509051085035%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > joyfQ%3D%3D%7C0%7C%7C%7C&sdata=b%2BFE08UHOcdxC%2Bon9IPaJBsHviU0mFt > aSsG2i2WAjnk%3D&reserved=0 > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-<http://www.rfc-> > editor.org%2Fauth48%2Frfc9887&data=05%7C02%7Cmohamed.boucadair%40o > range.com%7C76a8d4b1d47d404baee508de13620f45%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C638969509051099651%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=CD3Ey%2FG12UH%2Fm0f > M0Y4kYH%2Fva8hJn5Oj5GRsZeZKkoc%3D&reserved=0 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9887 (draft-ietf-opsawg-tacacs-tls13-24) > > Title : Terminal Access Controller Access-Control > System Plus over TLS 1.3 (TACACS+ over TLS) > Author(s) : T. Dahm, J. Heasley, D. C. Medway Gash, A. Ota > WG Chair(s) : Joe Clarke, Benoît Claise > > Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani > ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
