Internet DRAFT - draft-blanchet-tvr-contactplan

draft-blanchet-tvr-contactplan







Internet Engineering Task Force                              M. Blanchet
Internet-Draft                                                  Viagenie
Intended status: Standards Track                         L. J. Torgerson
Expires: 8 January 2024                        Jet Propulsion Laboratory
                                                                   Y. Qu
                                                               Futurewei
                                                             7 July 2023


Contact Plan Yang Model for Time-Variant Routing of the Bundle Protocol
                   draft-blanchet-tvr-contactplan-01

Abstract

   Some networks, such as in space, have links that are up and down
   based on a known schedule.  The links characteristics, such as
   latency and bandwidth, are often also known in advance and are
   important information for routing decisions.  This document describes
   a Yang data model, also known as contact plan.  This specification
   applies to the Bundle Protocol.

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 8 January 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



Blanchet, et al.         Expires 8 January 2024                 [Page 1]

Internet-Draft              TVR Contact Plan                   July 2023


   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Data Model  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Some networks, such as in space, have links that are up and down
   based on a known schedule.  The links characteristics, such as
   latency and bandwidth, are also known in advance and are important
   information for routing decisions.  This document describes a Yang
   data model, also known as contact plan.  This specification applies
   to the Bundle Protocol.

   For delay-tolerant networks using the Bundle Protocol(BP) [RFC9171],
   implementations have defined different formats and data models
   ([iondtncp], [ionipncp], [ud3tncgf], [hdtncp]) for such data.  This
   specification aims to specify a common interoperable data model.

   While this work is related to space communications, it could be
   applied to any use case that is using a contact plan.

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 BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Data Model

   The Yang data model augments the Bundle Protocol Yang data
   model[draft-blanchet-dtn-bp-yang-model] by adding the TVR schedule
   Yang data model [draft-qu-tvr-schedule-yang] to the neighbors of a
   Bundle protocol node.



Blanchet, et al.         Expires 8 January 2024                 [Page 2]

