draft-ietf-ccamp-l1csm-yang-05.txt   draft-ietf-ccamp-l1csm-yang-06.txt 
CCAMP Working Group G. Fioccola (Ed.) CCAMP Working Group G. Fioccola (Ed.)
Telecom Italia Telecom Italia
Internet Draft K. Lee Internet Draft K. Lee
Intended Status: Standard Track Korea Telecom Intended Status: Standard Track Korea Telecom
Expires: January 3, 2019 Y. Lee (Ed.) Expires: January 17, 2019 Y. Lee (Ed.)
D. Dhody D. Dhody
Huawei Huawei
O. Gonzalez de-Dios O. Gonzalez de-Dios
Telefonica Telefonica
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
July 2, 2018 July 17, 2018
A Yang Data Model for L1 Connectivity Service Model (L1CSM) A Yang Data Model for L1 Connectivity Service Model (L1CSM)
draft-ietf-ccamp-l1csm-yang-05 draft-ietf-ccamp-l1csm-yang-06
Abstract Abstract
This document provides a YANG data model for Layer 1 Connectivity This document provides a YANG data model for Layer 1 Connectivity
Service Model (L1CSM). Service Model (L1CSM). This YANG model is NMDA-compliant.
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 1, line 46 skipping to change at page 1, line 46
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 January 3, 2019. This Internet-Draft will expire on January 17, 2019.
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
skipping to change at page 2, line 27 skipping to change at page 2, line 27
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
1.1. Deployment Scenarios......................................3 1.1. Deployment Scenarios......................................3
1.2. Terminology...............................................6 1.2. Terminology...............................................6
1.3. Tree diagram..............................................6 1.3. Tree diagram..............................................6
1.4. Prefixes in Data Node Names...............................7 1.4. Prefixes in Data Node Names...............................7
2. Definitions....................................................7 2. Definitions....................................................7
3. L1SM YANG Model (Tree Structure)...............................7 3. L1SM YANG Model (Tree Structure)...............................7
4. L1SM YANG Code.................................................8 4. L1SM YANG Code.................................................8
5. Security Considerations.......................................20 5. JSON Example..................................................19
6. IANA Considerations...........................................21 6. Security Considerations.......................................20
7. Acknowledgments...............................................22 7. IANA Considerations...........................................21
8. References....................................................23 8. Acknowledgments...............................................22
8.1. Normative References.....................................23 9. References....................................................23
8.2. Informative References...................................23 9.1. Normative References.....................................23
9. Contributors..................................................24 9.2. Informative References...................................23
10. Contributors.................................................24
Authors' Addresses...............................................24 Authors' Addresses...............................................24
1. Introduction 1. Introduction
This document provides a YANG data model for L1VPN Connectivity This document provides a YANG data model for L1VPN Connectivity
Service Model (L1CSM). The intent of this document is to provide a Service Model (L1CSM). The intent of this document is to provide a
transport service model exploiting Yang data model, which can be transport service model exploiting Yang data model, which can be
utilized by a client network controller to initiate a service utilized by a client network controller to initiate a service
request connectivity request as well as retrieving service states request connectivity request as well as retrieving service states
toward a transport network controller communicating with the client toward a transport network controller communicating with the client
controller via a NETCONF [RFC8341] interface. controller via a NETCONF [RFC8341] or a RESTCONF [RFC8040]
interface.
[RFC4847] provides a framework and service level requirements for [RFC4847] provides a framework and service level requirements for
Layer 1 Virtual Private Networks (L1VPNs). It classifies service Layer 1 Virtual Private Networks (L1VPNs). It classifies service
models as management-based service model, signaling-based service models as management-based service model, signaling-based service
model (Basic Mode) and signaling and routing service model (Enhanced model (Basic Mode) and signaling and routing service model (Enhanced
Mode). Mode).
In the management-based service model, customer management systems In the management-based service model, customer management systems
and provider management systems communicate with each other. and provider management systems communicate with each other.
Customer management systems access provider management systems to Customer management systems access provider management systems to
skipping to change at page 4, line 11 skipping to change at page 4, line 11
Figure 1 depicts a deployment scenario of the L1VPN SDN control- Figure 1 depicts a deployment scenario of the L1VPN SDN control-
based service model for an external customer instantiating L1 point- based service model for an external customer instantiating L1 point-
to-point connectivity to the provider. to-point connectivity to the provider.
+------------+ +------------+
| Customer | | Customer |
| Service | | Service |
|Orchestrator| |Orchestrator|
+------------+ +------------+
| |
.. .. .. .. ..|.. .. .. .. .. .. .. .. .. ..|.. .. .. .. .. .. .
: | : : | :
: +--------------------+ : : +--------------------+ :
: | | : : | | :
: | +----------+ | : : | +----------+ | :
: | | Network | | : : | | Network | | :
: | | SDN | | : : | | SDN | | :
: | |Controller| | : : | |Controller| | :
: | |/NMS/EMS | | : : | |/NMS/EMS | | :
: | +----------+ | : : | +----------+ | :
: | | : : | | :
: | | : : | | :
skipping to change at page 6, line 20 skipping to change at page 6, line 20
shared by multiple services usually with flexibility to modify shared by multiple services usually with flexibility to modify
topologies, while separating the control functions for each service topologies, while separating the control functions for each service
department. Thus, each customer can select a specific set of department. Thus, each customer can select a specific set of
features that are needed to provide their own service [RFC4847]. features that are needed to provide their own service [RFC4847].
1.2. Terminology 1.2. Terminology
Refer to [RFC4847] and [RFC5253] for the key terms used in this Refer to [RFC4847] and [RFC5253] for the key terms used in this
document. document.
The following terms are defined in [RFC6241] and are not redefined The following terms are defined in [RFC7950] and are not redefined
here: here:
o client o client
o configuration data
o server o server
o state data
The following terms are defined in [RFC6020] and are not redefined
here:
o augment o augment
o data model o data model
o data node o data node
The following terms are defined in [RFC6241] and are not redefined
here:
o configuration data
o state data
The terminology for describing YANG data models is found in The terminology for describing YANG data models is found in
[RFC6020]. [RFC7950].
1.3. Tree diagram 1.3. Tree diagram
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
chapter 3 of this this document. The meaning of the symbols in chapter 3 of this this document. The meaning of the symbols in
these diagrams is defined in [RFC8340]. these diagrams is defined in [RFC8340].
1.4. Prefixes in Data Node Names 1.4. Prefixes in Data Node Names
In this document, names of data nodes and other data model objects In this document, names of data nodes and other data model objects
skipping to change at page 8, line 18 skipping to change at page 8, line 18
+--rw service +--rw service
+--rw service-list* [subscriber-l1vc-id] +--rw service-list* [subscriber-l1vc-id]
+--rw subscriber-l1vc-id string +--rw subscriber-l1vc-id string
+--rw service-config +--rw service-config
+--rw subscriber-l1vc-id? string +--rw subscriber-l1vc-id? string
+--rw subscriber-l1vc-ep-id-1? string +--rw subscriber-l1vc-ep-id-1? string
+--rw subscriber-l1vc-ep-id-2? string +--rw subscriber-l1vc-ep-id-2? string
+--rw subscriber-l1vc-ep-UNI-1? -> /l1cs/access/uni-list/UNI-ID +--rw subscriber-l1vc-ep-UNI-1? -> /l1cs/access/uni-list/UNI-ID
+--rw subscriber-l1vc-ep-UNI-2? -> /l1cs/access/uni-list/UNI-ID +--rw subscriber-l1vc-ep-UNI-2? -> /l1cs/access/uni-list/UNI-ID
+--rw time-start? yang:date-and-time +--rw time-start? yang:date-and-time
+--rw time-interval? int16 +--rw time-interval? Int32
+--rw performance-metric? Identityref +--rw performance-metric? Identityref
4. L1SM YANG Code 4. L1SM YANG Code
The YANG code is as follows: The YANG code is as follows:
<CODE BEGINS> file "ietf-l1csm@2018-07-02.yang" <CODE BEGINS> file "ietf-l1csm@2018-07-05"
module ietf-l1csm { module ietf-l1csm {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm"; namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm";
prefix "l1csm"; prefix "l1csm";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
skipping to change at page 9, line 25 skipping to change at page 9, line 25
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2018-07-02 { revision "2018-07-05" {
description description "Initial revision.";
"updated version to incorporate MEF comments"; reference "RFC XXXX: A Yang Data Model for L1 Connectivity
reference "to add the draft name"; Service Model (L1CSM)";
} // Note: The RFC Editor will replace XXXX with the number
// assigned to the RFC once this draft becomes an RFC.
revision 2018-06-20 {
description
"updated version to incorporate MEF comments";
reference "to add the draft name";
}
revision 2018-04-11 {
description
"Initial revision.";
reference "to add the draft name";
} }
grouping protocol-coding-optical_interface { grouping protocol-coding-optical_interface {
description description
"describes <p,c,o> where p:protocol type; c:coding "describes <p,c,o> where p:protocol type; c:coding
function; o:optical interface function"; function; o:optical interface function";
leaf protocol { leaf protocol {
type identityref { type identityref {
base "l1-st:protocol-type"; base "l1-st:protocol-type";
} }
skipping to change at page 10, line 47 skipping to change at page 10, line 36
Specification) Service Attribute expressed in a 3-tuple Specification) Service Attribute expressed in a 3-tuple
<p,c,o> of the form."; <p,c,o> of the form.";
leaf time-start { leaf time-start {
type yang:date-and-time; type yang:date-and-time;
description "a time that represent the date and time description "a time that represent the date and time
for the start of the SLS"; for the start of the SLS";
} }
leaf time-interval { leaf time-interval {
type int16; type int32;
units seconds; units seconds;
description "a time interval (e.g., 2,419,200 seconds description "a time interval (e.g., 2,419,200 seconds
which is 28 days) that is used in which is 28 days) that is used in
conjunction wuth time-start to specify a conjunction wuth time-start to specify a
contiguous sequence of time intervals T for contiguous sequence of time intervals T for
determining when performance objectives are determining when performance objectives are
met."; met.";
} }
leaf performance-metric { leaf performance-metric {
skipping to change at page 12, line 51 skipping to change at page 12, line 41
description "service-config container"; description "service-config container";
uses subscriber-attributes; uses subscriber-attributes;
}//end of service-config }//end of service-config
}//end of service list }//end of service list
} //end of service container } //end of service container
}//service top container }//service top container
} }
<CODE ENDS> <CODE ENDS>
<CODE BEGINS> file "ietf-l1-mef-service-types@2018-7-02.yang" <CODE BEGINS> file "ietf-l1-mef-service-types@2018-07-05"
module ietf-l1-mef-service-types { module ietf-l1-mef-service-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-l1-mef-service-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-l1-mef-service-types";
prefix "l1-st"; prefix "l1-st";
organization organization
"IETF CCAMP Working Group"; "IETF CCAMP Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/ccamp/> "WG Web: <http://tools.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org> WG List: <mailto:ccamp@ietf.org>
skipping to change at page 13, line 41 skipping to change at page 13, line 30
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2018-07-02" { revision "2018-07-05" {
description description "Initial revision.";
"Revision 0.2"; reference "RFC XXXX: A Yang Data Model for L1 Connectivity
reference "TBD"; Service Model (L1CSM)";
} // Note: The RFC Editor will replace XXXX with the number
// assigned to the RFC once this draft becomes an RFC.
revision "2018-06-20" {
description
"Revision 0.2";
reference "TBD";
}
revision "2018-04-11" {
description
"Revision 0.1";
reference "TBD";
} }
identity protocol-type { identity protocol-type {
description description
"base identity from which client protocol type is derived."; "base identity from which client protocol type is derived.";
} }
identity aGigE { identity aGigE {
base "protocol-type"; base "protocol-type";
description description
skipping to change at page 20, line 21 skipping to change at page 19, line 46
identity One-way-Availability { identity One-way-Availability {
base "performance-metriclist"; base "performance-metriclist";
description "one-way-availability"; description "one-way-availability";
} }
} }
<CODE ENDS> <CODE ENDS>
5. Security Considerations 5. JSON Example
This section provides a JSON example of the YANG module described in
Section 4.
{
"l1cs": {
"access": {
"uni-list": [
{
"UNI-ID": "MTL-HQ-Node3-Slot2-Port1",
"protocol": "a10GigE_LAN ",
"coding": "a10GR-PCS-49 ",
"optical_interface": "LR-PMD-clause-52 "
},
{
"UNI-ID": "MTL-STL-Node5-Slot4-Port3",
"protocol": "a10GigE_LAN ",
"coding": "a10GR-PCS-49 ",
"optical_interface": "ER-PMD-clause-52 "
}
]
},
"service": {
"service-list": [
{
"subscriber-l1vc-id": "Sub-L1VC-1867-LT-MEGAMART",
"service-config": {
"subscriber-l1vc-id": "Sub-L1VC-1867-LT-MEGAMART",
"subscriber-l1vc-ep-id-1": "MTL-HQ_1867-MEGAMART",
"subscriber-l1vc-ep-id-2": "MTL-STL_1867-MEGAMART",
"subscriber-l1vc-ep-UNI-1": "MTL-HQ-Node3-Slot2-Port1",
"subscriber-l1vc-ep-UNI-2": "MTL-STL-Node5-Slot4-Port3",
"time-start": "2018-07-13T06:06:09Z",
"time-interval": 2419200,
"performance-metric": "One-way-Delay "
}
}
]
}
}
}
6. Security Considerations
The configuration, state, and action data defined in this document The configuration, state, and action data defined in this document
are designed to be accessed via a management protocol with a secure are designed to be accessed via a management protocol with a secure
transport layer, such as NETCONF [RFC6241] or RESTCONF [RFC8040]. transport layer, such as NETCONF [RFC6241] or RESTCONF [RFC8040].
The lowest NETCONF layer is the secure transport layer, and the The lowest NETCONF layer is the secure transport layer, and the
mandatory-to-implement secure transport is Secure Shell (SSH) mandatory-to-implement secure transport is Secure Shell (SSH)
[RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory- [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-
to-implement secure transport is TLS [RFC5246]. to-implement secure transport is TLS [RFC5246].
The NETCONF access control model [RFC8341] provides the means to The NETCONF access control model [RFC8341] provides the means to
skipping to change at page 21, line 8 skipping to change at page 21, line 32
Service-Config: Service-Config:
- subscriber-l1vc-id - subscriber-l1vc-id
- subscriber-l1vc-ep-id-1 - subscriber-l1vc-ep-id-1
- subscriber-l1vc-ep-id-2 - subscriber-l1vc-ep-id-2
- subscriber-l1vc-ep-UNI-1 - subscriber-l1vc-ep-UNI-1
- subscriber-l1vc-ep-UNI-2 - subscriber-l1vc-ep-UNI-2
- time-start - time-start
- time-interval - time-interval
- performance-metric - performance-metric
6. IANA Considerations 7. IANA Considerations
This document registers the following namespace URIs in the IETF XML This document registers the following namespace URIs in the IETF XML
registry [RFC3688]: registry [RFC3688]:
-------------------------------------------------------------------- --------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-l1csm URI: urn:ietf:params:xml:ns:yang:ietf-l1csm
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
-------------------------------------------------------------------- --------------------------------------------------------------------
skipping to change at page 22, line 5 skipping to change at page 22, line 26
namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm
reference: RFC XXXX (TDB) reference: RFC XXXX (TDB)
-------------------------------------------------------------------- --------------------------------------------------------------------
-------------------------------------------------------------------- --------------------------------------------------------------------
name: ietf-l1-mef-service-types name: ietf-l1-mef-service-types
namespace: urn:ietf:params:xml:ns:yang:ietf-l1-mef-service-types namespace: urn:ietf:params:xml:ns:yang:ietf-l1-mef-service-types
reference: RFC XXXX (TDB) reference: RFC XXXX (TDB)
-------------------------------------------------------------------- --------------------------------------------------------------------
7. Acknowledgments 8. Acknowledgments
The authors would like to thank Tom Petch and Italo Busi for their The authors would like to thank Tom Petch and Italo Busi for their
helpful comments and valuable contributions. helpful comments and valuable contributions.
8. References 9. References
8.1. Normative References 9.1. Normative References
[MEF-L1CS] "Subscriber Layer 1 Connectivity Service Attributes", [MEF-L1CS] "Subscriber Layer 1 Connectivity Service Attributes",
Working Draft (WD) v0.09 December 13, 2017. Working Draft (WD) v0.09 December 13, 2017.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, June 2011. (NETCONF)", RFC 6241, June 2011.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011. Shell (SSH)", RFC 6242, June 2011.
[RFC6991] J. Schoenwaelder, Ed., "Common YANG Data Types", RFC 6991,
July 2013.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, August 2016. RFC 7950, August 2016.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, January 2017. Protocol", RFC 8040, January 2017.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", RFC 8341, March 2018. Access Control Model", RFC 8341, March 2018.
8.2. Informative References 9.2. Informative References
[RFC4847] T. Takeda (Editor), "Framework and Requirements for Layer [RFC4847] T. Takeda (Editor), "Framework and Requirements for Layer
1 Virtual Private Networks", RFC 4847, April 2007. 1 Virtual Private Networks", RFC 4847, April 2007.
[RFC5253] T. Takeda, "Applicability Statement for Layer 1 Virtual [RFC5253] T. Takeda, "Applicability Statement for Layer 1 Virtual
Private Network (L1VPN) Basic Mode", RFC 5253, July 2008. Private Network (L1VPN) Basic Mode", RFC 5253, July 2008.
[Service-Yang] Q. Wu, et al, "Service Models Explained", draft-wu- [Service-Yang] Q. Wu, et al, "Service Models Explained", draft-wu-
opsawg-service-model-explained, Work in progress. opsawg-service-model-explained, Work in progress.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, March 2018, (NMDA)", RFC 8342, March 2018,
[RFC6991] J. Schoenwaelder, Ed., "Common YANG Data Types", RFC 6991, 10. Contributors
July 2013.
9. Contributors
Contributor's Addresses Contributor's Addresses
I. Busi I. Busi
Huawei Huawei
Email: Italo.Busi@huawei.com Email: Italo.Busi@huawei.com
Authors' Addresses Authors' Addresses
G. Fioccola (Editor) G. Fioccola (Editor)
 End of changes. 27 change blocks. 
71 lines changed or deleted 95 lines changed or added

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