Hi Randy, Please find below some few minor comments on this update:
(1) As a complement to the discussion in the first para of the Introduction, I would add a note that the source address does not necessary point to the user. You may add a pointer to https://datatracker.ietf.org/doc/html/rfc6269#autoid-14 when issues with geolocation are discussed. (2) Section 1 CURRENT: An optional utterly awesome but slightly complex means for authenticating geofeed data is also defined. You may add a pointer to Section 4 for better clarity. (3) Section 3 CURRENT: "Currently, this has been..." It is good to report what is implemented, but I don't think we need to have them frozen in the spec. Please see RFC7942. (4) Note sure we can mandate by spec how the data can be "consumed". I'm afraid the NEW sentence in the Sec Cons isn't useful. I would at least avoid the use of normative language there. (5) RFC9092 is not normative, as this is obsoleted by this one. (6) I would maintain the OLD title and delete "A Minor Update to" Cheers, Med > -----Message d'origine----- > De : OPSAWG <opsawg-boun...@ietf.org> De la part de Randy Bush > Envoyé : mardi 27 juin 2023 18:53 > À : Ops Area WG <opsawg@ietf.org> > Objet : [OPSAWG] draft-ymbk-opsawg-9092-update-01 > > we have pushed draft-ymbk-opsawg-9092-update-01 > > as the document says > > Changes from [RFC9092] 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". > * If geofeed data are present, ignore geographic location hints > in > other data. > > your read and review would be appreciated. > > randy, for the usual suspects > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.ietf.org%2Fmailman%2Flistinfo%2Fopsawg&data=05%7C01%7Cmohamed. > boucadair%40orange.com%7C7ae90fff2b864c18972008db772eef23%7C90c7a2 > 0af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638234815683182753%7CUnknown% > 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwi > LCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DCsZ7JJXBuSUH96opbUOge9V%2Fvb > e60x6VdrBAEmrMds%3D&reserved=0 ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
