On Jul 29, 2010, at 3:21 PM, Christopher Morrow wrote: > (from Jeff Haas) > The chairs need to petition IANA sooner rather than later to reserve a > table type number for the geo type in the mrt type field.
I thought Jeff was saying that the registries haven't been set up yet and should be. IANA would normally do this when you move the MRT draft to RFC but it might be worth doing sooner. The MRT draft sez: 6. IANA Considerations This section provides guidance to the Internet Assigned Numbers Authority (IANA) regarding registration of values related to the MRT specification, in accordance with BCP 26, RFC 5226 [RFC5226]. There are two name spaces in MRT that require registration: Type Codes and Subtype Codes. [...etc...] By the way Terry asked what kind of type code to ask for. The MRT draft sez: 6.1. Type Codes Type Codes have a range from 0 to 65535, of which 1-64 have been allocated. New Type Codes MUST be allocated starting at 65. Type Codes 65 - 511 are to be assigned by IETF Review. Type Codes 512 - 2047 are assigned based on Specification Required. Type Codes 2048 - 64511 are available on a First Come First Served policy. Type Codes 64512 - 65534 are available for Experimental Use. The Type Code Values of 0 and 65535 are reserved. I can't quite imagine why you'd bother with the hoop-jumping required by IETF Review. If I were you, I'd probably just use an FCFS code point. Numbers is numbers after all, they all work the same. --John _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
