Re: [TLS] (offline) Re: Draft for SM cipher suites used in TLS1.3

"Kepeng Li" <> Sun, 18 August 2019 08:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 23B0B120041 for <>; Sun, 18 Aug 2019 01:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tv1Ftn-yPvsm for <>; Sun, 18 Aug 2019 01:09:29 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5188112001A for <>; Sun, 18 Aug 2019 01:09:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=default; t=1566115762; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=e5ghcgxhq7vLkLcH5aQ4uABDjn+KoQggbKRR/ZbyaXQ=; b=OhlDzULaQ70nBBGFBmM2p2Ho7F6aW9PFVVkKaIJHN1ItkKakoH+4uIRsZ1HH3f50o26eXSdXQMftg5Icq3wh8sFyC4Mtm6UEoMpGyhV/cdHGFPDPZDsdf8piW/uQGPRD8pcGQCbslC2Om58/BOziYI7gbm0MvZjx5rndOMw1S00=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R681e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03275;; NM=1; PH=DW; RN=3; SR=0; TI=dingding_android.COREAPId97b0a46aeea488e929d9023e45cbc73;
Received: from WS-web ([dingding_android.COREAPId97b0a46aeea488e929d9023e45cbc73]) by e01l04452.eu6 at Sun, 18 Aug 2019 16:09:17 +0800
Date: Sun, 18 Aug 2019 16:09:17 +0800
From: "Kepeng Li" <>
To: "=?UTF-8?B?U2FseiwgUmljaA==?=" <>, "Kepeng Li" <>
Cc: "''" <>
Message-ID: <>
X-Priority: 3
X-Mailer: [Alimail-Mailagent]
MIME-Version: 1.0
In-Reply-To: <>
References: <> <>, <>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_28735_483fa940_5d5907ad_1987141"
Archived-At: <>
Subject: Re: [TLS] =?utf-8?q?=28offline=29_Re=3A__Draft_for_SM_cipher_suites_?= =?utf-8?q?used_in_TLS1=2E3?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 18 Aug 2019 08:09:31 -0000

>Can you point to specific drafts where *normative* references are only available for paying a fee?  I guess that there are some, but I don’t know of any. 
This is one example:
[RNC]; ISO/IEC, "Information technology -- Document Schema Definition Language (DSDL) -- Part 2: Regular-grammar-based validation -- RELAX NG", ISO/IEC 19757-2, Annex C: RELAX NG Compact syntax, December 2008.
Kind Regards

发件人:Salz, Rich<>;
日期:8月16日 23:06
收件人:Kepeng Li<>;
输入主题Re: [TLS] (offline) Re: Draft for SM cipher suites used in TLS1.3

>How does the other IETF drafts make the references to ISO documents? ISO documents are often referenced by IETF drafts.
Can you point to specific drafts where *normative* references are only available for paying a fee?  I guess that there are some, but I don’t know of any. Your claim implies definitive knowledge, however.
In general, the IETF tends to dislike using standards where the specification is not freely available in English. That last part, in English, is perhaps narrow-minded these days, but the IETF works in English.  Also, note that I said “tends to dislike” and didn’t claim a hard rule always enforced.  In the past, where there have been issues, it has been not uncommon to write internet-drafts and publish through CFRG; see for many examples. Sometimes they are published as individual stream RFC’s; see for a highly applicable example.