Internet-Draft              TVR Contact Plan                   July 2023


   In the case of DTN networks using Bundle Protocol, additional
   attributes are used on the contact, such as the bandwidth of the
   convergence layer adapter link at the time of the contact.  It is
   added to the augmentation.

  <CODE BEGINS> file "ietf-tvr-bundle-schedule@2023-07-05.yang"
  module ietf-tvr-bundle-schedule {
    yang-version 1.1;
    namespace "urn:ietf:params:xml:ns:yang:ietf-tvr-bundle-schedule";
    prefix bundle-schedule;

    import ietf-bundle-protocol {
      prefix bundle;
    }
    import ietf-tvr-schedule {
      prefix tvr-schedule;
    }

    organization
      "IETF TVR - Time Variant Routing Working Group";
    contact
      "WG Web:   <http://datatracker.ietf.org/wg/tvr>
       WG List:  <mailto:tvr@ietf.org>

       Author:   Marc Blanchet
                 <mailto:marc.blanchet@viagenie.ca>
       Author:   Yingzhen Qu
                 <mailto:yingzhen.ietf@gmail.com>
       Author:   Leigh Jordan Torgerson
                 <mailto:jordan.l.torgerson@jpl.nasa.gov>";

    description
      "The YANG module defines an augmentation to the Bundle
       protocol YANG mode.

       This YANG model conforms to the Network Management
       Datastore Architecture (NMDA) as described in RFC 8342.

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

       Redistribution and use in source and binary forms, with or
       without modification, is permitted pursuant to, and subject to
       the license terms contained in, the Revised BSD License set
       forth in Section 4.c of the IETF Trust's Legal Provisions
       Relating to IETF Documents
       (https://trustee.ietf.org/license-info).




Blanchet, et al.         Expires 8 January 2024                 [Page 3]

Internet-Draft              TVR Contact Plan                   July 2023


       This version of this YANG module is part of RFC XXXX
       (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
       for full legal notices.

       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 BCP 14 (RFC 2119) (RFC 8174) when, and only when,
       they appear in all capitals, as shown here.";
    reference
      "RFC XXXX: Contact Plan Yang Model for Time-Variant Routing of the Bundle Protocol";

    revision 2023-07-05 {
      description
        "Initial Version";
      reference
        "RFC XXXX: Contact Plan Yang Model for Time-Variant Routing of the Bundle Protocol.";
    }

    augment "/bundle:node/bundle:neighbors/bundle:neighbor" {
      container contact-schedule {
        description
          "Augment Bundle node neighbor with a contact schedule.";
        uses tvr-schedule:schedule;
        leaf bandwidth {
          type yang:gauge64;
          units "bits/second";
          description
            "An estimate of the convergence layer current bandwidth in bits
             per second";
        }
      }
      description
        "Augment the neighbor with a contact schedule.";
    }
  }
  <CODE ENDS>

3.  Security Considerations

   The YANG modules specified in this document define a schema for data
   that is designed to be accessed via network management protocols such
   as NETCONF [RFC6241] or RESTCONF [RFC8040].  The lowest NETCONF layer
   is the secure transport layer, and the mandatory-to-implement secure
   transport is Secure Shell (SSH) [RFC6242].  The lowest RESTCONF layer
   is HTTPS, and the mandatory-to-implement secure transport is TLS
   [RFC8446].




Blanchet, et al.         Expires 8 January 2024                 [Page 4]

Internet-Draft              TVR Contact Plan                   July 2023


   The NETCONF access control model [RFC8341] provides the means to
   restrict access for particular NETCONF or RESTCONF users to a pre-
   configured subset of all available NETCONF or RESTCONF protocol
   operations and content.

   Augmenting neighbors with a contact plan could be used by an
   adversary to influence the routing and the base function of the
   networking config of the node, the end-result may be a denial of
   service.

4.  IANA Considerations

   This document registers an URI in the IETF XML registry [RFC3688].
   Following the format in [RFC3688], the following registration is
   requested to be made:

      URI: urn:ietf:params:xml:ns:yang:ietf-tvr-bundle-schedule
      Registrant Contact: The IESG.
      XML: N/A, the requested URI is an XML namespace.

   This document registers a YANG module in the YANG Module Names
   registry [RFC6020].

      name: ietf-tvr-bundle-schedule
      namespace: urn:ietf:params:xml:ns:yang:ietf-tvr-bundle-schedule
      prefix: bundle-schedule
      reference: RFC XXXX

5.  References

5.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <https://www.rfc-editor.org/info/rfc3688>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,
              <https://www.rfc-editor.org/info/rfc6020>.






Blanchet, et al.         Expires 8 January 2024                 [Page 5]

Internet-Draft              TVR Contact Plan                   July 2023


   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <https://www.rfc-editor.org/info/rfc6241>.

   [RFC6242]  Wasserman, M., "Using the NETCONF Protocol over Secure
              Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
              <https://www.rfc-editor.org/info/rfc6242>.

   [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
              <https://www.rfc-editor.org/info/rfc8040>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8341]  Bierman, A. and M. Bjorklund, "Network Configuration
              Access Control Model", STD 91, RFC 8341,
              DOI 10.17487/RFC8341, March 2018,
              <https://www.rfc-editor.org/info/rfc8341>.

   [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
              <https://www.rfc-editor.org/info/rfc8446>.

   [RFC9171]  Burleigh, S., Fall, K., and E. Birrane, III, "Bundle
              Protocol Version 7", RFC 9171, DOI 10.17487/RFC9171,
              January 2022, <https://www.rfc-editor.org/info/rfc9171>.

   [draft-qu-tvr-schedule-yang]
              Qu, Y., Lindem, A., and M. Blanchet, "YANG Model for
              Scheduled Attributes", Work in Progress, Internet-Draft,
              draft-qu-tvr-schedule-yang-00, July 2023, <draft-qu-tvr-
              schedule-yang>.

   [draft-blanchet-dtn-bp-yang-model]
              Blanchet, M. and Y. Qu, "Bundle Protocol Yang Model", Work
              in Progress, Internet-Draft, draft-blanchet-dtn-bp-yang-
              model-00, July 2023, <draft-blanchet-dtn-bp-yang-model>.

5.2.  Informative References

   [ud3tncgf] "µD3TN Contacts Data Format", <https://gitlab.com/d3tn/
              ud3tn/-/blob/master/doc/contacts_data_format.md>.






Blanchet, et al.         Expires 8 January 2024                 [Page 6]

Internet-Draft              TVR Contact Plan                   July 2023


   [hdtncp]   "High-rate Delay Tolerant Network Contact Plan Example",
              <https://github.com/nasa/HDTN/blob/master/module/
              scheduler/src/contactPlan.json>.

   [iondtncp] "ION "dtn" scheme configuration commands file",
              <https://sourceforge.net/p/ion-
              dtn/code/ci/current/tree/bpv7/doc/pod5/dtn2rc.pod>.

   [ionipncp] "ION "ipn" scheme configuration commands file",
              <https://sourceforge.net/p/ion-
              dtn/code/ci/current/tree/bpv7/doc/pod5/ipnrc.pod>.

Acknowledgements

   This work is vastly inspired by Scott Burleigh's' Contact Graph
   Routing for DTN as implemented in ION as well as the contact plan of
   HDTN and uD3TN implementations.

   The following people have provided comments to improve this document
   (in no particular order): Felix Walter, Scott Burleigh, Dean
   Bogdanovic, Tony Li, Brian Sipos, Jordan Leigh Torgerson, Yingzhen
   Qu.

Authors' Addresses

   Marc Blanchet
   Viagenie
   Canada
   Email: marc.blanchet@viagenie.ca


   Leigh Jordan Torgerson
   Jet Propulsion Laboratory
   United States of America
   Email: jordan.l.torgerson@jpl.nasa.gov


   Yingzhen Qu
   Futurewei
   2330 Central Expressway
   Santa Clara, CA 95050
   United States of America
   Email: yingzhen.qu@futurewei.com








Blanchet, et al.         Expires 8 January 2024                 [Page 7]