Operational Security Capabilities for IP Network InfrastructureT. Fiebig
Internet-Draft                                                          
Intended status: Standards Track                             C. Martinez
Expires: 3 February 2024                                          LACNIC
                                                               Q. Misell
                                                                AS207960
                                                           2 August 2023


                      BGP Operations and Security
                  draft-misell-opsec-rfc7454bis-latest

Abstract


Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 3 February 2024.

Copyright Notice

   Copyright (c) 2023 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction
     1.1.  Requirements Language
   2.  References
     2.1.  Normative References
     2.2.  Informative References
   Authors' Addresses

1.  Introduction


1.1.  Requirements Language

   The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
   SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL in this
   document are to be interpreted as described in [BCP14] when, and only
   when, they appear in all capitals, as shown here.

2.  References

2.1.  Normative References

   [BCP14]    Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

              Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, May 2017.

              <https://www.rfc-editor.org/info/bcp14>

2.2.  Informative References

Authors' Addresses

   Tobias Fiebig
   Email: tobias@fiebig.nl
   URI:   https://fiebig.nl


   Carlos M. Martinez
   Latin American and Caribbean Internet Address Registry
   Rambla Mexico 6125
   11400 Montevideo
   Uruguay
   Phone: +598 2604 2222
   Email: carlos@lacnic.net


   Q Misell
   AS207960 Cyfyngedig
   13 Pen-y-lan Terrace
   Caerdydd
   CF23 9EU
   United Kingdom
   Email: q@as207970.net, q@magicalcodewit.ch
   URI:   https://magicalcodewit.ch