RFC 3825

Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information

📅 published July 2004, from ietf

RFC 3825 🎀 Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information

okay so here's the title block, bestie 💖

  • Network Working Group 🌸
  • Authors: J. Polk, J. Schnizlein, and M. Linsner, all from Cisco Systems 👑
  • Category: Standards Track ✨
  • Date: July 2004 📅
  • It doesn't obsolete or update any other RFC, so nothing to chase down 🦋

Status of this Memo 💅

this one is an Internet standards track protocol for the Internet community, and it's literally asking people for discussion and suggestions for improvements 🫶 for the current standardization state and status, check the "Internet Official Protocol Standards" (STD 1). distribution of this memo is unlimited, so share it with everyone 🌈

Copyright (C) The Internet Society (2004).

Abstract ✨

okay so this doc specifies a Dynamic Host Configuration Protocol Option for the coordinate-based geographic location of the client 📍 the Location Configuration Information (LCI) has latitude, longitude, and altitude, and each one comes with its own resolution indicator 🔥 the reference datum for these values is included too, so everyone's on the same map 🗺️

Table of Contents 🦋

1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
    1.1.  Conventions  . . . . . . . . . . . . . . . . . . . . . .  3
    1.2.  Motivation . . . . . . . . . . . . . . . . . . . . . . .  3
    1.3.  Rationale  . . . . . . . . . . . . . . . . . . . . . . .  4
2.  Location Configuration Information (LCI) Elements. . . . . . .  4
    2.1.  Elements of the Location Configuration Information . . .  5
3.  Security Considerations. . . . . . . . . . . . . . . . . . . . .  8
4.  IANA Considerations. . . . . . . . . . . . . . . . . . . . . .  8
5.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
Appendix Calculations of Imprecision possible with the DHC LCI . . 10
    A.1.  LCI of "White House" (Example 1) . . . . . . . . . . . . 10
    A.2.  LCI of "Sears Tower" (Example 2) . . . . . . . . . . . . 12
6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
    6.1.  Normative References . . . . . . . . . . . . . . . . . . 13
    6.2.  Informational References . . . . . . . . . . . . . . . . 14
7.  Author Information . . . . . . . . . . . . . . . . . . . . . . 14
8.  Full Copyright Statement . . . . . . . . . . . . . . . . . . . 15

1. Introduction 🧚

okay so this document specifies a Dynamic Host Configuration Protocol [1] Option for the coordinate-based geographic location of the client, and the server is the one who provides it 💜

