For more information on OTP, please refer to IETF RFC 2289 (see Resources).
关于OTP的更多信息，请参见IETF RFC 2289(参见参考资料)。
Details on how this attack works are explained in IETF RFC 2965, if you're curious (see Resources for a link).
如果您对此关心，可以参考IETF RFC 2965，可以得到关于这种攻击的详细说明(在参考资料中有相关链接)。
As of today, the only security mechanism supported by most of the GSS-API offerings is the popular symmetric key-based mechanism called Kerberos [IETF RFC-1964].
到目前为止，大部分GSS - API产品所支持的惟一的安全机制就是名为kerberos [ietf RFC - 1964]的流行的基于对称密钥的机制。
The prime reason for this increased support is that the NFS V4 [IETF RFC-3530] has mandated the use of SPKM and LIPKEY security mechanisms for its security module.
这种支持增长的主要原因是，NFSV4 [IETF RFC-3530]强制规定其安全模块使用SPKM和LIPKEY 安全机制。
As mentioned in IETF RFC 2847, LIPKEY is a low infrastructure based GSS-API security mechanism which maps to a typical TLS (Transport Layer security) deployment scenario.
正如在IETF RFC 2847中所提到的，LIPKEY是一种基于GSS - API安全机制的低基础设施，该安全机制对应于典型的TLS (TransportLayerSecurity)部署场景。
RFC 4627: Learn more about the JSON Format in a detailed IETF memo.
RFC 4627：在这个详细的IETF备忘录中了解JSONFormat的更多信息。
You could even read RFC 4287, the IETF specification for the Atom format (see Resources).
您甚至可以阅读RFC 4287，这是用于atom格式的IETF规范(请参阅参考资料)。
You could even read RFC 4287, the IETF specification for the Atom format (see Resources).
您甚至可以阅读RFC 4287，这是用于atom格式的IETF规范(请参阅参考资料)。
应用推荐