mornin' paul, >>> Also, is the word "Geofeed" case sensitive? >> >> "MUST be as in this example." do we need ABNF the ex compiler hacker >> asks? i can add enough syntactic sugar to give you a diabetic coma :) > > I don't think you need abnf. But some text specifying it is/isn't case > sensitive would help. It may not be necessary if there is a strong > established policy for handling case in RPSL. But even if there is it > might not be applicable to processing the text of remarks.
will clarify. how about The format of the inetnum: geofeed attribute MUST be as in this example, "remarks: Geofeed ", where the token "Geofeed" is case sensitive, followed by a URL which will vary, but MUST refer only to a single [RFC8805] geofeed file. >> you mean you don't read decoded certs for breakfast? > No I don't. nor do i. but i trust russ :) >>> I'm not sure how to feel about using *awesome* in the >>> Introduction. It seems unusually informal for a standards >>> document. But in a way I also find it refreshing. >> >> so do we. as i said to the kind opsdir reviewer, we'll see how far >> up the chain a sense of perspective still exists. > > It will be interesting to see. we tend to take ourselves too seriously. but i hope there is life in us yet. >>> IdNits reports a number of things worth looking into. Notably the >>> downrefs >> >> the downrefs are only informational. they are the best doccos on >> INETNUM today. sigh. > > But the references are included in the Normative References > section. If you put them in an Informative References section then I > think IdNits will be happy. something weird going on here. in the -06 on datatrucker, i see the INETNUM and INET6NUM refs under informative. so we are either talking about different downrefs or one or both of us needs new glasses. clue bat, please. thanks! randy _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www.ietf.org/mailman/listinfo/gen-art
