draft-ietf-geopriv-rfc3825bis-08.txt   draft-ietf-geopriv-rfc3825bis-09.txt 
GEOPRIV Working Group J. Polk GEOPRIV Working Group J. Polk
INTERNET-DRAFT Cisco Systems INTERNET-DRAFT Cisco Systems
Obsoletes: 3825 (if approved) J. Schnizlein Obsoletes: 3825 (if approved) J. Schnizlein
Category: Standards Track Individual Contributor Category: Standards Track Individual Contributor
Expires: August 15, 2010 M. Linsner Expires: September 15, 2010 M. Linsner
13 February 2010 Cisco Systems 7 March 2010 Cisco Systems
M. Thomson M. Thomson
Andrew Andrew
B. Aboba (ed) B. Aboba (ed)
Microsoft Corporation Microsoft Corporation
Dynamic Host Configuration Protocol Options for Dynamic Host Configuration Protocol Options for
Coordinate-based Location Configuration Information Coordinate-based Location Configuration Information
draft-ietf-geopriv-rfc3825bis-08.txt draft-ietf-geopriv-rfc3825bis-09.txt
Abstract Abstract
This document specifies Dynamic Host Configuration Protocol Options This document specifies Dynamic Host Configuration Protocol Options
(both DHCPv4 and DHCPv6) for the coordinate-based geographic location (both DHCPv4 and DHCPv6) for the coordinate-based geographic location
of the client. The Location Configuration Information (LCI) includes of the client. The Location Configuration Information (LCI) includes
Latitude, Longitude, and Altitude, with resolution or uncertainty Latitude, Longitude, and Altitude, with resolution or uncertainty
indicators for each. Separate parameters indicate the reference indicators for each. Separate parameters indicate the reference
datum for each of these values. datum for each of these values.
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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."
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 August 15, 2010. This Internet-Draft will expire on September 15, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 3, line 26 skipping to change at page 3, line 26
3. Security Considerations. . . . . . . . . . . . . . . . . . . . 15 3. Security Considerations. . . . . . . . . . . . . . . . . . . . 15
4. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 15 4. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 15
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1. Normative References . . . . . . . . . . . . . . . . . . 16 6.1. Normative References . . . . . . . . . . . . . . . . . . 16
6.2. Informational References . . . . . . . . . . . . . . . . 17 6.2. Informational References . . . . . . . . . . . . . . . . 17
Appendix A. GML Mapping . . . . . . . . . . . . . . . . . . . . . 18 Appendix A. GML Mapping . . . . . . . . . . . . . . . . . . . . . 18
A.1. GML Templates . . . . . . . . . . . . . . . . . . . . . 18 A.1. GML Templates . . . . . . . . . . . . . . . . . . . . . 18
Appendix B. Calculations of Resolution . . . . . . . . . . . . . . 22 Appendix B. Calculations of Resolution . . . . . . . . . . . . . . 22
B.1. LCI of "White House" (Example 1) . . . . . . . . . . . . 22 B.1. LCI of "White House" (Example 1) . . . . . . . . . . . . 22
B.2. LCI of "Sears Tower" (Example 2) . . . . . . . . . . . . 24 B.2. LCI of "Sears Tower" (Example 2) . . . . . . . . . . . . 25
Appendix C. Calculations of Uncertainty . . . . . . . . . . . . . 26 Appendix C. Calculations of Uncertainty . . . . . . . . . . . . . 26
C.1 LCI of "Sydney Opera House" (Example 3) . . . . . . . . 26 C.1 LCI of "Sydney Opera House" (Example 3) . . . . . . . . 26
Appendix D. Changes from RFC 3825 . . . . . . . . . . . . . . . . 30 Appendix D. Changes from RFC 3825 . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
The physical location of a network device has a range of The physical location of a network device has a range of
applications. In particular, emergency telephony applications rely applications. In particular, emergency telephony applications rely
on knowing the location of a caller in order to determine the correct on knowing the location of a caller in order to determine the correct
skipping to change at page 20, line 29 skipping to change at page 20, line 29
The uncertainty fields (LatUnc, LongUnc, AltUnc) indicate the bounds The uncertainty fields (LatUnc, LongUnc, AltUnc) indicate the bounds
of the location region described by a DHCP location object. For of the location region described by a DHCP location object. For
version 0 of the DHCPv4 option, the uncertainty fields represent version 0 of the DHCPv4 option, the uncertainty fields represent
resolution, indicating how many bits of a value contain information. resolution, indicating how many bits of a value contain information.
Any bits beyond those indicated can be either zero or one. For the Any bits beyond those indicated can be either zero or one. For the
DHCPv6 option and version 1 of the DHCPv4 option, the LatUnc, LongUnc DHCPv6 option and version 1 of the DHCPv4 option, the LatUnc, LongUnc
and AltUnc fields indicate uncertainty distances. and AltUnc fields indicate uncertainty distances.
The two sections below describe how to compute the Latitude, The two sections below describe how to compute the Latitude,
Longitude, and Altitude bounds (e.g., $lowlatitide$, $highAltitude$) Longitude, and Altitude bounds (e.g., $lowLatitude$, $highAltitude$)
in the templates above. The first section describes how these bounds in the templates above. The first section describes how these bounds
are computed in the "resolution encoding" (version 0), while the are computed in the "resolution encoding" (version 0), while the
second section addresses the "uncertainty encoding" (version 1). second section addresses the "uncertainty encoding" (version 1).
A.1.1.1. Resolution Encoding A.1.1.1. Resolution Encoding
Given a number of resolution bits (i.e., the value of a resolution Given a number of resolution bits (i.e., the value of a resolution
field), if all bits beyond those bits are set to zero, this gives the field), if all bits beyond those bits are set to zero, this gives the
lowest possible value. The highest possible value can be found lowest possible value. The highest possible value can be found
setting all bits to one. setting all bits to one.
skipping to change at page 22, line 8 skipping to change at page 22, line 8
Altitude uncertainty (AltUnc in version 1) uses the same process with Altitude uncertainty (AltUnc in version 1) uses the same process with
different constants: different constants:
distance = 2 ^ (21 - uncertainty) distance = 2 ^ (21 - uncertainty)
lowvalue = value - distance lowvalue = value - distance
Appendix B. Calculations of Resolution Appendix B. Calculations of Resolution
The following examples for two different locations demonstrate how The following examples for two different locations demonstrate how
the Resolution values for Latitude, Longitude, and Altitude (used the Resolution values for Latitude, Longitude, and Altitude (used in
in the version 0 DHCPv4 option) can be used. In both examples, the version 0 DHCPv4 option) can be calculated. In both examples,
the geo-location values were derived from maps using the WGS84 the geo-location values were derived from maps using the WGS84 map
map datum, therefore in these examples, the Datum field would datum, therefore in these examples, the Datum field would have a
have a value = 1 (00000001, or 0x01). value = 1 (00000001, or 0x01).
B.1. Location Configuration Information of "White House" (Example 1) B.1. Location Configuration Information of "White House" (Example 1)
The grounds of the White House in Washington D.C. (1600 Pennsylvania
Ave. NW, Washington, DC 20006) can be found between 38.895375 and
38.898653 degrees North and 77.037911 and 77.035116 degrees West. In
this example, we assume that we are standing on the sidewalk on the
north side of the White House, between driveways. Since we are not
inside a structure, we assume an Altitude value of 15 meters,
interpolated from the US Geological survey map, Washington Washington
West quadrangle.
The address was NOT picked for any political reason and can easily be The address was NOT picked for any political reason and can easily be
found on the Internet or mapping software, but was picked as an found on the Internet or mapping software, but was picked as an
easily identifiable location on our planet. easily identifiable location on our planet.
Postal Address: In this example, the requirement of emergency responders in North
White House America via their NENA Model Legislation [NENA] could be met by a
1600 Pennsylvania Ave. NW LatUnc value of 21 and a LongUnc value of 20. This would yield a
Washington, DC 20006 geo-location that is Latitude 38.8984375 north to Latitude 38.8988616
north and Longitude -77.0371094 to Longitude -77.0375977. This is an
Standing on the sidewalk, north side of White House, between area of approximately 89 feet by 75 feet or 6669 square feet, which
driveways. is very close to the 7000 square feet requested by NENA. In this
example, a service provider could enforce that a device send a
Latitude 38.89868 degrees North (or +38.89868 degrees) Location Configuration Information with this minimum amount of
Using 2s complement, 34 bit fixed point, 25 bit fraction resolution for this particular location when calling emergency
Latitude = 0x04dcc1fc8, services.
Latitude = 0001001101110011000001111111001000
Longitude 77.03723 degrees West (or -77.03723 degrees)
Using 2s complement, 34 bit fixed point, 25 bit fraction
Longitude = 0xf65ecf031,
Longitude = 1101100101111011001111000000110001
Altitude 15
In this example, we are not inside a structure, therefore we will An approximate representation of this location might be provided using
assume an Altitude value of 15 meters, interpolated from the US the version 0 encoding as follows:
Geological survey map, Washington West quadrangle.
AltUnc = 30, 0x1e, 011110 0 1 2 3
AT = 1, 0x01, 000001 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
Altitude = 15, 0x0F00, 00000000000000000000000001111100000000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code (123) | OptLen (16) | LatUnc | Latitude .
|0 1 1 1 1 0 1 1|0 0 0 1 0 0 0 0|0 1 0 0 1 0|0 0 0 1 0 0 1 1 0 1.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Latitude (cont'd) | LongUnc | .
.1 1 0 0 1 0 1 1 1 0 0 1 1 0 0 0 0 1 1 0 0 0 1 1|0 1 0 0 0 1|1 1.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Longitude (cont'd) |
.0 1 1 0 0 1 0 1 1 1 1 0 1 1 0 1 0 1 0 0 0 0 1 0 1 1 0 0 0 1 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AType | AltUnc | Altitude .
|0 0 0 1|0 1 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Alt (cont'd) |Ver| Res |Datum|
.0 0 0 0 0 0 0 0|0 0|0 0 0|0 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If: LatUnc is expressed as value 2 (0x02 or 000010) and LongUnc is In hexadecimal, this is 7B10484D CB986347 65ED42C4 1440000F 0001.
expressed as value 2 (0x02 or 000010), then it would describe a
geo-location region that is north of the equator and extends from
-1 degree (west of the meridian) to -128 degrees. This would
include the area from approximately 600km south of Saltpond,
Ghana, due north to the North Pole and approximately 4400km
south-southwest of Los Angeles, CA due north to the North Pole.
This would cover an area of about one-sixth of the globe,
approximately 20 million square nautical miles (nm).
If: LatUnc is expressed as value 3 (0x03 or 000011) and LongUnc is Decoding Location Configuration Information with Resolution
expressed as value 3 (0x03 or 000011), then it would describe a
geo-location area that is north from the equator to 63 degrees
north, and -65 degrees to -128 degrees Longitude. This area
includes south of a line from Anchorage, AL to eastern Nunavut,
CN, and from the Amazons of northern Brazil to approximately
4400km south-southwest of Los Angeles, CA. This area would
include North America, Central America, and parts of Venezuela
and Columbia, except portions of Alaska and northern and eastern
Canada, approximately 10 million square nm.
If: LatUnc is expressed as value 5 (0x05 or 000101) and LongUnc is Decoding this option gives a latitude of 38.897647 (to 7 decimal
expressed as value 5 (0x05 or 000101), then it would describe a places) with 18 bits of resolution; a longitude of -77.0366000 with
geo-location area that is Latitude 32 north of the equator to 17 bits of resolution; an altitude type of meters with a value of 15
Latitude 48 and extends from -64 degrees to -80 degrees and 17 bits of resolution; version 0 (resolution) and the WGS84
Longitude. This is approximately an east-west boundary of a time datum.
zone, an area of approximately 700,000 square nm.
If: LatUnc is expressed as value 9 (0x09 or 001001) and LongUnc is For the latitude value, 18 bits of resolution allow for values in the
expressed as value 9 (0x09 or 001001), which includes all the range from 38.8964844 to 38.8984375. For the longitude value, 17
integer bits, then it would describe a geo-location area that is bits of resolution allow for values in the range from -77.0390625 to
Latitude 38 north of the equator to Latitude 39 and extends from -77.0351563. Having 17 bits of resolution in the altitude allows for
-77 degrees to -78 degrees Longitude. This is an area of values in the range from 0 to 32 meters.
approximately 9600 square km (111.3km x 86.5km).
If: LatUnc is expressed as value 18 (0x12 or 010010) and LongUnc is GML Representation of Decoded Location Configuration Information
expressed as value 18 (0x12 or 010010), then it would describe a
geo-location area that is Latitude 38.8984375 north to Latitude
38.9003906 and extends from -77.0390625 degrees to -77.0371094
degrees Longitude. This is an area of approximately 36,600
square meters (169m x 217m).
If: LatUnc is expressed as value 22 (0x16 or 010110) and LongUnc is The following GML shows the value decoded in the previous example as
expressed as value 22 (0x16 or 010110), then it would describe a a point in a three dimensional CRS:
geo-location area that is Latitude 38.896816 north to Latitude
38.8985596 and extends from -77.0372314 degrees to -77.0371094
degrees Longitude. This is an area of approximately 143 square
meters (10.5m x 13.6m).
If: LatUnc is expressed as value 28 (0x1c or 011100) and LongUnc is <gml:Point srsName="urn:ogc:def:crs:EPSG::4979"
expressed as value 28 (0x1c or 011100), then it would describe a xmlns:gml="http://www.opengis.net/gml";>
geo-location area that is Latitude 38.8986797 north to Latitude <gml:pos>38.897647 -77.0366 15</gml:pos>
38.8986816 and extends from -77.0372314 degrees to -77.0372296 </gml:Point>
degrees Longitude. This is an area of approximately 339 square
centimeters (20.9cm x 16.23cm).
If: LatUnc is expressed as value 30 (0x1e or 011110) and LongUnc is This representation ignores the values included in the resolution
expressed as value 30 (0x1e or 011110), then it would describe a parameters. If resolution values are provided, a rectangular prism
geo-location area that is Latitude 38.8986797 north to Latitude can be used to represent the location.
38.8986802 and extends from -77.0372300 degrees to -77.0372296
degrees Longitude. This is an area of approximately 19.5 square
centimeters (50mm x 39mm).
If: LatUnc is expressed as value 34 (0x22 or 100010) and LongUnc is The following example uses all of the decoded information from the
expressed as value 34 (0x22 or 100010), then it would describe a previous example:
geo-location area that is Latitude 38.8986800 north to Latitude
38.8986802 and extends from -77.0372300 degrees to -77.0372296
degrees Longitude. This is an area of approximately 7.5 square
millimeters (3.11mm x 2.42mm).
In the (White House) example, the requirement of emergency responders <gs:Prism srsName="urn:ogc:def:crs:EPSG::4979"
in North America via their NENA Model Legislation [NENA] could be met xmlns:gs="http://www.opengis.net/pidflo/1.0";
by a LatUnc value of 21 and a LongUnc value of 20. This would yield xmlns:gml="http://www.opengis.net/gml";>
a geo-location that is Latitude 38.8984375 north to Latitude <gs:base>
38.8988616 north and Longitude -77.0371094 to Longitude -77.0375977. <gml:Polygon>
This is an area of approximately 89 feet by 75 feet or 6669 square <gml:exterior>
feet, which is very close to the 7000 square feet requested by NENA. <gml:LinearRing>
In this example, a service provider could enforce that a device send <gml:posList>
a Location Configuration Information with this minimum amount of 38.8964844 -77.0390625 0
resolution for this particular location when calling emergency 38.8964844 -77.0351563 0
services. 38.8984375 -77.0351563 0
38.8984375 -77.0390625 0
38.8964844 -77.0390625 0
</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</gs:base>
<gs:height uom="urn:ogc:def:uom:EPSG::9001">
32
</gs:height>
</gs:Prism>
B.2. Location Configuration Information of "Sears Tower" (Example 2) B.2. Location Configuration Information of "Sears Tower" (Example 2)
Postal Address: Postal Address:
Sears Tower Sears Tower
103rd Floor 103rd Floor
233 S. Wacker Dr. 233 S. Wacker Dr.
Chicago, IL 60606 Chicago, IL 60606
Viewing the Chicago area from the Observation Deck of the Sears Viewing the Chicago area from the Observation Deck of the Sears
skipping to change at page 27, line 41 skipping to change at page 27, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Latitude (cont'd) | LongUnc | . . Latitude (cont'd) | LongUnc | .
.0 1 0 0 1 0 0 1 0 0 1 1 0 1 1 0 0 0 0 0 1 1 0 1|0 1 0 0 1 0|0 1. .0 1 0 0 1 0 0 1 0 0 1 1 0 1 1 0 0 0 0 0 1 1 0 1|0 1 0 0 1 0|0 1.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Longitude (cont'd) | . Longitude (cont'd) |
.0 0 1 0 1 1 1 0 0 1 1 0 1 1 1 0 0 0 1 0 1 1 1 0 1 1 0 0 0 0 1 1| .0 0 1 0 1 1 1 0 0 1 1 0 1 1 1 0 0 0 1 0 1 1 1 0 1 1 0 0 0 0 1 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AType | AltUnc | Altitude . | AType | AltUnc | Altitude .
|0 0 0 1|0 0 1 1 1 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1. |0 0 0 1|0 0 1 1 1 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Alt (cont'd) | Datum | . Alt (cont'd) |Ver| Res |Datum|
.1 0 1 1 0 0 1 1|0 1 0 0 0 0 0 1| .1 0 1 1 0 0 1 1|0 1|0 0 0|0 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In hexadecimal, this is 7B104BBC 49360D49 2E6E2EC3 13C00021 B341. In hexadecimal, this is 7B104BBC 49360D49 2E6E2EC3 13C00021 B341.
The DHCPv6 form only differs in the code and option length portion. The DHCPv6 form only differs in the code and option length portion.
C.1.2. Decoding a Location from DHCP Geodetic Form C.1.2. Decoding a Location from DHCP Geodetic Form
If receiving the binary form created in the previous section, this If receiving the binary form created in the previous section, this
section describes how that would be interpreted. The result is then section describes how that would be interpreted. The result is then
represented as a GML object, as defined in [GeoShape]. represented as a GML object, as defined in [GeoShape].
skipping to change at page 30, line 9 skipping to change at page 30, line 9
Note that this representation is only appropriate if the uncertainty Note that this representation is only appropriate if the uncertainty
is sufficiently small. [GeoShape] recommends that distances between is sufficiently small. [GeoShape] recommends that distances between
polygon vertices be kept short. A GML representation like this one polygon vertices be kept short. A GML representation like this one
is only appropriate where uncertainty is less than 1 degree (an is only appropriate where uncertainty is less than 1 degree (an
encoded value of 9 or greater). encoded value of 9 or greater).
Appendix D. Changes from RFC 3825 Appendix D. Changes from RFC 3825
Technical changes: Technical changes:
-09: Updated and shortened Appendix B.1.
-08: Added Appendix A on GML mapping. -08: Added Appendix A on GML mapping.
-06: Added recommendation on link layer confidentiality to the -06: Added recommendation on link layer confidentiality to the
Security Considerations section. Security Considerations section.
-05: Added version field to DHCPv6 option. -05: Added version field to DHCPv6 option.
-04: Added Appendix C providing an example relating to -04: Added Appendix C providing an example relating to
uncertainty. Added Section 2.3.1 on Latitude and Longitude uncertainty. Added Section 2.3.1 on Latitude and Longitude
resolution and Section 2.4.4 on Altitude resolution. resolution and Section 2.4.4 on Altitude resolution.
Added definition of Resolution to Section 1.2. Added definition of Resolution to Section 1.2.
-03: Clarified potential behavior of version 0 clients receiving -03: Clarified potential behavior of version 0 clients receiving
a version 1 option and added recommendations for clients and a version 1 option and added recommendations for clients and
 End of changes. 22 change blocks. 
110 lines changed or deleted 100 lines changed or added

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