[Tls-reg-review] Request to register TLS EXPORTER-BBF-Dying-Gasp label

[William Lupton <[e-mail]>]

Hello,


The Broadband Forum (BBF) would like to register the following TLS Exporter
label:


   - Value: EXPORTER-BBF-Dying-Gasp
   - DTLS-OK: N (because the intended use exports material from TLS, not
   DTLS)
   - Recommended: N
   - Reference: TR-301 Issue 2 Amendment 1 (will be published at
   https://www.broadband-forum.org/technical/download/TR-301_Issue-2_Amendment-1.pdf
   )

The referenced document is currently in the final stages of review but has
not been published yet (the latest published version can be downloaded from
https://www.broadband-forum.org/technical/download/TR-301_Issue-2_Corrigendum-1.pdf;
the new version is due for publication in June 2020). One of the things
delaying publication is that we want to register this label prior to
publication!

We could supply the latest version of the document on request (but would
need reassurance that it will be available only to the expert reviewers).
However, maybe it will be sufficient to quote the relevant section from the
current draft?

Please see below:
--------

8.1.1.2 Dying Gasp Message Format Version 1
...

R-265 The DPU and PMA MUST export the key used to generate the HMAC from
the TLS connection supporting the current DPU/PMA NETCONF connection, using
the keying material export function as defined in RFC 5705 with the
following input parameters:

   - Label = “EXPORTER-BBF-Dying-Gasp”
   - Application context = “Dying-Gasp”
   - Length = 32

--------

Thanks,
William Lupton
Broadband Forum Software Architect