| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Jay, You don’t get to just say what we can do when you, in fact, just learned about this issue about 2 hours ago. You can’t possibly speak authoritatively on the matter. A straw poll doesn’t change anything. Sorry you don’t want to have a
back and forth but then don’t just declare that I’m wrong and we can do what you want.
I think the prudent course of action will be to do nothing at this point since we don’t need to have any reference to draft-vos AT THIS POINT IN TIME. It’s still and individual submission, it has no status really. Let’s wait until we
get an official response from the IETF-IEEE liaison who can bring it up with the relevant parties who know and care about this stuff. Maybe it’ll be OK, maybe it won’t.
By the way, how many Internet-Drafts have you been affiliated with that got held up by the IESG due to a downref issue? I’ll wager that it is zero.
Dan. -- “the object of life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane.” – Marcus Aurelius On 11/10/26, 2:58 PM, "Jay Yang" <yang.zhijie@xxxxxxxxxx> wrote: Hi Dan, Thanks for the quick response. The short answer is we can
normatively refer to the draft based on the cross-reference rule defined in RFC 7241. I don't want to have a back and forth discussion in the reflector; perhaps we need a SP on this tomorrow. Thanks you for the good discussion. 杨志杰10343608 Thanks Best Regards Jay Yang (杨志杰)
Original From: Harkins,Dan <daniel.harkins@xxxxxxx>
To: 杨志杰10343608;
Cc: stds-802-11-tgbt@xxxxxxxxxxxxxxxxx <stds-802-11-tgbt@xxxxxxxxxxxxxxxxx>; Date: 2026年11月10日
15:48 Subject: Re: cross-reference discussion Yes, I believe you are mistaken. It is an issue. A blocker? No, it just means we can’t *normatively* refer to the draft, we can refer to it
informatively as a “work in progress” though. I don’t see that as an issue. If you think it’s an issue then we need to specify the key exchange more fully in the TGbt draft as I have done in 11-26/0089r8. As a bit of history, about 15 years ago I was sent to ISO meetings to deal with a Chinese protocol called WAPI which the China National Body was trying to push in ISO as an “international standard”. As part of
their effort to lift up WAPI, they also tried to drag down 802.11 with spurious claims about insecurity. When their claims were all addressed they finally responded with a challenge that 802.11 was invalid because it was normatively referring to several Informational
RFCs. We had to educate them about the downref procedure and that the normative references at the time had all been given exceptions by the IETF and they then withdrew that complaint. So it seems to me the last thing we, 802.11, want to do is give any more
ammunition to these rogue national bodies in ISO which continue to vote negatively in ISO ballots to approve our 802.11 standard and various amendments as “international standards”. Dan. -- “the object of life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane.” – Marcus Aurelius On 11/10/26, 2:39 PM, "yang.zhijie@xxxxxxxxxx" <yang.zhijie@xxxxxxxxxx>
wrote: Hi Dan, Thanks for the discussion on Downref registry. I copy the link here you provided during the F2F discussion this afternoon. Based on my understanding, it's IETF/IRTF the internal procedure, nothing relevant to 802.11 referring to the I-D of PQC PAKE protocol. I will leave the author of PQC PAKE protocol in CFRG to have a look at this. (e.g. clarify an RFC refer to informational I-D as TLS did if PQC
PAKE protocol becomes an RFC ahead of its references), maybe Peter can have some talk with the author to see how to handle it. But it's not a block issue for us. Please feel free to correct me if I make any mistake. Welcome the further insight.
杨志杰10343608 Thanks Best Regards Jay Yang (杨志杰) To unsubscribe from the STDS-802-11-TGBT list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 To unsubscribe from the STDS-802-11-TGBT list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBT&A=1 |