diff --git a/draft-ymbk-9092update.xml b/draft-ymbk-9092update.xml index ed3bf33..768f6b1 100644 --- a/draft-ymbk-9092update.xml +++ b/draft-ymbk-9092update.xml @@ -8,7 +8,9 @@ - + @@ -79,9 +81,9 @@ This document specifies how to augment the Routing Policy Specification Language inetnum: class to refer specifically to - geofeed data comma-separated values (CSV) files and describes an - optional scheme that uses the Routing Public Key Infrastructure - to authenticate the geofeed data CSV files. + geofeed data files and describes an optional scheme that uses + the Routing Public Key Infrastructure to authenticate the + geofeed datafiles. @@ -105,8 +107,8 @@ This document specifies how to augment the Routing Policy Specification Language (RPSL) inetnum: class to refer specifically to - geofeed data CSV files and how to prudently use them. In all - places inetnum: is used, inet6num: should also be assumed . @@ -119,6 +121,31 @@ An optional utterly awesome but slightly complex means for authenticating geofeed data is also defined. + + This document obsoletes . Changes from + include the following: +
    +
  • + It is no longer assumed that a geofeed file is a CSV, comma + separated value list. +
    • +
  • + RIPE has implemented the geofeed: attribute. +
    • +
  • + Allow, but discourage, an inetnum: to have both a geofeed + remarks: attribute and a geofeed: attribute. +
    • +
  • + Stress that authenticating geofeed data is optional. +
    • +
  • + IP Address Delegation extensions must not use "inherit". +
    • +
+ + +
Requirements Language @@ -207,7 +234,7 @@ While we leave global agreement of RPSL modification to the @@ -219,7 +246,7 @@ Registries MAY, for the interim, provide a mix of @@ -249,13 +276,18 @@ - Any particular inetnum: object MUST have, at + Any particular inetnum: object SHOULD have, at most, one geofeed reference, whether a remarks: or a proper geofeed: attribute when it is implemented. If there is more than one, the geofeed: attribute SHOULD be used. - If a geofeed CSV file describes multiple disjoint ranges of IP + For inetnum:s covering the same address range, or an inetnum: + with both remarks: and geofeed: attributes, a signed geofeed + file SHOULD be preferred over an unsigned file. + + + If a geofeed file describes multiple disjoint ranges of IP address space, there are likely to be geofeed references from multiple inetnum: objects. Files with geofeed references from multiple inetnum: objects are not compatible with the signing @@ -364,8 +396,8 @@ identical to or a subset of A. "Address range" is used here because inetnum: objects and RPKI certificates need not align on Classless Inter-Domain Routing (CIDR) - prefix boundaries, while those of the CSV lines in a geofeed - file do. + prefix boundaries, while those of the lines in a geofeed file + do. As the signer specifies the covered RPKI resources relevant to @@ -627,9 +659,10 @@
IANA Considerations - IANA has registered object identifiers for one content - type in the "SMI Security for S/MIME CMS Content Type - (1.2.840.113549.1.9.16.1)" registry as follows: + The IANA is requested to change the Description of the object + identifier for the content type in the "SMI Security for S/MIME + CMS Content Type (1.2.840.113549.1.9.16.1)" registry to the + following: @@ -643,8 +676,8 @@ - - + +
47id-ct-geofeedCSVwithCRLFRFC 9092id-ct-geofeedwithCRLFthis document
@@ -671,6 +704,7 @@ + @@ -1159,10 +1193,9 @@ following detached CMS signature. , (SECDIR), , , (GENART), , and - . The authors also thank - , the awesome document - shepherd. + Kyzivat"/> (GENART), , , and .