draft-ietf-idr-sla-exchange-07.txt   draft-ietf-idr-sla-exchange-08.txt 
IDR S. Shah IDR S. Shah
Internet-Draft K. Patel Internet-Draft K. Patel
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: August 7, 2016 S. Bajaj Expires: August 8, 2016 S. Bajaj
Juniper Network Juniper Network
L. Tomotaki L. Tomotaki
Verizon Verizon
M. Boucadair M. Boucadair
Orange Orange
February 4, 2016 February 5, 2016
Inter-domain SLA Exchange Attribute Inter-domain SLA Exchange Attribute
draft-ietf-idr-sla-exchange-07.txt draft-ietf-idr-sla-exchange-08.txt
Abstract Abstract
Network administrators typically enforce Quality of Service (QoS) Network administrators typically enforce Quality of Service (QoS)
policies according to Service Level Agreement (SLA) with their policies according to Service Level Agreement (SLA) with their
providers. The enforcement of such policies often relies upon providers. The enforcement of such policies often relies upon
vendor-specific configuration language. Both learning of SLA, either vendor-specific configuration language. Both learning of SLA, either
thru SLA documents or via some other out-of-band method, and thru SLA documents or via some other out-of-band method, and
translating them to vendor specific configuration language is a translating them to vendor specific configuration language is a
complex, often manual, process and prone to errors. complex, often manual, process and prone to errors.
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 7, 2016. This Internet-Draft will expire on August 8, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 25, line 46 skipping to change at page 25, line 46
This document defines a new BGP optional transitive path attribute, This document defines a new BGP optional transitive path attribute,
called QoS Attribute. IANA action is required to allocate a new called QoS Attribute. IANA action is required to allocate a new
code-point in the BGP path Attributes registry. code-point in the BGP path Attributes registry.
IANA is requested to create a registry for QoS Attribute subTypes. IANA is requested to create a registry for QoS Attribute subTypes.
This is a registry of 1 octet value, to be assigned on a standards This is a registry of 1 octet value, to be assigned on a standards
action/early allocation basis. The initial assignments are: action/early allocation basis. The initial assignments are:
QoS Attribute subTypes QoS Attribute subTypes
============= ======== ============= ========
Reserved 0x00 Reserved 0x00
SLA 0x01 SLA 0x01
Reserved 0x02-0xff (Standards Action) Reserved 0x02-0xff (Standards Action)
IANA is requested to create a registry for SLA Event Types. This is IANA is requested to create a registry for SLA Event Types. This is
a registry of 4-bits value, to be assigned on a standards action or a registry of 4-bits value, to be assigned on a standards action or
early allocation basis. The initial assignments are: early allocation basis. The initial assignments are:
QoS Attribute SLA Event Types QoS Attribute SLA Event Types
============= =============== ============= ===============
Reserved 0x00 Reserved 0x0
ADVERTISE 0x01 ADVERTISE 0x1
Reserved 0x2 - 0xf (Standards Action)
IANA is requested to create a registry to define QoS SLA Direction. IANA is requested to create a registry to define QoS SLA Direction.
This is the direction in forwarding path, advertised QoS SLA is This is the direction in forwarding path, advertised QoS SLA is
applicable to. The values for QoS SLA direction are: applicable to. This is a 2-bit registry. Values for QoS SLA
direction are:
QoS SLA Direction Value QoS SLA Direction Value
================= ===== ================= =====
Reserved 0x00 Reserved 0x0
To source AS from destination AS 0x01 To source AS from destination AS 0x1
From source AS to destination AS 0x02 From source AS to destination AS 0x2
Reserved (Standards Action) 0x3
QoS SLA Traffic Class Element Types will be referring to existing QoS SLA Traffic Class Element Types will be referring to existing
IPFIX IANA types as listed in Table 1. IPFIX IANA types as listed in Table 1.
IANA is requested to create a registry for QoS SLA Traffic Class IANA is requested to create a registry for QoS SLA Traffic Class
Service Types. This is a registry of 2 octet values, to be assigned Service Types. This is a registry of 2 octet values, to be assigned
on a standards action/early allocation basis. The initial on a standards action/early allocation basis. The initial
assignments are: assignments are:
Traffic Class Service Type Value Traffic Class Service Type Value
skipping to change at page 27, line 4 skipping to change at page 27, line 17
Reserved 0x00 Reserved 0x00
TRAFFIC_CLASS_TSPEC 0x01 TRAFFIC_CLASS_TSPEC 0x01
L2_OVERHEAD 0x02 L2_OVERHEAD 0x02
MINRATE_IN_PROFILE_MARKING 0x03 MINRATE_IN_PROFILE_MARKING 0x03
MINRATE_OUT_PROFILE_MARKING 0x04 MINRATE_OUT_PROFILE_MARKING 0x04
MAXRATE_IN_PROFILE_MARKING 0x05 MAXRATE_IN_PROFILE_MARKING 0x05
MAXRATE_OUT_PROFILE_MARKING 0x06 MAXRATE_OUT_PROFILE_MARKING 0x06
DROP_THRESHOLD 0x07 DROP_THRESHOLD 0x07
RELATIVE_PRIORITY 0x08 RELATIVE_PRIORITY 0x08
SUB_TRAFFIC_CLASSES 0x09 SUB_TRAFFIC_CLASSES 0x09
Standards Action 0x0A - 0x3FFF
FCFS 0x4000 - 0x4FF0
11. Security Considerations 11. Security Considerations
The QOS attribute defined in this document SHOULD be used by the The QOS attribute defined in this document SHOULD be used by the
managed networks for enforcing Quality of Service policies and so managed networks for enforcing Quality of Service policies and so
there should not be any risks for identity thefts. To strengthen the there should not be any risks for identity thefts. To strengthen the
security for the QoS attribute, RPKI based origin validation security for the QoS attribute, RPKI based origin validation
[RFC7115] MAY be used. In addition to the RPKI based origin [RFC7115] MAY be used. In addition to the RPKI based origin
validation, BGP Path Validation (e.g., [I-D.ietf-sidr-bgpsec- validation, BGP Path Validation (e.g., [I-D.ietf-sidr-bgpsec-
protocol]) procedures could be used over BGP QoS attribute and its protocol]) procedures could be used over BGP QoS attribute and its
 End of changes. 10 change blocks. 
12 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/