Hi all,
I agree with the concern raised below.
It is likely that securing access would be to pay the fees for every access. I’m not sure this can be fixed by write-up unless we have in mind
something similar to the approach considered in my write-up at:
https://datatracker.ietf.org/doc/draft-ietf-drip-reqs/shepherdwriteup/ =================================================== All normative references are published RFCs, except a reference to an external specification ([F3411-19]).
Note that [F3411-19] is not freely available ($88), but an early version is publicly available at https://raw.githubusercontent.com/opendroneid/specs/master/ OpenDroneID_Bluetooth_0.64.3.pdf. A pointer to this freely available document is also cited in the document. This is clearly called in the draft (see the text right after Figure 2). =================================================== Cheers, Med De : ietf <ietf-bounces@xxxxxxxx> De la part de Salz, Rich
I understand the desire for everything that is defined by the IETF to be built on public freely available resources. I think this goes WAY WAY WAY too far. Can I buy a copy of a standard and require it to be postal mailed to everyone serially? _________________________________________________________________________________________________________________________ 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. |