the DHCP server is assumed to have worked out the location from the Circuit-ID Relay Agent Information Option (RAIO), which is defined as SubOpt 1 in [2] 🔌 to turn the circuit (that's the switch port identifier) into a location, the server is assumed to have access to a service that maps circuit-ID to the spot in the building where the circuit for that port ends, like the location of the wall jack 🧱

the big feature here is that once the relevant DHC exchanges are done, the location info gets stored on the end device, not somewhere else where getting it back could be a nightmare in practice 😭✨

another iconic thing about this LCI is that it includes a resolution parameter for each dimension of location 💅 this resolution parameter doesn't have to apply to all dimensions equally, so there's a resolution value for each of the 3 location elements 🌈

resolution does NOT define Geographic Privacy policy. just saying 🙈

the resulting location info using this resolution method is a small, fixed-length Configuration Information, which means it can easily ride along in protocols like DHCP that have limited packet size 🍓 this LCI is only 18 bytes long, periodt 🎀

finally, the appendix of this document has some arithmetic examples showing how different resolution values change the La/Lo/Alt 🧮

1.1. Conventions used in this document 🌸

the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [3] 📖

1.2. Motivation 💖

okay so as applications like IP Telephony replace conventional telephony, users expect the same (or better) level of service from the new tech 📞 one thing conventional telephony offers that is missing, in any standardized way, within IP Telephony is that a user gets automatically located by emergency responders, in a timely fashion, when they summon help (like dialing 911 in North America, for example) 🚨

the thing is, unless strict administrative rules are followed, the mobility of a wired Ethernet device within a campus means an emergency responder has zero chance of finding it quickly 😭 users don't want to give up the mobility IP Telephony offers, though 🦋 telling the host device its geo-location at host configuration time lets the device use that info to tell others where it is, if the user and/or application wants that 🫶

the goal of this option is to let a wired Ethernet host get its location, which it could hand to an emergency responder, as one example 🚑

wireless hosts can use this option to learn the location of the radio access point they were on during host configuration 📡 but they'd need some more exotic mechanisms, maybe GPS, or maybe a future DHCP option that includes a list of geo-locations like the one defined here, containing the locations of radio access points close to the client 🛰️

1.3. Rationale 🧠

within the LCI described here, Latitude and Longitude are represented in fixed-point 2s-complement binary degrees 🔢 why? for the economy of a smaller option size compared to a string encoding of digits in [7] 💅 the integer parts of these fields are 9 bits long to fit +/- 180 degrees 🌍 the fractional part is 25 bits long, which is better than the precision of 7 decimal digits 🔥 each field is 40 bits long, and 34 of those are the sum of the integer (9) and fractional (25) bits, plus 6 bits of resolution 🎀

altitude is determined by the Altitude Type (AT) indicated by the AT field, which is 4 bits long 🦋 two Altitude Types are defined here: meters (code=1) and floors (code=2), and both are 2s-complement fixed-point with 22 bits of integer part and 8 bits of fractional part 🪜 additional Altitude Types MAY be assigned by IANA 🧚 the "floors" Altitude Type exists because altitude in meters may not be known inside a building, and a floor indication may be more useful 🏢

GPS systems today can use WGS84 for horizontal and vertical datums 🛰️ [6] defines WGS84 as a three-dimensional datum 💜 for other datum values that don't include a vertical component, both the horizontal and vertical datum of reference will be specified in the IANA record 📝

each of these 3 elements starts with a 6-bit accuracy sub-field that says how many bits of resolution it has 🎯 this resolution sub-field lets you easily adjust how precise a reported location is 🌸 contents beyond the claimed resolution MAY be randomized to obscure any greater precision that might be available 🙈 (this is the privacy-slay part, iykyk 🫣)

2. DHC Location Configuration Information Elements 🌈

okay so DHCP is a binary protocol, and LCI using protocols are likely to be text based 📝 since most coordinate systems translate easily between binary-based and text-based location output (even emergency services within the US), translation/conversion is a non-issue with DHCP's binary format 💖

this binary format is a fortunate benefit when you want to make a true/correct location coordinate imprecise 🫶 it also gives you the capability to make this binary representation deterministically imprecise ✨

the LCI format looks like this 👇

  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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |   Code 123    |      16       |   LaRes   |     Latitude      +
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                Latitude (cont'd)              |    LoRes  |   +
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                             Longitude                         |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |   AT  |   AltRes  |                Altitude                   |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  Alt (cont'd) |     Datum     |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

🫶 part 2 is coming next, so stay tuned 💅

2.1. Elements of the Location Configuration Information ✨

okay bestie, let's go through the fields that make up the LCI 🎀 Here's the header stuff first:

  • Code 123: the code for this DHCP option 💖
  • 16: the length of this option, which is 16 bytes 📏

LaRes is the latitude resolution 🌸. It's 6 bits that tell you how many valid bits are in the fixed-point value of Latitude. This number is how many high-order Latitude bits should be considered valid. Any bits to the right of that limit should not be considered valid and might be purposely false, or zeroed by the sender 🙈

The examples in the appendix show that a smaller value in the resolution field makes the area where the device is located bigger. Iykyk 😭

LaRes doesn't define any Geographic Privacy policy, so that's a whole separate convo 🔒

Values above decimal 34 are undefined and reserved 🚫

Latitude is a 34 bit fixed point value made of 9 bits of integer and 25 bits of fraction 🧁. Latitude SHOULD be normalized to within +/- 90 degrees. Positive numbers are north of the equator and negative numbers are south of the equator 🌍

A LaRes value of 2 means a precision of no greater than 1/6th that of the globe (see the first example in the appendix) ✨. A LaRes value of 34 means a precision of about 3.11 mm in Latitude at the equator. Ate 💅

LoRes is the longitude resolution 🦋. Same vibe as LaRes: 6 bits that count the valid bits in the fixed-point value of Longitude. This is the number of high-order Longitude bits that should be considered valid. Any bits entered to the right of this limit should not be considered valid and might be purposely false, or zeroed by the sender 🫶

LoRes doesn't define any Geographic Privacy policy either 🔒

Values above decimal 34 are undefined and reserved 🚫

Longitude is another 34 bit fixed point value, with 9 bits of integer and 25 bits of fraction 🧁. Longitude SHOULD be normalized to within +/- 180 degrees. Positive values are East of the prime meridian, and negative (2s complement) numbers are West of the prime meridian 🧭

A LoRes value of 2 indicates a precision of no greater than 1/6th that of the globe (see the first example of the appendix) 🌸. A LoRes value of 34 indicates a precision of about 2.42 mm in longitude (at the equator). Lines of longitude meet at the poles, so the distance gets smaller, which means better precision, for locations away from the equator 👑

Altitude is a 30 bit value, and the AT field tells you how to read it 📈

AltRes is the altitude resolution 💜. It's 6 bits that count the valid bits in the altitude. Values above 30 (decimal) are undefined and reserved 🚫

AltRes doesn't define any Geographic Privacy policy 🔒

AT is the Altitude Type for the altitude 🌈. These are the codes that are defined:

1: Meters - in 2s-complement fixed-point 22-bit integer part with 8-
           bit fraction

2: Floors - in 2s-complement fixed-point 22-bit integer part with
           8-bit fraction

If AT = 1, an AltRes value of 0.0 would mean the altitude is unknown 🤷‍♀️. The most precise Altitude would have an AltRes value of 30. Plenty of other AltRes values would hide any variation caused by vertical datum differences, so be careful 🙈

AT = 2 is for Floors, and it's a much more useful way to show altitude inside buildings where floor-to-floor heights are all different 🏢. An altitude coded as AT = 2, AltRes = 30, and Altitude = 0.0 still makes sense even outside a building, and it means ground level at the given latitude and longitude 🌱. Inside a building, 0.0 means the floor that goes with ground level at the main entrance. This document only defines a number, so you have to get to the actual number by counting floors up or down from the floor that's been defined as 0.0 🧗‍♀️

The values for this AT are only of local significance 📍. Buildings and floors can differ because nobody controls them all in one place, so the building operator and the people who'll use the data have to agree on the values that describe each building 🤝. Trying to standardize this kind of thing is beyond the scope of this document, so don't even go there 🙅‍♀️

Sub-floors can be shown with non-integer values. For example, a mezzanine between floor 1 and floor 2 could be represented as a value = 1.1. And (2) mezzanines between floor 4 and floor 5 could be represented as values = 4.1 and 4.2 respectively 🪜

Floors below ground level could be shown with negative values 🕳️

Bigger values mean floors that are higher up (higher in altitude) than floors with lower values ⬆️

The AltRes field SHOULD be set to maximum precision when AT = 2 (floors) and a floor value is included in the DHCP Reply, or when AT = 0 is used to show that the floor isn't known 💅

Any additional LCI Altitude Types(s) to be defined for use via this DHC Option MUST be done through a Standards Track RFC. No shortcuts here, babe 📜

Datum is the Map Datum used for the coordinates given in this Option 🗺️

The datum has to include both a horizontal and a vertical reference. Since the WGS 84 reference datum is three-dimensional, it covers both. For any other datum parameters, the datum codepoint must specify both a horizontal datum and a vertical datum reference 🧠

The Datum byte has 256 possibilities, and 3 of them have been registered with IANA by this document (all derived from the specification in [5]) 🦄:

1: WGS 84  (Geographical 3D) - World Geodesic System 1984, CRS
           Code 4327, Prime Meridian Name: Greenwich

2: NAD83 - North American Datum 1983, CRS Code 4269, Prime
           Meridian Name: Greenwich; The associated vertical datum
           is the North American Vertical Datum of 1988 (NAVD88)

           This datum pair is to be used when referencing
           locations on land, not near tidal water (which would
           use Datum = 3 below)

3: NAD83 - North American Datum 1983, CRS Code 4269, Prime
           Meridian Name: Greenwich; The associated vertical datum
           is Mean Lower Low Water (MLLW)

           This datum pair is to be used when referencing
           locations on water/sea/ocean

Any additional LCI datum(s) to be defined for use via this DHC Option MUST be done through a Standards Track RFC 🎀

3. Security Considerations 🔐

Where critical decisions might be based on the value of this GeoConf option, DHCP authentication in [4] SHOULD be used to protect the integrity of the DHCP options. This is not optional vibes, this is serious 🚨

Since there is no privacy protection for DHCP messages, an eavesdropper who can monitor the link between the DHCP server and the requesting client can discover this LCI 👀. Yikes, it's giving "anyone on the wire can see where you are" 💀

To cut down on the unintended exposure of location information, the LCI option SHOULD be returned by DHCP servers only when the DHCP client has included this option in its 'parameter request list' (section 3.5 [1]) 🙈🫶

When implementing a DHC server that will serve clients across an uncontrolled network, one should consider the potential security risks 🕸️ Please think about this before you ship, periodt 😤

4. IANA Considerations 📋

IANA has assigned a DHCP option code of 123 for the GeoConf option defined in this document 🎀

The GeoConf Option defines two fields that IANA keeps a registry for: the Altitude (AT) field (see Section 2) and the Datum field (see Section 2). The datum indicator MUST include specification of both horizontal and vertical datum 🗂️. New values for the Altitude (AT) field are assigned through "Standards Action" [RFC 2434]. The initial values of the Altitude registry look like this:

AT = 1  meters of Altitude defined by the vertical datum specified.

AT = 2  building Floors of Altitude.

Datum = 1 denotes the vertical datum WGS 84 as defined by the EPSG as
        their CRS Code 4327; CRS Code 4327 also specifies WGS 84 as
        the vertical datum

Datum = 2 denotes the vertical datum NAD83 as defined by the EPSG as
        their CRS Code 4269; North American Vertical Datum of 1988
        (NAVD88) is the associated vertical datum for NAD83

Datum = 3 denotes the vertical datum NAD83 as defined by the EPSG as
        their CRS Code 4269; Mean Lower Low Water (MLLW) is the
        associated vertical datum for NAD83

Any additional LCI datum(s) to be defined for use via this DHC Option MUST be done through a Standards Track RFC 📜✨

5. Acknowledgements 💌

The authors would like to thank Patrik Falstrom, Ralph Droms, Ted Hardie, Jon Peterson, and Nadine Abbott for their inputs and constructive comments on this document 🫶. They also want to thank Greg Troxel for the education on vertical datums, and Carl Reed too 🌸

Appendix: Calculations of Imprecision Possible with the DHC LCI 🧮

The following examples for two different locations show how the Resolution values for Latitude, Longitude, and Altitude can be used 🗺️✨. In both examples the geo-location values were derived from maps using the WGS84 map datum, so the datum field in these examples would have a value = 1 (00000001, or 0x01) 💖

A.1. Location Configuration Information of "White House" (Example 1) 🏠✨

okay so the address was not picked for any political reason 🙅‍♀️ you can find it on the Internet or in mapping software. It was just picked as an easily identifiable spot on our planet 🌍

Postal Address:
   White House
   1600 Pennsylvania Ave. NW
   Washington, DC 20006

Standing on the sidewalk, north side of White House, between
driveways.
Latitude 38.89868 degrees North (or +38.89868 degrees)
   Using 2s complement, 34 bit fixed point, 25 bit fraction
   Latitude = 0x04dcc1fc8,
   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

we're not inside a structure here, so we assume an altitude of 15 meters, interpolated from the US Geological survey map, Washington West quadrangle 🗺️

AltRes = 30, 0x1e, 011110
AT = 1, 0x01, 000001
Altitude = 15, 0x0F00, 00000000000000000000000001111100000000

now the fun part, the LaRes and LoRes combos and what each one describes 🤩

  • LaRes 2 and LoRes 2 (0x02 or 000010): this is a geo-location region north of the equator, extending from -1 degree (west of the meridian) to -128 degrees. It covers the area from approximately 600km south of Saltpond, Ghana, due north to the North Pole, and from approximately 4400km south-southwest of Los Angeles, CA, due north to the North Pole. That's about one-sixth of the globe, roughly 20 million square nautical miles (nm) 🌐
  • LaRes 3 and LoRes 3 (0x03 or 000011): this one goes north from the equator to 63 degrees north, and from -65 degrees to -128 degrees longitude. It sits south of a line from Anchorage, AL to eastern Nunavut, CN, and runs from the Amazons of northern Brazil to approximately 4400km south-southwest of Los Angeles, CA. It includes North America, Central America, and parts of Venezuela and Columbia, except portions of Alaska and northern and eastern Canada, about 10 million square nm 🌎
  • LaRes 5 and LoRes 5 (0x05 or 000101): a geo-location area from latitude 32 north of the equator to latitude 48, extending from -64 degrees to -80 degrees longitude. It's roughly an east-west boundary of a time zone, about 700,000 square nm ⏰
  • LaRes 9 and LoRes 9 (0x09 or 001001, which includes all the integer bits): this covers latitude 38 north of the equator to latitude 39, and -77 degrees to -78 degrees longitude. That's about 9600 square km (111.3km x 86.5km) 📐
  • LaRes 18 and LoRes 18 (0x12 or 010010): latitude 38.8984375 north to latitude 38.9003906, and -77.0390625 degrees to -77.0371094 degrees longitude. That's about 36,600 square meters (169m x 217m) 🏛️
  • LaRes 22 and LoRes 22 (0x16 or 010110): latitude 38.896816 north to latitude 38.8985596, and -77.0372314 degrees to -77.0371094 degrees longitude. That's about 143 square meters (10.5m x 13.6m) 🏠
  • LaRes 28 and LoRes 28 (0x1c or 011100): latitude 38.8986797 north to latitude 38.8986816, and -77.0372314 degrees to -77.0372296 degrees longitude. That's about 339 square centimeters (20.9cm x 16.23cm) 🔍
  • LaRes 30 and LoRes 30 (0x1e or 011110): latitude 38.8986797 north to latitude 38.8986802, and -77.0372300 degrees to -77.0372296 degrees longitude. That's about 19.5 square centimeters (50mm x 39mm) 🔬
  • LaRes 34 and LoRes 34 (0x22 or 100010): latitude 38.8986800 north to latitude 38.8986802, and -77.0372300 degrees to -77.0372296 degrees longitude. That's about 7.5 square millimeters (3.11mm x 2.42mm) 🤏

okay and here's the bit that really matters 🚨 in the White House example, the emergency responder requirement in North America via their NENA Model Legislation [8] could be met by a LaRes value of 21 and a LoRes value of 20. That yields a geo-location from latitude 38.8984375 north to latitude 38.8988616 north, and longitude -77.0371094 to longitude -77.0375977. That's about 89 feet by 75 feet, or 6669 square feet, which is super close to the 7000 square feet NENA asked for 🚑 in this example, a service provider could enforce that a device sends a Location Configuration Information with this minimum amount of resolution for this particular location when calling emergency services 📞

A.2. Location Configuration Information of "Sears Tower" (Example 2) 🏙️

Postal Address:
   Sears Tower
   103rd Floor
   233 S. Wacker Dr.
   Chicago, IL  60606

picture this: we're viewing the Chicago area from the Observation Deck of the Sears Tower 🌆

Latitude 41.87884 degrees North (or +41.87884 degrees)
Using 2s complement, 34 bit fixed point, 25 bit fraction
Latitude = 0x053c1f751,
Latitude = 0001010011110000011111011101010001
Longitude 87.63602 degrees West (or -87.63602 degrees)
Using 2s complement, 34 bit fixed point, 25 bit fraction
Longitude = 0xf50ba5b97,
Longitude = 1101010000101110100101101110010111

Altitude 103

this time we're inside a structure, so we assume an altitude of 103 to show the floor we're on 🏢 the Altitude Type value is 2, which means floors. The AltRes field indicates that all bits in the Altitude field are true, since we want to accurately represent the floor of the structure where we are located 💜

AltRes = 30, 0x1e, 011110
AT = 2, 0x02, 000010
Altitude = 103, 0x00006700, 000000000000000110011100000000

for the latitude and longitude accuracy, the best info we had came from a generic mapping service that shows a single geo-loc for all of the Sears Tower. So LaRes is value 18 (0x12 or 010010) and LoRes is value 18 (0x12 or 010010). That describes a geo-location area from latitude 41.8769531 to latitude 41.8789062, and from -87.6367188 degrees to -87.6347657 degrees longitude. That's about 373412 square feet (713.3 ft. x 523.5 ft.) 🦋

6. References

6.1. Normative References

6.2. Informational References

  • [7] Farrell, C., Schulze, M., Pleitner, S. and D. Baldoni, "DNS Encoding of Geographical Location", RFC 1712, November 1994.
  • [8] National Emergency Number Association (NENA) www.nena.org NENA Technical Information Document on Model Legislation Enhanced 911 for Multi-Line Telephone Systems.

7. Author Information 👩‍💻

James M. Polk
Cisco Systems
2200 East President George Bush Turnpike
Richardson, Texas 75082 USA

EMail: jmpolk@cisco.com
John Schnizlein
Cisco Systems
9123 Loughran Road
Fort Washington, MD 20744 USA

EMail: john.schnizlein@cisco.com
Marc Linsner
Cisco Systems
Marco Island, FL 34145 USA

EMail: marc.linsner@cisco.com

Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property 🔐

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document, or the extent to which any license under such rights might or might not be available. It also doesn't represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat, any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.

Acknowledgement 🫶

Funding for the RFC Editor function is currently provided by the Internet Society. thank you, Internet Society, you're iconic 🌈💖

📦 where this page comes from