RFC 3588:Diameter Base Protocol
RFC-Ref

validity


Click on the red underlined text to get to the source

... encounter any code point from 0x00000001 to 0x7fffffff. Byte sequences that do not correspond to the valid encoding of a code point into UTF-8 ...
... diameter" / "radius" / "tacacs+" ) The following are examples of valid Diameter host identities: ...
... Integer32 AVP Base Format. The definition contains a list of valid values and their interpretation and is described in the Diameter application ...
... 1.2.3.0 to 1.2.3.255 will match. The bit width MUST be valid for the IP version and the IP ...
... IP fragment with a fragment offset of one. This is a valid packet, but it only has one use, to try to circumvent firewalls. ...


... query and the domain name in the replacement field MUST both be valid based on the site certificate handed out by the server in ...
... target in the SRV record MUST both be valid based on the same site certificate. Otherwise, an attacker ...
... values in a different domain, and the client could not validate that this was the desired behavior, or the result of an attack ...
... is not sufficient to conclude this. For example, a web server may have obtained a valid TLS certificate, and secured RRs ...
... inform its peer of its intent to disconnect the transport layer, and that the peer shouldn't reconnect unless it has a valid reason to do so (e.g., message to be forwarded). Upon receipt of the message, the ...


... The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology ...



Google
Web
RFC-Ref