draft-ietf-dmm-lma-controlled-mag-params-04.txt   draft-ietf-dmm-lma-controlled-mag-params-05.txt 
DMM WG D. Patki DMM WG D. Patki
Internet-Draft S. Gundavelli Internet-Draft S. Gundavelli
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: September 12, 2017 J. Lee Expires: December 2, 2017 J. Lee
Sangmyung University Sangmyung University
Q. Fu Q. Fu
China Mobile China Mobile
L. Bertz L. Bertz
Sprint Sprint
March 11, 2017 May 31, 2017
LMA Controlled MAG Session Parameters LMA Controlled MAG Session Parameters
draft-ietf-dmm-lma-controlled-mag-params-04.txt draft-ietf-dmm-lma-controlled-mag-params-05.txt
Abstract Abstract
This specification defines a new extension, LMA-Controlled-MAG- This specification defines a new extension, LMA-Controlled-MAG-
Session-Params to Proxy Mobile IPv6. This option can be used by the Session-Params to Proxy Mobile IPv6. This option can be used by the
local mobility anchor in Proxy Mobile IPv6 signaling for notifying local mobility anchor in Proxy Mobile IPv6 signaling for notifying
the mobile access gateway to conform to various parameters contained the mobile access gateway to conform to various configuration
in this extension. parameters such as heartbeat parameters and binding refresh
parameters.
Status of This Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. 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). 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 September 12, 2017. This Internet-Draft will expire on December 2, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3
2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . 3 3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . 4 3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . . 4
3.1.1. Binding Re-registration Control Sub-Option . . . . . 5 3.1.1. Binding Re-registration Control Sub-Option . . . . . . 5
3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . 6 3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . . 6
4. Protocol Configuration Variables . . . . . . . . . . . . . . 6 4. Protocol Configuration Variables . . . . . . . . . . . . . . . 7
4.1. Local Mobility Anchor - Configuration Variables . . . . . 6 4.1. Local Mobility Anchor - Configuration Variables . . . . . 7
5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8 5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8
5.1. Local Mobility Anchor Considerations . . . . . . . . . . 8 5.1. Local Mobility Anchor Considerations . . . . . . . . . . . 9
5.2. Mobile Access Gateway Considerations . . . . . . . . . . 9 5.2. Mobile Access Gateway Considerations . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . 11 9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
A large Proxy Mobile IPv6 (PMIPv6) deployment, such as residential A large Proxy Mobile IPv6 (PMIPv6) [RFC5213] deployment, such as
deployment, can have tens of thousands of mobile access gateways residential deployment, can have tens of thousands of mobile access
(MAG) spread across geographical locations. While it can be gateways (MAG) spread across geographical locations. While it can be
operationally challenging to manage such a large number of MAGs, it operationally challenging to manage such a large number of MAGs, it
can also be very difficult to ensure configuration consistency across can also be very difficult to ensure configuration consistency across
all the MAGs if they are not centrally managed. Configuring all the MAGs if they are not centrally managed. Configuring
aggressive values of parameters such as re-registration timeout and aggressive values of parameters such as re-registration timeout and
heartbeat interval can potentially create considerable signaling load heartbeat interval can potentially create considerable signaling load
on the local mobility anchor (LMA). This document provides a new on the local mobility anchor (LMA). This document provides a new
option to enable the LMA to control various parameters on the MAG option to enable the LMA to control various parameters on the MAG
such as the re-registration frequency [RFC5213] and heartbeat such as the re-registration frequency [RFC5213] and heartbeat
frequency [RFC5847]. With this option, the configuration of these frequency [RFC5847]. With this option, the configuration of these
tunable parameters done centrally on the LMA enables Service tunable parameters done centrally on the LMA enables Service
skipping to change at page 3, line 26 skipping to change at page 3, line 44
in [RFC5213], [RFC5847] and [RFC7563]. in [RFC5213], [RFC5847] and [RFC7563].
3. Protocol Extension 3. Protocol Extension
The LMA Controlled MAG Parameters (LCMP) option is a mobility header The LMA Controlled MAG Parameters (LCMP) option is a mobility header
option used to exchange information related to the parameters that a option used to exchange information related to the parameters that a
LMA enforces on a MAG. The option can be included in Proxy Binding LMA enforces on a MAG. The option can be included in Proxy Binding
Acknowledge (PBA) message only, and there MUST NOT be more than a Acknowledge (PBA) message only, and there MUST NOT be more than a
single instance of this mobility option in the PBA message. This single instance of this mobility option in the PBA message. This
mobility option MUST contain one or more LCMP sub-options. The sub- mobility option MUST contain one or more LCMP sub-options. The sub-
options are defined in Section 3.1. The alignment of this option options are defined in Section 3.1. The LCMP option has an alignment
MUST be 4n [RFC2460]. requirement of 4n+2 [RFC2460].
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | | LCMP Sub-option(s) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... LCMP Sub-option(s) ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: LMA Controlled MAG Parameters Option Figure 1: LMA Controlled MAG Parameters Option
Type Type
MUST be set to the value of IANA-1, indicating that it is a LMA- MUST be set to the value of IANA-1, indicating that it is a LMA-
Controlled-MAG-Parameters option. Controlled-MAG-Parameters option.
Length Length
8-bit unsigned integer indicating the length in octets of the 8-bit unsigned integer indicating the length in octets of the
option, excluding the Type and Length fields. option, excluding the Type and Length fields.
Reserved
MUST be set to zero when sending and ignored when received.
LCMP Sub-option(s) LCMP Sub-option(s)
LCMP Sub-options are described in the below sections. The sub- LCMP Sub-options are described in the below sections. The sub-
options can be present in any order. Inclusion of any specifc options can be present in any order. Inclusion of any specifc
sub-option is optional, but at least one sub-option MUST be sub-option is optional, but at least one sub-option MUST be
present. present.
3.1. Format of the LCMP Sub-Options 3.1. Format of the LCMP Sub-Options
The LCMP sub-options are used for carrying information elements The LCMP sub-options are used for carrying information elements
related to various parameters that need to be configured on the MAG. related to various parameters that need to be configured on the MAG.
These sub-options can be included in the LCMP option defined in These sub-options can be included in the LCMP option defined in
Section 3. The alignment of the sub-option MUST be 4n. The format Section 3. The LCMP sub-options have an alignment requirement of 4n.
of this sub-option is as follows. The format of this sub-option is as follows.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LCMP Type | LCMP Length | Sub-Option Data ~ | LCMP Type | LCMP Length | Sub-Option Data ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: LMA Controlled MAG Parameters Sub-Option Figure 2: LMA Controlled MAG Parameters Sub-Option
Type Type
skipping to change at page 6, line 46 skipping to change at page 7, line 19
HB-Max-Retransmissions HB-Max-Retransmissions
16-bit unsigned integer indicating maximum number of heartbeat 16-bit unsigned integer indicating maximum number of heartbeat
retransmissions. retransmissions.
4. Protocol Configuration Variables 4. Protocol Configuration Variables
4.1. Local Mobility Anchor - Configuration Variables 4.1. Local Mobility Anchor - Configuration Variables
The LMA MUST allow the following variables to be configured by the This specification defines the following variables to be configured
system management. The configured values for these protocol by the system management. The configured values for these protocol
variables MUST survive server reboots and service restarts. variables MUST survive server reboots and service restarts.
EnableLCMPSubOptReregControl EnableLCMPSubOptReregControl
This flag indicates the operational state of the Binding Re- This flag indicates the operational state of the Binding Re-
registration Control sub-option support. The default value for registration Control sub-option support. The default value of
this flag is set to (0), indicating that support for the Binding this flag is (0), indicating that support for the Binding Re-
Re-registration Control sub-option is disabled. registration Control sub-option is disabled.
EnableLCMPSubOptHeartbeatControl EnableLCMPSubOptHeartbeatControl
This flag indicates the operational state of the Heartbeat Control This flag indicates the operational state of the Heartbeat Control
sub-option support. The default value for this flag is set to sub-option support. The default value of this flag is (0),
(0), indicating that support for the Heartbeat Control sub-option indicating that support for the Heartbeat Control sub-option is
is disabled. disabled.
The following variables MAY be defined at various granularities such The following variables MAY be defined at various granularities such
as per binding, per peering MAG, per cluster of MAGs or any other as per binding, per cluster of bindings, per peering MAG, per cluster
custom grouping. Regardless of the granularity of this of peering MAGs or any other custom grouping. Regardless of the
configuration, the LMA MUST be able to determine the value of these granularity of this configuration, the LMA MUST be able to determine
variables on an individual binding basis by way of configuration the value of these variables for every individual binding.
hierarchy.
LCMPReregistrationStartTime LCMPReregistrationStartTime
This variable is used to set the minimum time interval in number This variable is used to set the minimum time interval in number
of seconds before the expiry of the PMIPv6 binding lifetime when of seconds before the expiry of the PMIPv6 binding lifetime when
the registration refresh process SHOULD be activated. The default the registration refresh process SHOULD be activated. The default
value is 10 units, where each unit is 4 seconds. value of this variable is 10 units, where each unit is 4 seconds.
LCMPInitialRetransmissionTime LCMPInitialRetransmissionTime
This variable is used to set the minimum delay in seconds before This variable is used to set the minimum delay in seconds before
the first PBU retransmission of the exponential back-off process. the first PBU retransmission of the exponential back-off process.
This variable is same as INITIAL_BINDACK_TIMEOUT mentioned in This variable is same as INITIAL_BINDACK_TIMEOUT mentioned in
Section 6.9.4 of [RFC5213]. The default value is 1 second. Section 6.9.4 of [RFC5213]. The default value of this variable is
1 second.
LCMPMaximumRetransmissionTime LCMPMaximumRetransmissionTime
This variable is used to set the maximum delay in seconds before This variable is used to set the maximum delay in seconds before
the last PBU retransmission message of the exponential back-off the last PBU retransmission message of the exponential back-off
process. This variable is same as MAX_BINDACK_TIMEOUT mentioned process. This variable is same as MAX_BINDACK_TIMEOUT mentioned
in Section 6.9.4 of [RFC5213]. The default value is 32 seconds. in Section 6.9.4 of [RFC5213]. The default value of this variable
is 32 seconds.
LCMPHeartbeatInterval LCMPHeartbeatInterval
This variable is used to set the time delay in seconds after a This variable is used to set the time delay in seconds after a
successful heartbeat exchange (heartbeat request followed by successful heartbeat exchange (heartbeat request followed by
response) when the next heartbeat exchange can be triggered. The response) when the next heartbeat exchange can be triggered. The
default value is 60 seconds. It SHOULD NOT be set to less than 30 default value of this variable is 60 seconds. The time delay
seconds or more than 3600 seconds. The value of this variable MAY SHOULD NOT be less than 30 seconds or more than 3600 seconds. The
be derived from the variable HEARTBEAT_INTERVAL defined in value of this variable MAY be derived from the variable
Section 5 of [RFC5847] if configured on the LMA. HEARTBEAT_INTERVAL defined in Section 5 of [RFC5847] if configured
on the LMA.
LCMPHeartbeatRetransmissionDelay LCMPHeartbeatRetransmissionDelay
This variable is used to set the minimum time delay in seconds This variable is used to set the minimum time delay in seconds
before a heartbeat message is retransmitted. The value of this before a heartbeat message is retransmitted. The value of this
variable SHOULD be less than LCMPHeartbeatInterval. The default variable SHOULD be less than LCMPHeartbeatInterval. The default
value is 5 seconds. value of this variable is 5 seconds.
LCMPHeartbeatMaxRetransmissions LCMPHeartbeatMaxRetransmissions
This variable is used to set the maximum number of heartbeat This variable is used to set the maximum number of heartbeat
retransmissions. The default value for this variable is 3. The retransmissions. The default value of this variable is 3. The
value of this variable MAY be derived from the variable value of this variable MAY be derived from the variable
MISSING_HEARTBEATS_ALLOWED defined in Section 5 of [RFC5847] if MISSING_HEARTBEATS_ALLOWED defined in Section 5 of [RFC5847] if
configured on the LMA. configured on the LMA.
5. Protocol Considerations 5. Protocol Considerations
The following considerations apply to the LMA and the MAG. The following considerations apply to the LMA and the MAG.
The conceptual Binding Cache Entry data structure maintained by the For supporting this extension, the conceptual Binding Cache Entry
LMA, described in Section 5.1 of [RFC5213] and the conceptual Binding data structure maintained by the LMA, described in Section 5.1 of
Update List entry data structure maintained by the MAG, described in [RFC5213] and the conceptual Binding Update List entry data structure
Section 6.1 of [RFC5213], MUST be extended to store the LCMP option maintained by the MAG, described in Section 6.1 of [RFC5213], need to
related information elements associated with the current session. be extended to store the LCMP option related information elements
Specifically the following parameters MUST be defined: defined below.
o LCMPReregistrationStartTime o LCMPReregistrationStartTime
o LCMPInitialRetransmissionTime o LCMPInitialRetransmissionTime
o LCMPMaximumRetransmissionTime o LCMPMaximumRetransmissionTime
o LCMPHeartbeatInterval o LCMPHeartbeatInterval
o LCMPHeartbeatRetransmissionDelay o LCMPHeartbeatRetransmissionDelay
skipping to change at page 10, line 28 skipping to change at page 11, line 7
+---+-----------------------------------------------------+ +---+-----------------------------------------------------+
| 0 | Reserved | | 0 | Reserved |
+---+-----------------------------------------------------+ +---+-----------------------------------------------------+
| 1 | Binding Re-registration Control Sub-Option | | 1 | Binding Re-registration Control Sub-Option |
+---+-----------------------------------------------------+ +---+-----------------------------------------------------+
| 2 | Heartbeat Control Sub-Option | | 2 | Heartbeat Control Sub-Option |
+---+-----------------------------------------------------+ +---+-----------------------------------------------------+
7. Security Considerations 7. Security Considerations
The LCMP Parameters option defined in this specification is for use The LCMP Parameters option defined in this specification allows the
in PBA message. This option is carried like any other mobility configuration of re-registration and heartbeat frequencies. This
header option as specified in [RFC6275] and does not require any option is defined for carrying it in Proxy Binding Update and Proxy
special security considerations. Binding Acknowledgement messages. This option is carried like any
other mobility header option as specified in [RFC5213] and does not
require any special security considerations.
8. Acknowledgements 8. Acknowledgements
The authors would like to thank the DMM working group for all the The authors would like to thank the DMM working group for all the
comments and discussions on this document. The authors would also comments and discussions on this document. The authors would also
like to thank Suresh Krishnan and Ralph Droms for their review like to thank Suresh Krishnan, Ralph Droms, Mirja Kuehlewind, Alexey
feedback. Melnikov and Ben Campbell for their review feedback.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
DOI 10.17487/RFC2119, March 1997, RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
RFC 5213, DOI 10.17487/RFC5213, August 2008, RFC 5213, DOI 10.17487/RFC5213, August 2008,
<http://www.rfc-editor.org/info/rfc5213>. <http://www.rfc-editor.org/info/rfc5213>.
[RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N., [RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N.,
Krishnan, S., and J. Laganier, "Heartbeat Mechanism for Krishnan, S., and J. Laganier, "Heartbeat Mechanism for
Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, June Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847,
2010, <http://www.rfc-editor.org/info/rfc5847>. June 2010, <http://www.rfc-editor.org/info/rfc5847>.
[RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen, [RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen,
J., and J. Kaippallimalil, "Extensions to the Proxy Mobile J., and J. Kaippallimalil, "Extensions to the Proxy Mobile
IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563, IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563,
DOI 10.17487/RFC7563, June 2015, DOI 10.17487/RFC7563, June 2015,
<http://www.rfc-editor.org/info/rfc7563>. <http://www.rfc-editor.org/info/rfc7563>.
9.2. Informative References 9.2. Informative References
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <http://www.rfc-editor.org/info/rfc2460>. December 1998, <http://www.rfc-editor.org/info/rfc2460>.
[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July Support in IPv6", RFC 6275, DOI 10.17487/RFC6275,
2011, <http://www.rfc-editor.org/info/rfc6275>. July 2011, <http://www.rfc-editor.org/info/rfc6275>.
Authors' Addresses Authors' Addresses
Dhananjay Patki Dhananjay Patki
Cisco Cisco
Cessna Business Park SEZ, Kadubeesanahalli Cessna Business Park SEZ, Kadubeesanahalli
Bangalore, Karnataka 560087 Bangalore, Karnataka 560087
India India
Email: dhpatki@cisco.com Email: dhpatki@cisco.com
 End of changes. 30 change blocks. 
81 lines changed or deleted 83 lines changed or added

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