(Status: UNKNOWN) (DOI: 10.17487/RFC0080)
0081 Request for Reference Information. J. Bouknight. December... tus: UNKNOWN)
(DOI: 10.17487/RFC0128)
0129 Request for comments on socket name structure. E. Harslem... 7487/RFC0471)
0472 Illinois' reply to Maxwell's request for graphics information (NIC
14925). S. Bun... (Status: UNKNOWN) (DOI: 10.17487/RFC0509)
0510 Request for network mailbox addresses. J.E. White. May 19
nfo/rfc80>.
RFC0081 | | Bouknight, J., "Request for Reference Information", RFC 81, DOI 10.17487/... | Harslem, E., Heafner, J., and E. Meyer, "Request for comments on socket name structure", RFC 129, ... | Bunch, S., "Illinois' reply to Maxwell's request for graphics information (NIC 14925)", RFC 472, D... g/info/rfc509>.
RFC0510 | | White, J., "Request for network mailbox addresses", RFC 510, DOI 10.1
sk Force (IETF) M. Loffredo
Request for Comments: 9536 ... a valid search condition by returning a 400 (Bad Request)
response when a problematic request is received.
A given reverse search or reverse search mapping ... a user.
It can be implemented by tagging a request with the usage purpose
and making the RDAP
sk Force (IETF) D. Eastlake 3rd
Request for Comments: 9542 ... s required only if the Expert does not reject the request.
It is NOT the same as just "IESG Approval" in... uired only
when the Expert does not reject the request. The procedure is as
follows:
The appl... in turn informs the applicant that their
request is denied; however, if the Expert believes the