draft-ietf-teas-actn-requirements-08.txt   draft-ietf-teas-actn-requirements-09.txt 
TEAS Working Group Young Lee (Editor) TEAS Working Group Young Lee (Editor)
Internet Draft Huawei Internet Draft Huawei
Intended status: Informational Intended status: Informational
Daniele Ceccarelli Daniele Ceccarelli
Expires July 25, 2018. Ericsson Expires September 1, 2018. Ericsson
Takuya Miyasaka Takuya Miyasaka
KDDI KDDI
Jong Yoon Shin Jong Yoon Shin
SKT SKT
Kwang-koog Lee Kwang-koog Lee
KT KT
January 25, 2018 March 1, 2018
Requirements for Abstraction and Control of TE Networks Requirements for Abstraction and Control of TE Networks
draft-ietf-teas-actn-requirements-08.txt draft-ietf-teas-actn-requirements-09
Abstract Abstract
This document provides a set of requirements for abstraction and This document provides a set of functional requirements for
control of Traffic Engineering networks to facilitate virtual abstraction and control of Traffic Engineering networks to
network operation via the creation of a single virtualized network facilitate virtual network operation via the creation of a single
or a seamless service. This supports operators in viewing and virtualized network or a seamless service. This supports operators
controlling different domains (at any dimension: applied technology, in viewing and controlling different domains (at any dimension:
administrative zones, or vendor-specific technology islands) as a applied technology, administrative zones, or vendor-specific
single virtualized network. technology islands) as a single virtualized network.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 16 skipping to change at page 2, line 16
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 25, 2018. This Internet-Draft will expire on September 1, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................3
1.1. Requirements Language.....................................4
2. High-level ACTN requirements...................................4 2. High-level ACTN requirements...................................4
2.1. Service-Specific Requirements.............................4 2.1. Service-Specific Requirements.............................5
2.2. Network-Related Requirements..............................7 2.2. Network-Related Requirements..............................7
3. References.....................................................9 3. Security Considerations........................................9
3.1. Normative References......................................9 4. IANA Considerations............................................9
3.2. Informative References....................................9 5. References....................................................10
4. Contributors..................................................10 5.1. Normative References.....................................10
Authors' Addresses...............................................11 5.2. Informative References...................................10
6. Contributors..................................................11
Authors' Addresses...............................................12
1. Introduction 1. Introduction
This document provides a set of requirements for Abstraction and This document provides a set of functional requirements for
Control of Traffic Engineering (TE) Networks (ACTN) identified in Abstraction and Control of Traffic Engineering (TE) Networks (ACTN)
various use-cases specified by the operators. [ACTN-Frame] defines identified in various use-cases specified by the operators. [ACTN-
the base reference architecture and terminology. Frame] defines the base reference architecture and terminology.
ACTN refers to the set of virtual network service operations needed ACTN refers to the set of virtual network service operations needed
to orchestrate, control and manage large-scale multi-domain TE to coordinate, control and manage large-scale multi-domain TE
networks so as to facilitate network programmability, automation, networks so as to facilitate network programmability, automation,
efficient resource sharing, and end-to-end virtual service aware efficient resource sharing, and end-to-end virtual service aware
connectivity. connectivity.
These operations are summarized as follows: These operations are summarized as follows:
- Abstraction and coordination of underlying network resources - Abstraction and coordination of underlying network resources
independent of how these resources are managed or controlled, independent of how these resources are managed or controlled,
so that higher-layer entities can dynamically control virtual so that higher-layer entities can dynamically control virtual
networks based on those resources. Control includes creating, networks based on those resources. Control includes creating,
modifying, monitoring, and deleting virtual networks. modifying, monitoring, and deleting virtual networks.
- Collation of the resources from multiple TE networks (multiple - Collation of the identifiers and other attributes of the
technologies, equipment from multiple vendors, under the resources from multiple TE networks (multiple technologies,
control of multiple administrations) through a process of equipment from multiple vendors, under the control of multiple
hierarchical abstraction to present a customer with a single administrations) through a process of recursive abstraction to
virtual network. This is achieved by presenting the network present a customer with a single virtual network. This is
domain as an abstracted topology to the customer via open and achieved by presenting the network domain as an abstracted
programmable interfaces. Hierarchical abstraction allows for topology to the customer via open and programmable interfaces.
the recursion of controllers in a customer-provider Recursive abstraction allows for the recursion of abstracted
relationship. data in a hierarchy of controllers.. It is expected that the
recursion levels should be at least three levels: customer
level, multi-domain network level, and domain network level.
- Orchestration of end-to-end virtual network services and - Coordination of end-to-end virtual network services and
applications via allocation of network resources to meet applications via allocation of network resources to meet
specific service, application and customer requirements. specific service, application and customer requirements. Refer
to [ACTN-Frame] for the definition of coordination.
- Adaptation of customer requests (to control virtual resources) - Adaptation of customer requests (to control virtual resources)
to the physical network resources performing the necessary to the physical network resources performing the necessary
mapping, translation, isolation and, policy that allows mapping, translation, isolation and, policy that allows
conveying, managing and enforcing customer policies with conveying, managing and enforcing customer policies with
respect to the services and the network of the customer. respect to the services and the network of the customer.
- Provision via a data model of a computation scheme and virtual - Provision via a data model and virtual control capability to
control capability to customers who request virtual network customers who request virtual network services. Note that these
services. Note that these customers could, themselves, be customers could, themselves, be service providers.
service providers.
ACTN solutions will build on, and extend, existing TE constructs and ACTN solutions will build on, and extend, existing TE constructs and
TE mechanisms wherever possible and appropriate. Support for TE mechanisms wherever possible and appropriate. Support for
controller-based approaches is specifically included in the possible controller-based approaches is specifically included in the possible
solution set. solution set.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 5, line 13 skipping to change at page 5, line 17
1. Requirement 1: Virtual Network Service (VNS) creation 1. Requirement 1: Virtual Network Service (VNS) creation
Customer MUST be able to request/instantiate the VNS to the network Customer MUST be able to request/instantiate the VNS to the network
within the confines of mutual agreement between customer and network within the confines of mutual agreement between customer and network
operator and network operator's capability. A VNS is the service operator and network operator's capability. A VNS is the service
agreement between a customer and provider to provide a VN [ACTN- agreement between a customer and provider to provide a VN [ACTN-
Frame]. There are different types of VNS in terms of the VN types Frame]. There are different types of VNS in terms of the VN types
the customer is allowed to operate (e.g., a VN type can be simply a the customer is allowed to operate (e.g., a VN type can be simply a
set of edge-to-edge links, or it can comprise of virtual nodes and set of edge-to-edge links, or it can comprise of virtual nodes and
virtual links, etc.). The customer MUST be able to express VNS virtual links, etc.). The customer MUST be able to express VNS
policy that captures Service Level Agreements (SLA) associated with preference that captures Service Level Agreements (SLA) associated
virtual network service (e.g., Endpoint selection policy, routing with virtual network service (e.g., Endpoint selection preference,
policy, time-related policy, etc.) routing preference, time-related preference, etc.)
Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG]. Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG].
2. Requirement 2: Virtual Network Service Query 2. Requirement 2: Virtual Network Service Query
Customer SHOULD be able to request VNS Query ("Can you give me these Customer SHOULD be able to request VNS Query ("Can you give me these
VN(s)?") that include the following parameters: VN(s)?") that include the following parameters:
- VN type: various VN types defined by the customer (e.g., - VN type: various VN types defined by the customer (e.g.,
path, graph, etc.) path, graph, etc.)
- VN end-points (Customer Edge interface information) - VN end-points (Customer Edge interface information)
- VN Topology Service-specific Objective Functions (e.g., - VN Topology Service-specific Objective Functions (e.g., a
maximum bandwidth, minimum latency, minimum hops, etc. and set of objective functions as defined in [RFC5541] to be
any combination of them). supported on the paths, but not limited to).
- VN constraints requirement (e.g., Maximum Latency threshold, - VN constraints requirement (e.g., Maximum Latency threshold,
Minimum Bandwidth, etc.) Minimum Bandwidth, etc.)
Reference: [KUMAKI], [FANG], [CHENG]. Reference: [KUMAKI], [FANG], [CHENG].
3. Requirement 3: VNS Instantiation ("Please create a VNS for me") 3. Requirement 3: VNS Instantiation ("Please create a VNS for me")
Customer MUST be able to instantiate VNS that includes various VNS Customer MUST be able to instantiate VNS that includes various VNS
related parameters: related parameters:
- VN type: various VN types defined by the customer (e.g., - VN type: various VN types defined by the customer (e.g.,
Type 1, Type 2, etc. See [ACTN-Frame] for the definition of Type 1, Type 2, etc. See [ACTN-Frame] for the definition of
VN Type 1 and Type 2). VN Type 1 and Type 2).
- VN end-points (Customer Edge interface information) - VN end-points (Customer Edge interface information)
- VN Topology Service-specific Objective Functions (e.g., - VN Topology Service-specific Objective Functions (e.g., a
maximum bandwidth, minimum latency, minimum hops, etc. and set of objective functions as defined in [RFC5541] to be
any combination of them). supported on the paths, but not limited to).
- VN constraints requirement (e.g., Maximum Latency threshold, - VN constraints requirement (e.g., Maximum Latency threshold,
Minimum Bandwidth, etc.) Minimum Bandwidth, etc.)
- VN Topology diversity when there are multiple instances of - VN Topology diversity when there are multiple instances of
VNS (e.g., VN1 and VN2 must be disjoint; Node/link disjoint VNS (e.g., VN1 and VN2 must be disjoint; Node/link disjoint
from other VNs) from other VNs)
Note that Requirement 3 provides specific details of Requirement 1.
Reference: [KUMAKI], [FANG], [CHENG]. Reference: [KUMAKI], [FANG], [CHENG].
4. Requirement 4: VNS Lifecycle Management & Operation (M&O) 4. Requirement 4: VNS Lifecycle Management & Operation (M&O)
Customer MUST be able to perform the following VNS operations: Customer MUST be able to perform the following VNS operations:
- VNS Delete: Customer MUST be able to delete VNS. - VNS Delete: Customer MUST be able to delete VNS.
- VNS Modify: Customer MUST be able to modify VNS related - VNS Modify: Customer MUST be able to modify VNS related
parameters during the lifecycle of the instantiated VNS. parameters during the lifecycle of the instantiated VNS.
skipping to change at page 6, line 38 skipping to change at page 7, line 8
other coexisting virtual networks. Other customers' VNS operation other coexisting virtual networks. Other customers' VNS operation
MUST NOT impact a particular customer's VNS network operation. MUST NOT impact a particular customer's VNS network operation.
Reference: [KUMAKI], [FANG], [LOPEZ] Reference: [KUMAKI], [FANG], [LOPEZ]
6. Requirement 6: Multi-Destination Coordination 6. Requirement 6: Multi-Destination Coordination
Customer MUST be able to define and convey service/preference Customer MUST be able to define and convey service/preference
requirements for multi-destination applications (e.g., set of requirements for multi-destination applications (e.g., set of
candidate sources/destinations, thresholds for load balancing, candidate sources/destinations, thresholds for load balancing,
disaster recovery policy, etc.) disaster recovery preference, etc.)
Reference: [FANG], [LOPEZ], [SHIN]. Reference: [FANG], [LOPEZ], [SHIN].
7. Requirement 7: VNS Performance Monitoring 7. Requirement 7: VNS Performance Monitoring
The customer MUST be able to define performance monitoring The customer MUST be able to define performance monitoring
parameters and its associated policy such as frequency of report, parameters and its associated preference such as frequency of
abstraction/aggregation level of performance data (e.g., VN level, report, abstraction/aggregation level of performance data (e.g., VN
tunnel level, etc.) with dynamic feedback loop from the network. level, tunnel level, etc.) with dynamic feedback loop from the
network.
Reference: [XU], [XU2], [DHODY], [CHENG] Reference: [XU], [XU2], [DHODY], [CHENG]
8. Requirement 8: VNS Confidentiality and Security Requirements 8. Requirement 8: VNS Confidentiality and Security Requirements
The following confidentiality/security requirements MUST be The following confidentiality/security requirements MUST be
supported in all interfaces: supported in all interfaces:
- Securing the request and control of resources, confidentially - Securing the request and control of resources, confidentially
of the information, and availability of function. of the information, and availability of function.
- Trust domain verification (external entity versus internal - Trust domain verification between a customer entity and a
entity) network entity. It verifies if a trust relationship has been
- Encrypting data that flow between components, especially when established between these entities.
they are implemented at remote nodes, regardless if these are - Encrypting data that flow between components, especially when
external or internal network interfaces. they are implemented at remote nodes, regardless if these are
external or internal network interfaces.
Reference: [KUMAKI], [FANG], [LOPEZ] Reference: [KUMAKI], [FANG], [LOPEZ]
2.2. Network-Related Requirements 2.2. Network-Related Requirements
1. Requirement 1: Virtual Network Service Coordination 1. Requirement 1: Virtual Network Service Coordination
Network MUST be able to support the following VNS operations: Network MUST be able to support the following VNS operations:
- VNS Create: Upon customer's VNS creation request, network
MUST be able to create VNS within the confines of network
resource availability.
- VNS Delete: Upon customer's VNS deletion request, network - VNS Delete: Upon customer's VNS deletion request, network
MUST be able to delete VNS. MUST be able to delete VNS.
- VNS Modify: Upon customer's VNS modification request, - VNS Modify: Upon customer's VNS modification request,
network MUST be able to modify VNS related parameters during network MUST be able to modify VNS related parameters during
the lifecycle of the instantiated VNS. the lifecycle of the instantiated VNS.
- VNS Monitor: Upon customer's VNS performance monitoring - VNS Monitor: Upon customer's VNS performance monitoring
setup, the network MUST be able to support VNS level setup, the network MUST be able to support VNS level
Operations, Administration and Management (OAM) Monitoring Operations, Administration and Management (OAM) Monitoring
under policy agreement. under service agreement.
Reference: [FANG], [KUMAKI], [LOPEZ], [DHODY], [FANG], [KLEE]. Reference: [FANG], [KUMAKI], [LOPEZ], [DHODY], [FANG], [KLEE].
2. Requirement 2: Topology Abstraction Capability 2. Requirement 2: Topology Abstraction Capability
The network MUST be capable of managing its networks based on the The network MUST be capable of managing its networks based on the
principle of topology abstraction to be able to scale multi-layer, principle of topology abstraction to be able to scale multi-layer,
multi-domain networks. multi-domain networks.
Reference: [KLEE], [LOPEZ], [DHODY], [CHENG]. Reference: [KLEE], [LOPEZ], [DHODY], [CHENG].
3. Requirement 3: Multi-Domain & Multi-layer Coordination 3. Requirement 3: Multi-Domain & Multi-layer Coordination
Network coordination for multi-domain and multi-layer path Network coordination for multi-domain and multi-layer path
computation and path setup operation MUST be provided: computation and path setup operation MUST be provided:
- End-to-end path computation across multi-domain networks - End-to-end path computation across multi-domain networks
(based on abstract topology from each domain) (based on abstract topology from each domain)
- Domain sequence determination - Domain sequence determination
- Request for path signaling to each domain controller - Request for path signaling to each domain controller
- Alternative path computation if any of the domain - Alternative TE path computation if any of the domain
controllers cannot find its domain path controllers cannot find its domain path
Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI]. Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI].
4. Requirement 4: End-to-End Path Restoration 4. Requirement 4: End-to-End Path Protection
End-to-end Path Restoration Operations MUST be provided with End-to-end Path Protection Operations MUST be provided with seamless
seamless coordination between domain-level recovery schemes and coordination between domain-level protection schemes and cross-
cross-domain recovery schemes. domain protection schemes.
Reference: [CHENG], [KLEE], [DHODY], [LOPEZ], [SHIN]. Reference: [CHENG], [KLEE], [DHODY], [LOPEZ], [SHIN].
5. Requirement 5: Dynamicity of virtual network control operations 5. Requirement 5: Dynamicity of virtual network control operations
Dynamic virtual network control operations MUST be supported. This Dynamic virtual network control operations MUST be supported. This
includes, but is not limited to, the following: includes, but is not limited to, the following:
- Real-time VNS control (e.g., fast recovery/reroute upon - Real-time VNS control (e.g., fast recovery/reroute upon
network failure). network failure).
- Fast convergence of abstracted topologies upon changes due - Fast convergence of abstracted topologies upon changes due
to failure or reconfiguration across the network domain to failure or reconfiguration across the network domain
view, the multi-domain network view and the customer view. view, the multi-domain network view and the customer view.
- Large-scale VNS operation (e.g., the ability to process tens
- Large-scale VNS operation (e.g., the ability to query tens of thousands of connectivity requests) for time-sensitive
of thousands of nodes, and to examine tens of thousands of applications.
connectivity requests) for time-sensitive applications.
Reference: [SHIN], [XU], [XU2], [KLEE], [KUMAKI], [SUZUKI]. Reference: [SHIN], [XU], [XU2], [KLEE], [KUMAKI], [SUZUKI].
3. Security Considerations 3. Security Considerations
The ACTN requirements described in this document do not directly The ACTN requirements described in this document do not directly
bear specific security concerns. When these requirements are bear specific security concerns. When these requirements are
implemented in specific interfaces, securing the request and control implemented in specific interfaces, securing the request and control
of resources, confidentially of the information, and availability of of resources, confidentially of the information, and availability of
function, should all be critical security considerations. function, should all be critical security considerations.
skipping to change at page 9, line 36 skipping to change at page 10, line 18
[ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and [ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and
Control of Transport Networks", draft-ietf-teas-actn- Control of Transport Networks", draft-ietf-teas-actn-
framework, work in progress. framework, work in progress.
5.2. Informative References 5.2. Informative References
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC5541] JL. Le Roux, JP. Vasseur, and Y. Lee, "Encoding of
Objective Functions in the Path Computation Element
Communication Protocol (PCEP)", RFC 5541, June 2009.
[RFC8174] B. Leiba, "Ambiguity of Uppercase vs Lowercase in RFC 2119 [RFC8174] B. Leiba, "Ambiguity of Uppercase vs Lowercase in RFC 2119
Key Words", RFC 8174, May 2017. Key Words", RFC 8174, May 2017.
[CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport [CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport
Networks in Mobile Backhaul Networks", draft-cheng-actn- Networks in Mobile Backhaul Networks", draft-cheng-actn-
ptn-requirements-00, July 21, 2014. ptn-requirements-00, July 21, 2014.
[DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use [DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use
Cases for Abstraction and Control of Transport Networks Cases for Abstraction and Control of Transport Networks
(ACTN)", draft-dhody-actn-poi-use-case-07, October 28, (ACTN)", draft-dhody-actn-poi-use-case-07, October 28,
skipping to change at page 11, line 4 skipping to change at page 11, line 24
[XU2] Y. Xu, et. al., "Requirements of Abstract Alarm Report in ACTN [XU2] Y. Xu, et. al., "Requirements of Abstract Alarm Report in ACTN
architecture", draft-xu-teas-actn-abstract-alarm-report- architecture", draft-xu-teas-actn-abstract-alarm-report-
00, July 6, 2015. 00, July 6, 2015.
[SUZUKI] T. Suzuki, et. al., "Use-case and Requirements for Multi- [SUZUKI] T. Suzuki, et. al., "Use-case and Requirements for Multi-
domain Operation Plane Change", draft-suzuki-teas-actn- domain Operation Plane Change", draft-suzuki-teas-actn-
multidomain-opc-00, July 6, 2015. multidomain-opc-00, July 6, 2015.
6. Contributors 6. Contributors
Dhruv Dhody
Huawei Technologies
Email: dhruv.ietf@gmail.com
Sergio Belotti
Nokia
Via Trento, 30
Vimercate, Italy
Email: sergio.belotti@nokia.com
Khuzema Pithewan
Peloton Technology
Email: khuzemap@gmail.com
Yunbin Xu Yunbin Xu
CATR CATR
Email: xuyunbin@ritt.cn Email: xuyunbin@ritt.cn
Toshiaki Suzuki Toshiaki Suzuki
Hitachi Hitachi
Email: toshiaki.suzuki.cs@hitachi.com Email: toshiaki.suzuki.cs@hitachi.com
Haomian Zheng Haomian Zheng
Huawei Huawei
skipping to change at page 12, line 10 skipping to change at line 480
KDDI KDDI
Email: ta-miyasaka@kddi.com Email: ta-miyasaka@kddi.com
Jong Yoon Shin Jong Yoon Shin
SKT SKT
Email: jongyoon.shin@sk.com Email: jongyoon.shin@sk.com
Kwang-koog Lee Kwang-koog Lee
KT KT
Email: kwangkoog.lee@kt.com Email: kwangkoog.lee@kt.com
Dhruv Dhody
Huawei Technologies
Email: dhruv.ietf@gmail.com
Sergio Belotti
Nokia
Via Trento, 30
Vimercate, Italy
Email: sergio.belotti@nokia.com
Khuzema Pithewan
Peloton Technology
Email: khuzemap@gmail.com
 End of changes. 32 change blocks. 
74 lines changed or deleted 103 lines changed or added

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