| section 3.1, bullet 4 - s/notaion/notation/ Bullet 4 of this list looks confused * Date and time fields MUST be converted to 64-bit NTP Timestamp Format [RFC5905]. thats a binary value, 32 bits of seconds since epoch and 32 bitss of fractions - right? Does this also mean that the Era is 1 January 1900? * AS numbers MUST be converted to ASPLAIN syntax [RFC5396]. hang on - thats ascii - why is the time field binary and this field ascii? * IPv6 addresses must be canonicalized as defined in [RFC5952]. this is also ascii * IPv4 addresses MUST be converted to a 32-bit representation (e.g., Unix's inet_aton()). inet_aton returns a binary struct - which is NOT ascii. * All IP prefixes (IPv4 and IPv6) MUST be represented in CIDR notaion [RFC4632]. so I think you are referring to a range of IP addresses. I assume that this means that at times this will be a list of addresses (i.e. the range of addresses 10.0.0.1 - 10.0.0.2 is 10.0.0.1/32 and 10.0.0.2/32) Are you wanting a cononical CIDR form? (i.e. should the pair of prefixes 10.0.0.0/24 and 10.0.1.0/24 be represented as 10.0.0.0/23?) Other RPKI specs (e.g. RFC6487) referenced the canonical representation of a set of addresses as defined in RFC3779. I assume you had a good reason not to use the same approach So why are some items in this list ascii and some binary? Would it make more sense to use either all binary or all ascii here? regards, Geoff On 18 Jun 2015, at 7:14 pm, Chris Morrow <[email protected]> wrote: |
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
