Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification on connection establishment with LEASE enabled #242

Open
mostroverkhov opened this issue Oct 9, 2017 · 0 comments
Open

Clarification on connection establishment with LEASE enabled #242

mostroverkhov opened this issue Oct 9, 2017 · 0 comments

Comments

@mostroverkhov
Copy link
Member

mostroverkhov commented Oct 9, 2017

Spec in connection establishment

The server-side Requester mirrors the LEASE requests of the client-side Requester. If a client-side Requester sets the L flag in the SETUP frame, the server-side Requester MUST wait for a LEASE
from the client-side Responder before it can send a request. The client-side Responder MUST send a LEASE frame after a SETUP frame with the L flag set.

Later in Sequences with LEASE

Server-side Request, Server-side accepts SETUP
Client connects & sends SETUP with L flag
Server accepts SETUP, sends back LEASE frame
Client sends LEASE frame
Server sends REQUEST

Last quote led me to thinking that client-side Responder MUST wait for LEASE from server-side Responder before issuing its LEASE.

Later in LEASE semantics

A Responder that receives a REQUEST that it can not honor due to LEASE restrictions MUST respond with an ERROR[REJECTED]. This includes an initial LEASE sent as part of Connection Establishment.

So violation of MUST mentioned above has to be punished with sending ERROR on 0 stream, and closing connection. Are these assumptions correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant