Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel
draft-ietf-dots-data-channel-07
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8783.
|
|
|---|---|---|---|
| Authors | Tirumaleswar Reddy.K , Mohamed Boucadair , Kaname Nishizuka , Liang Xia , Prashanth Patil , Andrew Mortensen , Nik Teague | ||
| Last updated | 2017-11-12 | ||
| Replaces | draft-reddy-dots-data-channel | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
TSVART Last Call review
(of
-27)
by Brian Trammell
Ready w/issues
GENART Last Call review
(of
-27)
by Roni Even
Ready w/nits
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Became RFC 8783 (Proposed Standard) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-ietf-dots-data-channel-07
module: ietf-dots-access-control-list
augment /ietf-acl:access-lists:
+--rw client-identifier* binary
augment /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/ietf-acl:actions/ietf-acl:packet-handling:
+--:(rate-limit)
+--rw rate-limit? decimal64
augment /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace:
+--rw fragments? empty
3.1.4. Filter Model YANG Module
<CODE BEGINS> file "ietf-dots-access-control-list@2017-10-12.yang"
module ietf-dots-access-control-list {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-dots-access-control-list";
prefix "dots-acl";
import ietf-access-control-list {
prefix "ietf-acl";
}
organization "IETF DOTS Working Group";
contact
"Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@McAfee.com>
Mohamed Boucadair <mohamed.boucadair@orange.com>
Kaname Nishizuka <kaname@nttv6.jp>
Liang Xia <frank.xialiang@huawei.com>
Prashanth Patil <praspati@cisco.com>
Andrew Mortensen <amortensen@arbor.net>
Nik Teague <nteague@verisign.com>";
description
"This module contains YANG definition for configuring
filtering rules using DOTS data channel.
Copyright (c) 2017 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 Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
Reddy, et al. Expires May 16, 2018 [Page 11]
Internet-Draft DOTS Data Channel November 2017
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision 2017-10-12 {
description "Fix nits and align the module with the signal
channel.";
reference
"-05";
}
revision 2017-06-12 {
reference
"https://tools.ietf.org/html/draft-ietf-dots-data-channel";
}
augment "/ietf-acl:access-lists" {
description "client-identifier parameter.";
leaf-list client-identifier {
type binary;
description "A client identifier conveyed by a DOTS gateway
to a remote DOTS server.";
}
}
augment "/ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/"
+ "ietf-acl:ace/ietf-acl:actions" {
description "rate-limit action";
leaf rate-limit {
type decimal64 {
fraction-digits 2;
}
description "rate-limit action.";
}
}
augment "/ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace" {
description "Handle non-initial and initial fragments.";
leaf fragments {
type empty;
description "Handle fragments.";
}
}
}
Reddy, et al. Expires May 16, 2018 [Page 12]
Internet-Draft DOTS Data Channel November 2017
<CODE ENDS>
3.2. Identifiers
3.2.1. Create Identifiers
A POST request is used to create identifiers, such as names or
aliases, for resources for which a mitigation may be requested. Such
identifiers may then be used in subsequent DOTS signal channel
exchanges to refer more efficiently to the resources under attack
(Figure 3).
Reddy, et al. Expires May 16, 2018 [Page 13]
Internet-Draft DOTS Data Channel November 2017
POST /restconf/data/ietf-dots-data-channel-identifier HTTP/1.1
Host: {host}:{port}
Content-Format: "application/yang.api+json"
{
"ietf-dots-data-channel-identifier:identifier": {
"client-identifier": [
"string"
],
"alias": [
{
"alias-name": "string",
"target-ip": [
"string"
],
"target-prefix": [
"string"
],
"target-port-range": [
{
"lower-port": integer,
"upper-port": integer
}
],
"target-protocol": [
integer
],
"fqdn": [
"string"
],
"uri": [
"string"
]
}
]
}
}
Figure 3: POST to create identifiers
The header parameters are described below:
client-identifer: This attribute has the same meaning, syntax and
processing rules as the 'client-identifier' attribute defined in
[I-D.ietf-dots-signal-channel]. This is an optional attribute.
alias-name: Name of the alias. This is a mandatory attribute.
Reddy, et al. Expires May 16, 2018 [Page 14]
Internet-Draft DOTS Data Channel November 2017
target-ip: IP addresses are separated by commas. This is an
optional attribute.
target-prefix: Prefixes are separated by commas. This is an
optional attribute.
target-port-range: The port range, lower-port for lower port number
and upper-port for upper port number. For TCP, UDP, SCTP, or
DCCP: the range of ports (e.g., 80 to 8080). This is an optional
attribute.
target-protocol: Values are taken from the IANA protocol registry
[proto_numbers]. The value 0 has a special meaning for 'all
protocols'. This is an optional attribute.
fqdn: Fully Qualified Domain Name, is the full name of a system,
rather than just its hostname. For example, "venera" is a
hostname, and "venera.isi.edu" is an FQDN. This is an optional
attribute.
uri: Uniform Resource Identifier (URI). This is an optional
attribute.
In the POST request at least one of the attributes 'target-ip' or
'target-prefix' or 'fqdn' or 'uri' MUST be present. DOTS agents can
safely ignore Vendor-Specific parameters they don't understand.
Figure 4 shows a POST request to create alias called "https1" for
HTTP(S) servers with IP addresses 2001:db8:6401::1 and
2001:db8:6401::2 listening on port 443.
Reddy, et al. Expires May 16, 2018 [Page 15]
Internet-Draft DOTS Data Channel November 2017
POST /restconf/data/ietf-dots-data-channel-identifier HTTP/1.1
Host: www.example.com
Content-Format: "application/yang.api+json"
{
"ietf-dots-data-channel-identifier:identifier": {
"client-identifier": [
"dz6pHjaADkaFTbjr0JGBpw",
"iAYmCNPmrYoKoqzgFMiobw"
],
"alias": [
{
"alias-name": "Server1",
"target-protocol": [
6
],
"target-ip": [
"2001:db8:6401::1",
"2001:db8:6401::2"
],
"target-port-range": [
{
"lower-port": 443
}
]
}
]
}
}
Figure 4: POST to create identifiers
The DOTS server indicates the result of processing the POST request
using HTTP response codes. HTTP 2xx codes are success, HTTP 4xx
codes are some sort of invalid requests and 5xx codes are returned if
the DOTS server has erred or it is incapable of accepting the alias.
Response code 201 (Created) will be returned in the response if the
DOTS server has accepted the alias. If the request is missing one or
more mandatory attributes then 400 (Bad Request) will be returned in
the response or if the request contains invalid or unknown parameters
then 400 (Invalid query) will be returned in the response. The HTTP
response will include the JSON body received in the request.
The DOTS client can use the PUT request (Section 4.5 in [RFC8040]) to
create or modify the aliases in the DOTS server.
Reddy, et al. Expires May 16, 2018 [Page 16]
Internet-Draft DOTS Data Channel November 2017
3.2.2. Delete Identifiers
A DELETE request is used to delete identifiers maintained by a DOTS
server (Figure 5).
DELETE /restconf/data/ietf-dots-data-channel-identifier:identifier\
/client-identifier=dz6pHjaADkaFTbjr0JGBpw,iAYmCNPmrYoKoqzgFMiobw\
/alias-name=Server1 HTTP/1.1
Host: {host}:{port}
Figure 5: DELETE identifier
In RESTCONF, URI-encoded path expressions are used. A RESTCONF data
resource identifier is encoded from left to right, starting with the
top-level data node, according to the 'api-path' rule defined in
Section 3.5.3.1 of [RFC8040]. The data node in the above path
expression is a YANG list node and MUST be encoded according to the
rules defined in Section 3.5.1 of [RFC8040].
If the DOTS server does not find the alias name conveyed in the
DELETE request in its configuration data, then it responds with a 404
(Not Found) error response code. The DOTS server successfully
acknowledges a DOTS client's request to remove the identifier using
204 (No Content) in the response.
3.2.3. Retrieving Installed Identifiers
A GET request is used to retrieve the set of installed identifiers
from a DOTS server (Section 3.3.1 in [RFC8040]). Figure 6 shows how
to retrieve all the identifiers that were instantiated by the DOTS
client. The content parameter and its permitted values are defined
in Section 4.8.1 of [RFC8040].
GET /restconf/data/ietf-dots-data-channel-identifier:identifier\
/client-identifier=dz6pHjaADkaFTbjr0JGBpw,iAYmCNPmrYoKoqzgFMiobw?\
content=config HTTP/1.1
Host: {host}:{port}
Accept: application/yang-data+json
Figure 6: GET to retrieve all the installed identifiers
Figure 7 shows response for all identifiers on the DOTS server.
Reddy, et al. Expires May 16, 2018 [Page 17]
Internet-Draft DOTS Data Channel November 2017
{
"ietf-dots-data-channel-identifier:identifier": {
"client-identifier": [
"dz6pHjaADkaFTbjr0JGBpw",
"iAYmCNPmrYoKoqzgFMiobw"
],
"alias": [
{
"alias-name": "Server1",
"traffic-protocol": [
6
],
"ip": [
"2001:db8:6401::1",
"2001:db8:6401::2"
],
"port-range": [
{
"lower-port": 443
}
]
},
{
"alias-name": "Server2",
"traffic-protocol": [
6
],
"ip": [
"2001:db8:6401::10",
"2001:db8:6401::20"
],
"port-range": [
{
"lower-port": 80
}
]
}
]
}
}
Figure 7: Response body
If the DOTS server does not find the alias name conveyed in the GET
request in its configuration data, then it responds with a 404 (Not
Found) error response code.
Reddy, et al. Expires May 16, 2018 [Page 18]
Internet-Draft DOTS Data Channel November 2017
3.3. Filtering Rules
The DOTS server either receives the filtering rules directly from the
DOTS client or via a DOTS gateway.
If the DOTS client signals the filtering rules via a DOTS gateway,
then the DOTS gateway validates if the DOTS client is authorized to
signal the filtering rules and if the client is authorized propagates
the rules to the DOTS server. Likewise, the DOTS server validates if
the DOTS gateway is authorized to signal the filtering rules. To
create or purge filters, the DOTS client sends HTTP requests to its
DOTS gateway. The DOTS gateway validates the rules in the requests
and proxies the requests containing the filtering rules to a DOTS
server. When the DOTS gateway receives the associated HTTP response
from the DOTS server, it propagates the response back to the DOTS
client.
The following APIs define means for a DOTS client to configure
filtering rules on a DOTS server.
3.3.1. Install Filtering Rules
A POST request is used to push filtering rules to a DOTS server.
Figure 8 shows a POST request example to block traffic from
192.0.2.0/24, destined to 198.51.100.0/24. The ACL JSON
configuration for the filtering rule is generated using the ACL YANG
data model defined in [I-D.ietf-netmod-acl-model] and the ACL
configuration XML for the filtering rule is specified in Section 4.3
of [I-D.ietf-netmod-acl-model].
Reddy, et al. Expires May 16, 2018 [Page 19]
Internet-Draft DOTS Data Channel November 2017
POST /restconf/data/ietf-dots-access-control-list HTTP/1.1
Host: www.example.com
Content-Format: "application/yang.api+json"
{
"ietf-dots-access-control-list:access-lists": {
"client-identifier": [
"dz6pHjaADkaFTbjr0JGBpw",
"iAYmCNPmrYoKoqzgFMiobw"
],
"acl": [
{
"acl-name": "sample-ipv4-acl",
"acl-type": "ipv4-acl",
"aces": {
"ace": [
{
"rule-name": "rule1",
"matches": {
"ipv4-acl": {
"source-ipv4-network": "192.0.2.0/24",
"destination-ipv4-network": "198.51.100.0/24"
}
},
"actions": {
"deny": [null]
}
}
]
}
}
]
}
}
Figure 8: POST to install filterng rules
The header parameters defined in [I-D.ietf-netmod-acl-model] are
discussed below:
acl-name: The name of access-list. This is a mandatory attribute.
acl-type: Indicates the primary intended type of match criteria
(e.g. IPv4, IPv6). This is a mandatory attribute.
protocol: Internet Protocol numbers. This is an optional
attribute.
Reddy, et al. Expires May 16, 2018 [Page 20]
Internet-Draft DOTS Data Channel November 2017
source-ipv4-network: The source IPv4 prefix. This is an optional
attribute.
destination-ipv4-network: The destination IPv4 prefix. This is an
optional attribute.
actions: "deny" or "permit" or "rate-limit". "permit" action is
used to white-list traffic. "deny" action is used to black-list
traffic. "rate-limit" action is used to rate-limit traffic, the
allowed traffic rate is represented in bytes per second indicated
in IEEE floating point format [IEEE.754.1985]. If actions
attribute is not specified in the request then the default action
is "deny". This is an optional attribute.
The DOTS server indicates the result of processing the POST request
using HTTP response codes. HTTP 2xx codes are success, HTTP 4xx
codes are some sort of invalid requests and 5xx codes are returned if
the DOTS server has erred or it is incapable of configuring the
filtering rules. Response code 201 (Created) will be returned in the
response if the DOTS server has accepted the filtering rules. If the
request is missing one or more mandatory attributes then 400 (Bad
Request) will be returned in the response or if the request contains
invalid or unknown parameters then 400 (Invalid query) will be
returned in the response.
The DOTS client can use the PUT request to create or modify the
filtering rules in the DOTS server.
3.3.2. Remove Filtering Rules
A DELETE request is used to delete filtering rules from a DOTS server
(Figure 9).
DELETE /restconf/data/ietf-dots-access-control-list:access-lists\
/client-identifier=dz6pHjaADkaFTbjr0JGBpw,iAYmCNPmrYoKoqzgFMiobw\
/acl-name=sample-ipv4-acl&acl-type=ipv4-acl HTTP/1.1
Host: {host}:{port}
Figure 9: DELETE to remove the filtering rules
If the DOTS server does not find the access list name and access list
type conveyed in the DELETE request in its configuration data, then
it responds with a 404 (Not Found) error response code. The DOTS
server successfully acknowledges a DOTS client's request to withdraw
the filtering rules using 204 (No Content) response code, and removes
the filtering rules as soon as possible.
Reddy, et al. Expires May 16, 2018 [Page 21]
Internet-Draft DOTS Data Channel November 2017
3.3.3. Retrieving Installed Filtering Rules
The DOTS client periodically queries the DOTS server to check the
counters for installed filtering rules. A GET request is used to
retrieve filtering rules from a DOTS server. Figure 10 shows how to
retrieve all the filtering rules programmed by the DOTS client and
the number of matches for the installed filtering rules.
GET /restconf/data/ietf-dots-access-control-list:access-lists\
/client-identifier=dz6pHjaADkaFTbjr0JGBpw,iAYmCNPmrYoKoqzgFMiobw?\
content=all HTTP/1.1
Host: {host}:{port}
Accept: application/yang-data+json
Figure 10: GET to retrieve the configuration data and state data for
the filtering rules
If the DOTS server does not find the access list name and access list
type conveyed in the GET request in its configuration data, then it
responds with a 404 (Not Found) error response code.
4. IANA Considerations
This specification registers new parameters for the DOTS data channel
and establishes registries for mappings to JSON attributes.
4.1. DOTS Data Channel JSON Attribute Mappings Registry
A new registry will be requested from IANA, entitled "DOTS data
channel JSON attribute Mappings Registry". The registry is to be
created as Expert Review Required.
4.2. Registration Template
JSON Attribute:
JSON attribute name.
Description:
Brief description of the attribute.
Change Controller:
For Standards Track RFCs, list the "IESG". For others, give the
name of the responsible party. Other details (e.g., postal
address, email address, home page URI) may also be included.
Specification Document(s):
Reference to the document or documents that specify the parameter,
preferably including URIs that can be used to retrieve copies of
Reddy, et al. Expires May 16, 2018 [Page 22]
Internet-Draft DOTS Data Channel November 2017
the documents. An indication of the relevant sections may also be
included but is not required.
4.3. Initial Registry Contents
o JSON Attribute: "client-identifier"
o Description: Client identifier.
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "alias-name"
o Description: Name of alias.
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "traffic-protocol"
o Description: Internet protocol numbers.
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "port-range"
o Description: The port range, lower-port for lower port number and
upper-port for upper port number. For TCP, UDP, SCTP, or DCCP:
the range of ports (e.g., 80 to 8080).
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "lower-port"
o Description: Lower port number for port range.
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "upper-port"
o Description: Upper port number for port range.
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "ip"
o Description: IP address.
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "prefix"
o Description: IP prefix
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "fqdn"
Reddy, et al. Expires May 16, 2018 [Page 23]
Internet-Draft DOTS Data Channel November 2017
o Description: Fully Qualified Domain Name, is the full name of a
system, rather than just its hostname. For example, "venera" is a
hostname, and "venera.isi.edu" is an FQDN.
o Change Controller: IESG
o Specification Document(s): this document
o JSON Attribute: "uri"
o Description: Uniform Resource Identifier (URI).
o Change Controller: IESG
o Specification Document(s): this document
5. Contributors
The following individuals have contributed to this document:
Dan Wing
Email: dwing-ietf@fuggles.com
6. Security Considerations
Authenticated encryption MUST be used for data confidentiality and
message integrity. TLS based on client certificate MUST be used for
mutual authentication. The interaction between the DOTS agents
requires Transport Layer Security (TLS) with a cipher suite offering
confidentiality protection and the guidance given in [RFC7525] MUST
be followed to avoid attacks on TLS.
An attacker may be able to inject RST packets, bogus application
segments, etc., regardless of whether TLS authentication is used.
Because the application data is TLS protected, this will not result
in the application receiving bogus data, but it will constitute a DoS
on the connection. This attack can be countered by using TCP-AO
[RFC5925]. If TCP-AO is used, then any bogus packets injected by an
attacker will be rejected by the TCP-AO integrity check and therefore
will never reach the TLS layer.
In order to prevent leaking internal information outside a client-
domain, DOTS gateways located in the client-domain SHOULD NOT reveal
the identity of internal DOTS clients (client-identifier) unless
explicitly configured to do so.
Special care should be taken in order to ensure that the activation
of the proposed mechanism won't have an impact on the stability of
the network (including connectivity and services delivered over that
network).
Reddy, et al. Expires May 16, 2018 [Page 24]
Internet-Draft DOTS Data Channel November 2017
Involved functional elements in the cooperation system must establish
exchange instructions and notification over a secure and
authenticated channel. Adequate filters can be enforced to avoid
that nodes outside a trusted domain can inject request such as
deleting filtering rules. Nevertheless, attacks can be initiated
from within the trusted domain if an entity has been corrupted.
Adequate means to monitor trusted nodes should also be enabled.
7. Acknowledgements
Thanks to Christian Jacquenet, Roland Dobbins, Roman Danyliw, Ehud
Doron, Russ White, Jon Shallow, and Gilbert Clark for the discussion
and comments.
8. References
8.1. Normative References
[I-D.ietf-dots-architecture]
Mortensen, A., Andreasen, F., Reddy, T.,
christopher_gray3@cable.comcast.com, c., Compton, R., and
N. Teague, "Distributed-Denial-of-Service Open Threat
Signaling (DOTS) Architecture", draft-ietf-dots-
architecture-05 (work in progress), October 2017.
[I-D.ietf-dots-signal-channel]
Reddy, T., Boucadair, M., Patil, P., Mortensen, A., and N.
Teague, "Distributed Denial-of-Service Open Threat
Signaling (DOTS) Signal Channel", draft-ietf-dots-signal-
channel-06 (work in progress), October 2017.
[I-D.ietf-netmod-acl-model]
Jethanandani, M., Huang, L., Agarwal, S., and D. Blair,
"Network Access Control List (ACL) YANG Data Model",
draft-ietf-netmod-acl-model-14 (work in progress), October
2017.
[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>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>.
Reddy, et al. Expires May 16, 2018 [Page 25]
Internet-Draft DOTS Data Channel November 2017
[RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP
Authentication Option", RFC 5925, DOI 10.17487/RFC5925,
June 2010, <https://www.rfc-editor.org/info/rfc5925>.
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing",
RFC 7230, DOI 10.17487/RFC7230, June 2014,
<https://www.rfc-editor.org/info/rfc7230>.
[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <https://www.rfc-editor.org/info/rfc7525>.
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>.
[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>.
8.2. Informative References
[I-D.ietf-dots-requirements]
Mortensen, A., Moskowitz, R., and T. Reddy, "Distributed
Denial of Service (DDoS) Open Threat Signaling
Requirements", draft-ietf-dots-requirements-07 (work in
progress), October 2017.
[I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-02 (work in progress),
October 2017.
[IEEE.754.1985]
Institute of Electrical and Electronics Engineers,
"Standard for Binary Floating-Point Arithmetic", August
1985.
[proto_numbers]
"IANA, "Protocol Numbers"", 2011,
<http://www.iana.org/assignments/protocol-numbers>.
Reddy, et al. Expires May 16, 2018 [Page 26]
Internet-Draft DOTS Data Channel November 2017
[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>.
[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>.
[RFC6520] Seggelmann, R., Tuexen, M., and M. Williams, "Transport
Layer Security (TLS) and Datagram Transport Layer Security
(DTLS) Heartbeat Extension", RFC 6520,
DOI 10.17487/RFC6520, February 2012,
<https://www.rfc-editor.org/info/rfc6520>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March
2014, <https://www.rfc-editor.org/info/rfc7159>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>.
Authors' Addresses
Tirumaleswar Reddy
McAfee, Inc.
Embassy Golf Link Business Park
Bangalore, Karnataka 560071
India
Email: kondtir@gmail.com
Mohamed Boucadair
Orange
Rennes 35000
France
Email: mohamed.boucadair@orange.com
Reddy, et al. Expires May 16, 2018 [Page 27]
Internet-Draft DOTS Data Channel November 2017
Kaname Nishizuka
NTT Communications
GranPark 16F 3-4-1 Shibaura, Minato-ku
Tokyo 108-8118
Japan
Email: kaname@nttv6.jp
Liang Xia
Huawei
101 Software Avenue, Yuhuatai District
Nanjing, Jiangsu 210012
China
Email: frank.xialiang@huawei.com
Prashanth Patil
Cisco Systems, Inc.
Email: praspati@cisco.com
Andrew Mortensen
Arbor Networks, Inc.
2727 S. State St
Ann Arbor, MI 48104
United States
Email: amortensen@arbor.net
Nik Teague
Verisign, Inc.
United States
Email: nteague@verisign.com
Reddy, et al. Expires May 16, 2018 [Page 28]