draft-ietf-lisp-mib-06.txt   draft-ietf-lisp-mib-07.txt 
Network Working Group G. Schudel Network Working Group G. Schudel
Internet-Draft A. Jain Internet-Draft A. Jain
Intended status: Experimental V. Moreno Intended status: Experimental V. Moreno
Expires: April 5, 2013 cisco Systems Expires: April 18, 2013 cisco Systems
October 2, 2012 October 15, 2012
LISP MIB LISP MIB
draft-ietf-lisp-mib-06 draft-ietf-lisp-mib-07
Abstract Abstract
This document defines managed objects for the Locator/ID Separation This document defines managed objects for the Locator/ID Separation
Protocol (LISP). These objects provide information useful for Protocol (LISP). These objects provide information useful for
monitoring LISP devices, including basic configuration information, monitoring LISP devices, including basic configuration information,
LISP status, and operational statistics. LISP status, and operational statistics.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 April 5, 2013. This Internet-Draft will expire on April 18, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 2, line 23 skipping to change at page 2, line 23
6.1. Overview of Defined Notifications . . . . . . . . . . . . 6 6.1. Overview of Defined Notifications . . . . . . . . . . . . 6
6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 7 6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 7
7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 8 7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 8
8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 62 8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 62
8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 62 8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 62
9. Security Considerations . . . . . . . . . . . . . . . . . . . 62 9. Security Considerations . . . . . . . . . . . . . . . . . . . 62
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63
11.1. Normative References . . . . . . . . . . . . . . . . . . . 63 11.1. Normative References . . . . . . . . . . . . . . . . . . . 63
11.2. Informative References . . . . . . . . . . . . . . . . . . 64 11.2. Informative References . . . . . . . . . . . . . . . . . . 64
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 65 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 64
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 65 Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 64
1. Requirements Notation 1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
2. Introduction 2. Introduction
This draft describes the Management Information Base (MIB) module for This draft describes the Management Information Base (MIB) module for
use with network management protocols in the Internet community. use with network management protocols in the Internet community.
Specifically, the MIB for managing Locator/ID Separation Protocol Specifically, the MIB for managing Locator/ID Separation Protocol
(LISP) devices is described. (LISP) devices is described.
LISP [LISP] specifies a network-based architecture and mechanisms LISP [LISP] specifies a network-based architecture and mechanisms
that implement a new semantic for IP addressing using two separate that implement a new semantic for IP addressing using two separate
skipping to change at page 5, line 38 skipping to change at page 5, line 39
behalf of LISP sites which send packets to destinations at non- behalf of LISP sites which send packets to destinations at non-
LISP sites. The PETR is defined and described in [INTERWORK]. LISP sites. The PETR is defined and described in [INTERWORK].
LISP Site: a set of routers in an edge network that are under a LISP Site: a set of routers in an edge network that are under a
single technical administration. LISP routers which reside in the single technical administration. LISP routers which reside in the
edge network are the demarcation points to separate the edge edge network are the demarcation points to separate the edge
network from the core network. network from the core network.
Map-Server: a LISP network infrastructure component which learns Map-Server: a LISP network infrastructure component which learns
EID-to-RLOC mapping entries from an authoritative source such as EID-to-RLOC mapping entries from an authoritative source such as
an ETR though static configuration, or another out-of-band an ETR through static configuration, or another out-of-band
mechanism. A Map-Server advertises these mappings into the mechanism. A Map-Server advertises these mappings into the
distributed mapping database. distributed mapping database.
Map-Resolver: a LISP network infrastructure component which accepts Map-Resolver: a LISP network infrastructure component which accepts
LISP Encapsulated Map-Requests, typically from an ITR, and quickly LISP Encapsulated Map-Requests, typically from an ITR, and quickly
determines whether or not the destination IP address is part of determines whether or not the destination IP address is part of
the EID namespace. If it is, the Map-Resolver finds the the EID namespace. If it is, the Map-Resolver finds the
appropriate EID-to-RLOC mapping by consulting the distributed appropriate EID-to-RLOC mapping by consulting the distributed
mapping database. If it is not, a Negative Map-Reply is mapping database. If it is not, a Negative Map-Reply is
immediately returned. immediately returned.
skipping to change at page 8, line 18 skipping to change at page 8, line 18
lispUseProxyEtr - This table provides the properties of all Proxy lispUseProxyEtr - This table provides the properties of all Proxy
ETRs that this device is configured to use. ETRs that this device is configured to use.
7. LISP MIB Definitions 7. LISP MIB Definitions
LISP-MIB DEFINITIONS ::= BEGIN LISP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
mib-2, Unsigned32, Counter64, mib-2, Unsigned32, Counter64,
Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC 2578] Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC2578]
TruthValue, TEXTUAL-CONVENTION, TruthValue, TEXTUAL-CONVENTION,
TimeStamp FROM SNMPv2-TC -- [RFC 2579] TimeStamp FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC 2580] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
MplsL3VpnName MplsL3VpnName
FROM MPLS-L3VPN-STD-MIB -- [RFC 4382] FROM MPLS-L3VPN-STD-MIB -- [RFC4382]
AddressFamilyNumbers AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA] FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA]
lispMIB MODULE-IDENTITY lispMIB MODULE-IDENTITY
LAST-UPDATED "201209280000Z" -- 28 September 2012 LAST-UPDATED "201210150000Z" -- 15 October 2012
ORGANIZATION ORGANIZATION
"IETF Locator/ID Separation Protocol (LISP) Working Group" "IETF Locator/ID Separation Protocol (LISP) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: lisp@ietf.org "Email: lisp@ietf.org
WG charter: WG charter:
http://www.ietf.org/html.charters/lisp-charter.html" http://www.ietf.org/html.charters/lisp-charter.html"
DESCRIPTION DESCRIPTION
"Locator/ID Separation Protocol (LISP) MIB Textual "Locator/ID Separation Protocol (LISP) MIB Textual
Conventions module. The LISP MIB is intended for Conventions module. The LISP MIB is intended for
management of LISP routers. management of LISP routers.
Copyright (C) The IETF Trust (2012)." Copyright (C) The IETF Trust (2012)."
REVISION "201209280000Z" -- 28 September 2012 REVISION "201210150000Z" -- 15 October 2012
DESCRIPTION "Initial version of the IETF LISP-MIB module. Published DESCRIPTION "Initial version of the IETF LISP-MIB module. Published
as RFC xxxx." as RFC xxxx."
-- RFC Ed.: RFC-editor pls fill in xxxx -- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: assigned by IANA, see section 10 for details -- RFC Ed.: assigned by IANA, see section 10 for details
-- --
-- Textual Conventions -- Textual Conventions
-- --
LispAddressType ::= TEXTUAL-CONVENTION LispAddressType ::= TEXTUAL-CONVENTION
skipping to change at page 9, line 47 skipping to change at page 9, line 47
To illustrate the use of this object, consider the LISP MIB To illustrate the use of this object, consider the LISP MIB
Object below entitled lispMapCacheEntry. This object begins Object below entitled lispMapCacheEntry. This object begins
with the following entities: with the following entities:
lispMapCacheEntry ::= SEQUENCE { lispMapCacheEntry ::= SEQUENCE {
lispMapCacheEidLength INTEGER, lispMapCacheEidLength INTEGER,
lispMapCacheEid LispAddressType, lispMapCacheEid LispAddressType,
... [skip] ... ... [skip] ...
Example 1: Suppose that the IPv4 EID prefix stored is Example 1: Suppose that the IPv4 EID prefix stored is
10.10.10.0/24. In this case, the values within 192.0.2.0/24. In this case, the values within
lispMapCacheEntry would be: lispMapCacheEntry would be:
lispMapCacheEidLength = 8 lispMapCacheEidLength = 8
lispMapCacheEid = 1, 4, 10.10.10.0, 24 lispMapCacheEid = 1, 4, 192.0.2.0, 24
... [skip] ... ... [skip] ...
where 8 is the total length in octets of the next where 8 is the total length in octets of the next
object (lispMapCacheEID of type LispAddressType). Then, object (lispMapCacheEID of type LispAddressType). Then,
the value 1 indicates the IPv4 AF (per [IANA]), the the value 1 indicates the IPv4 AF (per [IANA]), the
value 4 indicates that the AF is 4-octets in length, value 4 indicates that the AF is 4-octets in length,
10.10.10.0 is the IPv4 address, and the value 24 is the 192.0.2.0 is the IPv4 address, and the value 24 is the
mask-length in bits. Note that the lispMapCacheEidLength mask-length in bits. Note that the lispMapCacheEidLength
value of 8 is used to compute the length of the fourth value of 8 is used to compute the length of the fourth
(last) field in lispMapCacheEid to be 1 octet - as (last) field in lispMapCacheEid to be 1 octet - as
computed by 8 - (2 + 1 + 4) = 1. computed by 8 - (2 + 1 + 4) = 1.
Example 2: Suppose that the IPv6 EID prefix stored is Example 2: Suppose that the IPv6 EID prefix stored is
2001:db8:a::/48. In this case, the values within 2001:db8:a::/48. In this case, the values within
lispMapCacheEntry would be: lispMapCacheEntry would be:
lispMapCacheEidLength = 20 lispMapCacheEidLength = 20
skipping to change at page 10, line 35 skipping to change at page 10, line 35
object (lispMapCacheEID of type LispAddressType). Then, object (lispMapCacheEID of type LispAddressType). Then,
the value 2 indicates the IPv4 AF (per [IANA]), the the value 2 indicates the IPv4 AF (per [IANA]), the
value 16 indicates that the AF is 16-octets in length, value 16 indicates that the AF is 16-octets in length,
2001:db8:a:: is the IPv6 address, and the value 48 is the 2001:db8:a:: is the IPv6 address, and the value 48 is the
mask-length in bits. Note that the lispMapCacheEidLength mask-length in bits. Note that the lispMapCacheEidLength
value of 20 is used to compute the length of the fourth value of 20 is used to compute the length of the fourth
(last) field in lispMapCacheEid to be 1 octet - as (last) field in lispMapCacheEid to be 1 octet - as
computed by 20 - (2 + 1 + 16) = 1. computed by 20 - (2 + 1 + 16) = 1.
Example 3: As an example where LCAF is used, suppose Example 3: As an example where LCAF is used, suppose
that the IPv4 EID prefix stored is 10.10.10.0/24 and it that the IPv4 EID prefix stored is 192.0.2.0/24 and it
is part of LISP Instance ID 101. In this case, the values is part of LISP Instance ID 101. In this case, the values
within lispMapCacheEntry would be: within lispMapCacheEntry would be:
lispMapCacheEidLength = 11 lispMapCacheEidLength = 11
lispMapCacheEid = 16387, 7, 2, 101, 1, 10.10.10.0, 24 lispMapCacheEid = 16387, 7, 2, 101, 1, 192.0.2.0, 24
... [skip] ... ... [skip] ...
where 11 is the total length in octets of the next object where 11 is the total length in octets of the next object
(lispMapCacheEID of type LispAddressType). Then, the value (lispMapCacheEID of type LispAddressType). Then, the value
16387 indicates the LCAF AF (see [IANA]), the value 7 16387 indicates the LCAF AF (see [IANA]), the value 7
indicates that the LCAF AF is 7-octets in length in this indicates that the LCAF AF is 7-octets in length in this
case, 2 indicates that LCAF Type 2 encoding is used (see case, 2 indicates that LCAF Type 2 encoding is used (see
[LCAF]), 101 gives the Instance ID, 1 gives the AFI (per [LCAF]), 101 gives the Instance ID, 1 gives the AFI (per
[IANA]) for an IPv4 address, 10.10.10.0 is the IPv4 [IANA]) for an IPv4 address, 192.0.2.0 is the IPv4
address, and 24 is the mask-length in bits. Note that the address, and 24 is the mask-length in bits. Note that the
lispMapCacheEidLength value of 11 octets is used to compute lispMapCacheEidLength value of 11 octets is used to compute
the length of the last field in lispMapCacheEid to be 1 octet, the length of the last field in lispMapCacheEid to be 1 octet,
as computed by 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) = 1." as computed by 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) = 1."
REFERENCE REFERENCE
"[LISP], Section 14.2." "[LISP], Section 14.2."
SYNTAX OCTET STRING (SIZE (5..39)) SYNTAX OCTET STRING (SIZE (5..39))
-- --
skipping to change at page 15, line 43 skipping to change at page 15, line 43
LispIidToVrfEntry ::= SEQUENCE { LispIidToVrfEntry ::= SEQUENCE {
lispIidToVrfName MplsL3VpnName lispIidToVrfName MplsL3VpnName
} }
lispIidToVrfName OBJECT-TYPE lispIidToVrfName OBJECT-TYPE
SYNTAX MplsL3VpnName SYNTAX MplsL3VpnName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for each VPN, as specified in "The identifier for each VPN, as specified in
[RFC4382, Section 7], that is mapped to the given RFC 4382, Section 7 [RFC4382], that is mapped to the
LISP Instance ID." given LISP Instance ID."
::= { lispIidToVrfEntry 2 } ::= { lispIidToVrfEntry 2 }
lispGlobalStatsTable OBJECT-TYPE lispGlobalStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispGlobalStatsEntry SYNTAX SEQUENCE OF LispGlobalStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides global statistics for a given "This table provides global statistics for a given
Instance ID per address-family on a LISP device." Instance ID per address-family on a LISP device."
REFERENCE REFERENCE
skipping to change at page 63, line 42 skipping to change at page 63, line 42
March 2012. March 2012.
[LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, [LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
"Locator/ID Separation Protocol (LISP)", "Locator/ID Separation Protocol (LISP)",
draft-ietf-lisp-23.txt (work in progress), May 2012. draft-ietf-lisp-23.txt (work in progress), May 2012.
[LISP-MS] Farinacci, D. and V. Fuller, "LISP Map Server", [LISP-MS] Farinacci, D. and V. Fuller, "LISP Map Server",
draft-ietf-lisp-ms-16.txt (work in progress), draft-ietf-lisp-ms-16.txt (work in progress),
March 2012. March 2012.
[RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987.
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96
within ESP and AH", RFC 2404, November 1998.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999. April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
skipping to change at page 64, line 17 skipping to change at page 64, line 10
April 1999. April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms [RFC4382] Nadeau, T. and H. van der Linde, "MPLS/BGP Layer 3
(SHA and HMAC-SHA)", RFC 4634, July 2006. Virtual Private Network (VPN) Management Information
Base", RFC 4382, February 2006.
11.2. Informative References 11.2. Informative References
[LCAF] Farinacci, D., Meyer, D., and J. Snijders, "LISP [LCAF] Farinacci, D., Meyer, D., and J. Snijders, "LISP
Canonical Address Format", draft-ietf-lisp-lcaf-00.txt Canonical Address Format", draft-ietf-lisp-lcaf-00.txt
(work in progress), August 2012. (work in progress), August 2012.
[LISP-MCAST] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, [LISP-MCAST] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas,
"LISP for Multicast Environments", "LISP for Multicast Environments",
draft-ietf-lisp-multicast-14.txt (work in progress), draft-ietf-lisp-multicast-14.txt (work in progress),
February 2012. February 2012.
[LISP-MN] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
"LISP Mobile Node Architecture",
draft-meyer-lisp-mn-07.txt (work in progress),
April 2012.
[RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
Traina, "Generic Routing Encapsulation (GRE)",
RFC 2784, March 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760,
January 2007.
Appendix A. Open Issues Appendix A. Open Issues
Open issues for the LISP MIB include the following: Open issues for the LISP MIB include the following:
1. This LISP MIB draft does not include LISP Multicast 1. This LISP MIB draft does not include LISP Multicast [LISP-MCAST]
considerations. Multicast considerations will be added in a considerations. Multicast considerations will be added in a
separate LISP Multicast MIB draft. separate LISP Multicast MIB draft.
Appendix B. Acknowledgments Appendix B. Acknowledgments
A thank you is owed to Dino Farinacci for his inputs and review A thank you is owed to Dino Farinacci for his inputs and review
comments on the initial versions of this draft. In addition, the comments on the initial versions of this draft. In addition, the
authors would like to gratefully acknowledge several others who have authors would like to gratefully acknowledge several others who have
reviewed and commented on this draft. They include: Darrel Lewis, reviewed and commented on this draft. They include: Darrel Lewis,
Isidor Kouvelas, Jesper Skriver, Selina Heimlich, and Parna Agrawal. Isidor Kouvelas, Jesper Skriver, Selina Heimlich, Parna Agrawal, Dan
Romascanu, and Luigi Iannone.
Authors' Addresses Authors' Addresses
Gregg Schudel Gregg Schudel
cisco Systems cisco Systems
Tasman Drive Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
EMail: gschudel@cisco.com EMail: gschudel@cisco.com
 End of changes. 26 change blocks. 
50 lines changed or deleted 30 lines changed or added

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