Hi all, The newly provided example appears to comply with RPKI/X.509 standards and is consistent with the new 9092bis text. I thank the authors for their patience.
Small nit: the “Error: Spurious zero bits in bitstring.” line in the dumpasn1 output in Appendix A can be removed, to avoid confusing the reader. I suspect that particular error message is a bug in dumpasn1 rather than in the encoding example. Kind regards, Job On Sun, 24 Sep 2023 at 19:00, <internet-dra...@ietf.org> wrote: > Internet-Draft draft-ietf-opsawg-9092-update-04.txt is now available. It > is a > work item of the Operations and Management Area Working Group (OPSAWG) WG > of > the IETF. > > Title: Finding and Using Geofeed Data > Authors: Randy Bush > Massimo Candela > Warren Kumari > Russ Housley > Name: draft-ietf-opsawg-9092-update-04.txt > Pages: 26 > Dates: 2023-09-23 > > Abstract: > > This document specifies how to augment the Routing Policy > Specification Language inetnum: class to refer specifically to > geofeed data files and describes an optional scheme that uses the > Resource Public Key Infrastructure to authenticate the geofeed > datafiles. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-opsawg-9092-update/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-9092-update-04 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-9092-update-04 > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg >
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
