https://github.com/anewton1998/draft-regext-rdap-extensions/issues/56
>> Section 4.2, paragraph 3 >> Extensions MUST explicitly define any required behavioral changes to the >> processing of referrals. If an extension does not make any provision in >> this respect, clients MUST assume the information provided by referrals >> requires no additional processing or modification to use in the >> dereferencing of the referral. > Similar to the comment in 4.1 the same applies here. If the referral is to be > treated as redirect, so that no processing of href is expected from the > client, then anything in the href must fulfill the same requirements as > redirect URL. In this case it is up to the server to assure compatibility of > the request with the link target. An alternative scenario would be if media > type application/rdap+json is an indicator of RDAP resources and in this case > the responsibility shall be put on client to construct a valid RDAP request > compatible with the target server and client's capabilities. In this case one > would need to define this default processing expected from the client. [JS] Sorry, missing your point. That’s what this para is asking of an extension; to guide the client in case anything beyond the default “don’t touch the referral URL” scenario.
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
