Date: Wed, 22 Jan 2020 14:35:13 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKY55KIWPK2D522MRR54GYAKDEVBNHHCCAWIWI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3387/577418196@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3387@github.com>
References: <quicwg/base-drafts/issues/3387@github.com>
Subject: Re: [quicwg/base-drafts] Clarify CANCEL_PUSH server send conditions
 (#3387)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e28ce21125aa_21853fc8d72cd9601081a1";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/uniL4WcSdv85R3SycxqbFYiqIbg>


----==_mimepart_5e28ce21125aa_21853fc8d72cd9601081a1
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

In some cases, creating a stream can result in a STREAM frame being sent.  It depends on the shape of the contract between the different components.  And it also might be difficult to determine whether anything has been sent.

I believe that the existing language is fine.

If you have created a stream object locally, and can be sure that the other side is unaware of this, and you have some means of taking it back or repurposing it, then it's fine to do that.  Note that this is only a "SHOULD" anyway.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3387#issuecomment-577418196
----==_mimepart_5e28ce21125aa_21853fc8d72cd9601081a1
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>In some cases, creating a stream can result in a STREAM frame being sent.  It depends on the shape of the contract between the different components.  And it also might be difficult to determine whether anything has been sent.</p>
<p>I believe that the existing language is fine.</p>
<p>If you have created a stream object locally, and can be sure that the other side is unaware of this, and you have some means of taking it back or repurposing it, then it's fine to do that.  Note that this is only a "SHOULD" anyway.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3387?email_source=notifications&amp;email_token=AFTOJK5BV5ELZJMJTQHM4H3Q7DC2DA5CNFSM4KKNQQAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJVLHVA#issuecomment-577418196">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJKZYLGTGN6UXXLKXSI3Q7DC2DANCNFSM4KKNQQAA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK7444YI5YHEG2BLARTQ7DC2DA5CNFSM4KKNQQAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJVLHVA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3387?email_source=notifications\u0026email_token=AFTOJK5BV5ELZJMJTQHM4H3Q7DC2DA5CNFSM4KKNQQAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJVLHVA#issuecomment-577418196",
"url": "https://github.com/quicwg/base-drafts/issues/3387?email_source=notifications\u0026email_token=AFTOJK5BV5ELZJMJTQHM4H3Q7DC2DA5CNFSM4KKNQQAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJVLHVA#issuecomment-577418196",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e28ce21125aa_21853fc8d72cd9601081a1--